| I would like to take the opportunity to telle that I also cannot
manage to use the alarm manager. All other POLYCENTER applications do
work well.
What I experience is that after selection of the POLYCENTER Alarm
Manager I get a DECterm only for a few seconds, and then that window
disappears as fast as it arrived (in fact a little faster).
I have exact the same behaviour when I start manually
"mcc_alarm_mgr" from a DECterm, although I then can read the message
put on the screen:
mcc_alarm_mgr
Start Command processor in background
Starting application
[1] 16080
I can see the mcc_alarm_mgr_ui for a while in the system with "ps -aux"
but also that process disappears quite rapidly.
I am running on ULTRIX V4.3 / DECmcc V1.3
Are there environment variables required ?
I'll appreciate help.
Regards,
Dominique.
|
|
Your problems (.0 and .1) are most likely the same thing. The alarm
manager requires MIRs like many other MCC applications/components.
If the file protection is not set correctly then you will not be
able to run the alarm manager. A note about this is printed at
installation time, but it is not well documented in the prototype.
Also the alarm manager prototype has a bug, in that it does not
print an error when it can not open the database (fixed in the field
test release).
please check the MIR files, mcc_alm_mgr_data.* and
mcc_alm_mgr_template.*. For the alarm manager to work a user must
have full read *AND* write access to the database files. Read access
alone is not sufficient! The MCC database routies always open the
database read/write.
Please let me know if this is not your problem
jill
|