1 DO Executes a DCL command or DCL command procedure on all nodes in the current management environment. Requires the privileges of the DCL command being executed. Format DO [command-line] 2 Parameter command-line Specifies a command string that SYSMAN passes to the command line interface (CLI) for execution. The command DO RUN SYS$SYSTEM:SYSMAN [SYSMAN-command] is not supported. Instead, follow these steps: 1. Enter RUN SYS$SYSTEM:SYSMAN at the dollar ($) prompt. 2. At the SYSMAN> prompt, set the environment to the selected node or nodes with the SET ENVIRONMENT command. 3. Enter a SYSMAN command at the SYSMAN> prompt. For complete information about DCL command syntax, see the VSI OpenVMS DCL Dictionary. 2 Qualifiers /CONFIRM Verifies that you want to perform a DO command on each node you have specified with the SYSMAN command SET ENVIRONMENT. When you use the /CONFIRM qualifier, the system prompts you as follows: Execute command for node ? [N]: The following responses are valid: YES NO QUIT ALL TRUE FALSE 1 0 Usage Notes o Affirmative answers are YES, TRUE, and 1. o Negative answers are NO, FALSE, 0, and pressing the Return key. o You can use any combination of uppercase and lowercase letters for word responses. o You can abbreviate word responses to one or more letters (for example, T, TR, or TRU for TRUE), but these abbreviations must be unique. o Entering QUIT or pressing Ctrl/C or Ctrl/Z indicates that you want to stop processing the command at that point. o When you enter ALL, the command continues to process, but the system displays no further prompts. o If you type a response that is not valid, SYSMAN issues an error message and redisplays the prompt. /OUTPUT /OUTPUT[=filespec] Records output from the command in the specified file, which is located on the node from which you are executing SYSMAN. Position the qualifier immediately after the DO command. The default file specification is SYSMAN.LIS in the current device and directory. SYSMAN prefaces output with the message "%SYSMAN- I-OUTPUT, command execution on node xxxxxx." /PAUSE Controls the rate at which the system displays information. Using the /PAUSE qualifier causes the system to display information about one node at a time; the system prompts you to press Return when you are ready to display information about the next node. 2 Description The DO command executes the accompanying DCL command or DCL command procedure on all nodes in the current environment. Each DO command executes as an independent process, so no process context is 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 an OpenVMS 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. The system cannot display output returned from a command of more than 2048 characters without concatenation. Three exceptions to be aware of when using the DO command in clusters are the following ones: o In a multi-architecture heterogeneous cluster running OpenVMS VAX, Alpha, and Integrity servers, 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, Alpha, and Integrity server nodes. See the example sequence that follows this description for an example. o Some DCL commands, such as MOUNT/CLUSTER or SET QUORUM/CLUSTER, 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. Similarly, operations on clusterwide logical names and tables operate clusterwide by design. o Make sure that if you redefine the logical DCLTABLES, you do so in SYLOGICALS.COM, not in SYSTARTUP_VMS.COM or elsewhere. Otherwise, you will receive a command interpreter failure when executing a DO command on a remote node. 2 Examples 1.SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE21 SYSMAN> DO/OUTPUT SHOW DEVICE The first command in this example defines the management environment to be the cluster where NODE21 is a member. The second command executes a DCL command on each node in the cluster. Output goes to the file SYSMAN.LIS rather than to the terminal. 2.SYSMAN> SET ENVIRONMENT/NODE=NODE21 SYSMAN> SET PROFILE /DEFAULT=[CJ.PROGRAMS] - _SYSMAN> /PRIVILEGES=NOSYSPRV SYSMAN> DO/OUTPUT @PROCESS_INFO The commands in this example define the environment as a single node and adjust the current privileges and directory. The DO command executes the command procedure PROCESS_INFO.COM, located in directory [CJ.PROGRAMS] and writes any output to SYSMAN.LIS in the directory from which SYSMAN is running. 3.$ 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: COM_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 This example shows how you can define logical names for VAX, Alpha, and Integrity server nodes in a multi-architecture heterogeneous cluster, so that you can use the DO command to install architecture-specific images. 4.$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username STEIN will be used on nonlocal nodes SYSMAN> DO/CONFIRM SHOW TIME Execute command for node EXPERT? [N]: Y %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:28 Execute command for node MODERN? [N]: Y %SYSMAN-I-OUTPUT, command execution on node MODERN 22-MAR-2002 09:40:56 Execute command for node IMPOSE? [N]: N Execute command for node ADU26A? [N]: Y . . . The commands in this example show how to control whether the system displays time for each node in a cluster. 5.SYSMAN> DO/PAUSE SHOW TIME %SYSMAN-I-OUTPUT, command execution on node EXPERT 22-MAR-2002 09:40:13 Press return to continue %SYSMAN-I-OUTPUT, command execution on node MODER 22-MAR-2002 09:40:41 Press return to continue %SYSMAN-I-OUTPUT, command execution on node IMPOSE 22-MAR-2002 09:39:46 Press return to continue . . . . The commands in this example show how you can control the rate at which information is displayed on your system.