OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

3.8.5 Performance verification trace operations

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.

Notes
  • Trace information is not passed for normal restart and hot standby.
  • The facility for acquiring the performance verification trace does not perform locking when acquiring trace information so that online performance is not affected. Accordingly, if contention for trace acquisition occurs in a multi-processor environment, some trace information may be lost or invalid trace information may be acquired. When you use the prfed command to edit trace information, an error code is displayed for invalid trace information.

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

[Figure]

  1. PRF trace data output during online operation is stored as files with the file name prf_nnn#1 under the directory $DCDIR/spool/dcprfinf. The prf_file_size operand specifies the maximum size of each file, and the prf_file_count operand specifies the number of files. When a file reaches its capacity during online operation, the file is swapped and subsequent traces are acquired to the new file.
  2. When OpenTP1 shuts down, the files prf_nnn.bk2#2 in $DCDIR/spool/save are moved to prf_nnn.bk1.#2
  3. The files prf_nnn #1 in $DCDIR/spool/dcprfinf are copied to $DCDIR/spool/save under the name prf_nnn.bk2.#2
    #1
    nnn: A number, starting from 001 and having the value specified for the prf_file_count operand as its upper limit.
    #2
    nnn: Value corresponding to the file name at the backup source.
Organization of this subsection
(1) Performance verification traces acquired by OpenTP1
(2) Backing up performance verification trace files
(3) Disabling backup of performance verification trace files

(1) Performance verification traces acquired by OpenTP1

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#

#
nnn: Value ranging from 001 to the value specified in the prf_file_count operand in the following definition:
[Figure] Performance verification trace: Performance verification trace definition
[Figure] XAR performance verification trace: XAR performance verification trace definition
[Figure] JNL performance verification trace: JNL performance verification trace definition
[Figure] LCK performance verification trace: LCK performance verification trace definition
[Figure] MCF performance verification trace: MCF performance verification trace definition
[Figure] TRN event trace: TRN event trace definition

(2) Backing up performance verification trace files

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:

(3) Disabling backup of performance verification trace files

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.