Defining terminal resources

This section describes how to define to CICS® the terminals (and logical units) that it is to use, and how it is to use them. You define terminals to CICS in one of two ways, depending on the type of terminal access method you are using:

  1. IBM® ACF/VTAM terminals are defined in the CSD either explicitly, or by using model terminal definitions if you are using the CICS automatic installation facility (autoinstall). Using autoinstall, you leave it to CICS to install the terminal resource definition dynamically at logon time. CICS obtains the information needed to create a terminal entry from the TERMINAL and TYPETERM definitions recorded in the CSD. For guidance information about this process, see the CICS Resource Definition Guide.

    You can add VTAM® definitions to the CSD offline using the DEFINE command of the CICS utility program, DFHCSDUP, or online using the CEDA DEFINE command. If you want the terminal definitions installed during CICS initialization, you must add the names of the groups containing the definitions to a group list used during a cold start. Otherwise you can install a group of definitions using the CEDA INSTALL GROUP(groupname) command online. For details of the GRPLIST system initialization parameter, see Specifying CICS system initialization parameters.

    Each terminal must also be defined to ACF/VTAM in a VTAM definition statement.

  2. Non-VTAM terminals are defined in a terminal control table (TCT) using DFHTCT macros.

    During CICS initialization, CICS loads the TCT specified by the TCT system initialization parameter, and those terminals defined in the TCT are installed as CICS resources. You must also make these terminals known to the operating system, and include a DD statement in the CICS startup job stream for each terminal.

If you are running CICS with XRF, see XRF considerations.

[[ Contents Previous Page | Next Page Index ]]