MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

Re: Spool file goes to SAV, but doesn't print



fixed

reading the 2nd link from Xerox, it is also recommend hp5si and the user defined option *IBMSHRCNN

I always do the timeout increase, although in my experience that is more about long reports timing out.
I would not rule out something outside system, like a bad switch port or ethernet card in printer. .
Jim Franz




----- Original Message ----- From: "John McKee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, October 17, 2012 10:03 PM
Subject: Re: Spool file goes to SAV, but doesn't print


The first link says to use HP5SI, yet the IBM page I found with Google
states *HP5. I know there are different versions of the IBM page.
What is the difference between HP5 and HP5SI?

Somehow, I got the idea that the first model listed was "better". The
weird problem happened twice last week, but is sporadic. I was wonder
if printer had gone to sleep and took "too long" to wake up, and
somehow managed to send status back to the i that was misleading.
Printer not quite ready, so output not buffered to internal HD and i
determines report was printed when output got discarded. Not
understanding the consequences of making this change, I changed the
inactivity timeout from default of 170 to 300.

Fun, fun, fun.

John McKee

On Wed, Oct 17, 2012 at 8:22 PM, franz400 <franz400@xxxxxxx> wrote:

check this post in 2011 - recommends diff config
http://archive.midrange.com/midrange-l/201103/msg01082.html

however - thius is a whole diff solution from xerox support
www.office.xerox.com/support/dctips/dc04cc0341.pdf

jim franz

----- Original Message -----
From: "Dan Kimmel" <dkimmel@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, October 17, 2012 12:21 PM
Subject: RE: Spool file goes to SAV, but doesn't print


> Spool file goes to SAV without printing when the print writer throws an
> error. Look at the print writer job log for the error. Usually it's an
> unescaped invalid character in the print stream or something to that
> effect, though it can be an error thrown by the printer or the SNMP > server
> on the printer.
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
> Sent: Wednesday, October 17, 2012 11:08 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Spool file goes to SAV, but doesn't print
>
> Not sure what yoou mean by "other side of a WAN connection". Do you > mean
> going through a firewall? If so, then the answer is no.
>
> Current driver for the printer is IBMSNMPDRV. This is a Xerox 3635MFP.
> Manufact type/model is set to *LEXOPTRAT. There is also a wscst used > for
> force drawer 2 for legal size.
>
> John McKee
>
> On Wed, Oct 17, 2012 at 10:55 AM, DeLong, Eric
> <EDeLong@xxxxxxxxxxxxxxx>wrote:
>
>> John, is this device on the other side of a WAN connection? Depending
>> on the quality of the WAN link, you might have better luck avoiding
>> the PJL drivers. I've found that the PJL drivers are not as robust on
>> WAN connections as, for example, SNMP.
>>
>> I've found that most modern print servers appear to support SNMP. You
>> should be able to try this out with a change to the device >> description.
>>
>> Change Device Desc (Printer) (CHGDEVPRT)
>>
>> Type choices, press Enter.
>>
>> System driver program . . . . . SYSDRVPGM > *IBMSNMPDRV
>>
>> Hth,
>> -Eric DeLong
>>
>> -----Original Message-----
>> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
>> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
>> Sent: Tuesday, October 16, 2012 9:00 AM
>> To: Midrange Systems Technical Discussion
>> Subject: Re: Spool file goes to SAV, but doesn't print
>>
>> This is a device, not a remote outq.
>>
>> John McKee
>>
>> On Tue, Oct 16, 2012 at 8:54 AM, Jan Grove Vejlstrup <jgv@xxxxxxxx>
>> wrote:
>> > Do you use a remote outq to do your printing?
>> >
>> > Am 16.10.2012 15:39, schrieb Jack Kingsley:
>> >> Maybe it makes it the printer buffer and then doesn't print. If
>> >> your
>> not
>> >> current on ptf's that could be an issue or maybe the firmware oh
>> >> the printer is old as well.
>> >>
>> >> On Tue, Oct 16, 2012 at 9:25 AM, John McKee
>> >> <jmmckee@xxxxxxxxxxxxxx>
>> wrote:
>> >>
>> >>> The countdown clock on the i is a tad over two weeks, so this
>> >>> issue may not be worth spending any time trying to resolve.
>> >>>
>> >>> I am wondering how a spool file to a device can go to SAV without
>> >>> printing. This happened twice last week.
>> >>>
>> >>> Could be something wrong with the printer, I guess. But, I
>> >>> watched it yesterday and no issues. I changed the activation
>> >>> timer from the default of 170 to 300 a few minutes ago, thinking
>> >>> that the printer had gone to sleep when the spool file was sent
>> >>> and somehow that was enough to have the output get discarded.
>> >>>
>> >>> System has not had PTFs applied in years. Just wondering if this
>> >>> is an issue that IBM fixed years ago and out sa was too uninvolved
>> >>> to deal with.
>> >>>
>> >>> How else could a spool file go from RDY to SAV and not be printed?
>> >>>
>> >>> John McKee
>> >>> --
>> >>> This is the Midrange Systems Technical Discussion (MIDRANGE-L)
>> >>> mailing
>> list
>> >>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
>> >>> unsubscribe, or change list options,
>> >>> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> >>> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
>> >>> take a moment to review the archives at
>> >>> http://archive.midrange.com/midrange-l.
>> >>>
>> >>>
>> >
>> > --
>> > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
>> > mailing
>> list
>> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
>> > unsubscribe, or change list options,
>> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
>> > take a moment to review the archives at
>> > http://archive.midrange.com/midrange-l.
>> >
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
>> unsubscribe, or change list options,
>> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
>> a moment to review the archives at
>> http://archive.midrange.com/midrange-l.
>>
>>
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
>> unsubscribe, or change list options,
>> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
>> a moment to review the archives at
>> http://archive.midrange.com/midrange-l.
>>
>>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at > http://archive.midrange.com/midrange-l.
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact