The user option bytes (TWAOPTL)
TWAOPTL contains the user option bytes TWAOPT1, TWAOPT2, and TWAOPT3, each of which contains action flags. On entry to DFHZNEP, these flags represent the default actions previously set by DFHZNAC. They can be reset by DFHZNEP.
- TWAOPT1
- User option byte 1. TWAOPT1 contains flags which are principally
debugging aids. The first five flags cause DFHZNAC to write the intended
information to the CSNE log if the appropriate bit is set. Setting
the sixth flag (TWAODNTA) on causes CICS® to
take a system dump when there is no task attached to the terminal
at the time of error detection, if the flag TWAOAT in TWAOPT2 is also
set on. Setting the TWAONQN flag causes the network qualified name
to be printed after any message that contains the action flag. Similarly
setting the TWAOTNA flag causes the TNADDR information to be printed. The flags are:
- TWAOAF (X'80')
- Print action flags.
- TWAORPL (X'40')
- Print z/OS® Communications Server RPL.
- TWAOTCTE (X'20')
- Print TCTTE.
- TWAOTIOA (X'10')
- Print TIOA.
- TWAOBIND (X'08')
- Print BIND area.
- TWAODNTA (X'04')
- System dump if no task attached.
- TWAONQN (X'02')
- Print NQNAME.
- TWAOTNA (X'01')
- Print TNADDR (TCP/IP client address, port and, optionally, host
name). Note:
- Note that DFHZC2411 is not related to a specific node—that is, the TCTTE has not yet been created, and the message is printed against a dummy TCTTE. The node error program is not called in this case, therefore the default setting cannot be overridden. This means that the NQNAME and the TNADDR information is always printed for DFHZC2411 messges.
- When DFHZC2410 is issued against the dummy TCTTE, the NQNAME and TNADDR are not printed.
- TWAOPT2
- User option byte 2. TWAOPT2 contains flags which are task-related.
The NEP can abend the task by setting TWAOAT, or cancel it by setting TWAOCT. The difference is that abend task does not take effect until the task requests or completes a terminal control operation: cancel task takes effect as soon as system and data integrity can be maintained. Setting TWAOAT to abend the task is normally sufficient, except where the task performs lengthy processing (such as a database browse) between terminal requests. If both TWAOAT and TWAOCT are set, TWAOCT (cancel task) takes priority.
If the task is to be abnormally terminated, sends and receives are purged. If TWAOGMM is set, the next transid is cleared and any communication area associated with the terminal is released—except in the case of permanent transids (specified on the TERMINAL definition as TRANSACTION(name)), when the communication area is not released. If the TYPETERM of the terminal indicates that the "good morning" message is supported (LOGONMSG(YES)), if TWAONINT is off, and if the terminal is not in a BMS paging session, then the “good morning” message transaction is initiated (the transaction specified by the system initialization parameter GMTRAN).
The flags are:- TWAOAS (X'80')
- Abandon any SEND for this terminal
- TWAOAR (X'40')
- Abandon any RECEIVE for this terminal
- TWAOAT (X'20')
- Abend any task attached to TCTTE
- TWAOCT (X'10')
- Cancel any task attached to TCTTE
- TWAOGMM (X'08')
- "good morning" message to be sent
- TWAOPBP (X'04')
- Purge any BMS pages for this session
- TWAOASM (X'02')
- SIMLOGON required.
Note:- If a definite response SEND has been performed, CICS has to issue a RECEIVE in order to obtain the response. If the response is negative, DFHZNAC is entered and sets flags TWAOAS (abandon the SEND) and TWAOAR (abandon the RECEIVE). TWAOAR must be kept on to ensure that the RECEIVE for the response is abandoned.
- If the request is to be retried, and the break connection action flag is off (that is, if TWAOCN in TWAOPT3 is off), then one or more of TWAOAS, TWAOAR, and TWAONEGR must be off as well as TWAOAT.
- The abend code returned as a result of setting TWAOCT is unpredictable.
- TWAOGMM forces TWAOAT only if set on by the node error program.
- TWAOPBP forces TWAOAT to be set on.
- For non-pipeline terminals, TWAOAT acts as a cancel request (TWAOCT) if the task has not yet been dispatched for the first time.
- TWAOPT3
- User option byte 3. TWAOPT3 contains flags which are node-related.
The flags are:
- TWAOINT (X'80')
- Internally generated logons (INTLOGs) allowed
- TWAONINT (X'40')
- No internally-generated logons allowed. Do not set this flag when processing error codeX'49' (TCZCLSIN)
- TWAONCN (X'10')
- Normal CLSDST (no reset allowed)
- TWAOSCN (X'08')
- Normal CLSDST (reset allowed)
- TWAONEGR (X'04')
- Send negative response
- TWAOOS (X'02')
- Keep node out of service
- TWAOCN (X'01')
- CLSDST node. Do not set this flag when processing error codeX'49' (TCZCLSIN).
TWAONINT forces TWAOCN.
TWAONEGR forces TWAOAR and TWAOAT.
TWAOOS forces TWAOCN.
TWAOCN forces TWAOAR, TWAOAS, and TWAOAT.
TWAOOS indicates that no further processing is to be done for this node. The node is logically out of service.
For an LU6.1 intersystem communication session, TWAOOS or TWAONINT causes the system entry to be put out of service if, as a result of the specified action, there are no allocatable sessions remaining. (A session can also be put out of service because of either an unknown modename being passed to z/OS Communications Server during an attempt to bind an APPC session, or an invalid logmode name for a z/OS Communications Server 3270-type terminal. However, the CICS default action resulting from this condition cannot be overridden in the NEP.)
If TWAOCN is set, the task is abnormally terminated and communication with the node is lost. Note that the NEP cannot reset this flag.
TWAOSCN provides the same function as TWAONCN, but the NEP can reset it if the session is not to be closed.
If DFHZNAC is scheduled because of the receipt of an exception response, the sense information in the TCTTE is available to DFHZNAC and DFHZNEP to determine any necessary actions.
If DFHZNAC is scheduled because of loss of the connection between CICS and a logical unit, DFHZNAC abnormally terminates any transaction in progress at the time of the failure. DFHZNEP and transaction-class error routine analysis and processing are permitted, but you should not attempt to retry the message.
However, if the application program handles the ‘TERMERR' condition, the transaction is not abended. Control is returned to the program. In this circumstance, no further use can be made of the failed session.