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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Preparing a Shared Environment<br />

5.5 Defining and Accessing <strong>Cluster</strong>wide Logical Names<br />

5.5.3 Using Conditional Definitions for Startup Command Procedures<br />

For clusterwide definitions in any startup command procedure that is common to<br />

all cluster nodes, Compaq recommends that you use a conditional definition. For<br />

example:<br />

$ IF F$TRNLNM("CLUSTER_APPS") .EQS. "" THEN -<br />

_$ DEFINE/TABLE=LNM$SYSCLUSTER/EXEC CLUSTER_APPS -<br />

_$ $1$DKA500:[COMMON_APPS]<br />

A conditional definition can prevent unpleasant surprises. For example, suppose<br />

a system manager redefines a name that is also defined in SYSTARTUP_<br />

VMS.COM but does not edit SYSTARTUP_VMS.COM because the new definition<br />

is temporary. If a new node joins the cluster, the new node would initially<br />

receive the new definition. However, when the new node executes SYSTARTUP_<br />

VMS.COM, it will cause all the nodes in the cluster, including itself, to revert to<br />

the original value.<br />

If you include a conditional definition in SYLOGICALS.COM or<br />

SYSECURITY.COM, specify the F$TRNLNM CASE argument as INTERLOCKED<br />

to ensure that clusterwide logical names have been fully initialized before the<br />

translation completes. An example of a conditional definition with the argument<br />

specified follows:<br />

$ IF F$TRNLNM("CLUSTER_APPS",,,,"INTERLOCKED") .EQS. "" THEN -<br />

_$ DEFINE/TABLE=LNM$SYSCLUSTER/EXEC CLUSTER_APPS -<br />

_$ $1$DKA500:[COMMON_APPS]<br />

Note<br />

F$GETSYI ("CWLOGICALS") always returns a value of FALSE on a<br />

noncluster system. Procedures that are designed to run in both clustered<br />

and nonclustered environments should first determine whether they are<br />

in a cluster and, if so, then determine whether clusterwide logical names<br />

are initialized.<br />

5.6 Coordinating Startup Command Procedures<br />

Immediately after a computer boots, it runs the site-independent command<br />

procedure SYS$SYSTEM:STARTUP.COM to start up the system and control the<br />

sequence of startup events. The STARTUP.COM procedure calls a number of<br />

other startup command procedures that perform cluster-specific and node-specific<br />

tasks.<br />

The following sections describe how, by setting up appropriate cluster-specific<br />

startup command procedures and other system files, you can prepare the<br />

<strong>OpenVMS</strong> <strong>Cluster</strong> operating environment on the first installed computer before<br />

adding other computers to the cluster.<br />

Reference: See also the <strong>OpenVMS</strong> System Manager’s Manual for more<br />

information about startup command procedures.<br />

Preparing a Shared Environment 5–13

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

Saved successfully!

Ooh no, something went wrong!