This program does not work if the job calls in the dataset with the base GDG name and not each generation separately. The files are large enough where I don't want them not to migrate. Any other suggestion would be appreciated.
Thank You -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Farley, Peter x23353 Sent: Thursday, July 24, 2008 3:20 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: HSM Recalls There is, and it does. It starts a TCB for each file in the whole job that needs recalling following the place where RECALL is invoked. In each TCB it issues HRECALL for one file and WAIT's for the recall to finish. Beware though -- If your shop's "maximum WAIT time" is too low or HSM is very busy, you can get an S522 abend when one or more of the HRECALL's takes too long to finish. HTH Peter > -----Original Message----- I have this job that calls in all generations of a dataset. This job executes once a month and most of the generation have been migrated. When the job starts executing is sends the request to HSM to start the recalls. It recalls the migrated datasets one at a time. Is there a way to make more recalls happen. This is not a HSM problem the max recalls we have set is 4. Any help would be appreciated. Thank You P.S. We are z/OS V1R7 going to z/OS V1R9 in August. ---------------------------------------------------------------------- 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
