CESF - sign off

Use the CESF transaction to sign off from the CICS system.

This transaction:
  • Writes the signoff message to your terminal
  • Logs the message on the transient data destination CSCS
  • Logs any error message on the transient data destination CSMT.

If you are using CESF to disconnect a terminal and security is active, a message will still be sent to the log if the signoff fails. However, this will not stop the terminal being disconnected if it is a preset terminal or if the terminal is not signed on.

You cannot use CESF on:
  • Fixed-format terminals (such as the 3608, the 3614, and the 3653)
  • Numeric-only terminals.

For these devices, you must code your own transaction using the EXEC CICS SIGNOFF command. For programming information about this command, see About the CICS API commands.

The syntax of the CESF transaction is as follows:

CESF

Read syntax diagramSkip visual syntax diagramCESFGOODNIGHTLOGOFF

If you type CESF by itself, you are signed off the CICS system. Your terminal can still start transactions without you having to request them, and messages can be sent to it. You can sign on again at that terminal at any time.

The effects of typing CESF with the GOODNIGHT value or the LOGOFF value depend on the access method in use, as shown in Table 1:

Table 1. Effect of CESF LOGOFF and GOODNIGHT with different access methods
VTAM DISCREQ=YES Otherwise
CESF TTI TTI
CESF LOGOFF Disc, TTI TTI
CESF GOODNIGHT Disc, TTI NOTTI
Note: VTAM is now z/OS Communications Server.
where:
Disc
The terminal is disconnected.
TTI
Terminal transaction initiation is allowed.
NOTTI
Terminal transaction initiation is not allowed, and your terminal is placed in RECEIVE status so that, the next time a connection is made, it can receive messages.

DISCREQ=YES is an operand of the TYPETERM definition associated with the terminal, and means that CICS is to honor a disconnect request. If DISCREQ=NO, a disconnect request (for example, a CESF LOGOFF request) is not honored.

If a CESF GOODNIGHT is given when there are outstanding automatic transaction initiation (ATI) requests, the ATI requests are actioned and the session is reacquired irrespective of the RDO options.