>I assume you are referring to MAXSPACE. I don't know of any setting that >documents how to "increase the size of DUMPSRV dataspaces" (although >that must be how the virtual storage maximum set via MAXSPACE is >implemented today).
Sorry, yes of course I mean MAXSPACE. Guess I have extracted too many dumps from those dataspaces in an sadump. Init&Tuna says "Specifies the maximum amount of virtual storage that SVC dump can use to capture volatile virtual storage data, summary dump data, and component- specific data before writing the dump to DASD. The default value is 500 megabytes. " And while we're on the OMVS topic, we had an 'sadump option' discussion a while back. After that I explicitly specified that OMVSs dataspaces (containing the file information for USS users, for instance) are also always included in sadump. One would think that sadump would do it on it's own by now, without explicitly being told! That's not the case, according to the 1.10 books. And a good thing I did that, too, as we had a case where WAS was unable to start due to a corrupted HFS owned by OMVS.... (And the dump captured by DUMPSRV could not be written out, either, but was in the sadump I took). Regards, Barbara ---------------------------------------------------------------------- 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
