Thanks all for the great comments. A few additional comments: 1) One of the sample reports for the DFSMS Report Generator is a Migrate/Recall thrashing report.
2) By default, HSM does not create an FSR record for data sets that are not eligible for primary space management. These also cause 'spin' because they are examined every cycle but never processed. Create FSRs with the following patch from the DFSMShsm I&C guide: "Enabling FSR records to be recorded for errors, reported by message ARC0734I, found during SMS data set eligibility checking for primary space management" To specify that FSR records are to be recorded for errors, reported by message ARC0734I, found during SMS data set eligibility checking for primary space management, issue the following PATCH command: PATCH .MGCB.+EF BITS(......1.) To specify that the FSR records are not to be recorded, issue the following PATCH command: PATCH .MGCB.+EF BITS(......0.) 3) Also documented in the DFSMS I&C, a patch to enable HSM to process empty and certain undefined data sets "Enabling backup and migration/expiration processing of empty data sets" DFSMShsm can be tuned such that the storage administrator can request that certain data sets that are allocated but not opened be backed up, migrated, and/or expired based on typical DFSMShsm configurations. The following two data set variations that can be handled by this change: 1. Cataloged data sets that have been allocated such that DSORG=0 (undefined) and have not been opened for output (DS1DSCHA=OFF and DS1LSTAR=0). This support will allow these types of data sets to be backed up and migrated based on the local DFSMShsm configuration. 2. Data sets that have been allocated such that a nonzero DSORG is set, but the data sets have not been opened for output (DS1DSCHA=OFF and DS1LSTAR=0). This data set variation is typically supported by DFSMShsm but might not be backed up as the change indicator (DS1DSCHA) indicates that the data set is unchanged. When DS1DSCHA indicates that the data set is unchanged, it can prevent the data set from being expired if the environment requires a valid backup before expiration. Once enabled, this support can ensure that these types of data sets can be backed up before they are migrated, thus allowing them to be expired based on the local SMS and/or non-SMS configuration. To support the data set variations that were just discussed, issue the following patch commands: PATCH .MCVT.+287 BITS(..1.....) Request empty non-VSAM data sets (DS1DSCHA=OFF & DS1LSTAR=0) to be backed up. PATCH .MCVT.+287 BITS(...1....) Allow empty cataloged data sets (DS1DSCHA=OFF & DS1LSTAR=0) with DSORG=UNDEFINED to be backed up and migrated Note: The following considerations must be made to ensure minimal impact to your environment as well as desired results: In environments that have many of these newly supported data sets, DFSMShsm functions can require additional time and CPU to complete. If these data sets have accumulated incrementally over time, this additional time and CPU requirement might be temporary. If these data sets are created frequently and in large quantities, the impact to DFSMShsm functions might be permanent. In a SETSYS INCREMENTALBACKUP(CHANGEDONLY) environment, DFSMShsm relies upon the DS1DSCHA flag of a data set to determine when the data set requires backup and when a backup might have already been created. With this support, empty data sets can be backed up even when the DS1DSCHA flag is off. For this data set type, DFSMShsm will rely on the backup date of the backup version to determine whether the data set with DS1DSCHA has a valid backup. For data sets that are allocated, backed up, deleted, and reallocated on the same date, DFSMShsm will not be able to distinguish that the backup is from a previously created version of the data set. The backup made on the same day as the creation will qualify the data set for expiration if the MC requires a backup or if a MIGRATE DELETEIFBACKEDUP command targets the data set. Given this support only applies to empty data set variations, this issue would only impact data sets whose most recent version is empty. Glenn Wilcock DFSMS Chief Product Owner ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
