Since these are AIX X-server errors, are  you talking to them?  Nothing any X
client does, NetView or some other, should cause the server to crash.  They
should have protection in there for that.  So I think two things:
(1) only AIX will have a procedure for debugging the X server to see why exactly
it crashed.
(2) only AIX can provide you with maintenance to prevent it.

As you probably know, NetView  V4 is out of support, but lots of people did (and
some of us still do) run it successfully on AIX 4.2.1.   Do you have the latest
NetView maintenance on?  If not, why not start there?  You have nothing to lose.
Try either
U459387 (server 12/11/98)     U459388 (client 12/11/98)   or the even more
current, U462279 (server 10/01/99)     U462280 (client 10/01/99) .  Once those
are applied, there is no more maintenance from NetView to be had, so then the
problem has got to be with AIX.  Can't they even provide you with a recommended
level of service?  I would also ask them about how to tune your mbufs.

And I thought I did reply in this same fashion the first time you put this out

James Shanks
Tivoli (NetView for UNIX) L3 Support



Abdur Rehman I Mamsa <aimamsa AT NOTES.WEST.RAYTHEON DOT COM> on 11/18/99 
11:36:55 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  X-Server crashes traversing NetView topology




Recently, we've been receiving the following errors from our X-Client processes:
     XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0" after # requests
(# known processed) with 0 events remaining.
     The connection was probably broken by a server shutdown or KillClient.

The entire X-Server crashes. In some instances, we receive the following errors
on the screen after the X-Server shutdown:
     Garbage collection failed.
     1356-815/usr/bin/x11/xinit: connection to x server lost

The "1356-815/usr/bin/x11/xinit: connection to x server lost" error is specific
to the X-Server. We've researched the AIX/X documentation and found that this
error code (815) is a display related, floating-point error.

This problem only seems to occur when a user attempts to open submaps and
"drill-down" through our NetView topology map. We are using NetView ver 4.1 for
AIX ver 4.2.1 and would appreciate any suggestions. So far, we've been told by
IBM that it may be a paging/swap space problem.

(This message was previously posted, with no responses.)

Thank you.
-AR