DFHTCT macro types
The DFHTCT macros you code depend on the device you are defining, and on the access method you are using.
You always start with one of these:
DFHTCT TYPE=INITIAL,... (See Control section: DFHTCT TYPE=INITIAL.)
There is a special macro to use when you assemble the TCT to migrate RDO-eligible definitions to the CSD file:
DFHTCT TYPE=GROUP,... (See Migrating TCT definitions: DFHTCT TYPE=GROUP.)
You can define your devices in any order you want. Each device needs one or more macros, and these sometimes have to be in a particular order. You are told when this is the case. The following table shows the macros you need for each type of device or system.
| Device or system | DFHTCT macros |
|---|---|
| Logical device codes. | DFHTCT TYPE=LDC,... |
| Sequential devices. | DFHTCT TYPE=SDSCI,... |
| Remote non-SNA LUs, for transaction routing. | DFHTCT TYPE=REMOTE,... |
DFHTCT TYPE=FINAL
END
- SYSIDNT and TRMIDNT operands
- CICS® accepts both uppercase and lowercase characters for SYSIDNT and TRMIDNT, but the lowercase characters are not checked for duplication. Assembling a TCT containing lowercase SYSIDNT or TRMIDNT results in an MNOTE. If you want duplicate checking, use only uppercase characters for SYSIDNT and TRMIDNT.
- Assembling the TCT
- The assembly and link-edit of a TCT leads to the creation of two
separate load modules. Assembly of a suffixed TCT (source name DFHTCTxx)
produces a single text file. However, when this is link-edited into
a load library, two members are created:
- DFHTCTxx, which contains the non-RDO-eligible definitions in control block format
- DFHRDTxx, which contains the RDO-eligible (SNA LU and system) definitions in RDO command format
This happens, whether or not you intend to use RDO. You need to be aware of the existence of these two tables if you copy or move assembled TCT tables between load libraries.
If you reassemble the TCT after starting CICS, any changes are picked up at a warm or emergency start.