z/OS Infoprint Server Messages and Diagnosis
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Starting the Generalized Trace Facility (GTF)

z/OS Infoprint Server Messages and Diagnosis
GA32-0927-00

Starting the Generalized Trace Facility (GTF)

You must start a GTF trace before starting a NetSpool external trace. When you start an external trace at NetSpool initialization, start GTF before starting NetSpool. NetSpool writes trace output to the GTF trace data set.

When you start GTF, specify these GTF parameters:

  • The USR=(FAC,FD2) parameter

    Specify this parameter with two event identifiers (FAC and FD2) to obtain these trace entries:

    • FAC causes NetSpool to trace the input data stream, end-of-file rules, data set allocation parameters, and so on. The NetSpool user or system programmer can use this trace information to diagnose problems related to the input data stream or to attributes defined in the Printer Inventory for a NetSpool printer LU.

      To obtain this trace information, also specify the LUNAME parameter either in the NetSpool trace options data set or on the MVS™ MODIFY command you use to start the NetSpool trace. If you know which LU is failing, specify the LU name in the LUNAME parameter to limit the amount of trace information and make the trace easier to read.

    • FD2 traces causes NetSpool to trace program control flow, control blocks, and so on. This trace information can help diagnose many types of problems.
  • The JOBNAME=proc_name parameter

    Specify this parameter to limit the trace entries to those produced by tasks running in the NetSpool address space. proc_name is the name of the NetSpool startup procedure.

For an example of how to start GTF, see Starting the Generalized Trace Facility (GTF).

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014