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 the AOAnywhere batch interface AOSUBX

For batch jobs, AOAnywhere contains a facility called AOSUBX. This facility is a partial replacement for the existing IMFSUBEX function. Both functions allow you to schedule an EXEC from a batch step with the PARM= specification.

Both facilities allow for requests to be scheduled across systems. However, AOSUBX (unlike IMFSUBEX), requires sysplex connectivity between the systems.

In addition, AOSUBX offers significantly shorter execution time and the ability to wait for EXECs scheduled across systems without tying up the VTAM link between multiple BBI-SS PASs. When sysplex connectivity exists, (as it should when using AOSUBX), you should always choose AOSUBX for EXEC invocation.

In a TSO/E environment, a suite of command processor functions is available under the AOEXEC facility. See AOEXEC-commands for more information. This approach is preferred under TSO/E as opposed to using the AOSUBX facility.

This section contains the following topics: 

Related topic

Performing-automation-with-the-AOAnywhere-API

 

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