Skip to Content
Information
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.

Implementing an EXEC

After an EXEC has been designed, coded, and tested, it can be implemented in 

BMC AMI Ops Automation

 by using the step below:

  • Move the EXEC to a data set in the SYSPROC or the SYSEXEC library concatenation of your production BBI-SS PAS.

    If you use both the SYSPROC and SYSEXEC members, the following limitations apply:

    • If you have an EXEC with the same name in both the SYSPROC and SYSEXEC members, the EXEC is SYSEXEC is executed.

    • If you have an EXEC with the same name in both the SYSPROC and SYSEXEC members, disabling the EXEC in one member also disables it in the other member.

      In other words, the EXEC always has the same status, no matter which member it is in.

    • Both SYSPROC and SYSEXEC can be browsed from the EXEC Management application.

    • If you try to schedule an EXEC from the EXEC Management application that is listed in SYSPROC and is also listed in SYSEXEC, you will receive an error message.

Related topic

Controlling-EXEC-execution

 

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

BMC AMI Ops Automation 8.3