Preparing to Use Remote Journals

Before establishing the remote journal environment, complete the following steps:

Determine the extent of your remote journal network or environment.
Library redirection is the ability to allow the remote journal and associated journal receivers to reside in different libraries on the target system from the corresponding source journal and its associated journal receivers.

Determine what library redirection, if any, you will be using for the remote journals and associated journal receivers.
Ensure that all selected libraries exist on the target systems. You must consider whether or not library redirection will be used when adding the remote journal.
Create the appropriate local journal if it does not already exist.
Configure and activate the communications protocol you have chosen to use.
After you have configured the communications protocol, it must be active while you are using the remote journal function.

For example, if you are using the OptiConnect for IBM i bus transport method, then the OptiConnect for IBM i subsystem, QSOC, must be active. QSOC must be active for both the source system and the target system, and the appropriate controllers and devices must be varied on. If you are using a SNA communications transport, vary on the appropriate line, controller, and devices and ensure subsystem QCMN is active on both systems. Start of change If you are using TCP/IP or Sockets IPv6, you must start TCP/IP by using the Start TCP/IP (STRTCP) command, including the distributed data management (DDM) servers. If you are using data port, you must configure a cluster, make sure that the cluster is active, and start the internet Daemon (inetd) server using the Start TCP/IP Server (STRTCPSVR) command.End of change
If one does not already exist, create the appropriate relational database (RDB) directory entry that will be used to define the communications protocol for the remote journal environment. When TCP communications are being used to connect to an independent disk pool, the RDB entry to the independent disk pool must have the Relational database value set to the target system's local RDB entry and the relational database alias value set to the independent disk pool's name.

Now you should be able to see the remote database connection by issuing the WRKRDBDIRE command.

 Work with Relational Database Directory Entries
 
 Position to . . . . . .
 
 Type options, press Enter.
   1=Add 2=Change 4=Remove 5=Display details 6=Print details
 
                             Remote
 Option Entry Location Text
 
         SYS1 system1
         SYS2 system2
         MYSYSTEM *LOCAL Entry added by system
         
         
          
          
 
 
 
 
                                                                         Bottom
 F3=Exit F5=Refresh F6=Print list F12=Cancel F22=Display entire field
 (C) COPYRIGHT IBM CORP. 1980, 2007.