Document revision date: 30 March 2001

The following command overrides the volume identification field, thus mounting a magnetic tape on MFA0 without a label specification:

$ MOUNT/OVERRIDE=IDENTIFICATION MFA0:

/OWNER_UIC=uic

The parameter, 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 to 37776; the member number is an octal number in the range 0 to 177776.

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

The following command mounts a disk device labeled WORK on DRA3 and assigns an owner UIC of [016,360]:

$ MOUNT/OWNER_UIC=[016,360] DRA3: WORK

/POLICY=[NO]MINICOPY[=(OPTIONAL)], REQUIRE_MEMBERS, [NO]VERIFY_LABEL

The following table lists the keywords for this qualifier:

Keyword	Description
[NO]MINICOPY [=OPTIONAL]	Controls the setup and use of the shadowing minicopy function. The meaning of the keyword [NO]MINICOPY[=OPTIONAL] for the MOUNT/POLICY qualifier depends on the status of the shadow set, as follows: If the shadow set is not mounted, either on a standalone system or on any cluster member, and MINICOPY=OPTIONAL is specified, the shadow set is mounted and a write bitmap is created. The write bitmap enables a shadowing minicopy operation. You must specify /MOUNT/POLICY=MINICOPY[=OPTIONAL] on the initial mount of a shadow set, either on a standalone system or in a cluster, to enable the shadowing minicopy operation. The OPTIONAL keyword allows the mount to continue, even if the system was unable to start the write bitmap. Likely reasons for the bitmap to fail to start properly include an improperly dismounted shadow set, a shadow set that requires a merge operation, and various resource problems. If the OPTIONAL keyword is omitted and the system is unable to start the write bitmap, the shadow set will not be mounted. If you specify the /POLICY=MINICOPY=OPTIONAL qualifier and the shadow set was already mounted on another node in the cluster without the /POLICY=MINICOPY[=OPTIONAL], the MOUNT command succeeds but a write bitmap is not created. If NOMINICOPY is specified, the shadow set is mounted but a write bitmap is not created. If a former member of the shadow set is returned to the shadow set, which has minicopy enabled, then a minicopy is started instead of a full copy. This is the default behavior and will occur even if you omit /POLICY=MINICOPY[=OPTIONAL]. If a minicopy is successfully started and then fails for some reasons, a full copy is performed. If a minicopy cannot be started and the keyword OPTIONAL was omitted, the mount will fail. If NOMINICOPY is specified, then no minicopy is performed, even if one is possible.
REQUIRE_MEMBERS	Requires that all of the proposed members must be accessible before the shadow set is mounted. You can specify the proposed members in the command line or by using the /INCLUDE qualifier. The default behavior is that if one or more members is not accessible for any reason (such as a connectivity failure) then the shadow set will be created with the remaining members. This option is especially useful in disaster tolerant clusters to insure that the correct member is selected as the master member following an event.
[NO]VERIFY_LABEL	Require that any member that is going to be added to the shadow set must have a volume label of 'SCRATCH_DISK'. This will help insure that the wrong disk is not added to a shadow set by mistake. If VERIFY_LABEL is going to be used, then the disk that is going to be added to the set must be either initialized with the label 'SCRATCH_DISK' or a SET VOLUME/LABEL must be performed. The default behavior is NOVERIFY_LABEL, which indicates that the volume label of the copy targets will not be checked.

/PROCESSOR=keyword

For Files-11 Structure Levels 2 and 5 disks, controls block cache allocation.

The following table lists the keywords for this qualifier:

Keyword	Description
UNIQUE	Creates a new process to execute the default ancillary control process (ACP) image supporting the magnetic tape, Files-11 ODS-1, ISO 9660, or High Sierra formatted media being mounted. For Files-11 Structure Levels 2 and 5 disks, allocates a separate block cache.
SAME:device	Uses an existing process that is executing the same ACP image supporting the magnetic tape, Files-11 ODS-1, ISO 9660, or High Sierra formatted media being mounted. For Files-11 Structure Levels 2 and 5 disks, takes the block cache allocation from the specified device.
file-spec	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 privileges. You must have the operator user privilege OPER to use the /PROCESSOR qualifier.

Example

The following command directs MOUNT to mount a magnetic tape on MFA0 using the same ACP process currently associated with MTA1:

$ MOUNT/PROCESSOR=SAME:MTA1: MFA0:

/PROTECTION=keyword

The following table describes the keywords for this qualifier:

Keyword	Description
protection code	Specifies the protection code according to the standard syntax rules for specifying user protection (that is, system/owner/group/world). 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.
XAR	Enables enforcement of the extended record attribute (XAR) access controls. For more information about XAR, refer to the OpenVMS Record Management Services Reference Manual.
DSI	Enables XAR permissions Owner and Group for XARs containing Digital System Identifiers (DSI). For more information, refer to the OpenVMS Record Management Services Reference Manual.

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.

