| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2972.1 | What kind of upgrade | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Mon May 11 1992 14:15 | 4 |
| What version of DECmcc was installed before T1.2.7?
Are you running on VMS or ULTRIX?
|
| 2972.2 | V1.2.4 - on a VAX running VMS V5.4-3 | WARNUT::PURNELLR | Life, it's not what I thought it was ! | Mon May 11 1992 14:32 | 0 |
| 2972.3 | Check the system time first | TOOK::GUERTIN | It fall down, go boom | Tue May 12 1992 08:02 | 10 |
| The last time I saw this message, it was because the system running
(or trying to run) alarms had its system time set wrong (in this
case, it had its clock running in the year 1991). If this is not
the case, you should have seen an error message during the ivp. The
Alarms module always looks in MCC_COMMON for it's repository files,
regardless of what you set your MCC_SYSTEM logical to. In addition,
you may want to check if the MCC_TDF logical is set correctly.
-Matt.
|
| 2972.4 | Re-setting MCC_TDF does not clear the issue | WARNUT::PURNELLR | Life, it's not what I thought it was ! | Mon May 18 1992 09:26 | 0 |
| 2972.5 | Something odd must have happened. | TOOK::GUERTIN | It fall down, go boom | Mon May 18 1992 14:25 | 8 |
| From FCL try re-enrolling alarms:
MCC> enroll mcc_alarms_fm
Note any informational message which might appear.
Then try creating an alarm rule.
-Matt.
|