A replication environment with DB2 Universal Database for OS/390 (DB2 for OS/390) data servers differs from other non-Sybase replication environments because RSM does not manage the Replication Agent for DB2 UDB for OS/390. Additionally, the Replication Agent cannot retrieve metadata from the DB2 for OS/390 database.
As with other non-Sybase data servers, DB2 for OS/390 has three environment configurations:
Primary-only
Replicate-only
Bidirectional
A DB2 for OS/390 replicate-only environment uses the same server configuration as other non-Sybase, replicate-only configurations. The following sections describe the DB2 for OS/390 primary-only and bidirectional configurations.
A primary-only connection is used when the DB2 for OS/390 database is only the source of replicated data (that is, data does not flow out to the DB2 database). RSM uses a DirectConnect for OS/390 gateway server to retrieve metadata from DB2 for OS/390.
As with other non-Sybase primary-only configurations, the DB2 for OS/390 primary-only solution is implemented in RSM.
The Replication Server database connection is set up as a primary-and-replicate connection, but RSM filters out the status of the DSI thread, and reports only the state of the Rep Agent User thread. The DSI thread still exists in the Replication Server in a suspended state.
The following servers are required to set up a DB2 for OS/390 primary-only configuration:
DB2 Universal Database for OS/390 primary data server
Replication Agent for DB2 UDB for OS/390
Replication Server
Replicate data server
DirectConnect for OS/390
RSM Server
The following limitations apply to a DB2 for OS/390 primary-only connection:
RSM does not support either a ping cycle or a heartbeat process for a primary-only connection because the DSI thread in the Replication Server is in a suspended state. If either the ping cycle or the heartbeat process is needed, set up a bidirectional configuration.
RSM cannot manage or monitor the Replication Agent for DB2 UDB for OS/390. You must set all Replication Agent configuration parameters manually.
A bidirectional (primary-and-replicate) connection is used when the DB2 for OS/390 database is both a source and target of replication. The DB2 for OS/390 bidirectional connection configuration uses a Replication Agent for DB2 UDB for OS/390 to retrieve data from the DB2 database, and a DirectConnect for OS/390 (or MainframeConnect in a gatewayless environment) to send data to the database. RSM can use DirectConnect for OS/390 to retrieve metadata from the DB2 for OS/390 database.
The following servers are required to set up a DB2 for OS/390 bidirectional configuration:
DB2 Universal Database for OS/390 data server
Replication Agent for DB2 UDB for OS/390
Replication Server
DirectConnect for OS/390 (or MainframeConnect in a gatewayless environment)
RSM Server
The following limitations apply to a DB2 for OS/390 bidirectional connection:
RSM does not validate Maintenance User permissions at the replicate database when it creates a subscription for a non-Sybase replicate data server.
RSM does not validate the table columns or stored procedure parameters by comparing the primary and replicate databases when it creates a subscription for a non-Sybase replicate data server.
RSM cannot manage or monitor the Replication Agent for DB2 UDB for OS/390. You must set all Replication Agent configuration parameters manually.
