Hello,
  Why not use Spill volumes. Create a STOrGRPP called SGSPILL put it under your 
 Dump volumes enable it to spill and problem solved.


Tobias Cafiero
Data Resource Management
Core Systems Technology
Lead System Architect
DTCC  New York
Office: 212-855-1117
E-mail: [email protected]
Web: www.dtcc.com <http://www.dtcc.com/



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Monday, April 24, 2017 2:41 AM
To: [email protected]
Subject: Re: SMS STORGRP question

You should implement TIERING. SMS first fills the first mentioned SG and only 
if it has not enough space, SMS will go to the second SG.

Kees.

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] 
> On Behalf Of Jesse 1 Robinson
> Sent: 22 April, 2017 2: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 information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN
DTCC DISCLAIMER: This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify us 
immediately and delete the email and any attachments from your system. The 
recipient should check this email and any attachments for the presence of 
viruses.  The company accepts no liability for any damage caused by any virus 
transmitted by this email.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to