When Y is set for DCCLTPRFINFOSEND of the client environment definition, identification information for performance verification is transferred to TP1/Server.

However, TP1/Client might not be able to transfer the identification information depending on the TP1/Server version. For details, see the manual OpenTP1 Operation or the manual TP1/LiNK User's Guide.

When Y is specified for DCCLTPRFINFOSEND of the client environment definition, TP1/Client adds unique identification information (such as an IP address) to messages sent to TP1/Server every time the dc_clt_cltin_s function is issued. The added information is included in the TP1/Client UAP trace. The information is also included in the TP1/Server performance verification trace.

By checking the TP1/Client UAP trace against the TP1/Server performance verification trace, you can determine the sequence of processing between TP1/Client and TP1/Server.

Note, however, that if the DCTRCUAP specification of the client environment definition is disabled, the identification information for performance verification is not included in the UAP trace (the information is transferred to TP1/Server).

Identification information for TP1/Client performance verification is added to the TP1/Client UAP trace and the TP1/Server performance verification trace.

(a) Items acquired as identification information for performance verification

The following explains the items acquired as identification information for performance verification:

Node ID: aa[bb] (four-byte alphanumeric character string)

aa: Either of the following values is set:

• For TP1/Client/W: _W
• For TP1/Client/P: _P

bb: Two alphanumeric characters (0 to 9, A to Z, a to z) are randomly set.

Root communication sequence number: [xxxxxxxx] (four-byte hexadecimal data)

xxxxxxxx: IP address

RPC communication sequence number: [yyyy][zzzz] (four-byte hexadecimal data)

yyyy: Random two-byte hexadecimal numbers

zzzz: Communication sequence number (incremented every time the function is called)

(b) Example of an output trace

The following shows an example of an output trace when the node ID is _WOX, the root communication sequence number is f784d10a, and the RPC sequence number is 4e880002.

Example of the output of a TP1/Client UAP trace:

Information between the function entry (EVENT=BEGIN) and exit (EVENT=END) is acquired before a message is sent.

 
DATE = 2008/08/11 TIME = 05:08:35.603 PID = 2072:3152 SIZE = 26  
FUNC = dc_rpc_call_s                         EVENT = PRF
Address   +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +a +b +c +d +e +f  
                                         0123456789abcdef
00000000  5f 57 4f 58 2f 30 78 66 37 38 34 64 31 30 61 2f  
                                          _WOX/0xf784d10a/
00000010  30 78 34 65 38 38 30 30 30 32                    
                                                0x4e880002
 

Example of the output of a TP1/Server performance verification trace:

PRF: Rec Node: smpl Run-ID: 0x4743dfcc Process: 53000        Trace: 4             Event: 0x1003 Time: 2008/08/11 05:08:36 583.000.000 Server-name: svgrp    
Rc: 0 Client:  - 0x4e880002     Server: **** Root: _WOX - 0xf784d10a  Svc-Grp: ******************************** Svc: ****************************** Trn: *

TP1/Client adds identification information for performance verification to the UAP trace when any of the following functions is issued:

• dc_rpc_call_s
• dc_rpc_call_to_s
• dc_clt_connect_s
• dc_clt_disconnect_s
• dc_trn_begin_s
• dc_trn_chained_commit_s
• dc_trn_chained_rollback_s
• dc_trn_unchained_commit_s
• dc_trn_unchained_rollback_s