That tells me that you allocated them correctly. The question is whether DSF actually wrote CP-compatible blocks (which are different than what minidisks use) on every cylinder. That¹s one of the reasons why I always add paging areas in full packs, and always run DSF on them, even if they¹re brand new or already been formatted by Some Other OS.
>From the other conversation, you may have ended up with a minidisk overlapping a paging area. In either case, you should reformat the disks in question next time you IPL and have the system down for any period (can¹t do it while it¹s up if pages have actually been written to the paging areas; CP doesn¹t really give you an easy way to force migration of pages off a pack if they are still referenced by something). Taking the problem volumes offline and bringing the system up to the point of having OPERATOR logged in but before AUTOLOG1 comes up would be one way to safely reformat them without going to standalone DSF. As Marcy said, though: you are very light on paging space for guests of the size you describe. You probably should wheedle some more paging packs from your storage guys. --d b On 2/10/09 5:23 PM, "Martin, Terry R. (CMS/CTR) (CTR)" <[email protected]> wrote: > Hi > > Yes, I formatted them using CPFMTXA. The output from the format showed that 0 > 0 PERM and 1 END PAGE. > > > Thank You, > > Terry Martin > Lockheed Martin - Information Technology > z/OS & z/VM Systems - Performance and Tuning > Cell - 443 632-4191 > Work - 410 786-0386 > [email protected] > > > From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf > Of David Boyes > Sent: Tuesday, February 10, 2009 2:56 PM > To: [email protected] > Subject: Re: Paging > > Did you format the new paging disks with DSF or CPFMTXA before you attached > them to SYSTEM? If you didn't, then that's the cause of the problem. > > received the following error just before the guest came down: >> > >> > HCP415E Six continuous paging errors have occurred on DASD nnnn volume >> > >> > volser. >> > >> > This error occurred on the two page packs that I just added yesterday >> > (VP51A0 and VP51A1). I believe I followed the appropriate steps to >> > defining and starting the new page data sets. >
