User`s guide

2-55
Printers, Print Jobs, and Queues for Systems Administrators
Printer Queuing System Status Conditions
If a printer/device is added as a tty device, the queuing system looks for carrier detect (CD)
to recognize the printer. If the device is an LP device, the queuing system uses CTS to
detect the printer.
Following is a list of print queue status conditions:
DEV_BUSY Identifies that:
• More than one queue is defined to a printer device (lp0), and another
queue is currently using the printer device.
• qdaemon attempted to use the printer port device (lp0), and another
application is currently using that printer device.
Normal recovery: To recover from a DEV_BUSY, wait until the queue
or application has released the printer device, or kill the job or process
that is using the printer port.
DEV_WAIT Indicates that the queue is waiting for the printer because the printer is
offline, out of paper, jammed, or the cable is loose, bad, or wired
incorrectly.
Normal Recovery: To recover from a DEV_WAIT, you must correct the
problem that caused it to wait. Check to see if the printer is offline, out
of paper, jammed, or loosely cabled. It may be easier for diagnostic
testing to use the enq command to move all queued jobs from the
DEV_WAIT queue to another queue that is either printing or is DOWN.
After the problem is corrected, you can move any unprinted jobs back to
the original queue.
DEV_WAIT can also be caused by improper flow control to the printer,
particularly when using XON/XOFF software control. Use SMIT to see if
you are using the proper flow control (XON/XOFF or DTR pacing).
Bad or improperly wired cabling can cause a DEV_WAIT situation.
Usually, you cannot recover from this situation except by replacing the
cable.
A queue that is in DEV_WAIT for longer than TIMEOUT seconds goes
into a DOWN state. See DOWN for more information on the TIMEOUT
value and the DOWN state.