You didn't say if we were talking remote or local printers. With the newer operating system and newer machines the bus actually pushes the jobs through faster...they check if the printers are there frequently, and if there is a signal that it is out of paper, or jammed, it gets tired of asking if the printer is there, so it brings the que down...This is really what it is supposed to do....
Printers are meant to timeout when it runs out of paper...the que goes down and
when it is restarted it starts from the beginning of the job. If it is a remote printer
You can increase the time of the timeout....
Timeout of Printers, what to do?
If the queue is defined as a remote printer with standard processing (backend is rembak), adding -T60 to the backend line in /etc/qonfig may help. If the queue is remote with local filtering, then -T60 can be put into the rembak flags section of /usr/lib/lpd/pio/etc/piorlfb. If the queue is defined using the HP Jetdirect software (piojetd backend), then -T60 doesn't apply.
lp0:
host = hostname
s_statfilter = /usr/lpd/aixshort
l_statfilter = /usr/lpd/aixlong
rq = queuename
device = dlp0
dlp0:
backend = /usr/lpd/rembak -T99
cp /usr/lib/lpd/pio/etc/piorlfb
/usr/lib/lpd/pio/etc/piorlfb.orig
# vi /usr/lib/lpd/pio/etc/piorlfb
typeset piorlfb_rbflags="-T99" #rembak flags
----------------------------------
I do not believe there is much you can do with local printers......If you do have a job that is like checks or something....normally you set up a separate que....disable the que so the job goes there...and when you are ready to print it......you make sure there is plenty of paper, and then enable the que...........
Not sure if that helps you or not?