| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2939.1 | Enrolls done by install | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Tue May 05 1992 22:28 | 19 |
| The dispatch table is created by the installation procedure, executed
by setld at install time. You could look at
/usr/etc/subsets/MCRBMS???.scp
if you are interested in how the installation procedure does it.
Basically, for each MM, you issue
manage enroll mcc_xxx_xm
where mcc_xxx_xm is the name of the executable.
Out of curiosity, what do you think corrupted the dispatch tables?
We haven't seen a problem that can't be fixed by re-enrolling a specific
module that has problems.
-- Erik
|
| 2939.2 | problems dispatching and loading | MICROW::LANG | | Wed May 06 1992 22:00 | 24 |
|
The reason I thought the tables were corrupt was that when I added
entry points, loaded the dap, and tried to dispatch I get an abort.
I've done this successfully before. When I bring the AM up in debug,
it breaks at validate_verb or valid or validate_partition. The
verbs and partitions look fine in the mar file though.
Now, in addition,
I'm getting the following errors:
DAP> update class tpcontroller from mcc_tps_am_tpcon_srvc_if.com
%MCC-E-NOENTITY, no corresponding entity instance exists
DAP> load class tpcontroller from mcc_tps_am_tpcon_srvc_if.com
%MCC-E-ENTEXIST, specified entity definition exists already
DAP> delete class tpcontroller
%MCC-E-NOENTITY, no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
DAP> exit
The exit hangs. The exit was hanging before, for a loong
time, so I finally did a control-c. Now it seems like its corrupt.
Bonnie
|
| 2939.3 | Looks like you have a corrupted dictionary... | DFLAT::PLOUFFE | Jerry | Thu May 07 1992 13:38 | 13 |
| Bonnie:
The symptoms that you are seeing in DAP point to a corrupted main
dictionary file. What version of DECmcc are you running?
There is no way to recover from this corruption asside from restoring
a backup copy of the dictionary files in the /usr/mcc/mcc_system directory.
- Jerry
P.S. v1.2 contains features in DAP that (hopefully) will prevent the
dictionary files (especially the main file mcc_fdictionary.dat)
from being corrupted.
|
| 2939.4 | more information | MICROW::LANG | | Mon May 11 1992 09:37 | 19 |
| > The symptoms that you are seeing in DAP point to a corrupted main
> dictionary file. What version of DECmcc are you running?
Do you mean mcc_fdictionary.dat? We're running
MCC 1.2 EFT.
> There is no way to recover from this corruption asside from restoring
> a backup copy of the dictionary files in the /usr/mcc/mcc_system
>directory.
So should all 4 dictionary files be restrored?
2 fdictionary files
2 meta files
If we have them on another system, is it possible to
copy the 4 files over?
thanks,
Bonnie
|
| 2939.5 | Need dictionary and parse tables | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Mon May 11 1992 11:31 | 25 |
| > > The symptoms that you are seeing in DAP point to a corrupted main
> > dictionary file. What version of DECmcc are you running?
>
> Do you mean mcc_fdictionary.dat? We're running
> MCC 1.2 EFT.
Does this mean T1.2.4, or T1.2.7? On VMS, the main dictionary is
mcc_fdictionary.dat. On ULTRIX, there is both .dat and .dat.dir.
You will probably need the corresponding parse table as well
(mcc_fdictionary.bpt). The dictionary files are sparse files, so if
be careful copying them. The copies may require more disk space.
> > There is no way to recover from this corruption asside from restoring
> > a backup copy of the dictionary files in the /usr/mcc/mcc_system
> >directory.
> So should all 4 dictionary files be restrored?
>
> 2 fdictionary files
> 2 meta files
The meta files are read only, so it is unlikely that they have been
corrupted. You should only need the 2 dictionary files and the parse tables.
-- Erik
|