Space Analysis by Data Set report

Edit online

Use this report to analyze the space utilization of data sets that were specified by the user. Entries are sorted in alphabetic order of the database name (DBNAME) and data set ddname (DDNAME).

Subsections:

Report example

The following figure shows an example of the Space Analysis by Data Set report.

Figure 1. SPMNPRT: Space Analysis by Data Set report
IMS HIGH PERFORMANCE POINTER CHECKER FOR z/OS - SPMN          "SPACE ANALYSIS BY DATA SET REPORT"                        PAGE:     1
5655-U09                                                   DATE: 07/11/2021  TIME: 18.05.23                         FABKSPMN - V3.R1

 MEMBER NAME : N/A
 ----------------------
 
 DBNAME         DDNAME      DSNAME                                         DBORG ACCM   CISP   CASP  UNIT     REORGDATE    HDPCDATE   
 TYP    PRI    SEC EXT AEXT     ALLOC %FSP %NRUS   TOTBLK  BLKSZ LRECL  MXSEG ACTMX      ROOTS   TOTALSEG VOLSER EXT     ALLOC %USE
        DATASET SIZE    %SZ
 --- ------ ------ ---  --- --------- ---- ----- --------- ----- ----- ------ -----  ---------  --------- ------ --- --------- ----

                            TESTDS.PUBLIC.SAMPLE.VSAM01                                  N/A    N/A  3390-3         N/A         N/A
 CYL      3      2   1  237         3  100 N/A          0   4096   240   N/A    N/A        N/A        N/A SYS001   1         3    0
 CYL      3      2                                                                                        SYS002   0         0    0

                   0  *****

 HDAMDB2        HDAMDS4     TESTDS.PUBLIC.SAMPLE.HDAMDS4                    HDAM ES-U    N/A    N/A  3390-3  07/06/2021  07/10/2021
 CYL     50     50   1  118        50   91   7       2475   1024  1017   122    122         70      18087 SYS004   1        50   10

           2,534,400    0.1
 
 HISAMDB1       HISAMDS1    TESTDS.PUBLIC.SAMPLE.HISAMDS1                  HISAM KS-U      0      0  3390-3  07/06/2021  07/10/2021
 CYL     50     50   1  118        50   98 N/A         90   8192   510   N/A    N/A        130        584 SYS004   1        50    2

             737,280    0.0

 HISAMDB1       HISAMDS2    TESTDS.PUBLIC.SAMPLE.HISAMDS2                  HISAM ES-U    N/A    N/A  3390-3  07/06/2021  07/10/2021
 CYL     50     20   1  118        50   68 N/A       1419   8192   512   N/A    N/A          0     106017 SYS004   1        50   32

          11,624,448    0.3

 TPFOH1         TPFOH1AA    TESTDS.PUBLIC.SAMPLE.TPFOH1.A00001             PHDAM ES-U    N/A    N/A  3390-3  07/06/2021  07/10/2021
 CYL     50     50   1  118        50   47   7      19845    512   505   246    246      11000      80037 SYS004   1        50   54

          10,160,640    0.2

 TPFOH2         TPFOH2AA    TESTDS.PUBLIC.SAMPLE.TPFOH2.A00001            PHIDAM ES-U    N/A    N/A  3390-3  07/06/2021  07/10/2021
 CYL     50     50   1  118        50   89   7       4410    512   505   122    122       9000      18178 SYS02D   1        50   12

           2,257,920    0.1

 TPFOH2         TPFOH2AX    TESTDS.PUBLIC.SAMPLE.TPFOH2.X00001            PHINDX KS-U      0      0  3390-3      NONE    07/10/2021
 CYL     20     10   1  118        20   98 N/A        735    512    14   N/A    N/A        N/A       9001 SYS02E   1        20    5

             376,320    0.0

 TPFOH3         TPFOH3AA    TESTDS.PUBLIC.SAMPLE.TPFOH3.A00001             PHDAM ES-U    N/A    N/A  3390-3  07/06/2021  07/10/2021
 CYL     50     20   1  118        50   97   7       1470    512   505   150    150       5000       5220 SYS02F   1        50    4

             752,640    0.0

 TPFOX1         TPFOX1AA    TESTDS.PUBLIC.SAMPLE.TPFOX1.A00001            PSINDX KS-U      0      0  3390-3  07/06/2021  07/10/2021
 CYL     10     10   1  118        10   87 N/A       1470    512    54   N/A    N/A        N/A       9178 SYS02F   1        10   20

             752,640    0.0

Report field description

This report contains the following information for each database data set and OS data set that is specified on the control statements.

In the report field description, the following abbreviations are used:

Table 1. Legend for reading the report field description
Abbreviation Description
(G) Indicates that the data is general information
(T) Indicates that the data is space analysis data of an IMS online full-function database data set, which is obtained by using IMS Tools Online System Interface (this data is not available for OS data sets)
(H) Indicates that it is HD Pointer Checker analysis data (this data is not available for OS data sets)

