Creates a new transaction log and copies records from an existing
    transaction log to the new one.

    Use the CONVERT LOG command when you want to move a transaction
    log or change its size.

                                 CAUTION

       If a node already has a transaction log, using the CONVERT
       LOG command to create a new one can corrupt data. See the
       OpenVMS System Manager's Manual for information on how to use
       the CONVERT LOG command safely.

    Requires:

    o  The CMKRNL privilege.

    o  READ access to the existing transaction log and the directory
       it is in.

    o  READ and WRITE access to the directory in which the new
       transaction log is to be created.

    Format

      CONVERT LOG  old-filespec new-filespec

1  –  Parameters

 old-filespec

    The file specification of the transaction log whose records are
    to be copied.

    The CONVERT LOG command uses the following defaults:

    o  If you omit the disk and directory, the CONVERT LOG command
       looks for the transaction log in the directories pointed to
       by the logical SYS$JOURNAL, which must be defined in executive
       mode in the system logical name table.

    o  If you omit the file type, the CONVERT LOG command uses
       .LM$JOURNAL.

 new-filespec

    The file specification of the new transaction log to be created.

    For DECdtm services to use the transaction log, the file must
    have a name of the form SYSTEM$node.LM$JOURNAL, where node is the
    name of the node.

    The CONVERT LOG command uses the following defaults:

    o  If you omit the disk and directory, the CONVERT LOG command
       creates the new transaction log in the first accessible
       directory pointed to by the logical SYS$JOURNAL, which must
       be defined in executive mode in the system logical name table.

    o  If you omit the file type, the CONVERT LOG command uses
       .LM$JOURNAL.

2    /OWNER

       /OWNER=uic

    Specifies the owner of the new transaction log.

    Specify the owner using the standard UIC format, as described in
    the OpenVMS User's Manual.

3    /SIZE

       /SIZE=size

    Specifies the size of the new transaction log in blocks.

    The minimum size is 100 blocks. If you omit this qualifier, the
    new transaction log is created with the default size of 4000
    blocks.

4  –  Example

  LMCP> CONVERT LOG/SIZE=6000 DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD -
  _LMCP> DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$JOURNAL

      This example creates a 6000-block transaction log called
      SYSTEM$RED.LM$JOURNAL in directory DISK$LOG2:[LOGFILES].
      It then copies records from the existing transaction log,
      SYSTEM$RED.LM$OLD in directory DISK$LOG2:[LOGFILES], into the
      new transaction log.