| I will try to help you with item 1.
The time and date are computed by taking the Greenwich Mean Time (the
Universal Time at the Royal Observatory in Greenwich, England), and
adding the Time Differential Factor (the value of the MCC_TDF logical).
Check the MCC_TDF logical. It should have a time value of hours.
Sometimes people inadvertently set it to values like "-5" or "-4",
which is interpreted at -5 days and -4 days respectively. The correct
syntax would be "-5:00" and "-4:00", to indicate -5 hours and -4 hours,
respectively. If (/when) you set the MCC_TDF logical, make sure you
stop all MCC processes and restart them. This is necessary because MCC
only reads in the TDF value once, when it starts up. Also, the event
pool contains timestamps, and the event timestamps will be off unless
you restart the MCC processes.
-Matt.
|
|
2. Operation can be perform on a list of selected entities. But it
seems that they have to be of the same class and on the same level
(domain), am I right?
You are right, this is how MCC is setup. We allow wildcarding of operations
only as they apply to a specific class (though things like node4 * line *
are accepted as well, since they are confinded ot a single class node4 line).
As to the domain stuff, if you run from the FCL you are confined by the
contents of the configuration if you use a wildcard, unless you also use
the IN DOMAIN=name qualifier. This allows you to constrain the view to
only those entities within the specified domain. From the Iconic map you
are always confined to the contents of a domain. (Note that from the FCL
a wildcard used with an IN DOMAIN means that the wildcard is expanded
down the entire hierarchy for all domains within the domain specified, as
long as the domains were defined as being dynamic domains.)
3. Does it required a DECnet account to register a NODE4 or NODE5?
Due to security reason (INSPECT) some nodes have their DECnet account
removed.
I don't believe so, but you might have to user the BY USER, BY PASSWORD
qualifiers to get around it....someone from the DECnet team should be
able to answer this one.
4. How can I make changes on a defined rules from icon map? And can
I have one rule apply on a number of entities?
Alarms only supports child entity wildcarding in the V1.1 rules. Also rules
are currently NOT modifiable. To change a rule you will have to delete and
recreate it. This is easier than it sounds since an extract rule facility
is provided for readingall of the rules out to an ascii file. Also note
that doing a show on all attribute, to a file in the FCL will give you an
easy to modify ascii file for creating the new rule (also use keyword TOOLS
to see some of the com files people have placed in the conference as
well.)
jill
|