| Re .0:
>
>DAP> delete class tpcontroller
>DAP> load class tpcontroller from mcc_tps_am_srvc_if.com
> %DAP-I-CMD_FILE, Command file: mcc_tps_am_srvc_if.com
>DAP> exit
>%MCCPTB-F-LOG, Unable to create output log (.LOG) file.
When exiting DAP, the parse tables are updated automatically. The V,E,A t-uples
processed are written to a log file with name mcc_fdictionary.log in your
MCC_SYS_LOCATION directory.
The error you get means that you have no write access to this file, either
because you have no write access to the MCC_SYS_LOCATION directory or to
the mcc_fdictionary.log file (if it exists).
An annoying consequence of this is that you have exited the DAP without
updating your parse tables, and so you need to rebuild them from scratch
by using the REBUILD command under mcc_dap.
A question for the MCC people : are there any mechanism to ensure that the
parse table and dictionary are correctly synchronised ?
Regards.
Pierre.
|
| Re 2011.2
I have read 2006.*. It does not seem to contain an answer to my question.
So, I'll try to be more precise :
- you enter DAP
- you do some modifications (delete, load, augment,...)
- you exit the DAP without updating the parse tables
(on error as mentionned in .0, killed, or something like that)
At this time :
1/ Is there a way to know that your parse tables are out-of-date ?
2/ If you enter DAP again and exit, will the DAP "remember" that the
parse tables need to be updated ?
3/ Is there a way, apart from the rebuild command to update the parse
tables ?
I know this is a minor issue, but when you implement new features you have
new questions, new problems...
Thanks for your help.
Regards.
Pierre.
|
| RE: 2011.3
Pierre:
Thanks for taking the time to be more specific.
Q: 1/ Is there a way to know that your parse tables are out-of-date ?
A: Regretably, no.
Q: 2/ If you enter DAP again and exit, will the DAP "remember" that the
parse tables need to be updated ?
A: Again, regretably, no.
Q: 3/ Is there a way, apart from the rebuild command to update the parse
tables ?
A: If you can remember what changes you made the last time, you might be
able to just do them again. For example, if you completed a LOAD
command before the error occurred, you could just do an UPDATE command
with the same DAP command file, and then just EXIT to cause a partial
update of the parse tables.
But in general, it is safest to execute a rebuild command to make sure
that the parse tables are in synch w/ the main dictionary file.
> I know this is a minor issue...
Actually, this is probably more important than you say. I'll record this
as a suggestion for later releases so that it doesn't get lost in the
shuffle.
- Jerry
P.S. Note 2006.0 has alleviated another kind of synch problem in that now
the main dictioanry file and parse table file are treated as a set that
must be manipulated in tandem. That is, they now must both be in the
same physical directory, where before, because of search lists, they
could have been in separate directories.
|