Document revision date: 30 March 2001

## OpenVMS System Manager's Manual

Previous | Contents | Index

#### 22.3.5.2 Modifying Field and Screen Size

To make a report fit the physical limits of the screen, you can change the width of certain fields in the report. For example, if SHOW CLUSTER provides a field width that can contain any possible value and the values your cluster generates do not require that much space, you can adjust the field width with the SET (Field) command.

SHOW CLUSTER also allows you to adjust the size of the terminal screen. If the terminal is Compaq-compatible and supports a wide report, you can set the screen to a width of up to 511 columns by specifying an appropriate value to the SET SCREEN command.

Examples

1.     Command> SET TRANSITION_TYPE/WIDTH=10

   The command in this example sets the width of the TRANSITION_TYPE field to 10, which removes the time of day from the field but leaves the date.

2.     Command> SET SCREEN=132

   The command in this example sets the screen width to 132.

Refer to the OpenVMS System Management Utilities Reference Manual for more details about using the SET (Field) and SET SCREEN commands.

#### 22.3.5.3 Moving a Report

By default, SHOW CLUSTER operates with AUTO_POSITIONING ON. This means that the utility automatically arranges the reports to take best advantage of the available display space. However, you can position reports manually with the MOVE command, which implicitly sets AUTO_POSITIONING to OFF.

If you have multiple reports in your display, you must first select the report to be repositioned. You use the SELECT window-name command to specify the report name; for example:

- SCS (the default report, which usually includes fields in the SYSTEMS and MEMBERS classes)
- CLUSTER
- LOCAL_PORTS

Note To select any report except the default SCS report, you must first add the class to the display if it is not already displayed; for example:
    Command> ADD LOCAL_PORTS

As an alternative, you can repeatedly press the Select function key or the period key on the keypad to cycle from one report to the next. The selected report appears highlighted.

How to Perform This Task

To move a report, perform either of the following actions:

- Enter MOVE commands at the command prompt.
- Use the arrow keys that you define as MOVE commands.

      Command> SET FUNCTION MOVE

  This command redefines the arrow keys as follows:

  Arrow Key | Redefinition
  --- | ---
  UP ARROW KEY | MOVE UP 1
  DOWN ARROW KEY | MOVE DOWN 1
  -> | MOVE RIGHT 1
  <- | MOVE LEFT 1

  When you enter a MOVE command, the display changes position by column (horizontally) or by line (vertically). For example, entering the command MOVE LEFT 5 moves the display 5 columns to the left. An empty frame appears around the new position of the report.
  When you are satisfied with the position of the report, enter the DESELECT command, which moves the report to the new position. Entering another SELECT command before the previous MOVE operation has been deselected also moves the report to its new position.

Example

    Command> SELECT CLUSTER
    Command> MOVE RIGHT 10
    Command> DESELECT

The following lists explains the commands in the example:

1. The SELECT command selects the CLUSTER report (which is then highlighted).
2. The MOVE command positions the report frame 10 spaces to the right.
3. The DESELECT command terminates the MOVE operation and displays the contents of the report.

For more information, refer to the SELECT, SET FUNCTION, and DESELECT commands in the OpenVMS System Management Utilities Reference Manual.

To reset the arrow keys, enter the following command:

    Command> SET FUNCTION EDIT

#### 22.3.5.4 Scrolling a Report

The SCROLL command provides a means of quickly scanning through a report without losing column headings. Scrolling scans a display by field (horizontally) and by line (vertically). The report headings remain stationary when you scroll vertically.

When the display has more than one report, you must first select a report by entering the SELECT command. The selected report is highlighted.

How to Perform This Task

To scroll a display, perform either of the following actions:

- Enter SCROLL commands at the command prompt.
- Use the arrow keys that you define as SCROLL commands.

      Command> SET FUNCTION SCROLL

  This command redefines the arrow keys as follows:

  Arrow Key | Redefinition
  --- | ---
  UP ARROW KEY | SCROLL UP 1
  DOWN ARROW KEY | SCROLL DOWN 1
  -> | SCROLL RIGHT 1
  <- | SCROLL LEFT 1

Example

    Command> SELECT SCS
    Command> SET FUNCTION SCROLL

The commands in this example first select the SCS report (which is then highlighted), and then set the arrow keys to scroll functions. Refer to the SET FUNCTION and SCROLL commands in the OpenVMS System Management Utilities Reference Manual for more information.

To reset the arrow keys, enter the following command:

    Command> SET FUNCTION EDIT

