HELPLIB.HLB  —  MOUNT  Qualifiers

1    /ACCESSED

       /ACCESSED=n

    Specifies, for ODS-1 disk volumes, the approximate number of
    directories that will be in use concurrently on the volume. (The
    /ACCESSED qualifier is meaningless for ODS-2 volumes.)

    Specify a value from 0 to 255 to override the default that was
    specified when the volume was initialized.

    You need the user privilege OPER to use /ACCESSED.

    Example

    The following command requests the volume labeled WORK to
    be mounted on DKA1, specifying 150 as the number of active
    directories on the volume:

    $ MOUNT/ACCESSED=150 DKA1 WORK

2    /ASSIST

       /ASSIST (default)
       /NOASSIST

    Directs the mount operation to allow operator or user
    intervention if the mount request fails.

    When you specify the /ASSIST qualifier, MOUNT notifies the user
    and certain classes of operator if a failure occurs during the
    mount operation. If a failure occurs, the operator or user can
    either abort the operation or correct the error condition to
    allow the operation to continue.

    The operator-assist messages are sent to all operator terminals
    that are enabled to receive messages; magnetic tape mount
    requests go to TAPE and DEVICE operators, and disk mount requests
    go to DISK and DEVICE operators. Thus, if you need operator
    assistance while mounting a disk device, a message is sent to
    DISK operators. See the description of the REPLY command for more
    information about enabling and disabling operator terminals.

    Any operator reply to a mount request is written to SYS$OUTPUT
    to be displayed on the user's terminal or written in a batch job
    log.

    If no operator terminal is enabled to receive and respond to
    a mount assist request, a message is displayed informing the
    user of the situation. If a volume is placed in the requested
    drive, no additional operator response is necessary. If the mount
    request originates from a batch job and no operator terminal
    is enabled to receive messages, the mount is aborted. See the
    OpenVMS System Messages: Companion Guide for Help Message Users
    for a description of the error messages and their suggested user
    actions.

    The default is /ASSIST and can be overridden by /NOASSIST.

    Example

    The following command mounts an HSG80 Fibre Channel disk volume
    labeled DOC and assigns the logical name WORK. The /NOASSIST
    qualifier signals MOUNT that no operator intervention is
    necessary.

    $ MOUNT/NOASSIST $1$DGA0: DOC WORK
    %MOUNT-I-MOUNTED, DOC         mounted on _$1$DGA0: (NODE)

3    /AUTOMATIC

       /AUTOMATIC (default)
       /NOAUTOMATIC

    Determines whether MOUNT enables or disables automatic volume
    switching and labeling for magnetic tape or ISO 9660 CD-ROM.

    Magnetic Tape

    If you have multiple magnetic tape drives allocated to a volume
    set, the magnetic tape ancillary control process (MTACP) performs
    the volume switch by sequentially selecting the next available
    drive allocated to the volume set. The MTACP expects the next
    reel of the volume set to be loaded on that drive.

    If the MTACP is writing to the volume set, it creates a label and
    initializes the magnetic tape with that label and the protections
    established for the first magnetic tape of the volume set. If it
    is reading from the volume set, the MTACP generates the label and
    attempts to mount the next magnetic tape with that label. If the
    drive has the wrong magnetic tape (or no magnetic tape) loaded,
    the MTACP sends a message to the operator's console to prompt for
    the correct magnetic tape.

    The label generated by the MTACP fills the 6-character volume
    identifier field. The first four characters of the field contain
    the first four characters of the label specified in the MOUNT
    command, padded with underscores when the label is not at least
    four characters. The fifth and sixth characters contain the
    relative volume number for this reel in the volume set.

    If you specify /NOAUTOMATIC, the MTACP requires operator
    intervention to switch to the next drive during end-of-tape
    processing, and requires that the operator specify a label for
    each new reel added to a volume set.

    ISO 9660 CD-ROM

    Under ISO 9660, not all volume-set members must be mounted to
    perform I/O operations against that volume set. By default, if
    I/O operations attempt to access an unmounted volume-set member,
    an operator message is sent to all DISK CLASS operators for
    system-mounted volume sets, or the owning process for privately
    mounted volume sets. The message specifies the volume-set member
    to mount to complete the I/O operation requested. If /NOAUTOMATIC
    is specified, then an I/O operation to a nonmounted volume set
    member completes with an error message SS$_DEVNOTMOUNT.

    Example

    The following command instructs MOUNT not to generate its own
    label for the second volume, but to use the ones supplied with
    the MOUNT command instead. If the second volume is not already
    labeled, then the operator must use REPLY/INIT and supply the
    second label.

    $ MOUNT/NOAUTOMATIC MTA0: ABCD,EFGH

