Document revision date: 19 July 1999

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

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)

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)

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

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.

MONITOR ALL_CLASSES

The MONITOR ALL_CLASSES command initiates monitoring of statistics for all classes except the CLUSTER and RMS classes.

Format

MONITOR ALL_CLASSES

Command Qualifiers

/qualifier[,...]

One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL

Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.

/AVERAGE

Selects average statistics to be displayed in a bar graph for display and summary output.

/CURRENT

Selects current statistics to be displayed in a bar graph for display and summary output. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.

/MAXIMUM

Selects maximum statistics to be displayed in a bar graph for display and summary output.

/MINIMUM

Selects minimum statistics to be displayed in a bar graph for display and summary output.

Description

If you do not specify any qualifiers with the ALL_CLASSES parameter, normal default output is produced for each class. The qualifiers have no effect on display of the PROCESSES class.

Note that the default interval is 6 seconds.

The MONITOR ALL_CLASSES command is particularly useful for playback of recording files because it eliminates the need to specify the particular classes of performance data the recording file contains. To override any of the default qualifiers, specify the class name with the qualifier after specifying ALL_CLASSES.

Example

MONITOR> MONITOR/INPUT=SYS$MANAGER:LOADBAL.DAT ALL_CLASSES,PROCESSES/TOPCPU
      

This command initiates playback of the recording file SYS$MANAGER:LOADBAL.DAT. All data contained in the file will be displayed.

The MONITOR CLUSTER command initiates monitoring of the CLUSTER statistics class, which shows clusterwide CPU, memory, disk, and locking activity.

Format

MONITOR CLUSTER

Command Qualifiers

/qualifier[,...]

One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL

Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.

/AVERAGE

Selects average statistics to be displayed in a bar graph for display and summary output.

/CURRENT

Selects current statistics to be displayed in a bar graph for display and summary output. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.

/MAXIMUM

Selects maximum statistics to be displayed in a bar graph for display and summary output.

/MINIMUM

Selects minimum statistics to be displayed in a bar graph for display and summary output.

Description

For the CLUSTER class, MONITOR collects data items for up to 48 nodes in a cluster. Because this class combines the most significant clusterwide performance statistics in a single display, it is particularly useful to cluster managers and other users seeking an overview of cluster activity.

MONITOR does not recognize nodes that enter the cluster while a request is active. MONITOR, therefore, does not collect data for these nodes.

You cannot specify the CLUSTER class in the same request with any other class.

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. MONITOR does not recognize these classes if they are the only classes specified on the command line, and displays a "no classes specified" error message.

The CLUSTER class includes the following data items:

• CPU Busy---Percentage of CPU in use; includes activity in all processor modes (except Idle Time) for each node.
• Percent Memory In Use---Memory in use on each node; calculated by dividing the Free List Size by total available memory and subtracting the result from 100%.
• I/O Operation Rate---Total rate of disk I/O operations on each disk by all nodes currently active in the request.
  In cluster configurations, the MSCP server software makes locally attached and HSC disks available to other nodes. A node uses remote access to a disk when it accesses the disk through another VAX node (using the MSCP server). A node uses direct access to a disk when it directly accesses a locally attached or HSC disk.
  An "R" following the device name indicates that the displayed statistics represent I/O operations requested by nodes using remote access.
  If an "R" does not appear after the device name, the displayed statistics represent I/O operations issued by nodes with direct access. These I/O operations might include those issued by the MSCP server on behalf of remote requests.
• Total ENQ/DEQ Rate---Sum of all local, incoming, and outgoing ENQs, DEQs, and conversions.

Two display formats are provided, depending on the classname qualifier specified:

• A tabular style format for the /ALL qualifier
• A bar graph style format for the /AVERAGE, /CURRENT, /MAXIMUM, and /MINIMUM qualifiers

Note to Cluster Managers on MONITOR_SERVER Process

When users enter the MONITOR CLUSTER command, MONITOR activates the image SYS$SYSTEM:VPM.EXE, which creates a process called MONITOR_SERVER on each active cluster node. (If users specify the /NODE qualifier with the MONITOR CLUSTER command or with any command of the form MONITOR class name, MONITOR creates the process only on the specified nodes.) The server process gathers data from remote nodes for live display or to record on the local node. To ensure accurate and timely data collection, the process is started at priority 15. Because server processes consume minimal resources, they have no significant effect on system performance.

