This article mainly introduces how to sort out the scope of DB2 data sets. The percentage of DB2 data sets in practice is still the majority. If you are curious about this, the following articles will unveil its mysteries. In practice, you can use the Storage Management Service (SMS) on the host to easily and quickly organize the dataset range without restoring the data space.
You can use the Storage Management Service (SMS) on the host to easily and quickly organize the dataset range without restoring the data space.
Code
1. Input a LISTCAT command from TSO terminal panel 3.4 to a suspicious dataset that may exceed the 119 range
2. Once you verify that the dataset reaches the 119 range. Determine which data space saves the dataset. Double-click to stop the data space.
3. input the following command to the command line from the opposite data set of TSO in 3.4. This command is: hmigrate. This will migrate the queried dataset.
4. Wait a few minutes so that DFHSM can move the dataset and then use the listcat command to verify that it has been migrated.
5. Then, enter the following command line in the same command line of the migrated data set's anti-DB2 data set: hrecall.
6. Wait a few minutes for DFHSM to undo your dataset. Once it is recalled, it will have a major boundary.
The preceding content describes the scope of the DB2 dataset. We hope to help you in this aspect.