I was playing with this and made another discovery. I was looking at
the spooler file that won't print...because I have this change I was
working on, there is another print file and it too is not printing.

I wondered what would happen if I played with the outfence. It
was currently at 6 and the spoolfile was at 12 with the spooler
and printer idle. I put the outfence up to 13 for that spooled device
and the spoolfile that normally won't print suddenly disappeared.
Checked the printer and nothing printing. Then I put the outfence
back down to 6 and the second spoolfile disappeared, but it did
print.

It is almost as if the printer was waiting to send something back to
the HP to delete the spoolfile because it was done printing (the
previous spoolfile...not the one that wouldn't print). Somehow,
by changing the outfence, it seemed to allow it to receive/act on
the command that the printer was done with the spoolfile. So it
disappeared and now things were back to "normal" and lowering
the fence made any waiting spoolfiles print. Is that strange or what?

The method I was using to stop and start the spooler also saved
the file from getting deleted.

The only thing I question in the programs is that I am sending a
printer reset (Escape E) at the beginning and end of the program.
I don't know why I did that now, since it was so long ago. But
removing the printer reset at the end of these programs had
no effect on the problem.

Anyway, it seems as though it is a communication problem between
the printer and the HP spooler.

Tom
From: Tom Hula
Sent: Tuesday, March 24, 2015 10:29 AM
To: [log in to unmask]
Subject: PCL Code possibly causing print spooler problems?

On 2 different laser printers (P3015, P4015), I get this strange situation.

A job stream generates several print files and they start printing as they
should. But one particular print just sits there in the queue not printing.

The spooler and printer go idle and the spool file is ready to print, but
won't print. I've been getting around the problem by running the following
job to reset the spooler:

!JOB JSPOOLER,BATCH.VSB,PUB;JOBQ=PDQ
!COMMENT  STOP AND START SPOOLER ON DEV 1002
!COMMENT   WORKAROUND BECAUSE TRAVELERS
!COMMENT   ARE GETTING 'STUCK' ON DEV 1002
!SPOOLER 1002;SHOW
!SPOOLER 1002;STOP;NOW;OPENQ
!PAUSE 7
!SPOOLER 1002;SHOW
!SPOOLER 1002;START
!SPOOLER 1002;SHOW
!EOJ

When I run this, the printfile takes off printing. I noticed I getting the
same problem on another printer when I was doing some testing for
program changes requested by a customer. I noted that some programs
that a particular spoolfile that was essentially empty with the exception
of a few PCL commands was taking a long time to print and then the
next file that has the problem was not printing.

I'm thinking that I am the problem...something in the PCL code I'm sending
Is possibly doing this?

Tom Hula
Victor S. Barnes Company

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *