Unless the Linux admin takes specific action to label the disk with the
current label, it will be overwritten with the Linux volume name, and will
then not be available the next time the userid is logged out and back in.
Two courses of action: Either change the minidisk to exclude cylinder zero,
Subject: Re: DASD second level
Unless the Linux admin takes specific action to label the disk with the
current label, it will be overwritten with the Linux volume name, and
will
then not be available the next time the userid is logged out and back
in.
Two courses of action: Either change the minidisk
Yes, to 3338 is 3339 but MDISK 3338 is for 3338.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Macioce, Larry
Sent: Monday, June 25, 2007 12:50 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
I'm coming in a bit
to
3338 that IS 3339 cyls. Did I miss something?
mace
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of RPN01
Sent: Monday, June 25, 2007 11:04 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
Unless the Linux admin takes specific
[mailto:[EMAIL PROTECTED]
On
Behalf Of Macioce, Larry
Sent: Monday, June 25, 2007 12:50 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
I'm coming in a bit late but from what I see, if you go from to
3338 that IS 3339 cyls. Did I miss something?
mace
-Original Message
On: Mon, Jun 25, 2007 at 01:18:58PM -0400,Anne Crabtree Wrote:
} how about i just say END!
That should work fine.
--
Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353
Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67
Canines:Val, Red,
Hello Anne,
Just some things that popped into my mind.
VMTEST 191 and looks like this:
USER WVLNX30 WVLNX30 512M 1024M G
..snip..
DEDICATE 0A81 163C
DEDICATE 067E 165F
VMTEST's USER DIRECT on first level:
..snip..
MDISK 163C 3390 000 10017 LX163C MR
MDISK 165F 3390 000 3338 LX165F MR
The
I have a directory entry VMTEST for a second level VM. (z/vm v5r1)
I am trying to put a Linux guest on second level. I have DEDICATE
statements for the dasd it needs but second level does not see this
dasd:
HCPLNM108E VMTEST 163C not linked; volid LX163C not mounted
HCPLNM108E VMTEST 165F not
Anne,
If you put:
User_Volume_Include *
in your SYSTEM CONFIG of your 2nd level system, then all the available
volumes will be attached to system at IPL time.
Ronald van der Laan
-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Anne Crabtree
Sent: Friday, June 22, 2007 8:40 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DASD second level
I have a directory entry VMTEST for a second level VM. (z/vm v5r1) I am
trying to put a Linux guest on second
, or attach those
volumes to SYSTEM so that the link statements can work.
David Wakser
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Anne Crabtree
Sent: Friday, June 22, 2007 8:40 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DASD second level
I
det 163c from system
HCPDTS121E DASD 163C not attached to system
Ready(00121); T=0.01/0.01 09:10:47
det 163c from all
Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Bill Munson
Sent: Friday, June 22, 2007 9:03 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
Anne,
You need to detach the volumes from SYSTEM on the 1st level VM That way
they can be attached
: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Bill Munson
Sent: Friday, June 22, 2007 9:03 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
Anne,
You need to detach the volumes from SYSTEM on the 1st level VM That way
they can be attached to VMTEST to be used
-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Bill Munson
Sent: Friday, June 22, 2007 9:03 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
Anne,
You need to detach the volumes from SYSTEM on the 1st level VM That
way
they can be attached
In the second level system, do a Q DASD ALL and look at the results; Do
you see your disks there, and what is their state?
In the first level system, do a Q DASD label for the two disks in
question, and see what their state is there.
There has to be a reason that the disk isn't finding its way
Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Bill Munson
Sent: Friday, June 22, 2007 9:03 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
Anne,
You need to detach the volumes from SYSTEM on the 1st level VM That
way
they can be attached to VMTEST to be used 2nd level
[EMAIL PROTECTED]
ext. 40441
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Anne Crabtree
Sent: Friday, June 22, 2007 8:50 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DASD second level
I didn't quite state that right. I'm signed onto
Good idea, there is one little problem though: CMS can be kille at two
places, and if it does, the EXEC will come to an end before the second level
VM is started.
The trick is to combine next 3 commands in one:
'TERMINAL CONMODE 3270'
'SET MACHINE ESA'
'IPL 711C CLEAR LOADPARM 0009'
should
cool
thanx
munson
Kris Buelens wrote:
Good idea, there is one little problem though: CMS can be kille at two
places, and if it does, the EXEC will come to an end before the second
level VM is started.
The trick is to combine next 3 commands in one:
'TERMINAL CONMODE 3270'
'SET MACHINE
Subject: Re: DASD second level
cool
thanx
munson
Kris Buelens wrote:
Good idea, there is one little problem though: CMS can be kille at two
places, and if it does, the EXEC will come to an end before the second
level VM is started.
The trick is to combine next 3 commands in one:
'TERMINAL
On 6/22/07, Bill Munson [EMAIL PROTECTED] wrote:
actually here is an easy way to ipl a 2nd level system
there are no DEDICATE statements in the Directory for VMTEST
Your approach requires that the 2nd level system has also class B.
While not as dangerous as class A, it will eventually bite
22 matches
Mail list logo
