Implementing BBI-SS PAS to CICS communication

This chapter describes the steps required to implement BBI-SS PAS to CICS communication.

For sites implementing the MainView for CICS product at the same time as MainView AutoOPERATOR for CICS, use the MainView for CICS Customization Guide and perform the steps described in 'Standard Implementation Procedures.'

This chapter discusses implementation procedures if you are installing MainView AutoOPERATOR for CICS only.

Certain MainView AutoOPERATOR for CICS functions require BBI-SS PAS to CICS communication. However, numerous MainView AutoOPERATOR for CICS functions are available to you if you do not implement BBI-SS PAS-to-CICS communication. See MainView-AutoOPERATOR-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 MainView AutoOPERATOR BBI-SS PAS at a time

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

To begin implementing BBI-SS PAS-to-CICS communication, go to Implementation-considerations-for-BBI-SS-PAS-to-CICS-communication.

Note

If you are running MainView AutoOPERATOR 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 MainView AutoOPERATOR 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.

Refer to the MainView for CICS Customization Guide for more important information about the ACONCICS parameter in BBPARM member BBISSP00.

 

 

 

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