[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

HP OpenVMS DCL Dictionary

Example

In the following example, 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.

$ INITIALIZE  MTA0: ABCD
$ MOUNT/NOHDR3 MTA0: ABCD

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

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

Automatically reconstructs a former shadow set to the way it was before the shadow set was dissolved. This qualifier is applicable only if you have the volume shadowing option. Refer to HP Volume Shadowing for OpenVMS for additional information.

The /INCLUDE qualifier 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.

Example

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

$ 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

/INITIALIZE=CONTINUATION

Specifies that any volume added to the magnetic tape volume set is initialized before you can write to the volume.

Example

The /INITIALIZE=CONTINUATION qualifier instructs the MOUNT command to assign its own continuation label. In this case, the operator can enter the command REPLY/BLANK=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).

$ MOUNT/INITIALIZE=CONTINUATION MTA0: ABCD

/LABEL (default)

/NOLABEL

Indicates that the volume is in the standard format used by the OpenVMS operating system; that is, a magnetic tape volume is in the standard ANSI format, or a disk volume is in Files-11 format.

The default is /LABEL.

Note that /NOLABEL is equivalent to /FOREIGN; they both set the FOREIGN flag.

Example

The following command mounts an ANSI-labeled magnetic tape on MFA1 and assigns the default logical name as TAPE$TAPE.

$ MOUNT/LABEL MFA1: TAPE

/MEDIA_FORMAT=CDROM

Mounts a volume assuming the media to be ISO 9660 (or High Sierra) formatted.

The /MEDIA_FORMAT=CDROM qualifier instructs the mount subsystem to attempt to mount a volume assuming the media to be ISO 9660 (or High Sierra) formatted.

Note

This qualifier specifies a CD-ROM mount (ISO 9660 or High Sierra). Specify this qualifier when a volume is known to be in either ISO 9660 or High Sierra CD-ROM format.

The Mount command attempts to read a CD-ROM in Files-11 ODS-2 format by default. This qualifier prevents the Mount command from attempting a Files-11 ODS-2 mount sequence.

Because it is possible to record parts of a CD-ROM in Files-11 ODS-2 and other parts in ISO 9660 format, this qualifier can be used to specify a CD-ROM mount (ISO 9660 or High Sierra).

/MEDIA_FORMAT=[NO]COMPACTION

Enables and controls data compaction and data record blocking on tape drives that support data compaction.

The /MEDIA_FORMAT qualifier allows you to mount a tape and enable data compaction and record blocking on a tape drive that supports data compaction. Data compaction and record blocking increase the amount of data that can be stored on a single tape.

Records can either be compacted and blocked, or they can be recorded in the same way that they would be recorded on a noncompacting tape drive. Note that for compacting tape drives, once data compaction or noncompaction has been selected for a given tape, that status applies to the entire tape.

The /MEDIA_FORMAT=[NO]COMPACTION qualifier is incompatible with the /DENSITY qualifier.

For Files-11 tapes, when you enable data compaction, caching is automatically enabled.

Note

The /MEDIA_FORMAT=[NO]COMPACTION qualifier is meaningful only for foreign mounts.

The /MEDIA_FORMAT=[NO]COMPACTION qualifier has no effect on a Files-11 tape. The compaction state of a Files-11 tape is determined by the state established when the tape is initialized.

Examples

The following command performs a foreign mount of a tape with data compaction and record blocking enabled and assigns the logical name BOOKS to the tape:

$ MOUNT/FOREIGN/MEDIA_FORMAT=COMPACTION MUA0: BOOKS

The following MOUNT command attempts a Files-11 mount of a tape labeled BOOKS with data compaction and record blocking enabled. Because the tape was initialized with compaction disabled, the MOUNT qualifier /MEDIA_FORMAT=COMPACTION has no effect.

$ INIT/MEDIA_FORMAT=NOCOMPACTION MUA0: BOOKS
$ MOUNT/MEDIA_FORMAT=COMPACTION MUA0: BOOKS

/MESSAGE (default)

/NOMESSAGE

Causes mount request messages to be sent to your current SYS$OUTPUT device.

If you specify /NOMESSAGE during an operator-assisted mount, messages are not output to SYS$OUTPUT; the operator sees them, however, provided an operator terminal is enabled.

Example

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/NOMESSAGE DLA0: SLIP DISC

/MOUNT_VERIFICATION (default)

/NOMOUNT_VERIFICATION

Specifies that the device is a candidate for mount verification.

The /MOUNT_VERIFICATION qualifier affects the following media:

Files-11 Structure Level 2 or 5 disks (mount verification is not supported for foreign-mounted disks)
ISO 9660 and High Sierra CD-ROMs
Foreign and ANSI-labeled magnetic tape volumes

Example

