Existing SF pubsets must be converted to SM pubsets to enable users to use SM pubsets for existing files. Multiple SF pubsets can be combined to form an SM pubset. The following fundamental aspects must be borne in mind here:
The pubset ID is the catalog id part of the path name for objects cataloged in the pubset. If an SF pubset is converted into an SM pubset whose ID differs from that of the SF pubset, the addressing is changed for the objects.
If there are objects in several SF pubsets, which are converted to the SM pubset, whose path names only differ by the catalog ID, name conflicts would occur when forming the SM pubset, i.e. the path names would no longer be unique. Users who only have files on one of the SF pubsets to be converted to the SM pubset cannot be affected by this since the user ID is part of the path name.
If an SF pubset is converted into an SM pubset whose ID contains more characters than that of the SF pubset, the length of the path names for objects on the pubset are increased. This can result in path names which exceed the maximum permitted length.
The processing level, background levels and backup archives are to be included when converting SF pubsets to SM pubsets. A detailed description can be found in the “SMS” manual [28].
Only the procedure for the processing level is described below. Two options are available for this: Conversion with SMPGEN or saving and restoring.
Conversion with SMPGEN (in-place conversion)
The processing level can be converted in-place with the SMPGEN utility. It allows one SM pubset to be formed from one or more SF pubsets, where each SF pubset is transferred into a volume set. The user files on the SF pubsets remain unchanged after conversion and the SF pubset metadata files (e.g. file, user and guards catalogs, etc.) is converted into corresponding SM pubset metadata files. Specific pubset and volume set properties, user quotas, etc. are determined automatically for the SM pubset by SMPGEN. If systems support wishes to change these settings, they must post-process the SM pubset appropriately after generation.
SMPGEN provides the following statements for in-place conversion:
CREATE-SYSTEM-MANAGED-PUBSET for checking and conversion to an SM pubset which is to be created
MODIFY-SYSTEM-MANAGED-PUBSET for checking and adding additional SF pubsets to an existing SM pubset
Conversion by saving and restoring files
The transition from SF to SM pubsets via saving and restoring files is recommended in particular if a structure which differs from that resulting from in-place conversion is required for an SM pubset. This is, for example, the case if several SF pubsets are to be converted to one SM pubset with several volume sets.
The SF pubsets being converted into an SM pubset are completely backed up (possibly without the files on the background levels). The SM pubset is then created by SIR. User entries for the previous SF pubset users are created on the SM pubset. This is supported by HSMS, which allows backups of SF pubset user catalogs to be transferred to SM pubsets. The user attributes introduced for SM pubsets (e.g. user quotas for high availability files) are preset to ensure as high a degree of compatibility as possible. Finally, the guards catalog is then set up using backups made on SF pubsets if required. Finally, the user files are transferred.