Re: z/OS 1.12 question
That depends on how you feel about Russian Roulette. I agree that "In most cases, that just isn't a problem. ", but that's not much comfort in the rare cases where it is a problem and you failed to check. Remember, even paranoids have real enemies. But it's not my dog. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jesse 1 Robinson Sent: Saturday, January 12, 2019 6:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question It's difficult for a mere monogamistic sysprog to challenge a polyamorous expert, but I can certify that in my shop two products failed to work *at all* in the upgrade to 2.3 from 2.1. This was despite having upgraded several other products over the previous year or so. There was a lengthy period starting in the 90s where we installed nearly every OS release, including those on six-month cycle. (Whew!) We habitually contacted ISVs and built recommended conditioning into the schedule. In the 2.3 upgrade, we miscommunicated with one ISV and overlooked the other. Bam and bam. You may get lucky, as when blowing through a full stop without a scratch, but I would not bet my reputation on luck. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Friday, January 11, 2019 12:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: z/OS 1.12 question I respectfully disagree. Upgrading when it's not necessary can be counter-productive for some sites. While many vendor products do require some maintenance to "fully" function, especially those that interact directly with the OS, that doesn't mean that older versions won't work, and in fact, some "newer" products might no longer operate the way the site needs or wants. That doesn't mean that the OP should do something stupid, but they don't have to feel that they need to look at their task as if it's a huge project either. I respect your expertise, but when it comes to migrations, I have performed, and still perform several at a time from some pretty old releases to the current ones, and having just this past year upgraded 5 sites from z/OS 1.12 and several older releases to z/OS 2.3 (and in one case 2.2), I can tell you that while it's ALWAYS a good idea to apply AVAILABLE maintenance, there is no reason to worry that something will not work at all just because you don't have the latest copy/version. In most cases, that just isn't a problem. No one said that they should not upgrade as they go, but doing it all at the same time is not always the smartest thing to do. Brian On Thu, 10 Jan 2019 16:20:07 -0800, Ed Jaffe wrote: >On 1/9/2019 11:05 PM, Brian Westerman wrote: >> Most, if not all, of the installed (vendor) software at 1.12 will work >> perfectly fine at 2.3. > >Don't know about most, but ALL seems highly unlikely. > >I can state with certainty that *every one* of the z/OS-based products >we run here from other ISVs would need to be upgraded (or at least have >all service applied if still supported) as would several of our own. > >My recommendation, especially for shops with a tendency to fall way >behind like this one has, is to bite the bullet and upgrade to the >"latest and greatest" release of everything possible whenever the >opportunity presents itself. Running old, unsupported code on a new >operating system is just asking for trouble. And, who knows how long it >might be before you get another chance to upgrade? > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://secure-web.cisco.com/1l5fO4olrnwHCN_165nvuEGwIL0_Lh17uWQO3BV9nRS4YaRnrQubrH_Uy2jsvWniVse3Q5xlw8hdz5cQZBOgIqQ3MErH_pmb-X_Z21SMbO9scwTBnH7ac0VoqijgLHW3MS8ybF4n7oau3-fSzC6Nc482zV8A2_L32D0HCKwzUTkw4iHMaj_mM02tFBzx_DWBXSRHUH-_WXB4HJ8IhtRDQFWQ7CslmHG8lECM2wDMvbWGsizX9o1k-DYTA0KOR7Iqz8JsEloY2mZGOYp0MgifQ4D96DdhREqMhGBh6Ia868-BXHqHtY_VbtzYl2sL0yQqrX-IlQJYxEAFFLJVQBuqlKOlyhtvglU6DKDyznkZbVaX3De8h9BxmjBrjGkPdAADGz4D6pQ8zCrK0mcqr_IN9IxQI61_xJRLs31WRJQ6evxu_1ImeInMMpWMiN-7D_ZzB/https%3A%2F%2Fwww.phoenixsoftware.com%2F -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
You can never be too paranoid. I once had a boss who asked me if he was taking too many copies of Stand-alone restore (SAR) to a DR test and I told him that he might hear me saying that he didn't have enough but that he would never hear me saying that he had too many. The same principle applies to asking 3rd party vendor about potential compatibility issues; it can only help, and not doing so can hurt. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jesse 1 Robinson Sent: Sunday, January 13, 2019 10:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question One product I discussed here last year. There was a change in TSO/E that caused StarTool to fail from the get-go. (Same problem with CBT PDS command.) For whatever reason the 'fix' was a whole new release of the product. I think there was some misunderstanding in our pro forma query to Microfocus, the new owner of Serena. In any case we were caught off guard. The other product was BMC Discovery, which was quite old and the object of some benign neglect. Not that benign actually. It would not run at all. Still working on a new release. The point of my emphatic posts is that while you may get away with forging ahead and 'fixing forward', the prudent course is to seek and follow vendors' advice whether or not it's strictly necessary. My ROT is which outcome you'd rather have to explain to the boss: some zealous over-prep or a hat-in-hand interruption to the published upgrade schedule. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Sunday, January 13, 2019 12:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: z/OS 1.12 question That's a pretty odd thing to happen from 2.1 to 2.3. What products were involved? I can see if the product had some ties into JES2 and you had to reassemble or relink the interface, but that can happen just by adding maintenance to any system. It's really odd for almost any vendor product to be tied into a specific OS especially when they are quite so close in release. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
One product I discussed here last year. There was a change in TSO/E that caused StarTool to fail from the get-go. (Same problem with CBT PDS command.) For whatever reason the 'fix' was a whole new release of the product. I think there was some misunderstanding in our pro forma query to Microfocus, the new owner of Serena. In any case we were caught off guard. The other product was BMC Discovery, which was quite old and the object of some benign neglect. Not that benign actually. It would not run at all. Still working on a new release. The point of my emphatic posts is that while you may get away with forging ahead and 'fixing forward', the prudent course is to seek and follow vendors' advice whether or not it's strictly necessary. My ROT is which outcome you'd rather have to explain to the boss: some zealous over-prep or a hat-in-hand interruption to the published upgrade schedule. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Sunday, January 13, 2019 12:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: z/OS 1.12 question That's a pretty odd thing to happen from 2.1 to 2.3. What products were involved? I can see if the product had some ties into JES2 and you had to reassemble or relink the interface, but that can happen just by adding maintenance to any system. It's really odd for almost any vendor product to be tied into a specific OS especially when they are quite so close in release. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
That's a pretty odd thing to happen from 2.1 to 2.3. What products were involved? I can see if the product had some ties into JES2 and you had to reassemble or relink the interface, but that can happen just by adding maintenance to any system. It's really odd for almost any vendor product to be tied into a specific OS especially when they are quite so close in release. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
On 1/12/2019 3:19 PM, Jesse 1 Robinson wrote: It's difficult for a mere monogamistic sysprog to challenge a polyamorous expert, but I can certify that in my shop two products failed to work *at all* in the upgrade to 2.3 from 2.1. This was despite having upgraded several other products over the previous year or so. The past couple of z/OS releases have been particularly brutal. Changes in long-standing FREEMAIN behavior, the high half of R15 now suddenly non-zero on various system macro calls, SWA and other control blocks being relocated, changes related to 8-byte TSO userids, new environmental restrictions for unauthorized services, EXECUTABLE=NO storage, and numerous other updates have created a virtual "mine field" for code that hasn't been properly cared for. I'm aware of some incompatible updates to CICS, VTAM, JES and other components as well with more planned in the coming months and years. Just saying... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
It's difficult for a mere monogamistic sysprog to challenge a polyamorous expert, but I can certify that in my shop two products failed to work *at all* in the upgrade to 2.3 from 2.1. This was despite having upgraded several other products over the previous year or so. There was a lengthy period starting in the 90s where we installed nearly every OS release, including those on six-month cycle. (Whew!) We habitually contacted ISVs and built recommended conditioning into the schedule. In the 2.3 upgrade, we miscommunicated with one ISV and overlooked the other. Bam and bam. You may get lucky, as when blowing through a full stop without a scratch, but I would not bet my reputation on luck. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Friday, January 11, 2019 12:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: z/OS 1.12 question I respectfully disagree. Upgrading when it's not necessary can be counter-productive for some sites. While many vendor products do require some maintenance to "fully" function, especially those that interact directly with the OS, that doesn't mean that older versions won't work, and in fact, some "newer" products might no longer operate the way the site needs or wants. That doesn't mean that the OP should do something stupid, but they don't have to feel that they need to look at their task as if it's a huge project either. I respect your expertise, but when it comes to migrations, I have performed, and still perform several at a time from some pretty old releases to the current ones, and having just this past year upgraded 5 sites from z/OS 1.12 and several older releases to z/OS 2.3 (and in one case 2.2), I can tell you that while it's ALWAYS a good idea to apply AVAILABLE maintenance, there is no reason to worry that something will not work at all just because you don't have the latest copy/version. In most cases, that just isn't a problem. No one said that they should not upgrade as they go, but doing it all at the same time is not always the smartest thing to do. Brian On Thu, 10 Jan 2019 16:20:07 -0800, Ed Jaffe wrote: >On 1/9/2019 11:05 PM, Brian Westerman wrote: >> Most, if not all, of the installed (vendor) software at 1.12 will work >> perfectly fine at 2.3. > >Don't know about most, but ALL seems highly unlikely. > >I can state with certainty that *every one* of the z/OS-based products >we run here from other ISVs would need to be upgraded (or at least have >all service applied if still supported) as would several of our own. > >My recommendation, especially for shops with a tendency to fall way >behind like this one has, is to bite the bullet and upgrade to the >"latest and greatest" release of everything possible whenever the >opportunity presents itself. Running old, unsupported code on a new >operating system is just asking for trouble. And, who knows how long it >might be before you get another chance to upgrade? > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Because if you give users a means to save more datasets that they don't need, they will do it. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Thursday, January 10, 2019 8:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question On 1/10/2019 5:12 PM, Tom Conley wrote: > Good to know folks out there aren't exploiting extended GDG's. Which is amazing considering, without that support, you can't even maintain one generation per day for a year! =-O -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
I respectfully disagree. Upgrading when it's not necessary can be counter-productive for some sites. While many vendor products do require some maintenance to "fully" function, especially those that interact directly with the OS, that doesn't mean that older versions won't work, and in fact, some "newer" products might no longer operate the way the site needs or wants. That doesn't mean that the OP should do something stupid, but they don't have to feel that they need to look at their task as if it's a huge project either. I respect your expertise, but when it comes to migrations, I have performed, and still perform several at a time from some pretty old releases to the current ones, and having just this past year upgraded 5 sites from z/OS 1.12 and several older releases to z/OS 2.3 (and in one case 2.2), I can tell you that while it's ALWAYS a good idea to apply AVAILABLE maintenance, there is no reason to worry that something will not work at all just because you don't have the latest copy/version. In most cases, that just isn't a problem. No one said that they should not upgrade as they go, but doing it all at the same time is not always the smartest thing to do. Brian On Thu, 10 Jan 2019 16:20:07 -0800, Ed Jaffe wrote: >On 1/9/2019 11:05 PM, Brian Westerman wrote: >> Most, if not all, of the installed (vendor) software at 1.12 will work >> perfectly fine at 2.3. > >Don't know about most, but ALL seems highly unlikely. > >I can state with certainty that *every one* of the z/OS-based products >we run here from other ISVs would need to be upgraded (or at least have >all service applied if still supported) as would several of our own. > >My recommendation, especially for shops with a tendency to fall way >behind like this one has, is to bite the bullet and upgrade to the >"latest and greatest" release of everything possible whenever the >opportunity presents itself. Running old, unsupported code on a new >operating system is just asking for trouble. And, who knows how long it >might be before you get another chance to upgrade? > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://www.phoenixsoftware.com/ > > > >This e-mail message, including any attachments, appended messages and the >information contained therein, is for the sole use of the intended >recipient(s). If you are not an intended recipient or have otherwise >received this email message in error, any use, dissemination, distribution, >review, storage or copying of this e-mail message and the information >contained therein is strictly prohibited. If you are not an intended >recipient, please contact the sender by reply e-mail and destroy all copies >of this email message and do not otherwise utilize or retain this email >message or any or all of the information contained therein. Although this >email message and any attachments or appended messages are believed to be >free of any virus or other defect that might affect any computer system into >which it is received and opened, it is the responsibility of the recipient >to ensure that it is virus free and no responsibility is accepted by the >sender for any loss or damage arising in any way from its opening or use. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks for the correction, Jim. I was going by an IBM presentation that suggested z/OS 1.13 was the first release to get a "pure z/Architecture" IPL, but sometimes there are "unadvertised" details from people in the know. Much appreciated. There are some toleration PTFs (available under extended support) that are required to run z/OS 1.13 on z14 machines, so there's *something(s)* of concern even in 1.13. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Just in our latest upgrade from 2.1 to 2.3, we were recommended by various ISVs to apply service or even upgrade to a higher release. We mostly did as directed but in a few cases demurred. In some of those cases we got away with that, in other cases burned. I would never advise hoping to gliding on through. Too much changes from OS release to release. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Thursday, January 10, 2019 4:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: z/OS 1.12 question On 1/9/2019 11:05 PM, Brian Westerman wrote: > Most, if not all, of the installed (vendor) software at 1.12 will work > perfectly fine at 2.3. Don't know about most, but ALL seems highly unlikely. I can state with certainty that *every one* of the z/OS-based products we run here from other ISVs would need to be upgraded (or at least have all service applied if still supported) as would several of our own. My recommendation, especially for shops with a tendency to fall way behind like this one has, is to bite the bullet and upgrade to the "latest and greatest" release of everything possible whenever the opportunity presents itself. Running old, unsupported code on a new operating system is just asking for trouble. And, who knows how long it might be before you get another chance to upgrade? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
On 1/10/2019 5:12 PM, Tom Conley wrote: Good to know folks out there aren't exploiting extended GDG's. Which is amazing considering, without that support, you can't even maintain one generation per day for a year! =-O -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
On 1/10/2019 7:20 PM, Ed Jaffe wrote: On 1/9/2019 11:05 PM, Brian Westerman wrote: Most, if not all, of the installed (vendor) software at 1.12 will work perfectly fine at 2.3. Don't know about most, but ALL seems highly unlikely. I can state with certainty that *every one* of the z/OS-based products we run here from other ISVs would need to be upgraded (or at least have all service applied if still supported) as would several of our own. My recommendation, especially for shops with a tendency to fall way behind like this one has, is to bite the bullet and upgrade to the "latest and greatest" release of everything possible whenever the opportunity presents itself. Running old, unsupported code on a new operating system is just asking for trouble. And, who knows how long it might be before you get another chance to upgrade? I stand in violent agreement with my good friend, the honorable gentleman from California. Just last week, I discovered two products at V2R3 that were not upgraded to support extended GDG's (available at V2R2, THREE YEARS AGO!!). The vendors will be shipping us PTF's to finally support this feature. Good to know folks out there aren't exploiting extended GDG's. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
On 1/9/2019 11:05 PM, Brian Westerman wrote: Most, if not all, of the installed (vendor) software at 1.12 will work perfectly fine at 2.3. Don't know about most, but ALL seems highly unlikely. I can state with certainty that *every one* of the z/OS-based products we run here from other ISVs would need to be upgraded (or at least have all service applied if still supported) as would several of our own. My recommendation, especially for shops with a tendency to fall way behind like this one has, is to bite the bullet and upgrade to the "latest and greatest" release of everything possible whenever the opportunity presents itself. Running old, unsupported code on a new operating system is just asking for trouble. And, who knows how long it might be before you get another chance to upgrade? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks Jim. It might be something to at least try with a sandbox LPAR. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jim Mulder Sent: Thursday, January 10, 2019 1:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question In z/OS, for MVS, and SADMP IPLs, the support for pure z/Architecture IPL was introduced in z/OS 1.12. That is because I had time to work on it back then, and I was hoping that if it was implemented soon enough, we wouldn't need to roll it back to older releases via PTFs when some future z/Architecture-only machine got built. And that's how it worked out. The z14 was far enough in the future that no backporting to older release was needed. That does not necessarily mean that z/OS 1.12 will work on on a z/14. It just means that the removal of ESA/390 isn't the thing that will make it fail. I don't remember which release introduced the DFDSS Standalone Restore support for z/Architecture-only machines. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "Timothy Sipples" wrote on 01/09/2019 08:17:17 PM: > From: "Timothy Sipples" > To: ibm-main@listserv.ua.edu > Date: 01/10/2019 12:58 AM > Subject: Re: z/OS 1.12 question > > To elaborate a bit on the possible technical reasons why z/OS 1.12 probably > won't work on an IBM z14 machine, even if you've applied every PTF you can > lay your hands on to z/OS 1.12, the z14 is the first machine model to drop > ESA/390 IPL support. As background, when IBM introduced z/Architecture > (64-bit) support in z/OS (all the way back when z/OS was born), the first > major step was to engineer z/OS so that it would still start the IPL > process in ESA/390 mode, as in OS/390, but then it would switch to > z/Architecture mode if available. Up through and including z/OS 1.5 > the operating system could run on either ESA/390 or z/Architecture machines. If > z/Architecture was available, it would switch into that mode automatically. > > IBM also offered some add-on software called the "z/OS Bimodal > Migration Accommodation" for those early releases of z/OS up through > 1.5. That add-on > software would force z/OS to remain in ESA/390 mode on z/Architecture > machines. > > From z/OS 1.6, IBM dropped support for continuing the IPL and running z/OS > in ESA/390 mode. The z/OS-initiated switch early in the IPL to > z/Architecture mode became mandatory. z/OS 1.6 was the first z/OS release > that could only run on z/Architecture machines, and (after the early > IPL > phase) it always ran in 64-bit mode. > > The z14 dropped support for ESA/390 IPL, so any operating system that > starts its IPL in ESA/390 (31-bit) mode doesn't work on that machine model, > with one caveat that I'll explain in a moment. As far as I know IBM > only backported pure z/Architecture IPL to z/OS 1.13 (under extended > support) and higher, not to z/OS 1.12 or prior. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks Brian. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Thursday, January 10, 2019 2:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question The OP needs to remember though that none of (or only very little of) that information is necessary. Assuming they share DASD, they can install the new z/OS 2.2 or 2.3 (I would go with 2.3) software for the z14 from the z10, after the first IPL of the z14 the cut-over from one to the other is dead simple and I (and many others) have done it lots of times. The architecture differences between the z10 and z14 are almost meaningless in that migration once they are both "up". Since they are so far back (release-wise) it's probably actually in many ways easier for them to migrate. As long as they don't try to do something really silly (like move as a sysplex) there should be very few (if any) issues with the migration. In fact, aside from local mods and exits it should be a very smooth migration. It's not that nothing can happen, but 1.12 is not really that old and converting from 1.12 to 2.3 is not really substantially different from converting to 1.13 or 2.1. Most, if not all, of the installed (vendor) software at 1.12 will work perfectly fine at 2.3. The IBM software is probably not a factor here as most will likely be replaced with the new OS version, but older versions of software (DB2, IMS, CICS) that will run on z/OS 1.12 will run perfectly fine on z/OS 2.3. Most other vendor software is equally migrated with very little effort (aside from reassembling some interface modules), so they should have no real problems. If the OP has any questions on how to do this, he/she should feel welcome to ask me (or anyone else here) for help. It's no problem and I for one am always interested in hearing about how others go about their migrations. Just make sure you create a plan and follow the plan, don't try to "wing it". Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
The OP needs to remember though that none of (or only very little of) that information is necessary. Assuming they share DASD, they can install the new z/OS 2.2 or 2.3 (I would go with 2.3) software for the z14 from the z10, after the first IPL of the z14 the cut-over from one to the other is dead simple and I (and many others) have done it lots of times. The architecture differences between the z10 and z14 are almost meaningless in that migration once they are both "up". Since they are so far back (release-wise) it's probably actually in many ways easier for them to migrate. As long as they don't try to do something really silly (like move as a sysplex) there should be very few (if any) issues with the migration. In fact, aside from local mods and exits it should be a very smooth migration. It's not that nothing can happen, but 1.12 is not really that old and converting from 1.12 to 2.3 is not really substantially different from converting to 1.13 or 2.1. Most, if not all, of the installed (vendor) software at 1.12 will work perfectly fine at 2.3. The IBM software is probably not a factor here as most will likely be replaced with the new OS version, but older versions of software (DB2, IMS, CICS) that will run on z/OS 1.12 will run perfectly fine on z/OS 2.3. Most other vendor software is equally migrated with very little effort (aside from reassembling some interface modules), so they should have no real problems. If the OP has any questions on how to do this, he/she should feel welcome to ask me (or anyone else here) for help. It's no problem and I for one am always interested in hearing about how others go about their migrations. Just make sure you create a plan and follow the plan, don't try to "wing it". Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
In z/OS, for MVS, and SADMP IPLs, the support for pure z/Architecture IPL was introduced in z/OS 1.12. That is because I had time to work on it back then, and I was hoping that if it was implemented soon enough, we wouldn't need to roll it back to older releases via PTFs when some future z/Architecture-only machine got built. And that's how it worked out. The z14 was far enough in the future that no backporting to older release was needed. That does not necessarily mean that z/OS 1.12 will work on on a z/14. It just means that the removal of ESA/390 isn't the thing that will make it fail. I don't remember which release introduced the DFDSS Standalone Restore support for z/Architecture-only machines. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "Timothy Sipples" wrote on 01/09/2019 08:17:17 PM: > From: "Timothy Sipples" > To: ibm-main@listserv.ua.edu > Date: 01/10/2019 12:58 AM > Subject: Re: z/OS 1.12 question > > To elaborate a bit on the possible technical reasons why z/OS 1.12 probably > won't work on an IBM z14 machine, even if you've applied every PTF you can > lay your hands on to z/OS 1.12, the z14 is the first machine model to drop > ESA/390 IPL support. As background, when IBM introduced z/Architecture > (64-bit) support in z/OS (all the way back when z/OS was born), the first > major step was to engineer z/OS so that it would still start the IPL > process in ESA/390 mode, as in OS/390, but then it would switch to > z/Architecture mode if available. Up through and including z/OS 1.5 the > operating system could run on either ESA/390 or z/Architecture machines. If > z/Architecture was available, it would switch into that mode automatically. > > IBM also offered some add-on software called the "z/OS Bimodal Migration > Accommodation" for those early releases of z/OS up through 1.5. That add-on > software would force z/OS to remain in ESA/390 mode on z/Architecture > machines. > > From z/OS 1.6, IBM dropped support for continuing the IPL and running z/OS > in ESA/390 mode. The z/OS-initiated switch early in the IPL to > z/Architecture mode became mandatory. z/OS 1.6 was the first z/OS release > that could only run on z/Architecture machines, and (after the early IPL > phase) it always ran in 64-bit mode. > > The z14 dropped support for ESA/390 IPL, so any operating system that > starts its IPL in ESA/390 (31-bit) mode doesn't work on that machine model, > with one caveat that I'll explain in a moment. As far as I know IBM only > backported pure z/Architecture IPL to z/OS 1.13 (under extended support) > and higher, not to z/OS 1.12 or prior. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
To elaborate a bit on the possible technical reasons why z/OS 1.12 probably won't work on an IBM z14 machine, even if you've applied every PTF you can lay your hands on to z/OS 1.12, the z14 is the first machine model to drop ESA/390 IPL support. As background, when IBM introduced z/Architecture (64-bit) support in z/OS (all the way back when z/OS was born), the first major step was to engineer z/OS so that it would still start the IPL process in ESA/390 mode, as in OS/390, but then it would switch to z/Architecture mode if available. Up through and including z/OS 1.5 the operating system could run on either ESA/390 or z/Architecture machines. If z/Architecture was available, it would switch into that mode automatically. IBM also offered some add-on software called the "z/OS Bimodal Migration Accommodation" for those early releases of z/OS up through 1.5. That add-on software would force z/OS to remain in ESA/390 mode on z/Architecture machines. >From z/OS 1.6, IBM dropped support for continuing the IPL and running z/OS in ESA/390 mode. The z/OS-initiated switch early in the IPL to z/Architecture mode became mandatory. z/OS 1.6 was the first z/OS release that could only run on z/Architecture machines, and (after the early IPL phase) it always ran in 64-bit mode. The z14 dropped support for ESA/390 IPL, so any operating system that starts its IPL in ESA/390 (31-bit) mode doesn't work on that machine model, with one caveat that I'll explain in a moment. As far as I know IBM only backported pure z/Architecture IPL to z/OS 1.13 (under extended support) and higher, not to z/OS 1.12 or prior. OK, here's the caveat. As further background, z/VSE underwent a similar evolution in how it IPLs. z/VSE 5.2 and above will IPL on IBM z14 machines even without any PTFs (although PTFs may very well be recommended for other reasons). IBM developed a PTF for z/VSE 5.1 to allow that release to IPL on z14 machines, to be "z/Architecture clean" as it were. But for the z/VSE 4.x releases (and prior), no go. IBM never developed PTFs to retrofit z/Architecture IPL from the very start of the IPL process to any of the z/VSE 4.x releases. However, although all z/VSE 4.x releases are out of support (and have been for years now), those releases are known to be able to IPL on an IBM z14 machine as z/VM guests, not in LPARs. In z/VM you have to use SET MACH ESA to make that work. Will z/OS 1.12 run as a guest under z/VM on an IBM z14 machine in similar fashion (SET MACH ESA)? You're welcome to try provided you've got the right licenses. If you decide to do that you should be fully aware that it's unsupported, and (if it works) you would only want to run that way on a very short term basis for migration purposes only, to help get up to a supported z/OS release. If you don't have a z/VM license, IBM offers sub-capacity z/VM licensing. You can license as little as one engine for z/VM if you wish. For example, if you have an IBM z14 ZR1 capacity model U03, that machine has 3 general purpose engines. You can license one, two, or all three of them for z/VM, as you wish, and then as long as you configure your z/VM LPAR(s) consistent with your licensing (and collect and keep the sub-capacity reports if you're licensing fewer than 3 engines), you're fine. You may also wish to check with your "friendly IBM representative" to inquire about a z/VM evaluation license which might be available under certain circumstances, and if this bit of speculation about z/OS 1.12 has any merit to help you upgrade. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks Timothy -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Timothy Sipples Sent: Tuesday, January 08, 2019 1:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question IBM offered extended support for z/OS 1.12 through September 30, 2017, for a fee. That end date was "close enough" to miss the first shipments of the first IBM z14 machines. To my knowledge IBM never did the work to make z/OS 1.12 tolerate the IBM z14 machines, so if that particular combination works it's only accidental and unsupported. You're welcome to try as long as you're licensed, but I don't think it'll work. Sometimes you can get a little farther in accidental working terms when you run z/OS under z/VM. You've got a couple realistic and viable options to upgrade: 1. With coexistence/fallback with z/OS 1.12, you could run z/OS 2.1 on your IBM z10BC machine and on your IBM z14 machine. z/OS 2.1 has reached End of Service, but fee-based extended support is still available from IBM. The basic path would be as follows: (a) Migrate from z/OS 1.12 to z/OS 2.1 (with extended support) on your z10BC machine, with coexistence/fallback support. (b) Migrate from your z10BC to your z14. (c) Migrate from z/OS 2.1 to z/OS 2.3, also with coexistence/fallback support. This path is the most conventional and lowest risk, although it might require more budget and/or time than the other paths I'm about to describe. 2. Without coexistence/fallback with z/OS 1.12, you could run z/OS 2.2 on your IBM z10BC machine and on your IBM z14 machine. z/OS 2.2 is currently (as I write this) within its standard support period. You just need to be careful not to share datasets between z/OS 1.12 and z/OS 2.2, or at least if you do so to do it very carefully and very selectively, preferably with the advice and support of a z/OS migration specialist who knows what he/she is doing. The path would be as follows: (a) Migrate from z/OS 1.12 to z/OS 2.2 on your z10BC (without coexistence/fallback support). (b) Migrate from your z10BC to your z14. (c) In due course, migrate from z/OS 2.2 to either z/OS 2.3 or (assuming past coexistence/fallback support predicts the future) the following z/OS release. 3. Without coexistence/fallback, a "diagonal" jump from z/OS 1.12 on your z10BC directly to z/OS 2.3 on your z14. Exactly which of these three options is "best" depends on your particular circumstances, such as the complexity and mission criticality of your particular environment. Sometimes the "best" approach is to attempt one of these paths (such as #3) and see how it goes but then fall back to a more "conservative" path if necessary. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks Brian. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Tuesday, January 08, 2019 4:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question While we didn't have exactly the same hardware mix, at one of our clients in November we were able to place a z14 and a z9 (with z/OS 1.12) side by side (shared DASD) and installed z/OS 2.3 on the z14 by downloading and doing the base installation of zos from the z9, then ipling the z14 and completing the installation from there. The only even semi difficult part was that I had to generate the initial IOCP on the z14 manually. I think we also "cheated" by generating the initial 2.3 IODF offsite and export/imported it to the z9 s that we could place it on the system volume for the new install, but that part may not have even been necessary as our IBM CE told us (afterwards of course) that the z14 would have been fine with one we generated for the "wrong" cpu. Alternatively, we could have got the COD, but we didn't want to wait. In all, the longest part of the installation was sitting at the HMC doing the initial upload because we couldn't figure out how to get FTP to work right. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
While we didn't have exactly the same hardware mix, at one of our clients in November we were able to place a z14 and a z9 (with z/OS 1.12) side by side (shared DASD) and installed z/OS 2.3 on the z14 by downloading and doing the base installation of zos from the z9, then ipling the z14 and completing the installation from there. The only even semi difficult part was that I had to generate the initial IOCP on the z14 manually. I think we also "cheated" by generating the initial 2.3 IODF offsite and export/imported it to the z9 s that we could place it on the system volume for the new install, but that part may not have even been necessary as our IBM CE told us (afterwards of course) that the z14 would have been fine with one we generated for the "wrong" cpu. Alternatively, we could have got the COD, but we didn't want to wait. In all, the longest part of the installation was sitting at the HMC doing the initial upload because we couldn't figure out how to get FTP to work right. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
I ran this by someone who really knows what he is doing concerning upgrades and here is what he recommended: > He can't run 1.12 on the new z14s, and he doesn't want to even think about > all the patching for 1.13 or 2.1. His best bet is to go to 2.2 on his z10, > then put the z14s patches on 2.2, then upgrade to the z14s, then go to 2.4 > when it goes GA. the end of this year. Good luck with this! Ken Kenneth A. Bloom CEO Avenir Technologies Inc /d/b/a Visara International 203-984-2235 bl...@visara.com www.visara.com > On Jan 8, 2019, at 1:54 AM, Timothy Sipples wrote: > > IBM offered extended support for z/OS 1.12 through September 30, 2017, for > a fee. That end date was "close enough" to miss the first shipments of the > first IBM z14 machines. To my knowledge IBM never did the work to make z/OS > 1.12 tolerate the IBM z14 machines, so if that particular combination works > it's only accidental and unsupported. You're welcome to try as long as > you're licensed, but I don't think it'll work. Sometimes you can get a > little farther in accidental working terms when you run z/OS under z/VM. > > You've got a couple realistic and viable options to upgrade: > > 1. With coexistence/fallback with z/OS 1.12, you could run z/OS 2.1 on your > IBM z10BC machine and on your IBM z14 machine. z/OS 2.1 has reached End of > Service, but fee-based extended support is still available from IBM. The > basic path would be as follows: > > (a) Migrate from z/OS 1.12 to z/OS 2.1 (with extended support) on your > z10BC machine, with coexistence/fallback support. > (b) Migrate from your z10BC to your z14. > (c) Migrate from z/OS 2.1 to z/OS 2.3, also with coexistence/fallback > support. > > This path is the most conventional and lowest risk, although it might > require more budget and/or time than the other paths I'm about to describe. > > 2. Without coexistence/fallback with z/OS 1.12, you could run z/OS 2.2 on > your IBM z10BC machine and on your IBM z14 machine. z/OS 2.2 is currently > (as I write this) within its standard support period. You just need to be > careful not to share datasets between z/OS 1.12 and z/OS 2.2, or at least > if you do so to do it very carefully and very selectively, preferably with > the advice and support of a z/OS migration specialist who knows what he/she > is doing. The path would be as follows: > > (a) Migrate from z/OS 1.12 to z/OS 2.2 on your z10BC (without > coexistence/fallback support). > (b) Migrate from your z10BC to your z14. > (c) In due course, migrate from z/OS 2.2 to either z/OS 2.3 or (assuming > past coexistence/fallback support predicts the future) the following z/OS > release. > > 3. Without coexistence/fallback, a "diagonal" jump from z/OS 1.12 on your > z10BC directly to z/OS 2.3 on your z14. > > Exactly which of these three options is "best" depends on your particular > circumstances, such as the complexity and mission criticality of your > particular environment. Sometimes the "best" approach is to attempt one of > these paths (such as #3) and see how it goes but then fall back to a more > "conservative" path if necessary. > > > Timothy Sipples > IT Architect Executive, Industry Solutions, IBM Z & LinuxONE > > > E-Mail: sipp...@sg.ibm.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
IBM offered extended support for z/OS 1.12 through September 30, 2017, for a fee. That end date was "close enough" to miss the first shipments of the first IBM z14 machines. To my knowledge IBM never did the work to make z/OS 1.12 tolerate the IBM z14 machines, so if that particular combination works it's only accidental and unsupported. You're welcome to try as long as you're licensed, but I don't think it'll work. Sometimes you can get a little farther in accidental working terms when you run z/OS under z/VM. You've got a couple realistic and viable options to upgrade: 1. With coexistence/fallback with z/OS 1.12, you could run z/OS 2.1 on your IBM z10BC machine and on your IBM z14 machine. z/OS 2.1 has reached End of Service, but fee-based extended support is still available from IBM. The basic path would be as follows: (a) Migrate from z/OS 1.12 to z/OS 2.1 (with extended support) on your z10BC machine, with coexistence/fallback support. (b) Migrate from your z10BC to your z14. (c) Migrate from z/OS 2.1 to z/OS 2.3, also with coexistence/fallback support. This path is the most conventional and lowest risk, although it might require more budget and/or time than the other paths I'm about to describe. 2. Without coexistence/fallback with z/OS 1.12, you could run z/OS 2.2 on your IBM z10BC machine and on your IBM z14 machine. z/OS 2.2 is currently (as I write this) within its standard support period. You just need to be careful not to share datasets between z/OS 1.12 and z/OS 2.2, or at least if you do so to do it very carefully and very selectively, preferably with the advice and support of a z/OS migration specialist who knows what he/she is doing. The path would be as follows: (a) Migrate from z/OS 1.12 to z/OS 2.2 on your z10BC (without coexistence/fallback support). (b) Migrate from your z10BC to your z14. (c) In due course, migrate from z/OS 2.2 to either z/OS 2.3 or (assuming past coexistence/fallback support predicts the future) the following z/OS release. 3. Without coexistence/fallback, a "diagonal" jump from z/OS 1.12 on your z10BC directly to z/OS 2.3 on your z14. Exactly which of these three options is "best" depends on your particular circumstances, such as the complexity and mission criticality of your particular environment. Sometimes the "best" approach is to attempt one of these paths (such as #3) and see how it goes but then fall back to a more "conservative" path if necessary. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z & LinuxONE E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Probably not if you dont already have a support contract. BUT - You could LPAR your current machine, install z/os like 2.1 or so , upgrade then move and upgrade again. Joe On Mon, Jan 7, 2019 at 1:57 PM Edgington, Jerry < jerry.edging...@westernsouthernlife.com> wrote: > Is z/OS v1.13 still orderable from IBM? That might be a path, if we can > get the code base with all the necessary features. Thanks. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joe Monk > Sent: Monday, January 07, 2019 2:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS 1.12 question > > I dont see why he couldnt install z/OS 1.13 on the old box, then move that > to the new box and upgrade... > > Joe > > On Mon, Jan 7, 2019 at 1:37 PM Ed Jaffe > wrote: > > > On 1/7/2019 5:47 AM, Edgington, Jerry wrote: > > > Our current situation is, we have zBC10 running z/OS v1.12. We want > > > to > > upgrade everything to current, including z/OS and hardware. I > > understand we can't get support for either z/OS or zBC12, but I am > > looking for options and if anyone has successfully done this type of > > upgrade. If so, what steps were taken? > > > > > > - Can we get maintenance for z/OS v1.12, understanding we might have > > > to > > pay IBM something for it? > > > - Will z/OS v1.12 work on z14, I understand the answer is maybe. > > > But, > > has anyone done it? If so and willing to share, we would like to know > > > - If not, we are looking at the possibility of move z/OS v1.12 to > > > zBC12, > > upgrade to z/OS v2.3, then z14. Again, we probably would need > > maintenance on z/OS v1.12 > > > > Must it be a push/pull install of the hardware? Or can you install the > > new z14 side-by-side with the z10 connected to the same DASD? > > > > -- > > Phoenix Software International > > Edward E. Jaffe > > 831 Parkview Drive North > > El Segundo, CA 90245 > > https://www.phoenixsoftware.com/ > > > > > > > > -- > > -- This e-mail message, including any attachments, appended > > messages and the information contained therein, is for the sole use of > > the intended recipient(s). If you are not an intended recipient or > > have otherwise received this email message in error, any use, > > dissemination, distribution, review, storage or copying of this e-mail > > message and the information contained therein is strictly prohibited. > > If you are not an intended recipient, please contact the sender by > > reply e-mail and destroy all copies of this email message and do not > > otherwise utilize or retain this email message or any or all of the > > information contained therein. Although this email message and any > > attachments or appended messages are believed to be free of any virus > > or other defect that might affect any computer system into which it is > > received and opened, it is the responsibility of the recipient to > > ensure that it is virus free and no responsibility is accepted by the > > sender for any loss or damage arising in any way from its opening or use. > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Is z/OS v1.13 still orderable from IBM? That might be a path, if we can get the code base with all the necessary features. Thanks. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joe Monk Sent: Monday, January 07, 2019 2:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question I dont see why he couldnt install z/OS 1.13 on the old box, then move that to the new box and upgrade... Joe On Mon, Jan 7, 2019 at 1:37 PM Ed Jaffe wrote: > On 1/7/2019 5:47 AM, Edgington, Jerry wrote: > > Our current situation is, we have zBC10 running z/OS v1.12. We want > > to > upgrade everything to current, including z/OS and hardware. I > understand we can't get support for either z/OS or zBC12, but I am > looking for options and if anyone has successfully done this type of > upgrade. If so, what steps were taken? > > > > - Can we get maintenance for z/OS v1.12, understanding we might have > > to > pay IBM something for it? > > - Will z/OS v1.12 work on z14, I understand the answer is maybe. > > But, > has anyone done it? If so and willing to share, we would like to know > > - If not, we are looking at the possibility of move z/OS v1.12 to > > zBC12, > upgrade to z/OS v2.3, then z14. Again, we probably would need > maintenance on z/OS v1.12 > > Must it be a push/pull install of the hardware? Or can you install the > new z14 side-by-side with the z10 connected to the same DASD? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > -- > -- This e-mail message, including any attachments, appended > messages and the information contained therein, is for the sole use of > the intended recipient(s). If you are not an intended recipient or > have otherwise received this email message in error, any use, > dissemination, distribution, review, storage or copying of this e-mail > message and the information contained therein is strictly prohibited. > If you are not an intended recipient, please contact the sender by > reply e-mail and destroy all copies of this email message and do not > otherwise utilize or retain this email message or any or all of the > information contained therein. Although this email message and any > attachments or appended messages are believed to be free of any virus > or other defect that might affect any computer system into which it is > received and opened, it is the responsibility of the recipient to > ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
I dont see why he couldnt install z/OS 1.13 on the old box, then move that to the new box and upgrade... Joe On Mon, Jan 7, 2019 at 1:37 PM Ed Jaffe wrote: > On 1/7/2019 5:47 AM, Edgington, Jerry wrote: > > Our current situation is, we have zBC10 running z/OS v1.12. We want to > upgrade everything to current, including z/OS and hardware. I understand > we can't get support for either z/OS or zBC12, but I am looking for options > and if anyone has successfully done this type of upgrade. If so, what steps > were taken? > > > > - Can we get maintenance for z/OS v1.12, understanding we might have to > pay IBM something for it? > > - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, > has anyone done it? If so and willing to share, we would like to know > > - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, > upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance > on z/OS v1.12 > > Must it be a push/pull install of the hardware? Or can you install the > new z14 side-by-side with the z10 connected to the same DASD? > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Ed, Yes, I believe we can do have the new z14 installed and connected to the same DASD. Jerry -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Monday, January 07, 2019 2:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question On 1/7/2019 5:47 AM, Edgington, Jerry wrote: > Our current situation is, we have zBC10 running z/OS v1.12. We want to > upgrade everything to current, including z/OS and hardware. I understand we > can't get support for either z/OS or zBC12, but I am looking for options and > if anyone has successfully done this type of upgrade. If so, what steps were > taken? > > - Can we get maintenance for z/OS v1.12, understanding we might have to pay > IBM something for it? > - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, > has anyone done it? If so and willing to share, we would like to know > - If not, we are looking at the possibility of move z/OS v1.12 to > zBC12, upgrade to z/OS v2.3, then z14. Again, we probably would need > maintenance on z/OS v1.12 Must it be a push/pull install of the hardware? Or can you install the new z14 side-by-side with the z10 connected to the same DASD? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
On 1/7/2019 5:47 AM, Edgington, Jerry wrote: Our current situation is, we have zBC10 running z/OS v1.12. We want to upgrade everything to current, including z/OS and hardware. I understand we can't get support for either z/OS or zBC12, but I am looking for options and if anyone has successfully done this type of upgrade. If so, what steps were taken? - Can we get maintenance for z/OS v1.12, understanding we might have to pay IBM something for it? - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, has anyone done it? If so and willing to share, we would like to know - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance on z/OS v1.12 Must it be a push/pull install of the hardware? Or can you install the new z14 side-by-side with the z10 connected to the same DASD? -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Surely local non-SNS 3270 displays can be used for both console and TSO terminals. I wonder about OSA, though. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Richards, Robert B. <01c91f408b9e-dmarc-requ...@listserv.ua.edu> Sent: Monday, January 7, 2019 8:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question https://secure-web.cisco.com/1TOE1-6JvBhycTADWSatyN1K6wnIMpBooZT-Ijh1KiJ2AJelOhIk-yPN5u85UBtSjMW9Sc_DO0JEpncOvUHezJSbAlOJUTR7USDj80zmT3s6oBELK79PzECWALl6zsleuKp8DqER1ludAbFyODkFbUkWBUnEL7YsyTBL4x-Ol8hgCJB5UQrxfVTunnEX0E78UylbWOZELZ9arfKZVPqF9CDvAjz8GGdLq1NfV_wdfknYNbf0EY7AZlutMDPSrIlfngjl2E-W8UzxB98eNZGberf0t2glG_UhrIHZ-mZwaRdjbRBfI9O9xOptB-C6TUPgBXYQI2D8ik36MtSsIlRGPNNOp2dal182MfJxcmVfEp4CGZSc9RH1MFnffXHP-PX9zlHLBk7h6K4ubdr5caaCia2mdfvmm4qbFwG7heLxRsSXV-UwdKD_JYmtv_j4FJqRV/https%3A%2F%2Fwww-01.ibm.com%2Fcommon%2Fssi%2Fcgi-bin%2Fssialias%3Finfotype%3Dan%26subtype%3Dca%26appname%3Dgpateam%26supplier%3D897%26letternum%3DENUS218-458 IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system to meet IBM z/OS installation requirements, has been updated. The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in dump-by-dataset format, where available), and z/OS Custom-Built Product Delivery Offering (CBPDO) packages when you do not have a driving system that meets the minimum requirements for IBM z/OS installation. The Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is supported by z/OS V2.2, or later. The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, a non-Systems Network Architecture (SNA) terminal or Hardware Management Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver is delivered on DVD media. For up-to-date information about the Customized Offerings Driver, including supported media, DASD volume sizes, product levels included, z/OS hardware and software prerequisites, and driving system requirements, see the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for Installation (GA32-0890) at the z/OS Internet Library. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Monday, January 07, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 1.12 question As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current. Thanks, Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
One option is to bring up the new z/OS on the z14 and restore the applications and test and recompile as needed then freeze the data and run from the new system. On Mon, Jan 7, 2019 at 7:48 AM Edgington, Jerry wrote: > > Thanks everyone. > > Our current situation is, we have zBC10 running z/OS v1.12. We want to > upgrade everything to current, including z/OS and hardware. I understand we > can't get support for either z/OS or zBC12, but I am looking for options and > if anyone has successfully done this type of upgrade. If so, what steps were > taken? > > - Can we get maintenance for z/OS v1.12, understanding we might have to pay > IBM something for it? > - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, has > anyone done it? If so and willing to share, we would like to know > - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, > upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance on > z/OS v1.12 > > Jerry > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Richards, Robert B. > Sent: Monday, January 07, 2019 8:42 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS 1.12 question > > I must have misinterpreted the following then: > > " If not, any ideas of how to get z/OS *and* hardware upgrade to current." > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Monday, January 07, 2019 8:26 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS 1.12 question > > IMHO the COD has nothing to do here. > Jerry wrote about mahcine change (upgrade) , not OS upgrade. > > Jerry, > Your system is out of service. That means you won't be able to get *for > free* any PTFs released after EOS date. That means your system may not > recognize z14 correctly. It does NOT mean it won't work at all, but there's a > risk. > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: > > https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an > > =ca=gpateam=897=ENUS218-458 > > > > IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving > > system to meet IBM z/OS installation requirements, has been updated. > > > > The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving > > system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in > > dump-by-dataset format, where available), and z/OS Custom-Built Product > > Delivery Offering (CBPDO) packages when you do not have a driving system > > that meets the minimum requirements for IBM z/OS installation. The > > Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 > > system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) > > processor that is supported by z/OS V2.2, or later. > > > > The Customized Offerings Driver requires three 3390-9 or larger DASD > > volumes, a non-Systems Network Architecture (SNA) terminal or Hardware > > Management Console (HMC) 3270 emulator for a z/OS console, and an SNA > > terminal for a Time Sharing Option Extended (TSO/E) session. The Customized > > Offerings Driver is delivered on DVD media. > > > > For up-to-date information about the Customized Offerings Driver, including > > supported media, DASD volume sizes, product levels included, z/OS hardware > > and software prerequisites, and driving system requirements, see the > > current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning > > for Installation (GA32-0890) at the z/OS Internet Library. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Edgington, Jerry > > Sent: Monday, January 07, 2019 7:57 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: z/OS 1.12 question > > > > As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what > > issues or gothas were there? Anything to look at for? If not, any ideas of > > how to get z/OS and hardware upgrade to current. > > > > Thanks, > > Jerry Edgington > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send
Re: z/OS 1.12 question
Thank you very much. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Monday, January 07, 2019 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question Jerry, In that scenario I would do the following: Install z/OS 2.3 using COD. That means you first install COD and then perform the installation of z/OS. Or I would try to use ServerPac Installation Dialog on z/OS 1.12. At least one problem *will* happen: ZFS >4GB, but you can address it by using SMS-managed ZFSes which is not bad idea. Important: z/OS 2.3 will be IPL-ed on z14, but Driver part of installation can be performed on BC10. Of course you have to have both machines concurrently connected to shared DASD. That also means you have to put some IOCP.txt to the z14. Side notes: - current COD base is (AFAIK) z/OS 2.2, which means you can run it on BC10 or z14, because both machines are supported for z/OS 2.2. - you could try to get z/OS 2.2 which runs on BC10, but IMHO it is not worth the troubles and money. - Regarding paid support for z/OS 1.12 - IBM offers "extended service" for systems which went end of (regular) service, but this is paid and also time-limited. I don't know whether 1.12 extedded support covers Z14ZR1, but it's really not worth to pay for that when you have both machines on the floor. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:47, Edgington, Jerry pisze: > Thanks everyone. > > Our current situation is, we have zBC10 running z/OS v1.12. We want to > upgrade everything to current, including z/OS and hardware. I understand we > can't get support for either z/OS or zBC12, but I am looking for options and > if anyone has successfully done this type of upgrade. If so, what steps were > taken? > > - Can we get maintenance for z/OS v1.12, understanding we might have to pay > IBM something for it? > - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, has > anyone done it? If so and willing to share, we would like to know > - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, > upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance on > z/OS v1.12 > > Jerry > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Richards, Robert B. > Sent: Monday, January 07, 2019 8:42 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS 1.12 question > > I must have misinterpreted the following then: > > " If not, any ideas of how to get z/OS *and* hardware upgrade to current." > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Monday, January 07, 2019 8:26 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: z/OS 1.12 question > > IMHO the COD has nothing to do here. > Jerry wrote about mahcine change (upgrade) , not OS upgrade. > > Jerry, > Your system is out of service. That means you won't be able to get *for > free* any PTFs released after EOS date. That means your system may not > recognize z14 correctly. It does NOT mean it won't work at all, but there's a > risk. > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: >> https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an >> =ca=gpateam=897=ENUS218-458 >> >> IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system >> to meet IBM z/OS installation requirements, has been updated. >> >> The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving >> system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in >> dump-by-dataset format, where available), and z/OS Custom-Built Product >> Delivery Offering (CBPDO) packages when you do not have a driving system >> that meets the minimum requirements for IBM z/OS installation. The >> Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 >> system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) >> processor that is supported by z/OS V2.2, or later. >> >> The Customized Offerings Driver requires three 3390-9 or larger DASD >> volumes, a non-Systems Network Architecture (SNA) terminal or Hardware >> Management Console (HMC) 3270 emulator for a z/OS console, and an SNA >> terminal for a Time Sharing Option Extended (TSO/E) session. The Customized >> Offerings Driver is delivered on DVD media. >> >> For up-to-date information about the Customized Offerings Driver, including >> supported media, DASD volume sizes, product levels included, z/OS
Re: z/OS 1.12 question
Jerry, In that scenario I would do the following: Install z/OS 2.3 using COD. That means you first install COD and then perform the installation of z/OS. Or I would try to use ServerPac Installation Dialog on z/OS 1.12. At least one problem *will* happen: ZFS >4GB, but you can address it by using SMS-managed ZFSes which is not bad idea. Important: z/OS 2.3 will be IPL-ed on z14, but Driver part of installation can be performed on BC10. Of course you have to have both machines concurrently connected to shared DASD. That also means you have to put some IOCP.txt to the z14. Side notes: - current COD base is (AFAIK) z/OS 2.2, which means you can run it on BC10 or z14, because both machines are supported for z/OS 2.2. - you could try to get z/OS 2.2 which runs on BC10, but IMHO it is not worth the troubles and money. - Regarding paid support for z/OS 1.12 - IBM offers "extended service" for systems which went end of (regular) service, but this is paid and also time-limited. I don't know whether 1.12 extedded support covers Z14ZR1, but it's really not worth to pay for that when you have both machines on the floor. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:47, Edgington, Jerry pisze: Thanks everyone. Our current situation is, we have zBC10 running z/OS v1.12. We want to upgrade everything to current, including z/OS and hardware. I understand we can't get support for either z/OS or zBC12, but I am looking for options and if anyone has successfully done this type of upgrade. If so, what steps were taken? - Can we get maintenance for z/OS v1.12, understanding we might have to pay IBM something for it? - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, has anyone done it? If so and willing to share, we would like to know - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance on z/OS v1.12 Jerry -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Monday, January 07, 2019 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question I must have misinterpreted the following then: " If not, any ideas of how to get z/OS *and* hardware upgrade to current." -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Monday, January 07, 2019 8:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question IMHO the COD has nothing to do here. Jerry wrote about mahcine change (upgrade) , not OS upgrade. Jerry, Your system is out of service. That means you won't be able to get *for free* any PTFs released after EOS date. That means your system may not recognize z14 correctly. It does NOT mean it won't work at all, but there's a risk. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an =ca=gpateam=897=ENUS218-458 IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system to meet IBM z/OS installation requirements, has been updated. The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in dump-by-dataset format, where available), and z/OS Custom-Built Product Delivery Offering (CBPDO) packages when you do not have a driving system that meets the minimum requirements for IBM z/OS installation. The Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is supported by z/OS V2.2, or later. The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, a non-Systems Network Architecture (SNA) terminal or Hardware Management Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver is delivered on DVD media. For up-to-date information about the Customized Offerings Driver, including supported media, DASD volume sizes, product levels included, z/OS hardware and software prerequisites, and driving system requirements, see the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for Installation (GA32-0890) at the z/OS Internet Library. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Monday, January 07, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 1.12 question As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current.
Re: z/OS 1.12 question
OK, beat me ;-) I missed the "z/OS" part in the statement. Silly me. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:41, Richards, Robert B. pisze: I must have misinterpreted the following then: " If not, any ideas of how to get z/OS *and* hardware upgrade to current." -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Monday, January 07, 2019 8:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question IMHO the COD has nothing to do here. Jerry wrote about mahcine change (upgrade) , not OS upgrade. Jerry, Your system is out of service. That means you won't be able to get *for free* any PTFs released after EOS date. That means your system may not recognize z14 correctly. It does NOT mean it won't work at all, but there's a risk. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an=ca=gpateam=897=ENUS218-458 IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system to meet IBM z/OS installation requirements, has been updated. The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in dump-by-dataset format, where available), and z/OS Custom-Built Product Delivery Offering (CBPDO) packages when you do not have a driving system that meets the minimum requirements for IBM z/OS installation. The Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is supported by z/OS V2.2, or later. The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, a non-Systems Network Architecture (SNA) terminal or Hardware Management Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver is delivered on DVD media. For up-to-date information about the Customized Offerings Driver, including supported media, DASD volume sizes, product levels included, z/OS hardware and software prerequisites, and driving system requirements, see the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for Installation (GA32-0890) at the z/OS Internet Library. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Monday, January 07, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 1.12 question As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current. == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
Thanks everyone. Our current situation is, we have zBC10 running z/OS v1.12. We want to upgrade everything to current, including z/OS and hardware. I understand we can't get support for either z/OS or zBC12, but I am looking for options and if anyone has successfully done this type of upgrade. If so, what steps were taken? - Can we get maintenance for z/OS v1.12, understanding we might have to pay IBM something for it? - Will z/OS v1.12 work on z14, I understand the answer is maybe. But, has anyone done it? If so and willing to share, we would like to know - If not, we are looking at the possibility of move z/OS v1.12 to zBC12, upgrade to z/OS v2.3, then z14. Again, we probably would need maintenance on z/OS v1.12 Jerry -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Monday, January 07, 2019 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question I must have misinterpreted the following then: " If not, any ideas of how to get z/OS *and* hardware upgrade to current." -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Monday, January 07, 2019 8:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question IMHO the COD has nothing to do here. Jerry wrote about mahcine change (upgrade) , not OS upgrade. Jerry, Your system is out of service. That means you won't be able to get *for free* any PTFs released after EOS date. That means your system may not recognize z14 correctly. It does NOT mean it won't work at all, but there's a risk. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: > https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an > =ca=gpateam=897=ENUS218-458 > > IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system > to meet IBM z/OS installation requirements, has been updated. > > The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving > system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in > dump-by-dataset format, where available), and z/OS Custom-Built Product > Delivery Offering (CBPDO) packages when you do not have a driving system that > meets the minimum requirements for IBM z/OS installation. The Customized > Offerings Driver is updated and is now a subset of a z/OS V2.2 system with > Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is > supported by z/OS V2.2, or later. > > The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, > a non-Systems Network Architecture (SNA) terminal or Hardware Management > Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a > Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver > is delivered on DVD media. > > For up-to-date information about the Customized Offerings Driver, including > supported media, DASD volume sizes, product levels included, z/OS hardware > and software prerequisites, and driving system requirements, see the current > z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for > Installation (GA32-0890) at the z/OS Internet Library. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Edgington, Jerry > Sent: Monday, January 07, 2019 7:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: z/OS 1.12 question > > As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what > issues or gothas were there? Anything to look at for? If not, any ideas of > how to get z/OS and hardware upgrade to current. > > Thanks, > Jerry Edgington > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN . > == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. s
Re: z/OS 1.12 question
I must have misinterpreted the following then: " If not, any ideas of how to get z/OS *and* hardware upgrade to current." -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Monday, January 07, 2019 8:26 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 1.12 question IMHO the COD has nothing to do here. Jerry wrote about mahcine change (upgrade) , not OS upgrade. Jerry, Your system is out of service. That means you won't be able to get *for free* any PTFs released after EOS date. That means your system may not recognize z14 correctly. It does NOT mean it won't work at all, but there's a risk. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: > https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an=ca=gpateam=897=ENUS218-458 > > IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system > to meet IBM z/OS installation requirements, has been updated. > > The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving > system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in > dump-by-dataset format, where available), and z/OS Custom-Built Product > Delivery Offering (CBPDO) packages when you do not have a driving system that > meets the minimum requirements for IBM z/OS installation. The Customized > Offerings Driver is updated and is now a subset of a z/OS V2.2 system with > Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is > supported by z/OS V2.2, or later. > > The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, > a non-Systems Network Architecture (SNA) terminal or Hardware Management > Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a > Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver > is delivered on DVD media. > > For up-to-date information about the Customized Offerings Driver, including > supported media, DASD volume sizes, product levels included, z/OS hardware > and software prerequisites, and driving system requirements, see the current > z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for > Installation (GA32-0890) at the z/OS Internet Library. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Edgington, Jerry > Sent: Monday, January 07, 2019 7:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: z/OS 1.12 question > > As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what > issues or gothas were there? Anything to look at for? If not, any ideas of > how to get z/OS and hardware upgrade to current. > > Thanks, > Jerry Edgington > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488
Re: z/OS 1.12 question
z/OS 1.12 is not supported on a z14. So, his only choice is to upgrade z/OS if he wants to run a z14. Joe On Mon, Jan 7, 2019 at 7:26 AM R.S. wrote: > IMHO the COD has nothing to do here. > Jerry wrote about mahcine change (upgrade) , not OS upgrade. > > Jerry, > Your system is out of service. That means you won't be able to get *for > free* any PTFs released after EOS date. That means your system may not > recognize z14 correctly. It does NOT mean it won't work at all, but > there's a risk. > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: > > > https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an=ca=gpateam=897=ENUS218-458 > > > > IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving > system to meet IBM z/OS installation requirements, has been updated. > > > > The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone > driving system that can be used to install z/OS(r) ServerPac, z/OS > SystemPac (in dump-by-dataset format, where available), and z/OS > Custom-Built Product Delivery Offering (CBPDO) packages when you do not > have a driving system that meets the minimum requirements for IBM z/OS > installation. The Customized Offerings Driver is updated and is now a > subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run > on any IBM Z(r) processor that is supported by z/OS V2.2, or later. > > > > The Customized Offerings Driver requires three 3390-9 or larger DASD > volumes, a non-Systems Network Architecture (SNA) terminal or Hardware > Management Console (HMC) 3270 emulator for a z/OS console, and an SNA > terminal for a Time Sharing Option Extended (TSO/E) session. The Customized > Offerings Driver is delivered on DVD media. > > > > For up-to-date information about the Customized Offerings Driver, > including supported media, DASD volume sizes, product levels included, z/OS > hardware and software prerequisites, and driving system requirements, see > the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS > Planning for Installation (GA32-0890) at the z/OS Internet Library. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Edgington, Jerry > > Sent: Monday, January 07, 2019 7:57 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: z/OS 1.12 question > > > > As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what > issues or gothas were there? Anything to look at for? If not, any ideas of > how to get z/OS and hardware upgrade to current. > > > > Thanks, > > Jerry Edgington > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > . > > > > > == > > Jeśli nie jesteś adresatem tej wiadomości: > > - powiadom nas o tym w mailu zwrotnym (dziękujemy!), > - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub > zapisałeś na dysku). > Wiadomość ta może zawierać chronione prawem informacje, które może > wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia > (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, > narusza prawo i może podlegać karze. > > mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, > www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy > XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: > 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na > 01.01.2018 r. wynosi 169.248.488 złotych. > > If you are not the addressee of this message: > > - let us know by replying to this e-mail (thank you!), > - delete this message permanently (including all the copies which you have > printed out or saved). > This message may contain legally protected information, which may be used > exclusively by the addressee.Please be reminded that anyone who > disseminates (copies, distributes) this message or takes any similar > action, violates the law and may be penalised. > > mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 > Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the > Capital
Re: z/OS 1.12 question
IMHO the COD has nothing to do here. Jerry wrote about mahcine change (upgrade) , not OS upgrade. Jerry, Your system is out of service. That means you won't be able to get *for free* any PTFs released after EOS date. That means your system may not recognize z14 correctly. It does NOT mean it won't work at all, but there's a risk. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-01-07 o 14:01, Richards, Robert B. pisze: https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an=ca=gpateam=897=ENUS218-458 IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system to meet IBM z/OS installation requirements, has been updated. The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in dump-by-dataset format, where available), and z/OS Custom-Built Product Delivery Offering (CBPDO) packages when you do not have a driving system that meets the minimum requirements for IBM z/OS installation. The Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is supported by z/OS V2.2, or later. The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, a non-Systems Network Architecture (SNA) terminal or Hardware Management Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver is delivered on DVD media. For up-to-date information about the Customized Offerings Driver, including supported media, DASD volume sizes, product levels included, z/OS hardware and software prerequisites, and driving system requirements, see the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for Installation (GA32-0890) at the z/OS Internet Library. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Monday, January 07, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 1.12 question As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current. Thanks, Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN . == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS 1.12 question
https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an=ca=gpateam=897=ENUS218-458 IBM Customized Offerings Driver V3.1, a prebuilt, stand-alone driving system to meet IBM z/OS installation requirements, has been updated. The IBM(r) Customized Offerings Driver is a prebuilt, stand-alone driving system that can be used to install z/OS(r) ServerPac, z/OS SystemPac (in dump-by-dataset format, where available), and z/OS Custom-Built Product Delivery Offering (CBPDO) packages when you do not have a driving system that meets the minimum requirements for IBM z/OS installation. The Customized Offerings Driver is updated and is now a subset of a z/OS V2.2 system with Job Entry Subsystem 2 (JES2) that can run on any IBM Z(r) processor that is supported by z/OS V2.2, or later. The Customized Offerings Driver requires three 3390-9 or larger DASD volumes, a non-Systems Network Architecture (SNA) terminal or Hardware Management Console (HMC) 3270 emulator for a z/OS console, and an SNA terminal for a Time Sharing Option Extended (TSO/E) session. The Customized Offerings Driver is delivered on DVD media. For up-to-date information about the Customized Offerings Driver, including supported media, DASD volume sizes, product levels included, z/OS hardware and software prerequisites, and driving system requirements, see the current z/OS PSP bucket (Upgrade ZOSV2R3, Subset ZOSGEN) and z/OS Planning for Installation (GA32-0890) at the z/OS Internet Library. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Monday, January 07, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS 1.12 question As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current. Thanks, Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
z/OS 1.12 question
As anyone upgraded a z/OS 1.12 from zBC10 to z14, directly? If so, what issues or gothas were there? Anything to look at for? If not, any ideas of how to get z/OS and hardware upgrade to current. Thanks, Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
