Future Pooling Report

The Future Pooling Report determines the pools that would be defined if all pooling definitions were active. The report displays projected pools based on the following criteria:

• DASDPOOL rules that assign data sets to pools
• SMPOOLxx pool definitions (if any)

See the following sections in this topic for more information:

• What you can do with the report
• Organization of the report
• Usage notes for creating the report
• Available fields on the report
• Sample report

What you can do with the report

This setup allows trial activation of pool definitions, without actually assigning data sets or volumes to pools and without moving data sets from one volume to another volume. Data set assignments can be set up and changed as required to define pools of the right size and composition. When pool definitions are satisfactory, all pool definitions and assignments can be activated.

Organization of the report

Selected data sets are grouped into possible pools, based on the assignments that are made by the active DASDPOOL rule list.

Possible data set movement between pools is shown; each pool displays a from data set count and a to data set count. The from count is composed of data sets that are assigned to a pool by DASDPOOL but are resident on volumes that are defined in a different pool. The to count is composed of data sets that are assigned to a pool by DASDPOOL, but are resident on volumes that are part of another pool. (The total movement from and to data sets always adds up to zero.)

Data sets residing on volumes that are not defined in a pool are reported from a report-only pseudo-pool named UNDEFIN. All volumes that are not assigned to a pool are also reported as part of UNDEFIN.

Usage notes for creating the report

Consider the following information when creating the Future Pooling Report:

• To select resources for inclusion in the report, you can use report control cards to make selection based on data set name, volume ID, pool, and so on. The selected resources are then processed by parameters in the DASDPOOL rule list. (The DASDPOOL filter list selection is not invoked.)

  Warning

  Note

  Although the Future Pooling Report displays data set movement (to and from pools), no changes are made; pools are reported as they would exist if the current pooling definitions were activated.

• The Future Pooling Report does not include any data sets or volumes that are under DFSMS management. Selection by storage group is not available.
• Pools that are included in the report and are not required to be fully defined. That is, the report does not require the DASDPOOL-assigned pools to be defined in SMPOOLxx. DASDPOOL assignments to non-existent pools create a pool for purposes of the report. This undefined pool is reported as if it were defined in SMPOOLxx; it shows a pool size (the size of all data sets that are assigned to it by DASDPOOL) in the DS MOVED TO POOL field, but it does not show any assigned volumes.
• Similarly, the report normally displays pools that are currently defined in SMPOOLxx but have no data set assignments by DASDPOOL. Defined pools might or might not show data set counts and sizes, depending on DASDPOOL assignments and volume composition.
• All possible pools are included in the report, even if selection is based on a specific pool. However, a pool is not reported if no selected data sets already exist on volumes in the pool or that would be assigned to the pool.
• For each pool, the following categories of information are displayed:
  

  • Data set composition

    The report displays the number of data sets that would reside in the pool; total and average sizes of these data sets; and a breakdown of size into allocated, used, and idle space. These figures show the total size of the pool for the current DASDPOOL assignments, including data sets residing on pool volumes that are unassigned by DASDPOOL.

  • Volume composition

    The report displays the number of volumes that are defined in the pool and the total space on those volumes. If the pool does not exist (that is, it is undefined in SMPOOL xx but has data set assignments in DASDPOOL), these volume composition figures are zero.

  • Data set movement

    The report displays the number of data sets that must be moved to and from the pool to comply with the current definitions. The to movement reflects data sets assigned to the pool by DASDPOOL, which are currently resident on a volume in another pool. The from movement reflects data sets residing on pool volumes, but assigned to another pool by DASDPOOL. If the pool does not exist (undefined in SMPOOL xx but assigned data sets by DASDPOOL), the from movement is zero.

• The DFSMSHSM migration control data set (MCDS) is required if migrated data sets are to be included in the report. If the ddname MCDS is not in the JCL, migrated data sets (ML1 or ML2) are not included. Omitting the MCDS data set has the same effect as specifying EXCLUDE MIGRATED DS=YES.

  Error

  Warning

  Many MainView SRM selection parameters are not available to the DASDPOOL rule list during report generation. For example, job execution-time parameters, such as job name and ddname, are valid for the report job only and thus are not really applicable to any pooling rules that may reference such parameters. The selection parameters that are available to the DASDPOOL rule list for the FPR are:

  • DSN (data set name)
  • DSNn (data set name qualifiers 1 through 8)
  • HLQ (data set name high-level qualifier)
  • LLQ (data set name low-level qualifier)
  • NQUAL (number of qualifiers in data set name)
• Rule list entries that select on other parameters (for example, UNIT or DSNTYPE) will not be considered for matching. See Filter-and-rule-lists.

Available fields on the report

The following fields are available for the Future Pooling Report:

Sample report

The following figure is a sample of the Future Pooling Report: