AutoConnect affinity factors
The factors include:
presence of a static or dynamic JNT element on the BBI-SS PAS for the CICS region
presence of a CMRDTL00 definition on the BBI-SS PAS for the CICS region
a previous connection between the CICS region and the BBI-SS PAS
presence of the name of a prospective BBI-SS PAS in the communication request
the current count of active CICS regions being managed by a prospective BBI-SS PAS
Each of these factors is given a weight and the weights are accumulated for each prospective BBI-SS PAS. The BBI-SS PAS with the greatest weight is assigned to manage the CICS region. You can use some of these factors to ensure that CICS regions connect with the appropriate BBI-SS PAS.
The following describes the affinity factors and their associated weights.
Affinity factors
Factor | Weight (decimal) | Weight (hexadecimal) | Comment |
---|---|---|---|
The initial weight factor. | 1,024 | 400 | This weight is assigned to every request as a starting point. |
The BBI-SS PAS has a communications link to a CICS region. | -10 | FFFFFFF6 | Negative weight is used to balance the load when more than one BBI-SS PAS is participating in AutoConnect. This factor is added for each CICS region already connected to the BBI-SS PAS. |
The target CICS region was previously attached to the BBI-SS PAS during the current execution of the BBI-SS PAS. | 8,192 | 2000 | This factor may be the result of recycling the CICS region, or terminating and restarting the MainView for CICS agent on the CICS region. |
The BBI-SS PAS has a static JNT element for the target CICS region (from a target entry in the BBIJNT00 parameter member). 1 | 16,384 | 4000 | This factor can be provided by using a BBIJNT00 element for the target CICS region on the BBI-SS PAS. Not used if the site utilizes the ACONCICS=ONLY parameter. |
The BBI-SS PAS has a dynamic JNT element for the target CICS region(from a TGTDEF). 1 | 8,191 | 1FFF | This factor can be provided by using a TGTDEF for the target CICS region. Not used if the site utilizes the ACONCICS=ONLY parameter. |
The target CICS region was provided the name of a BBI-SS PAS from an INITPARM parameter. 1 | 10,240 | 2800 | This factor can be provided by using an INITPARM parameter in the CICS SIT. |
The target CICS region was provided the name of a BBI-SS PAS internally. | 15,360 | 3C00 | This is the result of the MainView for CICS agent on the target CICS region having been terminated and restarted, or the BBI-SS PAS having been recycled. The agent remembers the state of the connection and various processes when it is terminated. |
The target CICS region was provided the name of a candidate BBI-SS PAS through the FST2 transaction. 1 | 1,073,741,823 | 3FFFFFFF | The FST2 transaction can be used to force the connection of a CICS region to a specified BBI-SS PAS by issuing FST2 INIT xxxx where xxxx is the name of the candidate BBI-SS PAS. |
The BBI-SS PAS already has an active service point for the target CICS region. | 805,306,367 | 2FFFFFFF | This normally means the CICS region has previously connected to the BBI-SS PAS. |
The BBI-SS PAS has a static or dynamic JNT element for the target CICS region and the CICS region has provided the name of the BBI-SS PAS as its preferred candidate. 1 | 536,870,911 | 1FFFFFFF | This large weight results from the combination of both the BBI-SS PAS and the CICS region basically agreeing that they should establish communications. |
The BBI-SS PAS has a CMRDETL definition for the target CICS region in it CMRDTL00 parameter member and the file can be allocated to the BBI-SS PAS job/started task. 1 | 3,072 | C00 | This weight is an indication of the ability of the BBI-SS PAS to record MainView for CICS transaction performance data as history records. |
The target CICS provides a directive in the member BMCICSnn or BBIJNTnn. 1 | 14,336 | 3800 | This factor can be provided in the CICS JCL by specifying a BBIPARM DD statement that refers to the data set that contains the member BMCICSnn or BBIJNTnn. |
|
Comments
Log in or register to comment.