Coding entries in the z/OS Communications Server LOGON mode table

You must code your z/OS® Communications Server LOGON mode table correctly for a terminal to be automatically installed.

Overview of the z/OS Communications Server LOGON mode table
CICS® uses the data that you code in your z/OS Communications Server LOGON mode table when processing an automatic installation (autoinstall) request. Automatic installation functions properly only if the logmode entries that you define to z/OS Communications Server have matches among the TYPETERMs and model TERMINAL definitions that you specify to CICS.
TYPETERM device types and pointers to related LOGON mode data
For each type of TYPETERM device, there is a reference number that has to be coded on the z/OS Communications Server MODEENT macros. You can use this information when deciding what terminals to autoinstall.
z/OS Communications Server MODEENT macro operands
The z/OS Communications Server LOGON mode table lists the MODEENT macro entries that are required for related CICS TYPETERM resources.
PSERVIC screen size values for LUTYPEx devices
You can use the autoinstall model device definition options table to help you decide what screen size values you must specify on the PSERVIC operand of the VTAM® MODEENT macro, for LUTYPE0, LUTYPE2, and LUTYPE3 devices.
Matching models and LOGON mode entries
This section contains a set of z/OS Communications Server LOGON mode table definitions, and their matching CICS autoinstall definitions. Each entry consists of a z/OS Communications Server logmode definition, the matching CICS TYPETERM and model TERMINAL definitions, and (for information) the BIND that CICS sends based on the specified model definition.
LOGON mode definitions for CICS-supplied autoinstall models
This section contains z/OS Communications Server LOGON mode table example definitions that match the CICS-supplied TYPETERM and model TERMINAL definitions for autoinstall.

Parent topic: System programming reference

Last updated: Friday, 18 December 2020 08:52