Re: Spam (7.802):Re: Page Data Set Sizes and Volume Types

2014-12-04 Thread Joel Ewing
With current emulated DASD and PAVs, performance is probably no longer an issue, but I believe multiple page data sets on one volume is still a potential availability issue: You wouldn't want failure of a single emulated drive to compromise two different systems at the same time, and I seem to

Re: Spam (7.802):Re: Page Data Set Sizes and Volume Types

2014-12-04 Thread Bob Shannon
With current emulated DASD and PAVs, performance is probably no longer an issue, but I believe multiple page data sets on one volume is still a potential availability issue: You wouldn't want failure of a single emulated drive to compromise two different systems at the same time, and I

Re: Spam (7.802):Re: Page Data Set Sizes and Volume Types

2014-12-04 Thread Staller, Allan
A couple of recent threads indicated the 30% rule is still valid No info on z/Flash as yet.. snip It may be time to revisit old paging ROTs. Does anyone have a double or triple digit paging rate anymore? Is the 30% rule still valid? (We completely ignore it). Does zFlash obviate the old

Re: Spam (7.802):Re: Page Data Set Sizes and Volume Types

2014-12-04 Thread Shane Ginnane
On Thu, 4 Dec 2014 18:46:38 +, Bob Shannon wrote: Unless the recommendation has changed, there should only be one page dataset per MVS volume. IIRC MVS remembers the last head position and performance suffers when the head has moved. That apparently all changed with the demise of the

Re: Spam (7.802):Re: Page Data Set Sizes and Volume Types

2014-12-04 Thread R.S.
W dniu 2014-12-04 o 19:28, Joel Ewing pisze: With current emulated DASD and PAVs, performance is probably no longer an issue, but I believe multiple page data sets on one volume is still a potential availability issue: You wouldn't want failure of a single emulated drive to compromise two