Subject: | |
From: | |
Reply To: | |
Date: | Thu, 5 Sep 2002 10:42:06 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I checked the archives on this problem and found nothing on it.
Thanks to Cory Black for responding that they have a similar
problem. He gets around the problem (sort of) by running a
job every morning that does a STOPSPOOL and then
STARTSPOOL. Anyone else run into this? One of the
printers is serial on an Axis print server and the other is
parallel on a Jetdirect print server.
>This behavior began since we migrated from a 927LX 6.5 PP2 to
>an A400/110 7.0 Express 1.
>We have 2 network printers in the computer room that are only used
>to print from the HP 3000. What they've started doing on a sporadic
>basis is stop printing at the end of one spoolfile ... usually there are
>no more to print at that point ... then when more print files are
>available to print, nothing happens. It looks like it should work
>Doing a SPOOLER 1006;SHOW indicates that the spooler is up and
>running, but idle. The print files do not have a 'D' by them, so they
>don't appear to be deferred. The outfence is low enough for the
>spool files to print. Trying a startspool just tells me it is already
>spooled (which is what I would expect) and a resumespool won't
>resume it (which is what I would expect). Then, in experimenting,
>I tried doing a SPOOLF;UNDEFER, and that worked!
>So what is going on?
>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 *
|
|
|