Appendix L. Acquiring Performance Verification Traces

This appendix describes the timing for acquisition of performance verification trace information and MCF performance verification trace information, as well as the actual information that is acquired for each event ID. For MCF performance verification trace information, this appendix also describes the MCF-specific dump output information.

Organization of this section
(1) Acquiring performance verification trace information
(2) Acquiring MCF performance verification trace information

(1) Acquiring performance verification trace information

OpenTP1 acquires the trace information at the timings of the event IDs listed in the following table. Also listed is the trace data length that is required for one transaction.

Table L-1 Timing to acquire the performance verification Traces

Event IDTimingTrace data length
(unit: bytes)
0x1000Immediately before sending the service request by dc_rpc_call()128
0x1001Before calling the service function by dc_rpc_mainloop()128
0x1002After the service function is returned by dc_rpc_mainloop()64
0x1003Immediately after responding to the client by dc_rpc_mainloop()64
0x1004Immediately before dc_rpc_call() returns.
Acquires the traces regardless of the synchronous, asynchronous or non-response type.
192
0x1005When accepting the asynchronous rpc response message128
0x1006Entry to the dc_rpc_poll_any_replies() function64
0x1007Immediately before dc_rpc_poll_any_replies() returns64
0x1008When discarding the dc_rpc_discard_further_replies() receive message128
0x1009When discarding the dc_rpc_discard_specific_reply() receive message128
0x2000Before notifying (msgsnd) the service function to a process when the service function is in the same node64
0x2001Immediately before sending the service function to the server node when the service function is in another node64
0x2002When receiving the service request that has been sent128
0x2003Before notifying (msgsnd) the service function to a process64
0x2004When transferring the service function to another node
(A service is requested to this node, but the service function is not executable so that it is sent to another node.)
64
0x2005Immediately after getting the service request from the scheduling queue128
0x2007When receiving the service request that has been transferred from another node128
0x4000When sending the prepare message192
0x4001When receiving the prepare message192
0x4002When sending the prepare completion message192
0x4003When receiving the prepare completion message192
0x4004When sending the commit message192
0x4005When receiving the commit message192
0x4006When sending the commit completion message192
0x4007When receiving the commit completion message192
0x4008When sending the rollback message192
0x4009When receiving the rollback message192
0x400aWhen sending the rollback completion message192
0x400bWhen receiving the rollback completion message192
0x400cWhen sending the read-only message192
0x400dWhen receiving the read-only message192
0x400eWhen sending the recovery message192
0x400fWhen receiving the recovery message192
0x4010When sending the recovery response message192
0x4011When receiving the recovery response message192
0x4012When sending the address resolve message192
0x4013When receiving the address resolve message192
0x4014When sending the RM thread message192
0x4015When receiving the RM thread message192
0x4016When sending the heuristic message192
0x4017When receiving the heuristic message192
0x4100When starting the transaction192
0x4150When terminating the transaction192
0x4a00Immediately after issuing a request to start a transaction branch128
0x4a01Immediately before the request to start a transaction branch returns128
0x4a02Immediately after issuing a request for RPC execution from inside a transaction branch128
0x4a03Immediately before the request for RPC execution from inside a transaction branch returns128
0x4a04Immediately after issuing a request to end a transaction branch128
0x4a05Immediately before the request to end a transaction branch returns128
0x4a06Immediately after issuing a request to prepare a transaction branch for commitment128
0x4a07Immediately before a request to prepare a transaction branch for commitment returns128
0x4a08Immediately after issuing a request to commit a transaction branch128
0x4a09Immediately before a commit request for a transaction branch returns128
0x4a0aImmediately after issuing a request to roll back a transaction branch128
0x4a0bImmediately before a rollback request for a transaction branch returns128
0x4a0cImmediately after issuing a request to notify about a transaction branch in Prepared or Heuristically Completed status64
0x4a0dImmediately before the request to notify about a transaction branch in Prepared or Heuristically Completed status returns64
0x4a0eImmediately after issuing a request to discard a transaction branch in Heuristically Completed status128
0x4a0fImmediately before a request to discard a transaction branch in Heuristically Completed status returns128
0x4b00Immediately before the transaction branch starts64
0x4b01Immediately after the transaction branch starts64
0x4b02Immediately before executing an RPC call from inside a transaction branch64
0x4b03Immediately after executing an RPC call from inside a transaction branch64
0x4b04Immediately before ending a transaction branch64
0x4b05Immediately after ending a transaction branch64
0x4b06Immediately before a transaction branch is prepared for commitment64
0x4b07Immediately after a transaction branch is prepared for commitment64
0x4b08Immediately before a transaction branch is committed64
0x4b09Immediately after a transaction branch is committed64
0x4b0aImmediately before a transaction branch is rolled back64
0x4b0bImmediately after a transaction branch is rolled back64
0x4b0cImmediately before notifying a transaction branch in Prepared or Heuristically Completed status64
0x4b0dImmediately after notifying a transaction branch in Prepared or Heuristically Completed status64
0x4b0eImmediately before discarding a transaction branch in Heuristically Completed status64
0x4b0fImmediately after discarding a transaction branch in Heuristically Completed status64
0x5001When receiving the connection establishment request from the client when using the remote API facility64
0x5002Before sending the RAP-processing server allocation request from the RAP-processing listener to the RAP-processing server when using the remote API facility64
0x5003After receiving the inheritance request for the connection from the RAP-processing listener to the RAP-processing server64
0x5004When receiving the API substitution execution request from the client when using the remote API facility64
0x5005Before sending the API substitution execution response when using the remote API facility64
0x5006When receiving the RAP-processing server deallocation or disconnection request from the client when using the remote API facility64
0x5007When receiving the RAP-processing server deallocation response from the RAP-processing server when using the remote API facility64
0x5008When sending the RAP-processing server deallocation response from the RAP-processing listener to the RAP-processing client when using the remote API facility64
0x6400When accepting a resource lock request128
0x6401When a resource lock request returns128
0x6410Immediately before a lock wait128
0x6411Immediately after a lock wait is released128
0x6420When accepting a request to release lock with a resource name specified128
0x6421When a request to release lock with a resource name specified returns128
0x6430When accepting a request to release lock for all resources128
0x6431When a request to release lock for all resources returns128
0x6805When input from an OpenTP1 file is completed192
0x6807When output to an OpenTP1 file is completed192
0x6905When read() system call processing on an OpenTP1 file is completed192
0x6907When write() system call processing on an OpenTP1 file is completed192
0x6909When lseek() system call processing on an OpenTP1 file is completed192
0xb001When a process is generated (child process)64
0xb002When a process expires64
0xb003When a process is generated (parent process)64
0xb010Entry to process generation request64
0xb012
0xb011Exit from process generation request64
0xb013
0xb014Entry to process information registration request64
0xb015Exit from process information registration request64
0xb016Entry to process information registration request (for TP1/Resource Manager Monitor)64
0xb017Exit from process information registration request (for TP1/Resource Manager Monitor)64
0xb018Entry to notification of process startup completion64
0xb019Exit from notification of process startup completion64
0xb01aEntry to waiting for notification of process startup completion64
0xb01bExit from waiting for notification of process startup completion64
0xb01cEntry to notification of process termination64
0xb01dExit from notification of process termination64
0xb01eEntry to notification of process termination (for TP1/Resource Manager Monitor)64
0xb01fExit from notification of process termination (for TP1/Resource Manager Monitor)64
0xb020Entry to waiting for notification of process termination64
0xb021Exit from waiting for notification of process termination64
0xb022Entry to request to forcibly terminate a process64
0xb024
0xb023Exit from request to forcibly terminate a process64
0xb025
0xb026Entry to instruction to terminate a process service64
0xb027Exit from instruction to terminate a process service64
0xb110Entry to process-generating processing of process server64
0xb111Exit from process-generating processing of process server64
0xb114Entry to process information registration processing of process server64
0xb115Exit from process information registration processing of process server64
0xb118Entry to acceptance of process startup completion notification process server64
0xb119Exit from acceptance of process startup completion notification process server64
0xb11aEntry to waiting for process startup completion notification processing of process server64
0xb11bExit from waiting for process startup completion notification processing of process server64
0xb11cEntry to reception of process termination notification process server64
0xb11dExit from reception of process termination notification process server64
0xb120Entry to process termination notification wait processing of process server64
0xb121Exit from process termination notification wait processing of process server64
0xb122Entry to forcible process termination processing of process server64
0xb124
0xb123Exit from forcible process termination processing of process server64
0xb125
0xb126Entry to process service termination processing64
0xb127Exit from process service termination processing64
0xb130Entry to regular fixed-interval processing by process service64
0xb131Exit from regular fixed-interval processing by process service64
0xb132Entry to process termination detection processing by process service64
0xb133Exit from process termination detection processing by process service64
0xc001After creating a journal record header128
0xc002After creating a journal block header128
0xc101Immediately before sending a message to an I/O process128
0xc102Immediately after receiving a response message from an I/O process64
0xc103Immediately before issuing a service request to an I/O process by RPC128
0xc104Immediately after receiving an RPC response from an I/O process64
0xc201Immediately after receiving an I/O request message128
0xc202Immediately before performing output to a journal file64
0xc203Immediately after performing output to a journal file64
0xc204Immediately before sending an I/O termination message to the I/O-requesting process64
0xc205Immediately after receiving an I/O-requesting RPC128
0xc206Immediately before sending an I/O-termination RPC response to the I/O-requesting process128
0xc301When journal buffering processing starts64
0xc302When journal buffering processing ends64
0xc401Immediately before waiting for an available journal buffer64
0xc402Immediately after waiting for an available journal buffer64
0xd000Immediately before the return of the MQPUT call of TP1/Message Queue192
0xd001Immediately before the return of the MQGET call of TP1/Message Queue256
0xd002Immediately before the return of the function of TP1/Message Queue for registering transferred messages192
0xd003Immediately before the return of the function of TP1/Message Queue for collecting transferred messages256
0xf000After the name server receives a request to send service information from a process on the local node128
0xf001Before the name server sends service information to a remote node128
0xf002After the name server sends service information to remote node128
0xf003After the name server receives service information from a remote node128
0xf004After the name server receives a request to delete service information from a process on the local node128
0xf005Before the name server sends a request to delete service information to a remote node128
0xf006After the name server sends a request to delete service information to a remote node128
0xf007After the name server receives a request to delete service information from a remote node128
0xf008After the name server receives a request to delete service information from a process on the local node128
0xf009Before the name server sends a request to delete service information to a remote node128
0xf00aAfter the name server sends a request to delete service information to a remote node128
0xf00bAfter the name server receives a request to modify user server load information from a process on the local node128
0xf00cBefore the name server sends a request to modify user server load information to a remote node128
0xf00dAfter the name server sends a request to modify user server load information to a remote node128
0xf00eAfter the name server receives a request to modify user server load information from a remote node128
0xf010After the name server receives a request to search service information128
0xf011Before the name server sends a request to search service information to a remote node128
0xf012After the name server sends a request to search service information to a remote node128
0xf013After the name server receives a request to search service information from a remote node128
0xf014Before the name server sends the results of searching service information to a remote node128
0xf015After the name server receives the results of searching service information from a remote node128
0xf016Before the name server sends the results of searching service information128
0xf017After the name server receives the results of searching service information from a remote node128
0xf018Before the name server sends a request to search service information to a remote node128
0xf019After the name server sends a request to search service information to a remote node128
0xf01aAfter the name server receives the results of searching service information from a remote node128
0xf020After the name server receives a request to search service information during RPC execution128
0xf021Before the name server sends a request to search service information to a remote node during RPC execution128
0xf022After the name server sends a request to search service information to a remote node during RPC execution128
0xf023After the name server receives a request to search service information from a remote node during RPC execution128
0xf024Before the name server sends a request to search service information to a remote node during RPC execution128
0xf025After the name server receives the results of searching service information from a remote node during RPC execution128
0xf026Before the name server sends the results of searching service information during RPC execution128
0xf027Before the name server sends a request to search service information to a remote node during RPC execution, when Y is specified for the name_global_lookup operand128
0xf028After the name server sends a request to search service information to a remote node during RPC execution, when Y is specified for the name_global_lookup operand128
0xf029Before the name server sends the results of searching service information to a remote node during RPC execution128
0xf100After a node is deleted from the RPC suppression list128
0xf101After a node is added to the RPC suppression list128
0xf102After service information is deleted from the global cache (when a node is detected to have gone down)128
0xf103After service information is added to the global cache128
0xf104After service information is deleted from the global cache (situations not related to detection of nodes going down)128
0xf105After modifying the load information of a user server operating on a remote node128
0xf106After starting service information search processing128
0xf107Before ending service information search processing128
0xf108After starting service information search processing during RPC execution128
0xf109Before ending service information search processing during RPC execution128
0xf200Before sending a request to send service information to the name server on the local node128
0xf201After sending a request to send service information to the name server on the local node128
0xf202Before sending a request to delete service information to the name server on the local node128
0xf203After sending a request to delete service information to the name server on the local node128
0xf204Before sending a request to delete service information to the name server on the local node64
0xf205After sending a request to delete service information to the name server on the local node64
0xf206Before sending a request to modify user server load information to the name server on the local node128
0xf207After sending a request to modify user server load information to the name server on the local node128
0xf210Before sending a request to search service information to the name server on the local node128
0xf211After sending a request to search service information to the name server on the local node128
0xf212After receiving the results of searching service information from the name server on the local node128
0xf213Before sending a request to search service information to the name server on the local node128
0xf214After sending a request to search service information to the name server on the local node128
0xf215After receiving the results of searching service information from the name server on the local node128
0xf216Before sending a request to search service information to the name server on the local node at RPC execution128
0xf217After sending a request to search service information to the name server on the local node at RPC execution128
0xf218After receiving the results of searching service information from the name server on the local node at RPC execution128

The following table lists the contents acquired for each event ID.

Table L-2 Information acquired for each event ID (performance verification traces)

Event IDClt IDClt com numSvr IDRt IDRt com numSvc grpSvcRet cdGbl IDQuMsg tknMsg ID
0x1000YYYYYYYNNNNN
0x1001YYNYYYYNNNNN
0x1002YYNYYNNYNNNN
0x1003YYNYYNNYNNNN
0x1004YYYYYYYYNNNN
0x1005YYYYYYYNNNNN
0x1006YNNYYNNNNNNN
0x1007YYNYYNNYNNNN
0x1008YYYYYYYNNNNN
0x1009YYYYYYYYNNNN
0x2000YYNYYNNNNNNN
0x2001YYYYYNNNNNNN
0x2002YYNYYYYNNNNN
0x2003YYNYYNNNNNNN
0x2004YYYYYNNNNNNN
0x2005YYNYYNNNNNNN
0x2007YYNYYYYNNNNN
0x4000YYYYNNNYYNNN
0x4001YYNYNNNYYNNN
0x4002YYYYNNNYYNNN
0x4003YYNYNNNYYNNN
0x4004YYYYNNNYYNNN
0x4005YYNYNNNYYNNN
0x4006YYYYNNNYYNNN
0x4007YYNYNNNYYNNN
0x4008YYYYNNNYYNNN
0x4009YYNYNNNYYNNN
0x400aYYYYNNNYYNNN
0x400bYYNYNNNYYNNN
0x400cYYYYNNNYYNNN
0x400dYYNYNNNYYNNN
0x400eYYYYNNNYYNNN
0x400fYYNYNNNYYNNN
0x4010YYYYNNNYYNNN
0x4011YYNYNNNYYNNN
0x4012YYYYNNNYYNNN
0x4013YYNYNNNYYNNN
0x4014YYYYNNNYYNNN
0x4015YYNYNNNYYNNN
0x4016YYYYNNNYYNNN
0x4017YYNYNNNYYNNN
0x4100YNNYNNNNYNNN
0x4150YNNYNNNYYNNN
0x4a00NNNNNNNNNNNN
0x4a01NNNNNNNYNNNN
0x4a02NNNNNNNNNNNN
0x4a03NNNNNNNYNNNN
0x4a04NNNNNNNNNNNN
0x4a05NNNNNNNYNNNN
0x4a06NNNNNNNNNNNN
0x4a07NNNNNNNYNNNN
0x4a08NNNNNNNNNNNN
0x4a09NNNNNNNYNNNN
0x4a0aNNNNNNNNNNNN
0x4a0bNNNNNNNYNNNN
0x4a0cNNNNNNNNNNNN
0x4a0dNNNNNNNYNNNN
0x4a0eNNNNNNNNNNNN
0x4a0fNNNNNNNYNNNN
0x4b00NNNNNNNNNNNN
0x4b01NNNNNNNYNNNN
0x4b02NNNNNNNNNNNN
0x4b03NNNNNNNYNNNN
0x4b04NNNNNNNNNNNN
0x4b05NNNNNNNYNNNN
0x4b06NNNNNNNNNNNN
0x4b07NNNNNNNYNNNN
0x4b08NNNNNNNNNNNN
0x4b09NNNNNNNYNNNN
0x4b0aNNNNNNNNNNNN
0x4b0bNNNNNNNYNNNN
0x4b0cNNNNNNNNNNNN
0x4b0dNNNNNNNYNNNN
0x4b0eNNNNNNNNNNNN
0x4b0fNNNNNNNYNNNN
0x5001NYNYYNNNNNNN
0x5002NYNYYNNNNNNN
0x5003NYNYYNNNNNNN
0x5004NYNYYNNNNNNN
0x5005NYNYYNNNNNNN
0x5006NYNYYNNNNNNN
0x5007NYNYYNNYNNNN
0x5008NYNYYNNYNNNN
0x6400NNNNNNNNYNNN
0x6401NNNNNNNYYNNN
0x6410NNNNNNNNNNNN
0x6411NNNNNNNYNNNN
0x6420NNNNNNNNYNNN
0x6421NNNNNNNYYNNN
0x6430NNNNNNNNYNNN
0x6431NNNNNNNYYNNN
0x6805NNNNNNNYNNNN
0x6807NNNNNNNYNNNN
0x6905NNNNNNNYNNNN
0x6907NNNNNNNYNNNN
0x6909NNNNNNNYNNNN
0xb001NNNNNNNNNNNN
0xb002NNNNNNNNNNNN
0xb003NNNNNNNNNNNN
0xb010NNNNNNNNNNNN
0xb011NNNNNNNNNNNN
0xb012NNNNNNNNNNNN
0xb013NNNNNNNNNNNN
0xb014NNNNNNNNNNNN
0xb015NNNNNNNNNNNN
0xb016NNNNNNNNNNNN
0xb017NNNNNNNNNNNN
0xb018NNNNNNNNNNNN
0xb019NNNNNNNNNNNN
0xb01aNNNNNNNNNNNN
0xb01bNNNNNNNNNNNN
0xb01cNNNNNNNNNNNN
0xb01dNNNNNNNNNNNN
0xb01eNNNNNNNNNNNN
0xb01fNNNNNNNNNNNN
0xb020NNNNNNNNNNNN
0xb021NNNNNNNNNNNN
0xb022NNNNNNNNNNNN
0xb023NNNNNNNNNNNN
0xb024NNNNNNNNNNNN
0xb025NNNNNNNNNNNN
0xb026NNNNNNNNNNNN
0xb027NNNNNNNNNNNN
0xb110NNNNNNNNNNNN
0xb111NNNNNNNNNNNN
0xb114NNNNNNNNNNNN
0xb115NNNNNNNNNNNN
0xb118NNNNNNNNNNNN
0xb119NNNNNNNNNNNN
0xb11aNNNNNNNNNNNN
0xb11bNNNNNNNNNNNN
0xb11cNNNNNNNNNNNN
0xb11dNNNNNNNNNNNN
0xb120NNNNNNNNNNNN
0xb121NNNNNNNNNNNN
0xb122NNNNNNNNNNNN
0xb123NNNNNNNNNNNN
0xb124NNNNNNNNNNNN
0xb125NNNNNNNNNNNN
0xb126NNNNNNNNNNNN
0xb127NNNNNNNNNNNN
0xb130NNNNNNNNNNNN
0xb131NNNNNNNNNNNN
0xb132NNNNNNNNNNNN
0xb133NNNNNNNNNNNN
0xc001NNNNNNNNNNNN
0xc002NNNNNNNNNNNN
0xc101NNNNNNNNNNNN
0xc102NNNNNNNNNNNN
0xc103NNNNNNNNNNNN
0xc104NNNNNNNNNNNN
0xc201NNNNNNNNNNNN
0xc202NNNNNNNNNNNN
0xc203NNNNNNNNNNNN
0xc204NNNNNNNNNNNN
0xc205NNNNNNNNNNNN
0xc206NNNNNNNNNNNN
0xc301NNNNNNNNNNNN
0xc302NNNNNNNNNNNN
0xc401NNNNNNNNNNNN
0xc402NNNNNNNNNNNN
0xd000NNNNNNNYNYYY
0xd001NNNNNNNYNYYY
0xd002NNNNNNNYNYYY
0xd003NNNNNNNYNYYY
0xf000NNNNNNNNNNNN
0xf001NNNNNNNNNNNN
0xf002NNNNNNNYNNNN
0xf003NNNNNNNNNNNN
0xf004NNNNNNNNNNNN
0xf005NNNNNNNNNNNN
0xf006NNNNNNNYNNNN
0xf007NNNNNNNNNNNN
0xf008NNNNNNNNNNNN
0xf009NNNNNNNNNNNN
0xf00aNNNNNNNYNNNN
0xf00bNNNNNNNNNNNN
0xf00cNNNNNNNNNNNN
0xf00dNNNNNNNYNNNN
0xf00eNNNNNNNNNNNN
0xf010NNNNNNNNNNNN
0xf011NNNNNNNNNNNN
0xf012NNNNNNNYNNNN
0xf013NNNNNNNNNNNN
0xf014NNNNNNNNNNNN
0xf015NNNNNNNNNNNN
0xf016NNNNNNNNNNNN
0xf017NNNNNNNNNNNN
0xf018NNNNNNNNNNNN
0xf019NNNNNNNYNNNN
0xf01aNNNNNNNNNNNN
0xf020NNNNNNNNNNNN
0xf021NNNNNNNNNNNN
0xf022NNNNNNNYNNNN
0xf023NNNNNNNNNNNN
0xf024NNNNNNNNNNNN
0xf025NNNNNNNNNNNN
0xf026NNNNNNNNNNNN
0xf027NNNNNNNNNNNN
0xf028NNNNNNNYNNNN
0xf029NNNNNNNNNNNN
0xf100NNNNNNNNNNNN
0xf101NNNNNNNNNNNN
0xf102NNNNNNNNNNNN
0xf103NNNNNNNNNNNN
0xf104NNNNNNNNNNNN
0xf105NNNNNNNNNNNN
0xf106NNNNNNNNNNNN
0xf107NNNNNNNYNNNN
0xf108NNNNNNNNNNNN
0xf109NNNNNNNYNNNN
0xf200NNNNNNNNNNNN
0xf201NNNNNNNYNNNN
0xf202NNNNNNNNNNNN
0xf203NNNNNNNYNNNN
0xf204NNNNNNNNNNNN
0xf205NNNNNNNYNNNN
0xf206NNNNNNNNNNNN
0xf207NNNNNNNYNNNN
0xf210NNNNNNNNNNNN
0xf211NNNNNNNYNNNN
0xf212NNNNNNNYNNNN
0xf213NNNNNNNNNNNN
0xf214NNNNNNNYNNNN
0xf215NNNNNNNYNNNN
0xf216NNNNNNNNNNNN
0xf217NNNNNNNYNNNN
0xf218NNNNNNNYNNNN
Legend:
Clt ID: Client OpenTP1 identifier
Clt com num: Client communication number
Svr ID: Server OpenTP1 identifier
Rt ID: Root OpenTP1 identifier
Rt com num: Root communication number
Svc grp: Service group name
Svc: Service name
Ret cd: Return code
Gbl ID: Global transaction identifier
Qu: Queue name
Msg tkn: Message token
Msg ID: Message identifier
Y: Acquires the information.
N: Does not acquire the information.

