    
    
    
                             MPMGR User's Guide
    
                              Matthew Madison
                  Center for Interactive Computer Graphics
                      Rensselaer Polytechnic Institute
                               Troy, New York
    
    
    Introduction
    
    Large VAXclusters and Local-Area VAXclusters can be a nightmare to 
    manage.  Where creating a MODPARAMS.DAT file for AUTOGEN is a pain 
    on a single VAX, this job is overwhelming when parameters have to be 
    adjusted on all 28 nodes in a full LAVc.
    
    MPMGR (MODPARAMS Manager) is a simple program that can be used to 
    develop MODPARAMS.DAT files for every node in a cluster quickly and 
    easily.
    
    
    The MPMGR Configuration File
    
    The key to using MPMGR is the MPMGR configuration file.  The 
    configuration file lists the SCS node name, SCS system ID, and 
    system root specification for each node in the cluster, along with a 
    list of file names from which MODPARAMS information is drawn.
    
    An example of an MPMGR configuration for a LAVc might be:
    
    --------------------------------------------------------------------------
    BOOT1,1025,BOOT1$DUA0:[SYS0.],BOOT_MEMBER,BOOT1_SPECIFIC,WPSPLUS
    BOOT2,1026,BOOT2$DUA0:[SYS0.],BOOT_MEMBER,BOOT2_SPECIFIC,WPSPLUS
    SAT01,1027,BOOT1$DUA0:[SYS1.],SATELLITE,VAXSTATION_II
    SAT02,1028,BOOT2$DUA0:[SYS1.],SATELLITE,GPX
    SAT03,1029,BOOT1$DUA0:[SYS2.],SATELLITE,GPX
    --------------------------------------------------------------------------
    
    The first item in each line is the SCS node name for the node, the 
    second is the SCS system ID, and the third is the system root 
    specification for the node.  The items that follow are names of 
    files in which MODPARAMS data is kept.  Up to 16 files may be 
    specified per node.
    
    When MPMGR builds a MODPARAMS file for a node, it starts by writing 
    a header comment that lists the date and time and the SCS node name 
    of the node for which it is creating the MODPARAMS file.  It then 
    writes the SCSNODE and SCSSYSTEMID definitions, as obtained from the 
    configuration file.
    
    MPMGR then starts copying data, uninterpreted, from the file 
    GENERIC.MOD (if it exists in the current default directory) into the 
    MODPARAMS file, followed by the data stored in the files listed in 
    the configuration file (using .MOD as the default extension for the 
    files).
    
    Comments may be included in the configuration file by preceding them 
    with exclamation points.  Configuration records may take up more 
    than one line by ending each line but the last with a hyphen.
    
    
    Using MPMGR
    
    MPMGR should be set up as a "foreign" command:
    
    	      $ MPMGR := $disk:[directory]MPMGR
    
    Then, you invoke MPMGR as follows:
    
    	      $ MPMGR [file-spec]
    
    	      file-spec		  File specification of the 
                                  configuration file.  The default, if 
                                  omitted, is SYS$DISK:[]MPM_CONFIG.CFG.
    
    MPMGR can take the following qualifiers:
    
    	      /[NO]TEST		  By default, MPMGR writes the 
                                  MODPARAMS.DAT files directly at each 
                                  node's SYS$SYSROOT:[SYSEXE] (/NOTEST). 
                                  /TEST causes MPMGR to create the files 
                                  in the current default directory using 
                                  the SCS node name as the file name.
    
    	      /SELECT=(node...)	  Allows selective creation of MODPARAMS 
                                  files.  The node specification(s) may 
                                  contain wildcard characters.  The 
                                  default is to create MODPARAMS files 
                                  for each node in the configuration 
                                  file.
    
    
    Contacting the Author
    
    Comments, suggestions, and questions about MPMGR can be directed to 
    the author via electronic mail at one of the following addresses:
    
    Internet: madison@cicgj.rpi.edu
    BITNET:   madison@rpicicge
    
    
    Copyright Notice
    
    COPYRIGHT © 1988, RENSSELAER POLYTECHNIC INSTITUTE.  ALL RIGHTS 
    RESERVED.  Permission is given to redistribute this software for 
    non-commercial purposes provided no there is no charge for the 
    distribution beyond handling and materials costs.
    
    DISCLAIMER: This software is provided "as is".  Neither the author 
    nor Rensselaer Polytechnic Institute makes any guarantee as to the 
    suitability, usefulness, performance, or security of the software.
