![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Specifies the default block size for magnetic tape volumes.
/BLOCKSIZE= n
n
Specifies the default block size value for magnetic tape volumes. Valid values are in the range 20 to 65,532 for OpenVMS RMS operations, and 18 to 65,534 for non OpenVMS 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.
You must specify /BLOCKSIZE in two situations:
- When mounting magnetic tapes that do not have HDR2 labels. For these magnetic tapes, you must specify the block size. For example, you must specify /BLOCKSIZE=512 to mount an RT--11 magnetic tape.
- When mounting magnetic tapes that contain blocks whose sizes exceed the default block size (2048 bytes). In this case, specify the size of the largest block for the block size.
$ 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.
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).
/CACHE= (keyword[,...])
/NOCACHE
EXTENT[=n]
NOEXTENT
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]
NOFILE_ID
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]
NOQUOTA
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. The /CACHE qualifier 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.
If a tape supports compaction, then the default is compaction, and caching is enabled. For tape storage devices that support compaction, the following command is valid.
$ MOUNT TAPE_DATA/FOREIGN/MEDIA=NOCOMPACTION/NOCACHEWRITETHROUGH
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.
Used with the disk options, the /CACHE qualifier overrides one or more of the present disk caching limits established at system generation time. Used with the TAPE_DATA option, the /CACHE qualifier enables write caching for the tape controller specified.If you do not specify the /CACHE qualifier and it is not implied by the use of the qualifier /MEDIA_FORMAT=COMPACTION, caching is enabled by default.
If you specify more than one option, separate them by commas and enclose the list in parentheses. The options [NO]EXTENT, [NO]FILE_ID, LIMIT, and [NO]QUOTA apply only to a disk device. The option TAPE_DATA applies only to a tape device.
The /NOCACHE qualifier is effective only if compaction is not enabled. If compaction is enabled (with the /MEDIA_FORMAT=COMPACTION), caching is enabled by default.
If you specify /NOCACHE for a disk device, all caching is disabled for this volume. Note that the /NOCACHE qualifier is equivalent to /CACHE=(NOEXTENT,NOFILE_ID,NOQUOTA,WRITETHROUGH).
If you specify /NOCACHE for a magnetic tape device, the tape controller's write cache is disabled for this volume.
Examples
$ MOUNT/CACHE=(EXTENT=60,FILE_ID=60,QUOTA=20,WRITETHROUGH) - _$ DMA0: FILES WORK %MOUNT-I-MOUNTED, FILES mounted on _NODE$DMA0:
$ MOUNT/CACHE=TAPE_DATA MUA0: TAPE %MOUNT-I-MOUNTED, TAPE mounted on _NODE$MUA0:
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 VMScluster (that is, the volume is mounted clusterwide).
/CLUSTER
Only system or group volumes can be mounted clusterwide. If you specify the /CLUSTER qualifier with neither the /SYSTEM nor the /GROUP qualifier, the default is /SYSTEM. Note that you must use a cluster device-naming convention. Use either node$device-name or allocation-class$device-name as required by your configuration.You need the user privileges GRPNAM and SYSNAM, respectively, to mount group and system volumes clusterwide.
If the system is not a member of an OpenVMS Cluster, the /CLUSTER qualifier has no effect.
$ 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.
Specifies additional information to be included with the operator request when the mount operation requires operator assistance.
/COMMENT= string
string
Specifies a 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
$ 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
$ 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-1995 10:27:38.15, request 2 pending by operator TTB6 %MOUNT-I-OPREPLY, This is a '/abort' response from the operator. 31-DEC-1995 10:29:59.34, request 2 aborted by operator TTB6 %MOUNT-F-OPRABORT, mount aborted by operator
$ (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-1995 10:43:42.30, request 3 completed by operator TTB6 %MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1:
Causes MOUNT to pause and request confirmation before performing a copy operation on the specified disk device. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS.
/CONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...])
/NOCONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...])
Controls whether MOUNT issues a request to confirm a full copy operation when mounting a shadow set. The /SHADOW qualifier must be used with the /CONFIRM qualifier. Use /CONFIRM to display the volume label and volume owner for any specified physical device that is a target for a copy operation. MOUNT stops before any 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 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.
The /CONFIRM qualifier is similar to /NOCOPY. Use /CONFIRM to mount shadow sets interactively; use /NOCOPY in the site-specific startup command procedure SYS$MANAGER:SYSTARTUP_VMS.COM.
$MOUNT/CONFIRM DSA0:/SHADOW=($200$DKA200:,$200$DKA300:,$200$DKA400:) X5OZCOPY
%MOUNT-F-SHDWCOPYREQ, shadow copy required
Virtual Unit - DSA0 Volume Label - X5OZCOPY
Member Volume Label Owner UIC
$200$DKA200: (VIPER1) X5OZCOPY [SYSTEM]
$200$DKA400: (VIPER1) X5OZCOPY [SYSTEM]
Allow FULL shadow copy on the above member(s)? [N]: Y
%MOUNT-I-MOUNTED, X5OZCOPY mounted on _DSA0:
%MOUNT-I-SHDWMEMSUCC, _$200$DKA300: (VIPER1) is now a valid member of
the shadow set
%MOUNT-I-SHDWMEMCOPY, _$200$DKA200: (VIPER1) added to the shadow set
with a copy operation
%MOUNT-I-SHDWMEMCOPY, _$200$DKA400: (VIPER1) added to the shadow set
with a copy operation
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 prompts for permission to perform a copy operation. The response of YES instructs MOUNT to mount the shadow set.
Enables or disables copy operations on physical devices specified when you mount a shadow set. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS.
/COPY virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...])
/NOCOPY virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...])
Instructs MOUNT to perform copy operations on shadow set members. You can mount shadow sets with /NOCOPY to test if proposed shadow set members are targets of copy operations. If any of the specified volumes is a target of a copy operation, the command quits without mounting any of the specified volumes (including those that did not require a copy operation).The default qualifier is /COPY.
The /NOCOPY qualifier is similar to /CONFIRM. Use /NOCOPY to mount shadow sets in the site-specific startup command procedure SYS$MANAGER:SYSTARTUP_VMS.COM; use /CONFIRM for interactive mounting.
$ 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 a copy operation is not required. Because the device DUA7 required a copy operation to become a member of the shadow set, the mount failed. You could reissue the command specifying /COPY to instruct MOUNT to build the shadow set providing the necessary copy operation.
Overrides the read-check or write-check option (or both) specified for a volume when it was initialized.
/DATA_CHECK [=(keyword[,...])]
READ
Performs checks following all read operations.WRITE
Performs checks following all write operations.
You can specify either or both of the keywords. If you specify more than one keyword, separate them by commas and enclose the list in parentheses.If you specify the /DATA_CHECK qualifier without specifying a keyword, MOUNT defaults to /DATA_CHECK=WRITE.
$ 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.
Specifies the density (in bits/in) at which a foreign or unlabeled magnetic tape is to be written.
[/FOREIGN][/NOLABEL]/DENSITY= n
n
Specifies a density of 800, 1600, or 6250 bits/in, 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.The /DENSITY qualifier is incompatible with the /MEDIA_FORMAT=[NO]COMPACTION qualifier.
The specified density is used only if you specify /FOREIGN or /NOLABEL and the first operation performed on the magnetic tape is a write.If you specify /LABEL, or if the first operation on the magnetic tape is a read, the magnetic tape is read or written at the density at which the first record on the magnetic tape is recorded. The default is /LABEL.
$ 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 bits/in.
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.
/EXTENSION= n
n
Specifies a value from 0 to 65,535 to override the value specified when the volume was initialized.
$ 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.
Indicates that the volume is not in the standard format used by the OpenVMS operating system.
/FOREIGN
Use the /FOREIGN qualifier when a magnetic tape volume is not in the standard ANSI format, or when a disk volume is not in Files--11 format.If you mount a volume with the /FOREIGN qualifier, the program you use to read the volume must be able to process the labels on the volume, if any. The OpenVMS operating system does not provide an ancillary control process (ACP) to process the volume.
You must mount DOS--1 and RT--11 volumes with the /FOREIGN qualifier and process them with the Exchange utility (EXCHANGE). See the OpenVMS Exchange Utility Manual.
The default protection applied to foreign volumes is RWLP (Read, Write, Logical I/O, Physical I/O) for the system and owner and no access for the group and world. If you also specify /GROUP, group members are also given RWLP access. If you specify /SYSTEM or /SHARE, the group and world are both given RWLP access. Note that the /GROUP, /SYSTEM, and /SHARE qualifiers do not alter the default protection.
If you mount a volume currently in Files--11 format with the /FOREIGN qualifier, you must have the user privilege VOLPRO, or your UIC must match the UIC on the volume.
The /FOREIGN qualifier is incompatible with the following qualifiers: /ACCESSED, /AUTOMATIC, /BIND, /CACHE, /[NO]CONFIRM, [NO]COPY, /EXTENSION, /HDR3, /INITIALIZE, /LABEL, /PROCESSOR, /QUOTA, /REBUILD, /SHADOW, /OVERRIDE=EXPIRATION, and /WINDOWS.
Examples
$ MOUNT/FOREIGN MTA1: ABCD TAPE
$ MOUNT/FOREIGN DMA2: SAVEDISK
Makes the volume available to other users with the same group number in their UICs as the user entering the MOUNT command.
/GROUP
The logical name for the volume is placed in the group logical name table. You must have the user privilege GRPNAM to use the /GROUP qualifier.Note that if the volume is owned by a group other than yours, access may be denied because of the volume protection.
The /GROUP qualifier is not valid for ISO 9660 volume sets.
The /GROUP qualifier is incompatible with the /OVERRIDE=IDENTIFICATION, /SHARE, and /SYSTEM qualifiers.
Examples
$ MOUNT/GROUP DB1:, DB2:, DB3: PAYVOL1,PAYVOL2,PAYVOL3 PAY
$ MOUNT/GROUP/BIND=MASTER_PAY DB4: PAYVOL4
Controls whether ANSI standard header label 3 is written on a magnetic tape volume.
/HDR3
/NOHDR3
By default, header label 3 is written. You can specify the /NOHDR3 qualifier to write magnetic tapes that are to be used on other systems that do not process HDR3 labels correctly.
$ 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.
Automatically reconstructs a former shadow set to the way it was before the shadow set was dissolved. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS.
/INCLUDE virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...])
/NOINCLUDE virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...])
Automatically mounts and restores a shadow set to the way it was before a system failure. 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 parentheses if you name only one device.
The /INCLUDE qualifier is position independent; it can appear anywhere on the command line.
The default qualifier is /NOINCLUDE.
$ MOUNT/INCLUDE DSA0: /SHADOW=$1$DUA10: 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 shadow set members that should be mounted. The /SHADOW qualifier ensures 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.
If the shadow set was properly dismounted and no write I/O requests remain outstanding, the shadow set devices are consistent and are added back without the need for a copy or merge operation. Otherwise, Volume Shadowing for OpenVMS automatically performs a copy or merge operation.
6048P039.HTM OSSG Documentation 26-NOV-1996 12:43:18.07
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.