Handling Shutdown Hung Terminals In The Node Error Program; Using The Node Error Program With Xrf Or Persistent Sessions; The Node Error Program In An Xrf Environment - IBM SC34-6814-04 Customization Manual

Handling shutdown hung terminals in the node error program

Error Code:
Symbolic Name:
Message Number:
For error code X'6F', DFHZNAC passes the setting of TCSACTN and the
DFHZC2351 reason code to DFHZNEP, and DFHZNEP can modify the force-close
action for the current terminal.
How DFHZNAC passes the setting of TCSACTN to DFHZNEP
For error code X'6F', DFHZNAC passes the setting of the TCSACTN system
initialization parameter to DFHZNEP by setting TWAOSCN. TWAOSCN off (B'0')
indicates TCSACTN=NONE, and TWAOSCN on (B'1') indicates
TCSACTN=UNBIND.
How DFHZNAC passes the DFHZC2351 reason code to DFHZNEP
For error code X'6F', the DFHZC2351 reason code is passed to DFHZNEP in the
NEP communications area (NEPCA) field TWATRSN. TWATRSN is a 1-byte code
field. Note that, currently, TWATRSN overlays TWAREASN (also a 1-byte field). The
codes, and their meaning, are:
See Terminal Control message DFHZC2351 for further details.
How DFHZNEP can modify the force-close action for the current
terminal
For error code X'6F', DFHZNEP can modify the force-close action, for the current
terminal, by setting TWAOSCN. If DFHZNEP sets TWAOSCN off (B'0'), DFHZNAC
will not attempt to force-close the terminal (TCSACTN=NONE), however, if
DFHZNEP sets TWAOSCN on (B'1'), DFHZNAC will attempt to force-close the
terminal (TCSACTN=UNBIND). Internally, DFHZNAC achieves this by converting
the TWAOSCN normal close to a TWAOCN forced close. DFHZNEP cannot modify
either of the system initialization parameters TCSWAIT or TCSACTN.

Using the node error program with XRF or persistent sessions

This section contains guidance information about the NEP in an XRF or persistent
sessions environment for CICS Transaction Server for z/OS, Version 3 Release 2.

The node error program in an XRF environment

The CICS extended recovery facility (XRF) is described in the CICS/ESA 3.3 XRF
Guide. If you are using XRF, a VTAM failure in your active CICS system may cause
a takeover by the alternate CICS system. Each terminal from the failing system that
is switched to the alternate system is passed to DFHZNAC for "conversation-restart"
processing. This is similar to "session opened" processing for a normal session
start.
One of the steps in the conversation-restart process is to link to the node error
program with error code X'3F'. If you want to be able to change any of the
510
Customization Guide
X'6F'
TCZSDAS
DFHZC2351
01 Request in progress
02 Task still active
03 Waiting for SHUTC
04 Waiting for BIS
05 Waiting for UNBIND
06 Waiting for RTR
07 BID in progress
08 Other TC work pending
99 (X'63') Undetermined