RE: remote outq problem

["Art Tostaine, Jr." <art@xxxxxxxxxxx>]

Lou:

Does it only happen with large reports?  If the writer is Host Print
Transform(*YES), the 400 will convert the whole spool file to *Ascii (or
something else I'm not really sure of) before it starts to print.  That
should take awhile.

BTW, who in the world would want to print a 1000 page report much less read
one?

Art Tostaine, Jr.
CCA, Inc.
Jackson, NJ 08527


-----Original Message-----
From: midrange-l-bounces@midrange.com
[mailto:midrange-l-bounces@midrange.com] On Behalf Of Lou Schmaus
Sent: Thursday, January 30, 2003 5:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: remote outq problem

Paul,

All the remote outq setups have XAUTOQ and XAIX in the destination options.
It's a habit we picked up long ago when dealing with dot matrix printers on
print servers. I've just never seen it this bad before. I've ended the outq
in question, walked out on the dock, verified the printer was online and had
paper, turned the print server and printer off and on again just for good
luck, walked back to the office, started the writer back up, and the spool
file still goes to 'SND' and stays there. Then, half an hour later, the
printer starts.

I added quite a bit of memory to the *SPOOL pool, and increased the number
of active jobs in the pool, and I'll see if that has any effect. It would
not be unusual for this location to have over 20 printers running reports at
once, with one or two of them being huge multi-1000 page reports.

--------------------------
Lou Schmaus
MIS Director
Apparel Distribution, Inc.
lou@appareld.com