Previous Topic: BMP Versus WTOR Output DisplaysNext Topic: Install the XTDOUT COF Interface for CICS/TS


IMS Type 2 Message Considerations

IMS Type 2 message protocol is used for communicating from an OPS/MVS system to any IMS system that is a member of an IMSPLEX. The communication can be local, that is, from OPS/MVS to an IMS system on the same LPAR with the ability to contact an active IMSPLEX. It may also be cross-system, where OPS/MVS can send the IMS command using an MSF connection to another OPS/MVS system, and then to the IMPLEX from there. The issuing OPS/MVS does not communicate with IMS directly, and the target OPS/MVS is the one with the requirement to contact an IMSPLEX manager.

If this facility is used, two IBM-supplied modules, CSLSDR00 and CSLSRG00, must be available to the OPS/MVS system that is in contact with the IMSPLEX. IBM provides the modules in the IMS RESLIB, and various choices are available:

The modules are downward compatible down to IMS 9. The modules from the highest IMS release should be used, and are able to service a site with a mixture of IMS systems at different release levels.

CA OPS/MVS has no requirements for any specific or unique IMSPLEX configuration or startup options. The IMSPLEX itself is tailored according to site standards, and the name is provided to the CA OPS/MVS commands at execution.

IMSPLEX security considerations for Type2 messages and commands are described in IBM manual IMS Vnn IMSplex Admin. Guide. The specific area of interest is the CA OPS/MVS interface with the components SCI and OM of the Common Service Layer (CSL).