Indirect volume serial support allows the system to dynamically resolve volume and device type information for non-VSAM data sets that reside on either the system residence volume (SYSRES) or one or more logical extensions to the SYSRES volume. If all the SYSRES data sets do not fit on a single DASD volume, you can use additional volumes as "logical extensions" to SYSRES and refer to them indirectly. This allows you to change the volume serial number or device type of SYSRES or its logical extension volumes without having to recatalog the non-VSAM data sets on that volume.
The indirect volume serial is specified by one of two methods, either six asterisks (******) or a system symbol. The method used depends on whether the data set will be cataloged on the SYSRES volume or on one of the SYSRES logical extension volumes.
- For data sets that will reside on the SYSRES volume, you can specify either:
- a string of six asterisks (******) in place of the volume serial, or
- the &SYSR1 static symbol in place of the volume serial. (See Restrictions.)
The system dynamically resolves ****** or &SYSR1 to the volume serial of the volume from which the system was IPLed (the SYSRES volume).
- For data sets that will reside on the logical extensions to SYSRES, you must specify a static system symbol in place of the volume serial. This static symbol must be defined in the IEASYMxx parmlib member.
Note: If you establish a naming convention for your SYSRES volume and associated logical extensions, you can define a system symbol in IEASYMxx that allows you to derive the logical extensions from whatever SYSRES volume is IPLed. This eliminates the need to update the IEASYMxx parmlib member if your installation IPLs with different SYSRES volumes. A naming convention example is shown in the following topic.