By default, MONITOR_SERVER processes are started in the system DECnet account, which is created when the NETCONFIG.COM command procedure executes at bootstrap time. If this account is not present on your system, you must either create it by executing NETCONFIG.COM, or specify another account in which the server processes can be started.

If you want to start the processes in another account, use the following sequence of commands to define VPM as known object 51 in the DECnet database and associate the object with the desired account:

$ SET PROCESS/PRIVILEGE=SYSPRV $ RUN SYS$SYSTEM:NCP NCP> DEFINE OBJECT VPM NUMBER 51 - _ FILE SYS$SYSTEM:VPM.EXE - _ PROXY NONE - _ ACCOUNT account - _ USER user-id - _ PASSWORD password NCP> SET OBJECT VPM NUMBER 51 - _ FILE SYS$SYSTEM:VPM.EXE - _ PROXY NONE - _ ACCOUNT account - _ USERNAME user-id - _ PASSWORD password NCP> EXIT $ SET PROCESS/PRIVILEGE=NOSYSPRV

For each server process, MONITOR creates a log file on the local node to which information about server connection activity, including error messages, is written. Note that error messages are written to the file only when errors occur. A single version is maintained for the life of the system. The default file specification has the form SYS$COMMON:[SYSMGR]VPM$nodename.LOG. The node name portion of the specification identifies the node on which the MONITOR_SERVER process has been started.

If you want to change the default specification, you can redefine the executive-mode logical name VPM$LOG_FILE in the system logical name table on the appropriate nodes. For example, if you wanted to write server error logging data to the file WRKD:[MONSERVER]VPM_ERRORS.LOG, you would define VPM$LOG_FILE as follows:

$ DEFINE/SYSTEM/EXECUTIVE_MODE VPM$LOG_FILE - _$ WRKD:[MONSERVER]VPM_ERRORS.LOG

To direct to a single file data for all MONITOR_SERVER processes on the cluster, you could assign the logical name the same value on each member system. Note that because the log files are created as shared sequential files, multiple server processes can access them simultaneously.

If you routinely monitor your cluster, you can reduce server startup time significantly by creating MONITOR_SERVER processes on each member node at bootstrap time and maintaining the processes for the life of the system. To do so, add the following lines to the appropriate site-independent startup command files:

$ DEFINE/SYSTEM/EXECUTIVE_MODE VPM$SERVER_LIVE TRUE $ RUN/DETACH/PAGE_FILE=10000 SYS$SYSTEM:VPM.EXE

You can enter these commands interactively at any time if you have the following privileges: ALTPRI, NETMBX, PSWAPM, SYSNAM, SYSPRV, and TMPMBX.

Example

MONITOR> MONITOR CLUSTER/ALL
 
 



  

    

      

      
 
  
 
  
                            OpenVMS Monitor Utility 
                               CLUSTER STATISTICS 
                                 on node CURLEY 
                              29-APR-1998 12:25:13 
 
CPU Busy                                   CUR        AVE        MIN        MAX 
 
LARRY                                   100.00     100.00     100.00     100.00 
CURLEY                                  100.00      99.83     100.00     100.00 
MOE                                       8.52       8.50       8.52       8.52 
 
                            OpenVMS Monitor Utility 
                               CLUSTER STATISTICS 
                                 on node CURLEY 
                              29-APR-1998 12:25:19 
%Memory In Use                             CUR        AVE        MIN        MAX 
 
MOE                                      88.00      88.00      88.00      88.00 
LARRY                                    78.00      78.00      77.00      78.00 
CURLEY                                   72.00      72.50      72.00      72.00 
 
 
                            OpenVMS Monitor Utility 
                               CLUSTER STATISTICS 
                                 on node CURLEY 
                              29-APR-1998 12:25:25 
 
I/O Operation Rate                         CUR        AVE        MIN        MAX 
 
