Re: Printing problem on V4R5

["Jeffrey Silberberg" <jsilberberg@xxxxxxxxxxxxxx>]

UPDATE !!!

            I had problems with a 4317 at COMMON HQ this week that worked
fine off the 50S V4R3 but would not
print duplex for us off the V4R4 720.  After Fred Pritchard and I identified
and applied a number of PTF's that are
not on the CUM tapes yet, and got them applied these and some other TCP/IP
printing issues went away..

        JMS...

PS:  Today is the Last day to VOTE in COMMONs 2000 board elections.  Please
participate and vote !!!


----- Original Message -----
From: <bdietz@3x.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, September 15, 2000 7:33 AM
Subject: Re: Printing problem on V4R5


>
> Make sure you  have created the device correctly.  A goo example is here:
>
http://as400service.rochester.ibm.com/s_dir/slkbase.NSF/$searchform?Open&vie
w=wall
> Search for CRTDEVPRT
>
>
> Bryan Dietz
>
>
>
>
>
>                     Ken.Slaugh@cm-inc.c
>                     om                         To:
MIDRANGE-L@midrange.com
>                     Sent by:                   cc:
>                     owner-midrange-l@mi        Subject:     Printing
problem on V4R5
>                     drange.com
>
>
>                     09/14/00 10:43 PM
>                     Please respond to
>                     MIDRANGE-L
>
>
>
>
>
>
> 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 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 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
+---