Re: Wierd CA Printer problem -- MIDRANGE-L

We have had that problem as well, since we went from V3R7 (CA version
V3R1M3)
to V4R3 (CA version V3R2).  We received from IBM some PTF's to fix this
problem.
I do not recall what they were, but the scenario was the same as what John
spoke of:
We varied off, and deleted the device description, and it would not
re-create.  The PTF's
had a program to call,  But I think it required an IPL to activate one of
the PTF's.

I have another problem that IBM is not able to fix. It deals with NT
workstations and
HP DeskJet printers, not able to run a printer session.  After Several
rounds of
 "Reinstall CA" and "Reinstall the printer drivers", I gave up.  This
problem cropped
 up early last year, but a service pack fixed it.  Now that we are on V4R3
(CA V3R2)
it has popped back up.

----- Original Message -----
From: Curtis Strouse <curtstrouse@earthlink.net>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, July 23, 1999 9:40 AM
Subject: Re: Wierd CA Printer problem


> Larry,
>
> I have had the exact same problem as you, since we upgraded from V3R7 to
> V4R3.  We are running CA V3R2 on a token ring environment.
> I have been working with IBM on this for many many months.  They keep
> throwing PTF's at me and nothing seems to fix the problem.
> I have found that ending the telnet server and starting it back up or
IPLing
> fixes the problem, but who can afford to do that in the middle of the day.
> So basically to make you feel better, your not alone...
>
> Curt
> North American Stainless
>
> -----Original Message-----
> From: Larry Bolhuis <lbolhui@ibm.net>
> To: Midrange Systems Mailing List <MIDRANGE-L@midrange.com>
> Date: Friday, July 23, 1999 10:14 AM
> Subject: Wierd CA Printer problem
>
>
> >Has anyone seen this:
> >
> > CA V3R2M0 with previous to current fixpack connecting to V4R2 of
> >OS/400.  All connections are TCP/IP on ethernet.  Over thirty stations
> >setup up with multiple sessions and printers. Everything works except
> >ONE printer.  Start the session and you see the gray printer control
> >box appear for about 2 seconds and quits.  Device on AS/400 is vary on
> >pending.  Tried varyoff-same, tried deleting it-it will not come back.
> >Tried a new CA session-same. Changed printer name in original
> >session-it creates and works fine!  Renamed this newly created device
> >to desired name-fails again!  NOTHING in QSYSOPR, DSPLOG, QSYSMSG,
> >WRKPRB and no writer joblog is created.  Attempting to view NETSTAT
> >*CNN during the startup shows no additional sockets being created, or
> >they are gone before I can see them.
> >
> > I truly suspect an IPL or possibly a shutdown/restart of TCP/IP on
> >the 400 will solve this but howcum?
> >
> > - Larry
> >


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