| 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 |
Hello,
I have one question regarding the DECmcc Exporter/Historian FM.
I would be very grateful if someone could provide me with an answer.
Thank you,
Maurice.
HW: VAX 6430
SW: VMS 5.5
DECmcc V1.1
QUESTION
========
The Basic Management System Use manual suggests to set alarm rules to check that
the Historian (p3-10) / Exporter (p4-12) backround processes are not stopped
(Operation Stopped event).
I tried the following experiment:
- on on session, from DECmcc, I issued the following command:
MCC> GetEvent mcc 0 EXPORTER_FM Operation Stopped
- from another session I aborted the exported batch background process
- on the first session, I did not receive any event
Potentially, the remote sink does not pass that event. Attached, you will
find the events that are passed by the remote sink.
What is the event class/type corresponding to the "Operation Stopped event" ?
Is my assumption about the event filtering correct or is there any other
reason for which I cannot trap the event ? (note: no exporting request is
currently running)
show node4 tplab local SINK * ALL ATTRIBUTES
Node4 48.116 Local Sink Monitor
AT 5-FEB-1992 17:04:58 All Attributes
Type = Monitor
State = On
Name = "MCC_DNA4_EVL"
Initial State = On
Initial Type = Monitor
show node4 tplab OUTBOUND STREAM * REMOTE SINK * ALL ATTRIBUTES
Node4 48.116 Outbound Stream 48.116 Remote Sink Monitor
AT 5-FEB-1992 17:00:28 All Attributes
Type = Monitor
EventFilter = { ( Choice = C5,
Source_Entity = All Sources,
Class = 0,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 2,
Event_Type = { 0,
1 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 3,
Event_Type = { 0,
1,
2 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 4,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 5,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 6,
Event_Type = { 0,
1,
2,
3,
4,
5 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 7,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11 } ) }
Initial Event Filter = { ( Choice = C5,
Source_Entity = All Sources,
Class = 0,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 2,
Event_Type = { 0,
1 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 4,
Event_Type = { 2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
15,
16,
18,
19 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 5,
Event_Type = { 0,
1,
2,
3,
4,
5,
6,
7,
8,
9,
10,
11,
12,
13,
14,
15,
16,
17,
18 } ),
( Choice = C5,
Source_Entity = All Sources,
Class = 128,
Event_Type = { 0,
1,
2,
3,
4 } ) }
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2274.1 | Help | BIS1::COLLEYE | Wed Feb 12 1992 07:47 | 25 | |
Hello,
I would like to stress the importance of my question since
I noticed that, after a reboot of the system (VAX VMS V5.5)
the background processed do not restart (even when submitted
with the /RESTART qualifier).
Even worst, when restarted manually, the scheduling sequence
is changed:
x---x---x---x--| |x---x---x---x---
t1 t2 t3 t4 t5 t6 t7 t8
T1 T2
t1: pooling begin time
(ti+1 - ti): pooling period
T1: system crash
T2: system rebooted
t5: backgrond process restarted
(ti+1 - ti) does not change
BUT t5-t4 is not a multiple of (ti+1 - ti)
Maurice.
| |||||
| 2274.2 | Additional info for help request | BIS1::COLLEYE | Mon Feb 17 1992 09:09 | 4 | |
Could this additional information help ?
In my environment, I cannot find any file MCC_COMMON:MCC_EVENT_POOL.DAT
(referenced in DECmcc - Management Module Programming Manual, P3-5)
| |||||
| 2274.3 | Event Pool file reference is obsolete | TOOK::T_HUPPER | The rest, as they say, is history. | Tue Feb 18 1992 14:26 | 9 |
RE .2:
There is not a file MCC_COMMON:MCC_EVENT_POOL.DAT in V1.1. The event
pool is contained in a temporary global section backed only by the
pagefile. The documentation is in error.
I don't have answers for your other questions.
Ted
| |||||
| 2274.4 | TOOK::SHMUYLOVICH | Tue Feb 18 1992 14:30 | 32 | ||
The Operation Stopped event does not indicate that the background
process is not running. It is generated when one of the recording/exporting
requests is automatically suspended due to the deregestering of the target
entity.
In V1.2 every command which changes the state of the recording/exporting
request to "active" (Record/Export, Resume and Modify) checks if the
background process is running and returns the corresponding exception.
In addition to this Show Recording/Exporting tells the user if the
background is not running.
> x---x---x---x--| |x---x---x---x---
> t1 t2 t3 t4 t5 t6 t7 t8
> T1 T2
>
> t1: pooling begin time
> (ti+1 - ti): pooling period
> T1: system crash
> T2: system rebooted
> t5: backgrond process restarted
>
> (ti+1 - ti) does not change
> BUT t5-t4 is not a multiple of (ti+1 - ti)
This is a expected behavior. The background tries to restart polling
operations immediately.
SAm
| |||||
| 2274.5 | Thank you | BIS1::COLLEYE | Wed Feb 19 1992 07:22 | 5 | |
Ted, Sam,
Thank you for your clarifications.
Maurice.
| |||||