HELP MOUNT — VMS 5.4
The Mount Utility (MOUNT) allows you to make a disk or magnetic
tape volume available for processing.
Format
MOUNT device-name[:][,...] [volume-label[,...]]
[logical-name[:]]
Additional information available:
Command Parametersusage summaryMOUNT Examples
/ACCESSED/ASSIST/AUTOMATIC/BIND/BLOCKSIZE
/CACHE/CLUSTER/COMMENT/CONFIRM/COPY/DATA_CHECK
/DENSITY/EXTENSION/FOREIGN/GROUP/HDR3/INCLUDE
/INITIALIZE/LABEL/MEDIA_FORMAT/MESSAGE/MOUNT_VERIFICATION
/MULTI_VOLUME/OVERRIDE/OWNER_UIC/PROCESSOR
/PROTECTION/QUOTA/REBUILD/RECORDSIZE/SHADOW
/SHARE/SYSTEM/UNLOAD/WINDOWS/WRITE
Command Parameters
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 Hierarchical Storage Controllers (HSCs), 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 Hierarchical Storage Controllers (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 VMS VAXcluster Manual
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 name(s). 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. For disk volumes, labels can
have from 1 through 12 characters; for magnetic tape volumes,
labels can have from 0 through 6 characters.
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- through 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.
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.
If the logical name of a volume is in a process-private table,
then the name is not deleted when the volume is dismounted.
usage summary
To invoke the Mount Utility, enter the command MOUNT at the
DCL prompt, followed by the device name, volume label, and
logical name. If you omit a parameter, MOUNT prompts you for it.
You must include a device name and a volume label (unless you
specify /OVERRIDE=IDENTIFICATION or use the /FOREIGN or /NOLABEL
qualifier); the logical name is optional.
The Mount Utility returns you to the DCL level after it either
successfully completes the operation or fails, generating an error
message. If you press CTRL/Y or CTRL/C, MOUNT aborts the operation
and returns you to the DCL prompt.
You can direct output from MOUNT operations with the /COMMENT and
/MESSAGE qualifiers. When the mount operation requires operator
assistance, use /COMMENT to specify additional information to be
included with the operator request. The /COMMENT text string is
sent to the operator log file and to SYS$OUTPUT. The string must
contain no more than 78 characters.
Use the /MESSAGE qualifier (this is the default) to send mount
request messages to your current SYS$OUTPUT device. If you
specify /NOMESSAGE during an operator-assisted mount, messages
are not sent to SYS$OUTPUT; the operator sees them, however, if an
operator terminal is enabled to receive messages.
Many MOUNT qualifiers require special privileges. Some qualifiers
require different privileges according to which qualifier keyword
you specify. See the individual qualifiers for details. Following
is a list of MOUNT qualifiers that require special privileges:
Qualifier Keywords Required Privilege
/ACCESSED OPER
/CACHE= [NO]EXTENT[=n] OPER
[NO]FILE_ OPER
ID[=n]
[NO]QUOTA[=n] OPER
/FOREIGN VOLPRO
/GROUP GRPNAM
/MULTI_VOLUME VOLPRO
/OVERRIDE= ACCESSIBILITY VOLPRO
EXPIRATION VOLPRO
LOCK VOLPRO
/OWNER_UIC= uic VOLPRO
/PROCESSOR= UNIQUE OPER
SAME:device OPER
filespec OPER and CMKRNL
/PROTECTION= code VOLPRO
/QUOTA VOLPRO
/SYSTEM SYSNAM
/WINDOWS= n OPER
/ACCESSED
Specifies, for disk volumes, the approximate number of directories
that will be in use concurrently on the volume.
Format
/ACCESSED=n device-name
Additional information available:
Qualifier Value
n Specifies the approximate number of directories that will be in use concurrently on the volume. Specify a value from 0 through 255 to override the default that was specified when the volume was initialized. You need the user privilege OPER to use /ACCESSED.
Example
$ MOUNT/ACCESSED=150 DBA1 WORK
This command requests the volume labeled WORK to be mounted on
DBA1, specifying 150 as the number of active directories on the
volume.
/ASSIST
Directs the mount operation to allow operator or user intervention
if the mount request fails.
Format
/ASSIST device-name
/NOASSIST device-name
Additional information available:
Example
$ MOUNT/NOASSIST DMA0: DOC WORK
%MOUNT-I-MOUNTED, DOC mounted on _NODE$DMA0:
This command mounts an RK07 volume labeled DOC and assigns the
logical name WORK. The /NOASSIST qualifier signals MOUNT that
no operator intervention is necessary.
/AUTOMATIC
Determines whether MOUNT enables or disables automatic volume
switching and labeling for magnetic tape.
Format
/AUTOMATIC device-name
/NOAUTOMATIC device-name
Additional information available:
Example
$ MOUNT/NOAUTOMATIC MTA0: ABCD,EFGH
This command instructs MOUNT not to generate its own label for
the second volume, but to use the ones supplied with the MOUNT
command. If the second volume is not already labeled, then the
operator must use REPLY/INIT and supply the second label.
/BIND
Creates a volume set of one or more disk volumes or adds one or
more volumes to an existing volume set.
Format
/BIND=volume-set-name device-name[,...] volume-label[,...]
Additional information available:
Keyword
volume-set-name Specifies a 1- through 12-alphanumeric-character name identifying the volume set.
Example
$ MOUNT/BIND=LIBRARY DMA0:,DMA1:,DMA2: BOOK1,BOOK2,BOOK3
This command creates a volume set named LIBRARY. This volume
set consists of the volumes labeled BOOK1, BOOK2, and BOOK3,
which are mounted physically on devices DMA0, DMA1, and DMA2,
respectively.
/BLOCKSIZE
Specifies the default block size for magnetic tape volumes.
Format
/BLOCKSIZE=n device-name
Additional information available:
Qualifier Value
n Specifies the default block size value for magnetic tape volumes. Valid values are in the range 20 through 65,532 for VMS RMS operations, and 18 through 65,534 for non-VMS RMS operations. By default, records are written to magnetic tape volumes in 2048- byte blocks. For foreign or unlabeled magnetic tapes, the default is 512 bytes.
Example
$ MOUNT/FOREIGN/BLOCKSIZE=1000 MTA1:
In this example, the /BLOCKSIZE qualifier specifies a block
size of 1000 bytes; the default for a magnetic tape mounted
with the /FOREIGN qualifier is 512.
/CACHE
For disks, controls whether caching limits established at system
generation time are disabled or overridden. With the TAPE_DATA
option, enables write caching for the tape controller specified
(if the tape controller supports write caching).
Format
/CACHE=(keyword[,...])
/NOCACHE
Additional information available:
Keywords
EXTENT[=n] Enables or disables extent caching. To enable extent caching, you must have the operator user privilege (OPER) and you must specify n, the number of entries in the extent cache. Note that NOEXTENT is equivalent to EXTENT=0; both disable extent caching. FILE_ID[=n] Enables or disables file identification caching. To enable file identification caching, you must have the operator user privilege (OPER) and you must specify n, the number of entries, as a value greater than 1. Note that NOFILE_ID is equivalent to FILE_ID=1; both disable file identification caching. LIMIT=n Specifies the maximum amount of free space in the extent cache in one-thousandths of the currently available free space on the disk. QUOTA[=n] Enables or disables quota caching. To enable quota caching, you must have the operator user privilege (OPER) and you must specify n, the number of entries in the quota cache. Normally n is set to the maximum number of active users expected for a disk with quotas enabled. Both NOQUOTA and QUOTA=0 disable quota file caching. TAPE_DATA Enables write caching for a magnetic tape device if the tape controller supports write caching. /NOCACHE is the default for mounting tape devices. You must specify TAPE_DATA to enable write caching. If the tape controller does not support write caching, the keyword is ignored. The write buffer stays enabled even after you dismount the magnetic tape. To disable the write buffer, mount a tape with the /NOCACHE qualifier. WRITETHROUGH Disables writeback caching, which writes only the file headers of files open for write when the files are closed. Thus, if you specify the WRITETHROUGH keyword, file headers are written to the disk on every file header operation.
Examples
1. $ MOUNT/CACHE=(EXTENT=60,FILE_ID=60,QUOTA=20,WRITETHROUGH) -
_$ DMA0: FILES WORK
%MOUNT-I-MOUNTED, FILES mounted on _NODE$DMA0:
This command mounts an RK07 device labeled FILES and assigns
the logical name WORK. The /CACHE qualifier enables an extent
cache of 60 entries, a file identification cache of 60 entries,
and a quota cache of 20; it disables writeback caching.
2. $ MOUNT/CACHE=TAPE_DATA MUA0: TAPE
%MOUNT-I-MOUNTED, TAPE mounted on _NODE$MUA0:
This command mounts the volume TAPE on device MUA0 and
instructs MOUNT to enable the tape controller's write cache
for MUA0.
/CLUSTER
Specifies that after the volume is successfully mounted on the
local node, or if it is already mounted /SYSTEM on the local node,
it is to be mounted on every other node in the existing VAXcluster
(that is, the volume is mounted clusterwide).
Format
/CLUSTER device-name
Additional information available:
Example
$ MOUNT/CLUSTER DOPEY$DMA1: SNOWWHITE DWARFDISK
%MOUNT-I-MOUNTED, SNOWWHITE mounted on _DOPEY$DMA1:
$ SHOW DEVICE/FULL DWARFDISK:
Disk $2$DMA1: (DOPEY), device type RK07, is online, mounted,
file-oriented device, shareable, served to cluster via MSCP Server,
error logging is enabled.
Error count 0 Operations completed 159
Owner process "" Owner UIC [928,49]
Owner process ID 00000000 Dev Prot S:RWED,O:RWED,G:RW,W:R
Reference count 1 Default buffer size 512
Total blocks 53790 Sectors per track 22
Total cylinders 815 Tracks per cylinder 3
Allocation class 2
Volume label "SNOWWHITE" Relative volume number 0
Cluster size 3 Transaction count 1
Free blocks 51720 Maximum files allowed 6723
Extend quantity 5 Mount count 7
Mount status System Cache name "_$255$DWARF1:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 5172
File ID cache size 64 Blocks currently in extent cache 0
Quota cache size 25 Maximum buffers in FCP cache 349
Volume status: subject to mount verification, file high-water marking,
write-through caching enabled.
Volume is also mounted on DOC, HAPPY, GRUMPY, SLEEPY, SNEEZY, BASHFUL.
This MOUNT/CLUSTER command mounts the volume SNOWWHITE on
DOPEY$DMA1, then proceeds to mount the volume clusterwide. The
SHOW DEVICE/FULL command displays information about the volume,
including the other nodes on which it is mounted.
/COMMENT
Specifies additional information to be included with the operator
request when the mount operation requires operator assistance.
Format
/COMMENT="string" device-name
Additional information available:
Keyword
string Specifies the text string that is output to the operator log file and the current SYS$OUTPUT device. The string must contain no more than 78 characters.
Examples
1. $ MOUNT DYA1: TESTSYS/COMMENT="Volume in cabinet 6."
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
Volume in cabinet 6.
%MOUNT-I-MOUNTED TESTSYS mounted on _DYA1:
%MOUNT-I-OPRQSTDON, operator request canceled - mount
completed successfully
This command requests the operator to mount the disk volume
TESTSYS on the device DYA1. Notice that the /COMMENT qualifier
is used to inform the operator of the location of the volume.
After the operator places the volume in DYA1, MOUNT retries the
operation. After the operation completes, the operator request
is canceled.
2. $ MOUNT DYA1: TESTSYS/COMMENT="Volume in cabinet 6."
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
Volume in cabinet 6.
%MOUNT-I-OPREPLY, This is a '/pending' response from the operator.
31-DEC-1989 10:27:38.15, request 2 pending by operator TTB6
%MOUNT-I-OPREPLY, This is a '/abort' response from the operator.
31-DEC-1989 10:29:59.34, request 2 aborted by operator TTB6
%MOUNT-F-OPRABORT, mount aborted by operator
This command is the same as in the previous example. However,
in this example, because the requested device is in use, the
operator aborts the mount.
3. $ MOUNT DYA0: TESTSYS/COMMENT="Volume in cabinet 6, once
again with feeling."
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA0:
Volume in cabinet 6, once again with feeling.
%MOUNT-I-OPREPLY, Substitute DYA1:
31-DEC-1989 10:43:42.30, request 3 completed by operator TTB6
%MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1:
This command requests the operator to mount the volume TESTSYS
on the device DYA0. In this example, the operator notices
that the requested device is in use and redirects the mount
to device DYA1.
/CONFIRM
Applicable only if you have the volume shadowing option. See the
VMS Volume Shadowing Manual.
Format
/NOCONFIRM (default)
Additional information available:
Description
Controls whether or not MOUNT issues a request to confirm a full copy operation when mounting a shadow set. Use /CONFIRM to display the volume label and volume owner for any specified physical device that is a target for a full copy operation. MOUNT stops before any full copy operations occur and issues the following prompt. Allow FULL shadow copy on the above member(s)? [N]: If you respond Y or Yes, the mount operation continues automatically with full copy operations allowed. If you respond N, No, <RETURN>, or <CTRL/Z> the command quits without mounting any of the specified volumes (including volumes that did not require copy operations. If you type a response other than those listed above, MOUNT reissues the prompt. /CONFIRM is similar to /NOCOPY. Use /CONFIRM to mount shadow sets interactively; use /NOCOPY in the site-specific startup command procedure SYS$MANAGER:SYSTARTUP.
Example
$ MOUNT/CONFIRM DSA23: /SHADOW=($1$DUA4:,$1$DUA6:) SHADOWVOL
%MOUNT-F-SHDWCOPYREQ, shadow copy required
Virtual Unit - DSA23 Volume Label - SHADOWVOL
Allow FULL shadow copy on the above member(s)? [N]: NO
This command shows how to use the /CONFIRM qualifier to check
the status of potential shadow set members before any data is
erased. The command instructs MOUNT to build a shadow set with
the specified devices, and prompt for permission to perform a
full copy operation. The response of No instructs MOUNT to quit
with no mounting or copying.
/COPY
Applicable only if you have the volume shadowing option. See the
VMS Volume Shadowing Manual.
Format
/NOCOPY
Additional information available:
Description
Instructs MOUNT to perform full copy operations on shadow set members. You can mount shadow sets with /NOCOPY to test if proposed shadow set members are targets of full copy operations. If any of the specified volumes are targets of copy operations, the command quits without mounting any of the specified volumes (including those that did not require a copy operation). /NOCOPY is similar to /CONFIRM. Use /NOCOPY to mount shadow sets in the site-specific startup command procedure SYS$MANAGER:SYSTARTUP; use /CONFIRM for interactive mounting.
Example
$ MOUNT/NOCOPY DSA2: /SHADOW=($1$DUA4:,$1$DUA6:,$1$DUA7:) -
_$ SHADOWVOL DISK$SHADOWVOL
%MOUNT-F-SHDWCOPYREQ, shadow copy required
%MOUNT-I-SHDWMEMFAIL, DUA7: failed as a member of the shadow set
%MOUNT-F-SHDWCOPYREQ, shadow copy required
This command shows how to use the /NOCOPY qualifier to check
the status of potential shadow set members before any data is
erased. The command instructs MOUNT to build a shadow set with
the specified devices only if no copy operations are required.
Because the device DUA7 required a full copy operation to
become a member of the shadow set, the mount operation failed.
You could reissue the command specifying /COPY to instruct
MOUNT to build the shadow set providing the necessary copy
operation.
/DATA_CHECK
Overrides the read-check or write-check option (or both) specified
for a volume when it was initialized.
Format
/DATA_CHECK[=(keyword[,...])] device-name
Additional information available:
Keywords
READ Performs checks following all read operations. WRITE Performs checks following all write operations.
Example
$ MOUNT/DATA_CHECK=READ CLEMENS$DBA2: SAM BOOK
This command mounts a volume labeled SAM on CLEMENS$DBA2 and
assigns the logical name BOOK. The /DATA_CHECK=READ qualifier
overrides a previous INITIALIZE/DATA_CHECK=WRITE specification,
so that subsequent read operations on BOOK are subject to data-
checking operations.
/DENSITY
Specifies the density (in bpi) at which a foreign or unlabeled
magnetic tape is to be written.
Format
[/FOREIGN][/NOLABEL]/DENSITY=n device-name
Additional information available:
Qualifier Value
n Specifies a density of 800 bpi, 1600 bpi, or 6250 bpi, if supported by the magnetic tape drive. If you do not specify a density for a magnetic tape that was previously written, the density defaults to that of the first record on the volume.
Example
$ MOUNT/FOREIGN/DENSITY=1600 MFA0: TAPE
This command mounts a foreign magnetic tape on drive MFA0 and
assigns the logical name TAPE. The /DENSITY qualifier specifies
that the magnetic tape is to be written at a density of 1600
bpi.
/EXTENSION
Specifies the number of blocks by which disk files are to be
extended on the volume unless otherwise specified by an individual
command or program request.
Format
/EXTENSION=n device-name
Additional information available:
Qualifier Value
n Specifies a value from 0 through 65,535 to override the value specified when the volume was initialized.
Example
$ MOUNT/EXTENSION=64 DBA0: DOC WORK
This command mounts a volume labeled DOC on DBA0, assigns the
logical name WORK, and specifies a default block extent of 64
for the files on WORK.
/FOREIGN
Indicates that the volume is not in the standard format used by
the VMS operating system.
Format
/FOREIGN device-name
Additional information available:
Examples
1. $ MOUNT/FOREIGN MTA1: TAPE
This command mounts a foreign magnetic tape on drive MTA1.
2. $ MOUNT/FOREIGN DMA2: SAVEDISK
This command mounts an RK07 device as a foreign volume on DMA2
and assigns the logical name SAVEDISK. As a volume that is
not file structured, SAVEDISK can be used for sequential-disk
BACKUP save operations.
/GROUP
Makes the volume available to other users with the same group
number in their UICs as the user entering the MOUNT command.
Format
/GROUP device-name
Additional information available:
Examples
1. $ MOUNT/GROUP DB1:, DB2:, DB3: -
_$ PAYVOL1,PAYVOL2,PAYVOL3 PAY
This command mounts and makes available on a group basis the
volume set consisting of volumes labeled PAYVOL1, PAYVOL2, and
PAYVOL3. The logical name PAY is assigned to the set; anyone
wanting to access files on these volumes can refer to the set
as PAY.
2. $ MOUNT/GROUP/BIND=MASTER_PAY -
_$ DB4: PAYVOL4
This command adds the volume labeled PAYVOL4 to the existing
volume set MASTER_PAY. The root volume for the volume set must
be on line when you enter this command.
/HDR3
Controls whether ANSI standard header label 3 is written on a
magnetic tape volume.
Format
/HDR3 device-name
/NOHDR3 device-name
Additional information available:
Example
$ INITIALIZE MTA0: ABCD
$ MOUNT/NOHDR3 MTA0: ABCD
The INITIALIZE and MOUNT commands prepare an ANSI-formatted
magnetic tape for processing. The /NOHDR3 qualifier specifies
that no HDR3 labels are to be written, thus creating a magnetic
tape that can be transported to systems that do not process
implementation-dependent labels correctly.
/INCLUDE
Applicable only if you have the volume shadowing option. See the
VMS Volume Shadowing Manual.
Format
/NOINCLUDE=(virtual-unit-name[:]
/SHADOW=(physical-device-name[:][,...]))
Additional information available:
Description
Automatically mounts and reinstates a shadow set (or volume set of shadow sets) to the way it was before the shadow set was dissolved. Supply the exact virtual unit name that was used when the shadow set was originally mounted. Use the virtual unit naming format DSAnnnn:. You must also include the /SHADOW qualifier and specify at least one of the disk devices from the original shadow set. Use the standard device naming format $allocation-class$ddcu[:]. Omit the parenthesis if you name only one device. If you specify more than one device, more current disks are copied to less current disks by default. You can disable the copy operation by using either the /CONFIRM or /NOCOPY qualifier. The Mount Utility uses the volume label information from the disk that you name to determine the membership of the original shadow set. The default is /NOINCLUDE which prevents the automatic reconstruction of former shadow sets.
Example
$ MOUNT /SYSTEM DSA4/SHAD=($4$DIA1,$4$DIA2,$4$DIA3) NEWDISK
%MOUNT-I-MOUNTED, NEWDISK mounted on _DSA4:
%MOUNT-I-SHDWMEMSUCC, _$4$DIA1: (DISK01) is now a valid member
of the shadow set
%MOUNT-I-SHDWMEMCOPY, _$4$DIA2: (DISK02) added to the shadow set
with a copy operation
%MOUNT-I-SHDWMEMCOPY, _$4$DIA3: (DISK03) added to the shadow set
with a copy operation
$ DISMOUNT DSA4
$
$ MOUNT DSA4:/SHAD=$4$DIA1 NEWDISK/INCLUDE
%MOUNT-I-MOUNTED, NEWDISK mounted on _DSA4:
%MOUNT-I-SHDWMEMSUCC, _$4$DIA1: (DISK01) is now a valid member
of the shadow set
%MOUNT-I-AUTOMEMSUCC, _$4$DIA2: (DISK02) automatically added
to the shadow set
%MOUNT-I-AUTOMEMSUCC, _$4$DIA3: (DISK03) automatically added
to the shadow set
This example shows how to reconstruct a shadow set wherein the
volume shadowing software determines which disk volumes are
former members of the shadow set.
o First is the original mount command that created the shadow
set represented by DSA4. The shadow set consists of three
shadow set members: $4$DIA1, $4$DIA2, and $4$DIA3.
o Next, the DISMOUNT command dissolves the shadow set.
o The /INCLUDE qualifier triggers MOUNT to reconstruct
the shadow set back to the way it was before the shadow
set was dissolved. The /INCLUDE qualifier is position
independent; it can appear anywhere in the command line. The
mount command must specify the original virtual unit name
(DSA4) and at least one of the original shadow set members
($4$DIA1). The Mount Utility reads the membership list on
$4$DIA1 (specified in the mount command) to determine that
$4$DIA2 and $4$DIA3 are also members of the shadow set.
o Because the shadow set was properly dismounted and there
were no write I/Os left outstanding, the shadow set members
are in a consistent state. The MOUNT status messages
indicate that the shadow set devices are added back into
the shadow set without the need for copy operations.
/INITIALIZE=CONTINUATION
Specifies that any volume added to the magnetic tape volume set is
initialized before you can write to the volume.
Format
/INITIALIZE=CONTINUATION device-name
Additional information available:
Example
$ MOUNT/INITIALIZE=CONTINUATION MTA0: ABCD
This /INITIALIZE=CONTINUATION qualifier instructs the MOUNT
command to assign its own continuation label. In this case,
the operator can enter the command REPLY/TO=n, and the system
assigns a label derived from the original. It uses the label
specified in the MOUNT command and adds the appropriate number
(ABCD02, ABCD03, and so forth).
/LABEL
Indicates that the volume is in the standard format used by the
VMS operating system; that is, a magnetic tape volume is in the
standard ANSI format, or a disk volume is in Files-11 format.
Format
/LABEL device-name
/NOLABEL device-name
Additional information available:
Example
$ MOUNT/LABEL MFA1: TAPE
This command mounts an ANSI-labeled magnetic tape on MFA1 and
assigns the logical name TAPE.
/MEDIA_FORMAT=[NO]COMPACTION
Enables and controls data compaction and record blocking on a
TA90E tape drive.
Format
/MEDIA_FORMAT=[NO]COMPACTION device-name
Additional information available:
Example
$ MOUNT/MEDIA_FORMAT=COMPACTION MUA0: BOOKS
In this example, a tape device labeled BOOKS is mounted with
data compaction and record blocking enabled.
/MESSAGE
Causes mount request messages to be sent to your current
SYS$OUTPUT device.
Format
/MESSAGE device-name
/NOMESSAGE device-name
Additional information available:
Example
$ MOUNT/NOMESSAGE DLA0: SLIP DISC
In this example an RL02 device labeled SLIP is mounted on drive
DLA0 and is assigned the logical name DISC. The /NOMESSAGE
qualifier disables the broadcast of mount request messages to
the user terminal.
/MOUNT_VERIFICATION
Specifies that the device is a candidate for mount verification.
Format
/MOUNT_VERIFICATION device-name
/NOMOUNT_VERIFICATION device-name
Additional information available:
Example
$ MOUNT/CACHE=(NOEXTENT,NOFILE_ID,NOQUOTA,WRITETHROUGH) -
_$ /NOMOUNT_VERIFICATION DMA0: FILES WORK
%MOUNT-I-MOUNTED, FILES mounted on _NODE$DMA0:
This command mounts an RK06 or RK07 device labeled FILES and
assigns the logical name WORK. The /CACHE qualifier disables
extent caching, file identification caching, quota caching, and
writeback caching; the /NOMOUNT_VERIFICATION qualifier disables
mount verification.
/MULTI_VOLUME
For foreign or unlabeled magnetic tape volumes, determines whether
you override MOUNT volume-access checks. Use /MULTI_VOLUME to
override access checks on volumes that do not contain labels that
MOUNT can interpret. If you have software produced before VMS
Version 5.0 that processes multiple-volume, foreign-mounted tape
volumes without specifically mounting and dismounting each reel,
you may now need to mount the first volume with the /MULTI_VOLUME
qualifier.
Format
/MULTI_VOLUME device-name
/NOMULTI_VOLUME device-name
Additional information available:
Example
$ MOUNT/FOREIGN/MULTI_VOLUME MUA0:
This command mounts a tape volume set. MOUNT performs an access
check on the first volume in the set and proceeds without
checks to subsequent reels as they are needed for processing.
/OVERRIDE
Inhibits one or more protection checks that the MOUNT command
performs.
Format
/OVERRIDE=(keyword[,...]) device-name
Additional information available:
Keywords
ACCESSIBILITY
For magnetic tapes only. If the installation allows, this keyword
overrides any character in the Accessibility Field of the volume.
The necessity of this keyword is defined by the installation.
That is, each installation has the option of specifying a routine
that the magnetic tape file system will use to process this field.
By default, VMS provides a routine that checks this field in the
following manner:
o If the magnetic tape was created on a version of VMS that
conforms to Version 3 of ANSI, then you must use this keyword
to override any character other than an ASCII space.
o If a VMS protection is specified and the magnetic tape conforms
to an ANSI standard that is higher than Version 3, then you
must use this keyword to override any character other than an
ASCII 1.
To use the ACCESSIBILITY keyword, you must have the user privilege
VOLPRO or own the volume.
EXPIRATION
For magnetic tapes only. Allows you to override the expiration
dates of a volume and its files. Use this keyword when the
expiration date in the first file header label of any file that
you want to overwrite has not been reached. You must have the user
privilege VOLPRO or your UIC must match the UIC written on the
volume.
IDENTIFICATION
Overrides processing of the volume identifier in the volume label.
Use this keyword to mount a volume for which you do not know the
label. Only the volume identifier field is overridden. Volume
protection, if any, is preserved. The volume must be mounted
/NOSHARE (either explicitly or by default).
LOCK
Directs MOUNT not to write-lock the volume as a consequence of
certain errors encountered while mounting it. Use this keyword
when you are mounting a damaged volume to be repaired using the
Verify Utility. You must have VOLPRO privilege or own the volume
to use the LOCK keyword.
OWNER_IDENTIFIER
For magnetic tapes only. Overrides the processing of the owner
identifier field. Use this keyword to interchange protected
magnetic tapes between VMS and other Digital operating systems.
SETID
For magnetic tapes only. Prevents MOUNT from checking the file-
set identifier in the first file header label of the first file
on a continuation volume. Use this keyword only for ANSI-labeled
volumes on which the file-set identifier of the first file on a
continuation volume differs from the file-set identifier of the
first file of the first volume that was mounted.
SHADOW_MEMBERSHIP
Applicable only if you have the volume shadowing option. See the
VMS Volume Shadowing Manual.
Allows you to override the write protection of former shadow set
members. When you mount a volume with this qualifier; the volume
shadowing generation number is erased. If you attempt to remount
the volume in a shadow set, the volume is considered an unrelated
volume and receives a full copy operation from a current shadow
set member.
If you specify more than one keyword, separate them with commas
and enclose the list in parentheses.
You need the user privileges OPER and VOLPRO to specify
/OVERRIDE=(ACCESSIBILITY, EXPIRATION) along with the /FOREIGN
qualifier; otherwise, the magnetic tape is not read.
Example
$ MOUNT/OVERRIDE=IDENTIFICATION MFA0:
This command overrides the volume identification field, thus
mounting a magnetic tape on MFA0 without a label specification.
/OWNER_UIC
Requests that the specified UIC be assigned ownership of the
volume while it is mounted, overriding the ownership recorded
on the volume. Or, if you are mounting a volume using the /FOREIGN
qualifier, requests an owner UIC other than your current UIC.
Format
/OWNER_UIC=uic device-name
Additional information available:
Keyword
UIC
Specifies the user identification code (UIC) in the following
format:
[group,member]
You must use brackets in the UIC specification. The group number
is an octal number in the range 0 through 37776; the member number
is an octal number in the range 0 through 17776.
To use the /OWNER_UIC qualifier for a Files-11 volume you must
have the user privilege VOLPRO, or your UIC must match the UIC
written on the volume.
Example
$ MOUNT/OWNER_UIC=[016,360] DRA3: WORK
This command mounts a disk device labeled WORK on DRA3 and
assigns an owner UIC of [016,360].
/PROCESSOR
For magnetic tapes and Files-11 Structure Level 1 disks, requests
that the MOUNT command associate an Ancillary Control Process
(ACP) to process the volume. The /PROCESSOR qualifier causes MOUNT
to override the default manner in which ACPs are associated with
devices.
For Files-11 Structure Level 2 disks, controls block cache
allocation.
Format
/PROCESSOR=keyword device-name
Additional information available:
Keywords
UNIQUE For magnetic tape and Files-11 Structure Level 1 disks, creates a new process to execute a copy of the default ACP image for the specified device type or controller. For Files-11 Structure Level 2 disks, allocates a separate block cache. SAME:device For magnetic tape and Files-11 Structure Level 1 disks, uses the same ACP process currently being used by the device specified. For Files-11 Structure Level 2 disks, takes the block cache allocation from the specified device. filespec Creates a new process to execute the ACP image specified by the file specification (for example, a modified or a user-written ACP). You cannot use wildcard characters, or node and directory names in the file specification. To use this keyword, you need CMKRNL and OPER privilege. You must have the operator user privilege OPER to use the /PROCESSOR qualifier.
Example
$ MOUNT/PROCESSOR=SAME:MTA1: MFA0:
This command directs MOUNT to mount a magnetic tape on MFA0
using the same ACP process currently associated with MTA1.
/PROTECTION
Specifies the protection code to be assigned to the volume.
Format
/PROTECTION=code device-name
Additional information available:
Keyword
code Specifies the protection code according to the standard syntax rules for specifying protection. If you omit a protection category, that category of user is denied all access. If you do not specify a protection code, the default is the protection that was assigned to the volume when it was initialized.
Example
$ MOUNT/PROTECTION=(SYSTEM:RWE,O:RWED,G:RE,W:R) DBA1:
WORKDISK
This command mounts a device labeled WORKDISK on DBA1 and
assigns a protection code. Access to the volume will be READ,
WRITE, and EXECUTE for SYSTEM users; READ, WRITE, EXECUTE,
and DELETE for OWNER; READ and EXECUTE for GROUP users; and
READ-only for users in the WORLD category.
/QUOTA
Controls whether or not quotas are to be enforced on the specified
disk volume.
Format
/QUOTA device-name
/NOQUOTA device-name
Additional information available:
Example
$ MOUNT/OWNER_UIC=[016,360]/NOQUOTA DRA3: WORK
This command specifies that the disk volume labeled WORK on
DRA3 has an owner UIC of [016,360] and no quotas enforced.
/REBUILD
Controls whether or not MOUNT performs a rebuild operation on a
disk volume.
Format
/REBUILD device-name
/NOREBUILD device-name
Additional information available:
Examples
1. $ MOUNT/REBUILD NODE$DBA2: WORKDISK
%MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DBA2:
%MOUNT-I-REBUILD, volume was improperly dismounted;
rebuild in progress
In this example, the volume WORKDISK is mounted on NODE$DBA2.
Because the volume is found to have been improperly dismounted
and the /REBUILD qualifier is in effect, MOUNT displays a
message and proceeds to rebuild the volume.
2. $ MOUNT/NOREBUILD NODE$DBA2: WORKDISK
%MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DBA2:
%MOUNT-I-REBLDREQD, rebuild not performed;
some free space unavailable;
diskquota usage stale
In this example, the volume WORKDISK is found to have been
improperly dismounted, but because the /NOREBUILD qualifier
is specified, a rebuild is not performed. Instead, MOUNT
displays a message to inform you that the rebuild is needed,
and proceeds to make WORKDISK available for use as is. You
can rebuild the volume later with the DCL command SET VOLUME
/REBUILD.
/RECORDSIZE
Specifies the number of characters in each record of a magnetic
tape volume.
Format
/RECORDSIZE=n device-name
Additional information available:
Qualifier Value
n Specifies the block size in the range 20 through 65,532 bytes if you are using VMS RMS, or 18 through 65,534 bytes if you are not using VMS RMS.
Example
$ MOUNT/FOREIGN/BLOCKSIZE=512/RECORDSIZE=512 MTA0:
In this example the magnetic tape is mounted on MTA0 with a
default block size and record size of 512 characters.
/SHADOW
Applicable only if you have the volume shadowing option. See the
VMS Volume Shadowing Manual.
Format
/SHADOW=(physical-device-name[:][,...])
Additional information available:
Description
Parameter qualifier: Indicates that you are mounting a shadow set including the physical devices and the virtual unit that represents them to the system. This qualifier instructs MOUNT to expect a virtual-unit- name as the device-name parameter. Use the virtual unit naming format DSAnnnn, where nnnn is a unique number from 0 through 9999. Place the /SHADOW qualifier after the virtual-unit name parameter, and include at least one device name to be mounted in the shadow set. If you specify only one device, you can omit the parenthesis. Use the standard device naming format $allocation- class$ddcu[:]. Note that the device names of shadow set members must have a nonzero allocation class to operate in a VAXcluster system.
Example
$ MOUNT DSA0: /SHADOW=($1$DUA10:,$1$DUA11:) SHADOWVOL
%MOUNT-I-MOUNTED, SHADOWVOL mounted on DSA0:
%MOUNT-I-SHDWMEMSUCC, _$1$DUA10: (MEMBER1) is now a valid member of
the shadow set
%MOUNT-I-SHDWMEMCOPY, _$1$DUA11: (MEMBER2) added to the shadow set
with a copy operation
This example shows how to create a shadow set wherein the
software determines automatically the correct copy operation
for the two shadow set members. In this case, $1$DUA10 is
the more current volume and becomes the source of the copy
operation to $1$DUA11.
/SHARE
Specifies, for a disk volume, that the volume is shareable.
Format
/SHARE device-name
/NOSHARE device-name
Additional information available:
Example
$ MOUNT/NOMESSAGE/SHARE DLA0: SLIP DISC
This command mounts the device labeled SLIP on DLA0, disables
broadcasting of MOUNT messages, specifies that the volume is
shareable, and assigns the logical name DISC.
/SYSTEM
Makes the volume public, that is, available to all users of the
system, as long as the UIC-based volume protection allows them
access.
Format
/SYSTEM device-name
Additional information available:
Examples
1. $ MOUNT/NOMESSAGE/SYSTEM DUA1: SLIP SACH
This command mounts the volume labeled SLIP on DUA1 with mount
messages disabled. The volume is made available systemwide.
MOUNT also assigns the logical name SACH.
2. $ MOUNT/SYSTEM/BIND=MASTER_PAY -
_$ DB1:,DB2:,DB3: PAYVOL1,PAYVOL2,PAYVOL3
This command creates the volume set named MASTER_PAY consisting
of the initialized volumes labeled PAYVOL1, PAYVOL2, and
PAYVOL3. These volumes are mounted physically on the devices
named DB1, DB2, and DB3, respectively. The volume PAYVOL1 is
the root volume of the set.
The volumes are mounted as system volumes to make them
available to all users.
/UNLOAD
Controls whether or not the disk or magnetic tape volume or
volumes specified in the MOUNT command are unloaded when they
are dismounted. The default is /UNLOAD.
Format
/UNLOAD device-name
/NOUNLOAD device-name
Additional information available:
Example
$ MOUNT/NOUNLOAD DBA1: OFFENS STRAT
In this example, the volume labeled OFFENS is mounted on DBA1
with the /NOUNLOAD qualifier so that it can be dismounted
without being physically unloaded. MOUNT also assigns the
logical name STRAT.
/WINDOWS
Specifies the number of mapping pointers to be allocated for file
windows.
Format
/WINDOWS=n device-name
Additional information available:
Qualifier Value
n Specifies a value from 7 through 80 that overrides the default value specified when the volume was initialized.
Example
$ MOUNT/SYSTEM/WINDOWS=25 DBA2: GONWITH THE_WINDOW
This command makes the volume labeled GONWITH on DBA2 available
systemwide and assigns the logical name THE_WINDOW. You
override the default number of mapping pointers by specifying a
value of 25 for the /WINDOWS qualifier.
/WRITE
Controls whether the volume can be written.
Format
/WRITE device-name
/NOWRITE device-name
Additional information available:
Example
$ MOUNT/CLUSTER/NOWRITE NODE$DBA1: BOOKS
This command mounts a volume labeled BOOKS on NODE$DBA1
and then proceeds to mount it on each node in the existing
VAXcluster. The /NOWRITE qualifier makes the volume available
for read-only access.
MOUNT Examples
The following examples describe how to use the Mount Utility with
and without operator assistance.
For examples 1 and 2, operator assistance is not required,
assuming the volumes are in the drives. Examples 3 through 6
describe operator-assisted mounts.
1. $ MOUNT MTA0: MATH06 STAT_TAPE
%MOUNT-I-MOUNTED, MATH06 mounted on _MTA0:
$ COPY ST061178.DAT STAT_TAPE:
This MOUNT command requests the magnetic tape whose volume label
is MATH06 to be mounted on the device MTA0 and assigns the logical
name STAT_TAPE to the volume.
Subsequently the COPY command copies the disk file ST061178.DAT to
the magnetic tape.
2. $ ALLOCATE DM:
%DCL-I-ALLOC, _DMB2: allocated
$ MOUNT DMB2: TEST_FILES
%MOUNT-I-MOUNTED, TEST_FILES mounted on _DMB2:
This ALLOCATE command requests an available RK06/RK07 device.
After the response from the ALLOCATE command, the physical volume
can be placed on the allocated device. Then, the MOUNT command
mounts the volume.
3. $ MOUNT DM: TEST_FILES
%MOUNT-I-OPRQST, Please mount volume TEST_FILES in device _DMB2:
%MOUNT-I-MOUNTED, TEST_FILES mounted on _DMB2:
This example achieves the same result as the series of commands
in the preceding example. The MOUNT command requests an available
RK06/RK07 device for the volume labeled TEST_FILES. After the
volume is physically mounted in the device named in the response
from MOUNT, the system completes the operation. Note that the
device is automatically allocated by MOUNT.
4. $ MOUNT DYA1: TESTSYS
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device DYA1:
<CTRL/Y>
$ EXIT
%MOUNT-I-OPRQSTCAN, operator request canceled
This MOUNT command requests the operator to mount the volume
TESTSYS on the device DYA1. In this example, the user cancels
the mount by pressing CTRL/Y. Notice that the image must exit
before the mount request is actually canceled. Here, the EXIT
command causes the image to exit. However, any command that is not
performed within the command interpreter causes the current image
to exit.
5. $ MOUNT DYA1: TESTSYS
%MOUNT-I-OPRQST, Device _DYA1: is not available for mounting.
%MOUNT-I-OPRQSTCAN, operator request canceled
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
%MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1:
%MOUNT-I-OPRQSTDON, operator request canceled - mount
completed successfully
This MOUNT command requests the operator to mount the volume
TESTSYS on the device DYA1. Because DYA1 is allocated to another
user, the device cannot be mounted. In this case, the user can
wait for the device to become available, redirect the mount to
another device, or abort the mount. Here, the user remains in
operator-assisted mount waiting for the process that is using
the device to deallocate it. At this point, because the device is
available but no volume is mounted, the original mount request is
canceled, and a new request to mount TESTSYS is issued. Finally,
the operator places the volume in the drive and lets MOUNT retry
the mount. When the mount completes, the request is canceled.
6. $ MOUNT DYA1: TESTSYS/COMMENT="Is there an operator
around?"
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
Is there an operator around?
%MOUNT-I-NOOPR, no operator available to service request
.
.
.
%MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1:
%MOUNT-I-OPRQSTDON, operator request canceled - mount
completed successfully
This MOUNT command requests the operator to mount the volume
TESTSYS on the device DYA1. In this example, no operator is
available to service the request. At this point, the user can
abort the mount by pressing CTRL/Y, or wait for an operator. Here,
the user waited, and an operator eventually became available to
service the request.