utotrcout [-s service-group-name [,service-name]...] [-v server-name] [-i] [-n] [-t [edit-start-date-and-time] [,edit-end-date-and-time]] edit-file-name

Edits the trace information in the specified trace file or trace merge file and outputs the information to standard output.

• -s service-group-name ~<identifier of 1-31 characters>
  service-name ~<identifier of 1-31 characters>
  Edits and outputs trace information for a specified service. Specify both the service group name and service name, delimiting the two names with a comma (,).
  Two or more services can be specified for a service group. Delimit the service names with commas. Do not insert a space or symbol before or after the comma.
  Both the service group name and service name must be specified. If no service name is specified, trace information is edited and output to standard output for all the services in the specified service group.
  When this option is omitted, the trace information of all the service groups in the specified file is edited and output.
  If this option is specified with the -v option, both specifications apply to the output trace information.
  If this option is specified with the -n option, trace information for the service request destination is also output.
  
• -v server-name ~<identifier of 1-8 characters>
  Edits and outputs trace information for the specified server.
  When this option is omitted, the trace information of all the servers in the specified file is edited and output.
  If this option is specified with the -s option, both specifications apply to the output trace information.
  If this option is specified with the -n option, trace information on service requests to the specified server is also output.
  
• -i
  Outputs selected information, such as function names, from the trace information collected in the specified file to standard output.
  When this option is omitted, all trace information is output to standard output.
  
• -n
  Outputs the trace information collected in the specified file to standard output in the sequence in which the information was collected.
  
• -t edit-start-date-and-time, edit-end-date-and-time
  Sets the time range for output of trace information. The specified start time is corrected to the log time for the process that made the first service request.
  Specify the start and end times within the range from 0:0:0 on January 1, 1970 to the current time.
  If the edit start time is omitted, trace information is output from the start of the specified file up to the specified edit end time.
  If the edit end time is omitted, trace information is output from the specified edit start time up to the end of the specified file.
  Specify the start and end times in the following format:
  

  hhmmss[MMDD[YYYY]]

  where

  hh

  hour (00 hh 23)

  mm

  minute (00 mm 59)

  ss

  second (00 ss 59)

  MM

  month (01 MM 12)

  DD

  day (01 DD 31)

  YYYY

  year (1970 YYYY 9999)

  If YYYY is omitted in the start or end time, the current year is assumed. If MM, DD, and YYYY are all omitted, the current month, day, and year are assumed.
  Either the edit start time or the edit end time must be specified.
  

• edit-file-name ~<pathname>
  Specify the name of the trace file or trace merge file to be edited.
  

(a) -i option omitted

1. Tester information:
   
   • Name of the server at which the UAP was started (up to 8 characters)
   • Date and time, corrected to the log time for the process that made the first service request
     (last two digits of year/month/day hour:minute:second)
     
   • Service group name of the activated service (up to 31 characters).
     **** is displayed for an SUP.
     
   • Time at which the UAP trace information was collected
     (last two digits of year/month/day hour:minute:second)
     
   • Sequence number of the entry for which trace information was collected (6 digits)
   • ID of the process for which trace information was collected
   • Test user ID of the user who started the UAP (up to 4 characters)
2. UAP trace information (same output format as for uatdump -e command):
   
   • Type of trace information collected
   • Date and time when the trace information was collected.
     Not displayed for functions that activate or terminate service requests.
     
   • Date and time when the tester information or the UAP trace information was collected in the format of year (last two digits)/month/day hour:minutes:seconds.
   • Sequential number (six digits) of the entry that collected trace information
   • Name of the service that activated the UAP (up to 31 characters).
     **** is displayed for an SUP or when the service is unknown.
     
3. Output area for call information on OpenTP1 functions

• Output example (-i option omitted)
  

  

  

  

  

  

  

  

1. Trace information collected at SPP startup
2. Trace information collected at SUP startup
3. Trace information collected at service execution
4. Trace information collected at SUP completion
5. Trace information collected at SPP completion

(b) -i option specified

1. Tester information:
   
   • Date and time, corrected to the log time for the process that made the first service request
     (last two digits of year/month/day hour:minute:second)
     
   • Date and time when the tester information was collected
     (last two digits of year/month/day hour:minute:second)
     
   • ID of the process for which the UAP trace was collected
   • Name of the server at which the UAP was started (up to 8 characters)
   • Service group name of the activated service (up to 31 characters).
     **** is displayed for an SUP.
     
   • Nest number of the UAP for which trace information was collected.
     0 is displayed for trace information for which the online tester version cannot perform nest control.
     When a simulated client UAP or TP1/Client UAP makes the service request, the nest numbers of the service request destinations are displayed from 1.
     
2. UAP trace information
   
   • Type of trace information collected
   • Time at which the trace information was collected.
     For functions that activate or terminate service requests, the name of the service that activated the UAP is displayed (up to 31 characters).
     

• Output example (-i option specified)
  

  

1. Trace information collected at SPP startup
2. Trace information collected at SUP startup
3. Trace information collected at service execution
4. Trace information collected at SUP completion
5. Trace information collected at SPP completion

• When the specified edit file contains trace information of an older version than this command, a warning message is output and the information is output in the order in which it was stored in the file.
• When the -n option is specified, a warning message is output if the required trace information does not exist (part of the information is missing).
• When the -n option is specified and the edition start date and time specified in the -t option is a time between the edition object date and times for two consecutive groups, the trace information for the latter and subsequent groups is output.
• When the -n option is specified, trace information is output up to the nesting level of the client process, even if the edition object date and time of the trace information for the service request destination exceeds the edition end date and time specified in the -t option.
• When trace information is collected with the complete I/O data specified, tester information may be output in the middle of I/O data.
• Valid option combinations are shown below.
  

  Specifiable option combinations	-s	-v	-n	-t	-i
  -s	-s	-s, -v	-s, -n	-s, -t	-s, -i
  -v	--	-v	-v, -n	-v, -t	-v, -i
  -n	--	--	-n	-n, -t	-n, -i
  -t	--	--	--	-t	-t, -i
  -i	--	--	--	--	-i

  Legend:

  -x: Only the -x option is valid.

  -x, -y: Both the -x and -y options are valid.

  --: Not applicable