### 22.3.6 Creating a Startup Initialization File

To customize the SHOW CLUSTER display, you can create a startup initialization file, which the utility executes when you enter it. SHOW CLUSTER takes the original default display, and adds or removes whatever classes or fields you specify. The resulting display becomes your default startup format. A startup initialization file resembles the following example:

    !
    !Startup Initialization File
    !
    !
    INITIALIZE
    REMOVE MEMBERS
    ADD RP_REVISION,RP_TYPE,SYS_ID
    SET SCREEN=132

This startup procedure deletes the MEMBERS class information from the default display. The procedure also adds the RP_REVISION and RP_TYPE fields from the CIRCUITS class and the SYS_ID field from the SYSTEMS class. The last line of the procedure sets the screen size to 132 columns.

How to Perform This Task

To create an initialization file, follow these steps:

1. Define the logical name SHOW_CLUSTER$INIT as device:[directory]SHCINI before invoking SHOW CLUSTER.
   For a startup file to execute before the display begins, you must assign the logical name SHOW_CLUSTER$INIT to the initialization file; for example:

       DEFINE SHOW_CLUSTER$INIT DEVA:[JONES]SHCINI

   When invoked, SHOW CLUSTER searches for the file defined by SHOW_CLUSTER$INIT. In this example, SHOW CLUSTER looks for DEVA:[JONES]SHCINI.INI when it starts up. If the initialization file is found, SHOW CLUSTER executes the procedure before beginning the display.
   If you do not define SHOW_CLUSTER$INIT or it does not include a directory specification, SHOW CLUSTER searches the current default directory for a file named SHOW_CLUSTER.INI.
2. Customize the display using SHOW CLUSTER commands during a continuous SHOW CLUSTER session.
3. Preserve the command sequence by entering the following command:

       Command> SAVE SHOW_CLUSTER$INIT.INI

   You must specify SHOW_CLUSTER$INIT.INI, because the SAVE command creates a file with a file type of .COM by default. SHOW CLUSTER looks for an .INI file when it searches for a startup initialization file.

You can edit the file that the SAVE command creates to include comments or to improve its efficiency. For more information, refer to the SAVE command in the OpenVMS System Management Utilities Reference Manual.

Instead of having SHOW CLUSTER build an initialization file, you can build one yourself in the same way you build a command procedure. The next section provides guidelines for creating a command procedure.

### 22.3.7 Using Command Procedures Containing SHOW CLUSTER Commands

You can create command procedures that contain SHOW CLUSTER commands. Such files let you modify display characteristics without having to enter commands interactively. You can use command procedures during a continuous SHOW CLUSTER session to perform a series of commands, for example, to customize the output of the display.

The following list contains guidelines for writing command procedures that contain SHOW CLUSTER commands:

- Use any valid SHOW CLUSTER commands.
- Nest command procedures up to 16 levels deep.
- Include the SHOW CLUSTER command INITIALIZE as the first command in the file. The INITIALIZE command ensures that the report is in a known state before any commands are executed to modify it.

Notes Do not include an EXIT command at the end of the command procedure. The EXIT command terminates SHOW CLUSTER and erases the SHOW CLUSTER display before you can see it. Also, do not run SHOW CLUSTER command procedures from a batch job.

The following command procedure customizes a report display:

    !
    ! Include only the node field from the default display; show votes
    ! and quorum for each node and for the cluster as a whole.
    !
    INITIALIZE
    REMOVE SOFTWARE,STATUS
    ADD VOTES,QUORUM,CL_VOTES,CL_QUORUM

This command procedure removes the SOFTWARE and STATUS fields from the report and adds fields that provide information about the cluster quorum and votes.

To execute a command procedure during a continuous SHOW CLUSTER session, specify the execute procedure (@) command, along with the file name of the command procedure. The default file type for command procedure files is .COM.

Example

The following command executes a command procedure named SYSMOD.COM:

    Command> @SYSMOD

In this example, the default file type .COM is assumed because the file type is omitted.

For more information about creating command procedures, refer to the SAVE command in the OpenVMS System Management Utilities Reference Manual.

## 22.4 Understanding SYSMAN and OpenVMS Cluster Management

The System Management utility (SYSMAN) provides two kinds of support for OpenVMS Cluster management:

- Cluster-specific commands, CONFIGURATION SET and CONFIGURATION SHOW, that you can use to manage security data and system time in a cluster
- Access to DCL-level commands with the DO command, which gives you the ability to apply a single DCL command across an entire cluster, rather than having to enter the command on each node

