In some cases, you might want to pass ACS a storage class that is different from that of the source data set. You can specify the RESTORE command with the STORCLAS keyword to pass ACS a storage class name as follows:

RESTORE  -
        INDDNAME(TAPE)  -
        DATASET(INCLUDE(USER12.**))  -
        STORCLAS(SCNAME1)

However, using STORCLAS does not guarantee that the data set is assigned the storage class you specify. It means only that the storage class you specified is passed to the ACS routines. Depending on how your installation’s ACS routines are written, the storage class you specify can be ignored, assigned to the data set, or used in combination with other input variables to determine a new storage class for the data set.

RACF® checks if the RESOWNER field of a given data set is authorized to define the data set with the given STORCLAS. Ensure that the RESOWNER field of the data set has the proper authority to use the indicated storage class.

To make certain that the storage class you specify is assigned to the data set, you can use the BYPASSACS keyword as follows:

RESTORE  -
        INDDNAME(TAPE)  -
        DATASET(INCLUDE(USER12.**))  -
        STORCLAS(SCNAME1)  -
        BYPASSACS(**)

In this case, ACS is not invoked, and therefore the data set is assigned whichever storage class that you have specified with STORCLAS. If you do not use STORCLAS, the data set is assigned the storage class of the source data set.

To limit the use of BYPASSACS, an installation can set up a RACF class profile.

You can use the NULLSTORCLAS keyword in conjunction with the BYPASSACS keyword to make a data set non-SMS-managed. For example, the following specification of the RESTORE command causes the specified data sets not to be SMS-managed:

RESTORE  -
        INDDNAME(TAPE)  -
        DATASET(INCLUDE(USER12.**))  -
        NULLSTORCLAS  -
        BYPASSACS(**)