Getting started with MVScope
You can use MVScope to specify one of the four sampling types: HIS, CPU, IO, and CPUIO. You can initiate MVScope HIS, CPU and I/O sampling from views in BMC AMI Ops or from the console. MVScope can also be invoked as a BMC AMI Ops Automation action if an alert is generated as a result of an alarm produced by Alarm Management. You can also customize sampling parameters.
When MVScope is invoked, it creates a monitor set. The monitor set is a set of BMC AMI Ops records that contains the following information:
- Name of the job or devices sampled
- Date and time of the set of samples
- Tracing parameters
- Samples collected
MVScope creates the monitor set automatically when you start MVScope against a specific job from a BMC AMI Ops view or from the console. You can also create and customize a monitor set from specific views.
BMC AMI Ops writes monitor sets to its history files at the end of the interval when the monitor set has been analyzed.
This section contains the following topic:
Frequently asked questions
How many MVScope monitor sets can I run at one time?
Four monitor sets can be run at one time. If you try to start a fifth monitor set, you might receive a warning message.
How can I increase the number of monitor sets that I can run concurrently?
BMC Software does not recommend running more than four MVScope monitor sets at one time because doing so impacts system performance.
How many times can I sample the same job?
Sample a job as many times as you want; however, for each sampling, you will need a separate monitor set.
How do I start a monitor set for a job that is not running yet?
Start the monitor set in the usual way. MVScope will start sampling when the job is initiated.
My monitor set got dropped. Why? What do I do now?
The space for the monitor set was reused. If you want to prevent a monitor set from being dropped, use the DSLIST view to make the historical data set ineligible for recording. You cannot recover the monitor set record that was dropped.
The MSICCW view reports all I/O data as 'Not Authorized.' What is wrong?
The system administrator has not authorized you to collect or view data transferred by traced I/Os.
How can I make MVScope sample for longer than 1 minute?
You can use the CHAnge line command in MSLIST to change sampling parameters for a job that is in the Ready state. If you want to resample a job, select that job from MSLIST by typing ADD next to the monitor set name. Then change the parameters to what you want, save the new monitor set, and use the MONitor line command to initiate sampling.
How long are monitor sets in the Filed state? Why do they get dropped?
Monitor sets remain in the Filed state until their historical data sets are reused. If you want to prevent a monitor set from being dropped, use the DSLIST view to make the historical data set ineligible for recording. You cannot recover the monitor set record that was dropped.
How long are monitor sets retained in the PAS’s virtual storage?
Monitor sets are retained for five intervals; during that time, you can still view them even if you have no historical data sets.
Can I run MVScope in SSI mode?
No. MVScope actions are not supported in SSI mode.
Can MVScope trace activity on any kind of device?
No. MVScope can trace activity on DASD and tape but not on a printer.