Hi James,
I understand what you want to say. And I don't think there is a need to change
all the netview code to get it working for different languages - english should
be OK for every network responsible.
All I wanted to say regarding the "bug" is that someone at tivoli/IBM already
thought about this LANG problem, but made a little mistake.
If you look at /etc/netnmrc, it is obvious that
----------------------------------------------------------------------------------------------------------------
if [ "$LANG" = "C" ] || [ "$LANG" = "" ] ; then
LANG=En_US
export LANG
fi
----------------------------------------------------------------------------------------------------------------
won't work for most LANG values as it should.
Here my patch:
----------------------------------------------------------------------------------------------------------------
# Force LANG to En_US, regardless of user defined value
LANG=En_US
export LANG
----------------------------------------------------------------------------------------------------------------
and everything will work fine.
Thats all. For us users it's a bug, for you not, as no one reported it.
So long
Michael
>>> James Shanks <James_Shanks@TIVOLI.COM> 16.02.2000 16.42 Uhr >>>
Michael -
Not being involved in any of your implementation issues in the past, I did not
mean to get you excited about them. It is not my intent to rub salt in your
wounds or belittle your problems. I am as sorry as anyone can be that the
product does not do what you want. And I am sorry for your December 30th
problem as well, but not being involved in that, I don't have anything helpful I
can say about it. And I am not surprised that hiring an outside top gun for
UNIX could not resolve your problems. If the code could be easily modified by
someone who knew little about its internals and no access to the source, then it
would really surprise me.
But the reason I asked you if you reported your "bug" , is this. NetView for
UNIX is certified as requiring En_US on AIX and no other English environment.
Period. Thus it is not a bug, I think, but a an enhancement request, to have
another language environment supported. This would be no different than adding
German or Spanish. Even without translation it requires a great deal of work
to alter the product to add new message catalogs and to then verify that no
other components require matching changes as you seem to have discovered with
snmpCollect.
I am sorry you had so many problems but the real issue seems to be that your
concerns did not reach the right people, and I don't know why not. I cannot
answer for that. If you want to revisit any of your issues with your marketing
rep as customer satisfaction issues, or reopen them with calls to official
IBM/Tivoli support, so they can be looked at by NetView Level 2, please fee free
to do so.
All I wanted to do was to point out that the issue gets confused by calling it
a known bug, when in fact there is no official record of it and no plans to fix
it. If you want a bug fixed, you have to report it. If the official result of
this report is that this issue is in fact a design change, an enhancement, then
you will have to ask that a formal enhancement request be opened and have
development address it in a future release.
That's the only point I was trying to make.
James Shanks
Tivoli (NetView for UNIX) L3 Support
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
|