I must not be reading between the lines properly. If the dataset is being modified (or even read) frequently enough, it should not be a candidate for migration regardless of the management class. If it is not being modified, you don't need periodic backups; one will suffice for disaster recovery.
Why do you allow a client to decide if data should be backed up? If you lose the dataset for any reason (head crash, JCL error, etc), you better hope he stipulated that in writing. (As a matter of data center policy, all non-page/spool disk datasets should be backed up upon creation and any subsequent modification.) Does the user work for a different company than the client? Shouldn't they coordinate their requirements? If the user just needs an occasional backup, you (or he) could issue the HBACK command at that time. -----Original Message----- From: esmie moo [mailto:snip] Sent: Thursday, November 01, 2007 11:29 AM To: IBM-MAIN@BAMA.UA.EDU Subject: DFHSM - NO MIGRATE OF DSN Good Morning Gentle Readers, I am in a quandry. A user has asked that a PDS not be migrated because it is a huge file (about 2,500 cylinders). I was able to satisfy his requirement, however, the MANAGEMENT CLASS which governs it has no backup attributes (client didn't want a backup) by DFHSM but the user wants a backup of the dsn. I think my only choice I have is to define the dsn in another MANAGEMENT Class and have DFHSM attributes for a backup done. Could there be another solution to my problem? ---------------------------------------------------------------------- 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
