Using indirect volume serial support

The following information is a guide to help you use indirect volume serial support:

Use access method services (IDCAMS) DEFINE NONVSAM to catalog the data sets that will reside on SYSRES or its logical extension volumes.
For a data set that will be cataloged on the SYSRES volume, specify ****** or the &SYSR1 static symbol in the VOLUMES parameter and a value of 0000 on the DEVICETYPES parameter.

For a data set that will be cataloged on a SYSRES logical extension volume, specify a static system symbol in the VOLUMES parameter. IBM® suggests using &SYSR2 for the first logical extension volume, &SYSR3 for the second, and so on. If you decide to use symbols with names different than &SYSR2, &SYSR3, and so on, keep in mind that the symbol name must be no smaller than the volume serial it represents, and no longer than six characters. This length includes the & but not the period.
Define static symbols &SYSR2, &SYSR3, and so on, in the IEASYMxx parmlib member. (The system sets &SYSR1 to the volume serial of the IPL volume. You cannot define &SYSR1.)
For example, if the logical extension for the SYSRES volume used to IPL your production system is P1RES2 and the logical extension for the SYSRES volume used to IPL your test system is TSTRS2, your IEASYMxx member might contain statements such as:
```
/* Symbols for production system, P1 */
SYSDEF .
       .
       .
       SYMDEF(&SYSR2='P1RES2')   /* Logical extension volume for P1 */
/* Symbols for test system, TST      */
SYSDEF .
       .
       .
       SYMDEF(&SYSR2='TSTRS2')   /* Logical extension volume for TST */
```
If your installation IPLs with different SYSRES volumes and you establish a naming convention for the SYSRES and its logical extension volumes, you can create a single IEASYSMxx member that can be used regardless of which SYSRES volume is used to IPL the system. To do this, use substrings of the SYSRES volume serial (&SYSR1) in defining the symbols for the extension volume serials. For example, if you have the following SYSRES volumes and logical extensions:
SYSRES Extensions

S01RES S01RS2,S01RS3

S02RES S02RS2,S02RS3

DEVRES DEVRS2,DEVRS3
you can refer to them using a single IEASYMxx parmlib member with the following statements:
```
SYSDEF .
       .
       SYMDEF(&SYSR2='&SYSR1(1:3).RS2') /* second SYSRES logical
                                                  extension */
       SYMDEF(&SYSR3='&SYSR1(1:3).RS3') /* third SYSRES logical
                                                 extension  */
       .
       .
```
If you use parmlib member PROGxx to specify authorized libraries, and any of those libraries are on SYSRES and its logical extensions, you can use static system symbols to identify the volumes. If, however, you still use parmlib member IEAAPFxx for this purpose, symbols will not work.
Note: You can use the CSVLNKPR tool to convert IEAAPFxx to PROGxx.
In RACF®, you may be able to remove the volser from PROGRAM profiles that refer to SYSRES and its logical extensions. See z/OS Security Server RACF Security Administrator's Guide for more information.
In DFSMShsm, a recovered or recalled data set catalog entry will not reflect system symbols used for indirect volume serials and may not return to its original volume. You may want to prevent migration of these data sets. See APAR OW24928 for more information.

	SYSRES	Extensions
	S01RES	S01RS2,S01RS3
	S02RES	S02RS2,S02RS3
	DEVRES	DEVRS2,DEVRS3