If it's all perm space as you suggest you could just put it as User_Volume_List 510W01 in system config it should not be defined as cp_owned, just a user_volume. Try using Cpfmtxa (help to see the usage). Page, spool, tdisk, parm, for cp_owned, slotted, everything else can be user volumes.
Regards, Richard Feldman Senior IT Architect Kelly, Douglas / Westfair Foods Ltd. Ph:(403)291-6339 Fax:(403)291-6585 -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Anne Crabtree Sent: Thursday, November 30, 2006 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: PERM space I need to add a 510W01 volume to z/vm as PERM space and I already have the following defined in SYSTEM CONFIG: CP_Owned Slot 1 510RES CP_Owned Slot 2 510SPL CP_Owned Slot 3 510PAG CP_Owned Slot 4 510PG1 CP_Owned Slot 5 510PG2 CP_Owned Slot 6 510PG3 Any problem with just adding it as Slot 7? Was planning on do this under MAINT on the fly: CPVOL FMT UNIT(1748) RANGE(0000,3338) TYPE(PERM,0000,3338) VFY(510W01) DEFINE CPOWNED SLOT 7 510W01 ATT 1748 MAINT CPVOL ALLOC UNIT(1748) RANGE(0000,3338) TYPE(PERM,0000,3338) VFY(510W01) DET 1748 MAINT ATT 1748 SYSTEM Just want to make sure this scenario will work and not hurt anything...