4    /BIND

       /BIND=volume-set-name

    Creates a volume set of one or more disk volumes or adds one or
    more volumes to an existing volume set.

    The parameter, volume-set-name, specifies a 1- to 12-
    alphanumeric-character name identifying the volume set.

    An ISO 9660 volume-set name can be from 1 to 128 characters in
    length.

    OpenVMS requires volume-set names to be unique in the first 12
    characters. In addition, if the first 12 characters of volume-set
    name are the same as the first 12 characters of any volume label,
    a lock manager deadlock will occur. To avoid this problem, you
    must override either the volume label (by using the /OVERRIDE
    qualifier) or the volume-set name (by using the /BIND qualifier).

    You must specify the /BIND qualifier when you first create the
    volume set or each time you add a volume to the set. To dismount
    an individual volume of the volume set, you must use the DISMOUNT
    qualifier /UNIT; otherwise, dismounting an individual volume
    dismounts the entire volume set.

    When you create a volume set, the volumes specified in the
    volume-label list are assigned relative volume numbers based
    on their positions in the label list. The first volume specified
    becomes the root volume of the set.

    When you add a volume or volumes to a volume set, the first
    volume label specified must be that of the root volume, or the
    root volume must already be on line.

    Note that if you attempt to create a volume set from two or more
    volumes that already contain files and data, the file system does
    not issue an error message when you issue the MOUNT/BIND command.
    However, the volumes are unusable as a volume set because the
    directory structures are not properly bound.

    If you mount an ISO 9660 volume using the /SYSTEM or /CLUSTER
    qualifier, and the volume label is not unique within the first
    12 characters, you must supply an alternate 12-character volume
    label using the qualifier /BIND=volume-set-name. If you choose
    this option, then Mount verification is disabled for the device.

                                   NOTE

       Once a volume is bound into a volume set, it cannot easily
       be unbound. To unbind a bound volume set (BVS):

       1. Do an image backup of the BVS.

       2. Initialize all volumes of the BVS.

       3. Do an image restore to a single volume with the
          /NOINITIALIZE qualifier, or do a nonimage restore to a
          single volume.

    Examples

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

    $ MOUNT/BIND=LIBRARY  DMA0:,DMA1:,DMA2:  BOOK1,BOOK2,BOOK3

    The following command creates a volume set with the logical
    name TEST3. The volume set TEST3 is not shadowed, however each
    element of the volume set (TEST3011 and TEST3012) is a shadow
    set, providing redundancy for the volume set as a whole.

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

5    /BLOCKSIZE

       /BLOCKSIZE=n

    Specifies the default block size for magnetic tape volumes.

    The parameter, 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:

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

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

    Example

    In the following example, the /BLOCKSIZE qualifier specifies a
    block size of 1000 bytes; the default for a magnetic tape mounted
    with the /FOREIGN qualifier is 512.

    $ MOUNT/FOREIGN/BLOCKSIZE=1000 MTA1:

