skip book previous and next navigation links
go up to top of book: HP OpenVMS System Manager's Manual, Volume 2:... HP OpenVMS System Manager's Manual, Volume 2:...
go to beginning of chapter: Managing DECdtm Services Managing DECdtm Services
go to previous page: Dismounting a Disk Dismounting a Disk
go to next page: Removing a NodeRemoving a Node
end of book navigation links

Adding a Node  



For every node you add to an OpenVMS Cluster, you must create a new transaction log. This section describes how to create a transaction log for a new node.

How to Perform This Task

Before you perform this task, the new node must be configured into the cluster. For instructions on how to configure a node into a cluster, refer to OpenVMS Cluster Systems.

  1. Decide the size and location of the new node's transaction log, using the guidelines in Planning Transaction Logs. Remember that the disk must have enough contiguous space to hold the log.
  2. Make sure that the disk on which you want to create the transaction log is mounted clusterwide.
  3. Decide which directory you want to create the new transaction log in. You may want to create a new directory for the transaction log.
  4. Make sure that SYS$JOURNAL points to the directory in which you want to create the new node's transaction log. If SYS$JOURNAL does not point to this directory, use SYSMAN to redefine SYS$JOURNAL clusterwide:DO DEFINE/SYSTEM/EXECUTIVE_MODE SYS$JOURNAL dirspec[,...] where dirspec is the full specification of a directory containing one or more transaction logs. List all the directories that contain transaction logs, including the directory in which you want to create the new node's transaction log. You can list the directories in any order.
  5. If you redefined SYS$JOURNAL in step 4, edit the SYS$MANAGER:SYLOGICALS.COM command procedure to update the SYS$JOURNAL definition.

    If you created node-specific versions of SYLOGICALS.COM, edit all the versions.
  6. Create the transaction log, using LMCP's CREATE LOG command: CREATE LOG [/SIZE=size] dirspecSYSTEM$node.LM$JOURNAL where:

    size
    is the size of the transaction log in blocks. By default, the size of the transaction log is 4000 blocks.
    dirspec
    is the full specification of the directory in which you want to create the transaction log.
    node
    is the name of the new node.

Example

This example shows how to create a transaction log for a new node, whose SCSNODE name is WHITE.

In this example, the cluster members and the locations of their transaction logs are as follows:

Node Directory Containing Log
BLUE
DISK$LOG3:[LOGFILES]
RED
DISK$LOG2:[LOGFILES]

Neither node has a node-specific version of SYLOGICALS.COM.

Decide the size and location of WHITE's transaction log:

Node Size of Log (in Blocks) Disk
WHITE
5000
DUA4

Mount the disk DUA4 clusterwide:

$ MOUNT/CLUSTER/SYSTEM DUA4: LOG4
Create a directory for the transaction log:
$ CREATE/DIRECTORY DISK$LOG4:[LOGFILES]
Redefine SYS$JOURNAL:
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO DEFINE/SYSTEM/EXECUTIVE_MODE SYS$JOURNAL - 
_SYSMAN> DISK$LOG2:[LOGFILES], DISK$LOG3[LOGFILES], DISK$LOG4:[LOGFILES]
SYSMAN> EXIT
Edit the SYS$STARTUP:SYLOGICALS command procedure to update the SYS$JOURNAL definition. Then create the transaction log:
$ RUN SYS$SYSTEM:LMCP
LMCP> CREATE LOG/SIZE=5000 DISK$LOG4:[LOGFILES]SYSTEM$WHITE.LM$JOURNAL
LMCP> EXIT

go to previous page: Dismounting a Disk Dismounting a Disk
go to next page: Removing a NodeRemoving a Node