HP OpenVMS Systems Documentation

Content starts here

OpenVMS System Management Utilities Reference Manual


Previous Contents Index

CLASS_SCHEDULE SHOW

The SHOW subcommand displays the characteristics of a scheduling class.

Format

CLASS_SCHEDULE SHOW [class_name] [/qualifier]


Parameter

class_name

Specifies the name of the scheduling class. You must specify a class name or the /ALL qualifier with the SHOW command. The maximum length for the class name is 16 characters.

Qualifiers

/ALL

Displays all scheduling classes. The qualifier must be specified if no class name is given.

/FULL

Displays all information about this scheduling class.

Description

By default, a limited display of data is shown by the SHOW subcommand. The default displays the following:
  • Name
  • Maximum CPU time or times for each range of hours
  • Primary days and secondary days
  • Windfall settings

CLASS_SCHEDULE SUSPEND

The SUSPEND subcommand suspends the specified scheduling class.

Format

CLASS_SCHEDULE SUSPEND class_name


Parameter

class_name

Specifies the name of the scheduling class. You must specify a class name with the SUSPEND command. The maximum length for this name is 16 characters.

Qualifiers

None.

Description

When you suspend a scheduling class, all processes that are part of the scheduling class remain as part of the class but are granted unlimited CPU time.

CONFIGURATION SET CLUSTER_AUTHORIZATION

Modifies security data in a local area cluster.

Requires SYSPRV privilege.


Format

CONFIGURATION SET CLUSTER_AUTHORIZATION


Parameters

None.

Qualifiers

/GROUP_NUMBER=[n]

Specifies the cluster group number that is recorded in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. A group number uniquely identifies each local area cluster on a single Ethernet. This number must be in the range from 1 to 4095 or 61440 to 65535.

/PASSWORD=password

Specifies a password for cluster access. A password consists of 1 to 31 characters, including alphanumeric characters, dollar signs, and underscores. A password provides a second level of validation to ensure the integrity of individual clusters on the same Ethernet that accidentally use identical group numbers. A password also prevents an intruder who discovers the group number from joining the cluster.

Description

The CONFIGURATION SET CLUSTER_AUTHORIZATION command modifies the group number and password of a local area cluster, as recorded in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. If your configuration has multiple system disks, SYSMAN automatically updates each copy of CLUSTER_AUTHORIZE.DAT, provided the environment is defined as a cluster (SET ENVIRONMENT/CLUSTER). For more information about CLUSTER_AUTHORIZE.DAT, refer to OpenVMS Cluster Systems.

Caution

If you change either the group number or the password, you must reboot the entire cluster.

The file CLUSTER_AUTHORIZE.DAT is initialized during execution of CLUSTER_CONFIG.COM and maintained through SYSMAN. Under normal conditions, altering records in the CLUSTER_AUTHORIZE.DAT file interactively is not necessary. To protect the integrity of the cluster membership use the CONFIGURATION SET CLUSTER_AUTHORIZATION command.


Example


SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
SYSMAN> SET PROFILE /PRIVILEGES=SYSPRV
SYSMAN> CONFIGURATION SET CLUSTER_AUTHORIZATION/PASSWORD=GILLIAN
%SYSMAN-I-CAFOLDGROUP, existing group will not be changed
%SYSMAN-I-GRPNOCHG, Group number not changed
SYSMAN-I-CAFREBOOT, cluster authorization file updated.
The entire cluster should be rebooted.

      

The CONFIGURATION SET CLUSTER_AUTHORIZATION command in this example sequence modifies the cluster password. Note that the environment is defined to be a cluster, and the SYSPRV privilege is established before entering the CONFIGURATION SET CLUSTER_AUTHORIZATION command.

CONFIGURATION SET TIME

Modifies the current system time.

Requires OPER, LOG_IO, and SYSPRV privileges, and, in a cluster environment, SYSLCK privilege.


Format

CONFIGURATION SET TIME [time]


Parameters

None.

Description

The CONFIGURATION SET TIME command enables you to reset the system time. Specify a time value using the following format:

[dd-mmm-yyyy[:]] [hh:mm:ss.cc]

You can also enter a delta time value. Refer to the OpenVMS User's Manual for more information about time formats.

In an environment of individual nodes, SYSMAN sets the time to the specified value on each node. Without a time specification, SYSMAN sets the time according to the time-of-year clock on each node.

In an OpenVMS Cluster environment, SYSMAN sets the time to the specified value on each node. If you do not specify a value, SYSMAN uses the time-of-year clock. In a local cluster, SYSMAN reads the clock on the node from which you are executing SYSMAN and assigns this value to all nodes in the cluster. In a remote OpenVMS Cluster, SYSMAN reads the clock on the target node in the cluster and assigns that value to all nodes. Note that the time-of-year clock is optional for some processors; refer to your processor handbook for further information.

SYSMAN uses special processing in an OpenVMS Cluster environment to ensure that all processors in the cluster are set to the same time. Because of communication and processing delays, it is not possible to synchronize clocks exactly. However, the variation is typically less than a few hundredths of a second. If SYSMAN cannot set the time to within one half second of the specified time, you receive a warning message that names the node that failed to respond quickly enough.

