Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for z/OS 6.3.

MVScope facility

This section describes the MVScope facility, which

  • traces CPU usage down to the CSECT level
  • traces I/O usage down to the channel program level

You can use MVScope to specify one of three sampling types: CPU, IO, and CPUIO. You can initiate MVScope CPU and I/O sampling from views in MainView or from the console. MVScope can also be invoked as a MainView AutoOPERATOR action if an alert is generated as a result of an alarm produced by MainView Alarm Manager. You can also customize sampling parameters.

When MVScope is invoked, it creates a monitor set. The monitor set is a set of MainView 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 MainView view or from the console. You can also create and customize a monitor set from specific views.

MainView 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 topics:



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*