RE: TCP Printing problem

["AS400 Admin" <as400admin@xxxxxxxxxxxxx>]

John

Same problem for 150 + printers, defined as *DEV. It does not happe for
*OUTQ. Affected are all our HP, Lexmarks & Canons.

Creating a *PSFCFG object linked to the writers description helped in a way,
but didn't avoid all miseries. We ended up with a combination of *DEV and
OUTQ for the printers, depending on their use.


Andrei Centea
Sara Lee Branded Apparel of Canada (Canadelle)
Montreal




-----Original Message-----
From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On
Behalf Of Lemen, George (Contractor)
Sent: Monday, June 26, 2000 3:11 AM
To: 'Midrange-L'
Subject: RE: TCP Printing problem

John --
 I hit the same problem with an HP4000 and an HP5 (with internal JetDirect).
 In my case, the problem cropped up when the printer had been sitting for a
while and had to "warm up" before it would print. On the internal jet-direct
cards I also got the problem if another host was printing a BIG document
(read lots of images etc or in some cases just plane long (> 300 pages)).

 I wound up making sure I named all the printer devices with someing in
common on the front end of the name and putting an auto-reply in the system
reply list for the message (CPU403D) looking for that common "front part" of
the device name.  I also tried setting the "inactivity timer" value higher
(I think I spotted this in the "Printing V" redbook). Setting the timer up
helped reduce the incidence of problems but didn't totally eliminate it.
I've had to do this on V4R2 (be SURE you have the group TCP/IP PTF installed
if you are that far back) and V4R4.

Good luck!

************** copy of original message for reference ********

>Date: Fri, 23 Jun 2000 19:18:15 -0400
>From: John Hall <jhall@hillmgt.com>
>Subject: TCP Printing problem
>
>I just converted an HP4000 from a rmtoutq a *lan printer (crtdevprt)
>
>Now when we print large reports we get communication errors on the
>writer.  CPA403D Operator Action required on Device (C R).
>
>We never had this problem before.  The printer has a built-in network
>card and is shared by the 400, NT servers, and a Unix box.  If I go back
>to a rmtoutq the problem goes away.
>
>Any Ideas?
>
>John Hall
>Home Sales Co.
___________
George Lemen
Sr. Project Analyst, CIBER Inc.
Weyerhaeuser CER Operations Manager
Weyerhaeuser phone: (253) 924-7648; E-mail: George.Lemen@Weyerhaeuser.com
CIBER phone and voice mail: (425) 451-2575 extension 142; E-mail:
glemen@ciber.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---