'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
