rpcdump [{-r|-m}] [{-c|-f}] [-d text-length] [-t begin-date-and-time] [,end-date-and-time]] [-s service-group-name [,service-name]...] [-b node-identifier [,node-identifier]...] [-v server-name [,server-name]...] [-p process-ID [,process-ID]...] [-x xid [,xid]...] [-n [begin-trace-number] [,end-trace-number]] [RPC-trace-file-name]

The rpcdump command edits trace information of RPC trace files and output it to the standard output.

-r

Outputs the result of editing in the form of an RPC trace file.

-m

Outputs outline RPC trace information. When this option is specified, specification of the -c, -f, and -d options becomes invalid.

-c

Extracts and edits the relationship between the call source and the call destination, and output it in units of call/called trace information and in chronological order according to other options' output conditions. The trace information involved with a call/called relationship to the trace information extracted through other options is output even if not meeting other options' output conditions.

-f

Extracts and edits a series of RPC flow and outputs it in units of nest/nested trace information and in chronological order according to other options' output conditions. The trace information involved in the same flow as the trace information extracted through other options is output even if not meeting other options' output conditions.

When neither the -c option nor the -f option is specified, RPC trace information is displayed chronologically.

-d text-length~((0~4096))

Outputs the contents of a text with the specified length. When this option is omitted, the contents of all texts are output.

-t [begin-date-and-time][,end-date-and-time]

Specifies the output range of trace information by the date and time of trace acquisition.

The times must be specified in the range from 00:00:00 on January 1, 1970 to the current date and time.

The start time and end time cannot both be omitted. When the start time is omitted, the output range is from the beginning of the RPC trace file to the specified end time. When the end time is omitted, the output range is from the specified start time to the end of the RPC trace file.

The begin and end times are expressed in the format hhmmss[MMDD[YYYY]]:

hh: Hour (00 hh 23); cannot be omitted

mm: Minute (00 mm 59); cannot be omitted

