If the extended storage level S1 has already been used for a while, various save files can be distributed over multiple volume sets. Therefore, the extended storage level S1 must be empty, before it can be reduced to a single volume set.
The following statement is required to reduce the extended storage level S1 to the volume set VS01 for an SM pubset SM01:
//MODIFY-SM-PUBSET-PARAMETERS SM-PUBSET-ID=sm01,vs01)
S1-DEFINITION=*PAR(S1-VOLUME-SET=
HSMS checks whether there are save files on volume sets controlled by HSMS. If this is the case, the MODIFY-SM-PUBSET-PARAMETERS statement is rejected with the HSM0500 message.
This also applies if the S1 level is to be completely removed with SM-PUBSET-ID=*UNDEFINED.
If it becomes necessary to switch to one volume set after the extended storage level S1 has been used, the administrator must empty the S1 level beforehand:
Migrate the migration archives from S1 to S2 using the MIGRATE-FILES statement. Save files which contain no invalid files are not reorganized in this case.
Copy backup and long-term archives from S1 to S2 using the COPY-SAVE-FILE statement. Then delete the save file from S1 with the following statement.
Reorganize version backup archives to level S2 using the REORGANIZE-VERSION-BACKUP statement.
//MODIFY-ARCHIVE ... SAVE-FILE=*DELETE