[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2011.0. "MCCPTB-F-LOG error on BSD field test version" by MICROW::LANG () Tue Dec 31 1991 01:32

I'm having a problem getting an AM I've written to run, since installing
    the official BSD internal field test version of mcc.
    
    I get an error exiting the dap, as follows.  Any ideas about
    what should be changed?
    
    	thanks,
    
    		Bonnie

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.
glaive.tay1.dec.com> pwd

T.RTitleUserPersonal
Name
DateLines
2011.1file protection problemTAEC::LAVILLATTue Dec 31 1991 06:0326
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.
2011.2Might want to read note 2006.0DFLAT::PLOUFFEJerryTue Dec 31 1991 11:028
  Pierre:

    Try reading note 2006.0 to see if this answers any of your questions.

    If not, please be more specific with your questions, and I'll give them
    a shot.

                                                                      - Jerry
2011.3precisions...TAEC::LAVILLATThu Jan 02 1992 05:2031
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.


2011.4Specific questions, specific answers...DFLAT::PLOUFFEJerryThu Jan 02 1992 10:2940
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.