The number of file entries, job variables and allocated pages is added, as are the catalog entry (CE) and public space limits. The quotas (limits) are set as follows:
FILE-NUMBER-LIMIT = Sum(FILE-NUMBER-LIMIT), totalled over all SF pubsets
JV-NUMBER-LIMIT = Sum(JV-NUMBER-LIMIT), totalled over all SF pubsets
TOTAL-SPACE-LIMIT(PERM) = MAXIMUM
S0-LEVEL-SPACE-LIMIT(PERM) = Sum(PUBLIC-SPACE-LIMIT), totalled over all SF pubsets
HIGH-PERF-SPACE-LIMIT(PERM) = MAXIMUM
VERY-HIGH-PERF-SPACE-LIMIT(PERM) = MAXIMUM
HIGH-AVAIL-SPACE-LIMIT(PERM) = Sum(PUBLIC-SPACE-LIMIT), totalled over all SF pubsets that become HIGH-AVAIL volume set
TOTAL-SPACE-LIMIT(TEMP) = Sum(TEMP-SPACE-LIMIT), totalled over all SF pubsets
HIGH-PERF-SPACE-LIMIT(TEMP) = MAXIMUM
VERY-HIGH-PERF-SPACE-LIMIT(TEMP) = MAXIMUM
TOTAL-SPACE-LIMIT(WORK) = MAXIMUM
HIGH-PERF-SPACE-LIMIT(WORK) = MAXIMUM
VERY-HIGH-PERF-SPACE-LIMIT(WORK) = MAXIMUM
MAXIMUM here means that no separate limit exists for the particular subquota, but that it is matched dynamically to the more comprehensive top quota. Thus the space available for VERY-HIGH-PERF files for example, can be more than the entire space available for HIGH-PERF files. For the top quota, MAXIMUM means the maximum assignable value (i.e. 2147483647).
The values for PUBLIC-SPACE-EXCESS, DMS-TUNING-RESOURCES and PHYSICAL-ALLOCATION are set to ensure that the least restrictive condition is taken over by all the SF pubsets concerned. The ascending order of restriction is as follows:
PUBLIC-SPACE-EXCESS: ALLOWED, TEMPORARILY-ALLOWED, NO
DMS-TUNING-RESOURCES: EXCLUSIVE-USE, CONCURRENT-USE, NONE
PHYSICAL-ALLOCATION: ALLOWED, NOT-ALLOWED
When determining the SPACE-USED values, all files of a user are considered in the assignment counters according to their position on the background levels, their attributes temporary/permanent, their performance and availability attributes. The files that reside on a HIGH-AVAILABILITY volume set are included in the HIGH-AVAIL quota because they receive the file attribute HIGH-AVAIL from SMPGEN.
If group structures are adopted from one of the pubsets, the following applies:
PUBLIC-SPACE-LIMIT: MAXIMUM
TEMP-SPACE-LIMIT: MAXIMUM
WORK-SPACE-LIMIT: MAXIMUM
FILE-NUMBER-LIMIT: MAXIMUM
JV-NUMBER-LIMIT: MAXIMUM
The values PUBLIC-SPACE-EXCESS and DMS-TUNING-RESOURCES are adopted from the pubset marked as ATTRIBUTE-ORIGIN.
The (physical) format of the control volume set is entered as DEFAULT FILE FORMAT.
The allocation defaults (for primary and secondary allocation) are taken from the SF pubset that becomes the control volume set.
The saturation thresholds remain the same in each volume set as those selected for the converted SF pubset.
The following files required for administration of the SM pubset are created on the control volume set:
$TSOS.SYS.PUBSET.CONFIG: Configuration description
$TSOS.TSOSCAT.#M00: Catalog of the migrated and nospace files
$TSOS.TSOSCAT.#P00: Catalog of the private disks and volume disks
$TSOS.TSOSCAT.#J00: Catalog of the job variables
$TSOS.TSOSCAT.$PFI: Index of all catalog entries
$TSOS.TSOSCAT.$NLO: List of all file names
$TSOS.TSOSCAT.$NLC: Copy of the file name list
Catalog entries not held in special catalogs in the SM pubsets (i.e. all those that take up space in the pubset, except for files) are migrated to this new special catalog.
The $TSOS.TSOSCAT files are renamed to ones that are volume-set-specific
The files $TSOS.SYSCAT.GUARDS and $TSOS.SYSSRPM are deleted on all pubsets that do not become a control volume set. The guard and user entries are transferred to the corresponding file on the control volume set.
If EAM is to be operated on the SM pubset, a new EAM file must be set up. The following files are deleted:
$TSOS.SYSEAM
$TSOS.SYSPBN
$TSOS.TSOSJOIN
$TSOS.SYSSRPM.BACKUP
The cache configuration is taken from the MRSCAT entries of the pubsets to be converted in the pubset configuration file of the SM pubset. Exception: the pubset-related cache size tolerance, which must be reset for the new pubset, if desired.
The shareability value anchored in the SVL of the pubset converted to the control volume set defines the shareability of the newly created SM pubset.
The SYSIDs in the SVLs are generally retained; only in the case of the control volume set is it replaced in the event of an SM pubset ID that is 1 byte long.