PVSREN renames pubsets or volumes sets or converts pubset notations.
For simplicity, this is referred to as “renaming pubsets” below.
When files, file generation groups and job variables are referred to, the general term “object” is used.
The RENAME-PUBSET-OR-VOLUME-SET is used for renaming. This statement supports SF pubsets, SM pubsets and volume sets. By means of the MODE operand it is possible to select two different modes in order to rename a pubset or volume set:
Complete renaming of a pubset or volume set.
In this case, the catalog ID, user catalogs and SCI are modified.Renaming of a pubset or volume set after separation by SHC-OSD. In this case, the user catalogs and SCI are modified.
Complete Renaming should not be carried out until all the requirements have been checked (see section “Prerequisites for the execution of PVSREN”). Please also observe the “Restrictions and reworking”.
Renaming an SF pubset
The lengths of the object names are checked, even if the CHECK-FILENAME-LENGTH statement has been processed previously. All objects whose names exceed the maximum permissible length are listed. Renaming is not performed until there are no more object names that are too long.
The VSN is modified in the volume list of the catalog entry for files and file generation groups.
The VSN is modified in the SVL of all disks that belong to the pubset.
The VSN of all disks that belong to the pubset is modified in the OLC (online catalog on the Pubres).
The old MRSCAT entry is deleted for the SF pubset and a new entry created with the new catalog ID.
The default catalog ID in the user catalog (TSOSJOIN or SYSSRPM) of the home pubset and of the renamed pubset is modified. This action is carried out in interactive mode only after confirmation, and by default in batch mode. The SF pubset is also imported.
The default catalog ID is modified with
/MODIFY-USER-ATTRIBUTES.Change the affected entries in the IMON-SCI on the data pubset and (following confirmation) HOME pubset.
The user can decide whether the pubset is to become or remain available.
Renaming an SM pubset
If a disk with corresponding VSN (e.g. ABC 00 for catid=ABC) is present for the MRSCAT entry of an SM pubset, the renaming operation is aborted, since it is not clear whether the SM pubset or the SF pubset, which also exists, is to be renamed.
A length check is performed for the object names, even if the CHECK-FILENAME-LENGTH statement has been executed. All objects whose names exceed the maximum permissible length are listed. Renaming is not performed until there are no more object names that are too long.
The catalog ID of the SM pubset is modified in the pubset configuration file on the control volume set.
The catalog ID of the SM pubset is modified in the SVL of each Volres of all SM volume sets that belong to the SM pubset.
The MRSCAT entries of all volume sets that belong to the SM pubset are deleted. They are recreated when the SM pubset is imported.
The old MRSCAT entry is deleted for the SM pubset and a new entry created with the new catalog ID.
The default catalog ID in the user catalog (SYSSRPM) of the home pubset and of the renamed pubset is modified. This action is carried out in interactive mode only after confirmation, and by default in batch mode. In the course of the operation, the SM pubset is imported.
The default catalog ID is modified with
/MODIFY-USER-ATTRIBUTES.Change the affected entries in the IMON-SCI on the data pubset and (following confirmation) HOME pubset.
The user can decide whether the pubset is to become or remain available.
Renaming a volume set
The catalog ID of the volume set is modified in the pubset configuration file on the control volume set.
The VSN is modified in the volume list of the catalog entry for files and file generation groups.
The VSN is modified in the SVL of all disks that belong to the volume set.
The VSN of all disks that belong to the volume set is modified in the OLC (online catalog on the Volres).
A length check of the object names is not necessary, since the catalog ID of the volume set is not incorporated in the file name.
The catalog ID of the volume set cannot be used as the default catalog ID; therefore, it is not necessary to modify the default catalog ID. The associated SM pubset is not imported after renaming. This action must be carried out by the user.
Renaming a control volume set
The catalog ID of the control volume set is modified in the pubset control volume set.
The VSN is modified in the volume list of the catalog entry for files and file generation groups.
The VSN is modified in the SVL of all disks that belong to the control volume set.
The VSN of all disks that belong to the control volume set is modified in the OLC (online catalog on the Pubres).
The catalog ID of the control volume set is modified in the SVL of the primary disk of all volume sets that belong to the SM pubset.
The MRSCAT entries of all volume sets that belong to the relevant SM pubset are deleted. They are recreated when the SM pubset is imported.
The MSRCAT entry is deleted for the relevant SM pubset and the a new one created with the new catalog ID of the control volume set.
A length check of the object names is not necessary, since the catalog ID of the control volume set is not incorporated in the file name.
The catalog ID of the control volume set cannot be used as the default catalog ID; therefore, it is not necessary to modify the default catalog ID. The associated SM pubset is not imported after renaming. This action must be carried out by the user.
Completing a mirror disk separation initiated by SHC-OSD
After separating and renaming mirror disks using SHC-OSD (START-CLONE-SESSION .. UNIT=*BY-PUBSET(PUBSET=A, NEW-PUBSET=B) ), the references in the IMON-SCI and user catalog are not yet adjusted.
This still has to be done using //RENAME-PUBSET-OR-VOLUME-SET ... MODE=*COMPLETE-SHC-RENAME, i.e.
(after query): Changing the standard catalog ID in the user catalog (SYSSRPM) of the home pubset and the changed pubset.
Changing the affected entries in the IMON-SCI on the data pubset and (after a query) also on the home pubset.