Usually, the definitions within a group have something in common. For example:
For application resources:
- It is more convenient to keep all the resource definitions belonging to
one application in one group.
- If you use PARTITIONSET or PROFILE definitions for many applications,
keeping them separate in their own groups avoids the possibility of unnecessary
duplication.
For communication resources:
- SESSIONS definitions must be in the same group as
the CONNECTION definition to which they refer. You may have more than one
group of definitions for each system and its sessions with other systems,
in a single CSD file that is shared by all the systems. Be careful that you
install each group of definitions in the correct system.
- Restrict a group to contain only one CONNECTION definition with its associated
SESSIONS definitions.
- Keep all your TYPETERM definitions in one group. This avoids the possibility
of unnecessary duplication. You must put the group of
TYPETERMs before the groups of TERMINAL definitions in your lists.
- It is convenient to group TERMINAL definitions according to departmental
function or geographical location.
- You must keep all the TERMINAL definitions for one
pool of pipeline terminals in the same group.
- Keep AUTINSTMODEL TERMINAL definitions separately in a group of their
own.
For CORBA resources:
- A CORBASERVER definition must be in the same
group as the DJAR definitions that refer to it, or in a group that is installed
before the group containing those DJAR definitions, otherwise CICS® may attempt
to install the DJAR before the CORBASERVER it requires.
For transient data resources, sample definitions for the CICS-supplied
transient data queues (those beginning with the letter “C”) are provided
in group DFHDCTG. For these definitions to become available for use at the
earliest possible point during CICS initialization, include group DFHDCTG
as the first group installed during an initial or cold start.