> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Joel C. Ewing > Sent: Friday, March 22, 2013 9:08 AM > To: [email protected] > Subject: Re: DFHSM QUESTION - RECALLING DSN TO ITS ORIGINAL VOLUME > > Noticing that this thread continues to focus on how to make a recall of > the PROCLIB dataset work, I think it should be re-emphasized that any > managed data set that is essential to the proper functioning of JES2, > or any other critical started task at your site, should really be > assigned a Management Class that inhibits migration. In the worst case > scenario, you might find yourself in a catch-22 situation where you > can't run something you need in order to get DFHSM functional because > the rarely-used but required datasets are migrated, or the required > ML1/ML2 > volume is unavailable. In the best case, start up of some important > address space may be delayed because a RECALL must first complete.
And to take it one step further, for datasets such as PROCLIBs where the using tasks thinks it knows the extents, you need to insure that the volumes containing such datasets are never defragged or the datasets are marked unmovable. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
