Behavior of the COPY-SAVE-FILE ... TO-STORAGE=*S1-STORAGE-LEVEL command depending on the environments in which the original and the target archive are defined

The result of the COPY-SAVE-FILE statement with the TO-STORAGE=*S1-STORAGE-LEVEL specification depends on the environment, in which the original and the target archive are defined.

• If the target archive is defined in the SF environment, the S1 level definition is taken from the global HSMS parameters. A global S1 pubset is either a traditional SF pubset or an S1-SM pubset. For an S1-SM pubset all volume sets should be defined with USAGE=*STD and the save files can be saved to any volume set of this S1-SM pubset. Only the control volume set should not be used. This can be prevented by defining a respective restriction with the MODIFY-PUBSET-RESTRICTIONS statement.

• If the target archive is defined in the SM environment, the S1 level definition is taken from the local SM pubset parameters of the environment. In HSMS V11.0A and higher, the S1 level can be restricted to a volume set or distributed to all volume sets under HSMS control.

The following table shows the possible results of the COPY-SAVE-FILE ... TO-STORAGE=*S1-STORAGE-LEVEL statement depending on the environment of the respective archives:

• Original archive *SINGLE-FEATURE

Target archive environment	S1 level in target environment (global S1 level for SF environments)	Result of the COPY-SAVE-FILE ... TO-STORAGE=*S1-STORAGE-LEVEL statement
*SINGLE-FEATURE	NOT-DEFINED	This statement is rejected with the HSM0214 message.
*SINGLE-FEATURE	SF1	The statement is accepted. The copy of the save file is created on the SF1 SF pubset. SF1 may also be an S1-SM-pubset. In this case, the copy of the save file is stored on a USAGE=*STD volume set. File and job variable names remain the same, if not otherwise specified.
*SYSTEM- MANAGED( CATALOG-ID = SM1)	NOT-DEFINED	This statement is rejected with the HSM0214 message.
*SYSTEM- MANAGED( CATALOG-ID = SM1)	HSM1	The statement is accepted. The copy of the backup file is created on the HSM1 volume set of the SM1 SM pubset. Files and job variables are automatically renamed. The catalogue ID is changed in SM1.
*SYSTEM- MANAGED( CATALOG-ID = SM1)	*ALL-HSMS-CONTROLLED	The statement is accepted. The copy of the save file is created on one or more HSMS controlled volume sets of the SM1 SM pubset (depending on the capacity). Files and job variables are automatically renamed. The catalogue ID is changed in SM1.

• Original archive *SYSTEM-MANAGED(CATALOG-ID = SM1)

Target archive environment	S1 level in target environment (global S1 level for SF environments)	Result of the COPY-SAVE-FILE ... TO-STORAGE=*S1-STORAGE-LEVEL statement
*SINGLE-FEATURE	NOT-DEFINED	This statement is rejected with the HSM0214 message.
*SINGLE-FEATURE	SF1	The statement is accepted. The copy of the save file is created on the SF1 SF pubset. SF1 may also be an S1-SM-pubset. In this case, the copy of the save file will be stored on a USAGE=*STD volume set. If the target file is not a long-term archive, the renaming of files/job variables has to be explicitly determined: the catalogue ID must be changed. Otherwise, the statement is rejected with the HSM02A3 message.
*SYSTEM- MANAGED( CATALOG-ID = SM1)	NOT-DEFINED	This statement is rejected with the HSM0214 message.
*SYSTEM- MANAGED( CATALOG-ID = SM1)	HSM1/ *ALL-HSMS-CONTROLLED	The statement is accepted. The copy of the save file is created on HSM1 or on one or more HSMS controlled volume sets of the SM1 SM pubset (depending on the capacity). Note: if the original save file is also stored on the S1 level and //COPY-SAVE-FILE is to be copied from one backup archive to another, no copy is created. Reason: the time stamp of the original and the target file, and therefore their file names, are identical.
*SYSTEM- MANAGED( CATALOG-ID = SM2)	NOT-DEFINED	This statement is rejected with the HSM0214 message.
*SYSTEM- MANAGED( CATALOG-ID = SM2)	HSM2/ *ALL-HSMS-CONTROLLED	The statement is accepted. The copy of the save file is created on HSM1 or on one or more HSMS controlled volume sets of the SM1 SM pubset (depending on the capacity). Files and job variables are automatically renamed. The catalogue ID is changed in SM2.