As a result of slight inaccuracies in each processor clock, times on various members of a cluster tend to drift apart. The following procedure synchronizes system times in a cluster environment:


$  SYNCH_CLOCKS:
$  RUN SYS$SYSTEM:SYSMAN
       SET ENVIRONMENT/CLUSTER
       CONFIGURATION SET TIME
       EXIT
$  WAIT 6:00:00
$  GOTO SYNCH_CLOCKS

The procedure sets the time on all cluster nodes to the value obtained from the local time-of-year clock, waits 6 hours, then resets the time for the cluster.


Example


SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)
SYSMAN> SET PROFILE /PRIVILEGE=LOG_IO
SYSMAN> CONFIGURATION SET TIME 12:38:00
      

The CONFIGURATION SET TIME command in this example sequence modifies the system time on NODE21, NODE22, and NODE23.

CONFIGURATION SHOW CLUSTER_AUTHORIZATION

Displays the group number and multicast address of a local area cluster.

Requires SYSPRV privilege.


Format

CONFIGURATION SHOW CLUSTER_AUTHORIZATION


Parameters

None.

Qualifier

/OUTPUT[=filespec]

Redirects output from SYS$OUTPUT to the specified file. If no file specification is provided, SYSMAN writes the output to SYSMAN.LIS in the current directory.

Description

The CONFIGURATION SHOW CLUSTER_AUTHORIZATION command displays the group number and multicast address, and Ethernet address used to send a message to all nodes in the cluster. The group number and multicast address are recorded in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT during the CLUSTER_CONFIG dialog.

In a cluster or multinode environment, SYSMAN displays the group number of the first node and then displays the names of any nodes in the cluster whose group numbers, passwords, or both, are different.


Example


SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
.
.
.
SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV
SYSMAN> CONFIGURATION SHOW CLUSTER_AUTHORIZATION
Node NODE23: Cluster group number 65240
Multicast address: AB-00-04-01-F2-FF

      

The CONFIGURATION SHOW CLUSTER_AUTHORIZATION command in this example displays the group number and multicast address of NODE21. Because the group number and password on other nodes in the cluster are identical, no further information is displayed.

CONFIGURATION SHOW TIME

Displays the current date and system time to the nearest hundredth of a second.

Format

CONFIGURATION SHOW TIME


Parameters

None.

Qualifier

/OUTPUT[=filespec]

Redirects output from SYS$OUTPUT to the specified file. If no file specification is provided, SYSMAN writes the output to SYSMAN.LIS in the current directory.

Example


SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
.
.
.
SYSMAN> CONFIGURATION SHOW TIME
System time on node NODE21:  19-JUN-2000 13:32:19.45
System time on node NODE22:  19-JUN-2000 13:32:27.79
System time on node NODE23:  19-JUN-2000 13:32:58.66
      

The CONFIGURATION SHOW TIME command in this example displays the system times for all nodes in the cluster.

DEFINE/KEY

Defines a key to execute a SYSMAN command. This enables you to press the key to enter a command, instead of typing the command name.

Format

DEFINE/KEY key-name string


Parameters

key-name

Specifies the name of the key you are defining. Use the key names in the following table when defining keys.
Key Name VT100 LK201/LK401
PF1 PF1 PF1
PF2 PF2 PF2
PF3 PF3 PF3
PF4 PF4 PF4
KP0, KP1--KP9 keypad 0--9 keypad 0--9
PERIOD period key period key
COMMA comma key comma key
MINUS minus key minus key
ENTER ENTER key ENTER key
UP, DOWN, LEFT, RIGHT arrow keys arrow keys
FIND, INSERT_HERE -- Find, Insert Here keys
REMOVE, SELECT -- Remove, Select keys
PREV_SCREEN -- Previous Screen key
NEXT_SCREEN -- Next Screen key
HELP, DO -- Help, Do keys
F6--F10, F11--F14 -- function keys
F17--F20 -- function keys

string

Specifies the string you want entered when you press the defined key. For example, you can define string as the SYSMAN command SHOW ENVIRONMENT or SHOW PROFILE.

Qualifiers

/ECHO (default)

/NOECHO

Specifies whether the command line echoes after you press the defined key. Note that you cannot define a key using both the /NOECHO and /NOTERMINATE qualifiers.

/IF_STATE=state_list

/NOIF_STATE

Specifies a list of states, any one of which must be set in order to enable the specified key definition. If you omit or negate this qualifier, the current state prevails.

/LOCK_STATE

/NOLOCK_STATE (default)

Retains the state specified by the /SET_STATE qualifier until you use the /SET_STATE qualifier again to change it.

/SET_STATE

/NOSET_STATE

Associates a state with the key you are defining. A state name can be any alphanumeric string. If you omit or negate this qualifier, the current state remains unchanged. You cannot define a key using both the /SET_STATE and /TERMINATE qualifiers.

