Table of Contents
Advertisement
Performing Routine Spooler Operations Using
Spoolcom
Table 14-7. Common Printer and Spooler Problems (page 2 of 2)
Problem
Jobs fail to print.
Possible Causes
A printer is down, offline, or
in an error state.
The spooler subsystem is
hung.
A print process is down or is
in an error state.
A paper jam has occurred.
An invalid (Job -1) state has
occurred with a given device.
A user sent a file to a dummy
or nonexistent location (or put
it on hold).
FORM attributes of the job
and the device do not match.
The spooler supervisor process
is down.
The job command fails to take
effect (jobs hang).
Guardian User's Guide —425266-001
14 -37
Problem-Solving Summary
Solution
Drain and restart the device in
question, or manually put it online.
Drain the spooler and perform a
warmstart.
Check configuration, restart the print
process, and check device status.
Suspend the printer, physically fix the
jam, and restart the printer.
Drain the device and restart it. If
problems persist, drain and warmstart
the spooler.
Reroute the job to an existing printer
or take the job out of the hold state.
Reroute the job or change the FORM
attributes.
Check for error messages, stop any
running collector or print processes,
drain the spooler, and warmstart the
spooler.
Check with your management: a
memory dump of the supervisor
process might be needed.
Advertisement
Table of Contents
