Document revision date: 30 March 2001

## OpenVMS System Management Utilities Reference Manual

Previous | Contents | Index

## HELP

> Provides help on LMCP commands.

### Format

> HELP [help-topic [help-subtopic]]

### Parameter

> #### help-topic

> Specifies the command that you want help for.

> #### help-subtopic

> Specifies the parameter or qualifier that you want help for.

## 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 transaction provides a means of changing transaction states.

> The REPAIR command requires:

> - The CMKRNL privilege
> - Read and write access to the transaction log and the directory it is in

### Format

> REPAIR filespec

### Parameter

> #### filespec

> The file specification of the transaction log containing the transactions whose states you want to change.

> The REPAIR command has the following requirements:

> - The logical SYS$JOURNAL must be defined in executive mode in the system logical name table.
> - The transaction log must be in a directory pointed to by the logical SYS$JOURNAL.
> - The file type of the transaction log must be .LM$JOURNAL.

> The REPAIR command uses the following defaults:

> - If you omit the disk and directory, the REPAIR command looks for the transaction log in the directories pointed to by the logical SYS$JOURNAL.
> - If you omit the file type, the REPAIR command uses .LM$JOURNAL.

### Qualifiers

> #### /LOGID=logid

> Selects records only for transactions that have participants whose logid field matches the specified value.

> The logid is in the Log ID field, to the right of the Type field in the output from the DUMP command. The value you specify must be exactly as it appears in the display, including hyphens.

> Note that you can use this qualifier only with the /RM qualifier.

> #### /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.

> If the participant name includes undisplayable characters, you 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, the participant name is:

>     Name (11): "SYSTEM$RED" (4445 52244D45 54535953)

> The value you specify for the /RM qualifier is:

>     /RM=%X53595354454D24524544

> #### /STATE=COMMITTED
> /STATE=PREPARED

> Selects records only for transactions in either the Committed or Prepared states.

> #### /TID=transaction_id

> Selects records only for the specified transaction.

> The transaction_id is shown in the Transaction ID field in the output from the DUMP command. The value you specify must be exactly as it appears in the display, including hyphens.

### 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 transaction provides a means of changing transaction states.

> Use this command only if none of the resource managers participating in the transaction provides a means of changing the transaction state.

> Change the transaction state only when you already know the outcome of the transaction and need to manually update the 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.

> Once you have selected the transactions to change, enter the REPAIR subcommand mode. Within this mode, the prompt changes to REPAIR>, and you have an additional set of subcommands. Use these subcommands 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 be aborted by removing its record from the transaction log. This writes a record of type Forgotten for the transaction. Note that DECdtm services use the presumed abort logging protocol.
> COMMIT | Specifies that a Prepared transaction is to be committed. This writes a record of type Committed for the transaction.
> EXIT | Returns to the LMCP> prompt.
> FORGET | Specifies that a Committed transaction can be removed from the transaction log. This writes a record of type Forgotten for the transaction.
> NEXT | Displays the next transaction that matches your selection criteria.

> LMCP displays each of the selected transactions in turn, so that you can change them. For each selected transaction, you can 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.

### Example

    LMCP> REPAIR/STATE=PREPARED DISK$JOURNALS:[LOGFILES]SYSTEM$ORANGE

> In this example, transactions to be modified are selected from the transaction log for node ORANGE. The transactions selected are those in the Prepared state.

> The first transaction is committed by manually changing its state from Prepared to Committed, then the NEXT subcommand is used to advance to the next selected transaction.

>     Dump of transaction log DISK$JOURNALS:[LOGFILES]SYSTEM$ORANGE;1
>     End of file block 4002 / Allocated 4002
>     Log Version 1.0
>     Transaction log UID:   98A43B80-81B7-11CC-A27A-08002B1744C3
>     Penultimate Checkpoint: 00000407B9AC 07AC
>     Last Checkpoint:        00000407C3B7 07B7

>     Transaction state (1):  PREPARED
>     Transaction ID: 9F7DF804-CBC4-11CC-863D-08002B17450A (18-OCT-2000 16:11:03.67)
>     DECdtm Services Log Format V1.1
>     Type ( 3): LOCAL RM         Log ID: 00000000-0000-0000-0000-000000000000
>     Name (1): "B" (42)
>     Type ( 4): PARENT           Log ID: AEC2FB64-C617-11CC-B458-08002B17450A
>     Name (13): "SYSTEM$BLUE" (45554C 42244D45 54535953)
>     Type (16): PARENT NODE      Log ID: AEC2FB64-C617-11CC-B458-08002B17450A
>     Name (6): "BLUE" (45554C42))

