OpenVMS System Management Utilities Reference Manual

Document revision date: 19 July 1999

OpenVMS System Management Utilities Reference Manual

Contents

Index

/SUBSYSTEM

Enables protected subsystems.

Format

/SUBSYSTEM

/NOSUBSYSTEM

Description

Enables the processing of subsystem ACEs. Requires the SECURITY privilege. By default, the disk from which you boot has /SUBSYSTEM enabled but other disks do not. For further details on subsystems, refer to the OpenVMS Guide to System Security.

Example


$ MOUNT/NOMESSAGE/SUBSYSTEM DUA1: SLIP SACH

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

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

Format

/SYSTEM

Description

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

#1
$ MOUNT/NOMESSAGE/SYSTEM DUA1: SLIP SACH

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

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

This command creates the volume set named MASTER_PAY consisting of the initialized volumes labeled PAYVOL1, PAYVOL2, and PAYVOL3. These volumes are mounted physically on the devices named DB1, DB2, and DB3, respectively. The volume PAYVOL1 is the root volume of the set.
The volumes are mounted as system volumes to make them available to all users.

/UCS_SEQUENCE

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

Format

/UCS_SEQUENCE=escape_sequence

Parameter

escape_sequence
A character sequence defined by the vendor who mastered the CD-ROM and is unique to the vendor's character set conversion tables.

Description

Use the /UCS_SEQUENCE qualifier when mounting an ISO 9660 CD-ROM that contains non-ASCII character sets on OpenVMS.
An ISO 9660 volume may contain an SVD that specifies a graphic character set. This graphic character, when selected at mount time, is used as default character set when displaying a volume's directories and file names.
The /UCS_SEQUENCE qualifer defines the escape sequence to select the coded graphic character set.
All ISO 9660 volumes contain a Primary Volume Descriptor (PVD) that uses ASCII (ISO 646-IRV) as the character set. Both ISO 9660 and OpenVMS filenaming conventions use the same subset of ASCII characters when displaying a volume's directories and file names.

/UNDEFINED_FAT

Establishes default file attributes to be used for records on ISO 9660 media for which no record format has been specified.

Format

/UNDEFINED_FAT=record-format:[record-attributes:][record-size]

Parameters

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

Description

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:
record formats

FIXED:record-attributes[,...]:record-size
VARIABLE:record-attributes[,...]
STREAM:record-size
STREAM_LF:record-size
STREAM_CR:record-size
LSB_VARIABLE:record-attributes[,...]

record_attributes

NONE - None
CR - Carriage_return
FTN - Fortran
PRN - Print
NOBKS - No-Block-Span

record_size

1 to 32767

Example


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

In this example, the volume labeled OFFENS is mounted on DBA1 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.

/UNLOAD

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

Format

/UNLOAD

/NOUNLOAD

Example


$ MOUNT/NOUNLOAD DBA1: OFFENS STRAT

In this example, the volume labeled OFFENS is mounted on DBA1 with the /NOUNLOAD qualifier so that it can be dismounted without being physically unloaded. MOUNT also assigns the logical name STRAT.

/WINDOWS

Specifies the number of mapping pointers to be allocated for file windows.

Format

/WINDOWS= n

Parameter

n
Specifies a value from 7 to 80 that overrides the default value specified when the volume was initialized.

Description

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


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

This command makes the volume labeled GONWITH on DBA2 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.

/WRITE

Controls whether the volume can be written.

Format

/WRITE

/NOWRITE

Description

By default, a volume is considered read/write when it is mounted. You can specify /NOWRITE to provide read-only access to protect files. This is equivalent to write-locking the device.

Example


$ MOUNT/CLUSTER/NOWRITE NODE$DBA1: BOOKS

This command mounts a volume labeled BOOKS on NODE$DBA1 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.

16.4 MOUNT Examples

The following examples describe how to use the Mount utility with and without operator assistance.

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

#1
$ MOUNT MTA0: MATH06 STAT_TAPE %MOUNT-I-MOUNTED, MATH06 mounted on _MTA0: $ COPY ST061178.DAT STAT_TAPE:

This MOUNT command requests the magnetic tape whose volume label is MATH06 to be mounted on the device MTA0 and assigns the logical name STAT_TAPE to the volume.
Subsequently, the COPY command copies the disk file ST061178.DAT to the magnetic tape.

#2
$ ALLOCATE DM: %DCL-I-ALLOC, _DMB2: allocated $ MOUNT DMB2: TEST_FILES %MOUNT-I-MOUNTED, TEST_FILES mounted on _DMB2:

