Implementing BBI-SS PAS to CICS communication
- Site-specific security
- Specifying resources to CICS
- Using auto maintenance
- Modifying CICS startup JCL
- Restarting CICS target regions
- MainView AutoOPERATOR for CICS functions (with BBI-SS PAS-to-CICS communication)
- MainView AutoOPERATOR for CICS functions (without BBI-SS PAS-to-CICS communication)
This section 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.
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
Specify resources to CICS: see Specifying resources to CICS
Modify CICS startup JCL: see Modifying CICS startup JCL
Restart CICS target regions: see Restarting CICS target regions
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.