HP OpenVMS System Manager's Manual, Volume 2:...

Managing DECdtm Services

Checking Whether a Transaction Log Is Too Small

Moving a Transaction Log

Changing the Size of a Transaction Log  

How to Perform This Task

Follow all the steps carefully. Taking shortcuts can lead to data corruption.

1. Log in to the node that the transaction log belongs to.
2. Find out which directory the transaction log is in, using LMCP's SHOW LOG command:SHOW LOG SYSTEM$node.LM$JOURNALwhere node is the name of the node that the transaction log belongs to.
3. Rename the transaction log: RENAME dirspecSYSTEM$node.LM$JOURNAL dirspecSYSTEM$node.LM$OLDwhere:

   dirspec	is the full specification of the directory containing the transaction log.
   node	is the name of the node that the transaction log belongs to.

   
   

4. Can you stop all the software that uses DECdtm services without shutting down any nodes?

   Yes

   Close the transaction log as follows: Step   Action a.   Stop all the software that uses DECdtm services. b.   Close the transaction log using LMCP's CLOSE LOG command: $ RUN SYS$SYSTEM:LMCP LMCP> CLOSE LOG The CLOSE LOG command closes the transaction log and stops the DECdtm TP_SERVER process. The command fails if any software is using DECdtm services. c.   Did the CLOSE LOG command succeed? Yes   Restart the TP_SERVER process: $ @SYS$STARTUP:DECDTM$STARTUP.COM No   Wait for 30 seconds, then repeat steps 4b and 4c.

   No

   Close the transaction log by rebooting the node. Log in to the node when it has rebooted.

   
   

5. Change the size of the transaction log, using LMCP's CONVERT LOG command: CONVERT LOG/SIZE=size dirspecSYSTEM$node.LM$OLD dirspecSYSTEM$node.LM$JOURNAL where:

   size	is the new size of the transaction log in blocks.
   dirspec	is the full specification of the directory containing the transaction log.
   node	is the name of the node that the transaction log belongs to.

   
   

6. If you stopped the software that uses DECdtm services in step 4, restart the software.
7. Delete the old transaction log: DELETE dirspecSYSTEM$node.LM$OLD;where:

   dirspec	is the full specification of the directory containing the old transaction log.
   node	is the name of the node that the transaction log belongs to.

   
   

Example

This example shows how to change the size of node RED's transaction log to 6000 blocks. Node RED is in an OpenVMS Cluster, and its transaction log is in DISK$LOG2:[LOGFILES].

Log in to node RED. Find out which directory RED's transaction log is in, then rename the transaction log:

$ RUN SYS$SYSTEM:LMCP
LMCP> SHOW LOG SYSTEM$RED.LM$JOURNAL

Directory of DISK$LOG2:[LOGFILES]
 
SYSTEM$RED.LM$JOURNAL;1
 
Total of 1 file.
LMCP> EXIT
 
$ RENAME DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL -
_$ DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD

$ RUN SYS$SYSTEM:LMCP
LMCP> CLOSE LOG
Transaction log closed, TP_SERVER process stopped
LMCP> EXIT

$ @ SYS$STARTUP:DECDTM$STARTUP.COM

$ RUN SYS$SYSTEM:LMCP
LMCP> CONVERT LOG/SIZE=6000 DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD -
_LMCP> DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL
Log file DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL;1 created.
Log file DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD converted.
LMCP> EXIT

Delete the old transaction log:

$ DELETE DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD;

Checking Whether a Transaction Log Is Too Small

Moving a Transaction Log