ss: Second (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 begin 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 the -t option is omitted, all information in the specified file is edited and output.

-s service-group-name [,service-name]~<1-31 character identifier>

Specifies a service group name and a service name to edit and output trace information including the call destination trace information for a particular service. More than one service name can be specified for a service group, with a comma (,) placed between names. When no service name is specified, the trace information for all services in the specified service group is edited and output. A service name alone cannot be specified.

When the XATMI request/response type communication service is specified, the service group name must be a name specified in the service definition of SPP. No XATMI conversational communication service name cannot be specified.

-b node-identifier~<4-character identifier>

Outputs the trace information collected at an OpenTP1 node with the specified node identifier. It must be the same as the node identifier specified in the system common definition. More than one node identifier can be specified, with a comma (,) placed between identifiers.

-v server-name~<1-8 character identifier>

Outputs trace information collected by the specified server. More than one server name can be specified, with a comma (,) placed between names.

-p process-ID~((0-2147483647))

Outputs trace information collected by the specified process. More than one process IDs can be specified, with a comma (,) placed between IDs.

-x xid~<1-8 hexadecimal digits> ((0-ffffffff))

Outputs trace information with the sequential number of the specified global transaction identifier. More than one xid can be specified, with a comma (,) placed between xids.

-n [begin-trace-number][,end-trace-number] ((1-2147483647))

Outputs trace information ranging from the begin trace number to the end trace number. A trace number is a sequential number assigned to trace information in an RPC trace file.

When the begin trace number is omitted, the output range is from the beginning of the RPC trace file to the end trace number.

When the end trace number is omitted, the output range is from the specified begin trace number to the end of the RPC trace file.

Either the begin or end trace number must be specified.

RPC-trace-file-name~<path name>

Specifies the name of the RPC trace file in which trace information is to be edited. One of the following three names can be used:

• The name of the file specified in rpc_trace_name of the system common definition or user service definition
• The name of the file that stores the result of executing the rpcmrg command
• The name of the file that stores the result of executing the rpcdump command with its -r option specified.

When this command argument is omitted, information is dumped from $DCDIR/spool/rpctr.

The name of the RPC trace file (default: rpctr) included in the path can be a maximum of 13 characters.

(1)-m option specified

1. Edits and output outline information for each RPC text specified by the node identifier, server name, service group name, and service name, or XATMI conversational text.

ff...ff

Name of an RPC trace file

oo...oo

Date and time of the oldest trace information that was edited

nn...nn

Date and time of the newest trace information that was edited

aaaa

Identifier of the node that collected RPC trace information (4 characters)

bb...bb

Name of the server that collected RPC trace information (1-8 characters)

cc...cc

Name of the service group at the RPC text receive destination (1-31 characters)

For an XATMI conversational text, "****" is displayed.

dd...dd

Name of the service at the RPC text receive destination (1-31 characters)

For an XATMI conversational text, "****" is displayed.

eee

Process ID (decimal, left-justified)

ff...ff

Number of RPC request send texts or XATMI reply texts (decimal, left-justified)

gg...gg

Number of RPC request receive texts or XATMI reply texts (decimal, left-justified)

hh...hh

Number of RPC reply send texts or XATMI response texts (decimal, left-justified)

ii...ii

Number of RPC reply receive texts or XATMI response texts (decimal, left-justified)

jj...jj

Number of RPC error reply send texts or XATMI error texts (decimal, left-justified)

kk...kk

Number of RPC error reply receive texts or XATMI error texts (decimal, left-justified)

(2) Neither -r nor -m option specified

1. Displayed only when an RPC request text is sent or received.

2. May not be displayed during XATMI conversational communication

3. The send source information is displayed for receive-side trace information. The receive destination information is displayed for send-side trace information.

4. Displayed only during communication using XATMI functions. Some items may not be displayed depending on the text type or send status.

5. Displayed repeatedly until all texts are processed.

6. Is not displayed if the length of the text specified in the -d option is 0.

aa...aa

RPC trace type

Send

RPC request text has been sent.

Receive

RPC request text has been received.

Send-Reply

RPC reply text has been sent.

Recv-Reply

RPC reply text has been received.

Send-Error

RPC error reply text has been sent.

Recv-Error

RPC error reply text has been received.

XATMI-R/R-Send

XATMI request/response-type request text has been sent.

XATMI-R/R-Recv

XATMI request/response-type request text has been received.

XATMI-R/R-Send-Reply

XATMI request/response reply text has been sent.

XATMI R/R-Recv-Reply

XATMI request/response reply text has been received.

XATMI-R/R-Send-Error

XATMI request/response error text has been sent.

XATMI-R/R-Recv-Error

XATMI request/response error text has been received.

XATMI-CNV-Send

XATMI conversational request text has been sent.

XATMI-CNV-Recv

XATMI conversational request text has been received.

XATMI-CNV-Send-Error

XATMI conversational error text has been sent.

XATMI-CNV-Recv-Error

XATMI conversational error text has been received.

bbb

Trace serial number in an RPC trace file (decimal)

ccc

Nest display (decimal)

Route of RPC nest calls; the route ccc is 1, which is incremented by 1 for each additional nest. 0 is displayed when an RPC is received from a CUP, different system, or an OpenTP1 system 03-00 or an earlier version. Note that, when the transaction is started from a CUP, the RPC request from the system process accepting a request from the CUP is the route, which is 1.

dd...dd

Server name (1-8 characters)

eeee

Node identifier of an OpenTP1 node (4 characters)

fff.fff

Node address of the RPC trace collection destination (decimal, left-justified)

ggggg

Process ID of the RPC trace collection source (decimal, left-justified)

hhhhh

BSD socket port number for the RPC trace collection source (decimal, left-justified)

ii...ii

Time at which a text was sent to an RPC trace file

Format: xxx.xxx x hh:mm:ss xxxx yyy:zzz

Example of output

Wed Jan 1 12:34:56 2003 789:012

The final yyy:zzz indicate the following information:

yyy: milliseconds

zzz: microseconds

This output example indicates that the text was output at 12:34 and 56.789012 seconds on Wednesday, January 1st, 2003.

jj...jj

Service group name (1-31 characters)

kk...kk

Service name (1-31 characters)

ll...ll

Chained RPC display

Chained

Chained RPC is in process.

Unchained

Not a chained RPC.

mmm

Sequence number of global transaction identifier (hexadecimal, left-justified)

nn...nn

Type of RPC

Reply

Synchronous reply type RPC

Noreply

Non-response type RPC

Nowait

Asynchronous reply type RPC

Chained

Chained RPC

oo

Priority value of a service request (decimal, left-justified)

xx...xx

Indication of the sender/receiver

Send source

The send source sends an RPC text.

(The RPC trace output source receives an RPC text.)

Receive destination

The receive destination receives an RPC text. (The RPC trace output source sends an RPC text.)

ppp.ppp

Nodes address of the send source and receive destination (decimal, left-justified)

q

Network type

rrrrr

Port number of the BSD socket for the send source and receive destination (decimal, left-justified)

sss

Thread ID of the send source (decimal, left-justified)

ttttt

Location of a text (hexadecimal)

uu...uu

Text body consisting of up to 16 bytes per line (hexadecimal)

ss...ss

Indication of the text body in terms of ASCII code (1-16 characters). Any character that cannot be printed as a result of conversion is displayed by a period (.).

AA...AA

XATMI service name (1-31 characters)

BB...BB

Buffer type name. Either X_OCTET, X_COMMON or X_C_TYPE is displayed. For the meaning of each name, see the XATMI manual.

CC...CC

Buffer sub-type name (1-16 characters). No sub-type name is displayed when the buffer type is X_OCTET.

DD...DD

Value of tpflags specified in the XATMI function (hexadecimal). Value 0 is not displayed.

EE...EE

Error code (tperror) of an error that occurred with the XATMI function (hexadecimal)

FF...FF

Event that occurred with the tprecv function. Either TREV_SENDONLY, TREV_SVCERR, TREV_SVCFAIL, TREV_SVCSUCC or TREV_DISCONIMM is displayed. For the meaning of each event, see the XATMI manual.

GG...GG

call description during XATMI conversational communication (hexadecimal)

Message ID	Description	Output destination
KFCA00308-E	RPC trace file contains no data.	Standard error output
KFCA00310-E	Specified RPC trace file was not found.	Standard error output
KFCA00312-E	Access error occurred in RPC trace file.	Standard error output
KFCA00314-I	Help message	Standard output
KFCA00352-E	RPC trace file data is incorrect.	Standard error output

• When RPC trace information is output by the rpcdump command, the receive information may be output before the send information. This is because the send information is written into the RPC trace file after text send is completed.
• All conditions specified by the -t, -s, -b, -v, -p, -n and -x options are AND conditions.
• The rpcdump command must be entered when no RPC trace is written. For example, by saving the RPC trace file, the write to the RPC trace file can be suppressed. If the rpcdump command is entered while collecting the RPC trace, an RPC trace file access error may occur depending on the timing. This error occurs if the RPC trace file is switched while RPC trace is being edited.
• If the amount of the transmitted text is greater than the value specified for the rpc_trace_size operand in the system common definition, the user service default definition, or the user service definition, the rpcdump command may not output anything or the output information may be incomplete.