Skip to Content
Information
End of support This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Controlling capacity planning

The capacity planning facility allows collection and reporting on resources over longer time periods than can be supplied by the detail space collector database.

The capacity planning database contains daily space summaries for the following resources:

  • Storage groups and pools
  • Volumes
  • Boxes
  • Physical disks
  • Applications
  • System-level summary
  • Data set summaries by group, HLQ, HLQ/group, management class, volume, and application include size, age, and percent-used distribution for all data sets, VSAM data sets, and uncataloged data sets

This information supplies the data for the capacity planning views. These views are used to see space usage over long periods of time, mapped across any of the resources above. Links to these capacity planning views are accessible from the Space Utilization Main Menu, and incorporated throughout the product where utilization trending options are available.

Capacity planning uses the Space Collector, VTOC scan master collection file, MCDS scan collection file and BCDS scan collection file to create daily summary information. The information is then logged to the capacity planning database. This summarization and logging process is initiated through the DAILYSUM console command and can be scheduled by using the MainView SRM Scheduled Services facility.

Warning

Note

If data is not collected to the detail space collector database, it will also be unavailable in the capacity planning database. For example, if the SPSUM command is not used to populate box, physical disk, and system summary information to the detail database, data for those resources will be unavailable in the capacity planning database. The same is true of application data if the APPLMON command is not used or for a group/pool if the group or pool is not assigned to a policy that causes the detail collection.

For more information, see:

 

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

MainView SRM Reporting 7.9