Conference azur::mcc

840.0. "Clusterwide install, but system specific use..." by ULTMAT::BELANGER (A ROSE by anyother name, would not be manageable) Mon Mar 25 1991 13:24

    
    	I'm installing DECmcc BMS and the Toolkit on an "unspoiled" LAVc.
    This LAVc is doing to be used by a number of engineers for development
    of MM for DECmcc.  During the course of the project, various engineers
    will be "toying" with the Dictionary.  I'd like to have this toying not
    affect the other engineers.  As a result, I'd like to have each system
    within the cluster have its own set of data files (MIR, dictionary,
    etc.).  I'd like to know if the following list of files are the ones
    which will allow for this asynchronous development to occur (NOTE: the
    directory information is where the files are located after VMSINSTAL):
    
    		SYS$COMMON:[MCC]MCC_ALARMS_ATTRIBUTE_MIR.DAT
    		SYS$COMMON:[MCC]MCC_ALARMS_INSTANCE_MIR.DAT
    		SYS$COMMON:[MCC]MCC_DEFINITION.DAT
    		SYS$COMMON:[MCC]MCC_DICTIONARY.DAT
    		SYS$COMMON:[MCC]MCC_DISPATCH_TABLE.DAT
    		SYS$COMMON:[MCC]MCC_META_DEFINITION.DAT
    		SYS$COMMON:[MCC]MCC_META_DICTIONARY.DAT
    		SYS$COMMON:[MCC]MCC_MIR_ATTRIBUTE.DAT
    		SYS$COMMON:[MCC]MCC_MIR_DIRECTORY.DAT
    
    Thanks for your assistance.
    
    ~Jon. Belanger

I'm not sure if that's all the files, but you might want to look into the
use of the MCC_SYSTEM, MCC_SPECIFIC and MCC_COMMON logicals, which parallel
SYS$SPECIFIC and SYS$COMMON under VMS.  Will those give you sufficient control?

Your missing the parse tables, mcc_ptb_parser.bpt.

Also note that how to do this is described in detail in the guide to writing
an access module. Also please understand that the full dictionary is huge and
that you might want to use the  development files provided in the SYS$EXAMPLES
MCC sub-directory.

jill