| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Greetings, The alarms and/or DNA4 modules are still passing NODE4 addresses to the user instead of NAME. Our only recourse is to use ncp in the script to get the name (most ugly). I thought there were plans to change this in 1.3 or did it get dropped off the list? best regards, brad... $show sym p1 P1 = "Domain LOCAL_NS:.lkg-55 Rule poll_LKG-55 " $show sym p2 P2 = "" $show sym p3 P3 = "" $show sym p4 P4 = "(node4 * circuit * substate <> none,at every 0:5:0)" $show sym p5 P5 = "22-DEC-1992 14:08:12.33" $show sym p6 P6 = "Rule fired: Node4 55.24 Circuit SYN-3 Substate = Synchronizing 22-DEC-19 92 14:08:11.52" $show sym p7 P7 = "" $type SYS$SCRATCH:MCC_ALARMS_DATA_14081233.DAT RULE: Domain LOCAL_NS:.lkg-55 Rule poll_LKG-55 MANAGED_OBJECT: Node4 55.24 Circuit SYN-3 DESCRIPTION: CATEGORY: EXPRESSION: (node4 * circuit * substate <> none,at every 0:5:0) TIME: 22-DEC-1992 14:08:12.33 EVIDENCE: Rule fired: Node4 55.24 Circuit SYN-3 Substate = Synchronizing 22-DEC- 1992 14:08:11.52 EVENT_ARGUMENTS: PARAMETER: DOMAIN: Domain LOCAL_NS:.lkg-55 SEVERITY: Critical
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4307.1 | It's in the release notes | RDGENG::PRATT | Wed Dec 23 1992 06:53 | 6 | |
Brad, You beat me to getting this one reported - according to the release notes 3.8.1 this should work. Ian | |||||
| 4307.2 | qar 61 | CTHQ::WOODCOCK | Wed Dec 23 1992 09:14 | 1 | |
QAR 61... | |||||
| 4307.3 | name usage problems | GOSTE::CALLANDER | Thu Dec 31 1992 14:24 | 16 | |
please note that there were a number of unexpected reprocutions
when the AM team made the change to use the name instead of the
address as the primary identifier. These had to do with the FM
functions that cared what the primary identifier of an instance
was/is. For example the targetting database uses the primary
identifier for determining if retargetting needs to occur.
Notification uses the primary identifier to determine domain
membership. The historian and exporter use the primary identifier
for deterining database keys. Also the reports package had aprioi
knowledge (and hard coded string lengths) for receiving the primary
identifier. Due to these interdependencies, the last I knew they
were trying to come up with a clean plan for moving to the use of
names without reaking havoc on those things you might already have
in your databases, and without losing any functionality (like reports).
Hope this clarifies a bit, this item has *NOT* been dropped.
| |||||