| 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 |
Can you change an identification number of an entity in the dictionary? When we use the update command in dap after we have changed an identification number in the .ms file the dictionary gets currupted. Is this a problem with the update command or a limitation of MCC, i.e. you are not allowed to do this? Larry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 146.1 | Any Dictionary corruption is a bug | TOOK::GUERTIN | Wherever you go, there you are. | Thu Jun 07 1990 14:42 | 20 |
DAP is not supposed to corrupt the dictionary under any circumstances.
The only time I've ever seen a dictionary get corrupted is when someone
does a control-Y (or control-C) in the middle of a Load or Update.
This is a bug which will get fixed as soon I have the time.
Update is meant to replace an entire MS with another MS. In fact, all
it does is delete the entity class you specify in the command, and
then do a Load for the command file you specify. DAP does not
currently support "zapping" an entity instance identifier code. The only
way you can do this is to delete the entire entity and add another one.
There was a RENAME command but no one ever asked for it and no one ever
used it, not even me (the implementor). Last month I remembered that
such a thing once existed, so I tried it but it didn't work (not
surprising, since it was never tested).
To summarize, if you can corrupt the dictionary simply by updating it with
a new entity identifier code, then that would be a bug.
-Matt.
| |||||
| 146.2 | Not a bug. | ASD::LSMITH | Fri Jun 08 1990 12:12 | 8 | |
We have found the problem we were having. Once we realized the update was deleting the whole entity class then re-loading it from the command file it was easy to determine what was going wrong. Thanks for the response, Larry | |||||