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 CMF 6.3.

VSMDATA

The VSMDATA control statement causes the CMF MONITOR Extractor to collect information about the use of virtual storage, including the use of system queue area (SQA) by subpool, common storage area (CSA) by subpool and key, and private area virtual storage by specific jobs.

VSMDATA
[SAMPLE={5000|nnnn}]
[JOBNAME=(job1,...,job32)]

Note

Both CMF MONITOR VSMDATA sampler and RMF VSTOR sampler use the MVS VSMLIST service, which can have high CPU overhead.

Monitoring modes

One VSMDATA statement can be specified for each monitoring mode, continuous (CPM) or intermittent (IPM).

Sampler and record types

The VSMDATA statement controls the VSMS sampler, which produces SMF type 78-2 records.

Analyzer statements and reports

VIRTSTOR

CMFSUM

Virtual Storage Activity Report

CMF Summary Report

Other BMC Software products

The VSMDATA control statement is used by the CMF MONITOR Extractor only.

Usage notes for private area sampling

Private area sampling is most useful for long-running, nonswappable jobs. Sampling other jobs can be insufficient for the following reasons:

  • Jobs are sampled only if they are active at the beginning of a recording interval. If a job starts after a recording interval has begun, it will not be sampled until the next recording interval.

    Similarly, if a job ends during a recording interval and another job of the same name begins, the data for the first job is flagged asjob terminated during interval and sampling for the new job does not begin until the next recording interval. In addition, the data for the two like-named jobs is reported as though they were the same job.

  • A job that begins and ends in the same recording interval is not sampled.
  • If CMF MONITOR finds that a job is swapped out, it skips the current sample; thus, the sample count for a particular job might be below that of another job and below the overall sample count. If the job was swapped out for every sample during a recording interval, no data is recorded for that job.

Parameters

Parameters for the VSMDATA control statement are as follows:

SAMPLE=

specifies the number of milliseconds between data gathering cycles for the VSM data being gathered

The default is 5000, which is also the minimum value. The maximum sampling rate is 60,000.

Note

The virtual storage sampler is a high overhead sampler. For this reason, the lowest sampling rate allowed is 5000 milliseconds. If you specify a value below 5000, CMF MONITOR automatically changes it to 5000.

JOBNAME=

specifies the names of jobs for which private area storage usage data is to be collected

You can specify up to 32 job names. The sampling rate for jobs is the same as that for the common areas. If the JOBNAME parameter is not specified, no private area data is collected and the Private Area Storage Summary and Detail sections of the Virtual Storage Activity Report are unavailable.


Examples

Example
 VSMDATA  SAMPLE=5000

The CMF MONITOR Extractor samples virtual storage data once every five seconds (the minimum sampling rate). Private area data is not collected.

Example
VSMDATA  SAMPLE=8000,JOBNAME=(RESOLVE,VAM2)

The CMF MONITOR Extractor samples virtual storage data for the common and private areas for jobs RESOLVE and VAM2 once every eight seconds.

 

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