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.
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.
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.
Make sure that the disk on which you want to createthe transaction log is mounted clusterwide.
Decide which directory you want to create the newtransaction log in. You may want to create a new directory for thetransaction log.
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.
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.
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.