| RE: .0
First of all, let me say that I tried to reproduce your problem (using the
DOMAIN class) but was unsuccessful. I need more info:
1.) A log of the exact DAP commands executed.
2.) In the log include the following commands:
a.) Do an "Env" command before running DAP to show me your
environmental variables.
b.) Do appropriate SHOW commands so that I can see the state
of the dictionary before and after the load and update
commands.
3.) You might need to send me the actual DAP command files (not the .MS
file just yet) you are using.
How long did you wait when you thought DAP hung? If you are using a full
dictionary for your updates, it might take a long time to do a partial update
-- please wait at least 5-10 minutes if you can.
Why were the DAP command files for the LOAD command different from the one
used for UPDATING the class?
Please send as much of this information to me directly at (molar::plouffe)
or call me at DTN: 264-4913.
Finally, concerning your questions...
> My Questions are as follows :-
>
> ...
>
> 3: Does the delete option still exist it appears to work but
> is not documented ( if it ever was ? )
I can't answer your first two question yet, because I can't reproduce your
problem, but I can answer the third.
Yes, the DELETE command exist, and it is not longer any big secret, and
yes, it remains undocumented. I just fixed two bugs in the DELETE command
and I know of two more, so it will not become a documented command until
after I clean up the known problems and I am confident that it works well.
If you need to use it, contact me directly and I'll fill you in on the
command syntax, known problems and all the appropriate disclaimers that,
of course, will deny any official responsibility on our part! ;)
- Jerry
|
| Thanks Jerry,
I think all the problems mentioned in the base note were caused by me
typing a control-C when mcc_dap appeared to hang.
After a load command, when dap exits then a message appears quickly
giving the impression that things are working. If I do an update and
then an exit no message appears for 15 minutes. This has obviously
confused the hell out of me!.
If I do a control-c this appears not to clean up properly and leaves
the dictionary in an indeterminate state.
My problems occur during an installation script of our software, if the
screen just goes blank for 15 minutes I think the user will do the same
as me and control-c the installation.
If you need the .com file etc then mail me direct MINDER::PORTEOUSJ
Thanks John
|
| John:
I think I understand your confusion.
When you execute an UPDATE command, the first thing DAP tries to do is
to DELETE the class you specified. This can take a long time and no working
message is displayed. After the delete finishes, the new file is loaded.
This stage does produce a working message.
When you execute a LOAD command, DAP doesn't have to DELETE any class,
so it immediately tries to load in the new file and immediately displays
a working message.
I agree that this is confusing and I will add this problem to our list.
Control C is indeed very dangerous in DAP especially if in the middle of a
LOAD, UPDATE or AUGMENT command. There is a warning in the release notes
about this.
Your best bet right now is to start with a clean dictionary and re-execute
your installation without cancelling the program. If you can, time it and
post the results here. We are working on performance improvements and could
use this additional data.
- Jerry
P.S. It shouldn't be necessary for me to get your DAP command files.
|