All this talk of cancelling DFHSM sounds scary to very wrong. In my experience, it almost always leaves the CDS's in a state of incompleteness. Requiring AUDIT and more.
I've never had a hang due to CDS back-up starting in the middle of other processing. I do Autobackup, then Secondary, then Primary. The CDS back-up is the first part of Autobackup. You back up first as unbackuped files won't migrate. Secondary next for maximum ML1 space, then migration. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of O'Brien, David W. (NIH/CIT) [C] > Sent: Wednesday, March 04, 2009 8:31 AM > To: [email protected] > Subject: Re: DFHSM Issue - Critical > > If it is a recycle impacting CDS Backups, the recycle can simply be held. > Recycle will then end pre-maturely and CDS Backup will proceed. > > There should not be any need to cancel DFHSM in this instance. > > Dave O'Brien > NIH Contractor > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] On Behalf Of > Staller, Allan [[email protected]] > Sent: Wednesday, March 04, 2009 11:24 AM > To: [email protected] > Subject: Re: DFHSM Issue - Critical > > 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 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