/TERMINATE

/NOTERMINATE

Determines whether the specified command string executes when you press the key. When you use /NOTERMINATE, you must press the Return key to execute the command string. You cannot define a key using both the /SET_STATE and /TERMINATE qualifiers.

Description

The DEFINE/KEY command assigns a key to a SYSMAN command. This enables you to execute the command by pressing the key. You can confirm which keys you have defined by using the SHOW KEY command.

When you exit from SYSMAN, any SYSMAN key definitions you established will be lost unless you define them in a SYSMAN initialization file. (See Section 21.1.2.)


Examples

#1

SYSMAN> DEFINE /KEY PF1 "SHOW PROFILE"
      

This example shows how to define the keypad key PF1 as the SYSMAN command SHOW PROFILE. To execute the SHOW PROFILE command, press PF1 and then the Return key.

#2

SYSMAN> DEFINE /KEY KP0 /TERMINATE "CONFIGURATION SHOW TIME"
      

This example shows how to define the keypad key 0 as the CONFIGURATION SHOW TIME command. The /TERMINATE qualifier causes the SYSMAN command to execute when you press keypad key 0 without having to press Return.

DISKQUOTA ADD

Adds an entry to a disk quota file and initializes the usage count to zero.

Requires write (W) access to the quota file.


Format

DISKQUOTA ADD owner


Parameter

owner

Specifies the user identification code (UIC) or rights identifier for which the quota entry is added. 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, be careful that the alphanumeric UIC or rights identifiers that you use are valid for the environment.


Qualifiers

/DEVICE=device-spec

Specifies the location of the quota file. SYSMAN validates the device specification. You can specify a logical name for device-spec. If you do, the logical name 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 omitted, 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 omitted, the permanent quota defaults to the value of the quota in the entry for [0,0].

Description

The DISKQUOTA ADD command appends individual entries to a quota file on the specified disk. Note that the quota file must already exist and be enabled.

Unless you specify the permanent quota and overdraft values, SYSMAN applies the default values from the UIC entry [0,0]. You adjust UIC [0,0] with the DISKQUOTA MODIFY command.


Example


SYSMAN> SET ENVIRONMENT/NODE=(NODE22,NODE21) (1)
%SYSMAN-I-ENV, Current command environment:
        Individual nodes: NODE22,NODE21
        Username ALEXIS    will be used on nonlocal nodes.
SYSMAN> SET PROFILE /PRIVILEGE=SYSPRV (2)
SYSMAN> DISKQUOTA ADD [MKT,MORSE] /DEVICE=WORK1 - (3)
_SYSMAN> /PERMQUOTA=200 /OVERDRAFT=50
SYSMAN> DISKQUOTA ADD PAYROLL /DEVICE=WORK1 /PERMQUOTA=1000 (4)


      

  1. Defines the management environment to be NODE22 and NODE21.
  2. Adds SYSPRV privilege to the user's current privileges in order to write to the quota file.
  3. Adds UIC [MKT,MORSE] to the quota file on the device named WORK1 on both NODE22 and NODE21, setting the permanent quota to 200 disk blocks and the overdraft limit to 50 disk blocks, for an absolute limit of 250 blocks.
    If the user name MORSE has a unique UIC on the system, you can enter the following command:


    SYSMAN> DISKQUOTA ADD MORSE
    
  4. Adds an entry for the rights identifier PAYROLL. Any user holding the PAYROLL identifier can use this disk space.

DISKQUOTA CREATE

Creates and enables a quota file for a disk volume that does not currently contain one.

Requires write (W) access to the volume's master file directory (MFD), plus one of the following items: SYSPRV privilege, a system UIC, or ownership of the volume.


Format

DISKQUOTA CREATE


Parameters

None.

Qualifier

/DEVICE=device-spec

Specifies the disk volume on which to create 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 CREATE command creates a quota file for a volume that does not currently have one.

Only one quota file, [000000]QUOTA.SYS, can be present on any volume or volume set. As soon as you create a quota file, establish default values for quotas and overdrafts by adjusting UIC [0,0] with the DISKQUOTA MODIFY command. When a disk has existing files, use the DISKQUOTA REBUILD command to have SYSMAN update the quota file to contain current usage values.

Note

Compaq recommends that you do not create and enable a quota file on the system disk unless users are allowed to create files on that disk.

Example


SYSMAN> SHOW ENVIRONMENT
%SYSMAN-I-ENV, Current command environment:
        Node NODE24 of local cluster
        Username ALEXIS    will be used on nonlocal nodes

SYSMAN> DO SHOW DEVICES
.
.
.
SYSMAN> DISKQUOTA CREATE /DEVICE=DJA31:
SYSMAN> DISKQUOTA MODIFY /DEVICE=DJA31: [0,0] -
_SYSMAN> /PERMQUOTA=10000 /OVERDRAFT=100

      

The commands in this example sequence display the characteristics of the current management environment and verify the device name. Then they create a quota file on the disk DJA31 and set up default quota values.


Previous Next Contents Index