| 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, My customer uses DECMCC BMS version 1.1 with the MCCBMS011_PATCH_ALARMS_1 patch.He uses the event manager and enable the alarms in a batch job. Sometimes (?), as soon as the decnet event occurs , the corresponding alarm does not appear. It seems there is no information in the mcc_dna4_evl logfile : .................... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... If he stops the batch job and restarts it, the alarms fire back and he founds in the batch logfile the following message : %MCC-F-FATAL_FW, fatal framework condition : Failed to dequeue next ready thread %MCC-F-FATAL_FW, fatal framework condition : Failed to dequeue next ready thread %MCC-F-FATAL_FW, fatal framework condition : Failed to dequeue next ready thread %MCC-F-FATAL_FW, fatal framework condition : Failed to dequeue next ready thread Is this problem known ? Any suggestions in trying to track it ? Thanks a lot. JOcelyne.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1880.1 | clean up event manager; don't delete MCC processes | TOOK::CALLANDER | MCC = My Constant Companion | Tue Jan 14 1992 10:54 | 17 |
Okay, part of your problem is most likely due the killing of the batch
job. MCC is a multi threaded system, what you are doing when you kill
the batch job is that you are killing most likely one of many threads
that are running through the system. The alarms FM is still running in
batch, still believes that it has a thread outstanding to get the
events from the dna4_evl that you just killed. Please make use of MCC
to terminate processes, do not simply kill them. I believe this is
documented (in the overly verbose) release notes. Since you killed the
batch job you will have to bring down ALL copies of MCC that are
running to completely clean up. This means the alarms batch job, any
users currently running MCC, as well as any other event sinks or
reporting/exporting currently active. This is necessary for the MCC
event manager to shutdown and perform a clean up.
jill
| |||||