A recent need to move large volumes of datasets to the new storage Class, new volume, is beginning to feel very headache. After careful study, it is very simple to find this thing. It really fits the other person's saying that things are going to be easier after you really start trying.
First create your target Storage class and Storage group, and add the relevant volume to the SG, this time do not need to worry about existing vol on a dataset already exist, change Storage Group will not delete the dataset.
Then configure ACS Routines, associate HLQ,SC and SG, validate and activate your ACS. Use the command/setsms SCDS (SMS. ACS) avoids having to enter yes again on the console.
Finally you can start the real move dataset, using ADRDSSU to achieve
Imprtcon EXEC pgm=adrdssu //sysprint dd sysout=* //sysin DD * COPY - DATASET ( INCLUDE (rbc9cat.**, - rbc9reg.**,- )- ) - Storclas (TPHCRYSC)- bypassacs (* *) - DELETE
Note that line 9th writes the target SC to which these datasets are to be moved, because the SC and SG have established associations, so the dataset is automatically placed on the target volume. In fact, this time can not establish HLQ and SC correspondence, because there are bypassacs (* *), so these new datasets can ignore the ACS rules.
The rest of the time is waiting, and these jobs can run for a long time because moving large datasets is time-consuming. So one of the common mistakes is
iew4000i FETCH for MODULE antcvxpr from Ddname *vlf* FAILED BECAUSE Insufficient STORAGE was AVAILABLE. csv031i LIBRARY ACCESS FAILED for MODULE antcvxpr, RETURN Code, REASON code 26080021, Ddname *lnklst*
The main problem is that the size of region is too small to enlarge the region or split the dataset above the JCL include to let the job run smoothly.