6    /CACHE

       /CACHE=(keyword[,...])
       /NOCACHE

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

    The following table lists the keywords for this qualifier:

    Keyword          Description

    DATA (default)   Enable or disable Extended File Caching (XFC). To
    and NODATA       enable XFC caching, you must specify the DATA (this
                     is the default value for /CACHE qualifier). To
                     disable XFC, specify NODATA. Note that /NOCACHE is
                     equivalent to /CACHE=NODATA.

    EXTENT[=n]       Enable or disable extent caching. To enable extent
    and NOEXTENT     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]      Enable or disable file identification caching.
    and NOFILE_ID    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]        Enable or disable quota caching. To enable quota
    and NOQUOTA      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/NOCACHE

    WRITETHROUGH     Disables the deferred write feature for file
                     headers. By default, this feature is enabled, which
                     improves the performance of applications, such as
                     PATHWORKS, that use it. The deferred write feature
                     is not available on Files-11 ODS-1 volumes.

                                   NOTE

       In a mixed-version OpenVMS cluster, an attempt to mount a
       volume with /CLUSTER and /CACHE=[NO]DATA from a V8.4 system
       fails on the pre-V8.4 systems (%MOUNT-W-RMTMNTFAIL) with
       MOUNT-F-BADPARAM.

       For more information on the restriction, see Enabling or
       Disabling XFC While Mounting a Volume in the OpenVMS Version
       8.4 New Features and Documentation Overview manual.

    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,
    NODATA).

    In the following command, NODATA is taken as default when you
    supply the following qualifiers NOEXTENT, NOFILE_ID, NOQUOTA,
    WRITETHROUGH (that is, XFC is disabled):

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

    In the following command, DATA is take as default (that is, XFC
    is enabled):

    $ MOUNT/CACHE=(FILE_ID=10)
    _$ $1$DGA0: FILES WORK
    %MOUNT-I-MOUNTED, FILES mounted on $1$DGA0: (NODE)

    If you specify /NOCACHE for a magnetic tape device, the tape
    controller's write cache is disabled for this volume.

    Examples

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

    $ MOUNT/CACHE=(EXTENT=60,FILE_ID=60,QUOTA=20,WRITETHROUGH) -
    _$ $1$DGA0: FILES WORK
    %MOUNT-I-MOUNTED, FILES         mounted on _$1$DGA0: (NODE)

    The following command mounts the volume TAPE on device MUA0 and
    instructs MOUNT to enable the tape controller's write cache for
    MUA0:

    $ MOUNT/CACHE=TAPE_DATA MUA0:  TAPE
    %MOUNT-I-MOUNTED, TAPE  mounted on _NODE$MUA0:

    The following command enables data cache (XFC) on a disk. The
    /CACHE=DATA qualifier is the default value for a basic MOUNT
    command:

    $ MOUNT/CACHE=(DATA)
    _$ $1$DGA0: FILES WORK
    %MOUNT-I-MOUNTED, FILES mounted on $1$DGA0: (NODE)

    The following command disables data cache (XFC) on a disk.
    /NOCACHE qualifier is equivalent to /CACHE=(NODATA):

    $ MOUNT/CACHE=(NODATA)
    _$ $1$DGA0: FILES WORK
    %MOUNT-I-MOUNTED, FILES mounted on $1$DGA0: (NODE)

    The following command disables data cache that is, XFC and
    metadata cache that is, XQP. /NOCACHE qualifier is equivalent
    to /CACHE=(NODATA):

    $ MOUNT/NOCACHE
    _$ $1$DGA0: FILES WORK
    %MOUNT-I-MOUNTED, FILES mounted on $1$DGA0: (NODE)

7    /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
    OpenVMS Cluster (that is, the volume is mounted clusterwide).

    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.

    Example

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

    $ 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: ODS-2, subject to mount verification,
         file high-water marking, write-through XQP caching enabled,
         write-through XFC caching enabled.
      Volume is also mounted on DOC, HAPPY, GRUMPY, SLEEPY, SNEEZY, BASHFUL.

8    /COMMENT

       /COMMENT=string

    Specifies additional information to be included with the operator
    request when the mount operation requires operator assistance.

    The parameter, 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

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

    $ 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

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

    $ 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-1990 10:27:38.15, request 2 pending by operator TTB6
    %MOUNT-I-OPREPLY, This is a '/abort' response from the operator.
    31-DEC-1990 10:29:59.34, request 2 aborted by operator TTB6
    %MOUNT-F-OPRABORT, mount aborted by operator

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

    $ 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-1990 10:43:42.30, request 3 completed by operator TTB6
    %MOUNT-I-MOUNTED, TESTSYS    mounted on _DYA1:

