Is there conflicting usage of APPC modegroups?

There is a possibility of conflicting APPC modegroup usage, where a mixture of generic and specific allocate requests is used within a CICS® region.

A specific allocate is an allocate request that specifies a particular (specific) mode group of sessions to allocate from, whereas a generic allocate does not specify any particular mode group only the system to which an allocate is required. In the latter case CICS determines the session and mode group to allocate.

The fields you need to investigate to answer this question, are:
  • "Total generic allocates satisfied" (field A20ESTAG)
  • "Total specific allocate requests" (field A20ESTAS)
  • "Peak outstanding allocates" (field A20ESTAM)
  • "Total specific allocates satisfied" (field A20ESTAP).
If the "Total generic allocates satisfied" is much greater than "Total specific allocate requests", and "Peak outstanding allocates" is not zero, it could indicate that generic allocates are being made only, or mainly, to the first modegroup for a connection.

This could cause a problem for any specific allocate, because CICS initially tries to satisfy a generic allocate from the first modegroup before trying other modegroups in sequence.

Action: Consider changing the order of the installed modegroup entries. Modegroups for a connection are represented by TCT mode entries (TCTMEs), with the modegroup name being taken from the MODENAME specified on the SESSIONS definition. The order of the TCTMEs is determined by the order in which CICS installs the SESSIONS definitions, which is in the order of the SESSIONS name as stored on the CSD (ascending alphanumeric key sequence). See Figure 1 for an illustration of this. To change the order of the TCTMEs, you must change the names of the SESSIONS definitions. You can rename the definition with a different SESSIONS name within the CSD group. By managing the order in which the TCTMEs are created you can ensure that specific allocates reference modegroups further down the TCTME chain, and avoid conflict with the generic ALLOCATEs. Alternatively, make all allocates specific allocates.
Figure 1. How the sequence of TCT mode entries is determined
The example shows the ISCGROUP in a CSD, containing a connection definition and two SESSIONS definitions. The diagram shows what happens when the group is installed in the CICS region. First, the connection definition for the remote system CICS, CONNECTION(CICA), is installed. At this point, the TCTSE is created, and a special TCTME is created, using the modename SNASVCMG, for the set of sessions reserved for the use of the LU services manager. Second, the SESSIONS definition SESSIONA is installed. It is a group of sessions for the CICA system, and the MODENAME is specified as MODEGRPY. At this point, the first user TCTME is created for MODEGRPY. It has a pointer to the next modegroup. Third, the SESSIONS definition SESSIONB is installed. It is another group of sessions for the CICA system, and the MODENAME is specified as MODEGRPX. At this point, a second user TCTME is created for MODEGRPX. MODEGRPY was therefore installed before MODEGRPX, because SESSIONA appeared in the ISCGROUP before SESSIONB.


dfht3c0028.html | Timestamp icon Last updated: Monday, 5 June 2017