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
Re: How to limit HRECALLs by USER request
HSM's CRQ(Common Recall Queue) groups recalls by tape and gives the ability to assign priority to recalls. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lizette Koehler 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
Re: How to limit HRECALLs by USER request
You could alter the priority of the recalls of the user submitting 1000s of recalls, see ALTERPRI in the HSM Admin Ref. Ex. TSO HSEND ALTERPRI USERID(USERA) LOW -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
Re: How to limit HRECALLs by USER request
When I have done lots of recalls, when a tape is mounted it processes all other pending requests on the same tape before it dismounts the tape. On Wed, May 2, 2012 at 11:35 AM, Lizette Koehler stars...@mindspring.com wrote: deleted 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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to limit HRECALLs by USER request
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
Re: How to limit HRECALLs by USER request
On Wed, 2 May 2012 09:35:14 -0700, Lizette Koehler wrote: 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. A potential bad offender here is NFS. We've had HSM busied out for days when a remote user simply did a ls -l of his TSO prefix. I suggested at that time that readdir() shouldn't report migrated data sets, but recall by specific DSN should be permitted. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to limit HRECALLs by USER request
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 stars...@mindspring.comwrote: 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 -- 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 lists...@bama.ua.edu with the message: INFO IBM-MAIN
user request
One of our analysts asked this question. She thinks it is software one of our clients uses but she cannot get any information through her contacts. I find nothing useful via Google. I have no idea what platform but I think the client is in Europe. Have you ever heard of the Edostar report management software? Anyone have an answer other than No? Thanx in advance. - The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you -- 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