9    /CONFIRM

       /CONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-
       name[:][,...])
       /NOCONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-
       name[:][,...])

    Causes MOUNT to pause and request confirmation before performing
    a copy operation on the specified disk device. This qualifier is
    applicable only if you have the volume shadowing option. See the
    VSI Volume Shadowing for OpenVMS for additional information.

    This qualifier 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.

    Example

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

    $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

10    /COPY

       /COPY virtual-unit-name[:] /SHADOW=(physical-dev-
       name[:][,...]) (default)
       /NOCOPY virtual-unit-name[:] /SHADOW=(physical-dev-
       name[:][,...])

    Enables or disables copy operations on physical devices specified
    when you mount a shadow set. This qualifier is applicable only if
    you have the volume shadowing option. See the VSI Volume Shadowing
    for OpenVMS for additional information.

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

    Example

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

    $ 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

11    /DATA_CHECK

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

    Overrides the read-check or write-check option (or both)
    specified for a volume when it was initialized.

    The keyword, READ, performs checks following all read operations,
    and the keyword, 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.

    Example

    The following command mounts a volume labeled SAM on CLEMENS$DKA2
    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.

    $ MOUNT/DATA_CHECK=READ CLEMENS$DKA2: SAM  BOOK

12    /DENSITY

       /DENSITY=keyword

    Specifies the density at which a magnetic tape is to be written.
    This qualifier is valid only if you mount a tape specifying the
    /FOREIGN qualifier. If you change the density on a tape, the
    first operation on the tape must be a write operation.

    The densities supported for tapes are shown in the following
    table:

    Table 1 Keywords for Tapes

    Keyword        Meaning

    DEFAULT        Default density
    800            NRZI 800 bits per inch (BPI)
    1600           PE 1600 BPI
    6250           GRC 6250 BPI
    3480           IBM 3480 HPC 39872 BPI
    3490E          IBM 3480 compressed
    833            DLT TK50: 833 BPI
    TK50           DLT TK50: 833 BPI
    TK70           DLT TK70: 1250 BPI
    6250           RV80 6250 BPI EQUIVALENT
            NOTE: Only the symbols listed above are understood
           by TMSCP/TUDRIVER code prior to OpenVMS Version 7.2.
            The remaining symbols in this table are supported
           only on OpenVMS Alpha and Integrity server systems.

    TK85           DLT Tx85: 10625 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK86           DLT Tx86: 10626 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK87           DLT Tx87: 62500 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK88           DLT Tx88: (Quantum 4000)-Cmpt IV - Alpha/Integrity
                   servers only
    TK89           DLT Tx89: (Quantum 7000)-Cmpt IV - Alpha/Integrity
                   servers only
    QIC            All QIC drives are drive-settable only -
                   Alpha/Integrity servers only

    TK85           DLT Tx85: 10625 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK86           DLT Tx86: 10626 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK87           DLT Tx87: 62500 BPI-Cmpt III - Alpha/Integrity
                   servers only
    TK88           DLT Tx88: (Quantum 4000)-Cmpt IV - Alpha/Integrity
                   servers only
    TK89           DLT Tx89: (Quantum 7000)-Cmpt IV - Alpha/Integrity
                   servers only
    QIC            All QIC drives are drive-settable only -
                   Alpha/Integrity servers only
    8200           Exa-Byte 8200 - Alpha/Integrity servers only
    8500           Exa-Byte 8500 - Alpha/Integrity servers only
    DDS1           Digital Data Storage 1-2G - Alpha/Integrity
                   servers only
    DDS2           Digital Data Storage 2-4G - Alpha/Integrity
                   servers only
    DDS3           Digital Data Storage 3-8-10G - Alpha/Integrity
                   servers only
    DDS4           Digital Data Storage 4 - Alpha/Integrity servers
                   only
    AIT1           Sony Advanced Intelligent Tape 1 - Alpha/Integrity
                   servers only
    AIT2           Sony Advanced Intelligent Tape 2 - Alpha/Integrity
                   servers only
    AIT3           Sony Advanced Intelligent Tape 3 - Alpha/Integrity
                   servers only
    AIT4           Sony Advanced Intelligent Tape 4 - Alpha/Integrity
                   servers only
    DLT8000        DLT 8000 - Alpha/Integrity servers only
    8900           Exabyte 8900 - Alpha/Integrity servers only
    SDLT           SuperDLT1 - Alpha/Integrity servers only
    SDLT320        SuperDLT320 - Alpha/Integrity servers only

    Note that tape density keywords cannot be abbreviated.

    When you initialize a tape with the INITIALIZE command and do
    not specify a density, the tape is initialized at the default
    density for the media and drive you are using (usually the
    highest density available).

    The density of a tape can only be changed if the tape is at
    beginning-of-tape (BOT). To change the density of a tape that
    has previously been recorded, the first operation must be a
    write operation. If the first operation on the tape is a read
    operation, the magnetic tape is set to the density at which the
    first record on the tape was recorded, no matter what density is
    specified with the /DENSITY qualifier.

    Example

    The following command mounts a tape on the MFA0: drive /FOREIGN
    and assigns it the logical name TAPE. The /DENSITY qualifier
    specifies that the tape is to be written at TK87.

    $ MOUNT/FOREIGN/DENSITY=TK87  MFA0: TAPE