(2) Acquiring MCF performance verification trace information

OpenTP1 acquires message transfer trace information at the times listed in the table below for each event ID. This table also shows the length of the trace data that is required when each events occurs.

Table L-3 Timing for acquisition of MCF performance verification trace information

Event IDTimingAcquisition processTrace data length
(units: bytes)
0xa000Immediately after receiving a messageC128
0xa001Immediately before sending a messageC128
0xa020Immediately before storing a receive message in the input queue (if an IJ is acquired, immediately before acquiring the IJ)C128
0xa021Immediately after a message is received by an MHP (if a GJ is acquired, immediately before acquiring the GJ)U128
0xa022Immediately after storing a send message in the output queue (if an OJ is acquired, immediately before acquiring the OJ)U128
0xa023Immediately before starting transaction commit processing (immediately before acquiring a PJ)U256
0xa024Immediately after preparations for transaction commit processing are completed (immediately before acquiring an HJ)U256
0xa025Immediately before rolling back a transaction (immediately before acquiring a BJ)U256
0xa026Immediately after synchronization point processing on transaction is finished (immediately before acquiring a TJ)U128
0xa027Immediately after message transmission is completed (if an AJ is acquired, immediately before acquiring the AJ)C128
0xa050Immediately before calling an MHP service functionU320#1
0xa051Immediately after an MHP service function returnsU320#1
0xa060Immediately after a function is called#2U128
0xa061Immediately before a function returns#2U128
0xa070Immediately before calling a user exit routineC#3128
0xa071Immediately after a user exit routine returnsC#3128
Legend:
C: Acquired by the MCF communication service process
U: Acquired by the user server process
#1
This information is not acquired if the MHP has a non-transaction attribute. In such a case, the trace data length is 192 bytes.
#2
This information might not be acquired if there is a syntax error in a UAP program written in COBOL.
#3
In the case of a user exit routine that edits sequential numbers of send messages, the information is acquired by the user server process.

