The HSMS statement MODIFY-PUBSET-PARAMETERS is used by the HSMS administrator to place pubsets under HSMS management and to set the pubset parameters. All modifications made are valid from the moment of statement entry for the current HSMS session and any following sessions.
A pubset can be placed under HSMS management only under the following conditions:
The pubset must be available locally, i.e. it must have been imported already by means of IMPORT-PUBSET.
The user ID SYSHSMS must be created on the pubset before it can be assigned to a storage level.
A pubset must be set up as an S1 pubset before it can be assigned as an S1 pubset to an S0 pubset.
It is necessary to take into account some special features of pubsets when placing them under HSMS management. This action should therefore only be performed together with the system administrator.
An entry relating to a particular pubset is not made in the HSMS control file unless at least one parameter differs from the default setting.
The following default values apply to pubsets being placed under HSMS management for the first time:
Operand value | Default value for pubsets under HSMS management |
STORAGE-LEVEL | *UNDEFINED |
SYSARCHIVE | global definition from the HSMS control file |
| SYSBACKUP | global definition from the HSMS control file |
| SYSVERSION | *UNDEFINED |
if S0: |
|
A pubset can be assigned to a storage level, while the pubset itself can be assigned default backup, version backup and archival system archives.
For S0 pubsets, it is also possible to define further parameters for migration (see section "Migration control and management of migration archives").
Notes
Save files on an S1 pubset are created with the same user ID as the archive directory that manages the save file. Therefore, this user ID must also exist on the pubset that is assigned to storage level S1.
It should be permissible to exceed the storage space limit (PUBLIC-SPACE-EXCESS).