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 BBI-SS PAS to IBM CICS communication

For sites implementing the 

BMC AMI Ops Monitor for CICS

 product at the same time as 

BMC AMI Ops Automation for CICS

, see 

Customizing after installation (BMC AMI Ops Monitor for CICS)

 and perform the steps described in 

Standard implementation

.  This section discusses implementation procedures if you are installing 

BMC AMI Ops Automation for CICS

 only.

Certain BMC AMI Ops Automation for CICS functions require BBI-SS PAS to CICS communication. However, numerous BMC AMI Ops Automation for CICS functions are available to you if you do not implement BBI-SS PAS-to-CICS communication. See BMC-AMI-Ops-Automation-for-CICS-functions-with-BBI-SS-PAS-to-CICS-communication for additional information.

Note

A CICS target can only connect to, and be automated by, one BMC AMI Ops Automation PAS at a time

The following steps are required to implement BBI-SS PAS to CICS communication

Note

If you are running BMC AMI Ops Automation for CICS and in BBPARM member BBISSP00 you specified ACONCICS=ONLY or ACONCICS=YES with no static or dynamic target definition, all CICS commands that can be used in BMC AMI OpsA Rules and EXECs are dependent, which means they will not be available until the CICS region target has established communications with the BBI-SS PAS.

For more important information about the ACONCICS parameter in BBPARM member BBISSP00, see BBISSP parameter.

This section contains the following topics:

 


 

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