ObjectConnect for Db2 Mirror
ObjectConnect provides an efficient way to copy objects from one IBM®® i to another without requiring disk space to store an intermediate copy of the objects that are being copied. ObjectConnect copy operations are initiated using Control Language (CL) commands, which are similar to the save and restore CL commands. SQL services described in this section are used to configure and monitor ObjectConnect for Db2® Mirror.
When ObjectConnect is used in the Db2 Mirror environment, called ObjectConnect for Db2 Mirror, the ObjectConnect commands use the MIRROR_OTHER Network Redundancy Group (NRG) to copy objects from one node to the other. ObjectConnect can only be used to copy objects which are not replicated by Db2 Mirror. Objects that can be copied using ObjectConnect for Db2 Mirror are those objects that are either not eligible for replication or have been configured in Db2 Mirror to not be replicated. Objects that cannot be copied are skipped with no error or warnings.
To execute CL commands using ObjectConnect for Db2 Mirror, the ObjectConnect for Db2 Mirror Server must be started on the target node.
See ObjectConnect function for more details about ObjectConnect.
Configuring ObjectConnect for Db2 Mirror
Before using ObjectConnect for Db2 Mirror, it can be configured by using the SQL procedure QSYS2.CHANGE_MIRROR_OBJECTCONNECT. See CHANGE_MIRROR_OBJECTCONNECT procedure for details.
The default configuration is to start ObjectConnect for Db2 Mirror automatically when the MIRROR_OTHER NRG become active, with the minimum number of jobs set to 1, maximum number of jobs set to 5, and inactive time set to 30 minutes.
Starting and stopping the ObjectConnect for Db2 Mirror Server
When ObjectConnect for Db2 Mirror is configured with the AUTO_START parameter set to YES, a single ObjectConnect for Db2 Mirror receiver job is started when the System Object Replicate NRG becomes active. The receiver job is ended when the System Object Replicate NRG becomes inactive.
The ObjectConnect for Db2 Mirror receiver job, named QOBJCMRRCV, starts multiple ObjectConnect for Db2 Mirror server jobs, named QOBJCMRSVR, to service any ObjectConnect operations. These jobs run in the QUSRWRK subsystem. The number of server jobs started is specified by the MINIMUM_JOBS configuration parameter.
The QSYS2.CHANGE_MIRROR_OBJECTCONNECT procedure can be used to start or end the ObjectConnect for Db2 Mirror server manually.
Reviewing the ObjectConnect for Db2 Mirror status and configuration
Use the MIRROR_OBJECTCONNECT_INFO view to display configuration information for ObjectConnect for Db2 Mirror and the server status.
SELECT * FROM QSYS2.MIRROR_OBJECTCONNECT_INFO;