Hi all, I thought I was getting the hang of using DIRMAINT, but now I think I
shot myself in the foot. I am wondering now how to fix the wound. Yesterday I made some changes that appeared to be successful. After some searches of the list archives, I thought I did something good but now I a m thinking it may be what is causing my problem. Backing up, I had followed the steps in Chapter 4 of Getting Started with Linux on System z. I ran a DIRMAP report before I started making changes and noted that several items that had overlaps also had 3390 (3390-01) lengths associate d with them. Since I only have 3390-09s, I thought the USER files should reflect that. So... I changed $SPOOL$, $PAGE$, MAINT and SYSDUMP1 0123 (the last two which I am assuming came out of my EXTENT CONTROL definitions) to all have the 3390-09 lenghths. Those overlaps all went away. THere was something called .DRCT. from 1-20 on 540RES which still had on overlap listed when I was done, but it was there to start with so I thought nothing of it. All the updates seemed to work as far as I could tell. Today I reipled to test some changes I made in AUTOLOG1 PROFILE suggested by the RH Virtualization Cookbook. I did a dirmaint get and made some changes for another user, and tried to do a replace. The scene is not good; I am getting errors: DVHDRC3212E Unexpected RC= 28, from DVHUPDIR 123 1DE : : DVHDRC6213E z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 4.0 DVHDRC6213E HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND DVHDRC6213E HCPDIR784E I/O ERROR 0123 DEVICE NOT ATTACHED DVHDRC6213E EOJ DIRECTORY NOT UPDATED after which DIRECTXA attempts to re-IPL and restart adn the whole error process happens again. I could restore the 540RES volume, but now that I have made this problem for myself, it might serve me better to know how to fix it(if there is a way).I could try to undo my changes, but I would really like to know how to debug this problem. Since I see the virtual address 123 in the error message, I am led to believe that it might have something to do with the DASD size changes I made that relate to virtual device 123. I could undo them all, but I would rather find out if this is the right path to take. I am concerned that they might not get updated if I DO try to change them i f DIRMAINT is not working correctly. Since I am just starting out, this is unfortunately my first level system . Someone suggested getting a second level up and running, but I did not do that before messing with DIRMAINT.
