Defining an APPC terminal – method 2
You can define a single-session APPC terminal as a TERMINAL with an associated TYPETERM.
About this task
- You can use a single TYPETERM for all your APPC terminals of the same type.
- It makes the AUTOINSTALL facility available for APPC single-session
terminals.
Autoinstall for APPC single sessions initiated by a z/OS® Communications Server VTAM® CINIT works in the same way as autoinstall for other terminals, in that you must supply a TERMINAL—TYPETERM model pair. For further information about using autoinstall with APPC single-session terminals, see Autoinstalling APPC connections.
Because all APPC devices are seen as systems by CICS®, the value that you define in the TERMINAL attribute is effectively a system name. When you inquire about an APPC terminal, you actually inquire about a CONNECTION.
A single, contention-winning session is implied when you create TERMINAL resource. However, for APPC terminals, CICS accepts a negotiated bind in which it is changed to the contention loser.
If you plan to use automatic installation for your APPC terminals, you need the model terminal definition (LU62) that is provided in the CICS-supplied CSD group DFHTERM. You also have to write an autoinstall user program, and provide suitable z/OS Communications Server LOGMODE entries.