>     REPAIR> COMMIT
>     REPAIR> NEXT
>         .
>         .
>         .

## SHOW LOG

> Displays information about transaction logs.

> Requires read access to the transaction logs and the directories they are in.

### Format

> SHOW LOG [filespec]

### Parameter

> #### filespec

> The file specification of the transaction logs you want to display information about. This can include the percent (%) and asterisk (*) wildcard characters.

> The SHOW LOG command uses the following defaults:

> - If you omit the disk and directory, the SHOW LOG command looks for the transaction log in the directories pointed to by SYS$JOURNAL, which must be defined in executive mode in the system logical name table.
> - If you omit the file type, the SHOW LOG command uses .LM$JOURNAL.

### Qualifiers

> #### /CURRENT

> Displays information about the local node's transaction log. This includes the number of checkpoints and stalls that have occurred since DECdtm services started on this node.

> To use the /CURRENT qualifier:

> - You must have the CMKRNL privilege.
> - You must omit the parameter to the SHOW LOG command.

> #### /FULL

> Lists all attributes of the transaction logs. For each transaction log, both the full file specification of the transaction log and its size are displayed.

> If you do not specify which transaction log you want to display, the SHOW LOG command lists all transaction logs of the form 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.

> #### /OUTPUT[=filespec]

> Requires read and write access to the directory in which the output file is to be created.

> Specifies where the output of the SHOW LOG command is sent. If you omit this qualifier, output is sent to the current SYS$OUTPUT device (usually your terminal). To send the output to a file, use 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.

### Example

    LMCP> SHOW LOG/FULL

> This example displays full details about the transaction logs in all directories pointed to by the logical SYS$JOURNAL. This logical is defined in executive mode in the system logical name table.

>     Directory of DISK$JOURNALS:[LOGFILES]

>     DISK$JOURNALS:[LOGFILES]SYSTEM$BLUE.LM$JOURNAL;1
>     End of file block 4002 / Allocated 4002
>     Log Version 1.0
>     Transaction log 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.0
>     Transaction log UID:   17BB9140-2674-11C9-8001-AA0004006AF8
>     Penultimate 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.0
>     Transaction log 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.

## Chapter 15
Monitor Utility

## 15.1 MONITOR Description

The Monitor utility (MONITOR) is a system management tool used to obtain information about operating system performance. MONITOR allows you to monitor classes of systemwide performance data (such as system I/O statistics, page management statistics, and time spent in each of the processor modes) at specifiable intervals, and produce several types of output.

To monitor a particular class of information, specify the class names corresponding to the information classes that you want to monitor. For example, to monitor page management statistics, specify the PAGE class name in the MONITOR command. MONITOR collects system performance data by class and produces the following three forms of optional output:

- A disk recording file in binary format
- Statistical terminal displays
- A disk file containing statistical summary information in ASCII format

The utility initiates a single MONITOR request for the classes of performance data specified each time you enter a command in the following form:

`MONITOR [/qualifier[,...]] classname[,...] [/qualifier[,...]]`

Regardless of the order in which you specify classname parameters, MONITOR always executes requests in the following sequence:

> PROCESSES
> STATES
> MODES
> PAGE
> IO
> FCP
> LOCK
> DECNET
> FILE_SYSTEM_CACHE
> DISK
> DLOCK
> SCS
> SYSTEM
> CLUSTER
> RMS
> MSCP_SERVER
> TRANSACTION
> VECTOR
> VBS (VAX Only)
> TIMER
> RLOCK

Depending on the command qualifiers specified, MONITOR collects system performance data from the running system or plays back data recorded previously in a recording file. When you play back data, you can display it, summarize it, and even rerecord it to reduce the amount of data in the recording file.

## 15.2 MONITOR Usage Summary

The Monitor utility (MONITOR) is a system management tool that enables you to obtain information about operating system performance.

### Format

> MONITOR

### Parameters

> #### None.

Usage Summary Issuing the MONITOR command from the DCL prompt invokes the Monitor utility and allows you to use any of the Monitor utility commands as follows:

    $ MONITOR
    MONITOR>

To begin monitoring a system, issue the MONITOR command MONITOR.

