The remote journal function supports the following communications protocols for replicating the journal entries to the remote systems:
- OptiConnect for i5/OS. If you want to use the OptiConnect for i5/OS® support, you must purchase and install the required hardware and software for that support. Refer to OptiConnect for i5/OS for more information.
- Systems Network Architecture (SNA). If you want to use SNA for the transport, there are no additional software considerations. The software support is in the base operating system. You must purchase whatever hardware is appropriate for your configuration. For more information see SNA Distribution Services on the V5R1 Supplemental Manuals Web site.
- Transmission Control Protocol/Internet Protocol(TCP/IP). If you
want to use TCP/IP for the transport, there are no additional software considerations.
The software support is in the base operating system. You must purchase whatever
hardware is appropriate for your configuration. Refer to TCP/IP Configuration and Reference for
more information.Note: All remote journal TCP connections use the TCP local port of 3777.
Specifying a relational database (RDB) directory entry will identify the communications protocol that the remote journal function will use. The RDB that is specified must meet the following rules:
- The communications protocol must be one of the remote journal function supported protocols.
- The remote location name in the RDB cannot refer to the *LOCAL database.
- The RDB cannot use an application requester driver program (*ARDPGM) to locate the target system.
When TCP communications are being used to connect to an independent
disk pool, the Relational Database (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.
For more information about creating relational databases, refer to the Distributed Database Programming.
Security of the remote journal function is dependent on the communications protocol security. The remote journal function does not alter the security characteristics that are available.
The communications function that is identified by the RDB can be shared by other activity. However, you may consider isolating the remote journal function activity in order to have the best performance.