Document revision date: 19 July 1999

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.

20.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

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

20.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

20.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.

20.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.

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.

20.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.

20.5 Using SYSMAN to Manage Security and System Time

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

Table 20-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
CONFIGURATION SET TIME	Updates system time
CONFIGURATION SHOW TIME	Displays current system time

20.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.

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

Use the CONFIGURATION SET TIME command to modify system time for nodes in an OpenVMS Cluster system, as well as for individual nodes. You can specify time values in the following format:

[dd-mmm-yyyy[:]] [hh:mm:ss.cc]

You can also enter delta time values. Refer to the OpenVMS User's Manual for more information about time formats.

In a cluster environment, SYSMAN sets the time on each node to the value you specify. However, if you do not specify a value, 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 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's hardware handbook for more information.

SYSMAN tries 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 first two examples show how to synchronize system time in a cluster.

Examples

1. The following 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:

   $ SYNCH_CLOCKS: $ RUN SYS$SYSTEM:SYSMAN SET ENVIRONMENT/CLUSTER CONFIGURATION SET TIME EXIT $ WAIT 6:00:00 $ GOTO SYNCH_CLOCKS

2. The next example sets the environment to NODE21, NODE22, and NODE23, sets privilege, and modifies the system time on all three nodes:

   SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23) SYSMAN> SET PROFILE/PRIVILEGE=LOG_IO SYSMAN> CONFIGURATION SET TIME 12:38:00

3. The following example sets the environment to cluster and displays the system time for all nodes:

   SYSMAN> SET ENVIRONMENT/CLUSTER/NODE=NODE23 SYSMAN> CONFIGURATION SHOW TIME System time on node NODE21: 19-APR-1998 13:32:19.45 System time on node NODE22: 19-APR-1998 13:32:27.79 System time on node NODE23: 19-APR-1998 13:32:58.66

The Time of Day Register (TODR), which the system uses to maintain system time, has a limit of approximately 15 months. Between January 1 and April 1, reset the system time; otherwise, the following problems might occur:

• The first time in a new year that you reboot an OpenVMS Cluster system or a node in the system, one or more nodes display any of the following system times:
  • A year in the past
  • A year in the future, which might cause passwords to expire and other difficulties
  • A correct time, but a SHOW SYSTEM command indicates that the system has been up since a time in the 1800s
• Even if you correct the system time during system boot, the following problems might remain:
  • A SHOW SYSTEM command displays an incorrect up time such as a date in the 1800s
  • The error log report (ERRLOG) shows errors for a year in the future
  • Batch jobs are waiting for a year in the future
  • Files have a creation or modification date in the future

Because the TODR has an approximate limit of 15 months, the system maintains time by combining the TODR value with a base time recorded in the base system image (SYS$LOADABLE_IMAGES:SYS.EXE). The definition of base time is:

01-JAN-CURRENT_YEAR 00:00:00.00

Because all TODRs ordinarily have the same base, multiple CPUs can boot off the same system disk, and you can use multiple system disks on one CPU; the system sets the time correctly.

When a SET TIME command is issued (with or without specifying a time), OpenVMS performs the following actions:

1. Writes the current time to the system image file
2. Resets the TODR as an offset within the current year

In an OpenVMS Cluster system (or for a node that is not part of the cluster), when you set the time, the TODR and the base time in the system image are reset with the values for the new year. However, multiple systems might share the system image. This does not normally cause a problem except after the first day of a new year.

By December, each node has a very large offset stored in the TODR (from the base time of 1-JAN of that year). When the time advances to a new year, the system image still has the old year and the TODR values are still large.

After January 1, if a SET TIME command is issued on any node (or any node is shut down using SHUTDOWN.COM), the following events occur:

1. The new year becomes the base year.
2. The system resets the TODR on that node.
3. The other nodes still have a large value in the TODR.

After these three events occur, if a node that has a large TODR crashes and rejoins the cluster, its system time is initially in the next year (applying the large TODR to the new year). This system time is recorded as the system's boot time. When the node joins the cluster, its time is set to the correct value but the boot time remains one year in the future. Certain forms of the SHOW SYSTEM command compare current time to boot time; in this instance, SHOW SYSTEM displays incorrect values.

If a system disk is used at different times by different, unclustered CPUs or if different system disks are used at different times on the same CPU, the system might incorrectly set the time to a year in the future or a year in the past, depending on how the CPU's TODR and the value recorded on the system disk become unsynchronized:

• Sharing a system disk across multiple CPUs pushes the time into the future
• Using multiple disks on one CPU pushes the time into the past

Example

The following example uses SYSMAN commands to reset the time on all nodes in an OpenVMS Cluster system:

$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/PRIVILEGE=(LOG_IO,SYSLCK) SYSMAN> CONFIGURATION SET TIME 05-JUN-1998:12:00:00 SYSMAN> EXIT

	privacy and legal statement
6017PRO_087.HTML