HP OpenVMS Systems Documentation

21.1 SYSMAN Description

Managing a system with SYSMAN is similar to the traditional management of an individual system because SYSMAN uses many of the same software tools. It can process most DCL commands, such as MOUNT, DEFINE, INITIALIZE, SET, and SHOW. It can also execute many OpenVMS system management utilities and command procedures, such as AUTHORIZE, AUTOGEN, and INSTALL.

SYSMAN also contains system management tools that let you perform the following tasks:

• Set disk quotas using DISKQUOTA commands.
• Load and unload licenses using LICENSE commands.
• Associate a terminal or port with a user name using the automatic login facility (ALF) commands.
• Modify or display System Generation utility (SYSGEN) parameters using PARAMETERS commands.
• Build site-specific startup procedures using STARTUP commands, which display or modify startup components of the OpenVMS operating system, site-specific programs, and layered products.
• Modify or display OpenVMS Cluster parameters using CONFIGURATION commands.
• Load system services using SYS_LOADABLE commands, which add and remove executive loaded images from the set of images loaded at boot time.
• Create and modify scheduling classes, which allow you to limit the amount of CPU time alloted to users on a system.
• On Alpha systems, detect all previously undiscovered tapes and medium changers.
• On Alpha systems, connect devices, load device drivers, and display configuration information using IO commands.
• Shut down systems using SHUTDOWN NODE command.

Instead of having to type lengthy command lines, SYSMAN enables you to define keys to execute SYSMAN commands. For example, you can define a key to execute a SET ENVIRONMENT command as follows:

SYSMAN> DEFINE/KEY/TERMINATE
_Key name: KP0
_Translation: "SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)"

Once the key is defined, you can press keypad 0, and SYSMAN executes the SET ENVIRONMENT command. Note that key definitions are lost each time that you exit from SYSMAN, unless you define them in the SYSMAN initialization file. (See Section 21.1.2 for more information about executing commands from an initialization file.)

21.1.2 Executing Commands from an Initialization File

You can create an initialization file that SYSMAN will use each time you invoke the utility. In the SYSMAN initialization file, you can perform tasks such as defining keys and setting the SYSMAN environment.

The default file specification for the SYSMAN initialization file is SYS$LOGIN:SYSMANINI.INI. If you want your SYSMAN initialization file to have a different file specification, you must define the logical name SYSMANINI to point to the location of the file.

The following example is a sample initialization file in which several keys are defined:

$ TYPE SYSMANINI.INI
DEFINE/KEY/TERMINATE KP0 "SET ENVIRONMENT/CLUSTER/NODE=(NODE21,NODE22,NODE23,NODE24)"
DEFINE/KEY/TERMINATE KP1 "CONFIGURATION SHOW TIME"
DEFINE/KEY/TERMINATE KP2 "SHOW PROFILE"
   .
   .
   .

The System Management utility (SYSMAN) centralizes system management, enabling you to manage nodes or clusters from one location.

Format

RUN SYS$SYSTEM:SYSMAN

Parameters

None.

$ RUN SYS$SYSTEM:SYSMAN

SYSMAN displays the following prompt at which you can enter SYSMAN commands using the standard rules of DCL syntax:

SYSMAN>

As an alternative, you can enter the RSX command MCR, which expands to RUN SYS$SYSTEM:

$ MCR SYSMAN

With the MCR command, you can invoke SYSMAN and supply a command in one command string. With any SYSMAN command invoked in this way (except SET ENVIRONMENT), SYSMAN executes the command string and exits. After executing a SET ENVIRONMENT command, the utility returns the SYSMAN> prompt.

To exit from SYSMAN and return to the DCL command level, enter the EXIT command at the SYSMAN> prompt or press Ctrl/Z.

This section describes the SYSMAN commands and demonstrates their use. Table 21-1 summarizes each command as follows.

Requests that SYSMAN read subsequent command input from the specific file or device.

Format

@ filespec

Parameter

filespec

Specifies either the input device or the command procedure you want to execute. The default file type is .COM. You cannot use wildcard characters in the file specification.

Description

Use the execute procedure command to execute a command procedure containing SYSMAN commands. To execute the command procedure, invoke SYSMAN, place the at sign (@) command at the beginning of a command line, then specify the file name of the command procedure.

The command procedure can contain any valid SYSMAN command.

Examples

$ CREATE ENV.COM
SET ENVIRONMENT
SHOW PROFILE[Ctrl/Z]
$ MCR SYSMAN
SYSMAN> @ENV.COM

%SYSMAN-I-DEFDIR, default directory on node -- SYS$SYSROOT:[SYSMGR]
%SYSMAN-I-DEFPRIV, default process privileges on node --
        CMKRNL
        CMEXEC
        SYSNAM
        .
        .
        .
        GRPPRV
        READALL
        SECURITY
SYSMAN>
      

This example shows how to create a command procedure that sets the SYSMAN environment to the local node, and displays the current profile. These commands execute when you enter the @ENV.COM command.

$ CREATE TIME.COM
SET ENVIRONMENT/CLUSTER
CONFIGURATION SHOW TIME[Ctrl/Z]
$ MCR SYSMAN
SYSMAN> @TIME

System time on node NODE23: 19-JUN-2000 13:32:19.45
System time on node NODE24: 19-JUN-2000 13:32:27.79
System time on node NODE25: 19-JUN-2000 13:32:58.66
      

This example shows how to create and execute a command procedure that shows the current date and time for all the nodes in the cluster.

Adds a new record to the automatic login facility (ALF) database. You can also create records for proxy accounts.

Requires read (R) and write (W) access to the SYSALF database (SYS$SYSTEM:SYSALF.DAT by default).

Format

ALF ADD device user

Parameters

device

Specifies the terminal name or port name that you want to assign to a user name. The parameter device must be a terminal name if you do not specify qualifiers on the command line, and can be either a logical name or an abbreviated device name. This parameter accepts a maximum of 63 characters, including devices for proxy accounts.

user

Specifies the user name of the account that you want to assign to a particular terminal or port.

Qualifiers

/TERMINAL (default)

Checks whether the device name you specified is a terminal on the target system. The parameter device can be a logical name or an abbreviated device name, which SYSMAN translates to a full device name.

/PORT

Checks whether the device name you specified is a valid port. If the port name contains special characters, such as a slash (/), or if it contains lowercase letters that you want to preserve, you must enclose the port name within quotation marks (" ").

Be aware that anything within quotation marks is written literally to the ALF database file. For example, if the actual port name contains uppercase letters as well as special characters, be sure to specify uppercase letters within the quotation marks. Otherwise, a mismatch will occur between the actual port name and what is specified in the SYSALF.DAT file.

/PROXY

Checks that the device name is in the NODE::USERNAME format.

/LOG

Displays the device names and user names as they are added to the ALF database.

Description

You can use the ALF ADD command to associate a terminal or port with a particular user name. This will enable certain users to log in to certain terminals or ports without specifying a user name.

The ALF ADD command adds a new record to the ALF database.

Examples

SYSMAN> ALF ADD TTA3 JBERGERON
SYSMAN> ALF ADD "MN34C3/LC-1-2" FMARTIN /PORT

      

In this example, the first command assigns terminal TTA3 to user JBERGERON. The second command assigns port MN34C3/LC-1-2 to user FMARTIN.

SYSMAN> ALF ADD VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM FOOBAR
      

In this example, VMS:.ZKO.VMSORG.SYSMAN.CLIENT1::SYSTEM is the value for the device parameter, which is assigned to FOOBAR.