Also, if doing this on the fly, you need to find a free slot with QUERY CPOWNED and then add the volume with DEFINE CPOWNED. Then and only then attach the volume to SYSTEM. Defining cyl 0 as perm is also unnecessary for modern releases of VM.
-----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Richard Corak Sent: Thursday, June 17, 2010 12:05 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: PGT004 MESSAGE No need for CP START DASD rdev PAGE CP START DASD is nothing more than undrain. If you haven't done DRAIN, don't bother with START. Edits to Mike's sequence: - Find an available DASD volume accessible to your z/VM system. - Find (or decide on) a label "volser" for the soon-to-be paging volume - Run CPFMTXA against that DASD, formatting the whole thing, assigning the label as decided above, and allocating - Cylinder zero as PERM, and - 1-END as PAGE. - DETACH that device from the ID that formatted/allocated - Update your "SYSTEM CONFIG" file on MAINT's CF1 disk using whatever procedures you already use. E.g. - Find a free CP_OWNed 'SLOT', and change that to match the new page DASD volser, and mark that as OWNED, e.g. if "volser" is "VMPG01" and slot 11 is not already assigned CP_Owned Slot 11 VMPG01 OWN - File "SYSTEM CONFIG", run CPSYNTAX against the updated "SYSTEM CONFIG" file to check for errors. - As long as there are no errors, bring the volume online to CP by entering: CP ATT rdev SYSTEM Richard Corak
