Document revision date: 19 July 1999

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.

15.1 MONITOR Description

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)

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

Format

MONITOR

Parameters

None.

$ 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.

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.

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

Format

EXIT

Parameters

None.

Qualifiers

None.

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.

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

Format

INITIALIZE

Parameters

None.

Qualifiers

None.

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
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
TRANSACTION	DECdtm services statistics
VBS (VAX Only)	Virtual balance slot statistics
VECTOR	Vector processor scheduled usage

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.

When a recording file containing a comment is played back, the comment is included in the heading of the display or single-file summary. Note that comment text is not displayed on playback for the CLUSTER class unless either the /SUMMARY or the /ALL qualifier is also used.

/DISPLAY[=file-spec] (default)

/NODISPLAY

Specifies whether information collected by MONITOR is to be displayed as ASCII screen images. Optionally names the disk file to contain the output.

If you omit the optional file specification, output is written to SYS$OUTPUT.

Note that although display output is produced by default, display output is never produced when a multifile summary is requested.

/ENDING=time

Specifies the time that monitoring ends, 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 omit the /ENDING qualifier, monitoring continues until you terminate the request with Ctrl/C or Ctrl/Z. If you have also specified the /INPUT qualifier to play back data from an input recording file, /ENDING defaults to the ending time recorded in the input file. If you specify /ENDING with a time, but are playing back a recording file, MONITOR selects the earlier of the ending time of the file and the ending time you specify. For live requests, the local node's time-stamp is used to determine ending time.

You can prematurely terminate a request, regardless of the value of the /ENDING qualifier, by pressing Ctrl/C or Ctrl/Z. To prematurely terminate a request running in a noninteractive process (that is, a batch job or a detached process or subprocess), enter the appropriate DCL command to terminate the process.

/FLUSH_INTERVAL=seconds

Specifies the interval, in seconds, at which data collected by MONITOR (contents of MONITOR buffers) is written to disk. Values must be in the range from 1 to 9,999. The default interval is 300 seconds.

If you are writing data to a shared recording file currently in use, specify a short interval to ensure that others accessing the file receive data that is as current as possible. The smaller the interval, the less data is lost if a system failure occurs while recording.

/INPUT[=(file-spec,...)]

/NOINPUT (default)

Controls whether performance data is played back from one or more input files or collected from the running system. If you specify more than one file, enclose the list in parentheses, and separate the file specifications with commas. Wildcard characters are allowed in the file specification.

Caution Data in all files in the list must have been collected by the same OpenVMS version.

With multiple input files, you must use the /SUMMARY qualifier. The maximum number of files MONITOR accepts for a multifile summary is 5000. In a multifile summary request, the classes CLUSTER and PROCESSES are ignored. If these classes are the only classes specified on the command line, MONITOR does not recognize them and displays a "no classes specified" error message.

In a list of input files, any omitted segment of the file specification (name or type) is defaulted to the corresponding segment of the previous file specification.

If you omit the file type, and you have not specified the file type previously in an input file list, the default file type .DAT is used. If you omit the file specification, MONITOR assigns the default file name MONITOR.DAT. The current device and directory defaults are applied.

If you omit the qualifier, performance data is collected from the running system.

/INTERVAL=seconds

Specifies the sampling interval between data collection events, recording events, and display events. Values can range from 1 to 9,999,999.

Collection events, recording events, and display events occur within a MONITOR request. Use the /INTERVAL qualifier to control the frequency of these events. A collection event causes raw data for all requested classes to be collected from the operating system or from a previously recorded file. A recording event causes data for all requested classes to be written to a recording file. A display event causes a screen image to be composed, for a single class, from the accumulated data collected for that class since the beginning of the MONITOR request.

For live collection requests, a collection event is always followed immediately by a recording event (if requested). The frequency of collection/recording event pairs is controlled by the /INTERVAL qualifier, which specifies the number of seconds that must elapse between occurrences of the event pair. Display events occur asynchronously to collection/recording event pairs at a frequency governed by the /VIEWING_TIME qualifier.

For playback requests, a collection event occurs each time a new interval is encountered in the input file of previously recorded data. A recording event (if requested) does not necessarily follow immediately as it does in live collection. Its frequency is still governed by the /INTERVAL qualifier; the specified /INTERVAL value is interpreted in terms of the /INTERVAL value specified when the input file was created. The new value must be an integral multiple of the original value. A recording event is then triggered every time an interval is encountered in the input file that is the appropriate multiple of the original interval. For playback requests, occurrences of display events (if requested) are indicated in exactly the same way as recording events (with the /INTERVAL qualifier) and immediately follow recording events (if both are specified). The actual length of time a displayed image remains on the screen is still specified with the /VIEWING_TIME qualifier, but, unlike the live collection case, this qualifier is not used to signal a display event. The following table summarizes which qualifiers cause the various MONITOR events.

Event	Live Collection Qualifier	Playback Qualifier
Collection	/INTERVAL	Original /INTERVAL value (from file)
Recording	/INTERVAL	/INTERVAL
Display	/VIEWING_TIME	/INTERVAL

Note that, for live requests, the collection interval is defined as the number of seconds from the end of one collection event to the beginning of the next. A collection event includes collection for all requested classes on all nodes specified. (For multiple-node requests, a collection event must complete on all nodes before a new event is initiated.) Therefore, the elapsed time from the beginning of one collection event to the beginning of the next is the interval value plus the time it takes to do the collection. For some requests, notably those including many classes or the PROCESSES, RMS, CLUSTER, or SYSTEM classes, collection time can be significant.

For /INPUT requests, the interval value defaults to the value specified in the input recording file. The default for monitoring the running system is 3 seconds for all classes except ALL_CLASSES, CLUSTER, and SYSTEM, which have a default of 6 seconds.

/NODE=(nodename,...)

Specifies the nodes (up to 48 in a cluster) for which data is to be collected. If you specify more than one name, separate the names with commas, and enclose the list in parentheses.

Remote monitoring in an OpenVMS Cluster environment might not be compatible for nodes that are running different OpenVMS versions. The following table shows the compatibility of versions for remote monitoring.

	OpenVMS Alpha and VAX Version 6.0 and later	OpenVMS Alpha Version 1.5 and VAX Version 5.n
OpenVMS Alpha and VAX Version 6.0 or later	Yes	No
OpenVMS Alpha Version 1.5 and VAX Version 5. n	No	Yes

---

Previous

Next

Contents

Index

	privacy and legal statement
6048PRO_040.HTML