Walter, I was able to recall other ML2 dsns to the original volumes by putting all the volumes (for that specific SG) in DISNEW status and only enabling the volume where the dsn is to be recalled. It is not a very scientific approach however it did the job eventhough it is quick and dirty.
________________________________ From: Walter Marguccio <[email protected]> To: [email protected] Sent: Thursday, March 21, 2013 4:54:13 PM Subject: Re: DFHSM QUESTION - RECALLING DSN TO ITS ORIGINAL VOLUME > From: willie bunter <[email protected]> > I checked the SC. It doesn't have Guaranteed Space. Willie, if the SC doesn't have Guaranteed Space, then there is no way to force hsm to recall a migrated dataset on the original volume (at least that I'm aware of). If your dataset would have had a SC with Guaranteed Space = Yes, then hsm would have recalled it on the same volume where it was allocated. And if the original volume is not there (for whatever reason) the recall would fail. If you have datasets with such a SC, you can test this yourself. Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
