The non-SMS volumes are not automatically processed like the SMS ones, you have to specify them specifically. You use the ADDVOL parameter (look in the HSM Storage Administration Reference for ADDVOL). You don't specify ADDVOL for SMS volumes, just the non-SMS one.
Brian Westerman and From the HSM Primer: 1.5 DFSMShsm functions for non-SMS-managed volumes For non-SMS-managed volumes, DFSMShsm uses volume parameters to determine how each data set on the volume is managed. Dump and restore functions: The dump function for non-SMS-managed volumes is governed by parameters of the DFSMShsm commands, but it is performed the same way as for SMS-managed volumes. Backup and recovery functions: The volume-basis operation of DFSMShsm for non-SMS-managed volumes causes differences in how backup is performed. For non-SMS-managed volumes: If automatic backup is in effect for the volume, all changed data sets that DFSMShsm can manage are backed up. All data sets processed by a particular DFSMShsm host have the same backup frequency unless the frequency has been modified for that data set by a DFSMShsm command. All data sets processed by a particular DFSMShsm host have the same number of backup versions, unless the number of backup versions has been modified for that data set by a DFSMShsm command. In addition, you can specify the number of days to retain backup versions of non-SMS-managed data sets only by command parameters for the entire system complex. Space management function: Space management consists of removing appropriate data sets from the level 0 volumes and reducing the space occupied on the level 0 volumes by the data sets that remain there. In removing the data sets, you can have DFSMShsm either delete them entirely or move them to other DASD or tape volumes. If you move the data sets to other DASD or tape volumes (ML1 or ML2), they can be automatically deleted from the migration volumes when they expire. Differences in the way that DFSMShsm performs space management for non-SMS-managed data sets include: The deletion age and management technique are the same for all data sets on a volume managed by the deletion (delete by age) technique. The deletion age and management technique are the same for all data sets on a volume managed by the retirement (delete if backed up) technique. The migration age and management technique are the same for all data sets on a volume managed by the migration technique. The time for the data set to remain unopened before migration from ML1 to ML2 volumes is the same for all non-SMS-managed data sets in the system complex. A data set migrated from a non-SMS-managed volume can be recalled to an SMS-managed volume if SMS is active and if the data set meets the conditions for selecting SMS management for that data set. DFSMShsm recalls a non-SMS-managed data set to a non-SMS-managed volume only if the data set does not meet the conditions to become an SMS-managed data set, or if a command forces the recall to a non-SMS-managed volume. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