$111$DUA7:   (DECEIT) SQMCLUSTERV4        0.48       6.53       0.48      10.41 
$111$DUA6:   (DECEIT) QUALD               1.93       1.07       0.00       1.93 
$111$DUA4:   (DECEIT) PAGESWAPDISK        1.44       0.96       0.00       1.44 
$111$DUA2:   (DECEIT) TSDPERF             0.32       0.53       0.16       1.12 
LARRY$DRA3:           QUALQUEST           0.00       0.21       0.00       0.64 
MOE$DMA1:             UVMSQAR             0.00       0.00       0.00       0.00 
MOE$DRA5:             USER01              0.00       0.00       0.00       0.00 
LARRY$DRA4:           TIMEDEV             0.00       0.00       0.00       0.00 
LARRY$DBB3:           REGLIB              0.00       0.00       0.00       0.00 
$111$DUA3:   (DECEIT) DUMPDISK            0.00       0.00       0.00       0.00 
$111$DUA5:   (DECEIT) BPMDISK             0.00       0.00       0.00       0.00 
$111$DJA8:   (DECEIT) ORLEAN              0.00       0.00       0.00       0.00 
$111$DJA10:  (DECEIT) QMISDATABASE        0.00       0.00       0.00       0.00 
$111$DJA9:   (DECEIT) MPI$DATA            0.00       0.00       0.00       0.00 
 
 
                            OpenVMS Monitor Utility 
                               CLUSTER STATISTICS 
                                 on node CURLEY 
                              29-APR-1998 12:25:56 
Tot ENQ/DEQ Rate                           CUR        AVE        MIN        MAX 
 
MOE                                       7.90      14.92       0.00      43.12 
LARRY                                    20.48      14.64       0.00      46.92 
CURLEY                                    1.93      13.29       0.00      57.30 




      

This example shows the tabular style format for the CLUSTER display.

The MONITOR DECNET command initiates monitoring of the DECNET class, which includes information about DECnet for OpenVMS network activity.

Format

MONITOR DECNET

Command Qualifiers

/qualifier[,...]

One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL

Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.

/AVERAGE

Selects average statistics to be displayed in a bar graph for display and summary output.

/CURRENT

Selects current statistics to be displayed in a bar graph for display and summary output. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.

/MAXIMUM

Selects maximum statistics to be displayed in a bar graph for display and summary output.

/MINIMUM

Selects minimum statistics to be displayed in a bar graph for display and summary output.

Description

The DECNET class consists of the following data items:

• Arriving Local Packet Rate---Rate at which local packets are being received
• Departing Local Packet Rate---Rate at which local packets are being sent
• Arriving Transit Packet Rate---Rate at which transit packets are arriving
• Transit Congestion Loss Rate---Rate of transit congestion loss
• Receiver Buffer Failure Rate---Rate of receiver buffer failures

Example

MONITOR> MONITOR DECNET
 
 



  

    

      

      
 
  
 
  
                           OpenVMS Monitor Utility 
                               DECNET STATISTICS 
                                 on node SAMPLE 
                              29-APR-1998 22:22:44 
 
                                       CUR        AVE        MIN        MAX 
 
     Arriving Local Packet Rate       9.54       5.08       0.00      11.25 
 
     Departing Local Packet Rate      9.22       4.66       0.00      10.92 
 
     Arriving Trans Packet Rate       0.00       0.00       0.00       0.00 
 
     Trans Congestion Loss Rate       0.00       0.00       0.00       0.00 
 
     Receiver Buff Failure Rate       0.00       0.00       0.00       0.00 




      

This example shows that arriving and departing network packet rates (including control packets) are roughly equivalent, and that network activity is currently at a level higher than the average since monitoring began, but not at its highest point.

The MONITOR DISK command initiates monitoring of the DISK statistics class. The maximum number of disks that can be monitored for record output is 909, and for display and summary output is 1817.

Format

MONITOR DISK

Command Qualifiers

/qualifier[,...]

One or more qualifiers as described in the Command Qualifier Descriptions section.

Classname Qualifiers

/ALL

Specifies that a table of all available statistics (current, average, minimum, and maximum) is to be included in the display and summary output. For summary output, this qualifier is the default for all classes; otherwise, it is the default for all classes except CLUSTER, MODES, PROCESSES, STATES, SYSTEM, and VECTOR.

/AVERAGE

Selects average statistics to be displayed in a bar graph for display and summary output.

/CURRENT

Selects current statistics to be displayed in a bar graph for display and summary output. The /CURRENT qualifier is the default for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.

/ITEM=(keyword[,...])

