> When a DB2 ASID requests a dump, the initial allocation request is larger > than a MOD-3. > Currently we just reply 'D' to trash the dump request. > > What controls are available in z/OS 1.6 to set a maximum primary/secondary > allocation for dumps? > > SMS Dataclass? Parmlib ?
Dynamic dump allocation gives you plenty of control over the allocation and you can use SMS. Those things are documented. However, why in this day and age are you thinking in terms of mod-3 devices? That is an utterly paltry 2.5GiB. I have a 4GiB flash drive sitting in my pocket right this second. The system takes dumps so the vendor can analyze and correct problems. It is in your own best self interest to make sure that it's possible for the vendor to do that effectively. You don't want to lose or corrupt the data in that DB2 database now do you? Carve off a pool of (much) larger custom volumes and let SVC dump processing use that. You don't have to let it take a gazillion dumps, but you really ought to get a complete dump for a problem otherwise you're risking a lot more than a few GiB of disk space. CC ---------------------------------------------------------------------- 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
