Defining terminal resources

You can define terminal resources in two different ways, depending on the type of terminal access method that you want to use.

  1. ACF/SNA LUs 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 Autoinstall.

    You can add z/OS® Communications Server 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 more information, see GRPLIST system initialization parameter.

    Each LU must also be defined to ACF/SNA in a z/OS Communications Server definition statement.

  2. Non-SNA LUs 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 LUs defined in the TCT are installed as CICS resources. You must also make these LUs known to the operating system, and include a DD statement in the CICS startup job stream for each LU.