The following table lists the information acquired for each event ID.

Table L-4 Information acquired for each event ID (MCF performance verification traces)

Event IDClt IDClt com numSvr IDRt IDRt com numSvc grpSvcRet cdGbl IDQuMsg tknMsg IDMCF#1
0xa000------------------------Y
0xa001------------------------Y
0xa020------------------------Y
0xa021------------------------Y
0xa022------------------------Y
0xa023----------------Y------Y
0xa024----------------Y------Y
0xa025----------------Y------Y
0xa026------------------------Y
0xa027------------------------Y
0xa050----------YY--Y#1--------
0xa051----------YY--Y#1--------
0xa060------------------------Y
0xa061--------------Y--------Y
0xa070------------------------Y
0xa071--------------Y#2--------Y
Legend:
Clt ID: Client OpenTP1 identifier
Clt com num: Client communication number
Svr ID: Server OpenTP1 identifier
Rt ID: Root OpenTP1 identifier
Rt com num: Root communication number
Svc grp: Service group name
Svc: Service name
Ret cd: Return code
Gbl ID: Global transaction identifier
Qu: Queue name
Msg tkn: Message token
Msg ID: Message identifier
MCF: MCF-specified information
Y: Acquires the information.
--: Does not acquire the information.
#1
For details about the MCF-specific information, see Table L-5.
#2
In the case of a user exit routine that edits sequential numbers of send messages, the information is not acquired.

