As the size of an SF pubset is limited to 4TB, it can occur that one SF pubset is not sufficient for the backup and migration to storage level S1. In HSMS V10.0 and higher (SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE parameter), an SM pubset can also be assigned as storage level S1 in this case. With the exception of the control volume set and S1 volume set, all volume sets of the SM pubset are used here. Such an SM pubset is called an S1-SM pubset. The maximum possible size of an SM pubset is almost 1000TB.
To prevent the control volume set of an S1-SM pubset from being occupied with save files, use of the control volume set must be restricted beforehand as follows:
/MODIFY-PUBSET-RESTRICTIONS PUBSET=<cat_id of S1-SM-pubset> - / ,PUBSET-TYPE=*SYSTEM-MANAGED(VOLUME-SET=<control-volume-set> - / ,RESTRICTION=*NEW-FILE-ALLOCATION(MODE=*PHYSICAL-ONLY))
It is urgently recommended that an SM pubset that is to be used as an S1-SM pubset consists exclusively of volume sets in NK2 format.
S1-SM pubsets cannot be used in an SM environment, i.e. an S1-SM pubset cannot be assigned to any other SM pubset than storage level S1.
Saving to an S1-SM pubset
Saving to an S1-SM pubset is performed using the BACKUP-FILES, BACKUP-FILE-VERSIONS, ARCHIVE-FILES, COPY-SAVE-FILE, MOVE-SAVE-FILE, REORGANIZE-VERSION-BACKUP or MIGRATE-FILES statement with the specification TO-STORAGE=*S1-STORAGE-LEVEL when an SM pubset is set globally for the entire system or as storage level S1 for individual pubsets.
The save file for such a save run is configured with the following name:
ARCHIVE.SAVE.FILE.date.time.subsave#.seq#
Key: | |
date.time | Generation time in the format yymmdd.hhmmss |
subsave# | Subsave number of the run which created this save file |
seq# | Sequence number of the save file with the same time stamp (0..F) |
If the capacity of the volume set on which the save file is saved, is insufficient for the backup, another save file is created on a different volume set of the S1-SM pubset.
Its name differs from the original save file by the sequence number seq# being incremented by 1.
A subtask can create up to 16 such save files.
Configuring an SM pubset as storage level S1
An SM pubset can be used as storage level S1 of an SF pubset only when the global HSMS parameter SAVE-FILE-PROCESSING is set to *HSMS-V10-COMPATIBLE (MODIFY-HSMS-PARAMETERS statement). If SAVE-FILE-PROCESSING=*HSMS-V9-COMPATIBLE is set, the attempt to save to an S1-SM pubset is rejected.
Changing this setting has repercussions on the functionality of HSMS. For details, see section "Processing mode for save files".
The following steps are required to configure an SM pubset as storage level S1:
Place the SM pubset under HSMS control
(CREATE-SM-PUBSET-PARAMETERS statement).Define the SM pubset as storage level S1
(MODIFY-PUBSET-PARAMETERS statement).Add the SM pubset as storage level S1 globally or on a pubset-specific basis
(MODIFY-HSMS-PARAMETERS or MODIFY-PUBSET-PARAMETERS statement).