Steve (et al) - Thats for the input. We've bumped the volume limit up to 10 for now, which should solve the few space abends we've had recently. One reason we thought of not to increase it further is that we do not want a run-away process to be able to extent to more than 10 volumes. We have had that happen. And we try to run our SMS pools downwards of 50% utilization, so extenting to 10 volumes would be a large file, for us anyway.
Thanks again. > > Generally, there's no particular reason not to increase the number of >ADDVOLs that SRS is allowed to do. I know of a number of shops that set it >to 59, which is the MVS limit. The only consideration might be something >like an application which formats, say, a VSAM RRDS, and depends upon an >out-of-space return code to know when to stop formatting. Otherwise, it's >not unreasonable to set it to 59. (Setting the SMS data class DVC value to >59 isn't such a good idea, though, as the SMS add-volume code, unlike SRS, >will actually use 59 slots in the TIOT at allocation time, so it may be >possible to run into TIOT-size issues if DVC is used for a lot of datasets). > Jeffrey Deaver, Senior Analyst, Systems Engineering 651-665-4231 ---------------------------------------------------------------------- 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