Generally, each MONITOR request runs until the time specified or implied by the /ENDING qualifier. To exit from MONITOR, enter the EXIT command at the MONITOR> prompt or press Ctrl/Z. To terminate a MONITOR request without exiting from the utility, press Ctrl/C.

Information collected by MONITOR is normally displayed as ASCII screen images. You can use the optional /DISPLAY qualifier to specify a disk file to contain the information. If you omit the file specification, output is directed to SYS$OUTPUT. See the MONITOR command MONITOR for a discussion of the /DISPLAY qualifier.

You can also initiate MONITOR requests from command level by entering the DCL command MONITOR with the desired qualifiers and parameters. However, in terms of conserving system resources, it is preferable to initiate requests in response to the MONITOR> prompt.

## 15.3 MONITOR Commands

This section describes and provides examples of MONITOR commands. For commands that specify classname parameters (other than ALL_CLASSES), a sample display or summary of each class is provided, with a brief description of the items in the class.

MONITOR recognizes the exclamation point (!) as a comment character. Thus, full- or partial-line comments are acceptable in command files specified as input to MONITOR.

Note that in MONITOR, rate indicates the number of occurrences per second. For example, the Page Fault rate indicates the number of page faults per second.

The following table lists the commands described in this section:

Command | Description
--- | ---
CONVERT | Converts a pre-Version 5.0 MONITOR recording file to the current format
EXECUTE (@) | Executes a series of MONITOR commands contained in a file
EXIT | Terminates MONITOR, returning control to command level
HELP | Displays information about MONITOR
INITIALIZE | Reestablishes initial default dettings for parameters and qualifiers altered by the SET DEFAULT command
MONITOR | Initiates monitoring of statistics for the classes of information you specify
SET DEFAULT | Sets command qualifier, classname parameter, and classname qualifier defaults for the MONITOR command
SHOW DEFAULT | Displays the defaults established by the SET DEFAULT command

## CONVERT

> The CONVERT command converts a pre-Version 5.0 MONITOR recording file to the current format.

### Format

> CONVERT file-spec

### Parameter

> #### file-spec

> Specifies the file to be converted. The default file specification is MONITOR.DAT.

### Qualifiers

> #### /OUTPUT

> The file specification of the converted file. The default specification is MONITOR.DAT.

### Description

> You must convert pre-Version 5.0 recording files to the current format before attempting to play them back with the current MONITOR version.

### Example

    MONITOR> CONVERT 24MAY_MONITOR.DAT/OUTPUT=24MAY_NEWMON.DAT

> This command converts the file 24MAY_MONITOR.DAT to the current format and names the output file 24MAY_NEWMON.DAT.

## EXECUTE (@)

> The EXECUTE command or the at sign (@) executes a series of MONITOR commands contained in a file.

### Format

> EXECUTE (@) file-spec

### Parameter

> #### file-spec

> Specifies a command file to be executed by the EXECUTE (@) command.

### Qualifiers

> None.

### Description

> With the EXECUTE command, you can direct MONITOR to obtain command input from a specified file rather than from the terminal. The file can contain any valid MONITOR command except an EXECUTE (@) command. Commands in the file are executed sequentially. If you omit the optional file specification, the default is MONITOR.MON.

> After the file has executed, subsequent commands are obtained from the terminal.

### Example

    MONITOR> EXECUTE INQMEM.MON
       .
       .
       .
    MONITOR> MONITOR /RECORD

> Contents of the file INQMEM.MON are as follows:

>     ! This file sets defaults for a memory management inquiry using
>     ! INTERVAL=5, PAGE, IO, and PROCESSES/TOPFAULT
>     !
>        .
>        .
>        .
>     SET DEFAULT /INTERVAL=5 PAGE, IO, PROCESSES/TOPFAULT

> In this example, appropriate default values for a memory management investigation are established in the file INQMEM.MON, and the file is executed with the EXECUTE command. Then a subsequent MONITOR command uses those defaults, adding the /RECORD qualifier, to display and record the selected classes with a 5-second interval.

> Note that the defaults established when the file INQMEM.MON is executed remain in effect until changed explicitly or until you exit from the utility.

## EXIT

> The EXIT command terminates MONITOR, returning control to command level.

### Format

> EXIT

### Parameters

> None.

### Qualifiers

> None.

## HELP

> The HELP command displays information about MONITOR.

### Format

> HELP [command]

### Parameter

> #### command

> Specifies the name of a MONITOR command for which HELP is desired.

### Qualifiers

> None.

