You can run multiple LTM for MVS instances in your replication system to obtain the following:
Improved performance of your replication system if you are replicating large volumes of transaction information
Access to multiple DB2 subsystems
Access to multiple DB2 data-sharing groups
For each LTM for MVS instance in your replication system, you must have uniquely named versions of some, but not all, data sets. The following tables shows which data sets must be unique, and which can be unique or shared:
Data set description |
Data set name |
---|---|
LTM for MVS configuration data set |
hlq.JCL(LTMCNFG) |
Truncation point data set |
hlq.ssid.TRUNCPT |
RA message data set |
hlq.ssid.LTMLOG |
Data set description |
Data set name |
---|---|
RA DB2 load library |
hlq.RA.LINKLIB |
DB2 table specifying which tables to replicate |
creator.LTMOBJECTS |