Defining CICS resource table and module keywords

About this task

The following table shows the system initialization keywords for those CICS resources that:
  • Have a suffix option, or
  • Result in a dummy program or table if you code resource=NO, or
  • Can perform individual cold starts
Table 1. Summary of resources with a suffix, a dummy load module, or a COLD option
DFHSIT keyword 1 Default 2 Suffix 3 Dummy 4 COLD start 5
BMS FULL - - COLD
CLT - xx - -
DIP NO - program -
FCT YES xx - -
ICP - - - COLD
MCT NO xx 6 -
PDIR NO xx - -
PLTPI NO xx - -
PLTSD NO xx - -
RST NO xx - -
SRT YES xx - -
TCT YES xx table -
TS - - - COLD
TST NO xx - -
XLT NO xx - -
Note:
  1. When the DFHSIT keyword is specified with more than one value, these values must be enclosed within parentheses: for example, BMS=(FULL,COLD).
  2. The Default column indicates the default value for the keyword in the DFHSIT macro.
    For keywords with the suffix option, if you code YES in the SIT, an unsuffixed version of the table or program is loaded. For example, TCT=YES results in a table called DFHTCT being loaded. You can also select an unsuffixed module or table at CICS startup by specifying keyword=, or keyword=YES. For example, if you code: 
    FCT=, or FCT=YES
    blanks are appended to DFHFCT, and these unsuffixed names are used during initialization.

    The result of specifying keyword=, as a system initialization parameter through PARM, SYSIN, or CONSOLE is not necessarily the same as in the DFHSIT macro. For example, TST=, (or omitted altogether) when coding the DFHSIT macro is taken to mean TST=NO, but TST=, through any of the other three methods is the same as TST=YES.

  3. The Suffix column indicates whether you can code a suffix. (xx indicates that a suffix can be coded.)

    A suffix can be any 1 or 2 characters, but you must not use DY, and you cannot use NO as a suffix.

    If you code a suffix, a table or program with that suffix appended to the standard name is loaded.

  4. The Dummy column indicates whether a dummy version of the program or table is loaded if you code NO. In some cases, coding NO for the operand associated with the table results in a dummy program. For more information about the effect of this option, see Selecting versions of CICS programs and tables.
  5. The COLD start column indicates whether the resource can be forced to start COLD. (COLD indicates that a cold start can be performed for the resource individually.) TST and cold start ensure that a cold start is performed for temporary storage or the whole system if you make any change to the TST.

    If COLD is coded, it can be overridden only by coding START=(...,ALL) as a system initialization parameter. For more information about this option, see topic ALL.

    For more information about CICS table and program selection, see Selecting versions of CICS programs and tables.

  6. If you code MCT=NO, the CICS monitoring domain builds dynamically a default monitoring control table. This ensures that default monitoring control table entries are always available for use when monitoring is on and a monitoring class is active.