Hey Jesse, I have the same setup but I have my OVERFLOW volumes set as QUINEW so they are only used if the original SG can't hold all of the data. Hope this helps.
Wayne Schroeder Mainframe Storage Administrator T 254.399.5070 M 254.644.8534 E [email protected] 7420 Fish Pond Rd. Waco, TX 76710 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Friday, April 21, 2017 7:43 PM To: [email protected] Subject: SMS STORGRP question 'Forever' we have directed DUMPSRV SVC dumps via ACS routine to STORGRP 'SVCDUMP', which is defined to a small set of volumes called SVCDxx. We had a (major) problem a while back when DB2/CICS wanted to take a humongous dump that exceeded the available capacity of of the SVCDxx volumes. So we *added* group 'OVERFLOW' to the ACS routine expecting this much larger group to accommodate dumps that SVCDUMP could not handle. Much to our chagrin, from that moment forward, *all* SVCDUMPs went directly to OVERFLOW without even trying to find space in group SVCDUMP. We have an RYO mechanism to manage dumps created on volume SVCDxx, so dumps created elsewhere are a problem we can live with on occasion but not regularly. I know there are various ways to resolve to this problem, but I want to know why SMS is behaving this way and whether there is a purely SMS solution: try SVCDUMP first; if no room, then try OVERFLOW. In that order. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office <===== NEW [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN [http://www.txfb-ins.com/TFBICImages/email.jpg] J.D. Power Disclaimer<https://www.txfb-ins.com/terms-conditions#disclaimer> CONFIDENTIALITY STATEMENT: The foregoing message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2521, and is CONFIDENTIAL. If you believe that it has been sent to you in error, do not read it. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