This ALLOCATE command requests an available RK06/RK07 device. After the response from the ALLOCATE command, the physical volume can be placed on the allocated device. Then, the MOUNT command mounts the volume.

#3
$ MOUNT DM: TEST_FILES %MOUNT-I-OPRQST, Please mount volume TEST_FILES in device _DMB2: %MOUNT-I-MOUNTED, TEST_FILES mounted on _DMB2:

This example achieves the same result as the series of commands in the preceding example. The MOUNT command requests an available RK06/RK07 device for the volume labeled TEST_FILES. After the volume is physically mounted in the device named in the response from MOUNT, the system completes the operation. Note that the device is automatically allocated by MOUNT.

#4
$ MOUNT DYA1: TESTSYS %MOUNT-I-OPRQST, Please mount volume TESTSYS in device DYA1: `[Ctrl/Y]` $ EXIT %MOUNT-I-OPRQSTCAN, operator request canceled

This MOUNT command requests the operator to mount the volume TESTSYS on the device DYA1. In this example, the user cancels the mount by pressing Ctrl/Y. Notice that the image must exit before the mount request is actually canceled. Here, the EXIT command causes the image to exit. However, any command that is not performed within the command interpreter causes the current image to exit.

#5
$ MOUNT DYA1: TESTSYS %MOUNT-I-OPRQST, Device _DYA1: is not available for mounting. %MOUNT-I-OPRQSTCAN, operator request canceled %MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1: %MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1: %MOUNT-I-OPRQSTDON, operator request canceled - mount completed successfully

$ MOUNT DYA1:  TESTSYS
%MOUNT-I-OPRQST, Device _DYA1: is not available for mounting.
%MOUNT-I-OPRQSTCAN, operator request canceled
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
%MOUNT-I-MOUNTED, TESTSYS    mounted on _DYA1:
%MOUNT-I-OPRQSTDON, operator request canceled - mount
completed successfully

This MOUNT command requests the operator to mount the volume TESTSYS on the device DYA1. Because DYA1 is allocated to another user, the device cannot be mounted. In this case, the user can wait for the device to become available, redirect the mount to another device, or abort the mount. Here, the user remains in operator-assisted mount waiting for the process that is using the device to deallocate it. At this point, because the device is available but no volume is mounted, the original mount request is canceled, and a new request to mount TESTSYS is issued. Finally, the operator places the volume in the drive and lets MOUNT retry the mount. When the mount completes, the request is canceled.

#6
$ MOUNT DYA1: TESTSYS/COMMENT="Is there an operator around?" %MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1: Is there an operator around? %MOUNT-I-NOOPR, no operator available to service request . . . %MOUNT-I-MOUNTED, TESTSYS mounted on _DYA1: %MOUNT-I-OPRQSTDON, operator request canceled - mount completed successfully

$ MOUNT DYA1:  TESTSYS/COMMENT="Is there an operator around?"
%MOUNT-I-OPRQST, Please mount volume TESTSYS in device _DYA1:
Is there an operator around?
%MOUNT-I-NOOPR, no operator available to service request
. 
. 
. 
%MOUNT-I-MOUNTED, TESTSYS    mounted on _DYA1:
%MOUNT-I-OPRQSTDON, operator request canceled - mount
completed successfully

This MOUNT command requests the operator to mount the volume TESTSYS on the device DYA1. In this example, no operator is available to service the request. At this point, the user can abort the mount by pressing Ctrl/Y, or wait for an operator. Here, the user waited, and an operator eventually became available to service the request.

#7
$ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA1 USER %MOUNT-I-CDROM_ISO, USER:VMS_ONLINE_DOCUMENTATION (1 of 4) , mounted on _$1$DKA1: (CDROM) $ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA2 PROGRAMMING_1 %MOUNT-I-CDROM_ISO, PROGRAMMING_1:VMS_ONLINE_DOCUMENTATION (2 of 4) , mounted on _$1$DKA2: (CDROM) $ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA3 PROGRAMMING_2 %MOUNT-I-CDROM_ISO, PROGRAMMING_2:VMS_ONLINE_DOCUMENTATION (3 of 4) , mounted on _$1$DKA3: (CDROM) MOUNT/SYSTEM/MEDIA=CDROM $1$DKA4 MANAGEMENT %MOUNT-I-CDROM_ISO, MANAGEMENT:VMS_ONLINE_DOCUMENTATION (4 of 4) , mounted on _$1$DKA4: (CDROM)

$ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA1 USER
%MOUNT-I-CDROM_ISO, USER:VMS_ONLINE_DOCUMENTATION (1 of 4) , 
mounted on _$1$DKA1: (CDROM)
$ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA2 PROGRAMMING_1
%MOUNT-I-CDROM_ISO, PROGRAMMING_1:VMS_ONLINE_DOCUMENTATION (2 of 4) , 
mounted on  _$1$DKA2: (CDROM)
$  MOUNT/SYSTEM/MEDIA=CDROM $1$DKA3 PROGRAMMING_2
%MOUNT-I-CDROM_ISO, PROGRAMMING_2:VMS_ONLINE_DOCUMENTATION (3 of 4) , 
mounted on  _$1$DKA3: (CDROM)
MOUNT/SYSTEM/MEDIA=CDROM $1$DKA4 MANAGEMENT
%MOUNT-I-CDROM_ISO, MANAGEMENT:VMS_ONLINE_DOCUMENTATION (4 of 4) , 
mounted on  _$1$DKA4: (CDROM)

These commands mount each member of a four-member ISO 9660 volume set whose volume-set name is VMS_ONLINE_DOCUMENTATION.

#8
$ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA1,$1$DKA2,$1$DKA3,$1$DKA4 USER,PROGRAMMING_1,PROGRAMMING_2,MANAGEMENT %MOUNT-I-CDROM_ISO, USER:VMS_ONLINE_DOCUMENTATION (1 of 4) , mounted on _$1$DKA1: (CDROM) %MOUNT-I-CDROM_ISO, PROGRAMMING_1:VMS_ONLINE_DOCUMENTATION (2 of 4) , mounted on _$1$DKA2: (CDROM) %MOUNT-I-CDROM_ISO, PROGRAMMING_2:VMS_ONLINE_DOCUMENTATION (3 of 4) , mounted on _$1$DKA3: (CDROM) %MOUNT-I-CDROM_ISO, MANAGEMENT:VMS_ONLINE_DOCUMENTATION (4 of 4) , mounted on _$1$DKA4: (CDROM)

$ MOUNT/SYSTEM/MEDIA=CDROM $1$DKA1,$1$DKA2,$1$DKA3,$1$DKA4 
USER,PROGRAMMING_1,PROGRAMMING_2,MANAGEMENT
%MOUNT-I-CDROM_ISO, USER:VMS_ONLINE_DOCUMENTATION (1 of 4) , mounted on 
_$1$DKA1: (CDROM)
%MOUNT-I-CDROM_ISO, PROGRAMMING_1:VMS_ONLINE_DOCUMENTATION (2 of 4) , 
mounted on  _$1$DKA2: (CDROM)
%MOUNT-I-CDROM_ISO, PROGRAMMING_2:VMS_ONLINE_DOCUMENTATION (3 of 4) , 
mounted on  _$1$DKA3: (CDROM)
%MOUNT-I-CDROM_ISO, MANAGEMENT:VMS_ONLINE_DOCUMENTATION (4 of 4) , 
mounted on  _$1$DKA4: (CDROM)

This command mounts four members of an ISO 9660 volume set whose volume set name is VMS_ONLINE_DOCUMENTATION.

#9
$ MOUNT/SYSTEM/SUBSYSTEM $8$DKA300: ATLANTIS_WORK1 %MOUNT-I-MOUNTED, ATLANTIS_WORK1 mounted on _$8$DKA300: (ATLANTIS) $ SHOW DEVICE/FULL $8$DKA300: Disk $8$DKA300: (ATLANTIS), device type RZ24, is online, mounted, file-oriented device, shareable, served to cluster via MSCP Server, error logging is enabled. Error count 0 Operations completed 385 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 1 Default buffer size 512 Total blocks 409792 Sectors per track 38 Total cylinders 1348 Tracks per cylinder 8 Allocation class 8 Volume label "ATLANTIS_WORK1" Relative volume number 0 Cluster size 3 Transaction count 1 Free blocks 396798 Maximum files allowed 51224 Extend quantity 5 Mount count 1 Mount status System Cache name "_$8$DKA700:XQPCACHE" Extent cache size 64 Maximum blocks in extent cache 39679 File ID cache size 64 Blocks currently in extent cache 0 Quota cache size 50 Maximum buffers in FCP cache 295 Volume owner UIC [VMS,PLATO] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD Volume status: ODS-2, subject to mount verification, protected subsystems enabled, file high-water marking, write-through caching enabled.