### Example

    MONITOR> HELP MONITOR INITIALIZE

    The INITIALIZE command reestablishes initial default settings for
           parameters and qualifiers previously altered by the SET DEFAULT
           command.

> The command in this example requests help information about the INITIALIZE command.

## INITIALIZE

> The INITIALIZE command reestablishes initial default settings for parameters and qualifiers altered by the SET DEFAULT command.

### Format

> INITIALIZE

### Parameters

> None.

### Qualifiers

> None.

## MONITOR

> The MONITOR command initiates monitoring of statistics for the classes of information you specify.

### Format

> MONITOR [/command qualifier[,...]] classname[,...] [/classname qualifier[,...]]

### Parameter

> #### classname[,...]

> Specifies the class of performance data to be monitored. To monitor all classes, specify the ALL_CLASSES parameter. When you specify several classes, separate the classname parameters with commas or plus signs. You cannot specify the CLUSTER class name with any other class name. Cluster monitoring functions require that DECnet for OpenVMS be installed.

> You must specify one or more of the following parameters:

> ALL_CLASSES | Statistics for all classes
> CLUSTER | Clusterwide performance statistics
> DECNET | DECnet for OpenVMS statistics
> DISK | Disk I/O statistics
> DLOCK | Distributed lock management statistics
> FCP | File control primitive statistics
> FILE_SYSTEM_CACHE | File system cache statistics
> IO | System I/O statistics
> LOCK | Lock management statistics
> MODES | Time spent in each of the processor modes
> MSCP_SERVER | MSCP server statistics
> PAGE | Page management statistics
> PROCESSES | Statistics on all processes
> RLOCK | Dynamic lock remastering statistics
> RMS | Record Management Services statistics
> SCS | System Communications Services statistics
> STATES | Number of processes in each of the scheduler states
> SYSTEM | Summary of statistics from other classes
> TIMER | Timer Queue Entry (TQE) statistics
> TRANSACTION | DECdtm services statistics
> VBS (VAX Only) | Virtual balance slot statistics
> VECTOR | Vector processor scheduled usage

This section describes qualifiers for the MONITOR and SET DEFAULT commands. Note that these commands accept the same qualifiers. As these qualifiers follow the standard rules of DCL grammar as specified in the OpenVMS DCL Dictionary, you can abbreviate any qualifier or keyword as long as the abbreviation is not ambiguous. Use the asterisk (*) and the percent sign (%) as wildcard characters unless otherwise noted.

### Command Qualifier Descriptions

> #### /BEGINNING=time

> Specifies the time that monitoring begins, by using a combination of absolute and delta times. Observe the syntax rules for time values described in the online help topic DCL_Tips (subtopic Date_Time).

> If you are monitoring a running system, and you omit the /BEGINNING qualifier, monitoring begins when you enter the MONITOR command. However, if you have specified the /INPUT qualifier to play back data from an input recording file, /BEGINNING defaults to the beginning time recorded in the input file. If you specify /BEGINNING with a time but are playing back a recording file, MONITOR selects either the beginning time of the file or the beginning time you specify, whichever is later. If you are monitoring a remote node, the local node time is used to determine beginning time.

> If you specify a future time for a request to monitor a running system, MONITOR issues an informational message, and the process issuing the request hibernates until the specified time. This feature can be useful when you run MONITOR from a batch job.

> #### /BY_NODE

> #### /NOBY_NODE

> Specifies that performance class data in a multifile summary be displayed as a single column of AVERAGE statistics for each node.

> The /BY_NODE qualifier displays data in a multifile summary. If you specify only one input file, MONITOR ignores the /BY_NODE qualifier because you are not performing a multifile summary.

> You can specify the /BY_NODE qualifier only in combination with the /SUMMARY qualifier. One column of AVERAGE statistics per node appears for each class requested.

> By default, multifile summaries include one column of AVERAGE statistics for each node requested in each input file.

> #### /COMMENT=string

> #### /NOCOMMENT (default)

> Specifies an ASCII string to be stored in the output recording file. The string can contain up to 60 characters.

> The /COMMENT qualifier is valid only when /RECORD is also specified. (MONITOR ignores the /COMMENT qualifier if you do not use the /RECORD qualifier in the command line.) If you omit the qualifier or specify /NOCOMMENT, a string consisting of 60 blanks is stored in the recording file by default.

> Previous | Next | Contents | Index

> | privacy and legal statement |
> 6048PRO_040.HTML