Design overview
- As a central point of control for most z/OS® Communications Server-related error situations, error actions can be standardized in table form, allowing for easy addition and alteration to the way conditions are processed.
- Some exception conditions that are not errors are also processed by DFHZNAC, but some exception conditions that are errors are not processed by DFHZNAC.
- It provides a single point of user interface to those who want to change the default actions for an error requiring at most one user program (NEP) - see Node error program.
To process conditions that are not associated with a known terminal, the dummy TCTTE is used. It is invoked by placing a TCTTE on the system error queue with a 1-byte code relating to the condition. Placing it on the queue makes the TCTTE ‘temporary OUTSERV' (TCTTESOS); that is, the decision is pending the outcome of DFHZNAC.
The activate scan routine (DFHZACT) is responsible for attaching the CSNE transaction to run DFHZNAC; this is done during CICS® initialization. The CSNE transaction remains in the system until CICS or z/OS Communications Server is quiesced. If DFHZNAC itself abends, or z/OS Communications Server is closed and then restarted, DFHZACT attaches a new CSNE transaction when there is more work for DFHZNAC to do.
There is only ever one CSNE transaction in the system at any one time. (This should not be confused with the CSNE transaction that is attached by the remote delete processing of autoinstall.)
Once DFHZNAC has been called, it runs down the system error queue, processing each error for each TCTTE on the queue. When there is no more work to be done, DFHZNAC suspends itself, to be resumed by DFHZACT when further processing is required.
Note that the system error queue need not be empty before DFHZNAC terminates; errors can remain on the queue to be processed later.
Node abnormal condition program (NACP) processing involves mapping the error code (placed into the TCTTE by a DFHZERRM macro call) to a set of actions, performing any specific processing for that error code, accumulating the actions for all the error codes in that TCTTE, and then performing the actions.
DFHZNCM MSGNO=3424,
E1=S88,
E2=NULL,
E3=NULL,
E4=NULL,
ACT=(ABSEND,ABRECV,ABTASK,CLSDST,SIMLOG),
CODE=NSP02,
TYPE=ENTRY

- The error codes in TCTEVRC* and default actions are defined in
the z/OS Communications Server-associated
errors section of the documentation.
In the example, TCTVRC5 contains X'5C', which equates to TCZNSP02 (ref CODE=NSP02).
- Errors that involve SNA sense have it saved in TCTEVNSS. It is processed by code in copy book DFHZNCS.
- Call any pre-NEP exits specified by the table entry; for example, E1=S88 references routine NAPES88.
- Call the node error program (NEP), passing a parameter list via a COMMAREA. This call may or may not change the default actions. The operation of the NEP is described in Writing a node error program and Node error program.
- Output error-code message associated with the table entry (DFHZC3424 from MSGNO=3424) to the CSNE log.
- Check for ‘unavailable printer error'—this caters for a screen copy request that is unable to find an eligible printer if the first choice is unavailable.
- Because there can be multiple error codes, the actions are accumulated now and performed together later.
- Output any sense message resulting from the DFHZNCS call, to the CSNE log.
- Output any z/OS Communications Server_3270 message resulting from the DFHZNCS call (if it was non-SNA) to the CSNE log.
- Call the post-NEP exit, if any (E4=NULL, no routine).
- Loop for each error code in TCTEVRC*.
- When all the error codes for this TCTTE that can be processed at this time have been processed, retrieve the actions that have been accumulated, such as ACT=(ABSEND, ABRECV, ABTASK, CLSDST, SIMLOG).
- Call the action routine to process each of the actions.
- Output the ‘actions taken' message DFHZC3437 to the CSNE log.
- Check again for any error codes added asynchronously while the CSNE transaction was running.
- Queue any work resulting from the actions to the activate scan routine.