Defining terminal resources to CICS
A given z/OS® Communications Server terminal, or logical unit, can be defined explicitly in the CICS® system definition file (CSD). If a terminal does not have an explicit definition in the CSD, CICS can create and install a definition dynamically for the terminal when the terminal logs on, using the CICS autoinstall facility.
About this task
- Defining terminal resources explicitly in the CICS CSD
- If a z/OS Communications Server terminal, or logical unit is defined explicitly in the CSD, the terminal has a TERMINAL name and a NETNAME, which is the same as the z/OS Communications Server node name. Terminals defined in this way have terminal entries installed at CICS startup.
- Using the CICS autoinstall facility to dynamically create and install definitions for terminals
- CICS can autoinstall terminals by reference to TYPETERM
and model TERMINAL definitions created with the AUTINSTMODEL and
AUTINSTNAME attributes. For information about TYPETERM and TERMINAL
definitions, see Autoinstalling model terminal definitions and Model TERMINAL definitions in group DFHTERM.
If you use autoinstall, you must ensure that the CICS resource definitions correctly match the z/OS Communications Server resource definitions. For programming information about z/OS Communications Server logmode definitions and their matching CICS autoinstall model definitions, see Coding entries in the VTAM LOGON mode table.
If you specify the system initialization parameter TCTUALOC=ANY, CICS stores the terminal control table user area (TCTUA) for z/OS Communications Server terminals above the 16 MB line if possible.