It has been a little while working directly with SMS, but if your volumes in the OVERFLOW storage group are in an ENABLE status then SMS will treat them the same as the volumes in the SVCDUMP storage group. SMS will look for the best "fit" for the dataset allocation. So if OVEFLOW has more free space and/or less fragmented or is on "faster" DASD then SMS may pick OVERFLOW over SVCDUMP.
Depending on your needs, you might consider a special management class for the dump datasets that will migrate them quicker than your normal other datasets. That may help manage things on a more automatic basis. Thanks.. Paul Feller AGT Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Friday, April 21, 2017 19:43 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
