|
|
|
|
|
Level 2 (and 3 and 4)
|
# Thu Jan 15 22:31:24 2004 668000 API> retrieve,c,dm_document
# Thu Jan 15 22:31:24 2004 688000 Res: '0900145280000148'
# Thu Jan 15 22:31:24 2004 688000 API> get,c,l,object_name
# Thu Jan 15 22:31:24 2004 688000 Res: 'Blank PowerPoint pre-3.0 Presentation'
# Thu Jan 15 22:31:24 2004 688000 API> set,c,l,object_name
# Thu Jan 15 22:31:24 2004 688000 SET> my new name
# Thu Jan 15 22:31:24 2004 688000 Res: 'OK'
# Thu Jan 15 22:31:24 2004 688000 API> save,c,l
# Thu Jan 15 22:31:24 2004 728000 Res: 'OK'
# Thu Jan 15 22:31:24 2004 728000 API> trace,c,0
|
|
|
The trace file for level 2 trace is shown above - the only addition to the information given in the level 1 trace is that each line is prefixed with '# ' followed by a date and time. The format for the date/time is a little strange:
|
DDD mmm dd HH:MM:SS YYYY nnnnnn
|
|
|
where:
|
DDD = Day of the week
mmm = Month, abbreviated alphanumeric format
dd = Day of the month
HH = Hour
MM = Minutes
SS = Seconds
YYYY = Year
nnnnnn = microseconds
|
|
|
Although the time is displayed to microsecond precision, in practice the clock tick resolutions provided by operating systems do not allow this level of accuracy - on Windows the resolution is usually 10 ms for a uni-processor machine and 15 ms for a multi-processor machine. Still this provides vital information about the time each API call takes to complete.
The same level of detail is contained in level 3 and 4 trace files. next
|
|
|