To obtain the data marked (H), HISTORY data set must be specified in the Space Monitor JCL and the database data set entry must exist in the HISTORY data set.

(S) Indicates that it is space analysis data
Note: For OS data sets, the IMS related information is not applicable.
MEMBER NAME
Name of the member specified by the EXEC PARM parameter. If no member name is specified by the EXEC PARM parameter (that is, control statements are specified in the FABKCTL or SPMNIN data set), N/A is shown. (G)
DBNAME
Name of the database. This field is left blank in the case of an OS data set. (G)
DDNAME
DDname of the data set. This field is left blank in the case of an OS data set. (G)
DSNAME
Name of the data set (G)
DBORG
Database organization (H)

One of the following texts is shown:

HDAM, HIDAM, HISAM, SHISAM, PINDX (HIDAM index), SINDX (secondary index), PHDAM, PHIDAM, PHINDX (PHIDAM index), PSINDX

This field is left blank if the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set.

ACCM
Access method (H)

One of the following texts is shown:

OSAM, LDS, KS-U, KS-S, ES-U, ES-S (KS=VSAM KSDS, ES=VSAM ESDS, U=UNIQUE, S=SUBALLOCATION, LDS=VSAM LINEAR)

This field is left blank if the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set.

UNIT
DASD device type (G)

If an asterisk * is marked after device type, for example 3390-A*, it means Extended Address Volume (EAV).

TYP
Space allocation type: CYL (cylinders), TRK (tracks), or BLK (blocks) (S)
PRI
Primary allocation (cylinders, tracks, or blocks) (S)
SEC
Secondary allocation (cylinders, tracks, or blocks) (S)
EXT
Total number of extents on the data set (S)

If 999* is shown, it indicates that the number of VSAM data set extents exceeded the maximum value (999) that can be printed.

AEXT
Number of available extents. It shows the smaller of the two values: that per volume or that for the entire data set. (S)

For more information, see Available data set extents and last space.

ALLOC
Total space allocated on the data set (cylinders, tracks or blocks) (S)

For OSAM multivolume data set, if the space allocation type is different for each volume, Space Monitor selects the unit for reporting the total allocation (cylinder, track, or block). The unit is shown in parentheses just below the allocation value.

%FSP
Percentage of the usable free space within the allocated space (G, T, H)

For HDAM, HIDAM, PHDAM, and PHIDAM database data sets, usable free space is calculated as shown in the following figure and is illustrated in Figure 7.

Figure 2. Formula to calculate usable free space (HDAM, HIDAM, PHDAM, and PHIDAM)
   Usable free space = (difference between the allocated space and DATASET SIZE)
                       + (usable free space managed by IMS)

The usable free space is calculated by using two factors of free space. The first factor is the difference in free space between the allocated space and DATASET SIZE. For a VSAM data set, this value is calculated as follows: (high-allocated-RBA) - (high-used-RBA)

The second factor is the free spaces that are chained by FSEAPs and FSEs, and in which IMS can store a segment (shown as usable free space managed by IMS in the formula). This value is obtained from the HISTORY data set. If the HISTORY data set is not specified in the Space Monitor JCL, Space Monitor ignores the second factor and calculates the usable free space based only on the first factor. In this case, the data set is treated as an OS data set.

For index database data sets, usable free space is calculated as shown in the following figure. If the HISTORY data set is not specified in the Space Monitor JCL, the data set is treated as an OS data set, and the usable free space is calculated as shown in Figure 4 and is illustrated in Figure 7.

Figure 3. Formula to calculate usable free space (index database data set)
   Usable free space = allocated space - 
                      (total number of segments x logical record length)
Note: Total number of segments for a shared index database is the sum of segments only for the specified DBNAME on the control statement.

For HISAM database data sets and OS data sets, usable free space is calculated as shown in the following figure and is illustrated in Figure 7.

Figure 4. Formula to calculate usable free space (HISAM database data set and OS data set)
   Usable free space = (difference between the allocated space and DATASET SIZE)

For a VSAM data set, this value is calculated as follows: (high-allocated-RBA) - (high-used-RBA)

An asterisk (*) after %FSP indicates that the imbedded free space is not accurate because the HD Pointer Checker run with the HISTORY=YES option is obsolete (older than the warning threshold value specified in the SPMNMBR, SPMNIN, or FABKCTL data set).

%NRUS
Percentage of nonreusable free space managed by IMS, which are chained by FSEAPs and FSEs (G, H)

This field applies to HDAM, HIDAM, PHDAM, and PHIDAM database data sets.

An asterisk (*) after %NRUS indicates that the nonreusable free space is not accurate because the HD Pointer Checker run with the HISTORY=YES option is obsolete (older than the warning threshold value specified in the SPMNMBR, SPMNIN, or FABKCTL data set).

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

TOTBLK
Total number of blocks in the data set (G, T)
BLKSZ
Block size or control interval (CI) size (G)
LRECL
Logical record length (G)
MXSEG
Longest segment length in the data set, including the segment prefix as defined in DBD (H)

