HP OpenVMS Systems Documentation

To enable autostart each time the system reboots, add the ENABLE AUTOSTART/QUEUES command to your queue startup command procedure, as shown in Example 7-2.

You must establish the logical devices LTA1 and LTA2 in the LAT startup command procedure LAT$SYSTARTUP.COM on each node on which the autostart queue can run. For more information, see the description of editing LAT$SYSTARTUP.COM in the OpenVMS System Manager's Manual.

Although the /START qualifier is specified to activate these autostart queues, they will not begin processing jobs until autostart is enabled.

In the example, these autostart queues were set up to run on one of three nodes. The queues start when the first of those nodes executes the ENABLE AUTOSTART/QUEUES command. The queue remains running as long as one of those nodes is running and has autostart enabled.

$ DEFINE/SYSTEM/EXECUTIVE SHUTDOWN$DISABLE_AUTOSTART
number-of-minutes

Set the value of number-of-minutes to the number of minutes before shutdown when autostart is to be disabled. You can add this logical name definition to SYLOGICALS.COM. The value of number-of-minutes is the default value for the node. If this number is greater than the number of minutes specified for the entire shutdown sequence, autostart is disabled at the beginning of the sequence.

• Establishes the new computer's root directory on a cluster common system disk and generates the computer's system parameter files (ALPHAVMSSYS.PAR for Alpha systems or VAXVMSSYS.PAR for VAX systems), and MODPARAMS.DAT in its SYS$SPECIFIC:[SYSEXE] directory.
• Generates the new computer's page and swap files (PAGEFILE.SYS and SWAPFILE.SYS).
• Sets up a cluster quorum disk (optional).
• Sets disk allocation class values, or port allocation class values (Alpha only), or both, with the ALLOCLASS parameter for the new computer, if the computer is being added as a disk server. If the computer is being added as a tape server, sets a tape allocation class value with the TAPE_ALLOCLASS parameter.

  Note: ALLOCLASS must be set to a value greater than zero if you are configuring an Alpha computer on a shared SCSI bus and you are not using a port allocation class.

• Generates an initial (temporary) startup procedure for the new computer. This initial procedure:
  • Runs NETCONFIG.COM to configure the network.
  • Runs AUTOGEN to set appropriate system parameter values for the computer.
  • Reboots the computer with normal startup procedures.
• If the new computer is a satellite node, the configuration procedure updates:
  • Network databases for the computer on which the configuration procedure is executed to add the new computer.
  • SYS$MANAGER:NETNODE_UPDATE.COM command procedure on the local computer (as described in Section 10.4.2).

• Deletes another computer's root directory and its contents from the local computer's system disk. If the computer being removed is a satellite, the cluster configuration command procedure updates SYS$MANAGER:NETNODE_UPDATE.COM on the local computer.
• Updates the permanent and volatile remote node network databases on the local computer.
• Removes the quorum disk.

• Enable or disable the local computer as a disk server
• Enable or disable the local computer as a boot server
• Enable or disable the Ethernet or FDDI LAN for cluster communications on the local computer
• Enable or disable a quorum disk on the local computer
• Change a satellite's Ethernet or FDDI hardware address
• Enable or disable the local computer as a tape server
• Change the local computer's ALLOCLASS or TAPE_ALLOCLASS value
• Change the local computer's shared SCSI port allocation class value
• Enable or disable MEMORY CHANNEL for node-to-node cluster communications on the local computer

Reference: See the chapter about DECdtm services in the OpenVMS System Manager's Manual for step-by-step instructions on setting up DECdtm in an OpenVMS Cluster system.

If you are not sure whether your cluster uses DECdtm services, enter this command sequence:

$ SET PROCESS /PRIVILEGES=SYSPRV

$ RUN SYS$SYSTEM:LMCP

LMCP> SHOW LOG

If your cluster does not use DECdtm services, the SHOW LOG command will display a "file not found" error message. If your cluster uses DECdtm services, it displays a list of the files that DECdtm uses to store information about transactions.

$ RUN SYS$SYSTEM:LANCP

LANCP> LIST DEVICE/MOPDLL

For nodes running DECnet for OpenVMS, enter the DCL command SHOW NETWORK to determine whether the network is up and running:

$ SHOW NETWORK

VAX/VMS Network status for local node 63.452 VIVID on 5-NOV-1994

This is a nonrouting node, and does not have any network
information.

The designated router for VIVID is node 63.1021 SATURN.

This example shows that the node VIVID is running DECnet for OpenVMS. If DECnet has not been started, the message "SHOW-I-NONET, Network Unavailable" is displayed.

For nodes running DECnet--Plus, refer to DECnet for OpenVMS Network Management Utilities for information about determining whether the DECnet--Plus network is up and running.

Follow these guidelines when selecting MOP and disk servers:

