The optional IMS Operations Facility (IOF) obtains IMS commands and unsolicited messages from the IMS AOI exit points. CA OPS/MVS dynamically inserts AOI exits into each IMS that you start. There are sample AOI exits in IMS that you may need to install. The CA OPS/MVS AOI exit does not preclude you from using your own AOI exit.
The CA OPS/MVS parameter IMSnINSTALLEXITS can be set to YES (the default value) for each IMS system to install the IOF exits at IMS initialization. Setting this parameter to NO before starting IMS bypasses the installation of the IOF exits.
Note: If the IOF exits were installed during the last initialization of IMS, setting this parameter to NO does not uninstall the exits. A recycle of IMS is required to remove the exits. If IMS was previously initialized without the IOF exits installed, setting this parameter to YES while IMS is up automatically installs the IOF exits on the next message event from that IMS system.
Note: The use of the IOF batch message processing (BMP) for issuing IMS commands without using the IMS WTOR is not affected by whether the IOF AOI exits are installed. There are two AOI exits. The original IMS AOI exit, DFSAOUE0, which is now designated as a TYPE 1 exit, was invoked only on a DB/DC or DCCTL-only system. A second AOI exit type, DFSAOE00, which is designated as a TYPE 2 exit, is invoked in all IMS system types (DB/TM, TM‑only, and DBCTL-only). Currently, DBCTL-only IMS systems are not fully supported by the IOF. It is recommended that the OPS/MVS parameter, IMSnCHAR, for that IMS, be set to a character that is not equal to the CRC (command recognition character) of the DBCTL region.
If you do not have your own AOI exits (either a TYPE 1 or TYPE 2 exit) installed, then you must install the sample exits provided in the OPS.CCLXASM library. Browse your IMS RESLIB to check whether any AOI exits have been installed. If the exits are not in the RESLIB, you must install the corresponding sample exits. In the OPS.CCLXASM library, the sample TYPE 1 exit member name is OPSAOUE0, and the sample TYPE 2 name is OPSAOE00. These sample members must be assembled and link-edited into the RESLIB. The proper link-edit statements are provided at the end of each member. The OPSAOUE0 and OPSAOE00 members in the OPS.CCLXCNTL library contain JCL and related usage instructions.
In an IMS Transaction Manager (TM) environment, the possibility of multiple exit types adds a level of coexistence complexity of which a CA OPS/MVS user must be aware.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|