The user data and the associated administration and protection information are retained except for the following restrictions:
The SYSEAM files on the SF pubsets are lost.
The privileges and authorizations on the SF pubsets which are only relevant to the home pubset are lost.
The logon passwords on the SF pubsets are totally lost.
The group structures on the SF pubsets to be added are totally lost.
The SYSSRPM.BACKUP file on the SF pubsets to be added is lost. This means that the pubset conversion and switchover to another user catalog cannot be carried out simultaneously.
Pubset configuration files on the SF pubsets to be added which originate from an aborted reconfiguration job or an aborted cache mode change are deleted implicitly, and a warning is issued.
It is recommended that you should not carry out pubset conversion if the reconfiguration is incomplete, or if the cache mode has been changed; instead, clean up the pubset beforehand using/RESUME-PUBSET-RECONFIGURATION.
The statements made regarding the conversion of SF pubsets to new SM pubsets also apply for the location of the files on the SF pubsets, the catalog entries of files and job variables on the SF pubsets and the guards on the SF pubsets.
The user entries on the SF pubsets are converted to the format valid for SM pubsets, groups structures being lost in the process.
If a user ID exists on one of the SF pubsets but not on the pubset from which the logon information is to be taken over, the user ID is marked as “locked” (USER-LOCKED=*YES) in the SM pubset since no accounting information is available.
This is not relevant for using the SM pubset as a data pubset. If a user ID exists on several of the SF pubsets which are to be added to the SM pubset or on the SM pubset, it is handled as though it were an identical user. The numbers of file entries, JVs and reserved pages in the SF pubsets to be included and the SM pubset are totaled, as are the CE and public space limits.
The statements made regarding the conversion of SF pubsets to new SM pubsets also apply for updating or creating user-specific quotas, SPACE-USED values and settings, with a sum total being obtained for all the SF pubsets to be added and the SM pubset.
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
The DEFAULT FILE FORMAT and the allocation defaults (standard for primary and secondary allocation) of the SM pubset remain unchanged. The saturation thresholds remain the same in each volume set as those selected for the converted SF pubset.
$TSOS.SYS.PUBSET.CONFIG: Configuration description
$TSOS.TSOSCAT.#Mnn (nn=00..99): Catalog(s) of the migrated and nospace files
$TSOS.TSOSCAT.#Pnn (nn=00..99): Catalog(s) of the private disks and volume disks
$TSOS.TSOSCAT.#Jnn (nn=00..99): Catalog(s) 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 from the SF pubsets that are to be added which are 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 these existing special catalogs.
The $TSOS.TSOSCAT files are renamed to ones that are volume-set-specific
The following files are deleted on the SF pubsets that are to be added:
$TSOS.SYSCAT.GUARDS
$TSOS.SYSEAM
$TSOS.SYSPBN
$TSOS.SYSSRPM
$TSOS.SYSSRPM.BACKUP
$TSOS.TSOSJOIN
The guard and user entries from the $TSOS.SYSCAT.GUARDS and $TSOS.SYSSRPM files are transferred to the relevant file on the control volume set.
The cache configuration is transferred from the MRSCAT entries of the SF pubsets that are to be converted to the pubset configuration file of the SM pubset. Exception: the systemrelated or pubset-related cache size tolerance, which must be reset for the new pubset, if required.
The shareability value anchored in the SVL of the control volume set remains unchanged.
The SYSIDs in the SVLs are generally retained.