This isn't as difficult as you might think.
Basically, you must distinguish between what is official and what is not.
NetView 5.1.1 is a maintenance level on top on NetView V5.1. That is the
latest official level. It has been through system
verification and is generally available to all customers. Fixes on top of that
would be what we call "e-fixes" ("e" for
"emergency"). These have not been through verification and are not official.
At the time you obtain them all that can be
said was that they fixed a similar problem on the box of the engineer who built
them. Nothing in an efix is guaranteed. You
get them by calling Support. They are not on any public site nor publicized
precisely because they have not been through
system verification. Level 2 will tell you how to get them if you really need
them, but until they are tested and rolled up
into a new maintenance level, they are not official.
As time goes on, and Level 2 hands out more and more efixes, they get paranoid
about what level of code the customer is
running, hence you may get asked several times about that.
NetView 5.1.1 is not at ftp.tivoli.com because it is huge. It contains dozens
of fixes and so cannot be shipped that way.
Thus you get it on a CD. If there ever comes a time that NetView fixes get
system tested one at a time, then you may see
them out there. But not today.
As for your specific problem, 5.1.1 fixed a loop problem in the V2 loader,
xnmloadmib2, (APAR number is IX80310). If you
were using xnmloadmib, and not xnmloadmib2, then you may have an entirely
different problem than what was fixed.
If, by chance, you have your corrupted database somewhere as a backup, or you
know how to re-create the problem, then
please call Support back and tell them that you would like to pursue that. If
they can get your database from you, and get
it to hang on their box, then we have a consistent problem that can be debugged
and fixed. Otherwise, the only thing I can
say is what you already know -- be careful what you load and make sure it works
correctly. If the thing dies or you cancel
it in mid-operation, then corruption is a possibility. Sorry if that seem
lame but that is the best I can offer you.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Chris Cowan <chris.cowan@2ND-WAVE.COM> on 06/21/99 03:18:53 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: Loading a MIB takes excessive machine resources
James Shanks wrote:
>
> Well, Chris, you cannot see it but there are dozens of error messages in
> xnmloadmib and xnmloadmib2 but they will never see
> the light of day if the code loops trying to read your database. A loop is a
> loop is a loop, and by definition if you
could
> break out of it, you wouldn't be looping. That's what I fixed (or at least
> tried to) in the fix I referred to. So unless
> you get the latest level and re-create your hosed database, we will never
> know if my latest attempt to keep this from
> happening was successful or not. That is why I advised you to get it.
>
> I think parsers that loop and don't give you messages are bad too
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
For the record, I updated to NV 5.1.1. I do not have any 5.1.1 patches,
although I asked several times if there were in fact any. (Still
wishing that they were consolidated with the rest of the Tivoli code at
ftp.tivoli.com!!!) 5.1.1 was just as terse as 5.1.
The Customer Support guy and I became suspicious because he was able to
load it on 5.0 and 5.1.1. And I had problems with both 5.1 and 5.1.1.
I may still have the hosed DB, and could restore it for testing. Is
there in fact, a fix to 5.1.1 or are you talking about 5.1.1
specifically?
chris.cowan.vcf
Description: Binary data
|