• Subject: Wierd CA Printer problem
  • From: Larry Bolhuis <lbolhui@xxxxxxx>
  • Date: Fri, 23 Jul 1999 09:14:25 -0400
  • Organization: Arbor Solutions, Inc

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

-- 
Larry Bolhuis         | Trivia Question: What famous car carried
Arbor Solutions, Inc  |  the tags:   BDR 529 ?
(616) 451-2500        |
(616) 451-2571 -fax   | Two rules to success in life:
lbolhui@ibm.net       | 1. Never tell people everything you know.
+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].