| 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 |
The following MCC_DNA4_EVL log file shows some exit status which I cannot interpret (not in mccmsg.exe or mcctbdmsg.exe). The EVENT manager died as a result of rceiving an alarm event from a remote node. I would like some help in interpreting the status codes in the log. Thanks for any help. Pointers to documentation or notes is fine. Andrew. $ type SYS$SYSROOT:[SYSMGR]MCC_DNA4_EVL.LOG;2 $ 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... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... A fatal error occurred when sending event = 9 to MCC event manager! The EVL sink is terminated! OPS_DNA4_STOP_SINK_MONITOR Failed at step 5, status = 52877226 STOP_SINK_MONITOR is terminated, thread id = 65539, status=52854793 SYSTEM job terminated at 25-OCT-1991 14:13:32.52 Accounting information: Buffered I/O count: 103 Peak working set size: 2386 Direct I/O count: 72 Peak page file size: 6920 Page faults: 1791 Mounted volumes: 0 Charged CPU time: 0 00:00:07.95 Elapsed time: 0 01:36:29.68
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1754.1 | more info | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Fri Nov 01 1991 01:22 | 24 |
Ther is also an alarm software error file
MCC_ALARMS_25-OCT-1991_ERROR.LOG
>>> 25-OCT-1991 09:50:52.82 MCC 0 ALARMS RULE LITTLE_test_alarm
Expression = (OCCURS(NODE4 LITTLE Circuit *
COUNTERS ZEROED))
Status = %MCC-E-INV_HANDLE_STAT, software error: invalid
handle stae
MCC 0 ALARMS RULE LITTLE_test_alarm
AT 25-OCT-1991 09:50:52
----------------
Restarting the MCC_DNA4_EVL process causes Notification Exception
maeesges to come on on the MAP. The message says "software logic error
detected MCC routine Error , %MCC-F-EVENTINTERNERR, Event Manager
internal error"
Andrew
| |||||
| 1754.2 | MCC_S_ALERT_TERMREQ | TOOK::T_HUPPER | The rest, as they say, is history. | Fri Nov 01 1991 14:16 | 10 |
RE .0:
CVR status code 52877226 is MCC_S_ALERT_TERMREQ. It looks as though
the sink is logging this code without translating it. It is valid to
receive this CVR if the sink is being instructed to terminate. Is
someone trying to do this?
CVR status code 52854793 is MCC_S_NORMAL, of course.
Ted
| |||||