OpenTP1 Version 7 Operation
prfed (Edit and output trace information files)
Format
prfed [-d] [-m] [-v] [-T [start-time][,end-time]] [-r run-ID]
[-p process-ID [,process-ID]...]
[trace-data-file-name [trace-data-file-name]...]
|
Function
The prfed command inputs prf trace information, edits it, and outputs the resulting trace information.
Options
-d
Outputs the detail information in dump format.
When this option is specified with the -v option also specified, the detail information is output as an ASCII character string and a hexadecimal number. The ASCII character string is enclosed in double quotation marks (") and characters that cannot be printed are displayed as periods (.). If a double quotation mark is included within detail information displayed as the ASCII character string, it is displayed in the output as two double quotation marks ("").
-m
Outputs the information with the event IDs of TP1/Message Queue.
-v
Outputs the edited result in CSV format.
-T [start-time][,end-time]
Outputs only the trace information obtained within a specified period.
Specify the start time between 00:00:00 on January 1, 1970, and the current time, the current day, and the current month of the current year.
You must specify either the start time or the end time, or both. If you omit the start time, the command outputs the trace information from the beginning until the specified end time. If you omit the end time, the command outputs the trace information from the specified start time until the end of the trace information.
The start and end times are expressed in the format hhmmss[MMDD[YYYY]]:
- hh: hour (00 hh 23); cannot be omitted
- mm: minutes (00 mm 59); cannot be omitted
- ss: seconds (00 ss 59); cannot be omitted
- MM: month (01 MM 12); can be omitted#
- dd: day (01 dd 31); can be omitted#
- yyyy: year (4-digit year from 1970); can be omitted#
- #: If the year is omitted from the start or end time, the specified month, day, and time of the current year are assumed. If the year, month, and day are omitted, the current year, month, and day, and the specified time are assumed. You cannot omit only the month and day, or the month or the day. Doing so causes an option error. If you want to omit the month or the day, then omit the year, the month, and the day (all three).
If you omit the -T option, all the information in the specified file is edited and output.
-r run-ID
Edits and outputs only the information with the specified run ID.
-p process-ID
Edits and outputs only the information with the specified process IDs. More than one process ID can be specified.
Command arguments
trace-data-file-name~<path name>
Specifies the file in which the trace data obtained with the prfget command is stored. When you omit this trace data file name, data will be input from the standard input. If trace data files acquired from multiple nodes are specified simultaneously, you can sort the output results in the order of the acquisition times.
Output format
No option is specified:
For a description of each output item, see below.
The -d option is specified:
The output formats are as shown below when the LCK performance verification trace information file and the TRN event trace information file are specified as the trace data sources.
The output format when the LCK performance verification trace information file is specified follows:
The output format when the TRN event trace information file is specified follows:
- 1 and 2: Displayed as a single line each.
- aaa
- Record status (3 characters)
- Rec: Normal record
- Err: Error record
- bbbb
- Node ID (up to 4 characters)
- cc...cc
- Run ID (10 hexadecimal digits [including 0x at the beginning])
- dd...dd
- ID of process that obtained the trace information (up to 10 decimal digits)
- eeeee
- Trace serial number of the process (up to 5 decimal digits)
- ffffff
- Event ID (6 hexadecimal digits [including 0x at the beginning])
- gggg
- Time when the trace was obtained (year)
- hh
- Time when the trace was obtained (month)
- ii
- Time when the trace was obtained (day)
- jj
- Time when the trace was obtained (time)
- kk
- Time when the trace was obtained (minute)
- ll
- Time when the trace was obtained (second)
- mmm
- Time when the trace was obtained (millisecond)
- nnn
- Time when the trace was obtained (microsecond)
- ooo
- Time when the trace was obtained (nanosecond)
- AA...AA
- Name of the server where an event occurred (up to 8 characters)
- pp...pp
- Return code (up to 11 decimal digits [including the first symbol])
- qqqq
- Client OpenTP1 identifier (up to 4 characters)
- rr...rr
- Client communication number (10 hexadecimal digits [including 0x at the beginning])
- ssss
- Server OpenTP1 identifier (up to 4 characters)
- tttt
- Route OpenTP1 identifier (10 hexadecimal digits [including 0x at the beginning])
- uu...uu
- Route communication number (10 hexadecimal digits [including 0x at the beginning])
- vv...vv
- Service group name (up to 32 characters)
- ww...ww
- Service name (up to 32 characters)
- xx...xx
- Global transaction ID (up to 128 characters)#1
- If no applicable event ID has been acquired, the asterisk (*) is displayed.
- y
- Dump information
- BB...BB
- Event type (up to 32 characters)
- When you specify xafunc in the trn_prf_event_trace_condition operand, an XA function name is output. When you specify trnservice in the trn_prf_event_trace_condition operand, one of the following event types is output.
Event |
Timing |
Event type |
Transaction management service |
Starting |
trnd starting |
Completely started |
trnd started |
Ending |
trnd ending |
Completely ended |
trnd ended |
Transaction recovery service |
Starting |
trnrvd starting |
Completely started |
trnrvd started |
Starting recovery |
trnrvd recovery started |
Ending recovery |
trnrvd recovery ended |
Ending |
trnrvd ending |
Completely ended |
trnrvd ended |
Resource manager monitoring service |
Starting |
trnrmd starting |
Completely started |
trnrmd started |
Ending |
trnrmd ending |
Completely ended |
trnrmd ended |
- CCC
- Acquisition timing (up to three characters)
- DD...DD
- Resource manager name + resource manager extension (up to 33 characters)
- EE...EE
- Transaction identifier assigned to a resource manager by OpenTP1 (80 hexadecimal digits)
- FF...FF
- Internal code 1 (up to six characters)
- GGGG
- Internal code 2 (up to four characters)
- HH...HH
- Resource manager name (up to 10 characters)
- III
- Lock request source type (3 characters)
- When the lock request is received from a UAP: usr
- When the lock request was generated within OpenTP1: dam, tam, mqa, or trn
- JJ....JJ
- Name of resource to be locked (maximum of 16 characters)
- KK
- Lock control mode (2 characters)
- LL....LL
- Request type (maximum of 20 characters)
- MM....MM
- Option flag (maximum of 25 characters)
- NN....NN
- Internal information 1 (16 characters)
- OO....OO
- Internal information 2 (16 characters)
- PP....PP
- Internal information 3 (hexadecimal, 10 digits (including the leading 0x))
- Note
- The asterisk (*) is displayed for items not obtained in the trace.
The -m option is specified:
- 1 and 2: Displayed as a single line each.
- aaa
- Record status (three characters)
- Rec: Normal record
- Err: Error record
- bbbb
- Node ID (up to four characters)
- cc...cc
- Run ID (10 hexadecimal digits (including the beginning 0x))
- dd...dd
- Process ID of the process whose trace information is acquired (up to 10 decimal digits)
- eeeee
- Serial trace number in the applicable process (up to five decimal digits)
- ffffff
- Event ID (six hexadecimal digits (including the beginning 0x))
- gggg
- Time when the trace is acquired (year)
- hh
- Time when the trace is acquired (month)
- ii
- Time when the trace is acquired (day)
- jj
- Time when the trace is acquired (hour)
- kk
- Time when the trace is acquired (minutes)
- ll
- Time when the trace is acquired (seconds)
- mmm
- Time when the trace is acquired (milliseconds)
- nnn
- Time when the trace is acquired (microseconds)
- ooo
- Time when the trace is acquired (nanoseconds)
- AA...AA
- Name of the server where the event occurred (up to eight characters)
- pp...pp
- Return code (up to 11 decimal digits (including the beginning sign))
- qqqq
- Client OpenTP1 identifier (up to four characters)
- rr...rr
- Client communication number (10 hexadecimal digits (including the beginning 0x))
- ssss
- Server OpenTP1 identifier (up to four characters)
- tttt
- Root OpenTP1 identifier (up to four characters)
- uu...uu
- Root communication number (10 hexadecimal digits (including the beginning 0x))
- vv...vv
- Service group name (up to 32 characters)
- ww...ww
- Service name (up to 32 characters)
- xx...xx
- Global transaction ID (up to 128 characters)#
- zz...zz
- Queue name (up to 48 characters)#
- BB...BB
- Message identifier (66 hexadecimal digits (including the beginning 0x))#
- CC...CC
- Message token (18 hexadecimal digits (including the beginning 0x))#
- y
- Dump information
- Note
- The asterisk (*) is displayed for items not obtained in the trace.
- #: The asterisk (*) is displayed if applicable event IDs are not acquired.
When the -v option is specified:
For explanations of the output items, see When the -d, -m, and -v options are specified below.
When the -d and -v options are specified:
For explanations of the output items, see When the -d, -m, and -v options are specified below.
When the -m and -v options are specified:
For explanations of the output items, see When the -d, -m, and -v options are specified below.
When the -d, -m, and -v options are specified:
- 1 and 2: Displayed as a single line each.
- 2: Displayed for each record for which a trace is acquired.
- aaa: Record status (3 characters)
- Rec: Normal record
- Err: Error record
- bbbb: Node ID (maximum of 4 characters)
- cc....cc: Run ID (hexadecimal, 10 digits (including the leading 0x))
- dd....dd: Process ID of the process from which trace information is acquired (hexadecimal, maximum of 10 digits)
- eeeee: Trace serial number in the applicable process (hexadecimal, maximum of 5 digits)
- ffffff: Event ID (hexadecimal, 10 digits (including the leading 0x))
- gggg: Year during which trace is acquired
- hh: Month during which trace is acquired
- ii: Date on which trace is acquired
- jj: Hour at which trace is acquired
- kk: Minute at which trace is acquired
- ll: Second at which trace is acquired
- mm....mm: Nanosecond at which trace is acquired
- nn....nn: Name of server where the event occurred (maximum of 8 characters)
- oo....oo: Return code (hexadecimal, maximum of 11 digits (including the leading symbol))
- pppp: Client OpenTP1 identifier (maximum of 4 characters)
- qq....qq: Client serial number (hexadecimal, 10 digits (including the leading 0x))
- rrrr: Server OpenTP1 identifier (maximum of 4 characters)
- ssss: Route OpenTP1 identifier (maximum of 4 characters)
- tt....tt: Route communication number (hexadecimal, 10 digits (including the leading 0x))
- uu....uu: Service group name (maximum of 32 characters)
- vv....vv: Service name (maximum of 32 characters)
- ww....ww: Global transaction ID (maximum of 128 characters)
If no applicable event ID is acquired, the asterisk (*) is displayed.
- xx....xx: Queue name (maximum of 48 characters)
- yy....yy: Message identifier (hexadecimal, 66 digits (including the leading 0x))
- zz....zz: Message token (hexadecimal, 18 digits (including the leading 0x))
- AA....AA: ASCII character string of the detail information (maximum of 256 characters)
- BB....BB: Hexadecimal character string of the detail information (including zutri2.tif (single-byte space) which appears after each string of 8 characters; maximum of 575 characters)
The table below shows the configuration of the detail information when the TRN event trace information file is specified for the trace data.
Item |
Position |
Length (bytes) |
Maintenance information 1 |
0 |
4 |
Maintenance information 2 |
4 |
4 |
Maintenance information 3 |
8 |
4 |
Maintenance information 4 |
12 |
4 |
Maintenance information 5 |
16 |
4 |
Resource manager name + resource manager extension |
20 |
36 |
Transaction identifier |
56 |
40 |
Event type# |
96 |
2 |
Acquisition timing: 0x10: IN, 0x20 or 0x30: OUT |
98 |
1 |
Maintenance information 6 |
99 |
9 |
Maintenance information 7 |
108 |
4 |
Maintenance information 8 |
112 |
16 |
- #
- The following table shows the event types. Event types not listed in the table are for OpenTP1 maintenance information.
Event type |
Event name |
0x1001 |
trnd starting |
0x1002 |
trnd started |
0x1003 |
trnrmd starting |
0x1004 |
trnrmd started |
0x1005 |
trnrvd starting |
0x1006 |
trnrvd started |
0x1007 |
trn preending |
0x1008 |
trn preended |
0x1009 |
trnd ending |
0x100a |
trnd ended |
0x100b |
trnrmd ending |
0x100c |
trnrmd ended |
0x100d |
trnrvd ending |
0x100e |
trnrvd ended |
0x100f |
trnrvd recover started |
0x1010 |
trnrvd recover ended |
0x2001 |
xa_open |
0x2002 |
xa_close |
0x2003 |
xa_start |
0x2004 |
xa_end |
0x2005 |
xa_rollback |
0x2006 |
xa_prepare |
0x2007 |
xa_commit |
0x2008 |
xa_recover |
0x2009 |
xa_forget |
0x200a |
xa_complete |
0x200b |
ax_reg |
0x200c |
ax_unreg |
0x2021 |
xa_done |
0x2022 |
xa_ready |
0x2023 |
xa_start_2 |
0x2024 |
xa_wait |
0x2025 |
xa_wait_recovery |
0x2041 |
ax_add_branch |
0x2042 |
ax_commit |
0x2043 |
ax_done |
0x2044 |
ax_end |
0x2045 |
ax_forget_branch |
0x2046 |
ax_get_branch_info |
0x2047 |
ax_prepare |
0x2048 |
ax_ready |
0x2049 |
ax_recover |
0x204a |
ax_reg_2 |
0x204b |
ax_rollback |
0x204c |
ax_set_branch_info |
0x204d |
ax_start |
0x204e |
ax_start_2 |
0x3000 |
dc_trn_begin |
0x3001 |
dc_trn_chained_commit |
0x3002 |
dc_trn_chained_rollback |
0x3003 |
dc_trn_unchained_commit |
0x3004 |
dc_trn_unchained_rollback |
0x3005 |
dc_trn_get_xid |
0x3006 |
dc_trn_info |
0x4000 |
tx_begin |
0x4001 |
tx_commit |
0x4002 |
tx_open |
0x4003 |
tx_close |
0x4004 |
tx_rollback |
0x4005 |
tx_info |
0x4006 |
tx_set_commit_return |
0x4007 |
tx_set_transaction_control |
0x4008 |
tx_set_transaction_timeout |
0x5000 |
trncmt |
0x5001 |
trnrbk |
0x5002 |
trnfgt |
0x5003 |
trnstics |
- Note: Any item not acquired in a trace is displayed as an asterisk (*).
Output messages
Message ID |
Description |
Output destination |
KFCA26750-E |
Command cannot be executed. |
Standard error output |
KFCA26751-E |
Command format is invalid. |
Standard error output |
KFCA26760-E |
Failed to open the prf trace file. |
Standard error output |
KFCA26761-E |
An error occurred during accessing the prf trace file. |
Standard error output |
KFCA26762-E |
Invalid data is detected during accessing the prf trace file. |
Standard error output |
KFCA26770-I |
Help message |
Standard output |
Notes
- This command can only be used if TP1/Extension 1 is installed. Operation is guaranteed only when TP1/Extension 1 is installed.
- In the example in Output format with no option specified, it appears that one record is output on 4 lines; however, the record is actually output on 2 lines. Therefore, the output display may differ depending on the terminal mode you are using. In this case, use a terminal mode with 80-digit columns such as vt100.
- The dump data in the example in Output format with the -d option specified is only displayed when the record includes data unique to the system or user.
- The traces listed below use the same trace numbers in a process. Consequently, if you use a command to edit these traces only, the trace numbers (eeeee) of the applicable processes that are output in Output format may not be in sequential order.
- Performance verification trace
- XAR performance verification trace
- JNL performance verification trace
- LCK performance verification trace
- MCF performance verification trace
- TRN event trace
- NAM event trace
- Process service event trace
- FIL event trace
For details about trace information, see the manual OpenTP1 Description.
- Do not specify a trace data file larger than 2 GB in the argument of the prfed command. If you want to edit a trace data file exceeding 2 GB, execute the prfed command as follows and edit the trace file:
- Entering trace data from the standard input
prfget [-a] > prf-trace-collection-file
cat prf-trace-collection-file | prfed [options] > trace-edition-result-file
|
- Entering trace data in the prf trace file acquisition directory ($DCDIR/spool/dcprfinf)
- This method allows you to directly enter data in a prf trace file without using the prfget command. Because data is directly entered in a prf trace file, execute this method after OpenTP1 has stopped. If you execute this method while OpenTP1 is running, an error may occur during entry of the prf trace data.
cd $DCDIR/spool/dcprfinf
prfed [options] prf-trace-file[prf-trace-file....]
|
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.