T.R | Title | User | Personal Name | Date | Lines |
---|
2454.1 | Did it ever work? Is this a brand-new installation? | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Fri Feb 28 1992 15:32 | 15 |
|
Livia,
(Q) Did you just install the t1.2.4 kit?
(Q) Are you sure the installation was successful?
(Q) Have you reset any MCC logicals?
o mcc_system
o mcc_specific
o mcc_common
(Q) What are the dates on the files: mcc_common:*fdictionary*.*
/keith
|
2454.2 | I created an example AM | ROM01::PROFETI | Livia Profeti - SWAS Rome | Mon Mar 02 1992 06:43 | 27 |
| > (Q) Did you just install the t1.2.4 kit?
Yes, I did it a month and a half ago, I installed the latest FT version
(I think), the 10th December one.
> (Q) Are you sure the installation was successful?
I think so, I had some problem with some FM, but I replied the
installation and all thinghs were right.
> (Q) Have you reset any MCC logicals?
o mcc_system
o mcc_specific
o mcc_common
All these logicals point to the system directories.
> (Q) What are the dates on the files: mcc_common:*fdictionary*.*
mcc_common:mcc_fdictionary.bpt 8-dec-1991
mcc_common:mcc_fdictionary.dat 8-dec-1991 revised 21-feb-1992
I have to inform you that in the date 21-feb-1992 I tried to create an
example AM and we created an entity (PROVA) with this AM. It was just a
test, but we modified the dictionary for this AM. Now, in addition to
this problem, I get the following error when I start the DECwindows
interface :
- No bitmap for entity PROVA
/livia
|
2454.3 | The Parse Tables must be out of sync (mcc_fdictionary.bpt) | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Mon Mar 02 1992 08:15 | 39 |
| Livia,
The only thing I can think of is the Binary Parse Tables (bpt) are out
of sync with the Dictionary.
>> mcc_common:mcc_fdictionary.bpt 8-dec-1991
>> mcc_common:mcc_fdictionary.dat 8-dec-1991 revised 21-feb-1992
>>
>> I have to inform you that in the date 21-feb-1992 I tried to create an
>> example AM and we created an entity (PROVA) with this AM. It was just a
>> test, but we modified the dictionary for this AM.
Both Dictionary files should have the same date...that is the .DAT revision
date and .BPT creation date should be the same.
When you updated the Dictionary, do you know if the Parse Tables were
successfully updated?
This explains why the Alarms FM isn't working correctly, except if the parse
tables are not properly updated anything could go wrong when you enter
a command to the FCL.
>> Now, in addition to this problem, I get the following error when I start
>> the DECwindows interface :
>>
>> - No bitmap for entity PROVA
You have created a new Global Entity ... the Iconic Map is warning you that
it could not find an Icon diagram for this Global Entity. You can create
your own Icon with DECpaint. There are other notes which describe this
process.
Even though there is no custom Icon for your Global Entity, you can still
access it ... Your Global Entity will be represented by an Icon with a "?"
inside.
/keith
|
2454.4 | Dictionary rebuild ? | ROM01::PROFETI | Livia Profeti - SWAS Rome | Mon Mar 02 1992 10:05 | 15 |
| When I was been updating the dictionary the system had a crash.
In a second time I read the manual and I decided to create my private
dictionary pointed by the logical mcc_system.
This phase was right and it took less time than the previous, but I
think I made an error becouse I couldn't access to the most of standard
AM (phase4).
So I reset the mcc_system logical definition to the standard mode
(system directories). At this point there was the Alarm problem.
Now a collegue of mine is rebuilding the dictionary, do you think this
is correct ?
/livia
|
2454.5 | | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Mon Mar 02 1992 13:01 | 48 |
| RE: .4
>> When I was been updating the dictionary the system had a crash.
A crash while updating the dictionary is bad; almost anything is possible.
If you were executing a Load or Update command, you should execute it
again to be sure the particular entities are defined in the dictionary
properly.
If you did a load command, this time use the Update command ... that is:
DAP> load from myfile.com <== command during the crash
DAP> update from myfile.com <== to reload the dictionary
(the update command will delete any entity-specific data in the dictionary
before re-loading).
>> Now a collegue of mine is rebuilding the dictionary, do you think this
>> is correct ?
Yes this would be best, but expect it to take a long time ... like over
night. When you load or update data into the dictionary, a partial rebuild
is of the Parse Tables is performed. The existing Parse Table (.BPT) is
read and only the entities you have modified in the load/update command
are updated in the Parse Table.
If your Dictionary .BPT and .DAT files are out of sync, you *must* use the
rebuild command. Rebuild will create a new Parse Table file from the
data in the dictionary -- this will take 4 to 8 hours to complete.
DAP> rebuild
If you still have problems .. I suggest that you reinstall the DECmcc kit.
After the installation make a copy of the dictionary and parse tables:
$ set default mcc_common
$ copy mcc_fdictionary.dat mcc_fdictionary.dat-t1-2-4
$ copy mcc_fdictionary.bpt mcc_fdictionary.bpt-t1-2-4
(where t1-2-4 is what ever version of DECmcc you have installed). Making
this copy will eliminate reinstalling DECmcc should you need to restore
the Dictionary. You may want to make the copy onto another disk as the
dictionary file is about 40,000 blocks.
Good Luck and let us know how you make out.
/keith
|
2454.6 | Rebuild was ok | ROM01::PROFETI | Livia Profeti - SWAS Rome | Tue Mar 10 1992 05:57 | 9 |
| Sorry to be so late but I was ill last week.
Rebuild completed and things seem to be ok now, I've got just another
problem but I'm not sure it is related to that situation (Target
entity), I'm going to insert another note about.
Many thanks for you help,
/livia
|