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