 |
OpenVMS System Management Utilities Reference
Manual
DISKQUOTA DELETE
Removes an entry from a quota file.
See the command DISKQUOTA REMOVE for more information. The DISKQUOTA
REMOVE and DISKQUOTA DELETE commands perform the same function.
DISKQUOTA DISABLE
Suspends the maintenance and enforcement of disk quotas on a volume in
the current management environment; this applies to each node that has
the disk mounted.
Caution
To use the DISKQUOTA DISABLE command on a disk that has been mounted on
multiple nodes in a cluster, you must first specify the nodes in the
SET ENVIRONMENT command.
|
Requires SYSPRV privilege, a system UIC, or ownership of the volume.
Format
DISKQUOTA DISABLE
Parameters
None.
Qualifier
/DEVICE=device-spec
Specifies a disk volume on which to disable a quota file. SYSMAN
validates the device specification. A logical name may be specified for
device-spec. If so, it is translated in the target environment.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
Description
The DISKQUOTA DISABLE command suspends quota operations on a volume. To
permanently disable quotas on a device, disable the quotas with the
DISKQUOTA DISABLE command and delete the file [000000]QUOTA.SYS.
Otherwise, the system implicitly enables quotas when the disk is
mounted, leaving invalid quota information.
If you enable the quota file later, enter the DISKQUOTA REBUILD command
to update UIC entries and usage counts.
Examples
| #1 |
SYSMAN> SET ENVIRONMENT/NODE=(AMANDA,BARRY)
SYSMAN> DISKQUOTA DISABLE /DEVICE=DJA1:
|
These commands suspend quota enforcement on disk DJA1, which is mounted
on nodes AMANDA and BARRY.
| #2 |
SYSMAN> SET ENVIRONMENT/CLUSTER (1)
%SYSMAN-I-ENV, current command environment:
Clusterwide on local cluster
Username STEIN will be used on nonlocal nodes
SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] (2)
%SYSMAN-I-OUTPUT, command execution on node WALTER
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node ARTOS2
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node ARTOS1
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node EXPERT
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
SYSMAN> DISKQUOTA DISABLE/DEVICE=$6$dkd0: (3)
SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] (4)
%SYSMAN-I-OUTPUT, command execution on node WALTER
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node ARTOS2
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node ARTOS1
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node EXPERT
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
SYSMAN>
|
In this example, the disk $6$dkd0: has been mounted clusterwide.
- The SET ENVIRONMENT command sets the
environment for all nodes in the cluster.
- The output of this DO SHOW QUOTA command
shows that disk quotas are enabled over the cluster.
- The DISKQUOTA DISABLE command disables disk
quotas over the entire cluster.
- The output of this DO SHOW QUOTA command
shows that disk quotas have been disabled.
DISKQUOTA ENABLE
Resumes quota enforcement on a disk volume in the current management
environment; this applies to each node that has the disk mounted.
Caution
To use the DISKQUOTA ENABLE command on a disk that has been mounted on
multiple nodes in a cluster, you must first specify the nodes in the
SET ENVIRONMENT command.
|
Requires SYSPRV privilege, a system UIC, or ownership of the volume.
Format
DISKQUOTA ENABLE
Parameters
None.
Qualifier
/DEVICE=device-spec
Specifies a disk volume on which to enable the quota file. SYSMAN
validates the device specification. A logical name may be specified for
device-spec. If so, it is translated in the target environment.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
Description
The DISKQUOTA ENABLE command reinstates the enforcement of quotas on a
volume that had been suspended with the DISKQUOTA DISABLE command.
Whenever you enable quotas on a volume, use the DISKQUOTA REBUILD
command to update UIC entries and usage counts.
Examples
| #1 |
SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22)
SYSMAN> DISKQUOTA ENABLE
SYSMAN> DISKQUOTA REBUILD
|
The DISKQUOTA ENABLE command in this example resumes quota enforcement
on the default disk DJA12, which is mounted on NODE21 and NODE22. The
DISKQUOTA REBUILD command updates the quota file, correcting quotas and
adding any new entries.
| #2 |
SYSMAN> SET ENVIRONMENT/CLUSTER (1)
%SYSMAN-I-ENV, current command environment:
Clusterwide on local cluster
Username STEIN will be used on nonlocal nodes
SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] (2)
%SYSMAN-I-OUTPUT, command execution on node WALTER
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node ARTOS2
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node ARTOS1
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
%SYSMAN-I-OUTPUT, command execution on node EXPERT
%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume
SYSMAN> DISKQUOTA ENABLE/DEVICE=$6$dkd0: (3)
SYSMAN> DO SHOW QUOTA/DISK=$6$dkd0:/USER=[0,0] (4)
%SYSMAN-I-OUTPUT, command execution on node WALTER
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node ARTOS2
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node ARTOS1
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
%SYSMAN-I-OUTPUT, command execution on node EXPERT
User [0,0] has 0 blocks used, 1000 available,
of 1000 authorized and permitted overdraft of 100 blocks on $6$DKD0
|
In this example, the disk $6$dkd0: has been mounted clusterwide.
- The SET ENVIRONMENT command sets the
environment for all nodes in the cluster.
- The output of this DO SHOW QUOTA command
shows that disk quotas have not been enabled.
- The DISKQUOTA ENABLE command enables disk
quotas over the entire cluster.
- The output of this DO SHOW QUOTA command
shows that disk quotas have been enabled over the cluster.
DISKQUOTA MODIFY
Changes an entry in a quota file or adjusts default values for quotas
and overdrafts. If a new quota limit is less than the current usage
count, SYSMAN issues a warning message before it implements the new
quota.
Requires write (W) access to the quota file.
Format
DISKQUOTA MODIFY owner
Parameter
owner
Specifies the user identification code (UIC) or rights identifier. You
can specify the UIC in numeric or alphanumeric format. For complete
information about UIC specification, refer to the OpenVMS Guide to System Security.
Rights identifiers are granted with the Authorize utility and use an ID
format rather than a UIC format. Refer to the OpenVMS Programming Concepts Manual for a
complete description of rights identifiers.
When working in nonlocal environments, make sure that the alphanumeric
UIC or rights identifiers that you use are valid for the environment.
Qualifiers
/DEVICE=device-spec
Specifies the disk volume that contains the quota file. SYSMAN
validates the device specification. A logical name may be specified for
device-spec. If so, it is translated in the target environment.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
/OVERDRAFT=value
Specifies a positive integer that provides an overdraft value for the
specified UIC. If you omit a value, the overdraft value defaults to the
overdraft value in the entry for [0,0].
/PERMQUOTA=value
Specifies a positive integer that provides the quota for the specified
UIC. If you omit a value, the permanent quota defaults to the value of
the quota in the entry for [0,0].
Description
The DISKQUOTA MODIFY command changes values in a quota file for the
disk named in the device specification. If you establish a quota limit
that is less than the current usage count, a user can still log in and
out, but cannot create files.
After creating a quota file, use the DISKQUOTA MODIFY command to set
default values for quotas and overdrafts. UIC [0,0] sets the default
permanent quota and overdraft values for a quota file, so you must
change the entry [0,0] to values appropriate for your installation.
Unless you specify quota and overdraft values when adding a file entry,
SYSMAN applies these defaults to UIC entries.
Examples
| #1 |
SYSMAN> SET ENVIRONMENT/NODE=NODE21
SYSMAN> DISKQUOTA MODIFY /DEVICE=DUA12: [0,0] -
_SYSMAN> /PERMQUOTA=3000 /OVERDRAFT=300
|
The commands in this example edit the entry for UIC [0,0] in the quota
file on DUA12, which is located on NODE21.
| #2 |
SYSMAN> DISKQUOTA MODIFY /DEVICE=SYS$DISK1 [TTD,DAVIS] -
_SYSMAN> /PERMQUOTA=900
|
This command sets the permanent quota for UIC [TTD,DAVIS] to 900
blocks, while making no change to the overdraft limit. SYSMAN modifies
the quota file that is located on disk SYS$DISK1 in the current
environment.
If the user name DAVIS has a unique UIC on the system, you can enter
the following command:
SYSMAN> DISKQUOTA MODIFY DAVIS/PERMQUOTA=900
|
DISKQUOTA REBUILD
Updates a quota file, adding new UICs and correcting usage counts for
each user on the volume.
Requires write (W) access to the quota file, plus one of the following
items: SYSPRV privilege, a system UIC, or ownership of the volume.
Format
DISKQUOTA REBUILD
Parameters
None.
Qualifier
/DEVICE=device-spec
Specifies the disk volume that contains the quota file. SYSMAN
validates the device specification and translates any logical name in
the target environment before rebuilding the file.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
Description
The DISKQUOTA REBUILD command reads the disk, recalculates usage counts
for all existing entries in QUOTA.SYS, and adds new entries. It sets
quota and overdraft values to the defaults set in UIC [0,0] if the
entry did not previously exist. While the DISKQUOTA REBUILD command is
executing, file activity on the volume is frozen. No files can be
created, deleted, extended, or truncated.
Use the DISKQUOTA REBUILD command in the following circumstances:
- After creating a quota file on a volume with existing files.
- When the quota file has been enabled after a period of being
disabled. The command corrects the usage counts and adds any new UICs.
Example
|
SYSMAN> SET ENVIRONMENT /NODE=NODE21
SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV
SYSMAN> DISKQUOTA ENABLE /DEVICE=DUA226:
SYSMAN> DISKQUOTA REBUILD /DEVICE=DUA226:
|
These commands enable the quota file and reconstruct the usage counts
for all entries on disk DUA226, which is located on node NODE21.
DISKQUOTA REMOVE
Removes an entry from a quota file.
Requires write (W) access to the quota file.
Format
DISKQUOTA REMOVE owner
Parameter
owner
Specifies the user identification code (UIC) or rights identifier. You
can specify the UIC in numeric or alphanumeric format. For complete
information about UIC specification, refer to the OpenVMS Guide to System Security.
Rights identifiers are granted with the Authorize utility and use an ID
format rather than a UIC format. For more information about rights
identifiers, refer to the OpenVMS Programming Concepts Manual.
When working in nonlocal environments, be careful that the alphanumeric
UIC or rights identifiers that you use are valid for the environment.
Qualifier
/DEVICE=device-spec
Specifies the disk volume containing the quota file. SYSMAN validates
the device specification and translates any logical name in the target
environment before deleting the UIC entry.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
Description
The DISKQUOTA REMOVE command eliminates the specified UIC from the
quota file on the named device.
If the usage count for the UIC is not zero, files remain on disk and
the user can still log in, but any attempt to create or extend files
will fail.
The UIC [0,0] entry cannot be removed.
Example
|
SYSMAN> SET ENVIRONMENT/NODE=MARS
SYSMAN> SHOW PROFILE
%SYSMAN-I-DEFDIR, Default directory on node MARS -- WORK2:[CASEY]
%SYSMAN-I-DEFPRIV, Process privileges on node MARS --
TMPMGX
OPER
NETMBX
SYSPRV
SYSMAN> DISKQUOTA REMOVE /DEVICE=DUA45: [TTD,DAVIS]
|
These commands remove UIC [TTD,DAVIS] from the quota file for disk
DUA45, which is located on node MARS.
DISKQUOTA SHOW
Displays quotas, overdrafts, and usage counts.
Requires no additional privileges to display your own quota, overdraft,
and usage count, but otherwise requires read (R) access to the quota
file.
Format
DISKQUOTA SHOW owner
Parameter
owner
Specifies the user identification code (UIC) or rights identifier. You
can specify the UIC in numeric or alphanumeric format. For complete
information about UIC specification, refer to the OpenVMS Guide to System Security.
Rights identifiers are granted with the Authorize utility and use an ID
format rather than a UIC format. Refer to the OpenVMS Programming Concepts Manual for a
complete description of rights identifiers.
You can use an asterisk wildcard character (*) to specify the quota
entry as follows:
| Command |
Description |
|
DISQUOTA SHOW CJ
|
Show user CJ (if CJ has a unique UIC on the system)
|
|
DISKQUOTA SHOW [TTD,CJ]
|
Show user CJ in group TTD
|
|
DISKQUOTA SHOW [TTD,*]
|
Show all users in group TTD
|
|
DISKQUOTA SHOW *
|
Show all entries
|
Qualifiers
/DEVICE=device-spec
Specifies the disk volume containing the quota file. DISKQUOTA
validates device specification and translates any logical name in the
target environment before displaying UIC entries.
Without a device specification, SYSMAN uses the default disk on the
target node. Unless you have set a default device with the SET PROFILE
command, the default disk is the current device on the local node or
the login default device on another node, depending on the established
environment.
/OUTPUT[=filespec]
Directs output to the specified file. Without a file specification,
/OUTPUT defaults to SYSMAN.LIS in the current directory on the local
node where you are running SYSMAN.
Example
|
SYSMAN> DISKQUOTA SHOW [ACCT,*]
|
This command displays quotas, overdrafts, and usage counts for all
users in group ACCT on the default disk.
DO
Executes a DCL command or DCL command procedure on all nodes in the
current management environment.
Requires the privileges of the DCL command being executed.
Format
DO [command-line]
Parameter
command-line
Specifies a command string that SYSMAN passes to the command line
interface (CLI) for execution.
The command DO MCR SYSMAN [SYSMAN-command] is not supported. Instead,
follow these steps:
- Enter MCR SYSMAN at the dollar ($) prompt.
- At the SYSMAN> prompt, set the environment to the selected node
or nodes with the SET ENVIRONMENT command.
- Enter a SYSMAN command at the SYSMAN> prompt.
For complete information about DCL command syntax, refer to the
OpenVMS DCL Dictionary.
Qualifier
/CONFIRM
Verifies that you want to perform a DO command on each node you have
specified with the SYSMAN command SET ENVIRONMENT.
When you use the /CONFIRM qualifier, the system prompts you as follows:
Execute command for node <nodename>? [N]:
|
The following responses are valid:
YES NO QUIT ALL
TRUE FALSE [Ctrl/Z]
1 0 [Ctrl/C]
[Return]
|
Usage Notes
- Affirmative answers are YES, TRUE, and 1.
- Negative answers are NO, FALSE, 0, and pressing the Return key.
- You can use any combination of uppercase and lowercase letters for
word responses.
- You can abbreviate word responses to one or more letters (for
example, T, TR, or TRU for TRUE), but these abbreviations must be
unique.
- Entering QUIT or pressing Ctrl/C or Ctrl/Z indicates that you want
to stop processing the command at that point.
- When you enter ALL, the command continues to process, but the
system displays no further prompts.
- If you type a response that is not valid, SYSMAN issues an error
message and redisplays the prompt.
/OUTPUT[=filespec]
Records output from the command in the specified file, which is located
on the node from which you are executing SYSMAN. Position the qualifier
immediately after the DO command. The default file specification is
SYSMAN.LIS in the current device and directory. SYSMAN prefaces output
with the message "%SYSMAN-I-OUTPUT, command execution on node
xxxxxx."
/PAUSE
Controls the rate at which the system displays information. Using the
/PAUSE qualifier causes the system to display information about one
node at a time; the system prompts you to press Return when you are
ready to display information about the next node.
Description
The DO command executes the accompanying DCL command or DCL command
procedure on all nodes in the current environment. Each DO command
executes as an independent process, so no process context is retained
between DO commands. For this reason, you must express all DCL commands
in a single command string, and you cannot run a program that expects
input.
In an OpenVMS Cluster environment, SYSMAN executes the commands
sequentially on all nodes in the cluster. Each command executes
completely before SYSMAN sends it to the next node in the environment.
Any node that is unable to execute the command returns an error
message. SYSMAN displays an error message if the timeout period expires
before the node responds.
Use the RSX command MCR to run programs located in SYS$SYSTEM. The MCR
command enables you to run a program and supply a command in a single
command string.
The system cannot display output returned from a command of more than
2048 characters without concatenation.
Three exceptions to be aware of when using the DO command in clusters
are the following ones:
-
In a dual-architecture heterogeneous cluster running both OpenVMS VAX
and OpenVMS Alpha, some uses of the DO command may require special
handling. For example, if you are installing images that are named
differently in each architecture, you can still use the DO command if
you create logical name tables for VAX and for Alpha nodes. See the
example sequence that follows this description for an example.
- Some DCL commands, such as MOUNT/CLUSTER or SET QUORUM/CLUSTER,
operate clusterwide by design. It is best to avoid using these kinds of
commands with the DO command in SYSMAN when the environment is set to
cluster. As alternatives, you could leave SYSMAN temporarily with the
SPAWN command and execute these commands in DCL, or you could define
the environment to be a single node within the cluster. Similarly,
operations on clusterwide logical names and tables operate clusterwide
by design.
- Make sure that if you redefine the logical DCLTABLES, you do so in
SYLOGICALS.COM, not in SYSTARTUP_VMS.COM or elsewhere. Otherwise, you
will receive a command interpreter failure when executing a DO command
on a remote node.
Examples
| #1 |
SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
SYSMAN> DO/OUTPUT SHOW DEVICE
|
The first command in this example defines the management environment to
be the cluster where NODE21 is a member. The second command executes a
DCL command on each node in the cluster. Output goes to the file
SYSMAN.LIS rather than to the terminal.
| #2 |
SYSMAN> SET PROFILE /PRIVILEGES=(CMKRNL,SYSPRV) -
_SYSMAN> /DEFAULT=SYS$SYSTEM
SYSMAN> DO INSTALL ADD /OPEN/SHARED WRKD$:[MAIN]STATSHR
SYSMAN> DO MCR AUTHORIZE ADD JONES/PASSWORD=COLUMBINE -
_SYSMAN> /DEVICE=WORK1 /DIRECTORY=[JONES]
|
The first command in this example adds CMKRNL and SYSPRV privileges to
the current profile because they are required by the INSTALL command
and the AUTHORIZE command. The next command installs the file STATSHR.
The last command sets up an account for user JONES, specifying a
password as well as a default device and directory. The MCR command in
the last line of the example enables you to invoke the AUTHORIZE
command from SYS$SYSTEM and add a record to the UAF in one command
string.
| #3 |
SYSMAN> SET ENVIRONMENT/NODE=NODE21
SYSMAN> SET PROFILE /DEFAULT=[CJ.PROGRAMS] -
_SYSMAN> /PRIVILEGES=NOSYSPRV
SYSMAN> DO/OUTPUT @PROCESS_INFO
|
The commands in this example define the environment as a single node
and adjust the current privileges and directory. The DO command
executes the command procedure PROCESS_INFO.COM, located in directory
[CJ.PROGRAMS] and writes any output to SYSMAN.LIS in the directory from
which SYSMAN is running.
| #4 |
$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY SYSMAN$NODE_TABLE
$ DEFINE/TABLE=SYSMAN$NODE_TABLE ALPHA_NODES NODE21,NODE22,NODE23
$ DEFINE/TABLE=SYSMAN$NODE_TABLE VAX_NODES NODE24,NODE25,NODE26
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SET ENVIRONMENT/NODE=ALPHA_NODES
%SYSMAN-I-ENV, current command environment:
Individual nodes: NODE21,NODE22,NODE23
Username BOUCHARD will be used on nonlocal nodes
SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE
%SYSMAN-I-OUTPUT, command execution on node NODE21
%SYSMAN-I-OUTPUT, command execution on node NODE22
%SYSMAN-I-OUTPUT, command execution on node NODE23
SYSMAN> DO INSTALL REPLACE SYS$SYSTEM: COM_FORTRAN.EXE
%SYSMAN-I-OUTPUT, command execution on node NODE21
%SYSMAN-I-OUTPUT, command execution on node NODE22
%SYSMAN-I-OUTPUT, command execution on node NODE23
SYSMAN> SET ENVIRONMENT/NODE=VAX_NODES
%SYSMAN-I-ENV, current command environment:
Individual nodes: NODE24,NODE25,NODE26
Username BOUCHARD will be used on nonlocal nodes
SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE
%SYSMAN-I-OUTPUT, command execution on node NODE24
%SYSMAN-I-OUTPUT, command execution on node NODE25
%SYSMAN-I-OUTPUT, command execution on node NODE26
SYSMAN> DO INSTALL REPLACE SYS$SYSTEM:FORTRAN$MAIN.EXE
%SYSMAN-I-OUTPUT, command execution on node NODE24
%SYSMAN-I-OUTPUT, command execution on node NODE25
%SYSMAN-I-OUTPUT, command execution on node NODE26
|
|