This field applies to HDAM, HIDAM, PHDAM, and PHIDAM database data sets.

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

ACTMX
Size of the longest segment detected by HD Pointer Checker in this data set (H)

This field applies to HDAM, HIDAM, PHDAM, and PHIDAM database data sets.

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

CISP
Number of VSAM control interval (CI) splits that have occurred for the data set. This field applies only to the data set with ACCM=KS-U or KS-S. (T, H)

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

CASP
Number of VSAM control area (CA) splits that have occurred for the data set. This field applies only to the data set with ACCM=KS-U or KS-S. (T, H)

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

ROOTS
Number of root segments in this database data set (H)

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

TOTALSEG
Total number of segments in this database data set, including roots (H)

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field shows 'N/A'.

REORGDATE
Date of the most recent reorganization (H)

If the reorganization date does not exist in the HISTORY data set, this field shows 'NONE'.

An asterisk (*) after REORGDATE indicates that the imbedded reorganization date might not be accurate because the HD Pointer Checker run with the HISTORY=YES option is obsolete (older than the warning threshold value specified in the SPMNMBR, SPMNIN, or FABKCTL data set).

HDPCDATE
Date of the most recent HD Pointer Checker run (with HISTORY=YES option) that created an entry in the HISTORY data set (H)

If HD Pointer Checker run date does not exist in the HISTORY data set, this field shows 'NONE'.

An asterisk (*) after the HDPCDATE indicates that the date of the HD Pointer Checker run with HISTORY=YES option is obsolete (older than the warning threshold value specified in the SPMNMBR, SPMNIN, or FABKCTL data set).

In the following fields (VOLSER, EXT, ALLOC, and %USE), the information is shown for each volume, in the case of a multivolume data set.

VOLSER
Volume serial number of the data set (S)
EXT
Number of extents on the volume (S)
ALLOC
Allocated space on the volume (S)
%USE
Percentage of used space within the allocated space on the volume (T, S)
This value is calculated as shown in the following figure. For a VSAM data set, the used space is the high-used-RBA on the volume, and the allocated space is the high-allocated-RBA on the volume.
Figure 5. Formula to calculate the percentage of used space within the allocated space on the volume
   %USE = (used space / allocated space) x 100
DATASET SIZE
The space that is used for the data set in bytes. This is the block or CI size multiplied by the number of the total blocks or CIs in the data set. (T, S)

For a VSAM data set, the space is the high-used-RBA and is illustrated in Figure 7.

%SZ
Percentage of the space that is used in the data set to the maximum database data set size (T, H)

This value is calculated as shown in the following figure.

Figure 6. Formula to calculate the percentage of the space that is used in the data set to the maximum data set size 
   %SZ = (DATASET SIZE / maximum data set size) x 100
For HDAM and HIDAM database data sets:
  • If the data set is an OSAM data set and the block size is even, the maximum size is 8 GB.
  • If the data set is a VSAM linear data set (OSAM LDS) and has the extended addressability attribute defined, the maximum size is 8 GB.
  • Otherwise, the maximum size is 4 GB.
For PHDAM and PHIDAM database data sets:
  • If the data set is an OSAM data set and OSAM8G is specified in the RECON data sets, the maximum size is 8 GB.
  • If the data set is a VSAM linear data set (OSAM LDS) with the extended addressability attribute and OSAM8G is specified in the RECON data sets, the maximum size is 8 GB.
  • Otherwise, the maximum size is 4 GB.

For other IMS database data sets, the maximum size is 4 GB.

If the data set is an OS data set or the HISTORY record entry for the database data set is not found in the HISTORY data set, this field is printed as asterisks '***...*'.

The following figure provides a brief overview of how a VSAM data set is used. When you analyze the Space Analysis by Data Set report, this figure helps you understand the fields that are printed in the report.

Figure 7. Overview of how a VSAM data set is used: Space Analysis by Data Set report

This figure provides a brief overview of how a VSAM data set is used.

The following error messages are included in the report if the data set encounters associated error conditions:

***** DASD NOT MOUNTED *****
The DASD which should contain the data set is not mounted, and the space allocation information for the data set is not available.
***** NO VTOC ENTRY ON ANY VOLUME *****
The data set is cataloged but no VTOC entry is found on any volume for the data set. Space allocation information for the data set is not available.
***** DATA SET NOT CATALOGED *****
The data set is not cataloged and the space allocation information for the data set is not available.
***** DATA SET ON TAPE *****
The data set resides on tape and space allocation information for the data set is not available.
***** DATA SET MIGRATED *****
The data set is cataloged but it is migrated. Space allocation information for the data set is not available.
***** DSCB BLOCK SIZE=0 *****
The block size information in DSCB for the data set is zero. Space allocation information for the data set is not available.
***** DATA SET ON UNSUPPORTED DEVICE *****
The data set resides on an unsupported device and space allocation information for the data set is not available.