![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Modifies security data in a local area cluster.Requires SYSPRV privilege.
CONFIGURATION SET CLUSTER_AUTHORIZATION
None.
/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.
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, see 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.
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.
Modifies the current system time.Requires OPER and LOG_IO privilege, and in a cluster environment, SYSLCK privilege.
CONFIGURATION SET TIME [time]
None.
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. See 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; see 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_CLOCKSThe 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.
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.
Displays the group number and multicast address of a local area cluster.Requires SYSPRV privilege.
CONFIGURATION SHOW CLUSTER_AUTHORIZATION
None.
/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.
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.
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.
Displays the current date and system time to the nearest hundredth of a second.
CONFIGURATION SHOW TIME
None.
/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.
SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21 . . . SYSMAN> CONFIGURATION SHOW TIME System time on node NODE21: 19-JUN-1996 13:32:19.45 System time on node NODE22: 19-JUN-1996 13:32:27.79 System time on node NODE23: 19-JUN-1996 13:32:58.66
The CONFIGURATION SHOW TIME command in this example displays the system times for all nodes in the cluster.
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.
DEFINE/KEY key-name string
key-name
Specifies the name of the key you are defining. Use the key names in Table 20-2 when defining keys.
Table 20-2 Key Names in SYSMAN 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.
/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.
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 20.3.)
Examples
SYSMAN> DEFINE /KEY PF1 "SHOW PROFILE"
SYSMAN> DEFINE /KEY KP0 /TERMINATE "CONFIGURATION SHOW TIME"
Adds an entry to a disk quota file and initializes the usage count to zero.Requires write (W) access to the quota file.
DISKQUOTA ADD owner
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 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, be careful that the alphanumeric UIC or rights identifiers that you use are valid for the environment.
/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].
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.
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)
- Defines the management environment to be NODE22 and NODE21.
- Adds SYSPRV privilege to the user's current privileges in order to write to the quota file.
- 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- Adds an entry for the rights identifier PAYROLL. Any user holding the PAYROLL identifier can use this disk space.
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: SYSPRV privilege, a system UIC, or ownership of the volume.
DISKQUOTA CREATE
None.
/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.
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
Digital 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.
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.
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.
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.
DISKQUOTA DISABLE
None.
/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.
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.
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.
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.
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.
DISKQUOTA ENABLE
None.
/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.
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
SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22) SYSMAN> DISKQUOTA ENABLE SYSMAN> DISKQUOTA REBUILD
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
6048P053.HTM OSSG Documentation 26-NOV-1996 12:43:40.36
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.