RE: TCP Printing problem

["AS400 Admin" <as400admin@xxxxxxxxxxxxx>]

I wouldn't blame IBM only.

IMHO this is a configuration issue, born from a certain context. For small
shops with IP only printing, it works well. Not the same in more
sophisticated setups, with several players involved - direct IP, Jet cards,
other IP emulator cards, SNA, IPX ...

Another cause is the multiple control and override control. A printer
defined as *DEV is controlled by the AS/400, is also controlled by some
manufacturer software (let's say HP direct) and is also controlled by
itself. All controls should be synch (COMM values, buffers, timeouts,
warnings, flags, auto continues, tray swaps and other animals) but in many
cases this is impossible. So, when a big AS report drops with a networking
bug message (cause: 22, by ex), why to blame only IBM?

On the other hand, a printer defined as *RMTOUTQ leaves away the AS/400
control and the results are much more stable. You lose some facilities, as
page range, but here come the fancy utilities like Brad Stone's SPLTOOLS.

To make a long case short: in our case, after a lot of time waste, the fine
tune is finished the best we could, with 95 % stable results. Not to forget
that we have 150+ printers, 4 AS/400 and dozens of servers of all nature,
all is networked and everybody prints everywhere w/o any restriction.


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 John Hall
Sent: Tuesday, June 27, 2000 10:22 AM
To: MIDRANGE-L@midrange.com
Subject: Re: TCP Printing problem

So it just doesn't work right yet ?????

How is it IBM can't figure out how to send a spool file to a printer
????

Is anyone able to print several hundred page reports on IP attached
laser printers consistently without any problems???

To borrow from a frequent poster on this list - This Sucks

John Hall
Home Sales co.


AS400 Admin wrote:
>
> John
>
> Same problem for 150 + printers, defined as *DEV. It does not happen 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
+---
| 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
+---