That's interesting because on my 1.4 system, HSM recalls invoked by Iefbr14 are done sequentially as each dataset is allocated by Jes. I have not tried nor observed how a base gdg is handled.
________________________________ From: Pommier, Rex R. [mailto] Sent: Mon 4/9/2007 12:00 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Recalling GDG generations 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: IBM-MAIN@BAMA.UA.EDU 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: IBM-MAIN@BAMA.UA.EDU 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. ---------------------------------------------------------------------- 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
