Installing MVScope

The steps for running the MVScope IVP are described in the following sections:

Installing the Installation Verification Program

Copy the sample file BBD9MAIV from the BBSAMP library to one of your data sets.

Tailor the JCL in the following figure to satisfy your site’s requirements, as described in the Tailoring-the-JCL section.

Sample file BBD9MAIV

Tailoring the JCL

Use the following procedure to tailor the JCL:

1. Replace the job card shown in the Sample file BBD9MAIV figure with a job card that satisfies your site’s standards.
   Make a note of the job name that you use. You will monitor this name in the views described in Initiating-MVScope-sampling-of-a-job. Use a job class that allows the job to run for at least two minutes. The program will use a lot of CPU time.
2. In the //STEPLIB statement, change *prefix* to the high-level qualifier that you have used for your distribution libraries.
3. In the //DD1 and //DD2 statements, change *tunit* to a valid unit name for temporary data sets at your site.
4. In the //DD1 and //DD2 statements, change *volser* to the volume where you want to trace I/O activity.
   If your site does not allow you to allocate data sets on specific volumes, you should delete the VOL=SER= keywords.

Initiating MVScope sampling of a job

Use the following procedure to iniate MVScope sampling of a job:

1. Display the JUDEV view.
2. Submit this job.(In your example, as shown in the following figure, the job is named BMVTAT4.) This action will allocate two temporary data sets, get 16 MB of virtual storage, and go into a continuous loop that references the storage and performs I/O to the data sets.

When the JUDEV view shows this job using the device where you directed it to allocate the //DD1 and //DD2 data sets, type M next to that row to initiate monitoring, as shown in the following figure:

MVScope initiates sampling and displays the MSMONSET view with the selected job in the sampling state, as shown in the following figure:

Verifying the analysis of MVScope

Use the following procedure to verify the analysis of MVScope:

1. 
   
   1. In MSMONSET, verify that the monitor set overview reported in the center column has the correct job name, device, date, and time.
   2. Verify that, initially, the monitor set is in the Sampling or Waiting state.As soon as MVScope detects that the job is active, it starts CPU and I/O sampling and sets the monitor set’s state to Sampling.
   3. Press Enter as sampling proceeds.
      1. Verify that both CPU and I/O counts increase.
      2. Verify that no more than 100 I/O samples are collected.
      3. Verify that sampling lasts only one minute.
   4. During sampling, observe the hot spots reported under the MSMONSET Symptoms heading on the left. Verify that a Hot Program, Hot Instruction, Hot Task, and Hot DASD Track are identified.
   5. Verify that after one minute, MVScope changes the monitor set state to Analyzing or Analyzed.
   6. Cancel the Installation Verification Program.

   7. Verify that MSMONSET reports that the monitor set’s state changes to Analyzed in less than five minutes.

      Important

      The Analyzing phase could be lengthened if MVScope is unable to quickly read the VTOC of the device where the //DD1 and //DD2 data sets are allocated, or if MVScope cannot quickly allocate and read the BBD9MAIV program from the //STEPLIB library.

   8. Verify that when the monitor set’s state is Analyzed, MSMONSET displays the following information:
      • Name of the busiest program
      • Name of the program and CSECT containing the busiest instruction
      • Name of the busiest task
      • Data set name of the busiest DASD extent
   9. After the monitor set’s state has changed to Analyzed, verify that the state changes at the start of the next interval to either Retained or Filed. If you have historical data sets and the state is Retained, wait one more interval for the state to change to Filed.
   10. If the PAS has historical data sets, verify that the monitor set state remains Filed until the historical data set is reused or otherwise becomes inaccessible to BMC AMI Ops. Verify that MVScope changes the monitor set’s state to Dropped at that time.You can use the DSLIST view to see and alter the state of the historical data sets.
   11. If you do not have any historical data sets, verify that the monitor set remains in the Retained state for five intervals, after which time MVScope changes the monitor set’s state to Dropped.

Hyperlinking to detailed views

Refer to MVScope-key-views for a description of how to use hyperlinks from the MSMONSET view to analyze the samples in the monitor set.

Refer to Summary-of-MVScope-views for a list of hyperlinks from MVScope views.

BBDTMSDP PARMLIB member

An optional PARMLIB member, BBDTMSDP, can be defined in the UBBPARM data set. This PARMLIB member allows you to specify and define default sampling parameters, which will be used for all monitoring sessions. MVScope uses the distributed default value for sampling parameters when BBDTMSDP is not defined in the PARMLIB.

Syntax rules

The following syntax rules apply to the creation of BBDTMSDP:

• An asterisk (*) in column 1 indicates a comment record. (Note that comments do not appear in the parameter record.)
• Keywords must be separated by a blank.
• Keyword values must be preceded by an equal sign (=).
• A statement can be continued without explicit continuation characters.
• Use columns 1 through 80.

Statements

BBDTMSDP PARMLIB member statements are described in the following table:

Examples

The following examples show valid ways of creating a BBDTMSDP PARMLIB member: