Finding the trace file

The trace facility creates a separate trace file for each Infoprint Server process traced:

• Daemon trace files are named:

  userid.daemon_name.process_id.uniqueidentifier.tracefile#

  For example:

  MACBETH.aopd.pid66297.BA71F05F29707301.1

• Command trace files (for example, the trace file for the lp command) are named:

  userid.process_id.uniqueidentifier.tracefile#

  For example:

  MACBETH.pid50397251.BA71F08C5514A644.1 

The variables in the trace file names are:

userid

The TSO user ID of the person who initiated the trace.

daemon_name

The name of the daemon that is traced, if applicable.

process_id

The ID of the process that is created in z/OS® UNIX to create the trace.

unique identifier

The time the trace was created. This value is the result of the STCK (Store Clock) processing instruction. The value is displayed in hexadecimal format as a character string.

tracefile#

The number of the trace file. If the size of the trace file exceeds the maximum size that is specified in AOPTRACEBYTES environment variable or Trace size (MBs) parameter in the Printer Inventory, Infoprint Server creates a new file that has the same name (including the unique identifier) except that tracefile# is incremented by 1. If the number of trace files exceeds the number that is specified in AOPTRACEMAXFILES environment variable or Number of files parameter in the Printer Inventory, Infoprint Server deletes the oldest file.