HP OpenVMS Systems Documentation
OpenVMS DCL Dictionary
/OWNER_UIC=uicRequests that the specified UIC be assigned ownership of the volume while it is mounted, overriding the ownership recorded on the volume. If you are mounting a volume using the /FOREIGN qualifier, requests an owner UIC other than your current UIC.
The parameter, uic, specifies the user identification code (UIC) in the following format:
You must use brackets in the UIC specification. The group number is an octal number in the range 0 to 37776; the member number is an octal number in the range 0 to 177776.
The following command mounts a disk device labeled WORK on DRA3 and assigns an owner UIC of [016,360]:
/POLICY=[NO]MINICOPY[=(OPTIONAL)], REQUIRE_MEMBERS, [NO]VERIFY_LABELControls the setup and use of shadow sets.
The following table lists the keywords for this qualifier:
/PROCESSOR=keywordFor 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 Levels 2 and 5 disks, controls block cache allocation.
The following table lists the keywords for this qualifier:
The following command directs MOUNT to mount a magnetic tape on MFA0 using the same ACP process currently associated with MTA1:
/PROTECTION=keywordSpecifies the protection code to be assigned to the volume.
The following table describes the keywords for this qualifier:
If you specify the /PROTECTION qualifier when you mount a volume with the /SYSTEM or /GROUP qualifier, the specified protection code overrides any access rights implied by the other qualifiers.
If you specify the /FOREIGN qualifier, the execute (E) or create (C) and delete (D) access codes are synonyms for logical I/O (L) and physical I/O (P). You can, however, specify the access codes physical I/O (P) or logical I/O (L), or both, to restrict the nature of input/output operations that different user categories can perform.
The following command mounts a device labeled WORKDISK on DKA1 and assigns a protection code. Access to the volume will be read, write, and create for system users; read, write, create, and delete for owner; read and create for group users; and read-only for users in the world category.
/NOQUOTAControls whether quotas are to be enforced on the specified disk volume.
The default is /QUOTA, which enforces the quotas for each user. The /NOQUOTA qualifier inhibits this checking. To specify the /QUOTA qualifier, you must have the user privilege VOLPRO or your UIC must match the UIC written on the volume.
The following command specifies that the disk volume labeled WORK on DRA3 has an owner UIC of [016,360] and no quotas enforced:
/NOREBUILDControls whether or not MOUNT performs a rebuild operation on a disk volume.
If a disk volume is improperly dismounted (such as during a system failure), you must rebuild it to recover any caching limits that were enabled on the volume at the time of the dismount. By default, MOUNT attempts the rebuild. For a successful rebuild operation that includes reclaiming all of the available free space, you must mount all of the volume set members.
The rebuild may consume a considerable amount of time, depending on the number of files on the volume and, if quotas are in use, on the number of different file owners.
The following caches may have been in effect on the volume before it was dismounted:
If caching was in effect for preallocated free space or file numbers, the rebuild time is directly proportional to the greatest number of files that ever existed on the volume at one time. If disk quota caching was in effect, you can expect additional time that is proportional to the square of the number of entries in the disk quota file.
If none of these items were in effect, the rebuild is not necessary and does not occur.
If you use the /NOREBUILD qualifier, devices can be returned to active use immediately. You can then perform the rebuild later with the DCL command SET VOLUME/REBUILD.
In this example, the volume WORKDISK is mounted on NODE$DKA2. 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.
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=nSpecifies the number of characters in each record of a magnetic tape volume.
The parameter, n, specifies the block size in the range 20 to 65,532 bytes if you are using OpenVMS RMS, or 18 to 65,534 bytes if you are not using OpenVMS RMS.
You typically use this qualifier with the /FOREIGN and /BLOCKSIZE qualifiers to read or write fixed-length records on a block-structured device. In this case, the record size must be less than or equal to the block size specified or used by default.
In the following example, the magnetic tape is mounted on MTA0 with a default block size and record size of 512 characters:
/SHADOWBinds up to three physical devices into a shadow set represented by the virtual unit named in the command. This qualifier is applicable only if you have the volume shadowing option. Refer to Volume Shadowing for OpenVMS for additional information.
The format of this qualifier is:
This 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. Place the /SHADOW qualifier after the virtual-unit-name parameter.
Use the virtual unit naming format DSAn, where n is a unique number from 0 to 9999. For the physical-device-name, use the standard device-naming format $allocation-class$ddcu[:].
The following 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.
The following command creates a volume set with the logical name TEST3013. The volume set TEST3013 is shadowed, and each element of the shadowset (TEST3011 and TEST3012) is itself a volume set.
/NOSHARESpecifies, for a disk volume, that the volume is shareable.
If another user has already mounted the volume shareable, and you request it to be mounted with the /SHARE qualifier, any other qualifiers you enter are ignored.
By default, a volume is not shareable, and the MOUNT command allocates the device on which it is mounted.
If you previously allocated the device and specify the /SHARE qualifier, the MOUNT command deallocates the device so that other users can access it.
The /SHARE qualifier is incompatible with the /GROUP and /SYSTEM qualifiers.
/NOSUBSYSTEMEnables protected subsystems and the processing of subsystem ACEs. Requires the SECURITY privilege.
By default, the disk from which you boot has /SUBSYSTEM enabled but other disks do not. For further details on subsystems, refer to the OpenVMS Guide to System Security.
/SYSTEMMakes the volume public; that is, available to all users of the system, as long as the UIC-based volume protection allows them access.
The logical name for the device is placed in the system logical name table. You must have the user privilege SYSNAM to use the /SYSTEM qualifier.
When you mount a volume with the /SYSTEM qualifier in a VMScluster system, you must use a volume label that is unique clusterwide, even if the specified volume is not mounted clusterwide.
The /SYSTEM qualifier is incompatible with the /GROUP, /OVERRIDE=IDENTIFICATION, and /SHARE qualifiers.
The following 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.
/UCS_SEQUENCE=escape_sequenceSupplies the escape sequence to select the coded graphic character set, a requirement when mounting an ISO 9660 volume for one of the Supplementary Volume Descriptors (SVDs).
The parameter, escape_sequence, is a character sequence defined by the vendor who mastered the CD-ROM and is unique to the vendor's character set conversion tables.
Use the /UCS_SEQUENCE qualifier when mounting an ISO 9660 CD-ROM that contains non-ASCII character sets on OpenVMS.
An ISO 9660 volume may contain an SVD that specifies a graphic character set. This graphic character, when selected at mount time, is used as default character set when displaying a volume's directories and file names.
The /UCS_SEQUENCE qualifer defines the escape sequence to select the coded graphic character set.
All ISO 9660 volumes contain a Primary Volume Descriptor (PVD) that uses ASCII (ISO 646-IRV) as the character set. Both ISO 9660 and OpenVMS file naming conventions use the same subset of ASCII characters when displaying a volume's directories and file names.
/UNDEFINED_FAT=record-format:[record-attributes:][record-size]Establishes default file attributes to be used for records on ISO 9660 media for which no record format has been specified.
The following table describes the parameters:
ISO 9660 media can be mastered from platforms that do not support semantics of files containing predefined record formats. The /UNDEFINED_FAT qualifier establishes default file attributes to be used for records on ISO 9660 media for which no record format has been specified.
The /UNDEFINED_FAT qualifier is valid only in conjunction with the /MEDIA_FORMAT=CDROM qualifier.
This qualifier temporarily overrides all undefined file types, replacing them with selectable record formats having selectable record attributes and selectable record sizes as shown in the following illustration:
In the following example, the volume labeled OFFENS is mounted on DKA1 and all files on the volume are defined to be fixed length, carriage return, and 80 bytes in length. MOUNT also assigns the logical name STRAT.
/NOUNLOADControls whether or not the disk or magnetic tape volume or volumes specified in the MOUNT command are unloaded when they are dismounted.
In the following example, the volume labeled OFFENS is mounted on DKA1 with the /NOUNLOAD qualifier so that it can be dismounted without being physically unloaded. MOUNT also assigns the logical name STRAT.
/WINDOWS=nSpecifies the number of mapping pointers to be allocated for file windows.
The parameter, n, specifies a value from 7 to 80 that overrides the default value specified when the volume was initialized.
When a file is opened, the file system uses the mapping pointers to access data in the file. Use MOUNT/WINDOWS to override the default value specified when the volume was initialized. If no value was specified at volume initialization, the default number of mapping pointers is 7.
You must have the operator user privilege (OPER) to use the /WINDOWS qualifier.
The following command makes the volume labeled GONWITH on DKA2 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.
/NOWRITEControls whether the volume can be written.
By default, a volume is considered read/write when it is mounted. You can specify /NOWRITE to provide read-only access to protect files. This is equivalent to write-locking the device.
The following command mounts a volume labeled BOOKS on NODE$DKA1 and then proceeds to mount it on each node in the existing OpenVMS Cluster. The /NOWRITE qualifier makes the volume available for read-only access.
$ 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.
$ 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.
$ 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.
$ 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.
$ 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