Quick start

This section guides you through the basics of MVScope. This section is intended for users who are familiar with BMC AMI Ops views, hyperlinks, online help, and menu structures.

MVScope keywords

The following table describes key words for using MVScope:

Key word	Description
Monitor set	Sampling profile and records for views
Monitoring	Sampling CPU and I/O activity and analyzing the samples
Primary view	MVScope primary views, which include MSLIST, MSMONSET, MSDIAG, MSDPROF, MSDCPU, MSDIO
Sampling	For CPU: Interrupting the CPUs and collecting instruction address samples; For I/O: Tracing a specified number of I/O events for one or more devices, optionally filtered by job, and collecting I/O samples
Tracing	Sampling a set of events in sequence, as for I/O sampling

MVScope key views

To begin using MVScope, you should be familiar with the two key views:

MSLIST view
Display the MSLIST view by typing MSLIST on the command line of any BMC AMI Ops view.

The MSLIST view is MVScope's primary administrative view. It shows all of the monitor sets and their states. You can execute several line commands against the monitor sets shown in MSLIST.

Refer to the Line commands for MSLIST table for a list of commands that you can issue in MSLIST.

The MSLIST view is shown in the following figure:

>W1 =MSLIST============SYSE=====*========DDMMMYYYY==HH:MM:SS====MVMVS====D====3
Cmd Monitor Set      Status    Samp Sampled Traced Sampling   Sampling CPU I/
--- -----------      ------    Types Job      Device Date       Start     ct c
    BMVVXK22002NOV20 Analyzed CPU   XTST7PAS        20NOVYYYY 15:47:08 27
    BMVVXK22002NOV20 Analyzed CPU   XTSTKPAS        20NOVYYYY 15:42:48   8
    BMVVXK22002NOV20 Analyzed CPU   XTST7PAS        20NOVYYYY 15:34:00 24
    Template Monset Ready     CPU                              00:00:00

MSMONSET view

Hyperlink to the MSMONSET view from the Monitor Set field in the MSLIST view. The MSMONSET view shows you all of the specific information for a monitor set-its status, date and time, and the hottest program, instruction, task and DASD extent.

MSMONSET also provides hyperlinks to more detailed views that help you identify the instructions and I/Os causing the problems encountered with the monitored job or devices.

The MSMONSET view shows the status of an individual monitor set, as shown in the following figure:

>W1 =MSMONSET==========SYSE=====*========DDMMMYYYY==HH:MM:SS====MVMVS====D====1
                                MVScope Monitor Set
     Symptoms                                            Problem Analysis
   . Hot Program             Job BMVSLKV , Devn 0D06   . Tasks a and SRBs
     Name: BBD9MAIV 89.9% 10:55:06 to 11:56:07      . Programs
   . Hot Instruction         257 CPU, 100 I/O samples . I/Os
     Addr: 00006B4E 29.2% Analyzed NOV 16, YYYY     . Traces
     Pgm:   BBD9MAIV         No sampling errors        > Maps
     Csect: BBD0MAIV
     Ofst:   +0001B6         +----------------------+    Utilities
   . Hot Task                |   Place cursor on    | > Monitored Job
     Addr: 007E39C8 89.5% |    menu item and     | > First Monitored Dev
     Name: BBD0MACP         |     press ENTER      | . Monitor Sets
   . Hot DASD Track          +----------------------+
     CCHH: 00E5000C 14.0%                            . Return ...
     Dsn:   SYS96158.T13504

Displaying hidden fields in MVScope views

Many of the MVScope views contain more detailed information in hidden fields.

To display hidden fields

On the command line, type CUST.
When view customization is displayed, type E on the command line.
The hidden fields are displayed.
For more information about hidden fields, place the cursor on the field heading and press PF1 (Help). Be sure to scroll to the right in the views to look for information that is in displayed fields but does not fit on the screen. For more information about customizing views, see Customizing-views-and-Help-text.

MVScope in historical mode

MVScope cannot sample jobs from views that are in historical mode.

You can, however, use the ADD line and primary command in an MSLIST view that is in historical mode.

You have to view and issue commands against the newly created monitor sets in a time frame that includes the current interval.

Where to go from here

This is the end of your MVScope Quick Start tour. The section Tutorial leads you step-by-step through the different features and views in the MVScope facility. For descriptions, screen prints, and a review of the views and how they are related, see Summary-of-MVScope-views.