|
Thanks Charles. I have been using PRTERMSG(*INFO). Works OK, as long as the cause is dealt with promptly. Multiple systems feed a lot of printers here. Another system is HP, and it does not seem to have issues with the writer shutting down.
John McKee
-----Original message-----
From: Charles Wilt charles.wilt@xxxxxxxxx
Date: Tue, 19 Jul 2011 06:59:21 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: Activation timer setting on 3812 Lexmark
Check PRTERRMSG--
http://www-912.ibm.com/s_dir/slkbase.NSF/0/00e3c3d5af21afa6862565c2007d437f?OpenDocument&ExpandSection=4#_Section4
Printer Error Message (PRTERRMSG)
This defaults to *INQ. For the R410 operating system and above, this
should be set to *INFO so the printer's message queue will receive
informational messages whenever possible. If this is set to *INQ and a
problem occurs on the printer (for example, out of forms or a paper
jam) a message will be sent to the printer's message queue that must
be answered before printing can continue. Often, this can also cause
the writer to end while in the middle of a spooled file.
HTH,
Charles
On Mon, Jul 18, 2011 at 2:51 PM, Jack Kingsley <iseriesflorida@xxxxxxxxx> wrote:
Are your sleep timers turned on, on the printer.--
On Mon, Jul 18, 2011 at 2:28 PM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote:
We are on V5R4. There are a number of printers attached as 3812 devices.--
None are AFP(*YES).
The writers end periodically. I have seen this happen due to jams as well
as out of paper. May be other issyes.
I thought I would look at the activation timer setting. One printer is set
to 170. Thought I might try increasing that value.
The help text states:
"Note: *NOMAX is valid only when DEVCLS(*LAN) and
AFP(*YES), or when are specified."
What does help state for current versions? Looks like something is missing
in that text, which I have checked twice for accuracy.
Is there any way I can keep the writer from ending when a printer is
ignored for an extended period of time?
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.