Re: Abnormal writer end

check the timeout value in the multifunction printer. usually the default is
too small for the way the i talks to the printer.
Check this doc for whats recommended by Rochester on config
http://www-01.ibm.com/support/docview.wss?uid=nas11e61e34f2505754f862566e20051c3de
I have found snmp sometimes works better than pjl.
Jim Franz

----- Original Message -----
From: "jmmckee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, September 29, 2010 8:48 PM
Subject: Re: Abnormal writer end

Thanks for the link. I will show this page to the Lexmark printer guru.
But, also in the joblog as explanation for the reason code was that the
printer was turned off and on while printing.

These printers use port 9100 while printing from other systems. They were
originally set up as remote output queues as they are multifunction
devices. When thry are scanning, faxing, or copying, they discard output
sent via remote output queue (I think that is port 515). Having the
writer end, seemingly at random, is not good. But, better than output
being dropped.

John McKee
-----Original message-----
From: "Jim Franz" franz400@xxxxxxxxxxxx
Date: Wed, 29 Sep 2010 17:47:02 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: Re: Abnormal writer end

http://www-01.ibm.com/support/docview.wss?uid=nas11e61e34f2505754f862566e20051c3de
scan for the 3426 in this doc
Jim

----- Original Message -----
From: "jmmckee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, September 29, 2010 6:07 PM
Subject: Abnormal writer end

A writer ended. The joblog has this: CPD 337A reason code 3426.

The printer is a device, with messages set to *INFO instead of *INQ.

Nothing else in the joblog, such as an unanswered message or a message
that had a C supplied.

Is this behavior a consequence of having messages set to *INFO instead
of
*INQ?

Is there some way to keep the writer running - or have it restart
aumatically when this happens?

The alternative of *INQ won't work well as computer operator rarely
observes messages. Doing other things.

Thanks.

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.