On Tue, 10 Feb 2009 15:25:58 -0600, Dave Jones <d...@vsoft-software.com> wrote:
>Hi, Terry. > >Martin, Terry R. (CMS/CTR) (CTR) wrote: >> Hi >> >[snp....] >> >> >> q alloc page >> EXTENT EXTENT TOTAL PAGES HIGH % >> VOLID RDEV START END PAGES IN USE PAGE USED >> ------ ---- ---------- ---------- ------ ------ ------ ---- >> 530PAG 5104 1 3338 600840 301180 594838 50% >> VP517A 517A 1 3338 600840 338482 600840 56% >> VP517B 517B 1 3338 600840 334685 600838 55% >> VP5198 5198 1 3338 600840 337162 600839 56% >> VP5199 5199 1 3338 600840 333914 600840 55% >> VP5109 5109 0 3338 601020 301240 598846 50% >> VP51A0 51A0 1 3338 600840 75804 76125 12% >> VP51A1 51A1 1 3338 600840 76068 76734 12% >> ------ ------ ---- >> SUMMARY 4694K 2049K 43% >> USABLE 4694K 2049K 43% >> >You have noticed, I hope, that for volume VP5109, the paging area starts on cylinder 0, >and not cylinder 1? Generally, I prefer to leave cylinder 0 for CP's exclusive use. > > >-- >DJ > >V/Soft > z/VM and mainframe Linux expertise, training, > consulting, and software development >www.vsoft-software.com >======================== ========================= ======================== Having cylinder 0 allocated for paging space is not a problem (as long as it's properly formatted). The only reason we recommend not to do it is t o avoid any confusion for the one instance where cylinder 0 would be a prob lem (and that is tdisk). Having cylinder 0 allocated for paging is not contributing to any of the observed symptoms (if it was properly formatte d first). - Bill Holder, z/VM Development, IBM Endicott
