Document revision date: 30 March 2001

## OpenVMS DCL Dictionary

Previous | Contents | Index

In this example, the DIRECTORY command lists the number of blocks used, the creation date, and the file protection code for the highest version number of all files named AVERAGE in the current directory.

#3
    $ DIRECTORY/FULL DISK$GRIPS_2:[VMS.TV]DEMO.EXE

    Directory DISK$GRIPS_2:[VMS.TV]

    DEMO.EXE;1                      File ID:  (36,11,0)
    Size:           390/390         Owner:    [0,0]
    Created:  12-NOV-2001 11:45:19.00
    Revised:  14-DEC-2001 15:45:19.00 (34)
    Expires:   <None specified>
    Backup:   28-NOV-2001 04:00:12.22
    Effective: <None specified>
    Recording: <None specified>
    File organization:  Sequential
    Shelved state:      Online
    Caching attribute:  Writethrough
    File attributes:    Allocation: 390, Extend: 0, Global buffer count: 0,
                        Version limit: 0, Backups disabled, Not shelvable
    Record format:      Fixed length 512 byte records
    Record attributes:  None
    RMS attributes:     None
    Journaling enabled: None
    File protection:    System:RE, Owner:RE, Group:RE, World:RE
    Access Cntrl List:  None
    Client attributes:  None

    Total of 1 file, 390/390 blocks.

> The example illustrates the DIRECTORY/FULL command.

#4
    $ DIRECTORY/VERSIONS=1/COLUMNS=1 AVERAGE.*

> The DIRECTORY command in this example lists only the highest version of each file named AVERAGE in the current default directory. The format is brief and restricted to one column. Heading and trailing lines are provided.

#5
    $ DIRECTORY BLOCK%%%

> The DIRECTORY command in this example locates all versions and types of files in the default device and directory whose names begin with the letters BLOCK and end with any three additional characters. The default output format is brief, four columns, with heading and trailing lines.

#6
    $ DIRECTORY/EXCLUDE=(AVER.DAT;*,AVER.EXE;*) [*...]AVER

> The DIRECTORY command in this example lists and totals all versions and types of files named AVER in all directories and subdirectories on the default disk, except any files named AVER.DAT and AVER.EXE.

#7
    $ DIRECTORY/SIZE=ALL FRESNO::DISK1:[TAMBA]*.COM

> The DIRECTORY command in this example lists all versions of all files with the file type COM in the directory TAMBA on node FRESNO and device DISK1. The listing includes the file size both in blocks used and in blocks allocated for each file.

#8
    $ DIRECTORY-
    _$ /MODIFIED/SINCE=14-DEC-2001:01:30/SIZE=ALL/OWNER-
    _$ /PROTECTION/OUTPUT=UPDATE/PRINTER [A*]

> The DIRECTORY command in this example locates all files that have been modified since 1:30 a.m. on December 14, 2001, and that reside on the default disk in all directories whose names begin with the letter A. It formats the output to include all versions, the size used and size allocated, the date last modified, the owner, and the protection codes. The output is directed to a file named UPDATE.LIS, which is queued automatically to the default printer queue and then is deleted.

#9
    $ DIRECTORY/SHELVED_STATE
    Directory MYDISK:[THOMPSON]
    MYFILE.TXT;2            Online
    NOT_SHELVED.TXT;1       Online
    SHELVED.TXT             Shelved
    Total of 3 files.

> The DIRECTORY command in this example lists all the files in a directory and shows whether a file is shelved, preshelved, online, or remote.

## DISABLE AUTOSTART

> Disables the autostart feature on a node for all autostart queues managed by the specific queue manager. By default, this command uses the /QUEUES qualifier.

> Requires OPER (operator) privileges.

> For more information on autostart queues, refer to the chapter on batch and print queues in the OpenVMS System Manager's Manual.

### Format

> DISABLE AUTOSTART[/QUEUES]

### Parameters

> None.

### Description

