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.

Table 5–2 Alias Collisions and Outcomes<br />

Collision Type Outcome<br />

Creating a local table with same<br />

name and access mode as an<br />

existing clusterwide table<br />

Creating a clusterwide table with<br />

same name and access mode as an<br />

existing local table<br />

Creating a clusterwide table with<br />

same name and access mode as an<br />

existing clusterwide table<br />

Preparing a Shared Environment<br />

5.4 <strong>Cluster</strong>wide Logical Names<br />

New local table is not created. The condition value<br />

SS$_NORMAL is returned, which means that the<br />

service completed successfully but the logical name<br />

table already exists. The existing clusterwide table<br />

and its names on all nodes remain in effect.<br />

New clusterwide table is created. The condition<br />

value SS$_LNMCREATED is returned, which means<br />

that the logical name table was created. The local<br />

table and its names are deleted. If the clusterwide<br />

table was created with the DCL command DEFINE,<br />

a message is displayed:<br />

DCL-I-TABSUPER, previous table table_name<br />

has been superseded<br />

If the clusterwide table was created with the<br />

$CRELNT system service, $CRELNT returns the<br />

condition value: SS$_SUPERSEDE.<br />

New clusterwide table is not created. The condition<br />

value SS$_NORMAL is returned, which means that<br />

the service completed successfully but the logical<br />

name table already exists. The existing table and<br />

all its names remain in effect, regardless of the<br />

setting of the $CRELNT system service’s CREATE-IF<br />

attribute. This prevents surprise implicit deletions of<br />

existing table names from other nodes.<br />

5.4.5 Creating <strong>Cluster</strong>wide Logical Names<br />

To create a clusterwide logical name, you must have write (W) access to the<br />

table in which the logical name is to be entered, or SYSNAM privilege if you<br />

are creating clusterwide logical names only in LNM$SYSCLUSTER. Unless<br />

you specify an access mode (user, supervisor, and so on), the access mode of the<br />

logical name you create defaults to the access mode from which the name was<br />

created. If you created the name with a DCL command, the access mode defaults<br />

to supervisor mode. If you created the name with a program, the access mode<br />

typically defaults to user mode.<br />

When you create a clusterwide logical name, you must include the name of a<br />

clusterwide logical name table in the definition of the logical name. You can<br />

create clusterwide logical names by using DCL commands or with the $CRELNM<br />

system service.<br />

The following example shows how to create a clusterwide logical name in the<br />

default clusterwide logical name table, LNM$CLUSTER_TABLE, using the<br />

DEFINE command:<br />

$ DEFINE/TABLE=LNM$CLUSTER_TABLE logical-name equivalence-string<br />

To create clusterwide logical names that will reside in a clusterwide logical<br />

name table you created, you define the new clusterwide logical name with the<br />

DEFINE command, specifying your new clusterwide table’s name with the<br />

/TABLE qualifier, as shown in the following example:<br />

Preparing a Shared Environment 5–9

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

Saved successfully!

Ooh no, something went wrong!