Sense code 0864

Function terminated abnormally: The conversation was terminated abnormally. Other terminations might occur after repeated reexecutions; the request sender is responsible for detecting such a loop.

VTAM® hint: Sense codes in the X'0864nnnn' range should not be used with APPCCMD CONTROL=SEND,QUALIFY=ERROR,TYPE=USER unless followed by an APPCCMD CONTROL=DEALLOCATE macro. These codes indicate to the receiver that deallocation is occurring.

Bytes 2 and 3 following the sense code contain sense-code-specific information.

0000

For LU 6.2, premature conversation termination: The conversation is terminated abnormally; for example, the transaction program might have issued a DEALLOCATE_ABEND verb, or the program might have terminated (normally or abnormally) without explicitly terminating the conversation. This sense data is sent only in FMH-7 or UNBIND.

For LU 6.2 half-duplex conversations, this sense data is sent only in FMH-7 or indicated in UNBIND.

For LU 6.2 full-duplex conversations, this sense data is also sent in the negative response that precedes an FMH-7, when there is a chain to respond to. The sense data in the negative response gives advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming. For this error, the ERP message will contain the same sense data value used in the negative response.

For non-LU 6.2, no additional information is specified.

0001

System logic error—no retry: A system logic error has been detected. No retry of the conversation should be attempted. This sense data is sent only in FMH-7 or UNBIND.

For LU 6.2 half-duplex conversations, this sense data is sent only in FMH-7 or indicated in UNBIND.

0002

Excessive elapsed time—no retry: Excessive time has elapsed while waiting for a required action or event. For example, a transaction program has failed to issue a conversation-related protocol boundary verb. No retry of the conversation should be attempted. This sense data is sent in UNBIND when there is no chain to respond to; otherwise, it is sent in FMH-7.

For LU 6.2 half-duplex conversations, this sense data is sent in UNBIND when there is no chain to respond to; otherwise, it is sent in FMH-7.

For LU 6.2 full-duplex conversations, this sense data is also sent in the negative response that precedes an FMH-7. The sense data in the negative response gives advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming. For this error, the ERP message will contain the same sense data value used in the negative response.

0003

Allocation error message forthcoming: An error has been detected in a received attach request, resulting in a rejection of the attach. The sense data value that indicates the reason for rejection will be specified in a forthcoming FMH-7.

This sense data is sent in the negative response that precedes an allocation error FMH-7 for an LU 6.2 full-duplex conversation. The negative response gives advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming.

Note: The phrases following the sense data are symbolic return codes provided to a full-duplex transaction program when a negative response with sense data is received by the LU. (See SNA Transaction Programmer's Reference Manual for LU 6.2 for full-duplex verbs and possible return codes.)

Sense Data: Return Code
08640000: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_PROG)
08640001: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_SVC)
08640002: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_TIMER)
08640003: ERROR_INDICATION (with a subcode of ALLOCATION_ERROR)