Software development, photography, jokes, ....

Sites by me

 
tas-logoTransportation Administration System
snoezelkussen-logo-kleinstSnoezelkussens voor verstandelijk gehandicapten
ikzoekeenbegeleider-logoBegeleiders voor gehandicapten
Laat uw hond het jaarlijkse vuurwerk overwinnen
logo 50x50Hey Vos! Je eigen naam@vos.net emailadres?
Kunst in huis? Nicole Karrèr maakt echt bijzonder mooie dingen
nettylogo2Kunst in huis? Netty Franssen maakt ook bijzonder mooie dingen
Salarisadministratie en belastingadvies bij De Zaak Loont
Zutphense Bomenstichting

Hosting Favorites

 
ANU Internet Services
XelMedia .internet Services
register.com

Blogroll

 
Bomenstichting
LassoSoft
MacFreak
Quality that computes
The Economy of Motion
Wheel 2.0
IntrAktv



Website Hosting bij Xel Media

Marc's Place

1 MOUNT

The Mount utility (MOUNT) allows you to make a disk or magnetic tape volume available for processing. Format MOUNT device-name[:][,...] [volume-label[,...]] [logical-name[:]] 2 Parameters device-name[:][,...] Specifies the physical device name or logical name of the device on which the volume is to be mounted. On a system where volumes are not connected to hierarchical storage controllers, use the following format: ddcu: The dd describes the device type of the physical devices used. For example, an RA60 disk drive is device type DJ, and an RA80 or RA81 disk drive is device type DU. The c identifies the controller, and the u identifies the unit number of the device. On a system with HSCs, use one of the following formats: node$ddcu: allocation-class$ddcu: If your devices are dual ported to HSCs, use the allocation- class format. For example, $125$DUA23 represents an RA80 or RA81 disk with unit number 23. The disk's allocation class is $125$. The c part of the format is always A for HSC disks. TROLL$DJA12 represents an RA60 disk with unit number 12. The device is connected to an HSC named TROLL. See VMScluster Systems for OpenVMS for more information about naming conventions. Device names can be generic so that if no controller or unit number is specified, the system attempts to mount the first available device that satisfies those specified components of the device names. If no volume is physically mounted on the specified device, MOUNT displays a message requesting that you place the volume in the device; after you place the volume in the named drive, MOUNT then completes the operation. If you specify more than one device name for a disk or magnetic tape volume set, separate the device names with either commas or plus signs. For a magnetic tape volume set, you can specify more volume labels than device names or more device names than volumes. volume-label[,...] Specifies the label on the volume. The number of characters allowed in a label depends on the type of device, as follows: Number of Characters Device Type in Label Magnetic tape 0-6 Files-11 disk 1-12 ISO 9660 disk 1-32 OpenVMS requires disk volume labels to be unique in the first 12 characters within a given domain. For example, disks mounted by different members of the same group using the /GROUP qualifier must be unique. However, disks mounted in different domains, such as one mounted using the /GROUP qualifier and one mounted privately, can use the same volume label. 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 volume label using the qualifier /OVERRIDE=IDENTIFICATION. If you choose this option, then Mount verification is disabled for the device. In addition, if a volume is part of a volume set and the first 12 characters of the volume-set name are the same as the first 12 characters of the 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). If you specify more than one volume label, separate the labels with either commas or plus signs. The volumes must be in the same volume set and the labels must be specified in ascending order according to relative volume number. When you mount a magnetic tape volume set, the number of volume labels need not equal the number of device names specified. When a magnetic tape reaches the end-of-tape (EOT) mark, the system requests the operator to mount the next volume on one of the devices. The user is not informed of this request; only the operator is informed. When you mount a disk volume set, each volume label specified in the list must correspond to a device name in the same position in the device name list. The volume-label parameter is not required when you mount a volume with the /FOREIGN or /NOLABEL qualifier or when you specify /OVERRIDE=IDENTIFICATION. To specify a logical name when you enter either of these qualifiers, type any alphanumeric characters in the volume-label parameter position. logical-name[:] Defines a 1- to 255-alphanumeric character string logical name to be associated with the volume. If you do not specify a logical name, the MOUNT command assigns the default logical name DISK$volume-label to individual disk drives; it assigns the default logical name DISK$volume-set-name to the device on which the root volume of a disk volume set is mounted. Note that if you specify a logical name in the mount request that is different from DISK$volume-label or DISK$volume- set-name, then two logical names are associated with the device. If you do not specify a logical name for a magnetic tape drive, the MOUNT command assigns only one logical name, TAPE$volume- label, to the first magnetic tape device in the list. No default logical volume-set name is assigned in this case. The MOUNT command places the name in the process logical name table, unless you specify /GROUP or /SYSTEM. In the latter cases, it places the logical names in the group or system logical name table. If you specify the /CLUSTER qualifier, the logical name is established on each node in the cluster. NOTE Avoid assigning a logical name that matches the file name of an executable image in SYS$SYSTEM. Such an assignment prohibits you from invoking that image. Do not use the logical name assigned to a volume as a distributed file system (DFS) access point. If you attempt to add a DFS access point using the same name as the logical name, DFS fails as in the following example: $ SHOW LOG DISK$* (LNM$SYSTEM_TABLE) "DISK$TIVOLI_SYS" = "TIVOLI$DUA0:" $ MCR DFS$CONTROL DFS> ADD ACCESS DISK$TIVOLI_SYS TIVOLI$DUA0:[000000] %DNS-W-NONSNAME, Unknown namespace name specified If the logical name of a volume is in a process-private table, then the name is not deleted when the volume is dismounted. 2 Usage_Summary To invoke MOUNT, enter the DCL command MOUNT, followed by the device name, volume label, and logical name. You must include a device name and a volume label (unless you specify /OVERRIDE=IDENTIFICATION or use the /FOREIGN or /NOLABEL qualifier); the logical name is optional. MOUNT returns you to the DCL level after it either successfully completes the operation or fails, generating an error message. If you press Ctrl/Y or Ctrl/C, MOUNT aborts the operation and returns you to the DCL prompt. You can direct output from MOUNT operations with the /COMMENT and /MESSAGE qualifiers. When the mount operation requires operator assistance, use /COMMENT to specify additional information to be included with the operator request. The /COMMENT text string is sent to the operator log file and to SYS$OUTPUT. The string must contain no more than 78 characters. Use the /MESSAGE qualifier (this is the default) to send mount request messages to your current SYS$OUTPUT device. If you specify /NOMESSAGE during an operator-assisted mount, messages are not sent to SYS$OUTPUT; the operator sees them, however, if an operator terminal is enabled to receive messages. Many MOUNT qualifiers require special privileges. Some qualifiers require different privileges according to which qualifier keyword you specify. See the individual qualifiers for details. MOUNT Qualifiers That Require Special Privileges lists MOUNT qualifiers that require special privileges. Table 1 MOUNT Qualifiers That Require Special Privileges Qualifier Keywords Required Privilege /ACCESSED OPER /CACHE= [NO]EXTENT[=n] OPER [NO]FILE_ID[=n] OPER [NO]QUOTA[=n] OPER /FOREIGN VOLPRO /GROUP GRPNAM /MULTI_VOLUME VOLPRO /OVERRIDE= ACCESSIBILITY VOLPRO EXPIRATION VOLPRO LOCK VOLPRO SHADOW VOLPRO /OWNER_UIC= uic VOLPRO /PROCESSOR= UNIQUE OPER SAME:device OPER file-spec OPER and CMKRNL /PROTECTION= code VOLPRO /QUOTA VOLPRO /SYSTEM SYSNAM /WINDOWS= n OPER 2 /ACCESSED Specifies, for ODS1 disk volumes, the approximate number of directories that will be in use concurrently on the volume. Format /ACCESSED=n 3 Parameter n Specifies the approximate number of directories that will be in use concurrently on an ODS1 volume. (The /ACCESSED qualifier is meaningless for ODS2 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. 3 Example $ MOUNT/ACCESSED=150 DBA1 WORK This command requests the volume labeled WORK to be mounted on DBA1, specifying 150 as the number of active directories on the volume. 2 /ASSIST Directs the mount operation to allow operator or user intervention if the mount request fails. Format /ASSIST /NOASSIST 3 Example $ MOUNT/NOASSIST DMA0: DOC WORK %MOUNT-I-MOUNTED, DOC mounted on _NODE$DMA0: This command mounts an RK07 volume labeled DOC and assigns the logical name WORK. The /NOASSIST qualifier signals MOUNT that no operator intervention is necessary. 2 /AUTOMATIC Determines whether MOUNT enables or disables automatic volume switching and labeling for magnetic tape or ISO 9660 CD-ROM. Format /AUTOMATIC /NOAUTOMATIC 3 Example $ MOUNT/NOAUTOMATIC MTA0: ABCD,EFGH This command instructs MOUNT not to generate its own label for the second volume, but to use the ones supplied with the MOUNT command. If the second volume is not already labeled, then the operator must use REPLY/INIT and supply the second label. 2 /BIND Creates a volume set of one or more disk volumes or adds one or more volumes to an existing volume set. Format /BIND=volume-set-name 3 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). 3 Examples 1.$ MOUNT/BIND=LIBRARY DMA0:,DMA1:,DMA2: BOOK1,BOOK2,BOOK3 This 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. 2.$ MOUNT/BIND=TEST3013 DSA3011/SHADOW=($1$DUA402:,$1$DUA403:), DSA3012/SHADOW=($1$DUA404:,$1$DUA405:) TEST3011,TEST3012 TEST3013 This command creates a volume set with the logical name TEST3013. The volume set TEST3013 is shadowed, and each element of the shadowset (TEST3011 and TEST3012) is itself a volume set. 2 /BLOCKSIZE Specifies the default block size for magnetic tape volumes. Format /BLOCKSIZE=n 3 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. 3 Example $ MOUNT/FOREIGN/BLOCKSIZE=1000 MTA1: In this example, the /BLOCKSIZE qualifier specifies a block size of 1000 bytes; the default for a magnetic tape mounted with the /FOREIGN qualifier is 512. 2 /CACHE 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). Format /CACHE=(keyword[,...]) /NOCACHE 3 Keywords EXTENT[=n] NOEXTENT Enables or disables extent caching. To enable extent 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] NOFILE_ID Enables or disables file identification caching. 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] NOQUOTA Enables or disables quota caching. To enable quota 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 writeback caching, which writes only the file headers of files open for write when the files are closed. Thus, if you specify the WRITETHROUGH keyword, file headers are written to the disk on every file header operation. 3 Examples 1.$ MOUNT/CACHE=(EXTENT=60,FILE_ID=60,QUOTA=20,WRITETHROUGH) - _$ DMA0: FILES WORK %MOUNT-I-MOUNTED, FILES mounted on _NODE$DMA0: This command mounts an RK07 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. 2.$ MOUNT/CACHE=TAPE_DATA MUA0: TAPE %MOUNT-I-MOUNTED, TAPE mounted on _NODE$MUA0: This command mounts the volume TAPE on device MUA0 and instructs MOUNT to enable the tape controller's write cache for MUA0. 2 /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 VMScluster (that is, the volume is mounted clusterwide). Format /CLUSTER 3 Example $ 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 siz 64 Blocks currently in extent cache 0 Quota cache size 25 Maximum buffers in FCP cache 349 Volume status: subject to mount verification, file high- water marking, write-through caching enabled. Volume is also mounted on DOC, HAPPY, GRUMPY, SLEEPY, SNEEZY, BASHFUL. This 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. 2 /COMMENT Specifies additional information to be included with the operator request when the mount operation requires operator assistance. Format /COMMENT=string 3 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. 3 Examples 1.$ 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 This 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. 2.$ 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 This 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. 3.$ 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: This 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. 2 /CONFIRM Causes MOUNT to pause and request confirmation before performing a copy operation on the specified disk device. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS. Format /CONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...]) /NOCONFIRM virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...]) 3 Description 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. 3 Example $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 This command 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. 2 /COPY Enables or disables copy operations on physical devices specified when you mount a shadow set. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS. Format /COPY virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...]) /NOCOPY virtual-unit-name[:] /SHADOW=(physical-dev-name[:][,...]) 3 Description 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 default qualifier is /COPY. 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. 3 Example $ 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 This command 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. 2 /DATA_CHECK Overrides the read-check or write-check option (or both) specified for a volume when it was initialized. Format /DATA_CHECK[=(keyword[,...])] 3 Keywords READ Performs checks following all read operations. WRITE Performs checks following all write operations. 3 Example $ MOUNT/DATA_CHECK=READ CLEMENS$DBA2: SAM BOOK This command mounts a volume labeled SAM on CLEMENS$DBA2 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. 2 /DENSITY Specifies the density (in bits/in) at which a foreign or unlabeled magnetic tape is to be written. Format [/FOREIGN][/NOLABEL]/DENSITY=n 3 Parameter n Specifies a density of 800, 1600, or 6250 bits/in, if supported by the magnetic tape drive. If you do not specify a density for a magnetic tape that was previously written, the density defaults to that of the first record on the volume. The /DENSITY qualifier is incompatible with the /MEDIA_ FORMAT=[NO]COMPACTION qualifier. 3 Example $ MOUNT/FOREIGN/DENSITY=1600 MFA0: TAPE This command mounts a foreign magnetic tape on drive MFA0 and assigns the logical name TAPE. The /DENSITY qualifier specifies that the magnetic tape is to be written at a density of 1600 bits/in. 2 /EXTENSION 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. Format /EXTENSION=n 3 Parameter n Specifies a value from 0 to 65,535 to override the value specified when the volume was initialized. 3 Example $ MOUNT/EXTENSION=64 DBA0: DOC WORK This command mounts a volume labeled DOC on DBA0, assigns the logical name WORK, and specifies a default block extent of 64 for the files on WORK. 2 /FOREIGN Indicates that the volume is not in the standard format used by the OpenVMS operating system. Format /FOREIGN 3 Examples 1.$ MOUNT/FOREIGN MTA1: ABCD TAPE This command mounts a foreign magnetic tape on drive MTA1. 2.$ MOUNT/FOREIGN DMA2: SAVEDISK This command mounts an RK07 device as a foreign volume on DMA2 and assigns the logical name SAVEDISK. As a volume that is not file structured, SAVEDISK can be used for sequential-disk BACKUP save operations. 2 /GROUP Makes the volume available to other users with the same group number in their UICs as the user entering the MOUNT command. Format /GROUP 3 Examples 1.$ MOUNT/GROUP DB1:, DB2:, DB3: PAYVOL1,PAYVOL2,PAYVOL3 PAY This 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. 2.$ MOUNT/GROUP/BIND=MASTER_PAY DB4: PAYVOL4 This 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. 2 /HDR3 Controls whether ANSI standard header label 3 is written on a magnetic tape volume. Format /HDR3 /NOHDR3 3 Example $ INITIALIZE MTA0: ABCD $ MOUNT/NOHDR3 MTA0: ABCD 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. 2 /INCLUDE Automatically reconstructs a former shadow set to the way it was before the shadow set was dissolved. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS. Format /INCLUDE virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...]) /NOINCLUDE virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...]) 3 Description 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. 3 Example $ 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 This 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. 2 /INITIALIZE=CONTINUATION Specifies that any volume added to the magnetic tape volume set is initialized before you can write to the volume. Format /INITIALIZE=CONTINUATION 3 Example $ MOUNT/INITIALIZE=CONTINUATION MTA0: ABCD 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). 2 /LABEL 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. Format /LABEL /NOLABEL 3 Example $ MOUNT/LABEL MFA1: TAPE This command mounts an ANSI-labeled magnetic tape on MFA1 and assigns the logical name TAPE. 2 /MEDIA_FORMAT 3 CDROM Mounts a volume assuming the media to be ISO 9660 (or High Sierra) formatted. Format /MEDIA_FORMAT=CDROM 3 COMPACTION Enables and controls data compaction and data record blocking on tape drives that support data compaction. Format /MEDIA_FORMAT=[NO]COMPACTION 4 Examples 1.$ MOUNT/FOREIGN/MEDIA_FORMAT=COMPACTION MUA0: BOOKS This command performs a foreign mount of a tape with data compaction and record blocking enabled and assigns the logical name BOOKS to the tape. 2.$ INIT/MEDIA_FORMAT=NOCOMPACTION MUA0: BOOKS $ MOUNT/MEDIA_FORMAT=COMPACTION MUA0: BOOKS This 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. 2 /MESSAGE Causes mount request messages to be sent to your current SYS$OUTPUT device. Format /MESSAGE /NOMESSAGE 3 Example $ MOUNT/NOMESSAGE DLA0: SLIP DISC 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. 2 /MOUNT_VERIFICATION Specifies that the device is a candidate for mount verification. Format /MOUNT_VERIFICATION /NOMOUNT_VERIFICATION 3 Example $ MOUNT/CACHE=(NOEXTENT,NOFILE_ID,NOQUOTA,WRITETHROUGH) - _$ /NOMOUNT_VERIFICATION DMA0: FILES WORK %MOUNT-I-MOUNTED, FILES mounted on _NODE$DMA0: This command mounts an RK06 or RK07 device labeled FILES and assigns the logical name WORK. The /CACHE qualifier disables extent caching, file identification caching, quota caching, and writeback caching; the /NOMOUNT_VERIFICATION qualifier disables mount verification. 2 /MULTI_VOLUME 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 VMS 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. Format /MULTI_VOLUME /NOMULTI_VOLUME 3 Example $ MOUNT/FOREIGN/MULTI_VOLUME MUA0: This 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. 2 /OVERRIDE Inhibits one or more protection checks that the MOUNT command performs. Format /OVERRIDE=(keyword[,...]) 3 Keywords If you specify more than one keyword, separate them with commas and enclose the list in parentheses. 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. 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 (on VAX systems) for an ISO 9660 volume whose label is not unique in the first 12 characters. Only the volume identifier field is overridden. Volume protection, if any, is preserved. The volume must be mounted /NOSHARE (either explicitly or by default). The /OVERRIDE=IDENTIFICATION qualifier is incompatible with the /GROUP and /SYSTEM qualifiers. LIMITED_SEARCH Allows the Mount utility to search an entire device for a home block, if a home block is not found at the expected location. By default, the search for a home block is limited to avoid excessive search times if no valid home block is present. LOCK Directs MOUNT not to write-lock the volume as a consequence of certain errors encountered while mounting it. Use this keyword when you are mounting a damaged volume to be repaired using the ANALYZE/DISK_STRUCTURE command. You must have VOLPRO privilege or own the volume to use the LOCK keyword. NO_FORCED_ERROR Directs the Mount utility to proceed with shadowing, even though the device or controller does not support forced error handling. Using unsupported SCSI disks can cause members to be removed from a shadow set if certain error conditions arise that cannot be corrected, because some SCSI disks do not implement READL and WRITEL commands that support disk bad block repair. OWNER_IDENTIFIER For magnetic tapes only. Overrides the processing of the owner identifier field. Use this keyword to interchange protected magnetic tapes between OpenVMS and other Digital operating systems. SECURITY Allows you to continue mounting a volume if an error is returned because the volume has an invalid SECURITY.SYS file. You must have the user privilege VOLPRO or own the volume to use this keyword. SETID For magnetic tapes only. Prevents MOUNT from checking the file- set identifier in the first file header label of the first file on a continuation volume. Use this keyword only for ANSI-labeled volumes on which the file-set identifier of the first file on a continuation volume differs from the file-set identifier of the first file of the first volume that was mounted. SHADOW_MEMBERSHIP Allows you to override the write protection of former shadow set members. Applicable only if you have the volume shadowing option. See 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. You must have VOLPRO privilege or own the volume to use the LOCK keyword. 3 Example $ MOUNT/OVERRIDE=IDENTIFICATION MFA0: This command overrides the volume identification field, thus mounting a magnetic tape on MFA0 without a label specification. 2 /OWNER_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. Format /OWNER_UIC=uic 3 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 17776. 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. 3 Example $ MOUNT/OWNER_UIC=[016,360] DRA3: WORK This command mounts a disk device labeled WORK on DRA3 and assigns an owner UIC of [016,360]. 2 /PROCESSOR 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 Level 2 disks, controls block cache allocation. Format /PROCESSOR=keyword 3 Keywords 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 Level 2 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 Level 2 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. 3 Example $ MOUNT/PROCESSOR=SAME:MTA1: MFA0: This command directs MOUNT to mount a magnetic tape on MFA0 using the same ACP process currently associated with MTA1. 2 /PROTECTION Specifies the protection code to be assigned to the volume. Format /PROTECTION=keyword 3 Keywords protection code Specifies the protection code according to the standard syntax rules for specifying user protection (that is, system/owner/group /world). If you omit a protection category, that category of user is denied all access. If you do not specify a protection code, the default is the protection that was assigned to the volume when it was initialized. XAR Enables enforcement of the extended record attribute (XAR) access controls. For more information on 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. 3 Example $ MOUNT/PROTECTION=(SYSTEM:RWE,O:RWED,G:RE,W:R) DBA1: WORKDISK This command mounts a device labeled WORKDISK on DBA1 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. 2 /QUOTA Controls whether quotas are to be enforced on the specified disk volume. Format /QUOTA /NOQUOTA 3 Example $ MOUNT/OWNER_UIC=[016,360]/NOQUOTA DRA3: WORK This command specifies that the disk volume labeled WORK on DRA3 has an owner UIC of [016,360] and no quotas enforced. 2 /REBUILD Controls whether or not MOUNT performs a rebuild operation on a disk volume. Format /REBUILD /NOREBUILD 3 Examples 1.$ MOUNT/REBUILD NODE$DBA2: WORKDISK %MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DBA2: %MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress In this example, the volume WORKDISK is mounted on NODE$DBA2. 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. 2.$ MOUNT/NOREBUILD NODE$DBA2: WORKDISK %MOUNT-I-MOUNTED, WORKDISK mounted on _NODE$DBA2: %MOUNT-I-REBLDREQD, rebuild not performed; some free space unavailable; diskquota usage stale 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. 2 /RECORDSIZE Specifies the number of characters in each record of a magnetic tape volume. Format /RECORDSIZE=n 3 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. 3 Example $ MOUNT/FOREIGN/BLOCKSIZE=512/RECORDSIZE=512 MTA0: In this example, the magnetic tape is mounted on MTA0 with a default block size and record size of 512 characters. 2 /SHADOW Binds up to three physical devices into a shadow set represented by the virtual unit named in the command. Applicable only if you have the volume shadowing option. See Volume Shadowing for OpenVMS. Format virtual-unit-name[:] /SHADOW=(physical-device-name[:][,...]) 3 Description 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[:]. 3 Examples 1.$ 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 This 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. 2.$ MOUNT/BIND=TEST3013 DSA3011/SHADOW=($1$DUA402:,$1$DUA403:), DSA3012/SHADOW=($1$DUA404:,$1$DUA405:) TEST3011,TEST3012 TEST3013 This command creates a volume set with the logical name TEST3013. The volume set TEST3013 is shadowed, and each element of the shadowset (TEST3011 and TEST3012) is itself a volume set. 2 /SHARE Specifies, for a disk volume, that the volume is shareable. Format /SHARE /NOSHARE 3 Example $ MOUNT/NOMESSAGE/SHARE DLA0: SLIP DISC This 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. 2 /SUBSYSTEM Enables protected subsystems. Format /SUBSYSTEM /NOSUBSYSTEM 3 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. 2 /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 3 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. 2 /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) 3 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. 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. 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. 2 /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] 3 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, see 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, 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. 3 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: { 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 } 3 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. 2 /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 3 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. 2 /WINDOWS Specifies the number of mapping pointers to be allocated for file windows. Format /WINDOWS=n 3 Parameter n Specifies a value from 7 to 80 that overrides the default value specified when the volume was initialized. 3 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. 2 /WRITE Controls whether the volume can be written. Format /WRITE /NOWRITE 3 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 VMScluster. The /NOWRITE qualifier makes the volume available for read-only access. 2 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 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 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) 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) 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: 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 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.

© 1997- Marc Vos (and others) Contact Me