sdptrced (edits trace information)
Format
sdptrced {-file trace-file-name[ trace-file-name...]
[-time [start-time][,end-time]]
[-threadid thread-ID[ thread-ID...]] [-csv]|-help}
Function
This command edits and outputs API trace information.
Execution permissions
Administrator user
Prerequisites for command execution
To execute this command, you need the following files:
Storage directory
working-directory\bin\
Arguments
-file trace-file-name[ trace-file-name...]
Specifies the absolute path names of the trace files to be edited. When you specify multiple trace file names, delimit the file names with a single-byte space.
-time [start-time][,end-time]
Specifies in the following format a start time and end time for the trace information that is to be output:
Specify start-time and end-time delimited with a comma and without any spaces.
The following describes the trace information that is displayed according to the specified time:
-threadid thread-ID[ thread-ID...]
Outputs only that trace information that was output by threads with the specified thread IDs.
Express a thread ID in single-byte numeric characters. The permitted value range is from 0 to 9223372036854775807. To specify multiple thread IDs, delimit them with the single-byte space.
-csv
Displays the trace information editing results in the CSV file format.
-help
Displays how to use the command.
If this option is specified, the command terminates without outputting trace information or checking the options for errors.
Notes
Return value
Value | Meaning |
---|---|
0 | The command terminated normally. |
1 | The command terminated abnormally. |
Output format
The output format is shown below. For an example of the output, see 6.3.2 Details of API trace information.
Ver Kind File
aa-aa-aa bbb cc...cc
Date Time nSec Current Parent Root EventID
dddd/dd/dd ee:ee:ee fffffffff gg...gg-hh...hh ii...ii-jj...jj kk...kk-ll...ll 0xmmmmmmmm
Rc Data
noo...oo pp...pp
Ver,Kind,File
aa-aa-aa,bbb,cc...cc
Date,Time,nSec,Current,Parent,Root,EventID,Rc,Data
dddd/dd/dd,ee:ee:ee,fffffffff,gg...gg-hh...hh,ii...ii-jj...jj,kk...kk-ll...ll,0xmmmmmmmm,
noo...oo,pp...pp
The table below explains the variables used in the output format.
Variable | Meaning |
---|---|
aa-aa-aa | Information about the Stream Data Platform - AF version used to output the trace files |
bbb | Type of trace files:
|
cc...cc | Path (absolute path) of the trace file |
dddd/dd/dd | Trace output date (year/month/day) |
ee:ee:ee | Trace output time (hour:minute:second) |
fffffffff | Trace output time nanosecond (9-digit decimal number) |
gg...gg-hh...hh | Serial number assigned to this trace (thread ID (19-digit decimal number) -processing serial number (10-digit decimal number)) |
ii...ii-jj...jj# | Reserved area. This information is output in the format 19-digit-decimal-number-10-digit-decimal-number. |
kk...kk-ll...ll | Serial number assigned to the trace start point (thread ID (19-digit decimal number) -processing serial number (10-digit decimal number)) The trace start point is the time at which the tuple handled by the process that collected this trace was input (or generated within a query). Traces with the same serial number constitute a series of processing on the same tuple. |
mmmmmmmm | Event ID (8-digit hexadecimal number):
|
noo...oo# | Reserved area n indicates the sign part. This information is output as an 11-digit decimal number. A single-byte space is displayed in n. |
pp...pp | Name of query that collected trace information (first 32 bytes of the query name) |