OpenTP1 Version 7 Operation
OpenTP1 acquires the performance verification trace for events of services operating on OpenTP1. The performance verification trace is used to improve efficiency of performance verification and troubleshooting.
The prfget command acquires the trace. The prfed command edits and outputs the acquired trace. The prfget command outputs the performance verification trace in binary format to a UNIX file. The prfed command converts the trace from binary format to character format and then edits and outputs the trace. The prfed command is used to view the details of the trace.
The features of the facility for acquiring the performance verification trace are as follows:
You can use an output event ID to determine when the trace information is acquired. For the event IDs and the timing of acquiring the trace, see L. Acquiring Performance Verification Traces.
You must install TP1/Extension 1 to use this facility. Without TP1/Extension 1 installed, this facility may not operate correctly.
The following figure shows the flow of performance verification trace file operation by using the function that acquires the performance verification trace.
Figure 3-27 Flow of performance verification trace file operation
The table below lists the trace information that OpenTP1 acquires for purposes of performance verification, collectively referred to as performance verification traces. The files acquired as performance verification trace data are called performance verification trace files.
Trace name | Performance verification trace file name |
---|---|
Performance verification trace | prf_nnn# |
XAR performance verification trace | _xr_nnn# |
JNL performance verification trace | _jl_nnn# |
LCK performance verification trace | _lk_nnn# |
MCF performance verification trace | _mc_nnn# |
NAM event trace | _nm_001, _nm_002, _nm_003 |
Process service event trace | _pr_001, _pr_002, _pr_003 |
FIL event trace | _fl_001, _fl_002, _fl_003 |
TRN event trace | _tr_nnn# |
The OpenTP1 functionality for acquiring performance trace data backs up the acquired trace files at OpenTP1 shutdown, to prevent the auditing process from being compromised in cases where trace data is deleted inadvertently. The advantages and disadvantages of taking such a backup are as follows:
In some system configurations, the disadvantages of backing up performance verification trace files may outweigh the advantages. In this case, you can prevent OpenTP1 from backing up these files. However, as this means that performance verification trace files will not be backed up automatically, you must back up these files yourself when necessary.
Before you disable backup of performance verification trace files, we recommend that you take due care to ensure that sufficient data is available for troubleshooting and other activities.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.