Nothing is as simple as it needs to be :-)

Letting a file span volumes can complicate your DASD backup/recovery
strategy. Volumes that are candidates for spanning may need to be
grouped and treated as a whole rather than individual volumes. 

So, as Darth wisely advises, think about your options and possible side
effects. For example, if you are not using C, then perhaps SMS data
compression might be something to consider. 

HTH and good luck.    

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Darth Keller
Sent: Wednesday, August 13, 2008 2:43 PM
To: [email protected]
Subject: Re: Dataclass extent constraint removal option

>>Before I set this option to yes I thought I would check and see if
there 

>>are any pit falls to setting it to yes. Any gotchas?

>>We have just one dataclass and are z/OS 1.7

>>Thanks

>>Jerry 
////////////////////////

I'd recommend thinking through this - there are a couple other fields I 
think you'll want to consider:

 REDUCE SPACE UP TO (%)         How much do you want to reduce the space

before allowing the job to fail?  25%?  50%? 

 and 

DYNAMIC VOLUME COUNT 

One of the things that can happen is that you can allow a job to start
by 
enabling a smaller allocation on a volume with less than the needed
space. 
  The job runs and then fails when it runs out of space on that volume. 
One point of view in that case is that you've wasted the run time and 
resources used by that failed job.  I think what you're really trying to

do here is enable the job to start and then have it run to a good EOJ
and 
in order to do that, you'll still need to provide all the space the job 
needs - which you can do by allowing the reduced allocation and
increasing 
the volume count.

This is the same kind of actions a product like Stop-X37 takes.

HTH's - ddk



************************************************************************
**************
This e-mail message and all attachments transmitted with it may contain
legally privileged and/or confidential information intended solely for
the use of the addressee(s). If the reader of this message is not the
intended recipient, you are hereby notified that any reading,
dissemination, distribution, copying, forwarding or other use of this
message or its attachments is strictly prohibited. If you have received
this message in error, please notify the sender immediately and delete
this message and all copies and backups thereof.

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

NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
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

Reply via email to