Design overview

Before a z/OS® Communications Server device can communicate with CICS®, a z/OS Communications Server session must be established between the device and CICS. The sequence of operations is LOGON, Open Destination (OPNDST), and Start Data Traffic (SDT). CICS can also initiate the LOGON by using a SIMLOGON.

The session can be requested by:
  • Specifying AUTOCONNECT when the terminal is defined to CICS
  • A z/OS Communications Server main terminal command requesting a LOGON to CICS for a given terminal; for example, V NET,LOGON=CICSA,ID=L3277C1
  • An individual terminal operator issuing a LOGON request (LOGON APPLID(CICSA))
  • A CICS main terminal command requesting LOGON for a given terminal (CEMT SET TERMINAL(xxxx) INSERVICE ACQUIRED)
  • CICS internally requesting a LOGON; for example, to process an ATI request
  • LOGAPPL=CICS in the LU statement.

Consoles are not z/OS Communications Server resource but they usse a similar mechanism to autoinstall the TCTTE.