Disconnection flow for terminals (LU-initiated)

This section describes the flow of control when a request is made to disconnect an autoinstalled terminal; for example, by entering a CESF LOGOFF command that causes an EXEC CICS ISSUE LOGOFF command to be issued.

  1. First the following functions are performed:
    • Set on the CLSDST flag in the TCTTE.
    • Put the TCTTE on the activate chain for DFHZACT to dispatch.
  2. Control is then passed to the Close destination program, DFHZCLS, which performs the following functions:
    • Set on the SHUTDOWN_IN_PROGRESS flag in the TCTTE.
    • Set on the REQUEST_SHUTDOWN flag in the TCTTE.
  3. The Send asynchronous commands program, DFHZDSA is then called to send a VTAM® SHUTD command to the LU (autoinstalled terminal) to be disconnected. The DFHZDSA program removes the TCTTE from the activate chain, pending completion of the SHUTD command.
  4. When the VTAM SHUTD command has completed, z/OS® Communications Server calls the asynchronous send exit, DFHZSAX, which performs the following functions:
    • Set off the REQUEST_SHUTDOWN flag in the TCTTE.
    • Set on the SHUTDOWN_SEND flag in the TCTTE.
    • Put the TCTTE back on the activate chain for DFHZACT to dispatch.
  5. z/OS Communications Server then drives the asynchronous receive exit, DFHZASX, with the SHUTC (“shutdown complete”) command sent by the LU to be disconnected. DFHZASX performs the following functions:
    • Ensures that the NODE_QUIESCED_BY_CICS, SHUTDOWN_IN_PROGRESS, and CLSDST flags are still on.
    • Puts the TCTTE back on the activate chain for DFHZACT to dispatch.
  6. Control is then passed to the Close_Destination program, DFHZCLS. The DFHZCLS program performs the following functions:
    • Set on the PENDING_DELETE flag in the TCTTE to prevent z/OS Communications Server exits scheduling requests for the device.
    • Issue UNBIND (CLSDST POST=RESP) for the device.
  7. The Close destination exit, DFHZCLX, is driven. If the CLSDST request is successful (that is, there is a positive response from UNBIND), the following functions are performed:
    • Set on the SESSION_CLOSED flag in the TCTTE.
    • Flag the TCTTE for deletion.
    • Enqueue the TCTTE to DFHZNAC.
  8. Control is passed to the DFHZNAC program, which performs the following functions:
    • Set on the DELETE_REQUIRED flag in the TCTTE.
    • Put the TCTTE on the activate chain for DFHZACT to dispatch.
    • Issue message DFHZC3462 (session terminated).
  9. On the delete request, the DFHZNCA copybook of DFHZNAC checks the value of the AILDELAY system initialization parameter.
    • If AILDELAY is zero, the TCTTE is queued via DFHZACT with the address of the TCTTE as input. Its function is to perform clean up operations, the principal operation being to ask DFHZCQ to delete the TCTTE.
    • If AILDELAY is not zero, DFHZNCA initiates CATD using the delay specified and passes the address of the TCTTE.

    Up to three attempts are made to delete the TCTTE. This is because the reason for the failure may be the existence of a transient condition, such as the TCTTE being on the DFHZNAC queue to output a message to CSMT. If the initial delete attempt fails, it is attempted again after one second; if this fails, another attempt is made after a further 5 seconds. If the third attempt fails, it is assumed that the failure is a hard failure, which will not disappear until the device is reconnected; in this case, message DFHZC6943 is issued, a syncpoint is taken, and the TCTTE delete status is reset to make the TCTTE reusable.

    If the deletion is successful, the delete is committed, the autoinstall control program is invoked to permit any specific clean up operations to take place, and message DFHZC6966 is issued.

    If a PWE exists for this TCTTE, the PWE is requeued onto the AWE chain.

Disconnection of an autoinstalled terminal can also be requested by CICS® shutdown, terminal timeout, and terminal errors. In these cases the flow is slightly different.



dfhs3c0028.html | Timestamp icon Last updated: Monday, 5 June 2017