Re: OUTQ question

There could be a relationship between timeout on the printer and the
keep-alive setting on the 400. Here's something from the Knowledge Base
<http://www-912.ibm.com/supporthome.nsf/document/10000051>

>Timeout Settings on the Printer
>
>On the printer, the processor timer (called job timeout or wait timeout)
>should be disabled or set to maximum (usually 300 seconds) since
>individual pages may have a delay in transmitting to the printer due to
>transforming considerations. This timer controls the amount of time in
>seconds (5-300) that the printer waits before printing the last page that
>does not end with a command to print the page. This timer should not
>affect the execution of this print driver, since we terminate each page
>with a form feed. We could have a case where a partial page is sent to the
>printer's buffer while complex transforming is taking place during which
>this timer expires, thus ejecting an incomplete page.
>
>
>Recommended Timeout Settings for IBM, HP and Lexmark Print Servers
>
>IBM Network Printer and InfoPrint printers:
>
>Set the Port Timeout to 300 (5 minutes). Setting this timeout to 0 does
>not disable the Port Timeout. IBM does not have an external adapter that
>supports this configuration at this time. The port timeout can be set
>through the control panel on the printer
>
>IBM Infoprint 1000 Family Printers:
>
>Disable the Job Timeout by setting it to 0. The Job Timeout can typically
>be set through the control panel on the printer, or it can be set using
>the Lexmark MarkVision Utility. The Lexmark MarkVision Utility can be
>downloaded from Lexmark's Web site, http://www.lexmark.com/.
>
>HP JetDirect cards/print servers:
>
>Set the IO Timeout (or Job Timeout) to 300 seconds (5 minutes) and set the
>Idle Timeout to somewhere between 900 seconds (15 minutes) and 3600
>seconds (1 hour). Setting the IO Timeout (or Job Timeout) and Idle Timeout
>to 0 does not disable them. It causes the printer and/or print server to
>timeout immediately. The IO Timeout can typically be set through the
>control panel on the printer, or it can be set using the HP JetAdmin
>Utility. The Idle Timeout can be set by TELNETing to the IP address for
>the printer, or it can be set using the HP JetAdmin Utility. The HP
>JetAdmin Utility can be downloaded from HP's Web site, http://www.hp.com/.
>
>Lexmark MarkNet cards/print servers:
>
>Disable the End of Job Timeout or Job Timeout by setting it to 0. The End
>of Job Timeout or Job Timeout can typically be set through the control
>panel on the printer, or it can be set using the Lexmark MarkVision
>Utility. The Lexmark MarkVision Utility can be downloaded from Lexmark's
>Web site, http://www.lexmark.com/.
>
>TCP/IP Keep-Alive Value on the OS/400 System
>
>The printer will close the socket if the printer has not processed any
>communication from the host within the LAN adapter's timeout limit (from
>step 1). This can happen if the printer has a large buffer, and it is
>filled with data to print. To prevent this from happening, the TCP/IP Keep
>Alive value OS/400 should be set to a value less than the print server's
>timeout value. The TCP/IP Keep Alive value can be changed using the Change
>TCP/IP Attributes (CHGTCPA) command. This will cause a poll to be sent to
>the printer before the printer times out. We want this timeout value to be
>as large as possible to prevent unnecessary network traffic. The
>recommended value if step 1 is done (the 3600 seconds), is 50 minutes.
>

At 09:25 AM 3/8/02 -0600, you wrote:
>Message ID . . . . . . :   TCP3427
>
>Date sent  . . . . . . :   03/08/02      Time sent  . . . . . . :   07:49:08
>
>
>
>Message . . . . :   Remote host system rejected the open attempt.
>
>
>
>Cause . . . . . :   This may have occurred because the remote host does not
>
>   have ports available for use or does not support TELNET.
>
>Recovery  . . . :   Try the request again or contact the system
>administrator.
>
>
>
>On one of our *OUTQ’s  which is a TCP/IP attached printer a 300+ page report
>“coughed”
>And started printing again from page 1. In the writer job I see a few of
>these messages.
>
>Is there anything we can do to prevent this….or is it just caused by network
>traffic.
>Because we tried 10 minutes later…and it worked fine.
>
>Jim Norbut
>Systems Administrator
>Grubb & Ellis Company
>Phone   (847) 753-7620
>Fax     (847) 753-9854
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.