Enlarging a fully extended user-managed data set
If a user-managed data set reaches the maximum number of VSAM extents, you can enlarge the data set.
Procedure
To enlarge a user-managed data set:
- To allow for recovery in case of failure during this procedure,
ensure that you have a recent full image copy of your table spaces
and indexes. Use the DSNUM option to identify the data set for table spaces or partitioning indexes.
- Issue the command STOP DATABASE SPACENAM for the last data set of the supported object.
- Delete the last data set by using access method services.
- Redefine the data set, and enlarge it as necessary.
The object must be a user-defined linear data set. The limit is 32 data sets if the underlying table space is not defined as LARGE or with a DSSIZE parameter, and the limit is 4096 for objects with greater than 254 parts. For a nonpartitioned index on a table space that is defined as LARGE or with a DSSIZE parameter, the maximum is MIN(4096, 232 / (index piece size/index page size)).
- Issue the command START DATABASE ACCESS (UT) to start the object for utility-only access.
- To recover the data set that was redefined, use the RECOVER
utility on the table space or index, and identify the data set by
the DSNUM option (specify this DSNUM option for table spaces or partitioning
indexes only).
The RECOVER utility enables you to specify a single data set number for a table space. Therefore, you need to redefine and recover only the last data set (the one that needs extension). This approach can be better than using the REORG utility if the table space is very large and contains multiple data sets, and if the extension must be done quickly.
If you do not copy your indexes, use the REBUILD INDEX utility.
- Issue the command START DATABASE to start the object for either RO or RW access, whichever is appropriate.