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 to exclude cylinder zero, making it begin on 001 and run for 3338, or have the Linux admin use the current label when he formats the disk (I don't remember seeing this as an option in the install process, but I wasn't looking for it, either), or let him format the disk, then discover the new label, and change all your references to match it. Note that it may not be unique if you have several Linux guests using the same virtual disk addresses. But at least you're in control of what addresses you present to the Linux guest... Option one is the simplest and most reliable, if you intend to run Linux as a guest only, and never try to boot it in a bare LPAR. You lose a cylinder per disk, but you keep control over the volumes. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/25/07 9:35 AM, Anne Crabtree [EMAIL PROTECTED] wrote: Yes, I guess that should be 3339. I have 3338 all over the place.. even on first level. I changed the MDISK statements for the LX packs to be 000 3339. Linux person hasn't really tried to use them yet so I don't know if the 000 will be a problem or not. It seems to know that it is labelled LX163C,etc. I formatted it on z/os and I don't know if he does something to format it for linux or not. Guess I'll find out..lol We are only doing the third level to make sure that the VM maintenance I put on second level is ok for linux. It really won't be used as production type system. It's just to play with. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351
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- 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 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, making it begin on 001 and run for 3338, or have the Linux admin use the current label when he formats the disk (I don't remember seeing this as an option in the install process, but I wasn't looking for it, either), or let him format the disk, then discover the new label, and change all your references to match it. Note that it may not be unique if you have several Linux guests using the same virtual disk addresses. But at least you're in control of what addresses you present to the Linux guest... Option one is the simplest and most reliable, if you intend to run Linux as a guest only, and never try to boot it in a bare LPAR. You lose a cylinder per disk, but you keep control over the volumes. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/25/07 9:35 AM, Anne Crabtree [EMAIL PROTECTED] wrote: Yes, I guess that should be 3339. I have 3338 all over the place.. even on first level. I changed the MDISK statements for the LX packs to be 000 3339. Linux person hasn't really tried to use them yet so I don't know if the 000 will be a problem or not. It seems to know that it is labelled LX163C,etc. I formatted it on z/os and I don't know if he does something to format it for linux or not. Guess I'll find out..lol We are only doing the third level to make sure that the VM maintenance I put on second level is ok for linux. It really won't be used as production type system. It's just to play with. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 - The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.
Re: DASD second level
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 late but from what I see, if you go from 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 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, making it begin on 001 and run for 3338, or have the Linux admin use the current label when he formats the disk (I don't remember seeing this as an option in the install process, but I wasn't looking for it, either), or let him format the disk, then discover the new label, and change all your references to match it. Note that it may not be unique if you have several Linux guests using the same virtual disk addresses. But at least you're in control of what addresses you present to the Linux guest... Option one is the simplest and most reliable, if you intend to run Linux as a guest only, and never try to boot it in a bare LPAR. You lose a cylinder per disk, but you keep control over the volumes. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/25/07 9:35 AM, Anne Crabtree [EMAIL PROTECTED] wrote: Yes, I guess that should be 3339. I have 3338 all over the place.. even on first level. I changed the MDISK statements for the LX packs to be 000 3339. Linux person hasn't really tried to use them yet so I don't know if the 000 will be a problem or not. It seems to know that it is labelled LX163C,etc. I formatted it on z/os and I don't know if he does something to format it for linux or not. Guess I'll find out..lol We are only doing the third level to make sure that the VM maintenance I put on second level is ok for linux. It really won't be used as production type system. It's just to play with. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 - The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: DASD second level
omg i should just go home... it's a wonder i'm getting anything accomplished today... Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/25/2007 12:49 PM 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- 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 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, making it begin on 001 and run for 3338, or have the Linux admin use the current label when he formats the disk (I don't remember seeing this as an option in the install process, but I wasn't looking for it, either), or let him format the disk, then discover the new label, and change all your references to match it. Note that it may not be unique if you have several Linux guests using the same virtual disk addresses. But at least you're in control of what addresses you present to the Linux guest... Option one is the simplest and most reliable, if you intend to run Linux as a guest only, and never try to boot it in a bare LPAR. You lose a cylinder per disk, but you keep control over the volumes. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/25/07 9:35 AM, Anne Crabtree [EMAIL PROTECTED] wrote: Yes, I guess that should be 3339. I have 3338 all over the place.. even on first level. I changed the MDISK statements for the LX packs to be 000 3339. Linux person hasn't really tried to use them yet so I don't know if the 000 will be a problem or not. It seems to know that it is labelled LX163C,etc. I formatted it on z/os and I don't know if he does something to format it for linux or not. Guess I'll find out..lol We are only doing the third level to make sure that the VM maintenance I put on second level is ok for linux. It really won't be used as production type system. It's just to play with. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 - The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.
Re: DASD second level
how about i just say END! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/25/2007 1:04 PM 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 late but from what I see, if you go from 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 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, making it begin on 001 and run for 3338, or have the Linux admin use the current label when he formats the disk (I don't remember seeing this as an option in the install process, but I wasn't looking for it, either), or let him format the disk, then discover the new label, and change all your references to match it. Note that it may not be unique if you have several Linux guests using the same virtual disk addresses. But at least you're in control of what addresses you present to the Linux guest... Option one is the simplest and most reliable, if you intend to run Linux as a guest only, and never try to boot it in a bare LPAR. You lose a cylinder per disk, but you keep control over the volumes. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/25/07 9:35 AM, Anne Crabtree [EMAIL PROTECTED] wrote: Yes, I guess that should be 3339. I have 3338 all over the place.. even on first level. I changed the MDISK statements for the LX packs to be 000 3339. Linux person hasn't really tried to use them yet so I don't know if the 000 will be a problem or not. It seems to know that it is labelled LX163C,etc. I formatted it on z/os and I don't know if he does something to format it for linux or not. Guess I'll find out..lol We are only doing the third level to make sure that the VM maintenance I put on second level is ok for linux. It really won't be used as production type system. It's just to play with. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 - The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: DASD second level
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, Shasta Casey (RIP), Red Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
Re: DASD second level
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 guest VM has a minidisk of 3338 cylinders. Shouldn't that be 3339 cylinders? A 3390-3 has 3339 cylinders. I would guess to have either 001 3338 as a minidisk or 000 3339 for a full pack disk. Secondly, in this case you dedicate the 165F to the linux machine, so fro m cylinder 0 through 3338. Wouldn't that overwrite cylinder 0, thus replaci ng the CP volume information with whatever linux would like to see? Our zLin ux guests format the volume with a label something like 0x0200. Should that label be placed on cylinder 0 the hosting VM (either host or second level VM) we wouldn't be able to find LX165F afterwards. And the last point, perhaps not applicable, beware of running 3rd-level guests. They don't perform as well as second level guests. The CPU overhe ad in 3rd level is very large due to the fact that SIE assist doesn't work a t that level. (Assuming you run in LPAR mode, which is the only way on z-series today) We had an issue when we ran VSE guests on a guest VM. It turned out the VSE had on overhead ratio 1:2 or worse because all CPU had to be emulated by the host. The VSE couldn't use SIE assist in this configuration. SIE assist works only two levels deep, LPAR mode being one of them. Regards, Berry.
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 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 linked; volid LX165F not mounted I've tried putting a MDISK statement for these in VMTEST directory entry and I've tried adding them to the User_Volume_List on second level. Neither has seemed to resolve the problem. On second level, if I 'q dasd' I don't see these volumes. However, if I do 'q 163c' I get this: q 163c Ready; T=0.01/0.01 08:34:02 DASD 163C LX163C So, my question is: What is the correct way to define dasd so that second level VM can see it and Linux can own it? Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351
Re: DASD second level
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
Re: DASD second level
Based on the messages not linked it would seem you are not using DEDICATE statements in the Linux directory entries, but LINK statements. You would either need to change those statements, 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 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 linked; volid LX165F not mounted I've tried putting a MDISK statement for these in VMTEST directory entry and I've tried adding them to the User_Volume_List on second level. Neither has seemed to resolve the problem. On second level, if I 'q dasd' I don't see these volumes. However, if I do 'q 163c' I get this: q 163c Ready; T=0.01/0.01 08:34:02 DASD 163C LX163C So, my question is: What is the correct way to define dasd so that second level VM can see it and Linux can own it? Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351
Re: DASD second level
I didn't quite state that right. I'm signed onto VMTEST on first level when I did the queries. Linux directory entry is in USER DIRECT on VMTEST 191 and looks like this: USER WVLNX30 WVLNX30 512M 1024M G IPL CMS PARM AUTOCR IUCV ANY IUCV ALLOW MACHINE ESA SPECIAL 3000 HIPERS 3 CONSOLE 009 3215 T SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 190 190 RR LINK MAINT 19E 19E RR LINK MAINT 19F 19F RR LINK MAINT 19D 19D RR LINK TCPMAINT 198 198 RR LINK TCPMAINT 592 592 RR MDISK 191 3390 7981 050 510RST MR READWRITEMULTIPLE DEDICATE 0A81 163C DEDICATE 067E 165F VMTEST's USER DIRECT on first level: USER VMTEST VMTEST 64M 128M BG MACHINE ESA 2 OPTION TODENABLE ACCOUNT 1 VMTEST IPL CMS *HIPERSOCKETS DEDICATE 3000 920 DEDICATE 3001 921 DEDICATE 3002 922 DEDICATE 3004 980 DEDICATE 3005 981 DEDICATE 3006 982 * CTC TO 2ND LEVEL SPECIAL 2000 CTCA TCPIP SPECIAL 2001 CTCA TCPIP SPECIAL 400 3270 SPECIAL 401 3270 SPECIAL 402 3270 SPECIAL 403 3270 SPECIAL 404 3270 SPECIAL 405 3270 CONSOLE 009 3215 T SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 191 3390 217 0070 510W01 MR MDISK 163C 3390 000 10017 LX163C MR MDISK 165F 3390 000 3338 LX165F MR . . . Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:44 AM Based on the messages not linked it would seem you are not using DEDICATE statements in the Linux directory entries, but LINK statements. You would either need to change those statements, 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 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 linked; volid LX165F not mounted I've tried putting a MDISK statement for these in VMTEST directory entry and I've tried adding them to the User_Volume_List on second level. Neither has seemed to resolve the problem. On second level, if I 'q dasd' I don't see these volumes. However, if I do 'q 163c' I get this: q 163c Ready; T=0.01/0.01 08:34:02 DASD 163C LX163C So, my question is: What is the correct way to define dasd so that second level VM can see it and Linux can own it? Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351
Re: DASD second level
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 HCPDTG1119E Device 163C was not detached. Detach with the ALL option is not val id for devices attached to SYSTEM. Ready(01119); T=0.01/0.01 09:10:57 I just LOVE this. Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 9:03 AM 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. good luck Bill Munson IT Specialist VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Anne Crabtree wrote: tried that... seems no matter what i do, second level just says they don't exist! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:58 AM 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
Re: DASD second level
I see a mix in the directory entry for VMTEST: - you seem to use DEDICATE to pass the VM volumes to VMTEST - but use MDISK to pass the Linux volumes You could use DEDUCATE for all of them A lesson about devices (something I explained several times when teaching. At the time there was not a single exception, now there are some)). The rule: A device can be given to 1 person only at a time. person can be CP itself or a virtual machine, never both. - When you give the device to CP itself, it can maybe be shared, depending on the device type - for a disk, it can then host minidisks. Command: ATTACH xx SYSTEM, or via SYSTEM CONFIG (CPOWNED or USER_VOLUME_INCLUDE) - for a 3270 terminal: you can then logon/loggoff. Command: ENABLE rdev - ... - To give a device to a virtual machine: ATTACH or DEDICATE is used. 2007/6/22, Stracka, James (GTI) [EMAIL PROTECTED]: Or LINK fullpack ucb ucb M (MW or RR) on in the PROFILE EXEC of VMTEST if you have a fullpack minidisk holder id. We LINK RR for 1st level volumes that VMTEST is to have READ only. VMTEST volumes all start VM2 (for VM 2nd Level) and LINK them MW. Each to his own. -Original 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 to VMTEST to be used 2nd level. good luck Bill Munson IT Specialist VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Anne Crabtree wrote: tried that... seems no matter what i do, second level just says they don't exist! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:58 AM 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 -- Kris Buelens, IBM Belgium, VM customer support
Re: DASD second level
Or LINK fullpack ucb ucb M (MW or RR) on in the PROFILE EXEC of VMTEST if you have a fullpack minidisk holder id. We LINK RR for 1st level volumes that VMTEST is to have READ only. VMTEST volumes all start VM2 (for VM 2nd Level) and LINK them MW. Each to his own. -Original 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 to VMTEST to be used 2nd level. good luck Bill Munson IT Specialist VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Anne Crabtree wrote: tried that... seems no matter what i do, second level just says they don't exist! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:58 AM 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 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: DASD second level
In VMTEST, I was only using DEDICATE for hipersocket devices??? not for any volumes.. The MDISK was the only way I could think to make VMTEST see that dasd. I don't understand why the User_Volume_Include * doesn't allow me to see all dasd. After I IPL VMTEST, I did 'ATT 163C TO VMTEST' from MAINT 1st level and that seemed to work. At least it exists on 2ndlevel anyway. Thanks for the info...I'm hoping to learn a lot at SHARE! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 9:25 AM I see a mix in the directory entry for VMTEST: - you seem to use DEDICATE to pass the VM volumes to VMTEST - but use MDISK to pass the Linux volumes You could use DEDUCATE for all of them A lesson about devices (something I explained several times when teaching. At the time there was not a single exception, now there are some)). The rule: A device can be given to 1 person only at a time. person can be CP itself or a virtual machine, never both. - When you give the device to CP itself, it can maybe be shared, depending on the device type - for a disk, it can then host minidisks. Command: ATTACH xx SYSTEM, or via SYSTEM CONFIG (CPOWNED or USER_VOLUME_INCLUDE) - for a 3270 terminal: you can then logon/loggoff. Command: ENABLE rdev - ... - To give a device to a virtual machine: ATTACH or DEDICATE is used. 2007/6/22, Stracka, James (GTI) [EMAIL PROTECTED]: Or LINK fullpack ucb ucb M (MW or RR) on in the PROFILE EXEC of VMTEST if you have a fullpack minidisk holder id. We LINK RR for 1st level volumes that VMTEST is to have READ only. VMTEST volumes all start VM2 (for VM 2nd Level) and LINK them MW. Each to his own. -Original 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 to VMTEST to be used 2nd level. good luck Bill Munson IT Specialist VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Anne Crabtree wrote: tried that... seems no matter what i do, second level just says they don't exist! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:58 AM 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 -- Kris Buelens, IBM Belgium, VM customer support
Re: DASD second level
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 into the second level system as a usable device Just need to figure out what that is. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 6/22/07 9:15 AM, Anne Crabtree [EMAIL PROTECTED] wrote: In VMTEST, I was only using DEDICATE for hipersocket devices??? not for any volumes.. The MDISK was the only way I could think to make VMTEST see that dasd. I don't understand why the User_Volume_Include * doesn't allow me to see all dasd. After I IPL VMTEST, I did 'ATT 163C TO VMTEST' from MAINT 1st level and that seemed to work. At least it exists on 2ndlevel anyway. Thanks for the info...I'm hoping to learn a lot at SHARE! 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
Re: DASD second level
Minidisks can only be created on volumes that are either CP_OWNED, either ATTACHed to SYSTEM. An MDISK statement defining a minidisk on any other volume will result in HCPLNM108E KRIS 5193 not linked; volid VSHR02 not mounted User_Voume_include is just an easy way to have DASDs attached to SYSTEM at IPL. You could have the same result by coding ATTACH rdev SYSTEM in the PROFILE EXEC of AUTOLOG1 (but AUTOLOG1 will be unable to run when the volumes for its 191 and MAINT 190 are not ATTACHED to SYSTEM yet) For your second level VM system (with Linux) you must decide to use - either DEDICATE, what means that the volumes to be passed on must NOT be attached to SYSTEM in your first level VM. - either MDISK, what means that those volumes must be attached to SYSTEM in your first level VM system. This can only work when those volumes have a unique disk labels. The advantage of using MDISKs is that you can more easier get access to for example MAINT 191 of the second level system from inside your first level system. Just use DEFINE MDISK 1191 startcyl size volser You only need to know where the minidisk you need is located in the directory of the second level VM system. But, beware: if your second level VM system is running, this DEFINE MIDKS gives you a MultiWrite minidisk and you can have dataloss. Use only when your VMTEST is down. -- Kris Buelens, IBM Belgium, VM customer support 2007/6/22, Anne Crabtree [EMAIL PROTECTED]: In VMTEST, I was only using DEDICATE for hipersocket devices??? not for any volumes.. The MDISK was the only way I could think to make VMTEST see that dasd. I don't understand why the User_Volume_Include * doesn't allow me to see all dasd. After I IPL VMTEST, I did 'ATT 163C TO VMTEST' from MAINT 1st level and that seemed to work. At least it exists on 2ndlevel anyway. Thanks for the info...I'm hoping to learn a lot at SHARE! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 9:25 AM I see a mix in the directory entry for VMTEST: - you seem to use DEDICATE to pass the VM volumes to VMTEST - but use MDISK to pass the Linux volumes You could use DEDUCATE for all of them A lesson about devices (something I explained several times when teaching. At the time there was not a single exception, now there are some)). The rule: A device can be given to 1 person only at a time. person can be CP itself or a virtual machine, never both. - When you give the device to CP itself, it can maybe be shared, depending on the device type - for a disk, it can then host minidisks. Command: ATTACH xx SYSTEM, or via SYSTEM CONFIG (CPOWNED or USER_VOLUME_INCLUDE) - for a 3270 terminal: you can then logon/loggoff. Command: ENABLE rdev - ... - To give a device to a virtual machine: ATTACH or DEDICATE is used. 2007/6/22, Stracka, James (GTI) [EMAIL PROTECTED]: Or LINK fullpack ucb ucb M (MW or RR) on in the PROFILE EXEC of VMTEST if you have a fullpack minidisk holder id. We LINK RR for 1st level volumes that VMTEST is to have READ only. VMTEST volumes all start VM2 (for VM 2nd Level) and LINK them MW. Each to his own. -Original 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 to VMTEST to be used 2nd level. good luck Bill Munson IT Specialist VM System Programmer Office of Information Technology State of New Jersey (609) 984-4065 President MVMUA http://www.marist.edu/~mvmua Anne Crabtree wrote: tried that... seems no matter what i do, second level just says they don't exist! Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:58 AM 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 -- Kris Buelens, IBM Belgium, VM customer support
Re: DASD second level
Hello Ann, I have been looking at your statements. Let me see if I have this right. You have a first level system that has two DASD 163C and 165F that you want to make MDISKs on VMTEST. MDISK 163C 3390 000 10017 LX163C MR MDISK 165F 3390 000 3338 LX165F MR But you get these messages when you logon to VMTEST HCPLNM108E VMTEST 163C not linked; volid LX163C not mounted HCPLNM108E VMTEST 165F not linked; volid LX165F not mounted If you want to have user MDISK statements on VMTEST, you will need these two volumes ATTACHed to the system. ATT 163C SYSTEM LX163C ATT 165F SYSTEM LX165F. Then re-logon to VMTEST. And you intend to have WVLNX30 run under VMTEST, right? Your DED statement should have 163C on attached to WVLNX30 as 0A81 on VMTEST only. I hope I explained this well enough. Ed Martin Aultman Health Foundation 330-588-4723 [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 VMTEST on first level when I did the queries. Linux directory entry is in USER DIRECT on VMTEST 191 and looks like this: USER WVLNX30 WVLNX30 512M 1024M G IPL CMS PARM AUTOCR IUCV ANY IUCV ALLOW MACHINE ESA SPECIAL 3000 HIPERS 3 CONSOLE 009 3215 T SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 190 190 RR LINK MAINT 19E 19E RR LINK MAINT 19F 19F RR LINK MAINT 19D 19D RR LINK TCPMAINT 198 198 RR LINK TCPMAINT 592 592 RR MDISK 191 3390 7981 050 510RST MR READWRITEMULTIPLE DEDICATE 0A81 163C DEDICATE 067E 165F VMTEST's USER DIRECT on first level: USER VMTEST VMTEST 64M 128M BG MACHINE ESA 2 OPTION TODENABLE ACCOUNT 1 VMTEST IPL CMS *HIPERSOCKETS DEDICATE 3000 920 DEDICATE 3001 921 DEDICATE 3002 922 DEDICATE 3004 980 DEDICATE 3005 981 DEDICATE 3006 982 * CTC TO 2ND LEVEL SPECIAL 2000 CTCA TCPIP SPECIAL 2001 CTCA TCPIP SPECIAL 400 3270 SPECIAL 401 3270 SPECIAL 402 3270 SPECIAL 403 3270 SPECIAL 404 3270 SPECIAL 405 3270 CONSOLE 009 3215 T SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR MDISK 191 3390 217 0070 510W01 MR MDISK 163C 3390 000 10017 LX163C MR MDISK 165F 3390 000 3338 LX165F MR . . . Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351 [EMAIL PROTECTED] 6/22/2007 8:44 AM Based on the messages not linked it would seem you are not using DEDICATE statements in the Linux directory entries, but LINK statements. You would either need to change those statements, 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 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 linked; volid LX165F not mounted I've tried putting a MDISK statement for these in VMTEST directory entry and I've tried adding them to the User_Volume_List on second level. Neither has seemed to resolve the problem. On second level, if I 'q dasd' I don't see these volumes. However, if I do 'q 163c' I get this: q 163c Ready; T=0.01/0.01 08:34:02 DASD 163C LX163C So, my question is: What is the correct way to define dasd so that second level VM can see it and Linux can own it? Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-5914 ext 8885 Fax 304-558-1351
Re: DASD second level
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 become: 'CP TERM CONMODE 3270' || , '15'x || 'SET MACHINE ESA'|| , '15'x ||'IPL 711C CLEAR LOADPARM 0009' -- Kris Buelens, IBM Belgium, VM customer support
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 CONMODE 3270' 'SET MACHINE ESA' 'IPL 711C CLEAR LOADPARM 0009' should become: 'CP TERM CONMODE 3270' || , '15'x || 'SET MACHINE ESA'|| , '15'x ||'IPL 711C CLEAR LOADPARM 0009' -- Kris Buelens, IBM Belgium, VM customer support
Re: DASD second level
We do something similar for TPF guests and have, under some circumstances gotten the message, DMSCIT171T Permanent console error; re-IPL CMS, before the other commands in the string completed. This has been a source of confusion to our users who, by and large, are naive. By doing something that causes a virtual system reset before the TERM command, that problem has been eliminated. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Bill Munson Sent: Friday, June 22, 2007 11:12 AM To: IBMVM@LISTSERV.UARK.EDU 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 CONMODE 3270' 'SET MACHINE ESA' 'IPL 711C CLEAR LOADPARM 0009' should become: 'CP TERM CONMODE 3270' || , '15'x || 'SET MACHINE ESA'|| , '15'x ||'IPL 711C CLEAR LOADPARM 0009' -- Kris Buelens, IBM Belgium, VM customer support
Re: DASD second level
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 you when the 2nd level OPERATOR drops into 1st level CP and believes he's working with 2nd level devices. You could at least set your privilege class to G once you've done your thing. Rob
