/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
|
To obtain data from an incompatible remote node, record the data on the
remote node and then use the MONITOR playback feature to examine the
data on the local node. The HP OpenVMS System Manager's Manual describes remote monitoring.
If you specify multiple node names with multiple system classes,
MONITOR displays one class at a time for each node. For example, the
command MONITOR/NODE=(NODE_A,NODE_B) STATES,MODES generates STATES data
for NODE_A and NODE_B and then MODES data.
/OUTPUT=file-spec
Used with the CONVERT command, this qualifier specifies the name of the
converted recording file. The default specification is MONITOR.DAT.
File lists are not permitted.
Recording files produced using MONITOR prior to VMS Version 5.0 must be
converted to the current format before they can be played back by the
current MONITOR version.
/RECORD[=file-spec]
/NORECORD (default)
Specifies that a binary disk file be created containing all collected
data for the request. Note that recording is restricted to files on
disks. No wildcard characters are allowed in the file specification. If
you omit the file type, the default file type is .DAT. If you omit the
file specification, output is generated to a file named MONITOR.DAT in
the current default device and directory. If you specify an existing
file but omit the version number, a new version of the file is created.
The output consists of all data for the requested classes, regardless
of the classname qualifiers specified. Note that recording file output
is not produced when a multifile summary is requested.
/SUMMARY[=file-spec]
/NOSUMMARY (default)
Specifies that an ASCII disk file be created containing summary
statistics on all data collected for this request. If the optional file
specification is omitted, it defaults to MONITOR.SUM.
The summary file, generated at the end of monitoring, contains one or
more pages of output for each requested class. The format of each page
is similar to that of display output and is determined by the classname
qualifiers. The /ALL qualifier is applied to all class names for which
no other qualifier is specified.
/VIEWING_TIME=seconds
Specifies the duration for each screen image display for /DISPLAY
requests. Values can range from 1 to 9,999,999.
If you are monitoring the running system, /VIEWING_TIME defaults to the
/INTERVAL value. If you specify /INPUT, and you are monitoring a
recording file, /VIEWING_TIME defaults to 3 seconds.
Effective viewing time varies, however, depending on whether you are
running MONITOR on your local system or on a remote node.
(Remote in this context refers to the use of the SET HOST
command to access another node.) For remote access, the time required
to display the screen is included in the viewing time, while for local
access, this time is not included. Therefore, use a larger viewing time
than the 3-second default when running MONITOR on a remote system. The
value appropriate for remote access depends on your terminal baud rate.
For a 9600--baud terminal line, 6 seconds is a reasonable viewing time.
Note also that the time between full screens of data for the PROCESSES
display is controlled by this qualifier.
