I have modified my schedule to do the same. The CDS backups rarely (with the exception of SSM) occur during concurrent migration and backup.
BTW, I have also had this situation occur when a recycle was processing concurrent w/CDS backup. In my most recent case, a multi-vol recycle was running when the CDS backup started. The CDS backup enqueued behind the recyle. When the recycle completed the current volume, he could not proceed because the CDS backup had an exclusive Enqueue on the CDS and the recycle could not read the CDS to obtain a shared enqueue on the next volume to be recycled. The CDS backup could not proceed because the it could not get exclusive control of the CDS in order to proceed. A cancel will release both enqueues and allow things to proceed when DFHSM Is restarted. <snip> Allan, I find that CDS Backups run before my Incremental Backups but then I've always scheduled Backups before Secondary Space Mgt. Is it possible that HSM automatically backs up the CDS datasets before the first major automated process after midnight whether it is Primary or Secondary Space Mgt. or Incremental Backups if the CDSVERSIONBACKUP parameter is coded in Parmlib? I haven't found a clear description in the FMs. </snip> Not sure about the what actually triggers the CDS backup either. In my case. SSM is the first major process to run nightly. ---------------------------------------------------------------------- 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
