A single-feature pubset (SF pubset) has a pubset ID (syntactically identical to a catalog ID) and consists of a maximum of 255 disks. The format of all the disks must be the same in relation to allocation unit, formatting, PAM key use etc. Certain attributes are assigned to the SR pubset, e.g. high availability, which apply to all the files within the pubset.
Privileged SIR can also be used to set up a system-managed pubset (SM pubset) or a volume set. As far as the user is concerned, a system-managed pubset (SM pubset) is virtually identical to a SF pubset. In the main, the differences between the two pubset types are relevant to system administration.
By contrast with the SF pubset, an SM pubset consists of several volume sets. Like an SF pubset, each volume set has a certain format and certain attributes. The formats and attributes of the various volume sets that belong to an SM pubset can be different. Like an SF pubset, the SM pubset is addressed from outside only via a catalog identifier. The specification of specific file attributes defines the volume set in which a file is stored, with the result that files with different requirements in terms of availability and performance can be stored in one SM pubset.
SM pubsets cannot be used as a home pubset. All SIR statements which are exclusively needed to create a home pubset are therefore rejected for SM pubsets.
Dynamic pubset reconfiguration
The pubset configuration defined during creation can be changed (or reconfigured) during the life of the pubset.
Configuration data, the disk and the volume set configuration of a pubset can be reconfigured via various command interfaces dynamically, i.e. while the pubset is in use. For detailed information on dynamic pubset reconfiguration, see the “Introduction to System Administration” [5 (Related publications)].