The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on 11/06/2008 07:52:20 PM:
> I'm seeing a strange problem with z/VM 5.4. On my 2nd level z/VM 5.4 > installation system, I have the predefined PARM disks, MAINT CF1, CF2, > and CF3. I also have the predefined MAINT 123 MDISK for the 540RES > volume. The problem that I am seeing is that, originally, from MAINT, I > could not get a write link to 540RES to load the directory using > DIRECTXA and the pre-defined directory without doing a CPRELEASE A, B, > and C. I still cannot even after redefining the MAINT 123 disk to the > size of the DRCT space. CP Q ALLOC MAP shows that the directory space > is cylinders 1-20. An ICKDSF CPVOL LIST shows the following allocation: > > CYLINDER ALLOCATION CURRENTLY IS AS FOLLOWS: > TYPE START END TOTAL > ---- ----- --- ----- > PERM 0 0 1 > DRCT 1 20 20 > PERM 21 38 18 > PARM 39 158 120 > PARM 159 278 120 > PARM 279 398 120 > PERM 399 3338 2940 > > so 540RES appears to be correctly allocated. > > As you might imagine, this causes all kind of problems with DIRMAINT, > which I installed and enabled on the 2nd level system. > > Has anyone seen anything like this before? It does not seem to > something that is related to the CP NUC because I copied CPLOAD MODULE > to my test lpar and it works as expected. > Is the "real" volume just a mod-3? MAINT's 123 should be defined as a full-volume MW minidisk. If it's in the directory as "mdisk 123 3390 0 3339 540res mw" and the actual disk is larger, then it won't qualify as a full-pack mini and I'd expect the results you're seeing. That is, CP won't allow you write access to a non-full-pack disk which overlays a STABLE link, which those to the parm disks are. Try changing the allocation to "0 END".
