Conference azur::mcc

31.0. "Suspected error in mcc$sample_am_auto_tools.com that caused a lot of problems." by BYBLOS::TAMER () Fri Dec 08 1989 16:56

I installed the new MCC T1.1.0 kit.  I tried the new command procedure
mcc$sample_am_auto_make.com (which calls mcc$sample_am_auto_tools.com).

Now entity sample does not dispatch in the TRM.  Sample's code in T1.0 was 43
and in T1.1 it is 15.  So I suspected a code mismatch. Looking into 
mcc$sample_am_auto_tools.com, I find the following:  

    update class sample from sample_am_service_interface.com
    update class sample subclass line from sample_am_mgmt_interface.com

I think this should be ... from mcc$sample_am_svc_interface.com and
                       ... from mcc$sample_am_mgmt_interface.com, respectively.


The problem is: the dictionary is being updated with the old version of sample
while the dispatch table has the new code of sample.

Having tried the correction, DAP does not take it. It responds to the update
command with the error message:

  %MCC-E-NOENTITY, No corresponding entity instance exists.

I tried to rebuild the dictionary. So, I set default to MCC$SYSTEM, and
executed MCC$BUILD_DICT.COM.  Funny thing happens. This command procedure 
deletes MCC$DICTIONARY.DAT, tries to build a new one, then dies in the middle
of rebuilding it with the following error(shown with some preceding text):


DAP> USE CLASS Mcc -
_DAP>    SUBCLASS control_fm
DAP> USE ATTRIBUTE_PARTITION Characteristics
DAP> !  Attribute List
DAP> SET DEFINITION CODE 16 TYPE LU COUNT 2 LENGTH 4 -
_DAP>   VALUE  -
_DAP> 2 1
%RMS-E-DNF, directory not found
%SET-E-SEARCHFAIL, error searching for SYS$COMMON:[MCC]MCC$DICTIONARY.DAT;
-RMS-E-FNF, file not found


Now I lost the dictionary, and I cannot rebuild a new one.

I will wait for some help before I attempt a new installation.

Thanks,
Phil

    
    It looks like there is a problem with the .COM, with the update portion
    of that SAMPLE thingie.  Sorry, we'll look into that.
    
    The Global Entity did change, but you should be able to run 
    MCC$BUILD_DICT.COM.  It appears that you haven't got the privs that you
    need to create the new dictionary.  Assert more privs and try again,
    you should be able to build up a new dictionary with all the right 
    values, so that you can get running again.
    
    Let us know what happens.
    
    

Phil,

    Thanks for bringing the problem with the .COM file to our attention.

    You are right, the modifications made to the
    MCC$SAMPLE_AM_AUTO_TOOLS.COM file to reflect the the SAMPLE AM's new
    file names were done incompletely.  The .COM file has been edited and
    tested for the next release.

    
Darryl
    

MCC$BUILD_DICT.com works.  The way DECmcc was installed on our cluster, it runs 
only on a certain node. I executed MCC$BUILD_DICT.COM from another node and 
that's why I got the error in .0 but now the dictionary is rebuilt. 

I will try the fix in mcc$sample_am_auto_tools.com to see if it now works.

Thanks for your replies,
Phil