Each SYSMAN command requires a specific level of privilege. For more information about each command, refer to the OpenVMS System Management Utilities Reference Manual.

## 22.5 Using SYSMAN to Manage Security

You can manage security data for an OpenVMS Cluster system with SYSMAN CONFIGURATION commands. Table 22-4 summarizes these CONFIGURATION commands and their functions.

Table 22-4 SYSMAN CONFIGURATION Commands
Command | Function
--- | ---
CONFIGURATION SET CLUSTER_AUTHORIZATION | Modifies the group number and password in a local area cluster
CONFIGURATION SHOW CLUSTER_AUTHORIZATION | Displays the group number and multicast address of a local area cluster

### 22.5.1 Modifying the Group Number and Password

The group number identifies the group of nodes in the cluster, and the associated Ethernet address is used to send messages to all nodes in the cluster. The OpenVMS Cluster password protects the integrity of the cluster membership.

Using the CONFIGURATION SET CLUSTER_AUTHORIZATION command modifies the group number and password, as recorded in SYS$SYSTEM:CLUSTER_AUTHORIZE.DAT. Normally, you do not need to alter records in the CLUSTER_AUTHORIZE.DAT file.

If your configuration has multiple system disks, SYSMAN automatically updates each copy of CLUSTER_AUTHORIZE.DAT, provided that you have defined the environment as a cluster with the SET ENVIRONMENT/CLUSTER command.

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

You cannot display the cluster password for security reasons, but you can display the group number and group multicast address with the CONFIGURATION SHOW CLUSTER_AUTHORIZATION command.

Examples

1. The following command example sets the environment to a specific cluster, sets privilege to SYSPRV, and modifies the cluster password:

       SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21
       SYSMAN> SET PROFILE/PRIVILEGE=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.

2. The following command example displays the group number and multicast address for NODE21. Because the group number and password on other nodes in the cluster are identical, no further information is displayed.

       SYSMAN> CONFIGURATION SHOW CLUSTER_AUTHORIZATION
       Node NODE21: Cluster group number 65240
       Multicast address: AB-00-04-01-F2-FF

## 22.6 Using the SYSMAN Command DO to Manage an OpenVMS Cluster

The SYSMAN command DO enables you to execute a DCL command or command procedure on all nodes in the current environment. This is convenient when you are performing routine system management tasks on nodes in the OpenVMS Cluster system, such as:

- Installing images
- Starting up software
- Checking devices
- Checking memory

Each DO command executes as an independent process, so there is no process context 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 a 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.

In a dual-architecture heterogeneous OpenVMS 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. Similarly, operations on clusterwide logical names and tables 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.

Examples

1. The following example installs an image on a cluster. First, it adds CMKRNL and SYSPRV privileges to the current privileges because they are required by INSTALL and AUTHORIZE. The DO INSTALL command installs the file STATSHR. The DO MCR AUTHORIZE command sets up an account for user Jones, specifying a password and a default device and directory.

       SYSMAN> SET PROFILE/PRIVILEGES=(CMKRNL,SYSPRV)/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]

2. The following example sets the environment to cluster and starts up a software product called XYZ on each node in the cluster:

       SYSMAN>SET ENVIRONMENT/CLUSTER
       %SYSMAN-I-ENV, Current command environment:
               Clusterwide on local cluster
               Username SMITH    will be used on nonlocal nodes
       SYSMAN> DO @SYS$STARTUP:XYZ_STARTUP

3. The following 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.

       $ 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

