Tracing considerations

If you are concerned about processor usage, throughput, timing, or storage, you might want to consider:

• Processor usage and throughput

  The full trace affects processor performance. Do not start a full trace during peak processor usage. All other traces affect processor performance, but the impact is not as significant.

• Timing considerations

  Activating any of the traces causes the timing relationships to change. The problems might disappear when tracing is active, especially if a full trace has been activated. If a problem disappears when you are tracing, specify different trace options. For example, limit the tracing to one printer LU.

• Storage considerations

  Tracing each printer LU requires a minimum additional storage of 6 K bytes above the 16 megabyte line. More storage is required if your trace options specify a PAGECOUNT that is greater than one. If you defined multiple printers in the Printer Inventory, you should consider tracing only the printer LUs that are needed to diagnose the problem.