The following command mounts an HSG80 Fibre Channel disk 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.

$ MOUNT/CACHE=(NOEXTENT,NOFILE_ID,NOQUOTA,WRITETHROUGH) -
_$ /NOMOUNT_VERIFICATION  $1$DGA0: FILES WORK
%MOUNT-I-MOUNTED, FILES         mounted on _$1$DGA0: (NODE)

/MULTI_VOLUME

/NOMULTI_VOLUME (default)

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 OpenVMS 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.

Use this qualifier when a utility that supports multiple-volume, foreign-mounted magnetic tape sets needs to process subsequent volumes, and these volumes do not contain labels that the OpenVMS Mount command can interpret.

By default, all tape volumes are subject to the complete access checks of the OpenVMS Mount command (MOUNT). Some user-written and vendor-supplied utilities used prior to OpenVMS Version 5.0 may mount only the first tape in a foreign tape set. To make these utilities compatible with more recent versions of OpenVMS, alter them to perform explicit calls to the $MOUNT and $DISMOU system services for each reel in the set. As an alternative, you can now mount the magnetic tape sets to be used by these utilities with the /MULTI_VOLUME qualifier.

You must specify the /FOREIGN qualifier with the /MULTI_VOLUME qualifier and you must have the user privilege VOLPRO. The default is /NOMULTI_VOLUME.

Note

The OpenVMS Backup utility (BACKUP) explicitly calls the $MOUNT and $DISMOU system services on each reel of a foreign-mounted magnetic tape set. For additional information, Refer to the section on multivolume save sets and BACKUP in the HP OpenVMS System Management Utilities Reference Manual: A--L.

Example

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

$ MOUNT/FOREIGN/MULTI_VOLUME MUA0:

/OVERRIDE=(keyword[,...])

Inhibits one or more protection checks that the MOUNT command performs.

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.

If you specify more than one keyword, separate them with commas and enclose the list in parentheses.

The following table lists the keywords for this qualifier:

Keyword	Description
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, the OpenVMS operating system provides a routine that checks this field in the following manner: If the magnetic tape was created on a version of OpenVMS that conforms to Version 3 of ANSI, then you must use this keyword to override any character other than an ASCII space. If an OpenVMS 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, or (on VAX systems) for an ISO 9660 volume whose label is not unique in the first 12 characters. Only the volume identifier field is overridden. Volume protection, if any, is preserved. The volume must be mounted /NOSHARE (either explicitly or by default). The /OVERRIDE=IDENTIFICATION qualifier is incompatible with the /GROUP and /SYSTEM qualifiers.
LIMITED_SEARCH	Allows the Mount command to search an entire device for a home block, if a home block is not found at the expected location. By default, the search for a home block is limited to avoid excessive search times if no valid home block is present.
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 ANALYZE/DISK_STRUCTURE command. You must have VOLPRO privilege or own the volume to use the LOCK keyword.
NO_FORCED_ERROR	Directs the Mount command to proceed with shadowing, even though the device or controller does not support forced error handling. Using unsupported SCSI disks can cause members to be removed from a shadow set if certain error conditions arise that cannot be corrected, because some SCSI disks do not implement READL and WRITEL commands that support disk bad block repair.
OWNER_IDENTIFIER	For magnetic tapes only. Overrides the processing of the owner identifier field. Use this keyword to interchange protected magnetic tapes between OpenVMS and other HP operating systems.
SECURITY	Allows you to continue mounting a volume if an error is returned because the volume has an invalid SECURITY.SYS file. You must have the user privilege VOLPRO or own the volume to use this keyword.
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	Allows you to override the write protection of former shadow set members. Applicable only if you have the volume shadowing option. Refer to HP Volume Shadowing for OpenVMS. 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.

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

Requests 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:

[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

Controls the setup and use of shadow sets. For more information about volume shadowing, refer to HP Volume Shadowing for OpenVMS.

The following table lists the keywords for this qualifier:

Keyword

Description

[NO]MINICOPY [=OPTIONAL] (Alpha only)

Controls the setup and use of the shadowing minicopy function.

Requires LOG_IO (logical I/O) privilege to create bitmaps.

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

Controls whether every physical device specified with the /SHADOW qualifier must be accessible when the MOUNT command is issued in order for the MOUNT command to take effect. The proposed members are either specified in the command line or found on the disk by means of the /INCLUDE qualifier.

The behavior, without this qualifier, is that if one or more members is not accessible for any reason (such as a connectivity failure), then the virtual unit will be created with the members that are accessible.

This option is especially useful in the recovery of disaster-tolerant clusters because it ensures that the correct membership is selected after 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 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:

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

Specifies the protection code to be assigned to the volume.

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

Controls 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.

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

Controls 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:

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 HP 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

Contents

Index