CICS recovery processing following a communication failure

Causes of communication failure include:
  • Terminal failure
  • Printer terminal running out of paper
  • Power failure at a terminal
  • Invalid SNA status
  • Network path failure
  • Loss of an MVS™ image that is a member of a sysplex
There are two aspects to processing following a communications failure:
  1. If the failure occurs during a conversation that is not engaged in syncpoint protocol, CICS® must terminate the conversation and allow customized handling of the error, if required. An example of when such customization is helpful is for 3270 device types. This is described later.
  2. If the failure occurs during the execution of a CICS syncpoint, where the conversation is with another resource manager (perhaps in another CICS region), CICS handles the resynchronization. This is described in Troubleshooting intersystem problems.

If the link fails and is later reestablished, CICS and its partners use the SNA set-and-test-sequence-numbers (STSN) command to find out what they were doing (backout or commit) at the time of link failure. For more information on link failure, see Recovery functions and interfaces.

When communication fails, the communication system access method either retries the transmission or notifies CICS. If a retry is successful, CICS is not informed. Information about the error can be recorded by the operating system. If the retries are not successful, CICS is notified.

When CICS detects a communication failure, it gives control to one of two programs:
  • The node error program (NEP) for z/OS® Communications Server SNA logical units
  • The terminal error program (TEP) for non- z/OS Communications Server SNA terminals

Both dummy and sample versions of these programs are provided by CICS. The dummy versions do nothing; they allow the default actions selected by CICS to proceed. The sample versions show how to write your own NEP or TEP to change the default actions.

The types of processing that might be in a user-written NEP or TEP are:
  • Logging additional error information. CICS provides some error information when an error occurs.
  • Retrying the transmission. This is not recommended because the access method will already have made several attempts.
  • Leaving the terminal out of service. This means that it is unavailable to the terminal operator until the problem is fixed and the terminal is put back into service by means of a master terminal transaction.
  • Abending the task if it is still active (see CICS recovery processing following a transaction failure).
  • Reducing the amount of error information printed.
For more information about NEPs and TEPs, see Communication error processing.


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