4. The following example shows which files are open on DISK2. You might use this if you want to dismount DISK2 and need to see which users in the cluster have files open.

       SYSMAN >SET ENVIRONMENT/CLUSTER
       %SYSMAN-I-ENV, Current command environment:
               Clusterwide on local cluster
               Username SMITH    will be used on nonlocal nodes
       SYSMAN> DO SHOW DEVICE/FILES DISK2:

       %SYSMAN-I-OUTPUT, command execution on node NODE21
       Files accessed on device $1$DIA2: (DISK2, NODE22) on 14-MAY-2000 15:44:06.05
       Process name      PID     File name
                       00000000  [000000]INDEXF.SYS;1
       %SYSMAN-I-OUTPUT, command execution on node NODE22
       Files accessed on device $1$DIA2: (DISK2, NODE21) on 14-MAY-2000 15:44:26.93
       Process name      PID     File name
                       00000000  [000000]INDEXF.SYS;1
       %SYSMAN-I-OUTPUT, command execution on node NODE23
       Files accessed on device $1$DIA2: (NODE21, NODE22) on 14-MAY-2000 15:45:01.43
       Process name      PID     File name
                       00000000  [000000]INDEXF.SYS;1
       %SYSMAN-I-OUTPUT, command execution on node NODE24
       Files accessed on device $1$DIA2: (NODE22, NODE21) on 14-MAY-2000 15:44:31.30
       Process name      PID     File name
                       00000000  [000000]INDEXF.SYS;1
       Susan Scott     21400059  [SCOTT]DECW$SM.LOG;228
       _FTA7:          214000DD  [SCOTT]CARE_SDML.TPU$JOURNAL;1
       %SYSMAN-I-OUTPUT, command execution on node NODE25
       Files accessed on device $1$DIA2: (NODE21, NODE22) on 14-MAY-2000 15:44:35.50
       Process name      PID     File name
                       00000000  [000000]INDEXF.SYS;1
       DECW$SESSION    226000E6  [SNOW]DECW$SM.LOG;6
       _FTA17:         2260009C  [SNOW.MAIL]MAIL.MAI;1
       SNOW_1          2260012F  [SNOW.MAIL]MAIL.MAI;1
       SNOW_2          22600142  [SNOW.MAIL]MAIL.MAI;1
       SNOW_3          22600143  [SNOW.MAIL]MAIL.MAI;1

5. The following example shows how much memory is available on the nodes in a cluster. You might use this if you are installing software and want to know if each node has enough memory available.

       SYSMAN > SET ENVIRONMENT/NODE=(NODE21,NODE22)
       %SYSMAN-I-ENV, Current command environment:
               Clusterwide on local cluster
               Username SMITH    will be used on nonlocal nodes
       SYSMAN>  DO SHOW MEMORY
       %SYSMAN-I-OUTPUT, command execution on node NODE21
                     System Memory Resources on 14-MAY-2000 15:59:21.61
       Physical Memory Usage (pages):     Total        Free      In Use    Modified
         Main Memory (64.00Mb)           131072       63955       65201        1916
       Slot Usage (slots):                Total        Free    Resident     Swapped
         Process Entry Slots                360         296          64           0
         Balance Set Slots                  324         262          62           0
       Fixed-Size Pool Areas (packets):   Total        Free      In Use        Size
         Small Packet (SRP) List          10568        1703        8865         128
         I/O Request Packet (IRP) List     3752         925        2827         176
         Large Packet (LRP) List            157          28         129        1856
       Dynamic Memory Usage (bytes):      Total        Free      In Use     Largest
         Nonpaged Dynamic Memory        1300480       97120     1203360       60112
         Paged Dynamic Memory           1524736      510496     1014240      505408
       Paging File Usage (pages):                      Free  Reservable       Total
         DISK$MTWAIN_SYS:[SYS0.SYSEXE]SWAPFILE.SYS
                                                      10000       10000       10000
         DISK$MTWAIN_SYS:[SYS0.SYSEXE]PAGEFILE.SYS
                                                      60502      -52278      100000
       Of the physical pages in use, 19018 pages are permanently allocated to VMS.

       %SYSMAN-I-OUTPUT, command execution on node NODE22
                     System Memory Resources on 14-MAY-2000 15:59:42.65
       Physical Memory Usage (pages):     Total        Free      In Use    Modified
         Main Memory (32.00Mb)            65536       44409       20461         666
       Slot Usage (slots):                Total        Free    Resident     Swapped
         Process Entry Slots                240         216          24           0
         Balance Set Slots                  212         190          22           0
       Fixed-Size Pool Areas (packets):   Total        Free      In Use        Size
         Small Packet (SRP) List           5080        2610        2470         128
         I/O Request Packet (IRP) List     3101        1263        1838         176
         Large Packet (LRP) List             87          60          27        1856
       Dynamic Memory Usage (bytes):      Total        Free      In Use     Largest
         Nonpaged Dynamic Memory        1165312      156256     1009056      114432
         Paged Dynamic Memory           1068032      357424      710608      352368
       Paging File Usage (pages):                      Free  Reservable       Total
         DISK$MTWAIN_SYS:[SYS1.SYSEXE]SWAPFILE.SYS
                                                      10000       10000       10000
         DISK$MTWAIN_SYS:[SYS1.SYSEXE]PAGEFILE.SYS
                                                     110591       68443      120000
       Of the physical pages in use, 9056 pages are permanently allocated to VMS.

Previous | Next | Contents | Index

| privacy and legal statement |
6017PRO_091.HTML