Selects one or more data items for inclusion in display and summary output. If you specify two or more keywords, enclose them in parentheses, and separate them with commas. When the /ITEM qualifier is omitted, the default is /ITEM=OPERATION_RATE.

The following table describes /ITEM qualifier keywords:

Keyword	Description
ALL	Specifies that statistics on all data items collected for the disks are displayed on successive screens.
OPERATION_RATE	Specifies that I/O operation rate statistics are displayed for each disk.
QUEUE_LENGTH	Specifies that the number of I/O request packets being serviced (current or waiting) is displayed for each disk.

/MAXIMUM

Selects maximum statistics to be displayed in a bar graph for display and summary output.

/MINIMUM

Selects minimum statistics to be displayed in a bar graph for display and summary output.

/PERCENT

/NOPERCENT (default)

Controls whether statistics are expressed as percent values in display and summary output. The /PERCENT qualifier is applicable only to the DISK, MODES, SCS, and STATES classes.

Description

The DISK class is a component class. Data items for this class are collected for each mounted disk device in a single-node or cluster system. The DISK class consists of the following data items:

• I/O Operation Rate---Rate at which I/O operations occur on each disk. By comparing operation rates for all disks in the system, you can tell which disks are busy and which are idle. However, because this statistic does not provide information about the time required for individual operations, use discretion in interpreting it.
• I/O Request Queue Length---Number of outstanding I/O request packets. Includes the request currently being serviced and those awaiting service. Note that, for greater precision, this item is always sampled at a 1-second interval, regardless of the value specified with the /INTERVAL command qualifier.
  The maximum number of disks that can be monitored is 909 for record output and 1817 for display or summary output. In previous versions, the limit was 799 disks for both types of output.

In the following example, typical of a cluster environment, note that each disk is identified by three elements:

• Disk name ending in a colon.
• Name of the cluster node through which the disk is accessed. This field appears only in the multiple-statistic display; it is not included in single-statistic displays or multifile summaries.
• Volume label.

In cluster configurations, the MSCP server software makes locally attached and HSC disks available to other nodes. A node uses remote access to a disk when it accesses the disk through another VAX node (using the MSCP server). A node uses direct access to a disk when it directly accesses a locally attached or HSC disk.

An "R" following the device name indicates that the displayed statistics represent I/O operations requested by nodes using remote access.

If an "R" does not appear after the device name, the displayed statistics represent I/O operations issued by nodes with direct access. These I/O operations might include those issued by the MSCP server on behalf of remote requests.

Example

MONITOR> MONITOR DISK/ITEM=QUEUE_LENGTH
 
 



  

    

      

      
 
  
 
  
                           OpenVMS Monitor Utility 
                              DISK I/O STATISTICS 
                                 on node SAMPLE 
                              29-APR-1998 14:19:56 
 
I/O Request Queue Length                   CUR        AVE        MIN        MAX 
 
SAMPLE$DBA0:          SAMPLE09APR         0.00       0.00       0.00       0.00 
SAMPLE$DRA2:          SAMPLEPAGE          2.00       1.43       0.00       4.00 
SAMPLE$DRB1:          ACCREG              0.00       0.00       0.00       0.00 
$1$DRA5:     (MOE)    MOE$$PAGE           0.00       0.00       0.00       0.00 
$1$DBA3:     (CURLEY) UMASTER             0.00       0.00       0.00       0.00 
$1$DBA5:     (CURLEY) MIDNITE             0.00       0.00       0.00       0.00 
$2$DRA7:     (LARRY)  RES26APR            0.00       0.00       0.00       0.00 
$2$DRB6:     (LARRY)  CLUSTERDUMP1        0.00       0.00       0.00       0.00 
$255$DUA4:   (SHEMP)  RES06AUG            0.00       0.00       0.00       0.00 
$255$DUA5:   (SHEMP)  VMSDOCLIB           0.00       0.00       0.00       0.00 




      

This example, typical of a cluster environment, shows the number of I/O packets awaiting service or in service for each disk. Note that the device SAMPLE$DRA2 is the only device with a nonzero queue length. Because MONITOR samples queue lengths every second, regardless of the collection interval value, the precision of the data does not depend on the collection interval.

	privacy and legal statement
6048PRO_041.HTML