Conference azur::mcc

    The error you saw when rebuilding the parse tables for TSAM is
    expected.  It has been mentioned in this notesfile many times.  It's
    okay just as it is - the ARP entity has nothing but an identifier
    and a subentitiy (ENTRY).  
    
    I don't think it is related to your other problem.
    
     - Linda

    Hi,
    
    I believe the error may be due to Hardware problems on the system disk
    as we are getting hundreds of errors on it... Maintenance are working
    on it, I'll reinstall the lot when they are finished.
    
    Btw, when I tried to re-install the TSAM, it seems the installation
    procedure does a DAP LOAD and not an update, as I got an "entity
    already  exists" (or words to that effect).
    
    To get back to the original topic, what are the differences in terms of
    files accessed / checked between the FCL PM and the Iconic Map ?
    
    Thanks for your help,
    
    Philippe.

    I have another set of conditions that produces the same response from
    the Iconic map pm.  I have a basic DECmcc installation that was
    working.  I added FDA and SNMP T1.1.  I can now run only from the
    command line mode.  The errors I got during the installation indicated
    that there was something missing from the SNMP am.
    
    Regards,
    
    Glen R.
    

    differences...
    
    The fcl is based upon the parse tables almost completely, with
    the exception of the parsing of constuctor datatypes(sets, records
    and the such).
    
    The iconic map also uses the parse tables, but in a more limited
    manner, mainly to parse the inputed data values and some of the
    qualifiers. For the most part it goes out to the dictionary to
    determine what operations are supported on a class and what information
    belongs in a form.
    
    As to a presentation name missing, that is actually impossible unless
    someone fiddles with the dictionary (or aborts a dap load/update). The
    way things work the presentation name IS the same as the name (with the
    spaces removed) that you see when you do a show in dap. The MSL
    translator simply removes the spaces from the presentation name and
    uses it to build up the "dictionary" name for the entry.
    
    The only things that come to mind, are:
    	- you said that you augmented the dictionary with the historian
    stuff, did you make sure that you did you an old version of the
    augmentation procedures that might have still been hanging around.
    
    	- SNMP has a dictionary problem in there was, else where in the
    conference, a procedure to fix it (an invalid code was entered for the
    set directive causing all other set commands to fail).
    
    	- you said you cleaned up and did a reinstall (or that is what I
    thought I read), but you then said you got a dupliacte entry message on
    the TSAM load command; this means that you didnt' start with a fresh
    dictionary. I would suggest starting with the BMS dictionary again,
    because if you were having disk problems the current files could be
    corrupt.
    
    good luck
    

    I also recently have seen a problem where I can do a directive with
    the FCL but not with IMPM.
    
    I opened a domain and then selected operation directory.
    After a long time... (during which both the Start and Stop buttons
    did not exist - as opposed to being greyed out)
    I got an MCC Unhandeled Service Reply -
    	No such entity: Domain CLAUDI_NS:nssg.lkg2-a Member *
    
    I have installed BMS and the new SNMP and ELM AMs. My understanding
    is that with the new SNMP AM I don't have to fix the dictionary.
    
    s/rob

Rob,

The reason the directory of toplevel domain does not work is that we had
been always sending the in_domain qualifier for every command.  

We have fixed that bug and now do not pass the in_domain qualifier for a top 
level domain, so soon that command will work in the Iconic Map.  

Sorry,
Verna