Re: Printing problem on V4R5 -- MIDRANGE-L

Ken,

  Do ANY Jet Direct devices work? If so swap one of the working ones
with a failing one. If the problem follows the device then the problem
is in there, if it stays with the location then there is a network or
TCP/IP Problem.  There may be a device in the network (switch, router,
firewall, etc) that is blocking a port or breaking frames up.

  Are any Other systems able to print to these jet directs?  Jet Direct
devices can accept data from only one system at a time. If another
system has the device locked up then problems will occur.  We have
solved this problem in the past by funneling ALL print jobs for each jet
direct through a single server.

  I have no experience w/ V4R5 yet so can't tell you if there are any
TCP/IP Problems there.

  One possible test would be to reduce the frame size on the network
interface to see if that solves the problem. Note that you probably
won't want to leave it that way but just try it as a test.

  Are you SURE that the devices in question are actually what is
responding at 10.85.96.217? ie check w/ the Jet Admin software with a PC
in the same hub as the AS/400.  Ping is not good enough because it just
says there is SOME device at address 10.85.96.217.  

  Hope I've Helped.

  - Larry

Ken.Slaugh@cm-inc.com wrote:
> 
> 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.

-- 
Larry Bolhuis         |  
Arbor Solutions, Inc  |  IBM AS/400e - Get There First!
(616) 451-2500        |  
(616) 451-2571 -fax   |  It's 10PM.  Has your NT Server had it's
lbolhuis@arbsol.com   |  therapeutic re-boot yet today?
+---
| 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
+---