SY1 trace flow

Figure 1 and Figure 2 contain the SY1 trace information found in SYSOMVS component trace formatted with CTRACE COMP(SYSOMVS) FULL.

Figure 1 describes the CTRACE entries generated by the BPXNXMSO processing on the client side. The ASID / TCB highlighted describe the client making the request.

The most important information is the Unique Request-ID (as noted with an asterisk (*)). This is used to track a request from the client to through the server, and back again.

Two separate trace entries are provided. One states that a message has been entered into a block of messages, and the other states that the block has been written. The buffer address (as noted with an @) is used to cross reference these two trace entries.

Figure 1. SY1 Trace Flow: Part 1

SYSNAME   MNEMONIC  ENTRY ID    TIME STAMP     DESCRIPTION
-------   --------  --------  ---------------  -------------
SY1       XCF       0D890407  18:14:14.551107  NXFST-->WRITE XCF BUFFER

   #ASID..0025      USERID....WELLIE1   STACK@....2566DF18
   #TCB...009E04A0  EUID......0000000B  SYSCALL...00000036
   +0000  E2C5D5C4  80180101  02000001  000A0002  | SEND............ |
   +0010  B2DBC852  285F5AC7 @7BA70500  403E3000  | ..H..¬!G#x.. ... |
   +0020  01FF0006  00008178  C6000000            | ......a.F...     |

SY1       XCF       0D6F0401  18:14:14.551325  NXMSO-->XCF MESSAGE OUT

   #ASID..0025      USERID....WELLIE1   STACK@....2566DF18
   #TCB...009E04A0  EUID......0000000B  SYSCALL...00000036
   +0000  E2E8D5C3  80A001D3 !0A010014 *01170BD4  | SYNC...L.......M |
   +0010 $0013C000  02000001  000A0002  00004C4B  | ..{...........<. |
   +0020 @7BA70500  000080E0  00000000  00000000  | #x.....\........ |
   +0030  0D6F0000  00030025  009E04A0  0000000B  | .?.............. |
   +0040  00000000  2538E980  01000000            | ......Z.....     |

# - ASID / TCB of requester    @ - Buffer address containing request
$ - Block #, Index into NXRQ   ! - HFS function being requested
* - Unique Request-ID = System number w/ 3byte seq#

Figure 2 describes the response arriving on the client system. First, the XCF SRB (BPXNXMSG) processes the incoming response to cause the client task to be activated. And then, the target task (no longer remapped) wakes up, and, in this example, explicitly frees the resources that were allocated to it as part of the XCF message processing.

Figure 2. SY1 Trace Flow: Part 2

SYSNAME   MNEMONIC  ENTRY ID    TIME STAMP     DESCRIPTION
-------   --------  --------  ---------------  -------------
SY1       XCF       0D690402  18:14:14.554457  NXMSG-->XCF MESSAGE SRB EXIT

    ASID..000E      USERID....OMVS      STACK@....25385F28
    TCB...00000000  EUID......00000000  SYSCALL...00000000
   +0000  D9C5E2D7  B4600101  009D6C68  00000080  | RESP.-....%..... |
   +0010  00030000 !0A010014 *01170BD4 $0013402C  | ...........M.. . |
   +0020  02000001  000A0002  00000118  01FF0006  | ................ |
   +0030  00300098  24C02910  00008000  00000000  | ...q.{.......... |
   +0040  00000000  00000000  00000000            | ............     |

SY1       XCF       0D6F0401  18:14:14.554513  NXMSO-->XCF MESSAGE OUT

   #ASID..0025      USERID....WELLIE1   STACK@....2566DF18
   #TCB...009E04A0  EUID......0000000B  SYSCALL...00000036
   +0000  C6D9C5C5  10000100  00000000  00000000  | FREE............ |
   +0010  00000000  00000000  00000000  00000000  | ................ |
   +0020  00000000  00000000  00000000  00000000  | ................ |
   +0030  0D6F0000  00000000  00000000  00000000  | .?.............. |
   +0040  00000000  2538E980  00000000            | ......Z.....     |

# - ASID / TCB of requester
$ - Block #, Index into NXRQ   ! - HFS function being requested
* - Unique Request-ID