> The DISABLE AUTOSTART/QUEUES command notifies the queue manager to perform the following tasks on the affected node:
> - Mark all of the queue manager's autostart queues as "stop pending" in preparation for a planned shutdown.
> - Prevent any of the queue manager's autostart queues from failing over to the node.
> - Upon completion of any jobs currently executing on any of that queue manager's autostart queues, force the queue to fail over to the next available node in the queue's failover list (if any) on which autostart is enabled. (For information on failover lists for autostart queues, see the /AUTOSTART_ON qualifier for the INITIALIZE/QUEUE command.)

> Autostart queues on the node that do not have a failover list, or for which no failover node is enabled for autostart, are stopped upon completion of any current jobs. These stopped queues remain activated for autostart. The queue manager will restart these stopped autostart queues when the ENABLE AUTOSTART command is entered for the affected node or a node to which the queue can fail over.

> By default the command affects the node on which it is entered. Specify the /ON_NODE qualifier to disable autostart on a different node.

> The DISABLE AUTOSTART/QUEUES command is included in the node shutdown command procedure SHUTDOWN.COM. If you shutdown a node without using SHUTDOWN.COM, and the node is running autostart queues, you might want to enter the DISABLE AUTOSTART/QUEUES command first.

> The DISABLE AUTOSTART/QUEUES command only affects autostart queues.

### Qualifiers

> #### /NAME_OF_MANAGER=name

> Specifies the name of the queue manager controlling the autostart queues you want to disable. The qualifier allows the autostart feature to be used differently for different sets of queues.

> If the /NAME_OF_MANAGER qualifier is omitted, the default queue manager name SYS$QUEUE_MANAGER is used. For more information on multiple queue managers, refer to the OpenVMS System Manager's Manual.

> #### /ON_NODE=nodename

> Specifies a node in an OpenVMS Cluster system. Use this qualifier to disable autostart on a node other than the one from which you enter the command.

> #### /QUEUES

> Specifies that autostart is to be disabled for queues. (This qualifier is used by default.)

### Examples

#1
    $ INITIALIZE/QUEUE/BATCH/START/AUTOSTART_ON=SATURN:: BATCH_1
    $ ENABLE AUTOSTART/QUEUES
       .
       .
       .
    $ DISABLE AUTOSTART/QUEUES

> In this example, the INITIALIZE/QUEUE command creates an autostart queue BATCH_1, capable of executing on node SATURN. The /START qualifier activates the queue for autostart. The ENABLE AUTOSTART/QUEUES command (executed on node SATURN) enables autostart on the node, causing the queue (and any other active autostart queues on the node) to begin executing jobs.

> The DISABLE AUTOSTART command (executed on node SATURN) stops autostart queues on the node, and prevents any queues from failing over to the node.

> This command only affects queues managed by the default queue manager SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER qualifier is not specified.

> Because BATCH_1 is set up to run only on one node, the queue cannot fail over to another node and therefore is stopped; however, the queue remains active for autostart and will be started when the ENABLE AUTOSTART command is entered for node SATURN. No START/QUEUE command is needed to restart BATCH_1 unless autostart of the queue is deactivated with the STOP/QUEUE/NEXT or STOP/QUEUE/RESET command.

#2
    $ DISABLE AUTOSTART/QUEUES/ON_NODE=JADE

> The DISABLE AUTOSTART/QUEUES command in this example disables autostart on the OpenVMS Cluster node JADE. This command can be entered from any node in the cluster.

## DISCONNECT

> Breaks the connection between a physical terminal and a virtual terminal. After the physical terminal is disconnected, both the virtual terminal and the process using it remain on the system.

> Requires that your physical terminal is connected to a virtual terminal.

### Format

> DISCONNECT

### Parameters

> None.

### Description

> Use the DISCONNECT command to disconnect a physical terminal from a virtual terminal and its associated process. The virtual terminal and the process remain on the system, so you can use the CONNECT command to reconnect to the process later. (For more information about virtual terminals and how to connect to them, see the description of the CONNECT command.) To terminate a process connected to a virtual terminal, use the LOGOUT command.

