Trace information is acquired for all main events that occur in each service running on OpenTP1. This process is called a performance verification trace (prf trace). A performance verification trace is made up of trace information intended for enhancing the efficiency of performance verifications and troubleshooting. A performance verification trace has the following features:

• You can acquire a trace even if the information extends over nodes or processes.
• You can acquire traces in units of internal events instead of units of APIs. This enables you to determine which area of processing is hindering performance.

TP1/Extension 1 must be installed before you can use this facility. Note that operation will be unpredictable if you run the facility while TP1/Extension 1 is not installed.

To acquire a user-specific performance verification trace from a UAP, call the function dc_prf_utrace_put() [CBLDCPRF('PRFPUT ')].

To find out the acquired sequential trace number of the latest performance verification trace within the process, call the function dc_prf_get_trace_num() [CBLDCPRF('PRFGETN ')]. The acquired sequential trace number of the latest performance verification trace within the process is reported to the call source of the function dc_prf_get_trace_num().