02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Preparing a Shared Environment<br />

5.6 Coordinating Startup Command Procedures<br />

Prepare the SYSTARTUP_VMS.COM procedure as follows:<br />

Step Action<br />

1 In each computer’s SYS$SPECIFIC:[SYSMGR] directory, edit the SYSTARTUP_<br />

VMS.TEMPLATE file to set up a SYSTARTUP_VMS.COM procedure that:<br />

• Performs computer-specific startup functions such as the following:<br />

Setting up dual-ported and local disks<br />

Loading device drivers<br />

Setting up local terminals and terminal server access<br />

• Invoking the common startup procedure (described next).<br />

2 Build a common command procedure that includes startup commands that you want to be<br />

common to all computers. The common procedure might contain commands that:<br />

• Install images<br />

• Define logical names<br />

• Set up queues<br />

• Set up and mount physically accessible mass storage devices<br />

• Perform any other common startup functions<br />

Note: You might choose to build these commands into individual command procedures that<br />

are invoked from the common procedure. For example, the MSCPMOUNT.COM file in the<br />

SYS$EXAMPLES directory is a sample common command procedure that contains commands<br />

typically used to mount cluster disks. The example includes comments explaining each phase<br />

of the procedure.<br />

3 Place the common procedure in the SYS$COMMON:[SYSMGR] directory on a common system<br />

disk or other cluster-accessible disk.<br />

Important: The common procedure is usually located in the SYS$COMMON:[SYSMGR]<br />

directory on a common system disk but can reside on any disk, provided that the disk is<br />

cluster accessible and is mounted when the procedure is invoked. If you create a copy of the<br />

common procedure for each computer, you must remember to update each copy whenever you<br />

make changes.<br />

5.6.3 Combining Existing Procedures<br />

To build startup procedures for an <strong>OpenVMS</strong> <strong>Cluster</strong> system in which existing<br />

computers are to be combined, you should compare both the computer-specific<br />

SYSTARTUP_VMS and the common startup command procedures on each<br />

computer and make any adjustments required. For example, you can compare<br />

the procedures from each computer and include commands that define the same<br />

logical names in your common SYSTARTUP_VMS command procedure.<br />

After you have chosen which commands to make common, you can build the<br />

common procedures on one of the <strong>OpenVMS</strong> <strong>Cluster</strong> computers.<br />

5.6.4 Using Multiple Startup Procedures<br />

To define a multiple-environment cluster, you set up computer-specific versions<br />

of one or more system files. For example, if you want to give users larger<br />

working set quotas on URANUS, you would create a computer-specific version<br />

of SYSUAF.DAT and place that file in URANUS’s SYS$SPECIFIC:[SYSEXE]<br />

directory. That directory can be located in URANUS’s root on a common system<br />

disk or on an individual system disk that you have set up on URANUS.<br />

Preparing a Shared Environment 5–15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!