Re: Printing problem on V4R5 -- MIDRANGE-L



Hi Ken,

I've had the same problem with V4R2 and V4R3 (exactly the same error message). I
did originally log a job with IBM and they recommended a PTF. I can't remember
the number because it didn't work anyway. I went back to IBM and they came up
with this :

1) Lower the value of the TCPKEEPALV parameter on the CHGTCPA command. This is
the length of time before the AS/400 sends a poll to any device connected via
TCP/IP (presuming there is no activity). I think the default is 120 secs.

2) Up the TCP/IP timeout value on the printer itself as high as it will go. If
you're using HP printers with JetDirect boxes you can use Jet Admin. Just right
click on the printer and modify. The TCP/IP timeout rate is on about the third
screen as you progress through the little wizard. We now up this figure to 3500
secs for printers that regularly have really large spool files sent to them. Of
course, this may affect printing from applications, although we have had no
problems. We still don't do this to every printer on the network though.

This will not fix the problem 100% of the time, but for us it works 98% of the
time. It is only really large spool files that cause us problems now. (Unless of
course the printer is switched off in the middle of a spool file being
transmitted).

The person at IBM support (in Australia) seemed to think this problem would be
fixed in later versions. As I said I've had the problem at both V4R2 and V4R3,
although I do admit it has gotten better with the later release. I will be
upgrading to V4R4 sometime in the next month or so, so I can let you know
whether we still have this problem. Good Luck!


Thanks

Adam Driver
AS/400 Systems Support Specialist
Star City
Sydney, Australia






Ken.Slaugh@cm-inc.com on 15/09/2000 12:43:31

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Adam Driver/SC/StarCity)
Subject:  Printing problem on V4R5




I'm helping a customer upgrade from V3R2 CICS to V4R5 RICS. TCP/IP seems to
working fine with one exception...

TCP/IP printing fails on three external jet direct devices with the
following joblog message:

Message . . . . :   An error occurred while receiving data.
Cause . . . . . :   A communications error occurred while receiving data
from
  remote device at RMTLOCNAME 10.85.96.217. The error code is 3426. This
error
  can also occur when the system attempts to print to the remote device
after
  it has been powered off and on while the printer writer remains active.

We have been trying to determine why with no success. Does any one have an
idea why or any thing to try? We have tried remote outqs and LAN attached
print devices. Either way results in the same situation.

Ken Slaugh  (707) 795-1512 x118
Chouinard & Myhre, Inc.
AS/400 Professional Administrator/MSE
Client Access Specialist
http://www.cm-inc.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 document should only be read by those persons to whom it is addressed and
is not intended to be relied upon by any other person. Accordingly, Star City
disclaims all responsibility and accepts no liability (including in negligence)
for the consequences for any other person acting, or refraining from acting, on
such information prior to the receipt by those persons of subsequent written
confirmation.

If you have received this document in error, please notify our Helpdesk
immediately by telephone on 61 2 9657 9797. Please also destroy and delete the
document from your computer.

Copyright Star City Pty Ltd. Any form of reproduction, dissemination, copying,
disclosure, modification, distribution and/or publication of this document and
its contents is strictly prohibited.


+---
| 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
+---