I've found in the past that the connection can drop during the stage when it's transforming the spooled file from SCS to ASCII. This stage is, or certainly used to be, very, very s-l-o-w. The solution is to use 2 output queues. The first one points to the second with transformation to ASCII. The second, which is on the same AS/400 as the first, points to the remote with no transformation. That way there's no long delay between the AS/400 and the remote device - as soon as the ASCII spooled file goes into send it starts streaming data. Clunky, but it works. Dave Kahn Johnson & Johnson International (Ethicon) France Phone : +33 1 55 00 3180 Email : firstname.lastname@example.org (work) email@example.com (home) -----Message d'origine----- De: firstname.lastname@example.org [mailto:email@example.com] Date: 06 October 1999 04:37 À: MIDRANGE-L@midrange.com Objet: Re: Help - Weird error with TCP printing & HPT We had a similar problem with "large" spool files. The typical reports are <50 pages, after that, the windoze spool manager would not provide feedback to the AS/400 and the 400 would think that the connection was lost. +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.