Taken together, the allocation as a spool or page extent an the inclusion in a defined MDISK extent is pretty strong protection and makes the separate allocation of cylinder 0 somewhat redundant. But if you want to do that, it does not prohibit you from allocating the space as PAGE or SPOL in CPFMTXA. The definition of the minidisk is unrelated to the allocation bit map.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern > Sent: Tuesday, June 24, 2008 2:58 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Allocating Cyl Zero as Perm (Was: Performance > toolkit under zVM 5.3) > > Yes, I also have placeholders for $PAGE$, $SPOOL$, $TDISK$, > $DIRECT$ and MVSDASD. But that is a different "best practices" item. > > /Tom Kern > > Schuh, Richard wrote: > > That is why I said, "Granted, for all other devices, it is best to > > allocate cylinder 0 as perm. There you have a guarantee that the > > volume label will get wiped out if that cylinder is > included in a user > > minidisk." > > > > If you are trying to wipe out the label on an active page or spool > > volume that is so allocated from 0 to end, you must work at > it and it > > must be intentional. Also, do you not create minidisks for > the areas > > allocated to PAGE or SPOL? That would include cylinder 0, > so you would > > still have that protection. > > > > > > Regards, > > Richard Schuh > > >
