You would have to assign a data class to the dumps with a retention period or
expiration date specified for HSM to delete the non-sms managed dumps. It
looks like you should be able to assign a data class via the DUMPDS ADD
command.
Max Smith
DFSMS Development
Thanks. Is there a delete option?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Yes, auto migration will suffice. Use the HSM ADDVOL command to have HSM
manage a nonSMS volume. You'll define it as a PRIMARY volume. You can specify
the days to keep the data sets on the volume before they are migrated with the
MIGRATE(days) keyword. You should also specify the THRESHOLD
I migrate the individual dumps directly to ML2 for 30 days. I migrate them
once they reach 3 days in age. If I need it longer than that then I just
change the mgmtclas. Mostly, any problems are fixed within that time. If you
have dumps that you don't want that get migrated, just HDEL them.
Can anyone recommend how to set up HSM to manage my sys1.dump datasets?
Currently they are dynamically allocated on one non sms device. Would auto
migration suffice? Ideally keep on device for x days then migrate or backup
with delete? Sorry not versed in HSM.
