1 DEVMOVE
  Allows you to move your directory to another device on the system;
  or the cluster.  Your choices of devices are limited to ones which
  are available for public use (e.g. you can't DEVMOVE to the system
  disk) and have more available space than the disk you're presently
  on.  See the "Overview" section for more information.
 
  Format:
 
    DEVMOVE  new-device-name[:]
 
  Note: Be sure to log off the system after the DEVMOVE operation is
  complete.  See the sections entitled "Overview" and "Examples" for
  further details.
 
2 Parameters
 
  new-device-name[:]
 
  Specifies the name of the "new" device your directory will reside
  on.  A list of available devices can  be generated with the /LIST
  qualifier.
 
2 Qualifiers
 
/LIST
 
  /LIST[=file-spec]
 
  Outputs a list of available devices which can support your direc-
  tory to the file "file-spec."  The list contains the device name,
  the number of free blocks for each device listed, and how much of
  the device has been utilized.  If no file-spec is specified, then
  the list is written to the current output device (which is usual-
  ly assigned to the terminal).  You may choose any one of these as
  your new device.
 
2 Overview
 
  The DEVMOVE utility moves your directory from the device you're on
  presently to another one of your choice.  The main reason for this
  is if you're on a device which is full or nearly-full, there might
  not be enough space to accommodate any new "large" files even tho-
  ugh you have sufficient diskquota resources to create the file(s).
  When new accounts are created, they're placed on the devices which
  have the most free space at the time.  The devices fill up at dif-
  ferent rates, depending on who uses them and what's being  stored.
  So, while two devices may support the same number of accounts, one
  might saturate faster than the other over time.  DEVMOVE gives you
  the ability  to transfer to an unsaturated device very simply.  If
  you discover that the amount of free  space on your present device
  is low, you may elect to move to another.
 
  Previous to DEVMOVE, the System Manager  would either have to arb-
  itrarily move people to other devices or take other actions when a
  disk becomes saturated.  Voluntary redistribution via DEVMOVE will
  help alleviate this problem.  Some restraint  should be exercised,
  however.  Don't get the idea that you  must constantly move to the
  disk with the largest amount of free space.  This  is analogous to
  moving from aisle to aisle at the checkout counter because the one
  next to you "seems to be moving faster."  You should consider mov-
  ing only if the free space is very low (less than 10,000 blocks is
  considered very low).  One or two moves throughout the life of the
  account is the most you should ever expect.
 
  Also, be aware of the consequences of moving around.  All files or
  command procedures which specifically reference files in your dir-
  ectory will have to be changed to reflect  your *new* device name.
  Anybody else on either system who might reference  your files will
  have to be notified of the change as well.  Utilities such as MAIL
  and SEND/RECEIVE will not be affected however.  In short, it's not
  an effortless  change, especially if you  insist on making a habit
  of it.
 
  The move process involves transfering your directory on the device
  you're presently on to another.  Unfortunately, it's not as simple
  as moving your directory header to the other device.  Every one of
  your files has to be moved - individually.  It is for this reason,
  as well as others, that "frequent" use of DEVMOVE is  discouraged.
  Say, for example, your UIC is presently [136,731] and your device/
  directory is DISK$E:[ZZ12].  Noticing that device DISK$E: has less
  than 10,000 free blocks (a block is 512 bytes), you decide to move
  to a device with more room.  But which one?  DEVMOVE allows you to
  move to any device that is available for public use (certain disks
  are off-limits), and has more free space than the disk you're pre-
  sently on.  DEVMOVE/LIST will generate a list of choices,
 
    $ DEVMOVE /LIST
    Device name     Free blocks     Pct Full
    -----------     -----------     --------
    DISK$A:              591939          51%
    DISK$B:             1798062          24%
    DISK$C:             2198140           7%
    DISK$D:             2191422           7%
    DISK$E:                1111          99%
    DISK$F:             1565952          34%
    DISK$G:             2178405           8%
 
  The obvious choice would be the ones with the largest free blocks,
  but you are free to choose from any of  the ones listed.  You dec-
  ide on devmoving to DISK$C:.  DEVMOVE's task is to move the entire
  contents of your current directory DISK$E:[ZZ12] to DISK$C:[ZZ12].
  If you've ACCMERGED your accounts together on every system  in the
  cluster, then every one will inheret your new device/directory/uic
  information as well.  Remember, the more files you have the longer
  DEVMOVE will take to complete.
 
  Do not use DEVMOVE 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 on MAX using
  the CHKOUT facility and run DEVMOVE, you may not be able to access
  your CHKOUT space afterwards.  In this case, wait until your space
  has expired before running DEVMOVE.
 
  Once the move is complete, log out and in again and make sure that
  your directory on your new device is complete.  Refer to the sect-
  ion entitled "Examples" for  more information on how to  interpret
  the output of DEVMOVE.  If any problems arise they should be taken
  to the System Manager as soon as possible.
 
