device-name[:][,...]
Specifies the physical device name or logical name of the device
on which the volume is to be mounted. On a system where volumes
are not connected to HSCs (hierarchical storage controllers), use
the following format:
ddcu:
The dd describes the device type of the physical devices used.
For example, an RA60 disk drive is device type DJ, and an RA80
or RA81 disk drive is device type DU. The c identifies the
controller, and the u identifies the unit number of the device.
On a system with HSCs, use one of the following formats:
node$ddcu:
allocation-class$ddcu:
If your devices are dual ported to HSCs, use the allocation-
class format. For example, $125$DUA23 represents an RA80 or
RA81 disk with unit number 23. The disk's allocation class
is $125$. The c part of the format is always A for HSC disks.
TROLL$DJA12 represents an RA60 disk with unit number 12. The
device is connected to an HSC named TROLL. See the HP OpenVMS
Cluster Systems for more information about naming conventions.
Device names can be generic so that if no controller or unit
number is specified, the system attempts to mount the first
available device that satisfies those specified components of the
device names. If no volume is physically mounted on the specified
device, MOUNT displays a message requesting that you place the
volume in the device; after you place the volume in the named
drive, MOUNT then completes the operation.
If you specify more than one device name for a disk or magnetic
tape volume set, separate the device names with either commas
or plus signs. For a magnetic tape volume set, you can specify
more volume labels than device names or more device names than
volumes.
volume-label[,...]
Specifies the label on the volume.
The number of characters allowed in a label depends on the type
of device, as follows:
Number of Characters
Device Type in Label
Magnetic tape 0-6
Files-11 disk 1-12
ISO 9660 disk 1-32
OpenVMS requires disk volume labels to be unique in the first 12
characters within a given domain. For example, disks mounted by
different members of the same group using the /GROUP qualifier
must be unique. However, disks mounted in different domains,
such as one mounted using the /GROUP qualifier and one mounted
privately, can use the same volume label.
If you mount an ISO 9660 volume using the /SYSTEM or /CLUSTER
qualifier, and the volume label is not unique within the first 12
characters, you must supply an alternate volume label using the
qualifier /OVERRIDE=IDENTIFICATION. If you choose this option,
then Mount verification is disabled for the device.
the volume-set name are the same as the first 12 characters of
the volume label, a lock manager deadlock will occur. To avoid
this problem, you must override either the volume label (by using
the /OVERRIDE qualifier) or the volume-set name (by using the
/BIND qualifier).
If you specify more than one volume label, separate the labels
with either commas or plus signs. The volumes must be in the same
volume set and the labels must be specified in ascending order
according to relative volume number.
When you mount a magnetic tape volume set, the number of volume
labels need not equal the number of device names specified.
When a magnetic tape reaches the end-of-tape (EOT) mark, the
system requests the operator to mount the next volume on one of
the devices. The user is not informed of this request; only the
operator is informed.
When you mount a disk volume set, each volume label specified in
the list must correspond to a device name in the same position in
the device name list.
The volume-label parameter is not required when you mount a
volume with the /FOREIGN or /NOLABEL qualifier or when you
specify /OVERRIDE=IDENTIFICATION. To specify a logical name
when you enter either of these qualifiers, type any alphanumeric
characters in the volume-label parameter position.
logical-name[:]
Defines a 1- to 255-alphanumeric character string logical name to
be associated with the volume.
If you do not specify a logical name, the MOUNT command assigns
the default logical name DISK$volume-label to individual disk
drives; it assigns the default logical name DISK$volume-set-name
to the device on which the root volume of a disk volume set is
mounted. Note that if you specify a logical name in the mount
request that is different from DISK$volume-label or DISK$volume-
set-name, then two logical names are associated with the device.
If you do not specify a logical name for a magnetic tape drive,
the MOUNT command assigns only one logical name, TAPE$volume-
label, to the first magnetic tape device in the list. No default
logical volume-set name is assigned in this case.
The MOUNT command places the name in the process logical name
table, unless you specify /GROUP or /SYSTEM. In the latter cases,
it places the logical names in the group or system logical name
table.
If you specify the /CLUSTER qualifier, the logical name is
established on each node in the cluster.
NOTE
Avoid assigning a logical name that matches the file name
of an executable image in SYS$SYSTEM. Such an assignment
prohibits you from invoking that image.
Do not use the logical name assigned to a volume as a distributed
file system (DFS) access point. If you attempt to add a DFS
access point using the same name as the logical name, DFS fails
as in the following example:
$ SHOW LOG DISK$*
(LNM$SYSTEM_TABLE)
"DISK$TIVOLI_SYS" = "TIVOLI$DUA0:"
$ RUN SYS$SYSTEM:DFS$CONTROL
DFS> ADD ACCESS DISK$TIVOLI_SYS TIVOLI$DUA0:[000000]
%DNS-W-NONSNAME, Unknown namespace name specified
If the logical name of a volume is in a process-private table,
then the name is not deleted when the volume is dismounted.