Configuring the IMS Commander Type-2 Automated Operator user exit

The IMS Commander component collects messages and commands that are destined for the IMS master terminal, for type-1 commands entered from APPC or OTMA connections, and for responses to those type-1 commands. z/OS Console messages for the IMS control regions (CTL, DLISAS, DBRC, IRLM) are collected and added to the IMS Commander repository. You can view the repository by using the enhanced 3270 user interface.

Choose a proper installation option and complete the steps for the configuration:

• Stand-alone exit.
  
  The rtehilev.RKANMODR data set contains member DFSAOE00, which is the member name that IMS searches during startup. Then, the DFSAOE00 module loads other modules from this library to the IMS environment.
  1. Add the rtehilev.RKANMODR data set to the IMS Control Region's STEPLIB concatenation.
     Note: Ensure that the DFSAOE00 module in this library is concatenated before any other same named module.
  2. After the IMS Control Region JCL is updated, recycle the IMS system to activate the OMEGAMON IMS Commander user exit support.
• User exit calling a second user exit.
  
  The rtehilev.RKANMODR data set contains member DFSAOE00, which is the member name that IMS searches during startup. Then, the DFSAOE00 module loads other modules from this library to the IMS environment.
  1. Add the rtehilev.RKANMODR data set to the IMS Control Regions STEPLIB concatenation.
     Note: Ensure that the DFSAOE00 module in this library is concatenated before any other same named module.
  2. Add the alternate load library to the IMS Control Regions STEPLIB concatenation after the rtehilev.RKANMODR data set.
  3. Update the IMS PROCLIB member KOIPiiii and add the following parameter, where iiii is the IMS ID:

     ILOGALTMODULE=cccccccc

     Where cccccccc is the name of the alternate load module that the OMEGAMON IMS Commander Type-2 Automated Operator user exit calls for each message.
  4. After the IMS Control Region JCL is updated, recycle the IMS system to activate the OMEGAMON IMS Commander user exit support.
• IMS multi-user exit.
  1. If you have another, non-OMEGAMON, exit of the same type which has a DFS* name or alias and you do not specify this exit in the DFSDFxxx member, this may cause a duplicate-name conflict with OMEGAMON. To prevent the conflict, you have two options. The first option is to concatenate the library containing the non-OMEGAMON exit before the OMEGAMON library; The other option is to delete the DFS* alias of the OMEGAMON exit prior to recycling the IMS. This can be done using the sample JCL in xKANSAM(KOIXDFSA). Note that the DFS* alias for this exit is provided for backward compatibility with installations using the stand-alone exit option. Any future maintenance applied to this exit will again contain the DFS* alias which will then also need to be deleted.
  2. Add the rtehilev.RKANMODR data set to the IMS Control Region's STEPLIB concatenation.
  3. Add the AOIE user exit definition to the IMS PROCLIB member DFSDFxxx:

     EXITDEF=(TYPE=AOIE,EXITS=(KOIAOE00))

  4. After the Control Region JCL is updated, recycle the IMS system to activate the OMEGAMON IMS Commander user exit.