BPXN005I

Explanation
 z/OS® UNIX System Services XCF processing
received a message with a duplicate sequence number, implying that
a cross-system message has been sent twice.  
 In the message
text: sysname
The sysplex member name of the system sending the message.
seqno
The 4-byte hexadecimal expected sequence number identifying the
message that duplicated.  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.  To prevent a possible system integrity exposure, the duplicate
message will be dropped on this system.

Operator response
 Issue D OMVS,W on the sending system (sysname)
and contact the system programmer.   

System programmer response
 This should be a rare event that z/OS UNIX should
recover from.  To verify that there is no problem, issue D OMVS,W
output on the sending system (sysname). Look for
match of seqno in this message with seqno in
BPXO063I on the sending system (sysname).  If a
match exists, the application identified should be verified that it
is not hung.  If a match does not exist, z/OS UNIX has
probably recovered from this temporary problem.  Regardless, contact IBM® Service with the dumps provided

Module
 BPXNXMSG

Source
 z/OS UNIX System Services kernel (BPX)

Routing Code
 10

Descriptor Code
 12