Define cross-system communication

Use the following procedure to set up CAS-to-CAS communication and BBI-SS PAS to BBI-SS PAS communication.

Tip

This task is optional for all products.

Related topic

Manual-customization

With cross-system communication, a single terminal session, using one or more BMC AMI Ops products, can monitor and manage multiple local or remote targets (the operating system itself in a sysplex or non-sysplex environment, and subsystems like CICS, IMS, and Db2).

A terminal session connects to:

  • A CAS (if a CAS is available)

    A CAS communicates with other CASs on other local and remote systems and allows direct communication between an individual terminal session and a PAS. Usually, one CAS runs per system image, but there is no limit to the number of remote CASs with which a single CAS can communicate.

  • A BBI-SS PAS

    BBI-SS PASs on local and remote systems are linked together to provide:

    • Cross-system communication for various processes within the PAS
    • Individual terminal sessions communication through a local BBI-SS PAS to any other BBI-SS PAS

    Depending on the products that are installed, the BBI-SS PAS might also connect to a CAS on that system image.

The Defining cross-system communicationfigure provides an overview of cross-system communication.

When CASs reside in the same sysplex, CAS-to-CAS communication is established automatically through the Cross-System Coupling Facility (XCF), as shown in the Cross-system communication in a sysplex environment figure.


Defining cross-system communication


    • ====

Defining MainView cross-system communication.png

Cross-system communication in a sysplex environment


    • ====

Cross-system communication in a sysplex environment.png

This section contains the following topics:

 

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