1.4. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Monday, April 09, 2007 10:11 AM To: [email protected] Subject: Re: Recalling GDG generations
Rex, What release of Zos are you on? ________________________________ From: Pommier, Rex R. [mailto:] Sent: Mon 4/9/2007 11:05 AM To: [email protected] Subject: Re: Recalling GDG generations Actually I just tried this (the IEFBR14 job) because I have seen the issue that Gil mentioned, where HSM recalls 1 dataset at a time for a normal batch job. I just recalled 31 generations out of a 91 generation GDG. I thought it would single reload the migrated generations but it didn't. Using the IEFBR14 job, HSM grouped the datasets by tape, and reloaded all the generations that were on that tape, then while rewinding tape 1, went to tape 2 and loaded all the generations on that tape. A pleasant surprise. Now that I learned something, can I go home? :-) Rex BTW, my MAXRECALLTASKS is 5 and my TAPEMAXRECALLTASKS is 2. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Monday, April 09, 2007 9:45 AM To: [email protected] Subject: Re: Recalling GDG generations No, HSM does not 'single thread' unless the maxrecall is set to 1. In the case of recall by jcl, the process is single threaded because the datasets are recalled in the order in which they are allocated. Optimally you would issue Hrecall commands against the set of datasets you wanted to recall HSM would then recall as many concurrently as possible. At the very least multiple tape mounts would be avoided if the desired datasets happened to be on the same ML2 tape. ---------------------------------------------------------------------- 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