2 Examples
 
  This example uses the scenario outlined in the "Overview" section.
  Since DEVMOVE 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 DEVMOVE session use the SET HOST/LOG facility as follows,
 
    $ SET HOST/LOG=DEVMOVE.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, 
  
    R$ DEVMOVE /LIST
    Device name     Free blocks     Pct Full
    -----------     -----------     --------
    DISK$A:              591939          51%
    DISK$B:             1798062          24%
    DISK$C:             2198140           7%
    DISK$D:             2191422           7%
    DISK$E:                1111          99%
    DISK$F:             1565952          34%
    DISK$G:             2178405           8%
    R$ DEVMOVE DISK$C:
    Move to device DISK$C:? [YES]:
 
  Type in the command "DEVMOVE /LIST" after the "$" prompt  to get a
  list of all choices of devices.  After making your decision, enter
  the command "DEVMOVE" followed by the name of the  device.  If you
  really want to perform this move enter  either "YES" or a carriage
  return.  If you don't want to perform this move, enter "NO".  Upon
  confirmation, DEVMOVE  will then  begin transfering your directory
  from your present  device to the one of your  choice.  During this
  phase, a message will be displayed for each file being transfered,
 
    %MOVE-I-STARTMOVE, beginning move operation - please stand by...
    %BACKUP-S-CREDIR, created directory DISK$C:[ZZ12]
    %BACKUP-E-OPENIN, error opening DISK$E:[ZZ12]DEVMOVE.OUT;1 as input
    -SYSTEM-W-ACCONFLICT, file access conflict
    %BACKUP-S-CREATED, created DISK$C:[ZZ12]MAIL.MAI;1
    %BACKUP-S-CREATED, created DISK$C:[ZZ12]FOO.BAR;86
    %BACKUP-E-OPENIN, error opening DISK$E:[ZZ12]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; DEVMOVE.OUT;1 was opened by the RECORDing
  utility.  You should expect the RECORDing file to not transfer but
  all other files should.  After the file transfer  phase has compl-
  eted you will see a few more informational messages as the device/
  directory/uic pointers are modified on the other systems,
 
    %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
    %MOVE-I-SUCCMOVED, move operation completed to device DISK$C:
    %MOVE-I-LOGOFFSYS, log off the system - see documentation
    R$ LOGOUT
 
  The last message, "move operation completed..." confirms  that the
  DEVMOVE 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  DEVMOVE.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).
 
  Now, log out and in again so that all of the VMS-internal pointers
  for your current session will be set to your new device/directory/
  uic values.  Check to see that your directory is exactly the same,
  except for the device name, as it was before.  If you have ACCMER-
  GED your accounts log into all of them and verify that the device/
  directory/uic is the same.  Type "SHOW PROCESS" at the terminal to
  to get this information,
 
    $ SHOW PROCESS
    26-JAN-1989 15:50:13.89   User: 12345678   Process ID:   20C006F7
                              Node: MAVEN      Process name: "12345678"
 
    Terminal:           LTA186:  (MAVEN1/LC-1-6)
    User Identifier:    [136,731]
    Base priority:      4
    Default file spec:  DISK$C:[ZZ12]
 
    Devices allocated:  MAVEN$LTA186:
 
  make sure that the "Default file spec" values match on each system
  (i.e., they should all state a Default file spec  of DISK$C:[ZZ12]
  in this example). If they do not, then notify the System Manager.
