| Hi, I am the manager of the decnet AMs. For MCC V1.1, the kernel,
alarms, dna4 Am, and notification services all provide some level
of asynchronous event support. Events from Node4 entities are made
available at the Call_access interface by the DNA4 AM. We have tested
this extensively with the Alarm FM. Other Access Modules will be
implementing complementary support in the near future. The DNA5 AM
actually has a prototype working with alarm support but due the
inability to test this with real DNA5 entities prior to our code
freeze dates, this is being deferred to some kit after MCC V1.1.
There is advanced development work going on with other Access Modules
to integrate more asynchronous events into MCC.
|
|
Paul,
Some more information, to add to what Wally said. How you detect
an event at the entity level is up to the AM (or service provider)
that is waiting on them. How they get reported inside of MCC is
described in the SRM V1.1, we use the term Event Manager to refer
to the internal mechanisms.
The Event Manager is NOT a poller, polling for events would mean
you would miss too many. Instead the Event Manager provides an input
and output mechanism for getting at the events. The events are stored
on a system wide basis.
The AM uses the mcc_event_put routine for putting the event into
the event manager. To get an event out you use the mcc_event_get
(check SRM for exact details on routine names). Each xM that wants
to support events must provide an entry point in the dispatch tables
for the GETEVENT directive. This verb is what is known as an event
directive-type (again reference the SRM for more information). This
entry point is called by any module that wants access to the events
supported by your module. When it is called, the entry point routine
should handle making the appropriate mcc_event_get requests.
The event manager is available in the V1.1 system, along with the
Notification FM which is a generic FM used for retrieving events
and alarming information in a consistent fashions for the PMs, see
the BMS Use manual for more information.
I'd like to end this by saying this is a QUICK overview of the ins
and outs but by no means is a complete picture. You need to get
the V1.1 SRM if you are looking for coding/implementation details.
If you are just looking to use the end user functions I suggest
you go to the Use books (you might want to wait until the V1.1 final
set of docs are ready) and read up on the support events from the
different modules (namely DNA4, Alarms, and Notificaiton for the
V1.1 product).
jill
|