I recall (no pun intended) in an HSM class that grouping recalls by tape volser was the default action of HSM at the 1.11 version if not prior.
On Wed, May 2, 2012 at 12:35 PM, Lizette Koehler <[email protected]>wrote: > I have not seen a good answer on this, so I thought I would throw this out. > > We have on occasion users submit 1000's of recalls at one time. They use > a variety of processes from TSO Batch HRECALL to a REXX process. Of course > this can impact other users who are looking to just get one or two datasets > back. > > Other than writing an exit, is there any simple approach to prevent user's > from submitting more than X recalls at one time? Or a way to ensure that > any recalls submitted are grouped together by migration tape? > > For example, if I submit 100 recalls that will actually need 40 different > migration tapes. Is there any way to get DFHSM to force the recalls to be > done by migration volume rather than FIFO? > > We are z/OS V1.12 and are using CRQ processing in DFHSM. > > thanks for any insights > > Lizette > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