• Ensure that MOP servers have direct access to the system disk.
• Ensure that disk servers have direct access to the storage that they are serving.
• Choose the most powerful computers in the cluster. Low-powered computers can become overloaded when serving many busy satellites or when many satellites boot simultaneously. Note, however, that two or more moderately powered servers may provide better performance than a single high-powered server.
• If you have several computers of roughly comparable power, it is reasonable to use them all as boot servers. This arrangement gives optimal load balancing. In addition, if one computer fails or is shut down, others remain available to serve satellites.
• After compute power, the most important factor in selecting a server is the speed of its LAN adapter. Servers should be equipped with the highest-bandwidth LAN adapters in the cluster.

Rules: If you are adding a satellite, you must be logged into the system manager's account on a boot server. Note that the process privileges SYSPRV, OPER, CMKRNL, BYPASS, and NETMBX are required, because the procedure performs privileged system operations.

• For computers with direct access to the system disk, x is a hexadecimal digit in the range of 1 through 9 or A through D (for example, SYS1 or SYSA).
• For satellites, x must be in the range of 10 through FFFF.

If your configuration includes satellite nodes, you may realize a performance improvement by locating satellite page and swap files on a satellite's local disk, if such a disk is available. The potential for performance improvement depends on the configuration of your OpenVMS Cluster system disk and network.

To set up page and swap files on a satellite's local disk, the cluster configuration procedure creates a command procedure called SATELLITE_PAGE.COM in the satellite's [SYS n.SYSEXE] directory on the boot server's system disk. The SATELLITE_PAGE.COM procedure performs the following functions:

• Mounts the satellite's local disk with a volume label that is unique in the cluster in the format node-name_SCSSYSTEMID.

  Reference: Refer to Section 8.6.5 for information about altering the volume label.

• Installs the page and swap files on the satellite's local disk.

Note: For page and swap disks that are shadowed, you must edit the MOUNT and INIT commands in SATELLITE_PAGE.COM to the appropriate syntax for mounting any specialized "local" disks (that is, host-based shadowing disks (DS xxx), or host-based RAID disks (DP xxxx), or DECram disks (MDA xxxx)) on the newly added node. CLUSTER_CONFIG(_LAN).COM does not create the MOUNT and INIT commands required for SHADOW, RAID, or DECram disks.

Note: To relocate the satellite's page and swap files (for example, from the satellite's local disk to the boot server's system disk, or the reverse) or to change file sizes:

1. Create new PAGE and SWAP files on a shared device, as shown:

   $ MCR SYSGEN CREATE
   device:[dir] PAGEFILE.SYS/SIZE=
   block-count
   
   
   

   Note: If page and swap files will be created for a shadow set, you must edit SATELLITE_PAGE accordingly.

2. Rename the SYS$SPECIFIC:[SYSEXE]PAGEFILE.SYS and SWAPFILE.SYS files to PAGEFILE.TMP and SWAPFILE.TMP.
3. Reboot, and then delete the .TMP files.
4. Modify the SYS$MANAGER:SYPAGSWPFILES.COM procedure to load the files.

• If you are adding a computer, the network manager supplies the address.
• If you are removing a computer, use the SHOW NETWORK command (as shown in Table 8-2).

• If you are adding a computer, the network manager supplies the address.
• If you are removing a computer, use the SHOW NETWORK command (as shown in Table 8-2).

• The namespace name, ending with a colon (:). This is optional.
• The root directory, designated by a period (.).
• Zero or more hierarchical directories, designated by a character string followed by a period (.).
• The simple name, a character string that, combined with the directory names, uniquely identifies the node. For example:

  .SALES.NETWORKS.MYNODE
  MEGA:.INDIANA.JONES
  COLUMBUS:.FLATWORLD

+Full name: BIGBANG:.GALAXY.NOVA.BLACKHOLE
Synonym: BLACKH

Note: The node synonym does not need to be the same as the OpenVMS Cluster node name.

• ++On Alpha systems, enter the following command at the satellite's console:

   >>> SHOW NETWORK
  
  
  

  Note that you can also use the SHOW CONFIG command.

• +On MicroVAX II and VAXstation II satellite nodes. When the DECnet for OpenVMS network is running on a boot server, enter the following commands at the satellite's console:

   >>> B/100 XQA0
  
   Bootfile: READ_ADDR
  
  
  

• +On MicroVAX 2000 and VAXstation 2000 satellite nodes. When the DECnet for OpenVMS network is running on a boot server, enter the following commands at successive console-mode prompts:

   >>> T 53
  
   2 ?>>> 3
  
   >>> B/100 ESA0
  
   Bootfile: READ_ADDR
  
  
  

  If the second prompt appears as 3 ?>>>, press Return.

• +On MicroVAX 3 xxx and 4 xxx series satellite nodes, enter the following command at the satellite's console:

   >>> SHOW ETHERNET