> After you are disconnected from a virtual terminal, you can use the physical terminal to log in again.

> You can use the DISCONNECT command only if your physical terminal is connected to a virtual terminal.

### Qualifier

> #### /CONTINUE

> #### /NOCONTINUE (default)

> Controls whether the CONTINUE command is executed in the current process just before connecting to another process. This procedure permits an interrupted image to continue processing after the disconnection until the process needs terminal input or attempts to write to the terminal. At that point, the process waits until the physical terminal is reconnected to the virtual terminal.

###

#### Examples

#1
    $ DISCONNECT

> This command disconnects a physical terminal from a virtual terminal, but does not log the process out. Now you can use the physical terminal to log in again.

#2

    $ RUN PAYROLL
    [Ctrl/Y]
    $ DISCONNECT/CONTINUE

> In this example, the RUN command is entered from a physical terminal that is connected to a virtual terminal. After the image PAYROLL.EXE is interrupted, the DISCONNECT command disconnects the physical and the virtual terminals without logging out the process. The /CONTINUE qualifier allows the image PAYROLL.EXE to continue to execute until the process needs terminal input or attempts to write to the terminal. At that point, the process waits until the physical terminal is reconnected to the virtual terminal; however, you can use the physical terminal to log in again and perform other work.

## DISMOUNT

> Closes a mounted disk or tape volume for further processing and deletes the logical name associated with the device.

> Requires the GRPNAM (group logical name) and SYSNAM (system logical name) privileges to dismount group and system volumes.

### Format

> DISMOUNT device-name[:]

### Parameter

> #### device-name[:]

> Name of the device containing the volume---either a logical name or a physical name. If a physical name is specified, the controller defaults to A and the unit defaults to 0.

> If the volume currently mounted on the device is a member of a disk or tape volume set, all volumes in the set are dismounted, unless the /UNIT qualifier is specified.

### Description

> The DISMOUNT command (which invokes the $DISMOU system service) checks for conditions that prevent a Files-11 volume from dismounting. The conditions fall into the following categories:
> - Installed swap and page files
> - Installed images
> - Devices spooled to the volume
> - Open user files (any files not falling into one of the first three categories)

> If the DISMOUNT command does not find any of these conditions, it performs the following operations:

> - Removes the volume from the user's list of mounted volumes, deletes the logical name (if any) associated with the volume, and decrements the mount count.
> - If the mount count equals zero after being decremented, the DISMOUNT command marks the volume for dismounting.
>   As soon as the volume is idle, that is, after the DISMOUNT command has determined that no user has any open files on the volume, the DISMOUNT command marks a Files-11 volume for dismounting, and dismounts the volume soon.
> - If the mount count does not equal zero after being decremented, the DISMOUNT command does not mark the volume for dismount (because the volume must have been mounted shared). In this case, the total effect for the issuing process is that the process is denied access to the volume and the logical name is deleted.
> - After a volume is dismounted, nonpaged pool is returned to the system. Paged pool is also returned if the volume was mounted using the /GROUP or /SYSTEM qualifiers.

> If the DISMOUNT command does find open files or any other condition that prevents the volume from dismounting, it does not mark the volume for dismounting. Instead, the DISMOUNT command displays a message indicating that the volume cannot be dismounted, followed by messages indicating the conditions that exist and the number of instances of each condition.

> The /OVERRIDE=CHECKS qualifier allows a volume to be marked for dismounting despite open files or other conditions. For example, marking a volume for dismounting prevents any new files from being opened. Also, when a volume is marked for dismounting, file-system caches are flushed. This activity is especially important when the system is shutting down and the file-system caches must be written to the disk.

> If a volume is part of a Files-11 volume set and the /UNIT qualifier is not specified, the entire volume set will be dismounted.

> If the volume was mounted with the /SHARE qualifier, it is not actually dismounted until all users who mounted it dismount it or log out; however, the DISMOUNT command deletes the logical name associated with the device.