The following table shows the MCF-specific dump output information for each event ID.

Table L-5 Dump output information for each event ID (MCF performance verification trace)

Event IDOffset
0x0000 to 0x00030x0004 to 0x00070x0008 to 0x000f0x0010 to 0x00170x0018 to 0x001f
0xa000MCF identifierThread ID--Input source logical terminal nameProtocol data type#1
0xa001MCF identifierThread ID--Output destination logical terminal nameMAP name,#2 Protocol data type#1
0xa020MCF identifierThread IDApplication nameInput source logical terminal nameIJ
0xa021----Application nameInput source logical terminal nameGJ
0xa022----Application nameOutput destination logical terminal nameOJ
0xa023--------PJ
0xa024--------HJ
0xa025--------BJ
0xa026--------TJ
0xa027MCF identifierThread IDApplication nameOutput destination logical terminal nameAJ
0xa050----------
0xa051----------
0xa060MCF identifierThread ID----API name#3
0xa061MCF identifierThread IDApplication nameLogical terminal nameAPI name#3
0xa070MCF identifierThread ID----User exit routine name#3
0xa071MCF identifierThread ID----User exit routine name#3
Legend:
--: Information is not acquired.
#1
The protocol data type is acquired only when TP1/NET/OSAS-NIF is used.
#2
The MAP name (map name) is acquired only when TP1/NET/XMAP3 is used.
#3
For details about the API name that is output for each MCF-provided function, see Table L-6. For details about the user exit routine name that is output for each user exit routine, see Table L-7.

