| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I am installing DECmcc for the first time and am completely new to it.
The installation fails while running the startup procedure with lots of
"Kernel cannot be initialized" messages. Could someone give me a clue
where to start looking?
Thank you
Gary
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 919.1 | Probably an RMS error accessing the dispatch tables | TOOK::GUERTIN | I do this for a living -- really | Tue Apr 16 1991 12:35 | 18 |
Gary,
These errors are almost always due to some RMS error trying to access
the MCC_SYSTEM:MCC_DISPATCH_TABLE.DAT file. Do you have read/write
access to the file? The file should exist at this point in the
installation. It is created in MCC_COMMON:, and opened for read/write
through MCC_SYSTEM:. You should make sure it is there. On occassion, a
process may have the file opened for write-noshare, and not allow
another process to access it, after a while the second process
times-out on the open with "KERNINITFAIL". If everything looks okay,
try
$ show device/file MCC_COMMON:
and look for MCC_DISPATCH_TABLE.DAT to see if anyone has it opened,
it should not show up. Also, is this a cluster installation? If so,
is MCC_COMMON pointing to the common disk?
Please let know if any of this has helped.
-Matt.
| |||||
| 919.2 | Should have read the Release Notes more carefully | GOONS::CHAPMAN | Tue Apr 16 1991 13:09 | 4 | |
Sorry! - all the problems went away when I set the installing account's
quotas as per the Release Notes.
Gary
| |||||