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 ServicesManaging DECdtm Services
go to previous page: Dismounting a DiskDismounting 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 createa new transaction log. This section describes how to create a transactionlog for a new node.

How to Perform This Task

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

  1. Decide the sizeand location of the new node's transaction log, using the guidelinesin Planning Transaction Logs. Rememberthat the disk must have enough contiguous space to hold the log.
  2. Make sure that the disk on which you want to createthe transaction log is mounted clusterwide.
  3. Decide which directory you want to create the newtransaction log in. You may want to create a new directory for thetransaction log.
  4. Make sure that SYS$JOURNAL points to the directoryin which you want to create the new node's transaction log. If SYS$JOURNALdoes not point to this directory, use SYSMAN to redefine SYS$JOURNALclusterwide:DO DEFINE/SYSTEM/EXECUTIVE_MODE SYS$JOURNAL dirspec[,...] where dirspec is the full specification of a directory containingone or more transaction logs. List all the directories that containtransaction logs, including the directory in which you want to createthe new node's transaction log. You can list the directories inany order.
  5. If you redefined SYS$JOURNAL in step 4, edit theSYS$MANAGER:SYLOGICALS.COM command procedure to update the SYS$JOURNALdefinition.

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

    size
    is the size of the transactionlog in blocks. By default, the size of the transaction log is 4000 blocks.
    dirspec
    is the full specificationof 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 newnode, whose SCSNODE name is WHITE.

In this example, the cluster members and the locations oftheir 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:SYSMANSYSMAN> SET ENVIRONMENT/CLUSTERSYSMAN> 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 updatethe SYS$JOURNAL definition. Then create the transaction log:
$ RUN SYS$SYSTEM:LMCPLMCP> CREATE LOG/SIZE=5000 DISK$LOG4:[LOGFILES]SYSTEM$WHITE.LM$JOURNALLMCP> EXIT

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