Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Reviewing the use of NetView exit DSIEX02A

BMC AMI Ops Automation Access NV

 uses the NetView exit DSIEX02A.

If you do not have a DSIEX02A exit, skip step 2 and go to step 3.

If you already use this exit, perform the following steps to ensure that your existing DSIEX02A exit and the BMC AMI Ops Automation Access NV DSIEX02A exit can coexist:

  1. Rename your existing DSIEX02A load module to DSIEX02B.

  2. Link the two exits by using the following linkage editor statements:

    //OLDLIB  DD DSN=your.user.exit.library
    //SYSLMOD DD DSN=AutoOPERATOR.BBLINK
    //SYSIN   DD *
       CHANGE DSIEX02A(DSIEX02B)
       INCLUDE OLDLIB(DSIEX02A)
       INCLUDE SYSLMOD(DSIEX02A)
       ORDER DSIEX02A
       ENTRY DSIEX02A
       NAME DSIEX02A(R)
    /*

    BMC AMI Ops Automation Access NV first passes control to DSIEX02B. If DSIEX02B has modified the incoming message, BMC AMI Ops Automation Access NV processes the modified message. If the exit indicates that the message should be discarded, BMC AMI Ops Automation Access NV returns control to NetView with a return code 4.

  3. For NetView version 5.1 and later, you must modify the DSIPARM member CNMSTYLE to activate this exit.See the Tivoli NetView for z/OS Administration Reference Guide for more information about loading NetView exits (LOADEXIT).

Related topic

Implementing-BMC-AMI-Ops-Automation-Access-NV

 

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