[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
5914.0. "ALARMS don't pass all info to the Batch-job" by STKHLM::BERGGREN (Nils Berggren, DC Sweden. 876-8287) Tue Mar 22 1994 06:20
Hi,
We're having a severe alarming problem at a customers DECmcc installation.
Environment: VS4000/90, VMS5.5-2, 128 Mb, DECmcc 1.3, SNA-AM
They have a SNA-node which monitor their DataPak network. This node
generates an event called 'Alert Condition' which we have a rule set for.
Along with that event the event-report contains all the necessary information
to determin what's happend.
The problem is that when the rule fires, the information passed to the
batch-procedure is not all the information that we can see in the
notifications window.
In the batch-procedure there's no way for us to determine what's happend
since we don't get all the information in the event-report passed to it.
What we need is the "Specific Problem Info"-field from the event-report or
the second information-field from the alarm-event.
How come ALARMS just pass the first Information-field to the batch-job?
Wouldn't you expect ALARMS to write all the information into the data-file
passed to the batch-job?
What can we do about it?
Below is the information passed to the batch-job (the procedure just logs
all its arguments P1-P8), the contents of the alarmdata-file and extract
from the notification-window. I have set up a notify request on the
entity for any events.
/Nils Berggren
Arguments passed to the Batch-job
*********************************
P1= Domain SE_NS:.TELIA.C.HAN.ASMTST Rule nisses_datapak_larm
P2=
P3=
P4= (OCCURS (SNAnode SE_NS:.telia.c.sna.DPNV1 any events))
P5= 22-MAR-1994 10:33:45.71
P6= The last event detected: SNAnode SETVTC99.DPNV1 Alert Condition
22-MAR-1994 10:33:45.70
P7=
P8= SYS$SCRATCH:MCC_ALARMS_DATA_10334571.DAT
Contents of SYS$SCRATCH:MCC_ALARMS_DATA_10334571.DAT
****************************************************
RULE: Domain SE_NS:.TELIA.C.HAN.ASMTST Rule nisses_datapak_larm
MANAGED_OBJECT: SNAnode SETVTC99.DPNV1
DESCRIPTION:
CATEGORY:
EXPRESSION: (OCCURS (SNAnode SE_NS:.telia.c.sna.DPNV1 any events))
TIME: 22-MAR-1994 10:33:45.71
EVIDENCE: The last event detected: SNAnode SETVTC99.DPNV1 Alert Condition
22-MAR-1994 10:33:45.70
PARAMETER:
DOMAIN: Domain SE_NS:.TELIA.C.HAN.ASMTST
SEVERITY: Minor
EXTRACT FROM NOTIFICATION-WINDOW
********************************
%%%%%%%%%%%%%% Event, 22-MAR-1994 10:33:46 %%%%%%%%%%%%%% [6,576]
Domain: SE_NS:.telia.c.han.asmtst Severity: Indeterminate
Notification Entity: SNAnode SE_NS:.telia.c.sna.DPNV1
Event Source: SNAnode SE_NS:.telia.c.sna.DPNV1
Event: Alert Condition
Reporting Product = { "NAP" }
Probable Cause = { "COMMUNICATIONS EQUIPMENT" }
Recommended Repair = { "No action necessary" }
Specific Problem Info = { "DEV PO: Problem resolved",
"Message Text from Application
Program",
"WLD PO CLR 20034051 AM HDN50
11 11 PO 4 hardware fault",
"EX: 020B 0006 0004 0008" }
Hierarchy Resource List = { (
Resource Type = Service Point,
Resource Name = DPNV1 ),
(
Resource Type = Transaction Program,
Resource Name = NAP ),
(
Resource Type = Management Server,
Resource Name = DPNVIEW ),
(
Resource Type = Unspecified Device,
Resource Name = HDN50 ),
(
Resource Type = Unspecified Device,
Resource Name = PO ) }
!!!!!!!!!!!!!! Alarm, 22-MAR-1994 10:33:46 !!!!!!!!!!!!!! [5,577]
Domain: SE_NS:.TELIA.C.HAN.ASMTST Severity: Minor
Notification Entity: SNAnode SE_NS:.TELIA.C.SNA.DPNV1
Event Source: Domain SE_NS:.TELIA.C.HAN.ASMTST Rule nisses_datapak_larm
Event: OSI Rule Fired
Event Type = QualityofServiceAlarm
Event Time = 22-MAR-1994 10:33:45.71
Probable Cause = Unknown
Additional Info = { (
significance = True,
information = "The last event detected: SNAnode
SETVTC99.DPNV1 Alert Condition
22-MAR-1994 10:33:45.70" ),
(
significance = True,
information = "Event: Alert Condition
Reporting Product = { ""NAP"" }
Probable Cause = {
""COMMUNICATIONS EQUIPMENT"" }
Recommended Repair = { ""No
action necessary"" } Specific
Problem Info = { ""DEV PO:
Problem resolved"", ""Message
Text from Application Program"",
""WLD PO CLR 20034051 AM HDN50 11
11 PO 4 hardware fault"", ""EX:
020B 0006 0004 0008"" }
Hierarchy Resource List = { (
Resource Type = Service Point,
Resource Name = DPNV1 ), (
Resource Type = Transaction
Program, Resource Name = NAP ),
( Resource Type = Management
Server, Resource Name = DPNVIEW
), ( Resource Type = Unspecified
Device, Resource Name = HDN50 ),
( Resource Type = Unspecified
Device, Resource Name = PO ) }" ),
(
significance = True,
information = "(OCCURS (SNAnode
SE_NS:.telia.c.sna.DPNV1 any
events))" ) }
Managed Object = SNAnode SETVTC99.DPNV1
Perceived Severity = Minor
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5914.1 | User error! | STKHLM::BERGGREN | Nils Berggren, DC Sweden. 876-8287 | Wed Mar 23 1994 05:23 | 15 |
| Sorry,
my mistake....
I didn't check the log-file from the batch-job carefully enough. I got
the EVENT_ARGUMENTS containing all the needed info, but I lost it in
in my procedure since it was a very long string and I got the
"%DCL-W-TKNOVF, command element is too long - shorten"
error-message when writing the symbol to a log-file.
/Nils Berggren
|