James
Thanks for your prompt reply again - do you ever sleep???
I do not exit the rule editor during these sessions as it is so slow to start
up on this development system - I only do a file|save and leave the editor
open. The problem won't be due to others playing with the files as I am the
only person with access to the system and am the only NMS person in the
company, such are the "benefits" of modern management principles.
I did notice that there are a lot of the temporary files lurking in the rules
directory - I presume that it is OK to remove these to clean things up.
Your point about the slowness of the system is well taken. Although my
production Netview platform is a nice fast AIX box with 2GB of RAM my
development box is a RS/6000 E30 with a paltry 256MB RAM and I am accessing it
from a Sun box across a 2MB link - maybe I can use this as a good excuse to
bump the link speed up from 2MB to something more respectable, say 155MB ATM
perhaps and get some grunt into the dev box!.
Thanks for the note about the "Refresh Layout" option, I will try this and see
how this goes. I presume the refresh uses the DASD based file as the source and
updates the GUI from the files version of the rule and not vice-versa.
Cheers from sunny Oz - Gavin
>>> <James_Shanks@tivoli.com> 02/08/2000 22:44:01 >>>
Hmmm. I don't know exactly why you had this problem, but the ruleset editor GUI
is an X-application, and as such it can take awhile to update. I have seen
cases where people have made changes to complex rulesets accidentally and then
exited before the GUI could catch up and re-draw what they had done, and so of
course, their changes were saved unwittingly. But for six nodes, I am mystified
as to how this could occur. However, there is an easy way to avoid the problem.
Just pull down the "Edit" menu and select "Refresh layout" before you exit. On
the refresh, the file and the GUI are synched, so what you see before you leave
is what you get.
You might also notice that the way the thing works under the covers is that when
you start your edit session of an existing rule, it makes a backup copy of the
ruleset "xxxx.rs.BAK" and also a temp copy "xxxx.rs.<random_chars>". The
temp copy is, or should be, erased, if you save your changes and exit the GUI
normally. If you cancel the edit session it stays around, just filling up the
directory. On the next edit, the old BAK file is removed and the current rs is
used to make a new one. If that didn't happen, or if someone played re-name
games after the last edit, you could get your old version back. Just a thought.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Gavin Newman" <NEWMANGJ@stgeorge.com.au> on 08/02/2000 02:43:11 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Ruleset - refreshing
Re my previous posting whereby changed rules were not being used in a dynamic
workspace....
I looked at the rule file in /usr/OV/conf/rulesets and noticed that the action
that I had deleted using the GUI is still there event though it is not on the
GUI display! This is a simple test rule with only 6 elements so I know it is not
hidden off the screen.
If I make changes to the contents of one of the existing rules they are
reflected in the dataset but I cant work out how to get rid of this recalcitrant
action node from the file given that it is not on the GUI.
Can I delete it manually? Why was it not deleted when I deleted it from the GUI?
Cheers - Gavin
PS : I just noticed that if I close the GUI & reopen it the rule now contains
the deleted action ode that wasn't there before but was in the rule on DASD. I
then deleted it through the GUI and it worked properly this time. Is there some
problem with the rule editor GUI here?
**********************************************************************
***** IMPORTANT INFORMATION *****
This document should be read only by those persons to whom
it is addressed and its content is not intended for use by
any other persons. If you have received this message in
error, please notify us immediately. Please also destroy and
delete the message from your computer. Any unauthorised form
of reproduction of this message is strictly prohibited.
St.George is not liable for the proper and complete transmission
of the information contained in this communication, nor for any
delay in its receipt.
**********************************************************************
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
**********************************************************************
***** IMPORTANT INFORMATION *****
This document should be read only by those persons to whom
it is addressed and its content is not intended for use by
any other persons. If you have received this message in
error, please notify us immediately. Please also destroy and
delete the message from your computer. Any unauthorised form
of reproduction of this message is strictly prohibited.
Bank SA is not liable for the proper and complete transmission
of the information contained in this communication, nor for any
|