Document revision date: 19 July 1999 | |
Previous | Contents | Index |
Removes one or more records from the ALF database.Requires read (R) and write (W) access to the SYSALF database (SYS$SYSTEM:SYSALF.DAT).
ALF REMOVE device
device
Specifies the terminal name or port name whose record you want to remove from ALF. You can use wildcard characters in the terminal name or port name. For example, if you specify the device TTA*, the system removes all records that start with the string TTA. The system does not, however remove any records that start with the string <nodename>$TTA, where <nodename> is the system's SCSNODE name.If you omit either of the wildcard characters and enter a REMOVE command, SYSMAN attempts to match the device name exactly. If more than one record matches the criteria, SYSMAN returns an error message.
/USERNAME=user
Enables you to remove a record in ALF by specifying a user name rather than a terminal name or port name. You can use wildcard characters with the /USERNAME qualifier./CONFIRM
Displays a message asking you to verify that you want to remove the record./LOG
Displays each device name and user name after it has been removed from the ALF database.
The ALF REMOVE command removes one or more records from the ALF database.
#1 |
---|
SYSMAN> ALF REMOVE _TTA3: SYSMAN> ALF REMOVE /USERNAME=SMITHSON |
In this example, the first command removes the record for terminal TTA3. The second command removes all records assigned to user name SMITHSON.
#2 |
---|
SYSMAN> ALF REMOVE <nodename>$TTA* SYSMAN> ALF REMOVE *TTA* |
Both of these commands remove records that begin with the system's SCSNODE name.
#3 |
---|
SYSMAN> REMOVE TTA |
This command produces the following error message:
%SYSMAN-E-ALFWILCRDREQ, more than one record might match - Wildcard or unit number of device required.
Note
Compaq recommends that you use caution when issuing REMOVE commands from Version 6.1 or lower SYSMAN clients to Version 6.2 or higher systems.For example, the following command issued from a system running OpenVMS Version 6.1 or lower to a system running OpenVMS Version 6.2 produces no error messages and deletes all records that match FOOBAR$TTA:
SYSMAN> SET ENVIRONMENT/NODE=FOOBAR ! FOOBAR runs OpenVMS Version 6.2 %SYSMAN-I-ENV, current command environment: Individual nodes: FOOBAR Username SYSTEM will be used on nonlocal nodes SYSMAN> ALF REMOVE TTA ! Does not produce an error message SYSMAN>Note that if the same command is issued from a system running OpenVMS Version 6.1 or lower to another system running OpenVMS Version 6.1 or lower, it produces the following error message:
This is due to incorrect processing of wildcards prior to OpenVMS Version 6.2.
%SYSMAN-I-NODERR, error returned from node FOO -SMI-E-ALFNOMATCH, no records matched search criteria
Displays one or more records from the ALF database.Requires read (R) and write (W) access to the SYSALF database (SYS$SYSTEM:SYSALF.DAT).
ALF SHOW [device]
[device]
Specifies the terminal name or port name whose record you want to display. You can use wildcard characters in the terminal name or port name. Certain restrictions in wildcard matching of ALF records exist, as shown in the examples section.
/USERNAME=user
Displays the records held by the specified user. You can use wildcard characters with this qualifier./OUTPUT[=filespec]
Directs the output of the command to a file. If you do not include a file specification with this qualifier, SYSMAN writes the output to the file SYSMAN.LIS in your default directory.
The ALF SHOW command displays one or more records in the ALF database.
#1 |
---|
SYSMAN> ALF SHOW TTA* /USERNAME=MANESS /OUTPUT=ALF.TXT |
In this example, the records for all terminals named TTAx that are assigned to user MANESS are selected and directed to the file ALF.TXT.
#2 |
---|
SYSMAN> ALF SHOW TTA* |
This command displays only those records that start with the string TTA.
#3 |
---|
SYSMAN> ALF SHOW TTA |
This command displays only those records that start with the string <nodename>$TTA.
#4 |
---|
SYSMAN> ALF SHOW *TTA |
This command displays records that have device names ending with TTA.
#5 |
---|
SYSMAN> ALF SHOW *TTA* |
This command displays all records that contain the string TTA.
Transfers control from your current process (which then hibernates) to the specified process in your job.The ATTACH and SPAWN commands cannot be used if your terminal has an associated mailbox.
ATTACH [process-name]
process-name
Specifies the name of a parent process or a spawned subprocess to which control passes. The process must already exist, be part of your current job tree, and share the same input stream as your current process. However, the process cannot be your current process or a subprocess created with the /NOWAIT qualifier.Process names can contain from 1 to 15 alphanumeric characters. If a connection to the specified process cannot be made, an error message is displayed.
/PARENT
Enables you to attach to the parent process. If no parent process exists, you receive an error message.
The ATTACH command connects your input stream to another process. You can use the ATTACH command to change control from one subprocess to another subprocess or to the parent process.When you enter the ATTACH command, the parent process goes into hibernation and your input stream connects to the specified destination process. You can use the ATTACH command to connect to a subprocess that is part of a current job (left hibernating as a result of the SPAWN/WAIT command or another ATTACH command) as long as the connection is valid. No connection can be made to the current process, to a process that is not part of the current job, or to a process that does not exist. If you attempt any of these connections, you receive an error message.
You can also use the ATTACH command in conjunction with the SPAWN/WAIT command to return to a parent process without terminating the created subprocess. See the description of the SPAWN command for more details.
$ SPAWN %DCL-S-SPAWNED, process SYSTEM_1 spawned %DCL-S-ATTACHED, terminal now attached to process SYSTEM_1 $ RUN SYS$SYSTEM:SYSMAN SYSMAN> ATTACH SYSTEM %DCL-S-RETURNED, control returned to process SYSTEM $ |
In this example, the SPAWN command creates a subprocess (SYSTEM_1). After you invoke SYSMAN and enter the ATTACH command, you transfer the terminal's control back to the parent process (SYSTEM).
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, 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.
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, LOG_IO, and SYSPRV privileges, 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. 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_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-1998 13:32:19.45 System time on node NODE22: 19-JUN-1998 13:32:27.79 System time on node NODE23: 19-JUN-1998 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 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.
/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.1.2.)
#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.
Previous | Next | Contents | Index |
privacy and legal statement | ||
6048PRO_065.HTML |