To use the /PROTECTION qualifier on a Files-11 volume, you must have the user privilege VOLPRO or your UIC must match the UIC written on the volume.

Example

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.

$ MOUNT/PROTECTION=(SYSTEM:RWE,O:RWED,G:RE,W:R) DKA1: WORKDISK

/QUOTA (default)

/NOQUOTA

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.

Example

The following command specifies that the disk volume labeled WORK on DRA3 has an owner UIC of [016,360] and no quotas enforced:

$ MOUNT/OWNER_UIC=[016,360]/NOQUOTA DRA3: WORK

/REBUILD (default)

/NOREBUILD

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:

• Preallocated free space (EXTENT cache)
• Preallocated file numbers (FILE_ID cache)
• Disk quota usage caching (QUOTA cache)

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.

For information about how to rebuild the system disk, refer to the OpenVMS System Manager's Manual.

Examples

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.

$ MOUNT/REBUILD NODE$DKA2: WORKDISK %MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DKA2: %MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress

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.

$ MOUNT/NOREBUILD NODE$DKA2: WORKDISK %MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DKA2: %MOUNT-I-REBLDREQD, rebuild not performed; some free space unavailable; diskquota usage stale

/RECORDSIZE=n

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.

Use the /RECORDSIZE qualifier when mounting magnetic tapes without HDR2 labels (such as RT-11 magnetic tapes) to provide OpenVMS RMS with default values for the maximum record size.

Example

In the following example, the magnetic tape is mounted on MTA0 with a default block size and record size of 512 characters:

$ MOUNT/FOREIGN/BLOCKSIZE=512/RECORDSIZE=512 MTA0:

/SHADOW

The format of this qualifier is:

(virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...]))

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[:].

Examples

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.

$ 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

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.

$ MOUNT/BIND=TEST3013 DSA3011/SHADOW=($1$DUA402:,$1$DUA403:), DSA3012/SHADOW=($1$DUA404:,$1$DUA405:) TEST3011,TEST3012 TEST3013

/SHARE

/NOSHARE

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.

Example

The following 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:

$ MOUNT/NOMESSAGE/SHARE DLA0: SLIP DISC

/SUBSYSTEM

/NOSUBSYSTEM

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.

Example

The following command mounts the volume labeled SLIP on DUA1 with mount messages disabled. Subsystems on the volume are accessible. MOUNT also assigns the logical name SACH.

$ MOUNT/NOMESSAGE/SUBSYSTEM DUA1: SLIP SACH

/SYSTEM

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.

Examples

The following 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.

$ MOUNT/NOMESSAGE/SYSTEM DUA1: SLIP SACH

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.

$ MOUNT/SYSTEM/BIND=MASTER_PAY - _$ DB1:,DB2:,DB3: PAYVOL1,PAYVOL2,PAYVOL3

/UCS_SEQUENCE=escape_sequence

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]

The following table describes the parameters:

Parameter	Description
record-format	Specifies the format for all records in a file: FIXED, VARIABLE, STREAM, STREAM_LF, STREAM_CR, LSB_VARIABLE, or MSB_VARIABLE. For a description of these record formats, refer to the discussion of the RMS field FAB$B_RFM in the OpenVMS Record Management Services Reference Manual.
record-attributes	Specifies the attributes for all records in a file: NONE, CR, FTN, PRN, NOBKS. Applies only to non-STREAM record formats. For a description of these record attributes, refer to the discussion of the RMS field FAB$B_RAT in the OpenVMS Record Management Services Reference Manual.
record-size	Specifies the maximum record size for all records in a file: 0 to 32767. Applies only to FIXED or STREAM record formats. For a description of possible RMS record sizes, refer to the discussion of the RMS field FAB$W_MRS in the OpenVMS Record Management Services Reference Manual.

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:

Example

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.

$ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=(FIXED:CR:80) DKA1: OFFENS STRAT

/UNLOAD (default)

/NOUNLOAD

Example

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.

$ MOUNT/NOUNLOAD DKA1: OFFENS STRAT

/WINDOWS=n

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.

Example

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.

$ MOUNT/SYSTEM/WINDOWS=25 DKA2: GONWITH THE_WINDOW

/WRITE (default)

/NOWRITE

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.

Example

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/CLUSTER/NOWRITE NODE$DKA1: BOOKS

Examples

For examples 1 and 2, operator assistance is not required, assuming the volumes are in the drives. Examples 3 to 6 describe operator-assisted mounts. Examples 7 and 8 describe mounting ISO 9660 CD-ROM volume sets, example 9 makes subsystems on a volume accessible, and example 10 demonstrates mounting a shadow set.

$ 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
      

---

Previous

Next

Contents

Index

	privacy and legal statement
9996PRO_039.HTML