Re: Is it bad to make one zlinux running on 2 z/vm?
On Sat, Jul 25, 2009 at 7:30 AM, O'Brien, Dennis L wrote: > Sunny, > > If you really have two guests up at the same time, using the same DASD, I > can’t believe that one or both of them haven’t crashed. > > > > We have the same guests defined on two z/VM systems. We use the XLINK > feature of CSE to make sure that only one of them can get the DASD > read/write. If the second one is accidentally logged on, some code in > PROFILE EXEC will discover that the DASD is read-only, message the operator, > and log off. > I really looking for the manual to setup linux system on two z/VM. Could you give me the detail manual ? > > > > Dennis O’Brien > > > > "That's one small step for (a) man, one giant leap for mankind". -- Neil > Armstrong, 20 July 1969, Sea of Tranquility > > > > > > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of sunny...@wcb.ab.ca > Sent: Friday, July 24, 2009 15:20 > To: IBMVM@LISTSERV.UARK.EDU > Subject: [IBMVM] Is it bad to make one zlinux running on 2 z/vm? > > > > We sometimes accidently turn on one linux guest on two z/VM systems. > Both z/VM system has their own DIRMAINT and RACF. No RSCS. > We add the same guest direct file to two z/VM so it makes the flexibility to > boot. > > Is it bad to make one zlinux running on 2 z/vm? > So far we didn't get any complaint. But I can't expain myself how. It has > same ip address and the same dasds. > > sunny > > > > This message is intended only for the addressee. It may contain privileged > or confidential information. Any unauthorized disclosure is strictly > prohibited. If you have received this message in error, please notify us > immediately so that we may correct our internal records. Please then delete > the original email. Thank you. (Sent by Webgate1)
Re: Any idea? Dirmaint error by detach 123 disk(540RES)
I found it in SYSTEM CONFIG file. it has been disabled.(z/VM 5.4) Do i need IPL of z/VM after enable privclass ? Regards. On Thu, May 28, 2009 at 9:25 PM, Alan Altmark wrote: > On Thursday, 05/28/2009 at 02:21 EDT, Kris Buelens > wrote: >> Strange that MAINT cannot issue SET PRIVCLASS > > SET PRIVCLASS has to be enabled in SYSTEM CONFIG via FEATURES ENABLE > SET_PRIVCLASS. > > Alan Altmark > z/VM Development > IBM Endicott >
Re: Any idea? Dirmaint error by detach 123 disk(540RES)
Thanks for your help. I re-defined the 123 minidisk to maint and then fix the Dirmaint in successfully. First, I tried to put the PRIVCLASS to DIRMAINT user by maint. It was not available , however, option as following errors. SET PRIVCLASS DIRMAINT +A Invalid option - PRIVCLASS Maint need the 123 minidisk (540RES) and dirmaint refer to the disk to update dictory. So, I put the DEVMAINT function(?) to MAINT. SETVMDBK MAINT DEVMAINT and issue command 'CP DEFINE MDISK 123 0 END 540RES' . it was successfully defined. after that, I need more time to fix dirmaint. It was not difficult job. really thanks again. On Wed, May 27, 2009 at 6:23 PM, Kris Buelens wrote: > I just tested an easy bypass. I've got an SETVMDBK EXEC that allows a > privileged user to zap certain bits in the VMDBK of logged on users. > This SETVMDBK has proven to work surely up to z/VM 5.4. > > From MAINT: > - XAUTOLOG DIRMAINT > - SET PRIVCLASS DIRAMINT +A (if it hasn't class A already) > - SETVMDBK DIRMAINT DEVMAINT > - DIRM CP DEFINE MDISK 123 0 END 540RES > Et voila I'll send SETVMDBK is a separate email (a bit too long > to imbed here) > > 2009/5/27 Yoon-suk Cho >> >> I try to 'DEFINE MDISK as 123 0 END 540RES' by maint. but I got a >> error msg like this. >> >> >> define mdisk as 123 0 end 540res >> HCPDEF003E Invalid option - MDISK >> Ready(3); T=0.01/0.01 16:13:41 >> >> It was successfully defined by lglopr user. >> and , I tried shutting down dirmaint and logging off MAINT, the >> restart dirmaint user. >> But. Same problem exist. I think really dirmaint need 123 minidisk of maint. >> >> How about this way? >> >> - disable the dirmaint >> - make user backup file >> - edit the 'USER DIRECT C' under 2C2 disk to 'MDISK 0123 3390 000 END 540RES >> MR' >> - issue command 'DIRECTXA USER DIRECT C' >> - fix the dirmaint config file for maint. >> - conversion 'USER DIRECT C' file to use the dirmaint. >> >> >> we need attach the 123 disk to maint. so we are using the DIRECTXA >> command first. >> and then conversion 'USER DIRECT C' file to use dirmaint. >> >> Do you known that way in detail? >> >> >> >> >> On Wed, May 27, 2009 at 5:46 PM, Rob van der Heij wrote: >> > On Wed, May 27, 2009 at 10:35 AM, Jonathan R Nolting >> > 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? >> > >> > If MAINT still had the 123 and it is not in the online directory >> > anymore, then logging off is not a wise approach. But you can get that >> > back. >> > Normally MAINT has the DEVMAINT option, so you should be able to issue >> > the DEFINE MDISK to get the 0123 full pack linked. Then get the >> > yesterday's user backup from DIRMAINT and use MAINT to bring that >> > online. This will give you a MAINT 123 again that DIRMAINT can link. >> > >> > Rob >> > > > > > -- > Kris Buelens, > IBM Belgium, VM customer support >
Re: Any idea? Dirmaint error by detach 123 disk(540RES)
I try to 'DEFINE MDISK as 123 0 END 540RES' by maint. but I got a error msg like this. define mdisk as 123 0 end 540res HCPDEF003E Invalid option - MDISK Ready(3); T=0.01/0.01 16:13:41 It was successfully defined by lglopr user. and , I tried shutting down dirmaint and logging off MAINT, the restart dirmaint user. But. Same problem exist. I think really dirmaint need 123 minidisk of maint. How about this way? - disable the dirmaint - make user backup file - edit the 'USER DIRECT C' under 2C2 disk to 'MDISK 0123 3390 000 END 540RES MR' - issue command 'DIRECTXA USER DIRECT C' - fix the dirmaint config file for maint. - conversion 'USER DIRECT C' file to use the dirmaint. we need attach the 123 disk to maint. so we are using the DIRECTXA command first. and then conversion 'USER DIRECT C' file to use dirmaint. Do you known that way in detail? On Wed, May 27, 2009 at 5:46 PM, Rob van der Heij wrote: > On Wed, May 27, 2009 at 10:35 AM, Jonathan R Nolting > 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? > > If MAINT still had the 123 and it is not in the online directory > anymore, then logging off is not a wise approach. But you can get that > back. > Normally MAINT has the DEVMAINT option, so you should be able to issue > the DEFINE MDISK to get the 0123 full pack linked. Then get the > yesterday's user backup from DIRMAINT and use MAINT to bring that > online. This will give you a MAINT 123 again that DIRMAINT can link. > > Rob >
Re: Any idea? Dirmaint error by detach 123 disk(540RES)
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 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(3); 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 wrote: >> On Wednesday, 05/27/2009 at 12:53 EDT, Yoon-suk Cho >> 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 >> >
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(3); 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/W107 CYL ON DASD DE00 SUBCHANNEL = 0007 DASD 0191 3390 540RES R/W175 CYL ON DASD DE00 SUBCHANNEL = 0009 DASD 0193 3390 540W01 R/W167 CYL ON DASD DE03 SUBCHANNEL = 0029 DASD 0194 3390 540RES R/W333 CYL ON DASD DE00 SUBCHANNEL = 0015 DASD 019D 3390 540W01 R/W146 CYL ON DASD DE03 SUBCHANNEL = 002A DASD 019E 3390 540W01 R/W250 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 wrote: > On Wednesday, 05/27/2009 at 12:53 EDT, Yoon-suk Cho > 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 >
Any idea? Dirmaint error by detach 123 disk(540RES)
Hi. all . 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. Regards. == DVHREQ2288I Your REPLACE request for MAINT at * has been accepted. DVHBIU3450I The source for directory entry MAINT has been updated. DVHBIU3424I The next ONLINE will take place immediately. DVHDRC3451I The next ONLINE will take place via delta object directory. DVHDRC3212E Unexpected RC= 28, from: DVHUPDIR 123 1DE DVHDRC3458I Directory updates will be brought online running DIRECTXA DVHDRC3458I against full source directory. 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 DVHBIU6219E Attempted DIRECTXA failed. DVHSHU2194T Automatic shutdown/restart DVHSHU2194T initiated. Machine= DIRMAINT, DVHSHU2194T caller= DVHBBIUP, reason= DIRECTXA DVHSHU2194T FAILURE DVHSHU2196I The failing command will be retried. DVHSHU2197I The DIRMAINT machine is attempting to DVHSHU2197I re-IPL and restart. DVHPRO2008I ROLE = DIRMAINT DVHREQ2288I Your REPLACE request for MAINT at * has been accepted. DVHBIU3450I The source for directory entry MAINT has been updated. DVHBIU3424I The next ONLINE will take place immediately. DVHDRC3451I The next ONLINE will take place via delta object directory. DVHDRC3212E Unexpected RC= 28, from: DVHUPDIR 123 1DE DVHDRC3458I Directory updates will be brought online running DIRECTXA DVHDRC3458I against full source directory. 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 DVHBIU6219E Attempted DIRECTXA failed. DVHSHU2194T Automatic shutdown/restart DVHSHU2194T initiated. Machine= DIRMAINT, DVHSHU2194T caller= DVHBBIUP, reason= DIRECTXA DVHSHU2194T FAILURE DVHSHU2195I The failing command has been purged. DVHSHU2197I The DIRMAINT machine is attempting to DVHSHU2197I re-IPL and restart. DVHPRO2008I ROLE = DIRMAINT
