Implementing a legacy multiple-RMGR configuration
This legacy RMGR configuration enables IMS systems that participate in a data-sharing environment to use the same RMGR resources and functions. BMC now provides the RMGR configuration to serve this purpose with less effort to implement, maintain, and operate RMGR components. BMC no longer recommends the RMGR configuration unless you are using the APPLICATION RESTART Control (AR/CTL) suspend-and-resume interface.
In a legacy multiple-RMGR configuration for an environment in which two or more IMS systems will share data, you must set up a sharegroup and create an RMGR for each IMS that is involved in data sharing. The RMGRs must belong to the same RMGR sharegroup, whether the IMS systems are running on one operating system or on different systems in a sysplex environment. Each IMS system is connected to its own RMGR. One repository is shared by all RMGRs that belong to the sharegroup.
In the repository, you must create a sharegroup environment record. You can also create IMS environment records if needed; if any IMS system in the sharegroup is at a different version level than the one defined in the sharegroup definition record, an individual IMS environment record is required. When you submit function requests through the ISPF interface or the Batch Interface utility, you can specify the sharegroup name or an RMGR name.
When you configure RMGR for use in a SYSPLEX environment, the procedure is identical to configuring RMGR in a data-sharing environment. You must set up a sharegroup and create an RMGR for each IMS system in the SYSPLEX.
The following figure shows a typical data-sharing environment.
Typical data-sharing environment
To achieve all of the functionality that RMGR is designed to provide in an IMS data-sharing or sysplex environment, an RMGR instance must be configured and available for each IMS instance that is involved in data sharing. This requirement applies whether an IMS instance is on the same or different system image as the other IMS instances, as long as the IMS instances communicate with each other by using the Cross-System Coupling Facility (XCF).
RMGR provides considerable functionality even if only one RMGR instance is available to participate in an IMS data-sharing environment. The following functions and utilities are available in this case:
Batch Interface utility (the functions that do not require IMS commands)
Check Assets function
Automatic Delete/Define (DRAMS) utility
Find Recovery Points function
Group Build function
Group Rebuild function
Group Validation function
Log Analysis function
Disaster Recovery RECON Cleanup (DRRCN) utility
Recovery Advisor functions (available only with BRS)
Create Recovery JCL function (/DBR of databases must be done manually)
When only one RMGR instance is used in a data-sharing environment, the unavailable RMGR functionality is related to issuing and validating IMS commands across all of the IMS instances. The following RMGR functionality is unavailable in this case:
Hold Point of Consistency (HPC) function: issuing /DBR and /STA commands to create quiet points for recovery
IMS Command utility: issuing various IMS commands in batch
Log Sync function: issuing /SWI command to synchronize log switches across multiple IMS instances
To implement a legacy multiple-RMGR configuration
Comments
Log in or register to comment.