> If the device was allocated with an ALLOCATE command, it remains allocated after the volume is dismounted with the DISMOUNT command. If the device was implicitly allocated by the MOUNT command, the DISMOUNT command deallocates it.

> If the volume was mounted with the /GROUP or the /SYSTEM qualifier, it is dismounted even if other users are currently accessing it. The GRPNAM and SYSNAM user privileges are required to dismount group and system volumes, respectively.

### Qualifiers

> #### /ABORT

> Requires volume ownership or the user privilege VOLPRO (volume protection) to use this qualifier with a volume that was mounted with neither the /GROUP nor the /SYSTEM qualifier. Additionally requires the user privilege SHARE if the volume is mounted privately by a process other than the process issuing the DISMOUNT command.

> Specifies that the volume is to be dismounted, regardless of who mounted it. The primary purpose of the /ABORT qualifier is to terminate mount verification. The DISMOUNT/ABORT command also cancels any outstanding I/O requests. If the volume was mounted with the /SHARE qualifier, the /ABORT qualifier causes the volume to be dismounted for all of the users who mounted it.

> #### /CLUSTER

> Dismounts a volume throughout a dual-architecture OpenVMS Cluster system. If you specify DISMOUNT/CLUSTER, the DISMOUNT command checks for open files or other conditions that will prevent a Files-11 volume on the local node from dismounting. If the DISMOUNT command does not find any open files or other conditions, it checks for conditions on all other nodes in the OpenVMS Cluster. If the DISMOUNT command finds one of the conditions on any node, it displays an error message identifying the device and the nodes on which the error occurred, followed by an error message indicating open files or other conditions on the volume.

> After the DISMOUNT command successfully dismounts the volume on the local node, it dismounts the volume on every other node in the existing OpenVMS Cluster environment. If the system is not a member of a cluster, the /CLUSTER qualifier has no effect.

> #### /FORCE_REMOVAL ddcu:

> Expels a named shadow set member from the shadow set.

> If connectivity to a device has been lost and the shadow set is in mount verification, you can use the `/FORCE_REMOVAL ddcu:` to immediately expel a named shadow set member (ddcu:) from the shadow set. If you omit this qualifier, the device is not dismounted until mount verification completes.

> Note that you cannot use this qualifier in conjunction with the /POLICY=MINICOPY (=OPTIONAL) qualifier.

> The device specified must be a member of a shadow set that is mounted on the node where the command is issued.

> #### /OVERRIDE=CHECKS

> Marks a Files-11 volume for dismounting even if files are open on the volume. If you specify DISMOUNT/OVERRIDE=CHECKS, the DISMOUNT command displays messages indicating any open files or other conditions that prevent dismounting, immediately followed by a message indicating that the volume has been marked for dismounting.

> This command does not close open files on the device. A device cannot be properly dismounted until either all processes with open files have properly closed them, or the processes have been rundown completely.

> A substantial amount of time can pass between the time you enter the DISMOUNT/OVERRIDE=CHECKS command and the completion of the dismount operation. Always wait for the dismount to complete before you remove the volume. (To verify that the dismount has completed, enter the SHOW DEVICES command.) Note that the final phase of volume dismounting occurs in the file system, and all open files on the volume must be closed before the actual dismount can be done. Note also that the file system cannot dismount a volume while any known file lists associated with it contain entries.

> By using this command, the device is marked for dismount. This prevents additional processes from opening files on the device while existing open files are closed.

> #### /POLICY=[NO]MINICOPY[=(OPTIONAL)]

> Controls the setup and use of the shadowing minicopy function.

> The exact meaning of the MINICOPY keyword depends on the context of the DISMOUNT command, as follows:

