Re: migrating an in-house MF tool
Hi, I was able to migrate it successfully. Thanks all for your valuable suggestion. Regards, Jags On Sun, Aug 7, 2011 at 8:13 AM, jagadishan perumal jagadish...@gmail.comwrote: Thanks I will definetly take your Inputs and read accordingly. On Sun, Aug 7, 2011 at 8:03 AM, john gilmore john_w_gilm...@msn.comwrote: The problem is not 1) that you post too often or 2) that you do not do enough manual readinmg before you post. It is that you do not provide enough circumstantial detail to enable us to be really helpful. Try describing your problems in [much] greater circumstantial detail. We all know how to discard irrelevant detail, and your instinct for brevity makes it unlikely that you will be prolix. John Gilmore Ashland, MA 01721-1817 USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Migrating a in house MF tool
Hi, Sorry for not providing much information. it is not a version dependent one. I am trying to do a dump and restore of the entire tool dataset MFCOE.** to the V1.12. Concatenate the Required REXX to the SYSEXEC. Regards, Jags On Sat, Aug 6, 2011 at 7:24 AM, Schwarz, Barry A barry.a.schw...@boeing.com wrote: You just love asking questions without providing any details. Unless the tool has some version dependent code, you should perform a complete installation of the tool on the 1.12 system, duplicating all the steps that were used to install it originally on the 1.6 system. Hopefully, the previously installation is well documented and you saved all the necessary datasets and files. If there are any version dependencies, now would be good time to document them. And maybe build a migration manual for the next time. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Friday, August 05, 2011 6:13 PM To: IBM-MAIN@bama.ua.edu Subject: Migrating a in house MF tool Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Migrating a in house MF tool
Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. Regards, Jags Jags, In house tools need to be documented by your shop as to how things are hooked up. However, if you did a DFDSS dump, a DFDSS restore should work. I do not know of any problems between z/OS V1.6 Dump and a z/OS V1.12 Restore. Though I probably would have used TSO XMIT or an IEBCOPY Unload and then used the correct restore process under z/OS V1.12. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Migrating a in house MF tool
If you know all the pieces that make up the tool and you have successfully identified them and successfully transported them to the new system, it's time to build the tool on the new system. If you have build instructions from the old system, those instructions may also work on the new system. If you do not have build instructions, you will have to reverse engineer the tool on the old system to create build instructions. Since this seems to be an internally-developed tool, only you or someone in your shop can do this. Have you already done any of this analysis? You really need to do some work up-front before posting a question. And when you do post a question you need to provide specific details, such as error messages, if something is not working as expected. - Don Imbriale On Sat, Aug 6, 2011 at 2:13 AM, jagadishan perumal jagadish...@gmail.comwrote: Hi, Sorry for not providing much information. it is not a version dependent one. I am trying to do a dump and restore of the entire tool dataset MFCOE.** to the V1.12. Concatenate the Required REXX to the SYSEXEC. Regards, Jags On Sat, Aug 6, 2011 at 7:24 AM, Schwarz, Barry A barry.a.schw...@boeing.com wrote: You just love asking questions without providing any details. Unless the tool has some version dependent code, you should perform a complete installation of the tool on the 1.12 system, duplicating all the steps that were used to install it originally on the 1.6 system. Hopefully, the previously installation is well documented and you saved all the necessary datasets and files. If there are any version dependencies, now would be good time to document them. And maybe build a migration manual for the next time. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Friday, August 05, 2011 6:13 PM To: IBM-MAIN@bama.ua.edu Subject: Migrating a in house MF tool Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Migrating a in house MF tool
Sure... I will try doing it and search manuals incase of any difficulties.. Post if i need the experts comment. On Sat, Aug 6, 2011 at 7:14 PM, Don Imbriale don.imbri...@gmail.com wrote: If you know all the pieces that make up the tool and you have successfully identified them and successfully transported them to the new system, it's time to build the tool on the new system. If you have build instructions from the old system, those instructions may also work on the new system. If you do not have build instructions, you will have to reverse engineer the tool on the old system to create build instructions. Since this seems to be an internally-developed tool, only you or someone in your shop can do this. Have you already done any of this analysis? You really need to do some work up-front before posting a question. And when you do post a question you need to provide specific details, such as error messages, if something is not working as expected. - Don Imbriale On Sat, Aug 6, 2011 at 2:13 AM, jagadishan perumal jagadish...@gmail.com wrote: Hi, Sorry for not providing much information. it is not a version dependent one. I am trying to do a dump and restore of the entire tool dataset MFCOE.** to the V1.12. Concatenate the Required REXX to the SYSEXEC. Regards, Jags On Sat, Aug 6, 2011 at 7:24 AM, Schwarz, Barry A barry.a.schw...@boeing.com wrote: You just love asking questions without providing any details. Unless the tool has some version dependent code, you should perform a complete installation of the tool on the 1.12 system, duplicating all the steps that were used to install it originally on the 1.6 system. Hopefully, the previously installation is well documented and you saved all the necessary datasets and files. If there are any version dependencies, now would be good time to document them. And maybe build a migration manual for the next time. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Friday, August 05, 2011 6:13 PM To: IBM-MAIN@bama.ua.edu Subject: Migrating a in house MF tool Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
migrating an in-house MF tool
The problem is not 1) that you post too often or 2) that you do not do enough manual readinmg before you post. It is that you do not provide enough circumstantial detail to enable us to be really helpful. Try describing your problems in [much] greater circumstantial detail. We all know how to discard irrelevant detail, and your instinct for brevity makes it unlikely that you will be prolix. John Gilmore Ashland, MA 01721-1817 USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: migrating an in-house MF tool
Thanks I will definetly take your Inputs and read accordingly. On Sun, Aug 7, 2011 at 8:03 AM, john gilmore john_w_gilm...@msn.com wrote: The problem is not 1) that you post too often or 2) that you do not do enough manual readinmg before you post. It is that you do not provide enough circumstantial detail to enable us to be really helpful. Try describing your problems in [much] greater circumstantial detail. We all know how to discard irrelevant detail, and your instinct for brevity makes it unlikely that you will be prolix. John Gilmore Ashland, MA 01721-1817 USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Migrating a in house MF tool
Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. Regards, Jags -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Migrating a in house MF tool
You just love asking questions without providing any details. Unless the tool has some version dependent code, you should perform a complete installation of the tool on the 1.12 system, duplicating all the steps that were used to install it originally on the 1.6 system. Hopefully, the previously installation is well documented and you saved all the necessary datasets and files. If there are any version dependencies, now would be good time to document them. And maybe build a migration manual for the next time. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of jagadishan perumal Sent: Friday, August 05, 2011 6:13 PM To: IBM-MAIN@bama.ua.edu Subject: Migrating a in house MF tool Hi, We recently decommissioned a Z/OS 1.6 server. There was a requirement that a tool which was developed under 1.6 needs to be migrated to the new LPAR Z/OS 1.12. Could you please guide me the required steps that needs to taken to migrate the entire tool and invoke those panels in 1.12 version. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
