| 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 |
Hi ,
I got some problems with the event notification :
o the DNA_STARTUP_DNA4_EVL.COM starts without an error message
- process MCC_DNA4_EVL is running
o I create following alarm rule :
Procedure = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_ALARM.
COM;5
Exception Handler = SYS$COMMON:[MCC]MCC_ALARMS_MAIL_EXCEPT
ION.COM;4
Description = "Counters zeroed on circuit Syn-1"
Category = "Counter"
Queue = "ALARM$BATCH"
Parameter = "xxxxxx::SYSTEM"
Expression = (OCCURS(NODE4 yyyyy CIRCUIT SYN-1
COUNTERS ZEROED))
Perceived Severity = critical
o if counters are zeroed, I receive the notification on iconic map
- colour changes
- no mail !
o The status of my alarm rule shows, that now the rule is now disabled by MCC
itself.
- Alarm rule status: State = Disabled
Substate = Disabled by error condition
Disable Time = 10-JUL-1991 15:26:26.95
Result of Last Evaluation = True
Error Condition = "%MCC-E-INV_HANDLE, software error:
invalid handle parameter"
o if I look into the DECNET account there is a NETSERVER.LOG like:
--------------------------------------------------------
Connect request received at 10-JUL-1991 18:18:51.77
from remote process HBOMCC::"0=SYSTEM"
for object "NMCC_EVENT"
--------------------------------------------------------
%DCL-E-OPENIN, error opening SYS$SYSDEVICE:[DECNET]NMCC_EVENT.COM; as input
-RMS-E-FNF, file not found
DECNET job terminated at 10-JUL-1991 18:18:51.99
- on my system there is no NMCC_EVENT.COM file
Who can gives me some help ?
Thank you ... Karsten.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1231.1 | Reproducible -- 1/2 the battle is over | TOOK::ORENSTEIN | Wed Jul 10 1991 17:40 | 6 | |
Hi,
I am able to reproduce your problem. I hope to have an answer to
you shortly. Thanks for letting us know about this problem.
aud...
| |||||
| 1231.2 | Queue does not exist ... | TOOK::ORENSTEIN | Wed Jul 10 1991 18:27 | 12 | |
Hi again,
I noticed that in your rule the QUEUE parameter is "ALARM$BATCH".
I find that I can reproduce your problem only by specifying a queue
that does not exist. Could you please check that alarm$batch
is a real queue and that you did not mean alarmS$batch?
^
Let me know how it goes ...
aud...
| |||||
| 1231.3 | Mismatch with queue names | HAM::HANSEN | Thu Jul 11 1991 04:54 | 24 | |
Hi Aud,
exactly - the queue name is alarmS$batch. Now the event notification
runs several times including mail.
Sorry to steal your time for that problem. I have to check my eyes
and fingers.
But let me ask you one more question:
o What do you think about that NMCC_EVENT.COM in the NETSEVER.LOG file ?
My MCCDNA_EVL.LOG shows me ** Unable to connect to NMCC ** .
$ manage/enter/presen=mcc_dna4_evl
Network object MCC_DNA4_EVL is declared, Status = 52854793
Waiting for the event message from EVL.....
The connection with EVL is established.
** Unable to connect to NMCC **
Ready to read the next event message...
Ready to read the next event message...
Did you reproduce that too ?
Regards from Hamburg .... Karsten.
| |||||
| 1231.4 | TOOK::ORENSTEIN | Thu Jul 11 1991 17:57 | 12 | ||
>> Sorry to steal your time for that problem. I have to check my eyes
>> and fingers.
No problem -- you DID find a bug. It is unreasonable for ALARMS to
tell you INVALIDHANDLE when it means NOSUCHQUEU. (Note: This only
happens on OCCURS function) This will QARed.
I'm just glad that you could get your rules running again.
As for your DNA problem, I'll let a real DNA guru help you on this.
aud...
| |||||
| 1231.5 | ignore unable to connect | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Fri Jul 12 1991 10:03 | 5 |
The DNA4 stuff is set up so that both MCC Decnet and NMCC can share events (EVL only allows for a single event listener). When you startup the MCC EVL stuff it will go out to see if NMCC is out there, and therefore in need of event information along with MCC. If NMCC isn't there then you will see the unable to connect message. | |||||