| Hi,
I'm afraid I don't have very encouraging news.
PMs (Presentation Modules, e.g. FCL and IMPM) on ultrix behave on ultrix
pretty much as they do on VMS. If you exit them, they're done.
FMs and AMs (Function and Access Modules, also known as Management Modules,
e.g. SNMP AM and Alarms FM) behave differently on ultrix than on VMS. Under
VMS, all MMs invoked by a PM run in the same process as the PM. When the
user exits from the PM, all MMs running in that process also exit. Under
Ultrix, each MM runs in a separate process. Once an MM is started (due
to a PM dispatching a directive to them) they continue running until they
are killed.
"Notification Services" consists of functionality in both PMs (FCL and IMPM)
and in MMs (Notification FM, Alarms FM, Collector AM).
Notify Requests in particular are run in a PM, which makes requests of
the Notification FM. When you exit the PM, the notify request dies.
"Notify , to file" from FCL is still run in FCL (the PM).
>Is it possible to have a background DECmcc with notification
>services started, to collect those events?
If there's no PM, there's no notify request.
>If yes, how can
>these be reentered in the prime system when this is again
>running?
>
>I think it is possible to run the Notification FM in the
>background by NOTIFY DOMAIN TOTO TO FILE notif.log. Does
>this solve the problem above ?
Sorry, no. "Notify , to file" from FCL will work for as long as the FCL
session it was started from is running.
>How to reenter those events in the Notif PM services
>(i.e notification summary and detail windows when the operator
>logs back in )?
>
>What about the Notification PM ? Can it run in the background
>while the operator is delogged ?
Sorry, no.
|