If one of the following conditions is not satisfied, the pubset is not renamed.
The pubset must have the status INACCESSIBLE since unwanted accesses to the catalog would otherwise be possible during renaming.
If a volume set is to be renamed, the associated SM pubset must first be exported. It is not possible to export a volume set.
All disks required must be available in the system in which the renaming is carried out.
When renaming an SM pubset, all disks of the control volume set and also the Volres of all volume sets that belong to the SM pubset are required.
When renaming a “normal” volume set, all disks of the volume set and also all disks of the control volume set are required.
When renaming a control volume set, all disks of the control volume set and also the Volres of all volume sets of all volume sets that belong to the SM pubset are required.
PVSREN must be able to exclusively reserve all the disks required.
When renaming an SM pubset, a volume set of this pubset must not be renamed simultaneously.
Renaming a volume set is possible only if no other volume set, or the SM pubset to which the volume set belongs, is renamed at the same time.
There must be no disks with the destination VSN.
Example: Renaming “ABC” to “X”
The pubset ABC consists of the disks ABC.00 to ABC.05: In this case, the disks PUBX00 to PUBX05 must not exist.
If an MRSCAT entry with the destination catalog ID exists, it must not have the status ACCESSIBLE.If this MRSCAT entry has the status INACCESSIBLE, renaming is carried out only after confirmation of message
PVR0205.When renaming an SM pubset or a control volume set, the SM pubset must not contain a volume set that has the status DEFECT.
It is not possible to rename a volume set that has the status DEFECT.
The length of the file, file generation groups and job variable names must not exceed the maximum length. The CHECK-FILENAME-LENGTH checks the length. This check is necessary only if the length of the catalog ID is increased.
The length check is not necessary for volume sets, since the volume set ID is not incorporated in the file name.
Furthermore, the following points should be observed prior to renaming so as to ensure correct execution of the function:
If an MRSCAT entry with the destination catalog ID exists, renaming should only be carried out on this catalog ID when this MRSCAT entry is no longer required. PVSREN deletes this MRSCAT entry and creates a new one.
All private files that are used after renaming should have a catalog entry in the catalog of this pubset, since only then is the length check carried out for these files.
It should be ensured that no ENTER jobs are present in the job pool, since these could possibly cease to be executable after renaming.
Before renaming is carried out, all print jobs for files located on the pubset to be renamed should be completed. The jobs would otherwise remain in the queue and the pubset required cannot be imported because it has been renamed .
If a home pubset is renamed, the following points must be observed:
In many computer centers, enter jobs in which this catalog ID is defined are started automatically at startup (e.g. ENTER to load SPEEDCAT). This catalog ID is now no longer valid and must be replaced by the new one.
If the source file of the subsystem catalog <subsystem catalog>.SRC created by IMON is used, the catalog ID which is no longer valid must also be replaced by the new one in this file, too.
A FAST startup is executed using a parameter file. Parts which reference the VSN must be changed.
Conversion from PUB to POINT notation is always possible. Conversion from POINT to PUB notation is possible only if the number of volumes is greater than 32.