1 03/31/86  add_volume_registration, avr
  2 
  3 Syntax as a command:  avr -control_args
  4 
  5 
  6 Function: registers a new physical volume.  If the specified logical
  7 volume does not exist, it will be registered as well.
  8 
  9 
 10 Control arguments: The following control arguments pertain to the
 11    registration of a physical volume.
 12 -device_model N, -model N
 13    specifies the Honeywell model number for the disk device.
 14    (Required.)  The following values are valid for N:
 15       VALUE     DEVICE
 16       400       MSU0400
 17       402       MSU0402
 18       451       MSU0451
 19       500       MSU0500
 20       501       MSU0501
 21 
 22 
 23 -location STR, -loc STR
 24    specifies the current location of the disk pack.  This is for
 25    administrative information only.  STR can be any 32 characters
 26    (e.g., "offline--in cabinet 13").  (Default: "uninitialized")
 27 -logical_volume LVNAME, -lv LV_NAME
 28    specifies the logical volume name.  If the specified logical volume
 29    is not already registered on the system, you are queried if the new
 30    logical volume should be registered.  (Required)
 31 -manufacturer_serial STR, -serial STR
 32    specifies the serial number of the physical medium.  This for
 33    administrative information only.  STR can be any 32 characters
 34    (e.g., "Memorex--M234634").  (Default: "unspecified")
 35 
 36 
 37 -physical_volume PV_NAME, -pv PV_NAME
 38    specifies the name of the physical volume to be registered.
 39    (Required; must immediately follow the command name)
 40 -physical_volume_uid UID, -pvid UID
 41    specifies the unique ID of the physical volume to be registered.  A
 42    UID is a string of 1 to 12 octal digits.  Normally, a UID is
 43    generated automatically.  Use -pvid only when recreating a
 44    registration after system failure.
 45 
 46 
 47    The following control arguments are allowed only when registering a
 48    new logical volume.
 49 -access_class MIN_AUTH{:MAX_AUTH}
 50    specifies the AIM authorization of users allowed to attach the
 51    volume.  You can specify the authorization by a minimum and a
 52    maximum authorization value, in which case users at any
 53    authorization in the range are allowed to attach the volume.
 54    Alternatively, you can specify the authorization as a single value,
 55    in which case only users at the specified authorization are allowed
 56    to use the volume.  You must specify the authorization values using
 57    valid site-defined authorization strings (see the print_auth_names
 58    command).
 59 
 60 
 61 -acs_path PATH, -acs PATH
 62    specifies the pathname of the access control segment (ACS) for the
 63    volume.  The ACS itself is not created, but must be created at the
 64    specified path and the desired access control list set (see "Notes"
 65    below).  The name of the entry must be {lv_name}.acs.  If you give
 66    no -acs when registering a public volume, only the volume owner will
 67    have executive privileges (everyone will have read/write privileges,
 68    given proper access to the hierarchy).  If you give no -acs when
 69    registering a nonpublic (i.e., a private) volume, the default ACS
 70    pathname will be >udd>{owner's Project_id}>{owner's
 71    Person_id}>{lv_name}.acs>.
 72 
 73 
 74 -logical_volume_uid UID, -lvid UID
 75    specifies the unique ID of the logical volume being registered.  A
 76    UID is a string of 1 to 12 octal digits.  Normally, the software
 77    automatically generates this ID.  Use -lvid only when recreating a
 78    registration after a system failure.
 79 -owner USER_ID, -ow USER_ID
 80    specifies the user who is to act as the primary volume
 81    administrator.  This user has the privilege of granting executive
 82    access to other users via the ACS, granting read/write access to
 83    others via the ACS (for private volumes), and for setting up volume
 84    quota accounts.  You can give the Person_id or Project_id as "*".
 85    (Default: to use the user's Person_id and Project_id)
 86 -public STR
 87    specifies whether the new logical volume is to be private or public.
 88    STR can be yes (public) or no (private).  (Default: yes)
 89 
 90 
 91 Notes: Physical volume names are restricted to lowercase letters,
 92 digits, and the underscore (_).
 93 
 94 If the logical volume does not exist, you will be queried whether the
 95 volume should be registered as a new logical volume.
 96 
 97 Private volumes must be explicitly attached to a process for access via
 98 the attach_lv command.  You must have rw access to the ACS for private
 99 volumes.  In either case, you must have proper hierarchy access before
100 segments may be read or written.
101 
102 Public volumes do not require attachment to the user's process; thus,
103 all users have read/write access to public volumes (provided there is
104 proper hierarchy access).
105 
106 
107 Access required: You require to have re access to the mdc_priv_ gate
108 and sma to >lv to register new logical volumes or sm to >lv to register
109 new physical volumes.