Files on Net-Storage when renaming SF or SM pubsets
If there are files in a pubset which reside on a default Net-Storage volume, the associated metadata of the file in the local pubset and on the Net-Storage volume is adjusted to the new pubset name.
If there are files in a pubset which reside on a Net-Storage volume with a user-defined VSN, the associated metadata of the file on the Net-Storage volume is adjusted to the new pubset name.
In both cases the Net-Storage files can be accessed without restriction after they have been renamed.
The administration of Net-Storage is described in the “Introduction to System Administration” [5 (Related publications)].
Modifying the default catalog ID
The default catalog ID can only be modified if the ID possesses the system privilege USER-ADMINISTRATION.
If the User ID does not possess this privilege, message PVR0200 is used to decide whether renaming should nevertheless take place. If so, the default catalog ID can be modified later using the MODIFY-JOINFILE as soon as the User ID has the correct privilege.
Maximum number of volumes
Renaming from point notation to PUB notation is possible only if the number of volumes is not greater than 32.
Renaming from point notation to point notation is not possible if the new catalog ID has four digits and the number of volumes is greater than 36, since only one digit is available for the sequence number.
File protection with GUARDS
With a guard, you can also define the program that controls file access (e.g. $TSOS.EDT). Here, the catalog ID is also stored in the GUARDS catalog.
When the pubset where the program resides is renamed, the access condition is no longer satisfied: the catalog ID in the GUARDS catalog and the catalog ID of the pubset where the program resides no longer match.
In this case, the access conditions are changed for all guards that contain this catalog ID. This affects not only those guards on the renamed pubset and the home pubset, but also the guards on all other pubsets.
PVSREN does not provide support for this problem.
Catalog ID in user files
PVSREN cannot modify the catalog ID in the user files.
If a user file contains the catalog ID of a pubset that is to be renamed (e.g. in procedures), this catalog ID must be changed by the owner of the file as required.
Catalog ID in IMON files
After the installation of software with the installation monitor (IMON), the storage location of the installation item is noted in the software configuration inventory (SCI). The catalog ID is also stored.
If a pubset on which the software was installed using IMON is renamed, all the SCIs in which this software is registered must be changed. The SCIs of the HOME and renamed pubsets are changed by PVSREN. The SCIs of other pubsets must be changed manually using /MODIFY-IMON-SCI. Here, the name of the pubset prior to renaming must be specified for OLD-NAME, and the name to be applied to the pubset after renaming must be specified for NEW-NAME.
Shared pubset
PVSREN can only modify the MRSCAT entries of the system on which renaming is carried out.
Since there is an MRSCAT entry for a shared pubset on all systems that use the pubset, the MRSCAT entries must be adapted by system administration on all remote systems.
For pubsets, the old MRSCAT entry must be deleted and a new MRSCAT entry created with the new catalog ID. For SM pubsets, the name of the control volume set has to be specified (the name can be new as well).
The MRSCAT entries for the volume sets of an SM pubset must be deleted together with the pubset entry (default for the REMOVE-MASTER-CATALOG-ENTRY command). They will be newly created automatically. See also the note at the bottom of the page.
When renaming the control volume set, the MRSCAT entry of the control volume set must also be deleted. The entry for the new control volume set is newly created during the import of the SM pubset. See also the note at the bottom of the page.
In the MRSCAT entry of the SM pubset to which the control volume set belongs, the catalog ID of the control volume set must be entered using /MODIFY-MASTER-CATALOG-ENTRY.
When renaming a “normal” volume set, only the MRSCAT entry of this volume set need be deleted. A new one need not be created, since this is done when the SM pubset is imported. See also the following note.
Storage classes
Catalogs for storage classes and volume set lists exist on all SM pubsets. Storage classes have no direct references to catalog IDs. Volume set lists, on the other hand, assign one or more volume sets to a storage class. The entries in the catalog of the volume set lists therefore contain one or more catalog IDs of the SM pubset’s volume sets.
When a volume set is renamed, this renaming also takes place in the volume set catalog to prevent the allocation of storage space for files via storage classes (explicitly specified or default storage classes in the user catalog) on the pubset from being affected by the renaming.
When a pubset is generated from mirror pubsets, the storage classes of the source pubset can either be accepted or deleted. Message PVR0207, which you can reply to, is output for this purpose. When the storage classes are accepted, the volume set lists (as in the case of renaming) are adjusted to the catalog IDs of the target pubset’s volume sets.
Startup parameter file
When renaming a home or paging pubset, it might be necessary to adapt the startup parameter file. In addition to the VSNs of the paging disks, it can contain full file names with catalog ID.
SDF parameter file
/MODIFY-SDF-PARAMETERS can be used to activate a syntax file and specify its name with the catalog ID.
/SHOW-SDF-PARAMETERS can be used to determine whether a syntax file resides on the renamed pubset. If so, it must be deactivated using /MODIFY-SDF-PARAMETERS and reactivated with the new file name.
MIP parameter file
/MODIFY-MIP-PARAMETERS can be used to activate a message file and specify its name with the catalog ID.
/SHOW-MIP-PARAMETERS can be used to determine whether a message file resides on the renamed pubset. If so, it must be deactivated using /MODIFY-MIP-PARAMETERS and reactivated with the new file name.
SLED parameter file
If the renamed pubset contains a SLEDFILE that is being referenced in the SLED parameter file, the file has to be adjusted.
Repeat jobs
Repeat jobs, for which the ENTER file resides on the renamed pubset, must be restarted.
Print jobs
Print jobs for files residing on the pubset to be converted cannot be performed following the conversion. They must be deleted and new ones created.
Migrated files on a pubset
If an SF or an SM pubset is renamed, the ARCHIVE directory must be processed using the DIRCONV tool. PVSREN does not output messages to indicate that a pubset contains migrated files.
Example
/START-DIRCONV
//RENAME-CATID DIRECTORY-NAME = <directory name>
OLD-CATID = *BY-SPECIFICATION(CATID = <old catid>),
NEW-CATID = <new catid>,
NEW-DIRECTORY-NAME = <new directory name>
//END
Then the new directory must be replaced with the old directory.
When renaming an HSMS-CONTROLLED volume set (S1 level), the S1 volume set must be modified using the HSMS statement MODIFY-SM-PUBSET-PARAMETERS.