OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/W, TP1/Client/P
A TP1/Server performance verification trace (PRF trace) provides trace information about major events related to services operating on TP1/Server. Use of this trace can improve the effectiveness of performance verification and troubleshooting.
In TP1/Client, identification information for performance verification can be preset. TP1/Client can add the identification information to the TP1/Server performance verification trace. The identification information for performance verification is also added to the TP1/Client UAP trace. This information can be used to check the TP1/Client function execution time (acquired by the UAP trace) against the TP1/Server service execution time (acquired by the performance verification trace). The information can also be used to determine the progress of processing.
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.
The following explains the items acquired as identification information for performance verification:
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.
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
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:
All Rights Reserved. Copyright (C) 2006, 2009, Hitachi, Ltd.