The result as belows.
cp q v 123 HCPQVD040E Device 0123 does not exist Ready(00040); T=0.01/0.01 17:43:24 dirm cp q v 123 DVHXMT1191I Your CP request has been sent for processing. Ready; T=0.01/0.01 17:43:28 DVHREQ2288I Your CP request for MAINT at * has been accepted. DVHCMS3868I HCPQVD040E Device 0123 does not exist DVHREQ2289E Your CP request for MAINT at * has failed; with RC = 40. CMS On Wed, May 27, 2009 at 5:35 PM, Jonathan R Nolting <jrnol...@us.ibm.com> wrote: > From MAINT issue: > > CP Q V 123 > Dirm cp q v 123 > > And provide results. > > Have you tried shutting down Dirmaint and logging off MAINT. Then restart > DIRMAINT? > > ----------------- > Jon Nolting - IBM zITA > jrnol...@us.ibm.com > 425 281 5750 (cell) > Sent from my BlackBerry Handheld. > > > ----- Original Message ----- > From: Yoon-suk Cho [isem...@gmail.com] > Sent: 05/27/2009 04:20 PM ZE9 > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Any idea? Dirmaint error by detach 123 disk(540RES) > > > > thanks for your time. > > Already , ommitted the 123 minidisks so, I can't update directory file > by dirm command like this 'dirm for maint replace'. > > I can't found other guests who linked to 123 disk except dirmaint. How > can i find it? > I think If i can attach the 123 minidisk(540RES) in dynamically, > dirmaint working correctly. > When dirmaint got a update command from maint, it seems to refer to > 123 disks of maint that i think. > > http://www.mail-archive.com/ibmvm@listserv.uark.edu/msg19288.html > > > As following above email, we can use this command 'DEFINE MDISK AS 123 > 0 END 540RES' . > But, I got a error message as belows. > > define mdisk as 123 0 end 540res > HCPDEF003E Invalid option - MDISK > Ready(00003); T=0.01/0.01 16:13:41 > > It might be change the 'DEFINE' option in 5.x except help page. > Plz. Help this. It really important product system. > > > Best Regards. > > ------------------------ > q v dasd > DASD 0190 3390 540RES R/W 107 CYL ON DASD DE00 SUBCHANNEL = 0007 > DASD 0191 3390 540RES R/W 175 CYL ON DASD DE00 SUBCHANNEL = 0009 > DASD 0193 3390 540W01 R/W 167 CYL ON DASD DE03 SUBCHANNEL = 0029 > DASD 0194 3390 540RES R/W 333 CYL ON DASD DE00 SUBCHANNEL = 0015 > DASD 019D 3390 540W01 R/W 146 CYL ON DASD DE03 SUBCHANNEL = 002A > DASD 019E 3390 540W01 R/W 250 CYL ON DASD DE03 SUBCHANNEL = 002B > DASD 0201 3390 540RES R/W 22 CYL ON DASD DE00 SUBCHANNEL = 000A > DASD 02A2 3390 540RES R/W 6 CYL ON DASD DE00 SUBCHANNEL = 0012 > DASD 02A4 3390 540RES R/W 6 CYL ON DASD DE00 SUBCHANNEL = 0013 > DASD 02A6 3390 540RES R/W 6 CYL ON DASD DE00 SUBCHANNEL = 0014 > --------------------- > > > > > > > On Wed, May 27, 2009 at 2:10 PM, Alan Altmark <alan_altm...@us.ibm.com> wrote: >> On Wednesday, 05/27/2009 at 12:53 EDT, Yoon-suk Cho <isem...@gmail.com> >> wrote: >> >>> This is my really mistake things. I detached the 123 minidisk by maint >>> user and then issuce this command 'dirm for maint replace'. >>> Dirmaint try to refer 123 minidisk to update DIRECTORY file as following >> errors. >>> Of course, I try to re-attach 123 minidisk (540RES) by maint to update >>> directory file. Already it has been detached, however, the >>> 123minidisk. >>> Dirmaint need 123 minidisk (540RES) and Maint Can't attach 123 >>> minidisk because dirmaint is not available such as DEADLOCK. >>> >>> How can I fix this? Please. Help. >> >> The easiest way is to: >> 1. DETACH MAINT 123 from whoever has it linked (if anyone) >> 2. FORCE and XAUTOLOG DIRMAINT >> >> Alan Altmark >> z/VM Development >> IBM Endicott >> >
