Re: Linux on z/VM Cloning Problem
If they are EDEVs, just update the VM directory entry for the virtual machine that is the cloning *target*. Make sure that the edevices are defined at IPL time. Either in SYSTEM CONFIG or in an EXEC called from AUTOLOG1 or AUTOLOG2's PROFILE EXEC On 02/13/2011 10:43 PM, Rakesh Krishnakumar wrote: Actually we are stuck at the place as we don't know which directory in Linux should be updated to point to correct Lun id ..Can anybody help us in that. These are SCSI devices set in z/VM as EDEV Regards Rakesh.K System z Middleware Services GTS, IBM India Pvt. Ltd. 4th Floor, IL&FS Building, Bandra Kurla Complex, Bandra(East), Mumbai 40051, India Mobile: +91 9004073443 Email: rkris...@in.ibm.com -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
Re: Linux on z/VM Cloning Problem
Actually we are stuck at the place as we don't know which directory in Linux should be updated to point to correct Lun id ..Can anybody help us in that. These are SCSI devices set in z/VM as EDEV Regards Rakesh.K System z Middleware Services GTS, IBM India Pvt. Ltd. 4th Floor, IL&FS Building, Bandra Kurla Complex, Bandra(East), Mumbai 40051, India Mobile: +91 9004073443 Email: rkris...@in.ibm.com From: Rich Smrcina To: IBMVM@LISTSERV.UARK.EDU Date: 13/02/2011 22:32 Subject:Re: Linux on z/VM Cloning Problem Sent by:The IBM z/VM Operating System The images didn't come through as they are blocked. Are these EDEVs or standard SCSI devices? Change the directory on COPYCLN1 to make the root device and swap device the same device numbers as on MSTRLCON. Make sure to log off and log on COPYCLN1 after the change. On 02/13/2011 10:17 AM, Rakesh Krishnakumar wrote: > Hi All, > >We are trying clone one Linux image running on system Z to another. Below > is the process we have adopted for the same. But while booting the cloned > image we are facing an issue that cloned root and swap partitions are > pointing to master image and not cloned image.Below are steps we have > followed. Any help in changing the pointers of root and swap partitions to > cloned image would be helpful. > > > Steps below illustrates the problem encountered while IPLing the new guest > after the clone process. > Here MSTRCLON is the Master Linux Copy. The target is COPYCLN1. > > 1 - As shown in the fig. below MDISK 200 is > assigned to MSTRCLON Linux > Guest. > >- This contains Linux /boot partition. > >- MDISK 300 is assigned to COPYCLN1 guest. > >- DDR COPY from MDISK 200 to MDISK 300 is successful. > > > (Embedded image moved to file: pic08728.jpg) > > > 2 - As shown below, A 32 GB LUN with LUN Number 00AF is > attached to MSTRCLON Linux Guest. > >- This LUN contains 26 GB / (root) partition, 6 > GB Swap > Partition. > >- A 32 GB LUN with LUN Number 00AE is attached to > COPYCLN1 Linux Guest. > >- From z/VM DDR COPY ALL command has been run to clone the > content of LUN 00AF to 00AE. > >- The DDR copy is successfull. > > (Embedded image moved to file: pic11302.jpg) > > > 3 - The Problem > >- While IPL-ing new Guest, COPYCLN1 the boot > device 300 which is > correct. > >-IPL is successful only if the ' / ' and > 'Swap' device is > 00AF, > >- This device belongs to the MSTRCLON. > >- We are unable to IPL the guest with ' / ' and 'Swap' device > 00AE, > > > > Regards > Rakesh > > -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
Re: CHARLOTTe Updates to WW2CORE REXX
On: Sun, Feb 13, 2011 at 04:52:30PM -0600,Dave Jones Wrote: } Whoever "compiled" the WW2XCORE Rexx code specified the SLINE compiler } option, so the original Rexx source is embedded in the module. It should } be possible, but probably a PITA, to extract that original source into a } file that could be updated. Actually, its fairly simple. I had an exec to do it, but of course I can't find it now. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself & my dogs only.VM'er since CP-67 Canines: Val, Red, Shasta, Zero & Casey (At the bridge)Owner:Chinook-L Canines: Red & Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
Re: CHARLOTTe Updates to WW2CORE REXX
Whoever "compiled" the WW2XCORE Rexx code specified the SLINE compiler option, so the original Rexx source is embedded in the module. It should be possible, but probably a PITA, to extract that original source into a file that could be updated. DJ On 02/13/2011 03:25 PM, Jim Elliott wrote: > ... > >> The source code is not in the CHARLOTT package on the IBM >> DOWNLOAD site. The package has a note that source code can be >> obtained by contacting charlotte.supp...@gems4.gov.bc.ca but >> this address in no longer active. > >> Does anyone know of a newer contact address? Or has someone >> already updated CHARLOTTe to handle the mentioned HTML >> entities? > > Fran: > > Perry Ruiter was maintaining this at the BC Government. As he is > now with VM development, try contacting him at prui...@ca.ibm.com > > Jim > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: CHARLOTTe Updates to WW2CORE REXX
On Tue, 8 Feb 2011 09:51:58 -0500, Fran Hensler wrote: >Good morning - > >I am still using CHARLOTTe 2.10 in z/VM 3.1. I think it is great for >except one annoyance -- newer HTML entities such as “ &rdq uo; squo; >‘ & do not get translated into displayable EBCDIC characte rs. > >I think it is WW2CORE REXX that does this work and I would like to >update it but I don't know how to decompile the compiled REXX. > >The source code is not in the CHARLOTT package on the IBM DOWNLOAD site. >The package has a note that source code can be obtained by contacting >charlotte.supp...@gems4.gov.bc.ca but this address in no longer active. > >Does anyone know of a newer contact address? Or has someone already >updated CHARLOTTe to handle the mentioned HTML entities? > >/Fran Hensler at Slippery Rock University of Pennsylvania USA for 47 yea rs >mailto:f...@zvm.sru.edu http://zvm.sru.edu/~fjh +1.724.738.2153 > "Yes, Virginia, there is a Slippery Rock" > -- Fran, I have all the source code to Charlotte 2.1.0 and I can send it to you. The code you would need to change is written in C and is called WW2PARSC. It is a rewrite of the REXX code originally supplied in WW2PARSE REXX. It looks like it would be easy to change it, but you woul d need a C compiler, of course. I don't have one so I can't help you. WW2PARSC was originally written and maintained by Jonathan Scott of IBM UK. It looks like he is still around and he might have a more current version with what you need. WW2PARSC is maintained with a control file and updates, (like all good VM/CMS code should be!). If you don't have a C compiler either, perhaps one of "Daves" :-)> would volunteer to change it, compile it, and regen it. -- Dale R. Smith
Re: CHARLOTTe Updates to WW2CORE REXX
... > The source code is not in the CHARLOTT package on the IBM > DOWNLOAD site. The package has a note that source code can be > obtained by contacting charlotte.supp...@gems4.gov.bc.ca but > this address in no longer active. > Does anyone know of a newer contact address? Or has someone > already updated CHARLOTTe to handle the mentioned HTML > entities? Fran: Perry Ruiter was maintaining this at the BC Government. As he is now with VM development, try contacting him at prui...@ca.ibm.com Jim
Re: Linux on z/VM Cloning Problem
>>> On 2/13/2011 at 11:17 AM, Rakesh Krishnakumar wrote: > 3 - The Problem > > - While IPL-ing new Guest, COPYCLN1 the boot device 300 which is > correct. > > -IPL is successful only if the ' / ' and 'Swap' device is > 00AF, > > - This device belongs to the MSTRCLON. > > - We are unable to IPL the guest with ' / ' and 'Swap' device > 00AE, So where in this process do you modify the configuration file to point to the new LUN? Are you also rebuilding the initrd afterward? Mark Post
Re: Linux on z/VM Cloning Problem
The images didn't come through as they are blocked. Are these EDEVs or standard SCSI devices? Change the directory on COPYCLN1 to make the root device and swap device the same device numbers as on MSTRLCON. Make sure to log off and log on COPYCLN1 after the change. On 02/13/2011 10:17 AM, Rakesh Krishnakumar wrote: Hi All, We are trying clone one Linux image running on system Z to another. Below is the process we have adopted for the same. But while booting the cloned image we are facing an issue that cloned root and swap partitions are pointing to master image and not cloned image.Below are steps we have followed. Any help in changing the pointers of root and swap partitions to cloned image would be helpful. Steps below illustrates the problem encountered while IPLing the new guest after the clone process. Here MSTRCLON is the Master Linux Copy. The target is COPYCLN1. 1 - As shown in the fig. below MDISK 200 is assigned to MSTRCLON Linux Guest. - This contains Linux /boot partition. - MDISK 300 is assigned to COPYCLN1 guest. - DDR COPY from MDISK 200 to MDISK 300 is successful. (Embedded image moved to file: pic08728.jpg) 2 - As shown below, A 32 GB LUN with LUN Number 00AF is attached to MSTRCLON Linux Guest. - This LUN contains 26 GB / (root) partition, 6 GB Swap Partition. - A 32 GB LUN with LUN Number 00AE is attached to COPYCLN1 Linux Guest. - From z/VM DDR COPY ALL command has been run to clone the content of LUN 00AF to 00AE. - The DDR copy is successfull. (Embedded image moved to file: pic11302.jpg) 3 - The Problem - While IPL-ing new Guest, COPYCLN1 the boot device 300 which is correct. -IPL is successful only if the ' / ' and 'Swap' device is 00AF, - This device belongs to the MSTRCLON. - We are unable to IPL the guest with ' / ' and 'Swap' device 00AE, Regards Rakesh -- Rich Smrcina Velocity Software, Inc. http://www.velocitysoftware.com Catch the WAVV! http://www.wavv.org WAVV 2011 - April 15-19, 2011 Colorado Springs, CO
Linux on z/VM Cloning Problem
Hi All, We are trying clone one Linux image running on system Z to another. Below is the process we have adopted for the same. But while booting the cloned image we are facing an issue that cloned root and swap partitions are pointing to master image and not cloned image.Below are steps we have followed. Any help in changing the pointers of root and swap partitions to cloned image would be helpful. Steps below illustrates the problem encountered while IPLing the new guest after the clone process. Here MSTRCLON is the Master Linux Copy. The target is COPYCLN1. 1 - As shown in the fig. below MDISK 200 is assigned to MSTRCLON Linux Guest. - This contains Linux /boot partition. - MDISK 300 is assigned to COPYCLN1 guest. - DDR COPY from MDISK 200 to MDISK 300 is successful. (Embedded image moved to file: pic08728.jpg) 2 - As shown below, A 32 GB LUN with LUN Number 00AF is attached to MSTRCLON Linux Guest. - This LUN contains 26 GB / (root) partition, 6 GB Swap Partition. - A 32 GB LUN with LUN Number 00AE is attached to COPYCLN1 Linux Guest. - From z/VM DDR COPY ALL command has been run to clone the content of LUN 00AF to 00AE. - The DDR copy is successfull. (Embedded image moved to file: pic11302.jpg) 3 - The Problem - While IPL-ing new Guest, COPYCLN1 the boot device 300 which is correct. -IPL is successful only if the ' / ' and 'Swap' device is 00AF, - This device belongs to the MSTRCLON. - We are unable to IPL the guest with ' / ' and 'Swap' device 00AE, Regards Rakesh
Re: Who is accessing DASD
thanks for all the suggestions! --- On Sat, 2/12/11, Rich Greenberg wrote: From: Rich Greenberg Subject: Re: Who is accessing DASD To: IBMVM@LISTSERV.UARK.EDU Date: Saturday, 12 February, 2011, 3:09 PM On: Sat, Feb 12, 2011 at 11:41:40AM -0800,Martin Magat Wrote: } Thanks. Yes, I know that guests minidisks are not defined in cpowned page packs. } Anyway, In case you want to drain a page pack and make it offline, you may want to know which guests are currently 'locked' into it. If permitted, I can perhaps logoff those guests if not needed to be up and running. Check the IBM VM download page. No idea what it was called but ISTR there is/was something that would identify users of page & spool packs. Its far from a simple command. The program had to chase down some control blocks for each spool page. Just as a guess, it likely had either SPOOL or SPL or similar in its name. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself & my dogs only. VM'er since CP-67 Canines: Val, Red, Shasta, Zero & Casey (At the bridge) Owner:Chinook-L Canines: Red & Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
