X'1084' MSG DEST = NON RECOV
Explanation
The message destination is nonrecoverable because of one of the following reasons:
- The destination transaction code name was defined as NORECOV
- The message was received from an LU 6.2 in synchronous conversation mode, which implies nonrecoverable
- The message was received from an OTMA client with a send-then-commit (commit mode 1 or CM1) protocol, which is always treated as nonrecoverable
Programmer response
Locate the MSGFLAGS byte in the message prefix of the message. MSGFNRQU should be set indicating
that the message is nonrecoverable. Some possible reasons are:
- If the message destination is local (system is not MSC, or it is MSC and the destination SYSID at MSGMSOID in the MSC segment item is local), then determine whether the destination name at MSGODSTN is a nonrecoverable transaction code.
- If the message destination is remote (system is MSC and the destination SYSID at MSGMSOID in the MSC segment item is remote), then determine whether the destination name at MSGMSONM in the MSC prefix segment item is a nonrecoverable transaction code.
- If the source name in the message prefix at MSGIDSTN starts with an
FDFFFFFF
, then the source of the message is an LU 6.2 (APPC) logical unit in LU 6.2 synchronous conversation mode. This message is not recoverable according to the LU 6.2 protocol. The LUNAME destination is in the APPC message prefix segment and is extracted and reported in the LOAD messages discarded by the destination report. - If all of the following conditions are satisfied, the message is
an OTMA transaction and the commit mode is send-then-commit (CM1):
- The source name in the message prefix at MSGIDSTN starts with an
FDFFFFFF
- The LUP_MSG_IS_OTMA flag is set in the LU 6.2 prefix
- The TMAMHCM1 flag is set in the state data prefix
This message is not recoverable according to the OTMA send-then-commit protocol.
The TMEMBER and TPIPE names are in the APPC message prefix segment in the MRPREFIX area of the 6701-MRQE trace record.
- The source name in the message prefix at MSGIDSTN starts with an
All of these conditions are considered normal, not errors.