Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for CICS, version 7.3

Affinity factor example two

This example assumes that these parameter settings are in effect:
  • PASA and PASB are running with ACONCICS=YES set in their respective BBISSP00 parameter members.

  • PASC is running without an ACONCICS= parameter (the same as ACONCICS=NO).

  • All BBI-SS PASs are running with DYNTGT=YES set in their respective BBISSP00 parameter members (indicating that TGTDEFs will be honored on the systems)

  • CASA contains TGTDEFs relating PASA to CICS01–CICS30, PASB to CICS31–CICS60 and PASC to CICS61–CICS75

  • The UBBPARM data set for PASA and PASB contains:

    • A BBIJNT00 member with no 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

  • CICS01–CICS60 do not use either the INITPARM SIT parameter or a BBIJNT00/BMCICS00 to indicate to the region which PAS it is to use.

  • CICS61–CICS75 use an INITPARM SIT parameter to indicate to the regions that they are to connect with PASC.

Case 2.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 either PASA or PASB (PASC is not participating in AutoConnect), which determines that it should connect to PASB based upon the following accumulated affinity weights:

PAS

Weights

Description

PASA

 1024
 -240
 3072
3826

Initial weight

Weight for each connected CICS region (negative)

Weight for BBI-SS PAS having CMRDTL00 entry for the region

Total weight for BBI-SS PAS

PASB

 1024
 -240
 3072
 8191
12047

Initial weight

Weight for each connected CICS region (negative)

Weight for BBI-SS PAS having CMRDTL00 entry for the region

Weight for a TGTDEF relating CICS52 to PASB

Total weight for BBI-SS PAS

PASC

NA

Not participating in AutoConnect

Case 2.B—a new production CICS region (CICS53) becomes active

The user wants the new CICS to be connected to PASA, so a directive of PASA is specified by using the INITPARM in CICS. CICS53 will connect to PASA based upon the following accumulated affinity weights:

PAS

Weights

Description

PASA

 1024
  -240
 10240
 3072
14066

Initial weight

Weight for each connected CICS region (negative)

Weight for specifying PASA in INITPARM

Weight for BBI-SS PAS having CMRDTL00 entry for the region

Total weight for BBI-SS PAS

PASB

 1024
 -240
 3072
 8191
12047

Initial weight

Weight for each connected CICS region (negative)

Weight for BBI-SS PAS having CMRDTL00 entry for the region

Weight for a TGTDEF relating CICS52 to PASB

Total weight for BBI-SS PAS

PASC

NA

Not participating in AutoConnect

Case 2.C—a new test CICS region (CICS66) becomes active

Because the CICS region has a directive to use a specific BBI-SS PAS, it examines the subsystem blocks for PASC and determines that it is not participating in AutoConnect. It then makes a direct connection to PASC.

PAS

Weights

Description

PASA

NA


PASB

NA


PASC

NA

Not participating in AutoConnect

Was this page helpful? Yes No Submitting... Thank you

Comments