> 1. If this is a dismount of a single member from a multi-member shadow set, a write bitmap is created to track all writes to the shadow set. This write bitmap may be used at a later time to return the removed member to the shadow set with a minicopy.
>    If the write bitmap cannot be initiated and the keyword OPTIONAL is not specified, the dismount will fail and the member will not be removed.
>    If you omit the /POLICY qualifier or if you specify /POLICY=NOMINICOPY, no bitmap will be created.
> 2. If this is the final dismount of the shadow set in the cluster, the shadow set is verified to be capable of a future minicopy operation.
>    If the shadow set has only one member or is in a merge state, and if OPTIONAL was not specified, the dismount will fail.
>    Specifying neither NOMINICOPY nor MINICOPY is the same as MINICOPY=OPTIONAL, as the set will be dismounted regardless of the prior checks.

> For additional information, refer to Volume Shadowing for OpenVMS.

> #### /UNIT

> Dismounts only one volume of a volume set on the specified device. By default, all volumes in a set are dismounted.

> Note Avoid dismounting the root volume of a volume set, because it contains the master file directory (MFD). It may be impossible to access files on a volume set if the MFD is not accessible.

> #### /UNLOAD

> #### /NOUNLOAD

> Determines whether the device on which the volume is mounted is physically unloaded. If you specify the DISMOUNT command without the /UNLOAD or the /NOUNLOAD qualifier, the qualifier that you specified with the MOUNT command (either /UNLOAD or /NOUNLOAD) determines whether the volume is unloaded physically.

### Examples

#1
    $ MOUNT MTA0: PAYVOL TAPE
       .
       .
       .
    $ DISMOUNT TAPE

> The MOUNT command in this example mounts the tape whose volume identification is PAYVOL on the device MTA0: and assigns the logical name TAPE to the device. By default, the volume is not shareable. The DISMOUNT command releases access to the volume, deallocates the device, and deletes the logical name TAPE.

#2
    $ MOUNT/SHARE DKA3:  DOC_FILES
       .
       .
       .
    $ DISMOUNT DKA3:

> The MOUNT command in this example mounts the volume labeled DOC_FILES on the device DKA3. Other users can enter MOUNT commands to access the device. The DISMOUNT command shown in this example deaccesses the device for the process issuing the command. If other users still have access to the volume, the volume remains mounted for their process or processes.

#3
    $ DISMOUNT/NOUNLOAD  DMA2:

> The DISMOUNT command in this example dismounts the volume; the /NOUNLOAD qualifier requests that the volume remain in a ready state.

#4
    $ MOUNT/BIND=PAYROLL  DMA1:,DMA2:  PAYROLL01,PAYROLL02
       .
       .
       .
    $ DISMOUNT/UNIT  DMA2:

> The MOUNT command in this example mounts PAYROLL, a two-volume set. The DISMOUNT command dismounts only PAYROLL02, leaving PAYROLL01 accessible. Note that because the master file directory (MFD) for the volume set is on the root volume, you should not dismount the root volume (in this case, PAYROLL01) of the volume set.

#5
    $ DISMOUNT $10$DJA100
    %DISM-W-CANNOTDMT, $10$DJA100: cannot be dismounted
    %DISM-W-INSWPGFIL, 4 swap or page files installed on volume
    %DISM-W-SPOOLEDEV, 3 devices spooled to volume
    %DISM-W-INSTIMAGE, 7 images installed on volume
    %DISM-W-USERFILES, 6 user files open on volume

> The DISMOUNT command in this example displays the open files and other conditions that prevent device $10$DJA100 from dismounting.

#6
    $ DISMOUNT/CLUSTER $10$DJA100
    %DISM-W-RMTDMTFAIL, $10$DJA100: failed to dismount on node SALT
    %DISM-W-FILESOPEN, volume has files open on remote node
    %DISM-W-RMTDMTFAIL, $10$DJA100: failed to dismount on node PEPPER
    %DISM-W-FILESOPEN, volume has files open on remote node
    %DISM-W-CANNOTDMT, $10$DJA100: cannot be dismounted

> The DISMOUNT command in this example displays messages identifying device $10$DJA100 and nodes SALT and PEPPER on which errors occurred followed by messages indicating open files on the volume.

Previous | Next | Contents | Index

| privacy and legal statement |
9996PRO_016.HTML