13    /EXTENSION

       /EXTENSION=n

    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.

    The parameter, n, specifies a value from 0 to 65,535 to override
    the value specified when the volume was initialized.

    Example

    The following command mounts a volume labeled DOC on DKA0,
    assigns the logical name WORK, and specifies a default block
    extent of 64 for the files on WORK:

    $ MOUNT/EXTENSION=64 DKA0: DOC WORK

14    /FOREIGN

    Indicates that the volume is not in the standard format used by
    the OpenVMS operating system.

    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 (available on the
    Documentation CD-ROM).

    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

    The following command mounts a foreign magnetic tape on drive
    MTA1:

    $ MOUNT/FOREIGN MTA1: ABCD TAPE

    The following command mounts an RK07 device as a foreign volume
    on DMA2 and assigns the default logical name as DISK$SAVEDISK.
    As a volume that is not file structured, SAVEDISK can be used for
    sequential-disk BACKUP save operations.

    $ MOUNT/FOREIGN DMA2: SAVEDISK

15    /GROUP

    Makes the volume available to other users with the same group
    number in their UICs as the user entering the MOUNT command.

    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

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

    $ MOUNT/GROUP DB1:, DB2:, DB3: PAYVOL1,PAYVOL2,PAYVOL3  PAY

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

    $ MOUNT/GROUP/BIND=MASTER_PAY DB4: PAYVOL4

16    /HDR3

       /HDR3 (default)
       /NOHDR3

    Controls whether ANSI standard header label 3 is written on a
    magnetic tape volume.

    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.

    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

17    /INCLUDE

       /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. See the VSI 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

18    /INITIALIZE

       /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

19    /LABEL

       /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

20    /MEDIA_FORMAT

       /MEDIA_FORMAT=CDROM
       /MEDIA_FORMAT=[NO]COMPACTION

    /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

21    /MESSAGE

       /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

22    /MOUNT_VERIFICATION

       /MOUNT_VERIFICATION (default)
       /NOMOUNT_VERIFICATION

    Specifies that the device is a candidate for mount verification.

    The /MOUNT_VERIFICATION qualifier affects the following media:

    o  Files-11 Structure Level 2 or 5 disks (mount verification is
       not supported for foreign-mounted disks)

    o  ISO 9660 and High Sierra CD-ROMs

    o  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, data 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)

23    /MULTI_VOLUME

       /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, see the section on multivolume save sets
       and BACKUP in the VSI 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:

24    /OVERRIDE

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

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

                   o  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 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_       Allows the Mount command to search an entire
    SEARCH         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_     Directs the Mount command to proceed with
    ERROR          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_         For magnetic tapes only. Overrides the processing
    IDENTIFIER     of the owner identifier field. Use this keyword
                   to interchange protected magnetic tapes between
                   OpenVMS and other 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_        Allows you to override the write protection of
    MEMBERSHIP     former shadow set members. Applicable only if
                   you have the volume shadowing option. see the VSI
                   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:

