HSM Assistant Process - HASP Download HASP today!
If you are looking for a way to reduce DASD storage at your site, DCMS/HASP may be the answer.
HASP is a valuable tool for the z/OS storage administrator, permitting you to easily identify which disk files are not getting migrated by IBM’s HSM (Hierarchical Storage Manager) and optionally define actions for handling these files dynamically.
HASP is particularly useful at a site that is billed for daily DASD residency charges --- the more disk storage you are using, the higher your monthly storage bill. In this scenario, you undoubtedly want to move disk files to cheaper tape media as quickly as possible. HASP can help you monitor and manage the HSM migration process.
The HASP batch process produces an “issues” report (or downloadable spreadsheet) that shows the datasets that HSM is not migrating. For each such dataset, HASP assigns a category that identifies one of several reasons why migration has not occurred.
|REQUIRED||The dataset’s assigned management class is defined to migrate only when explicitly instructed to do so with an HMIGRATE command.|
|EXCLUDED||The dataset’s assigned management class is defined to never migrate.|
|DELAYED||Migration is defined and should have already occurred, but is late.|
|NON-SMS||The dataset cannot migrate because it resides on non-SMS volume.|
|EMPTY||The dataset cannot migrate because it is empty (contains no records).|
|HELD-CHPBIT||The dataset cannot migrate because the checkpoint bit is set in the VTOC.|
|HELD-ERASE||The dataset cannot migrate because the VSAM ERASE option was used.|
|UNKNOWN||The dataset has no management class or an invalid management class.|
|UNSUPPORTED||The dataset has an attribute that prevents migration, such as an uninitialized creation date, an unknown DSORG or DSORG=DA.|
The HASP CONTROL file can be used with a combination of report column criteria to isolate the specific files you wish to manage, including selection based on:
|STATUS||The STAT column (PROD, TEST or other user-defined values)|
|TYPE||The file TYPE column (SEQ, GDG, PDS, VSAM, DB2, IMS, etc.)|
|MGMTCLAS||The MGMTCLAS column|
|HLQ||The first DSN node --- wildcards are accepted|
|SLQ||The second DSN node --- wildcards are accepted|
|REF-DATE||Days since last reference|
|CRE-DATE||Days since file creation|
|LATE||The number of days migration has been delayed|
|SIZE||The file size in kilobytes allocated|
|UNUSED||The calculated percentage of kilobytes used / allocated|
|CATEGORY||The HASP-assigned CATEGORY column (see above)|
Once identified, the HASP CONTROL records can then indicate the desired actions to be taken against the files, such as:
|HMIGRATE||Explicitly migrate the dataset to ML2|
|ALTER||Change the dataset’s management class to a new value|
|HBACKUP||Explicitly request an HSM backup|
|DELETE||Delete the dataset|
|MOVE||Move the dataset to new SMS-managed volume|
Here are some examples of how you could use HASP: