OUTSTANDING CROSS SYSTEM MESSAGES:
SENT SYSPLEX MESSAGES:
USER ASID TCB FCODE MEMBER REQID MSG TYPE AGE
MEGA 0025 008DD218 0008 SY2 01000038 LookupCall 00.03.08
TC0 0026 008E6E88 1011 SY1 0100003A Quiesce 00.00.05
OMVS 000E 008E9828 0804 SY2 01000039 VfsInactCall 00.01.18
RECEIVED SYSPLEX MESSAGES:
FROM FROM FROM
ON TCB ASID TCB FCODE MEMBER REQID MSG TYPE AGE
008D97C8 0026 008E6E88 1011 SY1 0100003A Quiesce 00.00.05
IS DOING: Mount Latch Wait
If pipes are used, the output from sysplex messages might not have a corresponding sent sysplex messages. The system that received the request replied to the user so that resources are released and continued processing. On the sender side, once the reply has been received, the task goes into an OSI wait where it will wait to be posted. Because this is a pipes task, the waiter is not shown in the other waiters table, which makes it difficult to correlate between the systems that received the message and the system where it originated. In these cases, the ReqID will be blank. In that situation, using the SPECIAL filtering option (D OMVS,W,S) might result in the corresponding waiter.