LMCP$HLB.HLB  —  CREATE_LOG
    Creates a new transaction log.

                                 CAUTION

       If a node already has a transaction log, using the CREATE
       LOG command to create a new one can corrupt data.

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

    Format

      CREATE LOG  filespec

1  –  Parameter

 filespec

    The file specification of the 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 CREATE LOG command uses the following defaults:

    o  If you omit the disk and directory, the CREATE LOG command
       creates the 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 CREATE LOG command uses
       .LM$JOURNAL.

    If you specify a disk and directory not pointed to by SYS$JOURNAL
    a warning message is displayed. However, the transaction log is
    still created, but will not be used until either:

    o  SYS$JOURNAL is modified to point to the disk and directory
       where the log was created, or

    o  You move the new transaction log to a directory pointed to by
       SYS$JOURNAL.

2    /NEW_VERSION

    Forces the CREATE LOG command to create a new version of an
    existing transaction log.

                                 CAUTION

       Creating a new version of an existing transaction log can
       lead to data corruption.

       The data in the two transaction logs cannot be merged.
       Once it has started using the new transaction log, DECdtm
       services cannot access any transaction records in the old
       transaction log.

3    /OWNER

       /OWNER=uic

    Specifies the owner of the transaction log.

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

4    /SIZE

       /SIZE=size

    Specifies the size of the transaction log in blocks.

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

5  –  Example

  LMCP> CREATE LOG/SIZE=5000 DISK$LOG1:[LOGFILES]SYSTEM$ORANGE.LM$JOURNAL

      This example creates a 5000-block transaction log for node
      ORANGE in DISK$LOG1:[LOGFILES].
Close Help