2.93 pdprfed (Edit and output performance trace information)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Command arguments
(6) Rules
(7) Notes
(8) Output format

(1) Function

The pdprfed command converts performance trace information files from binary to CSV format and then outputs them to the standard output.

(2) Executor

HiRDB administrator

(3) Format

 pdprfed [-T start-time,end-time]
         [-p process-ID[,process-ID]...] [-e event-ID[,event-ID]...]
         [-H]
          performance-trace-information-file-name

(4) Options

(a) -T start-time,end-time

Specifies that the trace information collected within the specified time period is to be output in CSV format. Specify each time in the format YYYYMMDDHHMMSS.

(b) -p process-ID[,process-ID]...

Specifies that the information for the specified process IDs is to be output in CSV format. When multiple process IDs are specified, the command outputs only the trace information applicable to all the specified process IDs.

(c) -e event-ID[,event-ID]...

Specifies that information for the specified event IDs is to be output in CSV format. When multiple event IDs are specified, the command outputs only the trace information applicable to all the specified event IDs.

(d) -H

Specifies that the performance trace information is to be output in CSV format without headers.

(5) Command arguments

(a) performance-trace-information-file-name

Specifies the name of the file that contains the performance trace information.

(6) Rules

  1. The pdprfed command can be executed regardless of whether HiRDB is running.
  2. You can execute the pdprfed command on any server machine.

(7) Notes

  1. The following are the pdprfed command's return codes:
    0: Normal termination
    8: Abnormal termination
    12: Abnormal termination (internal conflict)
  2. When this command executes, performance traces are output in CSV format in the order they were stored in the performance trace information file (binary format), not necessarily in chronological order. If you need to sort the contents of the performance trace file in chronological order or merge the contents of multiple files, you must edit the CSV data that was output by this command.
  3. The pdprfed command outputs performance trace information in CSV format as is, even if the performance trace information file (binary format) lacks some information or contains invalid information. In such a case, the return code is 0 (normal termination).
  4. If some items in the performance trace information file (binary format) are corrupted, the format of the output results might differ from the format shown in (8) Output format.
  5. Specify the command on the same platform on which the performance trace information file was collected. If a file collected on a different platform is specified, invalid results might be output.

(8) Output format

The following shows the output example:

time,svname,pid,tid,eid,no,ip,len,c_ip,c_pid,c_port,c_conn,c_no,r_id,r_user,binary,text
2012/12/04 12:13:06.902202,f001,9974,1,0x10022002​,13,10.197.12.141,104,10.197.12.141,12862,,2,,unt100000002​,,02004F50 4E320000,..OPN2..
2012/12/04 12:13:06.902684,f001,9974,1,0x13012503​,14,10.197.12.141,124,10.197.12.141,12862,,2,,unt100000002​,,64000000​ 62303131​ 00202020​ 00000000​ E42E0000 01000000​ 00000000​,d...b011.
2012/12/04 12:13:06.902769,f001,9974,1,0x11019101​,15,10.197.12.141,92,,,,,,unt100000002​,,0AC50C8D 0200E42E 00000000​ AA2A0000,.............*..
2012/12/04 12:13:06.902797,f001,9974,1,0x11019100​,16,10.197.12.141,72,,,,,,unt100000002​,,,
2012/12/04 12:13:06.903019,b011,10064,1,0x11029101​,1,10.197.12.141,60,,,,,,,,,
2012/12/04 12:13:06.903476,b011,10064,1,0x11009600​,2,10.197.12.141,168,,,,,,unt100000002​,,2F350E00 20000000​ 30000000​ 05000000​ F6260000​ 48524442​ 756E7431 02010100​ 00000000​ 00000000​ 02000000​ 03000000​ 05000000​ 04000000​ 90000000​ 48524442​ 756E7431 66303031​ 00000000​ 00000000​ F6260000​ 02000000​ 05000000​,/5.. ...0........&..HRDBunt1................................HRDBunt1f001.........&..........
2012/12/04 12:13:06.903503,b011,10064,1,0x13022003​,3,10.197.12.141,112,0.0.0.0,0,,2,,unt100000002​,,64000000​ 0000A03A 00000000​ 01000000​,d......:........
2012/12/04 12:13:06.904324,f001,9974,1,0x10012002​,17,10.197.12.141,108,10.197.12.141,12862,,2,,unt100000002​,,02004F50 4E320000 00000000​,..OPN2......
Explanation
The following table describes the information that is output:
HeaderDescriptionExample of output
timeTrace collection time2010/02/10 13:40:36.201194
svnameServer name, process name#fes1
pidProcess ID30089
tidThread ID1
eidEvent ID0x10012002​
noPerformance trace sequence number125
ipIP address10.208.175.34
lenMaintenance information100
c_ipClient's IP address10.208.175.35
c_pidClient's process ID31884
c_portClient's port number30142
c_connClient's connection sequence number3
c_noMaintenance information
r_idPerformance ID#unt10000043​E
r_userWhen integrated with Hitachi Application Server:
Root application information
Other:
Maintenance information
41424300​ 4AE40000 012E0000
binaryMaintenance information02004155​ 49320000​ 00000000​
textMaintenance information..AUI2......
Legend:
Blank column: Not output.
#
A byte whose character data is invalid due to missing data in the performance trace information file (binary format) is displayed as a dot (.).