1 ACCMERGE
  Allows you to merge the files and device/directory/uic information
  together for (each of) your accounts.  Once merged, you'll be able
  to access your files from any system in the UCSVAXcluster in which
  have an account, since they'll all access the same directory.
 
  Format:
 
    ACCMERGE
 
  Notes: Make sure to log off all systems after the merger operation
  is completed.  See the sections entitled "Overview" and "Examples"
  for further details.  THIS MERGER PROCESS IS IRREVERSIBLE.  Please
  read the help text carefully before using this utility.
 
2 Qualifiers
 
/LIST
 
  /LIST[=file-spec]
 
  Outputs a list of the "merge" status of your accounts on all nodes
  in the cluster (if they've been  created) to the file "file-spec."
  The status returned will be one of the following:
 
    o  "Not created or has expired" - an account under the same name
       as the one one on this node has not  been created or has exp-
       ired due to non-use.
 
    o  "Already merged with account on this node" - the two accounts
       already share the same device/directory/uic information.
 
    o  "Not merged with account on this node" - the accounts haven't
        been merged together.
 
  If no file-spec is specified, then the list is written to the cur-
  rent output device (which is usually assigned to the terminal).
 
2 Overview
 
  The ACCMERGE utility merges the files and device/directory/uic in-
  formation of your VAXaccounts together.  The reason for doing this
  is so your accounts (one on each system in the cluster) will refer
  to the same directory, and therefore share the same files.  One of
  the benefits is that if one system goes down, you can log into an-
  other system and continue  working.  Also, you won't have to main-
  tain independent directories (i.e. keeping up multiple LOGIN.COM's
  duplicate data, etc...)  Everything will be centralized, including
  your mail database.  See the topic Vax_Mail for information on the
  side-effects of ACCMERGE and the VMS Mail facility.
 
  You must have an account under the same name on all systems  to be
  able to use ACCMERGE.  Typing ASSETS at the terminal will show you
  your account name.  Do this on each system in the cluster you have
  an account, and make sure they are the  same.  Do not confuse your
  your account name with your  username (the one you log in  under).
  ACCMERGE  can also show you the "merge" status of your accounts on
  all nodes in the cluster (if they've been created),
 
    $ ACCMERGE /LIST
    Node name      Merge Status
    ---------      ------------
    MAX            Not merged with account on this node
    MAVEN          Not merged with account on this node
 
  The merger process involves transfering all of the files from your
  accounts on the other nodes into a subdirectory in your account on
  this system and then modifying the other accounts to refer to this
  directory instead.  Say, for example, you have an account 12345678
  on all nodes with a device/directory of DISK$F:[AC31] on VAX1, and
  DISK$E:[PK87] on MAX and MAVEN (assume your MAX and MAVEN accounts
  have already been merged).  If ACCMERGE is run on VAX1, the  files
  in PK87 will be placed in a subdirectory of AC31,
 
                            DISK$F:[AC31]
                                  |
          +---------------+-------+-------+---------------+
          |               |               |               |
     [AC31.PK87]           {your existing files under AC31}
 
  In other words the entire contents of DISK$E:[PK87] will be placed
  within the subdirectory DISK$F:[AC31.PK87]. Tech. Note #1 explains
  subdirectories in greater detail.  The opposite would have happen-
  ed if you ran ACCMERGE on MAX or MAVEN (AC31 would be a subdirect-
  ory of PK87).  It therefore may be advantageous to determine which
  account has the least files, and enter the ACCMERGE command on an-
  other system, so that a minimum number of files are transfered be-
  tween directories.  Remember, the more files there are, the longer
  ACCMERGE will take to complete.
 
  Do not use ACCMERGE if you have batch jobs or procedures currently
  running which  either create or read data files in your directory.
  These files may not be transfered - and therefore could be lost or
  destroyed.  Wait until all such jobs and procedures have finished.
  Also be aware that  if you have "checked out" disk space using the
  the CHKOUT facility and perform an ACCMERGE you may not be able to
  access your CHKOUT space  afterwards.  It would be better (in this
  case) to run ACCMERGE on after the CHKOUT space has expired.
 
  Once the merger operation is completed, log off and then back into
  all systems and verify that the  [AC31.PK87] subdirectory (or else
  the [PK87.AC31] subdirectory, depending  on which  system ACCMERGE
  was entered) exists and is complete.  Refer to the section entitl-
  ed "Examples" for more information on how to use and interpret the
  output of an ACCMERGE. If any problems arise, they should be taken
  to the System Manager as soon as possible.
 
2 Examples
 
  This example uses the scenario described in the "Overview" section
  with an ACCMERGE command initiated under account 12345678 on VAX1.
  Since ACCMERGE displays messages (and errors if any) to the screen
  as it progresses, it is recommended that a file copy of the output
  be produced - in case any problems arise.  To make a file copy  of
  the ACCMERGE session use the SET HOST/LOG facility as follows,
 
    $ SET HOST/LOG=ACCMERGE.OUT VAX1
  
        Welcome to VAX1.  Please log in.
  
    Username: 
    Password: 
  
  The system will prompt you for your username and password.   Enter
  them as you would when logging into the system. Next, 
  
    $ ACCMERGE /LIST
    Node name      Merge Status
    ---------      ------------
    MAX            Not merged with account on this node
    MAVEN          Not merged with account on this node
    $ ACCMERGE
    Password for 12345678 on MAX:
    Password for 12345678 on MAVEN:
    Merge accounts together? [YES]:
 
  Type in the command "ACCMERGE /LIST" after the "$" prompt to get a
  list of which accounts have been merged.  If it states that you're
  accounts are not yet merged together, type the command "ACCMERGE".
  ACCMERGE will then prompt for your passwords on the other systems.
  Enter your passwords for 12345678 on MAX and MAVEN  (they will not
  appear when entered).  If each password  matches exactly, then you
  will be prompted for confirmation.  If you really want  to perform
  this merger enter either "YES" or a carriage return.  If you don't
  want to perform this merger, enter "NO".  Upon  confirmation,  the
  transfer phase will proceed.  During this phase, a message will be
  displayed for each file being transfered,
 
    %MERGE-I-STARTMOVE, beginning merge operation - please stand by...
    %BACKUP-S-CREDIR, created directory HSC$DUA1:[AC31.PK87]
    %BACKUP-S-CREATED, created HSC$DUA1:[AC31.PK87]MAIL.MAI;1
    %BACKUP-S-CREATED, created HSC$DUA1:[AC31.PK87]FOO.BAR;86
    %BACKUP-E-OPENIN, error opening HSC$DUA6:[PK87]F.F;1 as input
    -SYSTEM-W-ACCONFLICT, file access conflict
            .
            .
            .
 
  the file F.F;1 was opened by a batch job at the time, so it wasn't
  transfered and was lost.  After the file transfer phase has compl-
  eted you will see a few more informational messages as the device/
  directory/uic pointers are modified for 12345678 on MAX and MAVEN,
 
    %UAF-I-MDFYMSG, user record(s) updated
    %UAF-I-DONEMSG, system authorization file modified
    %UAF-I-RDBNOMODS, no modifications made to rights database
    %UAF-I-MDFYMSG, user record(s) updated
    %UAF-I-DONEMSG, system authorization file modified
    %UAF-I-RDBNOMODS, no modifications made to rights database
    %MERGE-I-SUCCMERGD, merge operation completed - use /LIST to list
    %MERGE-I-LOGOFFSYS, log off the system - see documentation
    $ LOGOUT
 
  The last message, "merge operation completed..." confirms that the
  ACCMERGE operation is finished. Enter the command LOGOUT after the
  "$" prompt to terminate the SET HOST session.  Note you will still
  be logged in at this point.  Save this output file ACCMERGE.LOG if
  any error messages (other than the ones explained above) appear or
  if any files were not transfered properly.  The System Manager can
  recover those files if necessary (be sure to mention the recording
  file, it will make the recovery process much easier).
 
  After the accounts are merged you should go through your directory
  and "weed-out" any duplicate or non-essential files since the con-
  tents of two directories are now in one.  This procedure is a must
  if you find that you are over your diskquota limit.  See the sect-
  ion entitled "Resources" for more information on diskquotas.
 
  Also, log into the other systems (if you're already logged in then
  log out and in again) and verify that your device/directory/uic is
  the same for all accounts.  Type "SHOW PROCESS" at the terminal to
  get this information,
 
    $ SHOW PROCESS
    26-JAN-1989 15:50:13.89   User: 12345678   Process ID:   20C006F7
                              Node: MAX        Process name: "12345678"
 
    Terminal:           LTA186:  (MAX/LC-1-6)
    User Identifier:    [123,123]
    Base priority:      4
    Default file spec:  DISK$F:[AC31]
 
    Devices allocated:  MAX$LTA186:
 
  make sure that the "UIC" and "Default file spec" values  match on
  all systems (i.e., they should each  state a UIC of [123,123] and
  a Default file spec of DISK$F:[AC35] in this example). If they do
  not, then notify the System Manager.
 
2 Resources
 
  Your account  resources consists of the total amount of diskquota
  you are allowed to consume (TDISK), how much CPU time (TCPU), and
  how long you can remain  on the system continuously (TCON) before
  being "load leveled."  (See Tech Note #20 for more information on
  load regulation.)  These values can be shown by  typing ASSETS at
  the terminal.  ACCMERGE affects these resources as follows.
 
  Diskquota:
  ----------
  Your Diskquota resource will be computed according to your account
  classification.  For Bronze-class accounts, you'll be granted 1.00
  Megabyte for each merged account on the UCSVAXcluster; for Silver-
  class accounts, you'll be granted 2.00 Megabytes per account up to
  a total of 10.00 Megabytes - the Silver-Maximum limit.  Gold-class
  accounts have no limit.  Using the example in the "Overview" sect-
  ion again, if 12345678 was a Bronze-class account you would have a
  total Diskquota of 3.00 Megabytes.
 
  Also note that if your accounts have been merged and, for example,
  you take a course on VAX 1 which increases your diskquota value by
  1.00 Megabyte, your MAX and MAVEN accounts will also have that in-
  creased diskquota value until the end of the quarter.  These quota
  additions are not subject to the Silver-Maximum cap mentioned abo-
  ve.  After the quarter ends, your Diskquota value will revert back
  to the above-mentioned value.
 
  CPU and Connect:
  ----------------
  Your CPU and Connect time thresholds remain the same on both syst-
  ems.  So, if you have a TCPU value of 5.0 on MAX and 1.0 on VAX 1,
  they will remain the same after the merger.  Only the disk resour-
  ces are shared.
 
2 Vax_Mail
 
  There are a few peculiarities with VAX/VMS Mail and accounts which
  have beem ACCMERGEd together that you should be aware of.  They do
  not, in any way affect your ability to send/receive mail messages.
  The way our cluster is set up currently, each machine operates in-
  dependent of one another.  Each maintains it's own files, and each
  has a unique e-mail  address.  So, if you have an  account on more
  than one system, you have more than one e-mail address.  ACCMERGE-
  ing your accounts won't change this fact.
 
  Whenever a new mail message is received for your account it's pla-
  ced in the file MAIL.MAI in your directory, and a new mail message
  counter is incremented on the machine which received your message.
  Since all of your mail messages are stored in your directory, MAIL
  can read the mail from either system.   Each time you "read" a new
  mail message, the new mail message counter is decremented  on that
  system.  Hence, this counter can get out of whack if you read mail
  messages from the "wrong" system.   Say, for example, you received
  3 new mail messages on VAX1.  The next time you log into VAX1, you
  will be told that there's 3 new mail messages.  But, if you logged
  into MAX, you would  not be informed of  any new messages.  If you
  read your mail on VAX1, the new mail message counter on VAX1 would
  be set to 0 (assuming you read all of the messages) and everything
  would be terrific. However, say you read your mail on MAX instead.
  The MAIL utility would still display all of your messages, but the
  new mail message count would be incorrect, because  the counter on
  VAX1 would still have a value of 3.
 
  There are two ways to get around this "annoyance."  The first, and
  simplest, is to choose one of your accounts  as your mail account.
  By using the SET FORWARD command within  the MAIL utility, you can
  re-route mail messages sent to your account (on any system) to the
  system of your choice.  So, in the above example, you might choose
  VAX1 as your mail  account and set the mail-forwarding  address on
  MAX to send all mail to VAX1.  Then, if you use MAIL on VAX1 only,
  the new mail message counter will never be off.  See the help text
  on SET/SHOW FORWARD (while in MAIL) for more information on how to
  set forwarding addresses.
 
  The other way is to not bother with setting forwarding  addresses,
  and to fix-up the new mail count by hand.  This method can also be
  used to reset the counter any time on  each system.  To reset  the
  counter, type the following,
 
    $ MAIL
    MAIL> READ/NEW
    MAIL> EXIT
 
  Do the above on each system you have an account on the cluster.
