No. HSM will not migrate a file if it is open. IIRC, But proclibs have short usage. So it is possible the proclib is not used within the timeframe for migration is specified. JES2 does not always open PROCLIBs after the TTRs are read into JES2 ASID. Unless the environment has multiple PROCxx statements in JES2 that are constantly used, PROC01 PROC02 etc, then the dataset is not needed. JES2 already knows where the data is located on the dasd volume.
An JES2 requires that the data map to the same TTR. So the proclib could be moved, but the tracks not over written. So the TTRs would still be valid for that proc. The minute the space is reused, is when JES2 will provide the I/O error. So it is not use going back to the same volume, but to the exact same TTR placements. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf > Of Paul Gilmartin > Sent: Thursday, March 21, 2013 9:23 AM > To: [email protected] > Subject: Re: DFHSM QUESTION - RECALLING DSN TO ITS ORIGINAL VOLUME > > On Thu, 21 Mar 2013 10:37:15 -0500, David Devine wrote: > > > >its not as simple as getting it recalled to the same volume. I believe it's > >still the case > that at jes startup it maps the dataset extents so you would need to get it > back to > exactly the same place(s) on the pack. > >The best solution is to make all your jes proclibs non migrateable. > >A simple alter mgmtclas to something suitable will do the job. > > > Does this mean that HSM will migrate a data set while it's open? Eek! > > -- gil > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
