Connection facility
BMC AMI Ops Monitor for CICS
establishes communications with target IBM CICS regions using the connection facility. It is based on entries in the Jobname Node Table (JNT), which is allocated in private storage of the BBI-SS PAS.
This table is also used by various other BMC products. Entries are added to the JNT in the following ways:
- From the static elements contained in the UBBPARM member BBIJNT00
- From Dynamic Target Definition (TGTDEF) elements
- Built at the request of the AutoConnect facility (recommended)
These sources, used separately or together, provide a wide range of options and methods to manage your CICS regions.
The connection facility has two parts:
- Code that executes during BMC AMI OpsM for CICS agent initialization on the CICS region requests the assignment of a BBI-SS PAS, or requests a specific BBI-SS PAS by using a BBI-SS PAS directive, as described in Providing-a-BBI-SS-PAS-directive-to-a-target-CICS-region
- Code that executes on the BBI-SS PAS
- Manages the common request queue (this queue is shared by each BBI-SS PAS running on an LPAR)
- Processes the requests from the common request queue and assigns the appropriate BBI-SS PAS based on a user requested control.
- Manages the creation and deletion of the resources (control blocks, tasks, and so on) that are needed to manage an assigned CICS region
The connection facility enables you to have as much or as little control over which CICS connects to which BBI-SS PAS running in the same LPAR as you want. Control is specified with parameter ACONCICS= in member BBISSPnn in UBBPARM.
This section contains the following topics:
Related topic