Backup, version backup archiving and migrating to the extended S1 level

After the extended S1 level has been set up as set out under section "Setup of the extended S1 level", the S1 level can be used as before. The statements for backup, version backup, archiving and migration do not have a special syntax for using the extended S1 level.

The storage of the save files is controlled by the allocator and cannot be influenced by the user. However, the system manager can deny the creation of new save files on certain volume sets with the following command:

/MODIFY-PUBSET-RESTRICTIONS PUBSET=<sm_pubset_catid>,
   PUBSET-TYPE=*S-M(VOL-SET=<volset_catid>,
   RESTRICTION=*NEW-FILE-ALLOCATION)