I believe I've see this sometimes where an SMS managed dataset that has a storclass with the guaranteed attribute is being recalled. Therefore, HSM will only attempt to recall it to the same volume from which it was migrated. Alter the storclass on the dataset to one that does not have the guaranteed attribute before recalling it.
Terry Traylor charlesSCHWAB TIS Mainframe Storage Management Remedy Queue: tis-hs-mstg (602) 977-5154 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gary Green Sent: Tuesday, May 20, 2008 12:55 PM To: IBM-MAIN@BAMA.UA.EDU Subject: DFHSM Abend Wouild someone be able to help me save a bunch of research time with this problem. We have a user that is attempting to recall a migrated dataset (standard JCL PDS). However, DFHSM is getting an abend E37-04 during the recall process. If this were a recover I would allocate a new dataset, with appropriate attributes, and then ask HSM to replace the existing one. However, the only options with a recall are volume, unit, wait, etc... I tried it myself, even sendig the recalled ds to other volumes, all to no avail. I do not recall getting anything like this for more than 10 years and I forgot the work-around. Thanks for anything anyone can contribute. ---------------------------------------------------------------------- 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
