Enabling AO exit routines


You can skip this section if you have an earlier version of BMC AMI Ops Automation for IMS installed and will use the same method for defining your exits in the new version.

IBM IMS gives control to AO exit routines to do initialization processing and to do message processing. BMC supplies AO exit routine to do initialization processing and message processing. You can define your own exits with the AOEINIT, AOEXIT, and AOIEXIT parameters, in an imsidSYS member in the UBBPARM dataset or in an IMFSYS00 member in an ibbparm dataset. For IMS 13.1 and above, you can alternatively define your exits, and the BMC exits, directly to IMS. However, they should not be defined in both places. Unless you want to define them in DFSDFxxx, no changes are needed when using IMS 13.1 or above.

BMC supplies two AO exit routines to do message processing: a type-1 AO exit routine, DFSAOUE0, and a type-2 AO exit routine, DFSAOE00. See the IBM documentation IMS Operations Guide for an explanation of how the DFSAOUE0 and DFSAOE00 routines differ.

The DFSAOUE0 and DFSAOE00 routines capture MTO messages and IMS commands and pass them to BMC AMI Ops Automation for IMS. They also perform the following functions:

  • provide an interface with your AO exit routines (unless you use DFSDFxxx)
  • automatically start up BMC AMI Ops Monitor for IMS monitors when IMS starts up
  • provide an interface between the Event Collector and the BBI-SS PAS for workload data collection
  • initialize the Event Collector

If you use DFSDFxxx to define your own AO initialization or message processing exits, the BMC DFSAOE00 message exit must also be defined as the last exit in the DFSDFxxx TYPE=AOIE,EXITDEF= list. In that case, you should also remove any AOEINIT, AOEEXIT, and AOIEXIT parameters from your BMC parameter library to avoid warning messages. Type-1 exits are not used in this case.

The following describes how BMC manages the AO exits and the features it provides. It does not apply if you define them directly to IMS through DFSDFxxx. In that case IMS manages and dispatches them.

On entry to DFSAOE00 with AOE0FUNC=1, BMC AMI Ops Monitor for IMS loads and executes any user exit specified in AOEINIT=xxxxxxxx one time only. The DFSAOE00 exit does not forward control to the user’s DFSAOE01 exit on the initialization call.

If you require a DFSAOE00 or DFSAOUE0 exit routine in addition to the exit provided by BMC, perform Step 1 and Step 2 below.

To enable AO exit routines

  1. If you have
    1. One DFSAOE00 exit: Rename it DFSAOE01, or choose a different name and use the control statements described in Step B.
    2. Multiple DFSAOE00 exits in addition to the BMC Software-supplied exit, or one exit not named DFSAOE01: You must add one or more of the following AOEEXIT control statements to an imsid SYS member in UBBPARM or an IMFSYS00 member in an ibbparm data set.

      AOEEXIT=MYNAME

      AOEEXIT=DFSAOE02

      In the example above, both exits are loaded and executed by the BMC DFSAOE00 exit. Program MYNAME executes first.


  2. If you have
    1. one DFSAOUE0 exit: Rename it DFSAOUE1, or choose a different name and use the control statements described in Step B.
    2. multiple DFSAOUE0 exits in addition to the BMC Software-supplied exit, or one or more exits not named DFSAOUE1: You must add one or more of the following AOIEXIT control statements to the imsidSYS member in UBBPARM or in an IMFSYS00 member in an ibbparm data set.

      AOIEXIT=MYNAME

      AOIEXIT=DFSAOUE2

      In the example above, both exits are loaded and executed by the BMC DFSAOE00 exit. Program MYNAME executes first.


This section contains the following the topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*