The resource definitions in all the groups in the specified lists
are loaded during initialization when CICS performs a cold start.
If a warm or emergency start is performed, the resource definitions
are derived from the global catalog, and the GRPLIST parameter
is ignored. Each name can be either a real group list name or
a generic group list name that incorporates global filename characters
(+ and *). If you specify more than one group list (either by specifically
coding two or more group list names or by coding a group list name
with global filename characters), the later group lists are concatenated
onto the first group list. Any duplicate resource definitions in later
group lists override those in earlier group lists.
Use the CEDA
command LOCK to protect the lists of resource groups specified on
the GRPLIST parameter.
The default is DFHLIST, the CICS-supplied
list that specifies the set of resource definitions needed by CICS.
If you create your own group list, either add to it the groups specified
in DFHLIST (omitting only those for CICS functions that you know you
do not need) or specify the DFHLIST name on the
GRPLIST parameter.
Do not code GRPLIST=NO unless you have a group list named NO.
Note: - Group lists specified by a generic group list name are concatenated
in alphabetic, then numeric, order. For example, the generic list
name CICSHT* would concatenate the group lists CICSHT#1, CICSHTAP,
CICSHTSD, and CICSHT3V in that order. If the order of concatenation
is important (for example, to ensure that a particular resource definition
overrides another), consider coding real group list names.
- If a group list contains resource definitions that are needed
by another group list, the group list containing those definitions
must be installed first. For example, if list A has TYPETERM definitions
needed for TERMINAL definitions in list B, list A must be installed
first. Therefore, you might need to specifically name the prerequisite
group on the GRPLIST parameter.
- Take care when using generic group list names, because if a group
list on your CSD satisfies the generic name, it will be installed.
This means that a group list can be installed more than once; for
example, if you specify the real group list name and a generic group
list name that it satisfies, or if you specify two generic group list
names that the group list name satisfies.
- To override one or more of the group lists specified on the GRPLIST system
initialization parameter, you must specify all list names (both real
and generic) that you want to use, even if you are not changing the
names.
For example, to use the four group lists CICSHT#1,
CICSHTAP, CICSHTSD, and CICSHT3V, you could specify either of the
following system initialization parameters:
GRPLIST=(CICSHT*)
GRPLIST=(CICSHT#1,CICSHTAP,CICSHT3V,CICSHTSD)
In
the first example, the group lists are loaded in the order CICSHT#1,
CICSHTAP, CICSHTSD, then CICSHT3V. Resource definitions installed
from the CICSHT3V group list override any duplicate definitions installed
by the other groups.
In the second example, the group lists
are loaded in the order specified. Resource definitions installed
from the CICSHTSD group list override any duplicate definitions installed
by the other groups.
If you specify
GRPLIST=(CICSHT#1,CICSAP*,CICSHT3V,CICSHTSD) and
you want to replace the list CICSHT3V with the list ANOLST05, specify
the override:
GRPLIST=(CICSHT#1,CICSAP*,ANOLST05,CICSHTSD)
In
general, any required resource definitions should appear in one of
the group lists specified on the GRPLIST system
initialization parameter.
For information about resource definitions,
groups, lists, and the CSD, see An overview of resource definition.