% Librarian A09-30,-.5e CLOSE_LOG& CONVERT_LOG CREATE_LOGDUMP@HELPREPAIR&8SHOW_LOG 1 CLOSE_LOG> Closes the transaction log of the local node and stops the  TP_SERVER process.! Requires the SYSNAM privilege. Format CLOSE LOGA The CLOSE LOG command fails if the node is currently executing transactions.ww1 CONVERT_LOGD Creates a new transaction log and copies records from an existing" transaction log to the new one.B 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 theC OpenVMS System Manager's Manual for information on how to use% the CONVERT LOG command safely. Requires: o The CMKRNL privilege.C o READ access to the existing transaction log and the directory it is in.= o READ and WRITE access to the directory in which th e new' transaction log is to be created. Format+ CONVERT LOG old-filespec new-filespec 2 Parameters old-filespecB The file specification of the transaction log whose records are to be copied.7 The CONVERT LOG command uses the following defaults:A o If you omit the disk and directory, the CONVERT LOG commandA looks for the transaction log in the directories pointed toD by the logical SYS$JOURNAL, which must be defined in executi ve, mode in the system logical name table.= o If you omit the file type, the CONVERT LOG command uses .LM$JOURNAL. new-filespecC The file specification of the new transaction log to be created.@ For DECdtm services to use the transaction log, the file mustE have a name of the form SYSTEM$node.LM$JOURNAL, where node is the  name of the node.7 The CONVERT LOG command uses the following defaults:A o If you omit the disk and directory, the CONVERT  LOG command= creates the new transaction log in the first accessibleA directory pointed to by the logical SYS$JOURNAL, which mustD 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=uic2 Specifies the owner of the new transaction log.C Specify the owner using the standard UIC format, as described in the OpenVMS User's Manual. 2  /SIZE /SIZE=size; Specifies the size of the new transaction log in blocks.B The minimum size is 100 blocks. If you omit this qualifier, the? new transaction log is created with the default size of 4000 blocks. 2 ExampleD LMCP> CONVERT LOG/SIZE=6000 DISK$LOG2:[LOGFILES]SYSTEM$RED.LM$OLD -1 _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, C SYSTEM$RED.LM$OLD in directory DISK$LOG2:[LOGFILES], into the  new transaction log. ww 1 CREATE_LOG! Creates a new transaction log.' CAUTION? If a node already has a transaction log, using the CREATE7 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 2 Parameter filespec? The file specification of the transaction log to be created.@ For DECdtm services to use the transaction log, the file mustD have a name of the form SYSTEM$node.LM$JOURNAL, where node is the name of the node.6 The CREATE LOG command uses the following defaults:@ o If you omit the disk and directory, the CREATE LOG commandC creates the transaction log in the first acc essible directoryB pointed to by the logical SYS$JOURNAL, which must be defined9 in executive mode in the system logical name table.< o If you omit the file type, the CREATE LOG command uses .LM$JOURNAL.D If you specify a disk and directory not pointed to by SYS$JOURNALB a warning message is displayed. However, the transaction log is4 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, orC 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. 2 /OWNER /OWNER=uic. Specifies the owner of the transaction log.C Specify the owner using the standard UIC format, as described in$ the OpenVMS System User's Manual. 2 /SIZE /SIZE=size7 Specifies the size of the transaction log in blocks.B The minimum size is 100 blocks. If you omit this qualifier, theC transaction log is created with the default size of 4000 blocks. 2 ExampleH 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]. ww1 DUMP. Displays the contents of a transaction log.C Requires READ access to the transaction log and the directory it is in. Format DUMP filespec 2 Parameter filespecC The file specification of the transaction log whose contents you want to display.0 The DUMP command uses the following defaults:@ o If you omit the disk and directory, the DUMP command looksB for the transaction log in the directories pointed to by theB logical SYS$JOURNAL, which must be defined in executive mode' in the system logical name table.C o If you omit the file type, the DUMP command uses .LM$JOURNAL. 2 /ACTIVEB Selects records only for active transactions that have not yet  been forgotten. 2 /FORMAT /FORMAT (default) /NOFORMAT= Determines whether the contents of the transaction log areA displayed as formatted records. Specify both the /NOFORMAT andA the /HEX qualifiers to display the contents of the transaction log in hexadecimal only.; If the /NOFORMAT qualifier is specified without the /HEX; qualifier, only the transaction log header is displayed. 2 /HEX /HEX /NOHEX (default)C Specifies that the contents of the transaction log are displayedC as both ASCII characters and hexadecimal longwords. Specify bothC the /NOFORMAT and /HEX qualifiers to display the contents of the' transaction log in hexadecimal only. 2 /LOGID /LOGID=logid@ Selects records only for transactions that have participants 1 whose logid field matches the specified value.= The logid is in the Log ID field, to the right of the Type@ field. The value you specify must be exactly as it appears in" the display, including hyphens.D Note that you can use this qualifier only with the /RM qualifier. 2 /OUTPUT /OUTPUT[=filespec]? Requires READ and WRITE access to the directory in which the output file is to be created.C Specifies where the output from the DUMP command is sent. If you@ omit this qualifier, output is sent to the current SYS$OUTPUTD device (usually your terminal). To send the output to a file, useD the /OUTPUT qualifier. If you do not supply a file specification,? the output is sent to the file LMCP_DUMP.LIS in your default directory. 2 /RM /RM=name? Selects records only for transactions that have participants. whose names begin with the specified value.D The participant name is shown in the Name field, and is output in both ASCII and hexadecimal.A If the participant name includes undisplayable characters, youC can select records for that participant by using the hexadecimal< form of its name. When specifying the hexadecimal form of> the name, you must convert it by reversing the pairs in the? hexadecimal number. For example, if the participant name is:3 Name (11): "SYSTEM$RED" (4445 52244D45 54535953)2 the value you specify for the /RM qualifier is: /RM=%X53595354454D24524544 2 /STATE /STATE=COMMITTED /STATE=PREPAREDC Selects records only for transactions in either the Committed or Prepared states. 2 /TID /TID=transaction_id6 Selects records only for the specified transaction.? The transaction_id is shown in the Transaction ID field. TheB value you specify must be exactly as it appears in the display, including hyphens. 2 Example9 LMCP> DUMP/RM="RMS$" DISK$LOGFILE:SYSTEM$BLUE.LM$JOURNALB This example displays the contents of the transaction log for5 node BLUE, selecting only transactions in which 1  RMS Journaling for OpenVMS is participating. ww1 HELP Gives help on LMCP commands. Format' HELP [help-topic [help-subtopic]]ww 1 REPAIR% Changes the state of transactions.' CAUTION> The REPAIR command can corrupt data. Use it only if none? of the resource managers participating in the transaction6 provides a means of changing transaction states. Requires: o The CMKRNL privilege.D o READ and WRITE access to the transaction log and the directory it is in. Format REPAIR filespec 2 Parameter filespec? The file specification of the transaction log containing the0 transactions whose states you want to change.- The REPAIR command requires the following:B o The logical SYS$JOURNAL must be defined in executive mode in$ the system logical name table.B o The transaction log must be in a directory pointed to by the logical SYS$JOURNAL.? o The file type of the transaction log must be .LM$JOURNAL.2 The REPAIR command uses the following defaults:B o If you omit the disk and directory, the REPAIR command looksB for the transaction log in the directories pointed to by the logical SYS$JOURNAL.8 o If you omit the file type, the REPAIR command uses .LM$JOURNAL. 2 /LOGID /LOGID=logid@ Selects records only for transactions that have participants + whose logid matches the specified value.C The logid is in the Log ID field, to the right of the Type fieldB in the output from the DUMP command. The value you specify must> be exactly as it appears in the display, including hyphens.D Note that you can use this qualifier only with the /RM qualifier. 2 /RM /RM=name? Selects records only for transactions that have participants. whose names begin with the specified value. @ The participant name is shown in the Name field in the output: from DUMP, and is output in both ASCII and hexadecimal.A If the participant name includes undisplayable characters, youC can select records for that participant by using the hexadecimal< form of its name. When specifying the hexadecimal form of> the name, you must convert it by reversing the pairs in the? hexadecimal number. For example, if the participant name is:3 Name (11): "SYSTEM$RED" (4445 52244D45  54535953)2 the value you specify for the /RM qualifier is: /RM=%X53595354454D24524544 2 /STATE /STATE=COMMITTED /STATE=PREPAREDC Selects records only for transactions in either the Committed or Prepared states. 2 /TID /TID=transaction_id6 Selects records only for the specified transaction.A The transaction_id is shown in the Transaction ID field in the> output from the DUMP command. The value you specify must be; exa!ctly as it appears in the display, including hyphens. 2 Description> Use the REPAIR command to change the state of transactions.' CAUTION> The REPAIR command can corrupt data. Use it only if none? of the resource managers participating in the transaction6 provides a means of changing transaction states.9 Use this command only if none of the resource managers@ participating in the transaction provides a means of changingA t "he transaction state. For example, if Rdb is a participant inC the transaction, do not use REPAIR; use the Rdb Management (RMU)A utility commands instead. Similarly, if DBMS is a participant,4 use the Database Operator (DBO) utility commands.> Change the transaction state only when you already know the= outcome of the transaction and need to manually update theB transaction log immediately. You might want to do this because,@ for example, you have lost the network link to a #remote node.@ When you use the REPAIR command you use qualifiers to specify@ which transactions you want to change. By default, the REPAIR$ command selects all transactions.C Once you have selected the transactions to change, you enter theB REPAIR subcommand mode. Within this mode, the prompt changes toA REPAIR> and you have a set of additional subcommands described? in Subcommands of the REPAIR Command. You use these commands= either to manually change the state of the $transaction, or= to select the next transaction that matches your selection- criteria. The subcommands are as follows: Subcommand Action= ABORT Specifies that a Prepared transaction is to beB aborted by removing its record from the transactionB log. This writes a record of type Forgotten for the transaction.? Note that DECdtm services use the presumed abort logging protocol.= COMMIT Spe %cifies that a Prepared transaction is to be@ committed. This writes a record of type Committed# for the transaction.+ EXIT Returns to the LMCP> prompt.D FORGET Specifies that a Committed transaction can be removed@ from the transaction log. This writes a record of2 type Forgotten for the transaction.> NEXT Displays the next transaction that matches your" selection criteria.C LMCP displays eac&h of the selected transactions in turn, so that> you can change them. For each selected transaction, you canA either use the ABORT, COMMIT, and FORGET subcommands to change> the state of the transaction, or use the NEXT subcommand to select the next transaction.: To exit from the REPAIR subcommand mode, enter the EXIT subcommand or press Ctrl/Z. 2 ExampleL LMCP> REPAIR/STATE=PREPARED/RM="RMS$" DISK$JOURNALS:[LOGFILES]SYSTEM$ORANGEB In this example transaction's to be modified are selected fromC the transaction log for node ORANGE. The transactions selected9 are those that match both of the following criteria:G o RMS Journaling for OpenVMS is participating in the transaction.1 o The transaction is in the Prepared state. ww 1 SHOW_LOG/ Displays information about transaction logs.C Requires READ access to the transaction logs and the directories they are in. Format SHOW (LOG [filespec] 2 Parameter filespec= The file specification of the transaction logs you want toB display information about. This can include the percent (%) and$ asterisk (*) wildcard characters.4 The SHOW LOG command uses the following defaults:> o If you omit the disk and directory, the SHOW LOG commandA looks for the transaction log in the directories pointed toD by SYS$JOURNAL, which must be defined in executive mode in the system logical) name table.: o If you omit the file type, the SHOW LOG command uses .LM$JOURNAL. 2 /CURRENTD Displays information about the local node's transaction log. ThisC includes the number of checkpoints and stalls that have occurred. since DECdtm services started on this node.! To use the /CURRENT qualifier:) o You must have the CMKRNL privilege. : o You must omit the parameter to the SHOW LOG command. 2 /FULL9 Lists all attributes of the t*ransaction logs. For each; transaction log, both the full file specification of the. transaction log and its size are displayed.C If you do not specify which transaction log you want to display,> the SHOW LOG command lists all transaction logs of the formD SYSTEM$*.LM$JOURNAL, in all directories pointed to by the logical> SYS$JOURNAL, which must be defined in executive mode in the system logical name table. 2 /OUTPUT /OUTPUT[=filespec]? Requires READ a+nd WRITE access to the directory in which the output file is to be created.A Specifies where the output of the SHOW LOG command is sent. IfD you omit this qualifier, output is sent to the current SYS$OUTPUTD device (usually your terminal). To send the output to a file, useD the /OUTPUT qualifier. If you do not supply a file specification,? the output is sent to the file LMCP_SHOW.LIS in your default directory. 2 Example LMCP> SHOW LOG/FULL& Directory of DISK,$JOURNALS:[LOGFILES]1 DISK$JOURNALS:[LOGFILES]SYSTEM$BLUE.LM$JOURNAL;1( End of file block 4002 / Allocated 4002 Log Version 1.05 Log File UID: 647327A0-2674-11C9-8001-AA00040069F8* Penultimate Checkpoint: 000000001A39 0039* Last Checkpoint: 000000001C8A 008A Total of 1 file.! Directory of DISK$RED:[LOGFILES]+ DISK$RED:[LOGFILES]SYSTEM$RED.LM$JOURNAL;1( End of file block 4002 / Allocated 4002 Log Version 1.05 Log File UID: 17BB9140-2674-11C9-8001-AA0004006AF8* P-enultimate Checkpoint: 000000ECADE5 41E5* Last Checkpoint: 000000F1O5FC 41FC Total of 1 file." Directory of DISK$LOGFILES:[LOGS]/ DISK$LOGFILES:[LOGS]SYSTEM$YELLOW.LM$JOURNAL;1( End of file block 1002 / Allocated 1002 Log Version 1.05 Log File UID: 590DAA40-2640-11C9-B77A-08002B14179F* Penultimate Checkpoint: 00000C8B4819 2019* Last Checkpoint: 00000C8BC15B 335B Total of 1 file.# Total of 3 files in 3 directories.B This example displays full details about the transaction logsC in all directories pointed to by the logical SYS$JOURNAL. ThisD logical is defined in executive mode in the system logical name table.ww