OpenVMS System Management Utilities Reference Manual

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 on 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. See 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 
   

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

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 on 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, see 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.

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 on 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. See 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.

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:

1. Enter MCR SYSMAN at the dollar ($) prompt.
2. At the SYSMAN> prompt, set the environment to the selected node or nodes with the SET ENVIRONMENT command.
3. Enter a SYSMAN command at the SYSMAN> prompt.

For complete information on 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.

Three exceptions to be aware of when using the DO command in clusters are:

• 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.
• 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: DEC_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 
   

   
   This example shows how you can define logical names for VAX and Alpha nodes in a dual-architecture heterogeneous cluster, so that you can use the DO command to install architecture-specific images.

5. $ MCR SYSMAN 
   SYSMAN> SET ENVIRONMENT/CLUSTER 
   %SYSMAN-I-ENV, current command environment: 
           Clusterwide on local cluster 
           Username STEIN   will be used on nonlocal nodes 
   SYSMAN> DO/CONFIRM SHOW TIME 
   Execute command for node EXPERT? [N]: Y [Return] 
   %SYSMAN-I-OUTPUT, command execution on node EXPERT 
     22-MAR-1996 09:40:28 
    
   Execute command for node MODERN? [N]: Y [Return] 
    
   SYSMAN-I-OUTPUT, command execution on node MODERN 
     22-MAR-1996 09:40:56 
    
   Execute command for node IMPOSE? [N]: N [Return] 
    
   Execute command for node ADU26A? [N]: Y [Return] 
      .
      .
      .
   

   
   The commands in this example show how to control whether the system displays time for each node in a cluster.

6. SYSMAN> DO/PAUDE SHOW TIME 
    
   %SYSMAN-I-OUTPUT, command execution on node EXPERT 
     22-MAR-1996 09:40:13 
    
   Press return to continue [Return] 
    
   %SYSMAN-I-OUTPUT, command execution on node MODERN 
     22-MAR-1996 09:40:41 
    
   Press return to continue [Return] 
    
   %SYSMAN-I-OUTPUT, command execution on node IMPOSE 
     22-MAR-1996 09:39:46 
    
   Press return to continue [Return] 
      .
      .
      .
   

   
   The commands in this example show how you can control the rate at which information is displayed on your system.

Terminates the SYSMAN session and returns control to the DCL command level. Any profile changes, established on the local node with the command SET PROFILE, are restored to their values at the time SYSMAN was invoked. You can also press Ctrl/Z to exit at any time.

Format

EXIT

PARAMETERS

None.

QUALIFIERS

None.

Provides online help for using the SYSMAN commands, parameters, and qualifiers. Press Ctrl/Z to exit.

Format

HELP [keyword...]

PARAMETER

keyword

Specifies the command, parameter, or qualifier for which you want help. If you omit the keyword, the HELP command displays a list of Help topics and prompts you for a particular keyword.

QUALIFIERS

None.

Example

SYSMAN> HELP DO 

This command displays help information about the SYSMAN command DO.

On Alpha systems, automatically identifies and configures all hardware devices attached to a system by connecting devices and loading their drivers. On VAX systems, use the SYSGEN command AUTOCONFIGURE.

You must have CMKRNL and SYSLCK privileges to use the IO AUTOCONFIGURE command.

Format

IO AUTOCONFIGURE

PARAMETERS

None.

QUALIFIERS

/SELECT=(device_name)

Specifies the device type to be automatically configured. Use valid device names or mnemonics that indicate the devices to be included in the configuration. You can use wildcard characters with this qualifier.

The /SELECT and /EXCLUDE qualifiers are not mutually exclusive, as they are on VAX systems. You can specify both qualifiers on the command line.

Table 20-3 shows /SELECT qualifier examples.

Table 20-3 /SELECT Qualifier Examples

Command	Devices That Are Configured	Devices That Are Not Configured
/SELECT=P*	PKA,PKB,PIA	None
/SELECT=PK*	PKA,PKB	PIA
/SELECT=PKA*	PKA	PKB,PIA

/EXCLUDE=(device_name)

Specifies the device type that should not be automatically configured. Use valid device names or mnemonics that indicate the devices to be excluded from the configuration. You can use wildcard characters with this qualifier.

The /SELECT and /EXCLUDE qualifiers are not mutually exclusive, as they are on VAX systems. You can specify both qualifiers on the command line.

/LOG

Controls whether the IO AUTOCONFIGURE command displays information about loaded devices.

DESCRIPTION

The IO AUTOCONFIGURE command identifies and configures all hardware devices attached to a system. VAX system managers use the SYSGEN command AUTOCONFIGURE. It connects devices and loads their drivers. You must have CMKRNL and SYSLCK privileges to use the IO AUTOCONFIGURE command.

Examples

SYSMAN> IO AUTOCONFIGURE/EXCLUDE=DKA0

This command autoconfigures all devices on the system except DKA0.

IO AUTOCONFIGURE automatically configures all standard devices that are physically attached to the system, except for the network communications device.

SYSMAN> IO AUTOCONFIGURE/LOG

The /LOG qualifier displays information about all the devices that AUTOCONFIGURE loads.

  6048P054.HTM
  OSSG Documentation
  26-NOV-1996 12:43:42.02

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal