| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4258.1 | Another old file? | TOOK::MINTZ | Erik Mintz | Wed Dec 16 1992 07:10 | 6 |
| Are you sure that you don't have another old file kicking about the system?
This is an obsolete syntax for alarm rules, so I'd be surprised if it
is in the startup procedure.
-- Erik
|
| 4258.2 | Installation on VMS-only system | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Dec 16 1992 15:38 | 5 |
| This was a new system build. DECmcc had not been previously loaded.
Joe O'connor suggested a re-install of BMS V1.2.3 to see if problem is
fixed. I'll do it shortly.
-Dan
|
| 4258.3 | Reinstall of BMS 1.2.3 didn't work | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Thu Dec 17 1992 02:40 | 5 |
| The problem still exists. Any ideas on which file(s) may be suspected?
Is this just a test procedure, or might I encounter problems later? I
don't really see anything yet.
-dan
|
| 4258.4 | You will probably have problems later | TOOK::GUERTIN | MCC Managing everything for everyone everywhere | Thu Dec 17 1992 10:14 | 11 |
| I would guess there is a problem with your parse tables or dictionary.
try:
$ man/tool/dict sho class mcc subclass alarms subclass rule
you should get a lot of information about definitions, attributes,
directives, events, attribute partitions, etc.
you should also try:
$ search mcc_system:mcc_fdictionary.log "CREATE MCC ALARMS RULE"
|
| 4258.5 | Can you try again? | WAKEME::ANIL | | Fri Jan 08 1993 05:22 | 15 |
| RE .0
> Will I have to re-install the V1.2.3 kit?
No! I tried this very same rule on V1.2 MCC and the current internal
base level X1.3.5. I was able to create the sample rule with no syntax
errors. Since I don't have the combination of software (DECmcc V1.2.3,
ELM_AM V1.2.0, TSAM V1.0.2, VMS V5.5-2), the best thing to do is look
in the dictionary you have on your system. Follow Matt's suggestion
and report the log file here.
Can you also try to create the same rule from FCL *after* installation?
- Anil
|
| 4258.6 | Problem solved - @sys$startup:dns$client_startup.com | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Wed Jan 13 1993 00:41 | 11 |
| Sorry for taking so long to reply to this note. I've been digging out
of an avalanche following the holidays :-) .
This occurred on a node that was using a DNS repository. The dns
client software was not running.
$ @SYS$STARTUP:DNS$CLIENT_STARTUP.COM
fixed the problem.
-Dan
|