$ MOUNT/SYSTEM/SUBSYSTEM $8$DKA300: ATLANTIS_WORK1
%MOUNT-I-MOUNTED, ATLANTIS_WORK1 mounted on _$8$DKA300: (ATLANTIS)
$ SHOW DEVICE/FULL $8$DKA300:
 
 
 
 
Disk $8$DKA300: (ATLANTIS), device type RZ24, is online, mounted, 
 file-oriented device, shareable, served to cluster via MSCP Server, 
 error logging is enabled. 
 
Error count                   0   Operations completed                385 
 Owner process                ""   Owner UIC                      [SYSTEM] 
 Owner process ID       00000000   Dev Prot            S:RWPL,O:RWPL,G:R,W 
 Reference count               1   Default buffer size                 512 
 Total blocks             409792   Sectors per track                    38 
 Total cylinders            1348   Tracks per cylinder                   8 
 Allocation class              8 
 
 Volume label   "ATLANTIS_WORK1"   Relative volume number                0 
 Cluster size                  3   Transaction count                     1 
 Free blocks              396798   Maximum files allowed             51224 
 Extend quantity               5   Mount count                           1 
 Mount status             System   Cache name        "_$8$DKA700:XQPCACHE" 
 Extent cache size            64   Maximum blocks in extent cache    39679 
 File ID cache size           64   Blocks currently in extent cache      0 
 Quota cache size             50   Maximum buffers in FCP cache        295 
 Volume owner UIC    [VMS,PLATO]   Vol Prot    S:RWCD,O:RWCD,G:RWCD,W:RWCD 
 
 
Volume status: ODS-2, subject to mount verification, protected 
    subsystems enabled, file high-water marking, write-through caching enabled.

The MOUNT command mounts a volume labeled ATLANTIS_WORK1, which is available systemwide. Subsystems on the volume are accessible.

#10
$ MOUNT DSA0: /SHADOW=($200$DKA200:,$200$DKA300:,$200$DKA400:) X5OZCOPY %MOUNT-I-MOUNTED, X5OZCOPY mounted on _DSA0: %MOUNT-I-SHDWMEMSUCC, _$200$DKA200: (VIPER1) is now a valid member of the shadow set %MOUNT-I-SHDWMEMSUCC, _$200$DKA300: (VIPER1) is now a valid member of the shadow set %MOUNT-I-SHDWMEMSUCC, _$200$DKA400: (VIPER1) is now a valid member of the shadow set $ DISMOUNT DSA0: $ MOUNT/INCLUDE DSA0: /SHADOW=$200$DKA200: X5OXCOPY %MOUNT-I-MOUNTED, X5OZCOPY mounted on _DSA0: %MOUNT-I-SHDWMEMSUCC, _$200$DKA200: (VIPER1) is now a valid member of the shadow set %MOUNT-I-AUTOMEMSUCC, _$200$DKA300: (VIPER1) automatically added to the shadow set %MOUNT-I-AUTOMEMSUCC, _$200$DKA400: (VIPER1) automatically added to the shadow set

#10

$ MOUNT DSA0: /SHADOW=($200$DKA200:,$200$DKA300:,$200$DKA400:) X5OZCOPY %MOUNT-I-MOUNTED, X5OZCOPY mounted on _DSA0: %MOUNT-I-SHDWMEMSUCC, _$200$DKA200: (VIPER1) is now a valid member of the shadow set %MOUNT-I-SHDWMEMSUCC, _$200$DKA300: (VIPER1) is now a valid member of the shadow set %MOUNT-I-SHDWMEMSUCC, _$200$DKA400: (VIPER1) is now a valid member of the shadow set $ DISMOUNT DSA0: $ MOUNT/INCLUDE DSA0: /SHADOW=$200$DKA200: X5OXCOPY %MOUNT-I-MOUNTED, X5OZCOPY mounted on _DSA0: %MOUNT-I-SHDWMEMSUCC, _$200$DKA200: (VIPER1) is now a valid member of the shadow set %MOUNT-I-AUTOMEMSUCC, _$200$DKA300: (VIPER1) automatically added to the shadow set %MOUNT-I-AUTOMEMSUCC, _$200$DKA400: (VIPER1) automatically added to the shadow set

In this example, an existing shadow set is mounted in two ways. The first MOUNT command specifies each member of the shadow set with the /SHADOW qualifier. Then, after DSA0: is dismounted, the second MOUNT command uses the /INCLUDE qualifier to automatically mount all members of the shadow set.

Contents

Index

privacy and legal statement

6048PRO_050.HTML