Automatic sign-off, logoff, and TCTTE deletion

If a session ends through expiry of the user's TIMEOUT period, the terminal entry is deleted as described in the preceding section only if SIGNOFF(LOGOFF) is specified in the TYPETERM definition of the model.

Table 1 summarizes the automatic deletion and recovery of TCTTEs for autoinstalled terminals.

Figure 1 shows how automatic sign-off, logoff, and TCTTE deletion occur if a session is timed out. Figure 2 shows how logon and TCTTE deletion occur if, at a warm start or emergency restart, a TCTTE exists for an autoinstalled terminal. Table 2 shows how automatic TCTTE deletion occurs if a session ends for any reason other than timeout.
Table 1. AUTOINSTALL—summary of TCTTE recovery and deletion
CICS RUNNING:
Restart delay = 0 TCTTE entries are not cataloged and therefore cannot be recovered in a subsequent run.
Restart delay > 0 TCTTE entries are cataloged. If they are not deleted during this run or at shutdown, they can be recovered in a subsequent emergency restart.
SHUTDOWN:
Warm Terminals are logged off and their TCTTEs are deleted, except for those terminals which were logged off before shutdown but whose AILDELAY has not expired.
Immediate No TCTTEs are deleted. All can be recovered in a subsequent emergency restart.
Abnormal termination No TCTTEs are deleted. All can be recovered in a subsequent emergency restart.
STARTUP:
Cold No TCTTEs are recovered.
Warm No TCTTEs are recovered.
Emergency restart when restart delay = 0 No TCTTEs are recovered (but see note in Figure 2). This session is unbound if it persists.
Emergency restart when restart delay > 0 TCTTEs are recovered. For details see Figure 2. This session is recovered if it persists.
Figure 1. Automatic sign-off, logoff and deletion of autoinstalled terminals.
When a session is timed out because there is no terminal activity, CICS uses these steps to determine whether to delete an autoinstalled terminal definition:
  1. If no timeout is specified in the RACF segment, the user is not automatically signed off or logged off.
  2. If SIGNOFF(NO) is specified in the TYPETERM definition, the user is not automatically signed off or logged off.
  3. If SIGNOFF(YES) is specified in the TYPETERM definition, and a timeout is specified in the RACF segment, the user is signed off when the timeout period has expired.

    Before the timeout period has expired, the user can resume terminal activity.

  4. If SIGNOFF(LOGOFF) is specified in the TYPETERM definition, and a timeout is specified in the RACF segment, the user is signed off and the terminal is logged off. The terminal definition is deleted after a further interval, which is specified in the AILDELAY attribute of the TYPETERM definition.

    Before the timeout period has expired, the user can resume terminal activity. After the timeout has expired, but before the terminal definition is deleted, the user can log on again without the overhead of the autoinstall process.

This figure is a flowchart, showing how autoinstalled terminals are deleted after sign-off.
Table 2. AUTOINSTALL
AUTOINSTALL—automatic TCTTE deletion after non-automatic logoff

Non-automatic LOGOFF:

z/OS® Communications Server informs CICS of a session outage, terminal logs off, or transaction disconnects terminal

<---------Delete delay period--------->

The terminal can log on during this period without repeating the autoinstall process.

TCTTE entry deleted.
Figure 2. AUTOINSTALL—automatic logoff and TCTTE deletion after an emergency restart.
During a warm or emergency start, CICS uses these steps to determine whether an autoinstalled terminal definition that has been recovered should be deleted:
  1. Before the restart delay period, specified in the AIRDELAY attribute of the TYPETERM definition, expires, the terminal definition is available for use.
  2. After the restart delay period expires, the terminal definition is deleted. If a user attempts to log on at the terminal, the definition is autoinstalled.
Note:
  1. Successive CICS runs are assumed to use the same restart delay period. If a run with restart delay > 0 is followed by an emergency restart with restart delay = 0, undeleted TCTTEs are recoverd. If the recovered TCTTE specifies AUTOCONNECT(YES), the associated terminal is logged on; otherwise the TCTTE is deleted after startup
  2. Emergency restart: If the restart delay peiod = 0, there is no TCTTE recovery during emergeny restart.
This figure is a flowchart, showing how CICS decides whether to delete an outoinstalled terminal following an emergency restart.


dfha45r.html | Timestamp icon Last updated: Thursday, 27 June 2019