Lizette, You may want to refer to 1.4.3 Processing Priority of Recalls and Deletions in the HSM Stor. Admin. Apparently recalls are not subject to FIFO.
-----Original Message----- From: Lizette Koehler [mailto:stars...@mindspring.com] Sent: Wednesday, May 02, 2012 12:35 PM To: IBM-MAIN@bama.ua.edu Subject: How to limit HRECALLs by USER request 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 lists...@bama.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
