As the documentation (CP Commands) says for DEFINE MDISK: Privilege Class: A
The user must be the primary system operator or the user's OPTION directory statement must include the DEVMAINT option. The user must have the appropriate ESM authorization if an ESM is installed. 1. ... Use this command only for disaster recovery because it provides access to any area of a DASD volume without requiring additional authorization. ... 4. Minidisks should not be defined on PAGE, SPOL, TDSK, or on DRCT allocation areas. Your gun, your bullet, your foot! On Thu, 20 Oct 2005 07:35:21 -0500, Berry van Sleeuwen <[EMAIL PROTECTED]> wrote: >Helo Kris, > >Do you want to place a bet on this? > >Take a look at this. My residentpack is VMSB00, it contains a default VM >installation, just as it is on the system DDR. The DRCT is on cylinder 1-20. > >def mdisk 001 1 20 vmsb00 >DASD 0001 DEFINED >Ready; T=0.01/0.01 14:01:22 >q v dasd >DASD 0001 3390 VMSB00 R/W 20 CYL ON DASD 30E6 SUBCHANNEL = 0008 >DASD 0190 3390 VMSB00 R/O 107 CYL ON DASD 30E6 SUBCHANNEL = 0004 >DASD 0191 3390 VMSB02 R/W 20 CYL ON DASD 30E8 SUBCHANNEL = 0007 >... > >So now I have a R/W disk on the directory extent. I agree, it cannot >overlap SPOOL, PAGE and TDISK. > >What is a bit disturbing is that it is possible to get the directory extent >in R/W and that the SYSWRM and SYSCKP are PERM and therefore available for >minidisks. It would be nice to have CP protect these a bit more. I don't >mind overlapping the PARM disks or my TDISK area. It is not as destructive >for my VM as overlapping the warmstart area or the directory extent. OK, we >do have those areas protected by a minidisk (or we supposed to have...) but >overlapping the warmstartarea is a disaster waiting to happen. Couldn't >they be protected in the same way as the SPOOL, PAGE and TDISK? By CP >instead of a minidisk in the directory. > >Regards, Berry. > >On Wed, 19 Oct 2005 11:17:44 +0200, Kris Buelens <[EMAIL PROTECTED]> >wrote: >
