You can require a backup before allowing migration to prevent this. Might increase utilization of primary volumes with datasets needing a backup.
On Wed, Oct 10, 2012 at 7:37 AM, Staller, Allan <[email protected]> wrote: > If you wish to change the default behavior of DFHSM to *NOT* require a backup > before deletion, use the DBU patch described in my previous post.. > > <snip> > If there is no BCDS information for a dataset, then as far as HSM is > concerned the dataset has no backup. Unless you patch HSM, it will not > delete a dataset that has no backup. > > Determining how this occurred may be more trouble than it is worth if the > datasets were migrated long ago. You could start tracking newly migrated > datasets to determine if the situation repeats and possibly catch it while > there is enough data to correct the cause. > > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
