| Called Eric, here's what we found:
1. He is running DECmcc BMS V1.1
2. The output file created by MCC_ALARMS_EXTRACT_RULES.EXE does NOT contain
any errors in it; the WRITE-PROCEDURE error only appears on the screen,
as if its writing to SYS$OUTPUT or SYS$ERROR.
3. Using FCL, we entered the command SHOW DOMAIN * RULE * ALL CHARACTERISTICS
No errors of any kind were generated, and the last rule displayed:
VPVSJ_CIRCUITDOWN_CLEAR
is the same last rule displayed by MCC_ALARMS_EXTRACT_RULES.EXE, so
at least the two displays are consistent.
4. Customer added several new rules since yesterday, and these also showed
up in the correct order in both his FCL display and when he runs
EXTRACT_RULES.
So it appears that EXTRACT_RULES is behaving properly until it loops though
all currently valid rules, and then falls off into the weeds somehow.
Please address the following question: In the formatted dump that
follows the WRITE-PROCEDURE error, the customer sees some rules
defined 6-12 months ago by someone that has left the project. He is
*very* concerned that these rules *not* get redefined somehow. I
explained how oftentimes a "deleted record" is not actually deleted,
but simply sets a flag bit indicating the record is invalid. He is
familiar with that technique, and asked if you could explain if that
is what EXTRACT_RULES is finding or if something else is happening.
This is a VAX 9000 customer, and for some reason he is extremely
nervous about this data showing up. Anything he can do to "really"
delete or overwrite that record?
Thanks very much, Keith, for your quick response to this. If you
would like this SPRed, let me know.
Dave
*** MORE INFORMATION ***
Keith, I ran the following commands on one of our local workstations and got
the same kind of error, only in this case the WRITE-PROCEDURE error occurs on
the FIRST rule, not the LAST. Owner of this node said this was a rule that he
had deleted while using the FCL interface; either he didn't delete it correctly
or there might be a problem with the DELETE RULE command. We added the rule
back (refers to node IAMWMN) but MCC inserted this as Rule 3, so we still got
the WRITE-PROCEDURE error.
This node is on the Enet, so if you need to login, I can get you permission.
$ manage /enterprise
DECmcc (V1.1.0)
show domain * rule * all characteristics
Domain SNAZZY_NS:.colo_sprgs Rule *
AT 3-MAR-1992 11:08:46 Characteristics
No such entity: Domain SNAZZY_NS:.colo_sprgs Rule *
Unknown Entity = Domain SNAZZY_NS:.colo_sprgs Rule *
Domain SNAZZY_NS:.DEMPR1 Rule *
AT 3-MAR-1992 11:08:48 Characteristics
No such entity: Domain SNAZZY_NS:.DEMPR1 Rule *
Unknown Entity = Domain SNAZZY_NS:.DEMPR1 Rule *
Domain SNAZZY_NS:.foobar Rule *
AT 3-MAR-1992 11:08:48 Characteristics
No such entity: Domain SNAZZY_NS:.foobar Rule *
Unknown Entity = Domain SNAZZY_NS:.foobar Rule *
Domain SNAZZY_NS:.Ithaca Rule *
AT 3-MAR-1992 11:08:48 Characteristics
No such entity: Domain SNAZZY_NS:.Ithaca Rule *
Unknown Entity = Domain SNAZZY_NS:.Ithaca Rule *
Domain SNAZZY_NS:.Rochester Rule *
AT 3-MAR-1992 11:08:49 Characteristics
No such entity: Domain SNAZZY_NS:.Rochester Rule *
Unknown Entity = Domain SNAZZY_NS:.Rochester Rule *
Domain SNAZZY_NS:.STATIC_DOMAIN Rule *
AT 3-MAR-1992 11:08:49 Characteristics
No such entity: Domain SNAZZY_NS:.STATIC_DOMAIN Rule *
Unknown Entity = Domain SNAZZY_NS:.STATIC_DOMAIN Rule
*
Domain SNAZZY_NS:.test Rule *
AT 3-MAR-1992 11:08:49 Characteristics
No such entity: Domain SNAZZY_NS:.test Rule *
Unknown Entity = Domain SNAZZY_NS:.test Rule *
Domain SNAZZY_NS:.usa Rule *
AT 3-MAR-1992 11:08:50 Characteristics
No such entity: Domain SNAZZY_NS:.usa Rule *
Unknown Entity = Domain SNAZZY_NS:.usa Rule *
Domain SNAZZY_NS:.walt Rule EMAWIZ_LINE_ZEROED
AT 3-MAR-1992 11:08:50 Characteristics
Examination of attributes shows:
Alarm Fired Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.
COM;3
Alarm Exception Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPT
ION.COM;3
Description = "Node EMAWIZ line SVA-0 counters have
been zeroed"
Category = "line_events"
Alarm Fired Parameters = "SHOTO::W_MCGAW"
Expression = (OCCURS(NODE4 EMAWIZ LINE SVA-0
COUNTERS ZEROED))
Severity = Critical
Domain SNAZZY_NS:.walt Rule REMOTE_NODE_STATE
AT 3-MAR-1992 11:08:51 Characteristics
Examination of attributes shows:
Alarm Fired Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.
COM;3
Alarm Exception Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPT
ION.COM;3
Description = "Node IAMWMN is unreachable "
Category = "Node unreachable"
Batch Queue = "SYS$BATCH"
Alarm Fired Parameters = "SNAZZY::W_MCGAW W_MCGAW"
Expression = (NODE4 CX03H1 REMOTE NODE 62.480
STATE = UNREACHABLE,AT EVERY
00:05:00)
Severity = Critical
Domain SNAZZY_NS:.walt Rule test
AT 3-MAR-1992 11:08:52 Characteristics
Examination of attributes shows:
Alarm Fired Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.
COM;3
Alarm Exception Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPT
ION.COM;3
Description = "test"
Category = "test_rule"
Batch Queue = "SYS$BATCH"
Alarm Fired Parameters = "CSC32::D_MCADOO"
Expression = (OCCURS (Node4 EMAWIZ Circuit SVA-0
COUNTERS ZEROED))
Severity = Critical
Domain SNAZZY_NS:.world1 Rule *
AT 3-MAR-1992 11:09:01 Characteristics
No such entity: Domain SNAZZY_NS:.world1 Rule *
Unknown Entity = Domain SNAZZY_NS:.world1 Rule *
exit
$ run sys$system:mcc_alarms_extract_rules
MCC_ALARMS_EXTRACT_RULES
- Generating a Procedure to Rebuild the Alarms MIR
- Output File: MCC_ALARMS_RULES.COM
WRITE-PROCEDURE failed on step 2
[ 0 ] (
[ 4 ] (
[ 6 ] (
[ 1 ] 06
[ 2 ] 53 59 53 24 43 4f 4d 4d 4f 4e 3a 5b 4d 43 43 5d 4d 43 43 5f
41 4c 41 52 4d 53 5f 4d 41 49 4c 5f 41 4c 41 52 4d 2e 43 4f
4d 3b 31 -- SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.COM;1
[ 3 ] 00
)
[ 10 ] (
[ 1 ] 06
[ 2 ] 53 59 53 24 43 4f 4d 4d 4f 4e 3a 5b 4d 43 43 5d 4d 43 43 5f
41 4c 41 52 4d 53 5f 4d 41 49 4c 5f 45 58 43 45 50 54 49 4f
4e 2e 43 4f 4d 3b 31 -- SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPTION.COM;1
[ 3 ] 00
)
[ 3 ] (
[ 1 ] 03
[ 2 ] 4e 6f 64 65 20 49 41 4d 57 4d 4e 20 69 73 20 75 6e 72 65 61
63 68 61 62 6c 65 20 -- Node IAMWMN is unreachable
[ 3 ] 00
)
[ 4 ] (
[ 1 ] 03
[ 2 ] 4e 6f 64 65 20 75 6e 72 65 61 63 68 61 62 6c 65 -- Node unreachable
[ 3 ] 00
)
[ 7 ] (
[ 1 ] 03
[ 2 ] 53 59 53 24 42 41 54 43 48 -- SYS$BATCH
[ 3 ] 00
)
[ 8 ] (
[ 1 ] 03
[ 2 ] 53 4e 41 5a 5a 59 3a 3a 57 5f 4d 43 47 41 57 20 57 5f 4d 43
47 41 57 -- SNAZZY::W_MCGAW W_MCGAW
[ 3 ] 00
)
[ 2 ] (
[ 1 ] 1a
[ 2 ] 28 4e 4f 44 45 34 20 43 58 30 33 48 31 20 52 45 4d 4f 54 45
20 4e 4f 44 45 20 36 32 2e 34 38 30 20 53 54 41 54 45 20 3d
20 09 09 20 20 55 4e 52 45 41 43 48 41 42 4c 45 2c 41 54 20
45 56 45 52 59 20 30 30 3a 30 35 3a 30 30 29
[ 3 ] 00
)
[ 21 ] (
[ 1 ] 0a
[ 2 ] 01
[ 3 ] 00
)
[ 5 ] (
[ 1 ] 02
[ 2 ] a5 82 00 b3 a1 82 00 06 81 01 12 82 01 00 a2 82 00 2a 81 01
17 82 01 01 a6 82 00 20 81 01 12 82 01 03 83 12 41 54 20 45
56 45 52 59 20 30 30 3a 30 35 3a 30 30 20 84 01 00 85 01 01
a3 82 00 06 81 01 0c 82 01 00 a4 82 00 19 81 01 13 82 01 01
a6 82 00 0f 81 01 04 82 01 0a 83 01 05 84 01 00 85 01 01 a5
82 00 50 81 01 15 82 01 00 a5 82 00 46 a1 82 00 2c a0 82 00
14 81 01 01 82 01 0c 83 01 01 84 01 18 85 06 43 58 30 33 48
31 a1 82 00 10 81 01 01 82 01 0a 83 01 02 84 01 19 85 02 f9
e0 82 01 02 83 01 29 85 01 0a 86 01 00 a9 82 00 03 81 01 00
88 01 01
[ 3 ] 00
)
)
)rule # 2 -- MCC 0 ALARMS RULE EMAWIZ_LINE_ZEROED , in domain -- SNAZZY_NS:.WALT
rule # 3 -- MCC 0 ALARMS RULE REMOTE_NODE_STATE , in domain -- SNAZZY_NS:.WALT
rule # 4 -- MCC 0 ALARMS RULE test , in domain -- SNAZZY_NS:.WALT
>>> EXIT - Alarms MIR extraction completed successfully
$ type MCC_ALARMS_RULES.COM
!
! MCC Alarm Rules
!
!
Create MCC 0 ALARMS RULE EMAWIZ_LINE_ZEROED -
Category = "line_events", -
Description = "Node EMAWIZ line SVA-0 counters have been zeroed", -
Expression = (OCCURS(NODE4 EMAWIZ LINE SVA-0 COUNTERS ZEROED)), -
Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.COM;3, -
Exception Handler = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPTION.COM;3, -
Parameter = "SHOTO::W_MCGAW", -
Perceived Severity = critical, -
in domain = SNAZZY_NS:.WALT
!
Create MCC 0 ALARMS RULE REMOTE_NODE_STATE -
Category = "Node unreachable", -
Description = "Node IAMWMN is unreachable ", -
Expression = (NODE4 CX03H1 REMOTE NODE 62.480 STATE = UNREACHABLE,AT EVERY 00:05:00), -
Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.COM;3, -
Exception Handler = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPTION.COM;3, -
Parameter = "SNAZZY::W_MCGAW W_MCGAW", -
Queue = "SYS$BATCH", -
Perceived Severity = critical, -
in domain = SNAZZY_NS:.WALT
!
Create MCC 0 ALARMS RULE test -
Category = "test_rule", -
Description = "test", -
Expression = (OCCURS (Node4 EMAWIZ Circuit SVA-0 COUNTERS ZEROED)), -
Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.COM;3, -
Exception Handler = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPTION.COM;3, -
Parameter = "CSC32::D_MCADOO", -
Queue = "SYS$BATCH", -
Perceived Severity = critical, -
in domain = SNAZZY_NS:.WALT
$ exit
|
| The reason the "WRITE-PROCEDURE, faile on step 2" problem was found and
corrected for the DECmcc T1.2.7 Field Test Update release.
Changing your DNS name server can cause this problem. Likewise, changing
to the Local-MIR and back to the real DNS server can cause it too.
o Select DNS server
o Create a Rule
o Select a new DNS server
o Reboot (to clear the DNS cache)
o Run Extract Rules
Selecting a new DNS server can include renaming the node which is the
server (I believe).
What happens is .. the "Domain Name" is a FullName datatype. This means
the DNS nameserver & actual domain name are stored together.
When you change the name server - and reboot - and run Extract Rules, the
system cannot convert the Domain Name internal representation to ASCII.
The error returned from the convertion routines is "Error in Fullname".
The t1.2.7 release traps this error, and prints an Error Summary (see
below).
I hope this clears up this problem .. please let me know if there are
any more questions.
/keith
------------------------------------------------------------------------------
MCC_ALARMS_EXTRACT_RULES - T1.2.7
- Generating a Procedure to Rebuild the DECmcc Alarms MIR
- Output File: MCC_ALARMS_RULES.COM
rule # 1 -- MCC 0 ALARMS RULE 1076_DTM_ZENA_R_210
rule # 2 -- MCC 0 ALARMS RULE BATCH
:
:
rule # 32 -- MCC 0 ALARMS RULE vin_6_enet
>>> WARNING - Error converting Domain Name to ASCII: status = 52877354
rule # 33 -- MCC 0 ALARMS RULE gwc , in domain <error in domain name>
:
:
rule # 63 -- MCC 0 ALARMS RULE seconds_operating , in domain ETHRFX_NS:.MKO_MCC_GROUP
rule # 64 -- MCC 0 ALARMS RULE snmp , in domain ETHRFX_NS:.16-126-16-0-HOSTS-2
*** Error Summary ***
>>> 1 Problem(s) converting a Domain Name to a String.
o This could be caused by Rules which were created with a
different DNS Namespace than the one you are currently using,
including using the Local MIR implementation as your Namespace.
o Bad rules will contain <error in domain name> as their Domain Name.
o The mcc_alarms_rules.com file must be edited before it can be used
to reload your Alarms MIR.
>>> EXIT - Alarms MIR extraction completed successfully
------------------------------------------------------------------------------
|