Whatever core your LPAR has needs to be backed by paging space 1X. If you want to take a Stand Alone Dump, you need another copy of the core and the paging space so 3X.
When it goes to write, it spreads the writes over all files. When one write gets done, it gets another CI. On Mon, Jul 6, 2015 at 12:12 AM, R Hey <[email protected]> wrote: > Hi, > > A site uses different size local page DS. > say most are 200K TRK , but 1 is 10K TRK. > normal : 15% 70% used > problem: 60-70% 95% > > I said it's best to use same-size DS & have usage of under 30% (each DS), but > it was rejected as old-recommendation. > > Sometimes they get IRA205I. > > MSG actually says: > ... When utilization exceeds 30%, the slot allocation algorithms become less > efficient, > and may degrade I/O performance. > > Is this ROT still apply: > same size local PAGE DS > < 30% used > > Is there any HW feature (DASD/HPAV/ton-of-cache/ton-of-this/that/etc), where > this ROT should be ignored? > > TIA, > Rez > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