The following table lists the API name that is output for each MCF function.

Table L-6 API name that is output for each MCF function

MCF-provided functionC language library function nameAPI name
Deletes application timer start requestsdc_mcf_adltap"TDLTAP"
Reports application informationdc_mcf_ap_info"APINFO"
Reports application information to UOCsdc_mcf_ap_info_uoc"APINFO_U"
Executes a commit operation on an MHPdc_mcf_commit"COMMIT"
Stops continuous-inquiry responsedc_mcf_contend"CONTEND"
Starts an application programdc_mcf_execap"EXECAP"
Receives messagesdc_mcf_receive"RECEIVE"
Receives a synchronous messagedc_mcf_recvsync"RECVSYNC"
Sends a response messagedc_mcf_reply"REPLY"
Resends a messagedc_mcf_resend"RESEND"
Executes a rollback operation on an MHPdc_mcf_rollback"ROLLBACK"
Sends a messagedc_mcf_send"SEND"
Sends and receives synchronous messagesdc_mcf_sendrecv"SENDRECV"
Sends a synchronous messagedc_mcf_sendsync"SENDSYNC"
Establishes a connectiondc_mcf_tactcn"TACTCN"
Releases a logical terminal from shutdown statusdc_mcf_tactle"TACTLE"
Releases a connectiondc_mcf_tdctcn"TDCTCN"
Shuts down a logical terminaldc_mcf_tdctle"TDCTLE"
Deletes a logical terminal's output queuedc_mcf_tdlqle"TDLQLE"
Receives temporary stored datadc_mcf_tempget"TEMPGET"
Modifies temporary stored datadc_mcf_tempput"TEMPPUT"
Cancels user timer monitoringdc_mcf_timer_cancel"TIMERCAN"
Sets user timer monitoringdc_mcf_timer_set"TIMERSET"
Acquires the connection statusdc_mcf_tlscn"TLSCN"
Acquires the status of the MCF communication servicedc_mcf_tlscom"TLSCOM"
Acquires the status of a logical terminaldc_mcf_tlsle"TLSLE"
Acquires the acceptance status for a server-type connection establishment requestdc_mcf_tlsln"TLSLN"
Stops accepting a server-type connection establishment requestdc_mcf_tofln"TOFLN"
Starts accepting a server-type connection establishment requestdc_mcf_tonln"TONLN"

The following table shows the user exit routine name that is output for each MCF user exit routine.

Table L-7 User exit routine name that is output for each MCF user exit routine

UOC typeUOC name
User exit routine that edits sequential numbers of send messages"SEND_UOC"
Any other user exit routineName of the system-provided variable that sets the address of the user exit routine function