Programming interface information DFSMShsm must be able to direct allocation of data sets it manages to its owned storage devices so that backup versions of data sets go to backup volumes, migration copies go to migration volumes, and so forth. DFSMShsm-owned DASD volumes are not SMS-managed. If SMS were allowed to select volumes for DFSMShsm-owned data sets, DFSMShsm could not control which volumes were selected. If SMS is allowed to allocate the DFSMShsm-owned data sets to a volume other than the one selected by DFSMShsm, DFSMShsm detects that the data set is allocated to the wrong volume and fails the function being performed. Therefore, include a filter routine (similar to the sample routine in Figure 1) within your automatic class selection (ACS) routine that filters DFSMShsm-owned data sets to non-SMS managed volumes. For information on the SMS-management of DFSMShsm-owned tape volumes, see Implementing DFSMShsm tape environments. End of programming interface information

 /***********************************************************************/
/* SAMPLE ACS ROUTINE THAT ASSIGNS A NULL STORAGE CLASS TO             */
/* DFSMSHSM-OWNED DATA SETS INDICATING THAT THE DATA SET SHOULD NOT BE */
/* SMS-MANAGED.                                                        */
/***********************************************************************/
/*                                                                     */
PROC &STORCLAS
 
 SET &STORCLAS = 'SCLASS2'
 
 FILTLIST &HSMLQ1 INCLUDE('DFHSM','HSM')
 FILTLIST &HSMLQ2 INCLUDE('HMIG','BACK','VCAT','SMALLDS','VTOC',
                          'DUMPVTOC','MDB')
 
 IF &DSN(1) = &HSMLQ1 AND
    &DSN(2) = &HSMLQ2 THEN
       SET &STORCLAS = '
 
END
/*                                                                     */ 

The high-level qualifiers for &HSMLQ1 and &HSMLQ2 are the prefixes that you specify with the BACKUPPREFIX (for backup and dump data set names) and the MIGRATEPREFIX (for migrated copy data set names). If you do not specify prefixes, specify the user ID from the UID parameter of the DFSMShsm startup procedure (shown in topic Starter set example). These prefixes and how to specify them are discussed in the z/OS DFSMShsm Storage Administration.