BPXN004I LOST MESSAGE DETECTED FROM sysname - SEQNO seqno EXPECTED seqno
Explanation
z/OS® UNIX System Services XCF processing received a message with an invalid sequence number, implying that a cross-system message has been dropped.
- sysname
- The sysplex member name of the system sending the message.
- seqno
- The 4-byte hexadecimal expected sequence number identifying the message that was lost. The number is of the form xxyyyyyy where xx is the system ID of the sender, and yyyyyy is the expected sequence number suffix. This number can be used to correlate with the sequence number reported via D OMVS,W (message BPXO063I) on the sending system, if it exists.
System action
An EC6 abend causing a two-system dump will be started.
Operator response
Issue D OMVS,W on the sending system (sysname) and contact the system programmer.
System programmer response
Depending on the type of lost message, there can be application errors as well as one or more z/OS UNIX latches not being released. D OMVS,W output on the sending system (sysname) would show this. Look for a match of seqno in this message with seqno in BPXO063I on the sending system (sysname). If a match exists, the application has been identified and it might be possible to recover without a shutdown by canceling the application or by issuing F BPXOINIT,RECOVER=LATCHES. If a match does not exist, and z/OS UNIX on the sending system appears hung, a F OMVS,SHUTDOWN (or IPL) of sysname might be required. Regardless, contact IBM® Service with the dumps provided.
Module
BPXNXMSG
Source
z/OS UNIX System Services kernel (BPX)
Routing Code
10
Descriptor Code
12