Only the NetView daemons are set up to core into /usr/OV/PD/cores. The
user GUI will always coe into the home directory of the user who started
the process. If the coring process is ipmap or ovw_binary, you could
format the nettl logs,
netfmt -f /usr/OV/log/nettl.LOG00 > formatted.LOG00
netfmt -f /usr/OV/log/nettl.LOG01 > formatted.LOG01
to see if there is more information available about what happened. Then
you will need to run the
utility to get a stack trace. The utility requires you to have dbx
For ipmap, the problem is almost always a bad/incomplete object in the
database, which, once removed, clears everything up. I doubt there is
anything you can do about a core in ovw_binary except call Support. I
suspect the same is true for an Nways core.
Tivoli (NetView for UNIX) L3 Support
Dror Katzman <zdror AT IL.IBM DOT COM> on 12/24/98 07:12:56 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)
Subject: nv gui fails
aix 421+ nv51 + nway 122 on 43p,512m,1 giga ps, df is ok .
Every once in a while NV gui disappear on us and a core dump is
created (not in /usr/OV/PD ... but in user home directory )
We can not recreate the problem and it is unpredictable .
The last time it happened , the core showed
and the other time it was ovw_binary .
I can not recreate the problem , it happens once a day .
The last time it occured was when I was working with ipmap .
Did not see anything in errpt ,
The problem is only with NV gui , the dtterm were ok .
Did any body experience it ?