Defining resources in CICS control tables
Some CICS® resource are defined in CICS control tables.
The tables and their resource definitions are created by macros. You must use macros to define non-z/OS Communications Server networks and terminals, non-VSAM files, databases, and resources for monitoring and system recovery. You must use RDO for VSAM files, programs, map sets, partition sets, queues, transactions, and profiles.
- Code the resource definitions you require.
- Assemble and link-edit these definitions, using the CICS-supplied procedure DFHAUPLE, to create a load module in the required CICS load library. The load library is either CICSTS54.SDFHLOAD or CICSTS54.SDFHAUTH, which you must specify by the NAME parameter of the DFHAUPLE procedure. The CICS-supplied macros used to create the CICS tables determine whether tables are loaded above the 16MB line. All tables, other than the TCT, are loaded above the 16MB line.
- Name the suffix of the load module by a system initialization
parameter. For most of the CICS tables,
if you do not require the table you can code tablename=NO.
The exceptions to this rule are as follows:
- CLT: specifying CLT=NO causes CICS to try and load DFHCLTNO. The CLT is used only in the alternate CICS, when you are running CICS with XRF, and is always required in that case.
- SIT: specifying SIT=NO causes CICS to try and load DFHSITNO. The SIT is always needed, and you can specify the suffix by coding the SIT system initialization parameter.
- TCT: specifying TCT=NO causes CICS to load a dummy TCT, DFHTCTDY.
- TLT: terminal list tables are specified by program entries in the CSD, and do not have a system initialization parameter.
- MCT: specifying MCT=NO causes the CICS monitoring domain to dynamically build 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 (or classes) are active.
- If you are running CICS with XRF, the active and the alternate CICS regions share the same versions of tables. However, to provide protection against DASD failure, you could run your active and alternate CICS regions from separate sets of load libraries—in which case, you should make the separate copies after generating your control tables.
Table 1 lists all the CICS tables that can be assembled, link-edited, and installed in your CICS libraries.
|
You can generate several versions of each CICS control table by specifying SUFFIX=xx in the macro that generates the table. This suffix is then appended to the default 6-character name of the load module.
To get you started, CICS provides the sample tables listed in Table 2 in the CICSTS54.SDFHSAMP library:
|
Although you can modify and reassemble the tables while CICS is running, you must shut down and restart CICS to make the new tables available to CICS. (The command list table (CLT) is exceptional in that a new table can be brought into use without shutting down either the active CICS region or the alternate CICS region.)