Brief description of the scope of the DB2 Dataset

This article mainly tells you about the scope of the DB2 dataset. You can use the Storage Management Service on the host to sort out the dataset scope, instead of restoring the data space, the following is a detailed description of the main content of the article. I hope you will have a better understanding of it after browsing.

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 moved dataset's anti-Dataset: 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.

The above content is an introduction to the scope of sorting out DB2 data sets. I hope you will find some gains.