*** Retransmission ***
Nous avons eu un problème de distribution de votre courrier électronique
Nous vous le transmettons à nouveau
PS: Ne pas tenir compte de ce message si vous l'aviez déjà reçu.
Merci
Eddy Beliveau, Ecole HEC, 514-340-6073, [log in to unmask]
We recently acquired a dozen LaserJet 4000s for multi-use deployment in
various offices. They are setup for printing with a Novell queue (for
desktop access) and TCP/IP (for HP-UX and MPE network printing). They
work fine from Novell, and HPUX works fine (configured with JetAdmin as
a LaserJet 5M, using net_lj4x driver). Configured them on MPE as
network printers (bear in mind we have two operational printers, a LJ4+
and a 640D). They seem to speak some new variant of PJL which confuses
the network spooler, with the end result that header pages are printed
over and over, the spooler thinking the printer was unsuccessful in
printing the page. I have a call into the HPRC but I doubt this is
going anywhere until somebody digs into the network printer driver
(which is probably unlikely, even though this is a bona-fide and
thoroughbred HP-system-to-HP-printer problem).
The console messages associated with the error go like this:
(MANAGER.SYS): 11:51/134/Output spooler, LDEV #270: Started.
fcopy from=;to=*out11:51/#J4/219/<ESP-> *** ESP scheduling activated
HP31900A.05.02 FILE COPIER (C) HEWLETT-PACKARD CO. 1990
*200*WARNING: FROMFILE RECSIZE IS 80 BYTES, TOFILE RECSIZE IS 132 BYTES.
CONTINUE OPERATION (Y OR N) ?
11:51/#J4/219/<ESP-> *** ESP awaiting work
Testing printer in Business Office from hp3000
< CONTROL Y >
1 RECORD PROCESSED *** 0 ERRORS
11:52/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS JOB
START
NAME="HP3000 FILE=O1 COPY=1
Native Mode Spooler message 9621
11:52/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS PAGE
1
ID=
Native Mode Spooler message 9621
11:52/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS JOB
END
NAME="HP3000 FILE=O1 COPY=1 H
Native Mode Spooler message 9621
11:53/134/Output spooler, LDEV #270: The IPCRECV intrinsic reported
error 64 while waiting for a generic event completion. The error text i
REMOTE ABORTED THE CONNECTION. (SOCKERR 64)
Native Mode Spooler message 9646
11:53/134/Output spooler, LDEV #270: Device has reported a power failur
other interruption while outputting the header for SPOOLID #O1. The spo
will reprint the header.
Native Mode Spooler message 9029
11:53/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS JOB
START
NAME="HP3000 FILE=O1 COPY=1
Native Mode Spooler message 9621
11:54/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS PAGE
1
ID=
Native Mode Spooler message 9621
11:54/134/Output spooler, LDEV #270: The PJL information returned from
the printer contains a syntax error. The first 52 (max) bytes are shown
@PJL USTATUS JOB
END
NAME="HP3000 FILE=O1 COPY=1"
Native Mode Spooler message 9621
abortio 270
(MANAGER.SYS): 11:54/134/Output spooler, LDEV #270: The file system rep
device error
during header processing.
Native Mode Spooler message 9539
11:54/134/Output spooler, LDEV #270: FDEVICECONTROL error.
Native Mode Spooler message 9547
11:54/134/Output spooler, LDEV #270: Error while waiting for printer
to process all data during end-of-job.
Native Mode Spooler message 9638
11:54/134/Output spooler, LDEV #270: I/O aborted by user command.
Native Mode Spooler message 9593
11:54/134/Output spooler, LDEV #270: The spooler could not complete
output of file O1.OUT.HPSPOOL.
Native Mode Spooler message 9511
11:54/134/Output spooler, LDEV #270: Stopped.
console 20
CONSOLE HAS BEEN SWITCHED FROM LDEV 218 TO LDEV 20 .
(MANAGER.SYS):
The last messages of course are where I aborted the output (enough
headers already). Initially the output spoolfile numbers were into five
digits, so I tried a :setcounter in case the #O number was too large,
but as you can see it made no difference.
I suppose I could disable page level recovery (and thus PJL) but that
isn't really an attractive option.
Jeff Kell <[log in to unmask]>
|