25    /OWNER_UIC

       /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

26    /POLICY

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

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

 The following table lists the keywords for this qualifier:

    Keyword        Description

    [NO]MINICOPY   Controls the setup and use of the shadowing
    [=OPTIONAL]    minicopy function.
    (Alpha/Integrity
    servers        Requires LOG_IO (logical I/O) privilege to create
    only)          bitmaps.

                   The meaning of the keyword [NO]MINICOPY[=OPTIONAL]
                   for the MOUNT/POLICY qualifier depends on the
                   status of the shadow set, as follows:

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

                   2. 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_       Controls whether every physical device specified
    MEMBERS        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_    Require that any member that is going to be added
    LABEL          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.

27    /PROCESSOR

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

28    /PROTECTION

       /PROTECTION=keyword

    Specifies the protection code to be assigned to the volume.

    The following table describes the keywords for this qualifier:

    Keyword       Description

    protection    Specifies the protection code according to
    code          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, see the OpenVMS Record
                  Management Services Reference Manual.

    DSI           Enables XAR permissions Owner and Group for XARs
                  containing Digital System Identifiers (DSI). For
                  more information, see 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

29    /QUOTA

       /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

30    /REBUILD

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

    o  Preallocated free space (EXTENT cache)

    o  Preallocated file numbers (FILE_ID cache)

    o  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, see the VSI
    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

31    /RECORDSIZE

       /RECORDSIZE=n

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

    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:

32    /SHADOW

    Binds 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. See
    the VSI Volume Shadowing for OpenVMS for additional information.

    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 not shadowed. However, each
    element of the volume set (TEST3011 and TEST3012) is a shadow
    set, providing redundancy for the volume set as a whole.

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

33    /SHARE

       /SHARE
       /NOSHARE

    Specifies, 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.

    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

34    /SUBSYSTEM

       /SUBSYSTEM
       /NOSUBSYSTEM

    Enables 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, see
    the VSI 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

35    /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.

    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

36    /UCS_SEQUENCE

       /UCS_SEQUENCE=escape_sequence

    Supplies 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 qualifier 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.

37    /UNDEFINED_FAT

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

    Parameter     Description

    record-       Specifies the format for all records in a file:
    format        FIXED, VARIABLE, STREAM, STREAM_LF, STREAM_CR, LSB_
                  VARIABLE, or MSB_VARIABLE. For a description of
                  these record formats, see the discussion of the RMS
                  field FAB$B_RFM in the OpenVMS Record Management
                  Services Reference Manual.

    record-       Specifies the attributes for all records in a file:
    attributes    NONE, CR, FTN, PRN, NOBKS. Applies only to non-
                  STREAM record formats. For a description of these
                  record attributes, see 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, see 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:

                   { FIXED:record-attributes[, . . . ]:record-size}
                   { VARIABLE:record-attributes[, . . . ]         }
                   { STREAM:record-size                           }
    record formats {                                              }
                   { STREAM_LF:record-size                        }
                   { STREAM_CR:record-size                        }
                   { LSB_VARIABLE:record-attributes[, . . . ]     }
                   {                                              }
                      { NONE - None           }
                      { CR - Carriage_return  }
    record_attributes { FTN - Fortran         }
                      { PRN - Print           }
                      {                       }
                      { NOBKS - No-Block-Span }

    record_size { 1 to 32767 }

    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

38    /UNLOAD

       /UNLOAD (default)
       /NOUNLOAD

    Controls whether or not the disk or magnetic tape volume or
    volumes specified in the MOUNT command are unloaded when they
    are dismounted.

    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

39    /WINDOWS

       /WINDOWS=n

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

    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

40    /WRITE

       /WRITE (default)
       /NOWRITE

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

    For host-based volume shadowing devices, there are other
    considerations. See the VSI Volume Shadowing for OpenVMS manual
    for more information.

    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
Close Help