Sense codes for FMH-7

The application program can set the sense data sent by VTAM® in an FMH-7 through the SENSE field on the APPCCMD CONTROL=SEND, QUALIFY=ERROR, TYPE=USER, or APPCCMD CONTROL=DEALLOC|DEALLOCQ, QUALIFY=ABNDUSER macroinstruction. For the other types of error reporting, VTAM sets the sense data. For more information on FMH-7s, refer to SNA Transaction Programmer's Reference Manual for LU Type 6.2.

For a complete listing of all sense codes, including sense codes for FMH-7, refer to z/OS Communications Server: IP and SNA Codes. VTAM can set the following sense data for FMH-7:

Code: Meaning
X'080Fnnnn': End user not authorized. The end user making the request does not have access to the requested resource.
Bytes 2 and 3 can contain sense-code-specific information.
X'080F6051': Access security violation. VTAM or the application program detects a security protocol violation.
X'084Bnnnn': Requested resources not available. Resources named in the request, and required to honor it, are not currently available. It is not known when the resources are to be available.
Bytes 2 and 3 contain the following sense-code-specific information.
X'084B6031': Transaction program not available—retry allowed. The FMH-5 ATTACH command specifies a transaction program that the receiver is unable to start. Either the program is not authorized to run or the resources to run it are not available at this time. The condition is temporary. The sender determines when and if to try the operation again.
X'084Cnnnn': Permanent insufficient resource. The receiver cannot act on the request because resources required to honor the request are permanently unavailable. The sender should not try again immediately because the situation is not transient.
Bytes 2 and 3 can contain sense-code-specific information.
X'084C0000': Transaction program not available—no retry. The FMH-5 ATTACH command specifies a transaction program that the receiver is unable to start. The sender should not try again immediately.
X'0864nnnn': Function terminated abnormally. The conversation was terminated abnormally. Other terminations can occur after repeated reexecution; the request sender must detect such a loop.
Bytes 2 and 3 can contain sense-code-specific information.

Note: 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=DEALLOC, QUALIFY=FLUSH macroinstruction. These codes indicate to the receiver that deallocation is occurring.
X'08640000': Premature conversation termination. The conversation terminates abnormally; for example, the transaction program might issue a DEALLOCATE_ABEND verb, or the application program might terminate (normally or abnormally) without explicitly terminating the conversation.
X'08640001': System logic error, no retry. A system logic error is detected. No retry of the conversation should be attempted.
X'08640002': Excessive elapsed time, no retry. Excessive time elapses while the conversation waits for a required action or event. For example, a transaction program fails to issue a conversation-related protocol boundary verb. No retry of the conversation should be attempted.
X'08640003': Allocation error. This code is used in a negative response to an allocation request on a full-duplex conversation. The sense code indicating the specific allocation error will be carried on the subsequent FMH-7.
X'0889nnnn': Transaction program error. The transaction program has detected an error.
Bytes 2 and 3 can contain sense-code-specific information.
X'08890000': Program error, no data truncation. The transaction program that is sending data detects an error but does not truncate a logical record.
Program error, purging. The transaction program that is receiving data detects an error. All remaining information, if any, that the receiving program has not received and that the sending program sent before being notified of the error is discarded. This is applicable only to half-duplex conversations.

Note: This code is not valid for an APPCCMD CONTROL=DEALLOC|DEALLOCQ, QUALIFY=ABNDUSER issued for a full-duplex conversation.
X'08890001': Program error, data truncation. The transaction program that is sending data detects an error and truncates the logical record that it is sending.
Note: This code is not valid for an APPCCMD CONTROL=DEALLOC|DEALLOCQ, QUALIFY=ABNDUSER issued for a full-duplex conversation.
X'08890100': Service transaction program error, no data truncation. The service transaction program that is sending data detects an error and does not truncate a logical record.
Service transaction program error, purging. The service transaction program that is receiving data detects an error. All remaining information, if any, that the receiving service transaction program has not yet received and that the sending service transaction program has sent before being notified of the error is discarded. This is applicable only to half-duplex conversations.

Note: This code is not valid for an APPCCMD CONTROL=DEALLOC|DEALLOCQ, QUALIFY=ABNDUSER issued for a full-duplex conversation.
X'08890101': Service transaction program error, data truncation. The service transaction program that is sending data detects an error and truncates the logical record that it is sending.
Note: This code is not valid for an APPCCMD CONTROL=DEALLOC|DEALLOCQ, QUALIFY=ABNDUSER issued for a full-duplex conversation.
X'1008nnnn': Not valid FM header. The receiver cannot understand or translate the FM header, or the receiver expects an FM header and one is not present.
Bytes 2 and 3 can contain sense-code-specific information.
X'1008600B': Unrecognized FM header command code. The partner LU receives an FM header command code that it does not recognize.
X'10086021': Transaction program name not recognized. The FMH-5 ATTACH command specifies a transaction program name that the receiver does not recognize.
X'10086031': PIP not allowed. The FMH-5 ATTACH command specifies that program initialization parameter (PIP) data is present but the receiver does not support PIP data for the specified transaction program.
X'10086032': PIP not specified correctly. The FMH-5 ATTACH command specifies a transaction program name that requires program initialization parameter (PIP) data and either the FMH-5 specifies that PIP data is not present or the number of PIP subfields present does not agree with the number required for the program.
X'10086034': Conversation type mismatch. The FMH-5 ATTACH command specifies a conversation type that the receiver does not support for the specified transaction program.
X'10086041': Synchronization level not supported. The FMH-5 ATTACH command specifies a synchronization level that the receiver does not support for the specified transaction program.
X'10086042': Reconnection not supported. The FMH-5 ATTACH command specifies reconnection support, but the receiver does not support reconnection for the specified transaction program.
X'10086043': Unable to reconnect transaction program, no retry. The FMH-5 RECONNECT command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect.
X'10086044': Unable to reconnect transaction program, retry allowed. The FMH-5 RECONNECT command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect. The condition is temporary.