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).
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
