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