Controlling tracing with environment variables

When tracing is controlled by environmental variables, the daemon that is traced must be stopped and restarted for the environment variable to take effect.
Important: When an Infoprint Server daemon is started, it uses the environment variables for tracing. However, if any of the Printer Inventory tracing parameters are set for a daemon, Infoprint Server then ignores the tracing environment variables and uses only the tracing parameters in the Printer Inventory.
These z/OS® UNIX System Services environment variables control tracing:
AOPTRACEON
Set this variable to any value to turn on tracing. Unset this variable to turn tracing off.
Tip: Setting this variable to any value, even to Off, turns on tracing.
Examples:
AOPTRACEON=1
AOPTRACEON=ON

If AOPTRACEON is turned on, Infoprint Server traces all daemons that were started after the variable was set. Start tracing with AOPTRACEON explains how to limit the trace to a specific Infoprint Server daemon.

If you are tracing Infoprint Central, AOPTRACEON creates a trace file in the directory that AOPTRACEDIR specifies and writes additional presentation layer tracing to the error log that is specified by the IBM HTTP Server - Powered by Apache ErrorLog directive.

Depending on the Infoprint Server component you are using, you can use these environment variables to optionally add data to the trace:

AOPTRACEON_DATA
Includes socket data in the trace. The default is off.
AOPTRACEON_EXITMAP
Includes IP PrintWay extended mode exit data in the trace. The default is off.
AOPTRACEON_FILTER
Includes IP PrintWay extended mode filter data in the trace. The default is off.
AOPTRACEON_MSGLOG
Includes message logging data in the trace. The default is off.
Examples:
  • AOPTRACEON=1 
    AOPTRACEON_DATA=1
  • AOPTRACEON=1 
    AOPTRACEON_EXITMAP=ON
  • 
    AOPTRACEON=ON 
    AOPTRACEON_FILTER=1
  • AOPTRACEON=ON 
    AOPTRACEON_MSGLOG=ON
AOPTRACEBYTES
Specify the maximum size of the trace file. This environment variable is optional. The default is 50 MB. If the size of the trace file exceeds the maximum size that you specified, Infoprint Server creates a new trace file.
Example: AOPTRACEBYTES=25000000
AOPTRACEDIR
Specify the directory where trace files are created. This environment variable is optional, except if you are tracing Infoprint Central. If this variable is not defined, trace files are created in default directory /var/Printsrv/trace/.
The requirements are:
Except for Infoprint Central
The AOPADMIN group must have permission to write to the specified trace directory, and the trace directory must exist.
For Infoprint Central
The user ID of the user who starts the IBM® HTTP Server - Powered by Apache must have permission to write to the specified trace directory, and the trace directory must exist.
Example: AOPTRACEDIR=/mydirectory/trace
AOPTRACEMAXFILES
Specify the number of trace files to be kept for each instance of a process. This environment variable is optional. The default is 2 per process. If the number of trace files exceeds the number you specified, Infoprint Server deletes the oldest file. Each time that you stop and restart Infoprint Server, it resets the number of trace files for each daemon.
Example: AOPTRACEMAXFILES=5
Tips:
  1. If you want all trace files to be created in the same directory, either do not specify the AOPTRACEDIR variable (all trace files are created in the default directory), or specify the same directory in both the aopstart EXEC and any other process you are tracing.
  2. To find out whether the AOPTRACEON variable is set in the z/OS UNIX shell, use the z/OS UNIX export and grep commands to look at the value of the AOPTRACEON variable:
    export | grep AOPTRACEON
     
    Results:
    • If AOPTRACEON is not set, the export and grep commands do not return any output.
    • If AOPTRACEON is set, the export and grep commands return the AOPTRACEON value or AOPTRACEON="".