Affinity factor example one

• All BBI-SS PASs are running with ACONCICS=YES set in their respective BBISSP00 parameter members.
• All BBI-SS PASs are running with DYNTGT=NO set in their respective BBISSP00 parameter members (indicating that TGTDEFs will have no affect on the systems).
• The UBBPARM data set for PASA and PASB contains:
  • A BBIJNT00 member with no IBM CICS entries
  • A CMRDTL00 member with an entry for each of the production CICS regions (CICS01-CICS60) only
• The UBBPARM data set for PASC contains:
  • A BBIJNT00 member with no CICS entries
  • A CMRDTL00 member with an entry for each of the test CICS regions (CICS61-CICS72) only
• None of the CICS regions use either the INITPARM SIT parameter or a BBIJNT00/BMCICS00 to indicate to the region which PAS it is to use.

Case 1.A—a new production CICS region (CICS52) becomes active

Because the CICS region does not have a directive to use a specific BBI-SS PAS, it places a request into the common communications request queue. This element is picked up by one of the three BBI-SS PASs, which determines that it should connect to PASB based upon the following accumulated affinity weights:

Case 1.B—a new test CICS region (CICS66) becomes active

Because the CICS region does not have a directive to use a specific BBI-SS PAS, it places a request into the common communications request queue. This element is picked up by one of the three BBI-SS PASs, which determines that it should connect to PASC based upon the following accumulated affinity weights: