Conference iosg::all-in-1_v30

2102.0. "Changing nodenames to cluster alias" by ADOVS9::SYMON (inFamy Soon) Sun Jan 17 1993 15:29

    A site running ALL-IN-1 V3.0 on a VAXcluster has finally decided to
    define a cluster alias.

    To take advantage of the cluster alias, we are going to perform the
    following steps (largely pinched from Tony's book!) after the alias has
    been defined.  Have I forgotten anything?

    0. BACKUP!!!

    1. OA$PRIMARY_NODE
       Reboot all nodes to let A1V30START.COM redefine this correctly.

    2. PROFILE.DAT
       Make sure the NODE field is blank unless the user's mail destination
       is VMSMAIL or VAXMAIL.  Change the NODE field for these users to the
       cluster alias.

    3. NETWORK.DAT
       Delete all references to users from the individual nodes.  This
       will leave any special entries such as X.400 addresses.  Rename this
       file.  Generate a new Network Profile from the User Profile.  Use
       CONVERT to merge the two files together.

    4. MNODES.DAT and NETWORK.DAT on Remote Nodes
       Modify MNODES.DAT on all remote nodes which obtain Network Profile
       information from the cluster.  Delete entries for the individual
       nodes and create an entry for the cluster alias.  Delete all
       references to users on individual nodes from NETWORK.DAT and run the
       UA housekeeping procedure to obtain the new records from the
       cluster.

    5. MAILbus on Remote Nodes
       For each individual node do
       MRMAN> DELETE node
       MRMAN> ADD node/REPLACE=""

    6. Distribution Lists and Nicknames on Remote Nodes
       Modify system distribution lists.  Advise users to update personal
       distribution lists and nicknames.

    7. DDS
       DDS is installed but not used at this stage (OA$DDS_PRIME = 0). 
       Rename the ALL-IN-1 user agent in DDS and in
       OA$DATA_SHARE:UAPASSWORD.DAT.  There shouldn't be any subscribers to
       worry about.

    8. Notes Conferences
       They only use conferences maintained by and accessed through a
       special application.  The nodename is not used in the conference
       location but is used for member access.  Use a script to modify the
       access field of all members of all conferences.
    
    
    Phew!
    FS

    >> 3. NETWORK.DAT
    
    You shouldn't need to create an extra file then merge the two together. 
    Careful use of SMNETINIT.SCP and SMNETUPDT.SCP should enable you to
    populate the file correctly.  But backup the original just in case! :-)
    
    Scott
    

    Just a minor step.
    
    If you ever got around to defining OA$A1_CLUSTER_NODE then you can now
    deassign it, since SYS$CLUSTER_NODE will do the job.
    
    The reason for this logical is to contribute towards a unique
    identifier for a user, for the benefit of document reservation. Ideally
    you should ensure nothing is currently reserved if you define a new
    name for SYS$CLUSTER_NODE but nothing too disastrous will go wrong if
    you don't.
    
    Dick

    I'm not sure I understand step 7 - how do you rename a Useragent in
    DDS?
    
    why not just use a modified version of the steps in the Mail Management
    Guide using <CREATE UAPASSWRD, USERAGENT_POST, MAIL_DIR_CONVERT ETC...
    
    Still if it's in 'the' book ....
    
    Regards,
    
    Andrew.D.Wicks        

    Can't recall it myself... what page, what book?

    Re .1
    Thanks, that will save hassle.
    
    Re .2
    I had never even heard of OA$A1_CLUSTER_NODE!  Was it introduced for
    V3.0 document reservation?  I helped this particular site through
    their V3.0 upgrade so I know that nothing was explicitly done to define
    it.  But I guess it doesn't matter if SYS$CLUSTER_NODE will do.
    
    Re .3
    Useragent name is OA$node$ALLIN1, where 'node' is the nodename or
    cluster alias name.  I assumed I would have to use MBMAN to delete the
    old one(s) and add the new one.  I was then just going to WRITE DELETE/
    WRITE ADD UAPASSWRD and not worry about populating the mail directory
    until they change OA$DDS_PRIME to 1.  (Which at the rate this customer
    assimilates new ideas will be a long time off.  It has taken about two
    years to convince them to define a cluster alias!)
    
    
    FS

    Make sure though that there really are no Subscriber objects with the
    old UA proxy.
    
    Dave.