Search Rocket site


Assign a set of CICS regions to a named group.

A group is defined using a GROUP statement followed by one or more CICS region definitions before being terminated with a GROUPEND statement. All CICS regions listed between the GROUP and the GROUPEND statement are members of the group.

Tip: To group your regions automatically, use the discovery process with the WITHGROUPING control statement. To learn more about grouping using discovery, see Generate a configuration file.

For example, to define a group named PRODPLX1 that contains three CICS regions, use the following control statements:


Assigning three CICS regions to a group

Use a group in the following situations:

  • To filter and view transaction originating from one or more groups using Transaction Selection Criteria panel (see Applying a filter to the transaction list).

  • To enable identification and sorting of CICS regions by group in the Region List panel (see Reviewing collection status across your topology)

  • To use MVS system commands to control collection for a group instead of for individual CICS regions (see Controlling the collector via operator commands). Placing a CICS region inside a group does not preclude you from submitting requests to individual regions inside the group.

  • To create a unique collector configuration for a set of CICS regions by inserting additional control statements after the initial GROUP control statement. Insert additional control statements in the following circumstances:

    • You want to use a specific data set naming patter for the group using the ARCHDSN control statement (see ARCHDSN=pattern).

    • You want to define specific data set allocation attributes for the group using the SUMMARY, DETAIL, and AUXILIARY control statements (see SUMMARY, DETAIL, and AUXILIARY).

    • The CICS regions in your group use multiregion operation (MRO). To enable this feature in C\Prof, use the MRO control statement (see MRO=YES | NO).

    • You want to use the same trace settings for all CICS regions in the group using ACTIVATETRACE, RESETTRACE, and STNTRxx control statements (see Control statements for internal trace data collection and control).

    • You want to increase or decrease the level of recorded detail when recording for profiling using the LEVEL control statement (see LEVEL=value).

    • You want to filter profiling data collected from the CICS internal trace using the TRAN, EXCLUDETRAN, PROGRAM, RESPONSE, or ABEND control statements (see Control statements for transaction filtering).

Control statements specified inside a group override global settings, and statements specified for individual CICS regions override group settings. CICS regions defined inside a group inherit any settings defined at a global level.


The following example demonstrates how you can specify unique settings for individual CICS regions and groups. In this example:

  • The LEVEL=1 control statement appears in the configuration file before any GROUP or CICS control statements. This setting will apply to all CICS regions, except where it is overridden by additional LEVEL control statements inside a group or assigned to a specific CICS region. In this example, the LEVEL=1 control statement has been overridden on CICS region CICSDEVT with the LEVEL=3 control statement.

  • The LEVEL=2 control statement inside the PRODPLEX group applies to all CICS regions defined in that group, except for CICS region CICSP3, which has been overridden with the LEVEL=3 control statement.

/* Global options
CICS=CICSP0    /* Collecting at level 1

LEVEL=2        /* Group option
CICS=CICSP1    /* Collecting at level 2
CICS=CICSP2    /* Collecting at level 2
CICS=CICSP3    /* Collecting at level 3
     LEVEL=3   /* Region option

CICS=CICSTEST  /* Collecting at level 1

CICS=CICSDEVT  /* Collecting at level 3
     LEVEL=3   /* Region option

A configuration file containing specific collection settings for each group or region