Evaluating the value of DSMAX
You might need to increase the value of the DSMAX subsystem parameter to prevent unneeded I/O operations.
Procedure
To evaluate whether to modify the value of the DSMAX subsystem parameter, use the following approaches:
- Specify a value for the DSMAX subsystem parameter that
is larger than the number of data sets that are open and in use at
one time.
- For the most accurate count of open data sets, refer to the OPEN/CLOSE ACTIVITY section of the Tivoli® OMEGAMON® XE for Db2 Performance Expert on z/OS® statistics report. Make sure the statistics trace was run at a peak period, so that you can obtain the most accurate maximum figure.
- The best indicator of when to increase the value of the DSMAX subsystem parameter is when the open and close activity of data sets is high. One-per-second is a general guideline. Refer to the OPEN/CLOSE value under the SER.TASK SWITCH section of the Tivoli OMEGAMON XE for Db2 Performance Expert on z/OS accounting report or NUMBER OF DATASET OPENS in the bufferpool statistics (which provides the statistics for specific buffer pools). Consider increasing DSMAX when these values show more than one event per second.
- Consider partitioned and LOB tables spaces. The formula that Db2 uses to calculate the initial size of the DSMAX subsystem parameter does not account for partitioned or LOB table spaces. Those table spaces can have many data sets.
- Consider the data sets for non-partitioned indexes that
are defined on partitioned table spaces with many partitions and multiple
partitioned indexes. When those indexes are defined with small PIECESIZE values, many data sets might be the result.
- You can calculate the total number of data sets (rather
than the number that are open during peak periods).
- To find the number of simple and segmented table spaces,
issue the following query:
SELECT CLOSERULE, COUNT(*) FROM SYSIBM.SYSTABLESPACE WHERE PARTITIONS = 0 GROUP BY CLOSERULE;The calculation assumes that you have one data set for each simple, segmented, and LOB table space. These catalog queries are included in DSNTESP in SDSNSAMP. You can use them as input to SPUFI. - To find the number of data sets for the partitioned
table spaces, issue the following query:
SELECT CLOSERULE, COUNT(*), SUM(PARTITIONS) FROM SYSIBM.SYSTABLESPACE WHERE PARTITIONS > 0 GROUP BY CLOSERULE;The query returns the number of partitioned table spaces and the total number of partitions. - To find the number of data sets required for each nonpartitioned
index, issue the following query:
SELECT CLOSERULE, COUNT(*) FROM SYSIBM.SYSINDEXES T1, SYSIBM.SYSINDEXPART T2 WHERE T1.NAME = T2.IXNAME AND T1.CREATOR = T2.IXCREATOR AND T2.PARTITION = 0 GROUP BY CLOSERULE;The calculation assumes that you have only one data set for each non-partitioned index. If you use pieces, adjust accordingly. - To find the number of data sets for the partitioned
indexes, issue the following query:
SELECT CLOSERULE, COUNT(*) FROM SYSIBM.SYSINDEXES T1, SYSIBM.SYSINDEXPART T2 WHERE T1.NAME = T2.IXNAME AND T1.CREATOR = T2.IXCREATOR AND T2.PARTITION > 0 GROUP BY CLOSERULE;The query returns the number of index partitions. You have one data set for each index partition. - To find the total number of data sets, add the numbers that result from the four queries. (For Query 2, use the sum of the partitions that was obtained.)
- To find the number of simple and segmented table spaces,
issue the following query: