Method 2
147
Because LineJet printers are typically connected to the network with a Print
Server internal network card or JetDirect EX interface, many of the spooler
commands (e.g., those described above) should be avoided for mid-file
suspension. This is because of two reasons: 1) a great deal of data is
buffered in the network process and must be completed, and, 2) the network
connection can be dropped if the printer is ready to receive data but no data is
being sent. (Refer to the
HP e3000 MPE/iX Native Mode Spooler Reference
Manual
.)
Restarting at the point of interruption when a device
exception occurs
When a device exception occurs, this is an unexpected recovery situation. A
device exception includes things such as paper jams, load paper error, etc.
Assume that the LineJet printer is connected to the network with a LineJet
Print Server internal network card or an “external” JetDirect EX interface. In
order for PLR (silent run) to take place after a device exception and without
specifying spooler commands to restart, the printer
must
be power cycled
(e.g., after the jam). This is different from the way it may work with other HP
printers that support PLR and use an “internal” JetDirect interface. This is also
different from the way it works with the C256X printers that use the HP-IB
interface. This caveat may be one of the reasons it appears that PLR does not
work for LineJet printers. Note that printing will start with the page following
the last one printed.
Restarting at the point of interruption when a particular
spool file is reprinted after being interrupted previously by a
command
In this case, a spool file is reprinted after being interrupted by a command
such as
spoolf #0
nnn
;defer. For LineJet printers, when the spool file
is undeferred, after being interrupted with the deferred option, a silent run
(PLR) will occur up until the page following the last one printed.
A spool file can also be interrupted with the
spooler ldev; stop
command, but this command should be avoided for a LineJet printer
connected to the network with the JetDirect EX or internal Print Server
interface. This is due to network printing problems with stopping mid-file
server.
