Using the SYSMAN Command DO to Manage an OpenVMS Cluster

If both a Table of Contents and Search form are not displayed in separate frames along with this one, you may wish to redisplay this book in a frameset, beginning with the first page.

HP OpenVMS System Manager's Manual, Volume 2:...

OpenVMS Cluster Considerations

Using SYSMAN to Manage Security

Network Considerations

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 or I64 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

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]
```

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

The following example shows how you can define logical names for VAX, Alpha, or I64 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

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

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.

Using SYSMAN to Manage Security

Network Considerations