[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3765.0. "Recording on alarm rules fails" by BACHUS::FOLENS () Fri Sep 18 1992 09:53

    I'm trying to start recording on a alarm rule. When I start it,
    it tells me the record is successfull created. But when I do
    a show recording, its telling me its active but the number of
    successfull polls=0 and the number of failed polls=1 with the the last poll
    failure reason = "MCC specialized exception code: 385".
    Should recording work on alarm rules? I could find it back in the doc.
    
    -Geert-

T.R Title User Personal
Name Date Lines

3765.1 works on Ultrix but not on VMS TOOK::SHMUYLOVICH Fri Sep 18 1992 13:41 28

T.R	Title	User	Personal Name	Date	Lines
3765.1	works on Ultrix but not on VMS	TOOK::SHMUYLOVICH		`Fri Sep 18 1992 13:41`	28
	> last poll failure reason ="MCC specialized exception code: 385". According to the data dictionary it tells "The rule ... was not enabled, and therefore has no counters". > Should recording work on alarm rules? You can record alarm rules on Ultrix but not on VMS. The Alarms FM performs polling operations in itself (not in the background process like the Historian) and stores all runtime information about rules in memory. On Ultrix each FM is running as a separate process and therefore when the Historian background process issues a "Show....rule..." directive it comes to the same Alarms process which is performing polling operations (assuming that both these processes are running under the same uid). On VMS each instance of MCC uses its own copy of FM so one Alarms FM "does not see" rules enabled by another Alarms FM. You can see this behavior if you invoke two MCCs, enable Alarms rule from one of them, and issue a "Show ... rule.." directive from another. SAm

> last poll failure reason ="MCC specialized exception code: 385".

	According to the data dictionary it tells "The rule ... was not
	enabled, and therefore has no counters".


>    Should recording work on alarm rules? 

	You can record alarm rules on Ultrix but not on VMS.

	The Alarms FM performs polling operations in itself (not in the
    background process like the Historian) and stores all runtime information
    about rules in memory. 

	On Ultrix each FM is running as a separate process and therefore
    when the Historian background process issues a "Show....rule..." directive
    it comes to the same Alarms process which is performing polling operations
    (assuming that both these processes are running under the same uid).

	On VMS each instance of MCC uses its own copy of FM so one Alarms FM
    "does not see" rules enabled by another Alarms FM.

	You can see this behavior if you invoke two MCCs, enable Alarms rule
    from one of them, and issue a "Show ... rule.." directive from another.

	SAm