Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
Ted, according to http://www-1.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html z/OS, z/OS.e, and OS/390 marketing and service announce, availability, and withdrawal dates projected date for service discontinued is the same for 1.4 and 1.5 (2007/03/31) Marian On 6/29/05, Ted MacNEIL <[EMAIL PROTECTED]> wrote: > ... > For example, I don't think IBM has officially announced an end-of-service > date for z/OS V1R5 yet, although the "projected" date is listed as March > 31, 2007. > ... > > Why would IBM expire two at the same time? > That's the EOS for 1.4! > > -teD > (The secret to success is sincerity. > If you can fake that, > you've got it made!) > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
>z/OS R6 is the currently orderable release. 1.4 is also SystemPac orderable for another couple weeks (until July 25, 2005). Last call! - - - - - Timothy F. Sipples Consulting Software Architect, Enterprise Transformation IBM Americas zSeries Software Phone: (312) 245-4003 E-Mail: [EMAIL PROTECTED] (PGP key available.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
See below. Peter Greening wrote: Had initially mentioned "only reference i've found so far is that z/OS 1.4 can coexist with z/OS 1.5, thru 1.7, but nothing about parallel sysplex". In hindsight that was obviously poorly proof-read. Coexistence includes parallel sysplex coexistence. i had been unable to find anything stating that zOS 1.4 can co-exist in a parallel sysplex with 1.5-1.7 when zOS1.4 is no longer supported. My question should simply have been "does it make any difference to this level of co-existence if z/OS 1.4 is out of support?" Look, this is pretty simple. z/OS R4 will coexist with z/OS R7. But once z/OS R4 is withdrawn from service, two things will happen. First, we will stop fixing any new coexistence issues that happen to arise on z/OS R4. Second, we won't support problems in your mixed sysplex if the problem is caused by the unsupported z/OS R4 system. (Yes, you can get extended support contracts, but I'm assuming you don't want to.) i infer from Don's response that it does make a difference, in that if zOS 1.4 is unsupported as of 31/03/2007 then it is not allowed to co-exist with other environments in the sysplex that are at 1.5 thru 1.7 (let alone 1.8) So far as I know, we won't change the code just to prevent it, but if it doesn't work for some reason you're on your own once R4 is unsupported. That's part of what "unsupported" means. But note that we might change the code in a way that prevents it for some other reason than merely preventing it. For example, suppose we find a problem on a higher release that requires a change to all the systems in the sysplex, and take an APAR that's fixed on all supported releases. If you can live without that fix, you're in luck. If you cannot, there won't be an R4 fix, which could be, um, "inconvenient." Of itself, we are not concerned about running on an unsupported level of OS for 6-9 months. We are concerned about having to either (1) conform, upgrade to z/architecture, and potentially move to a Group 80 license on a z890 from our current Amdahl Group 70 license, or (2) suffer expulsion from the sysplex by no longer being part of PSLC pricing. Our desire is to stay in the sysplex on an unsupported version of zOS, continue to benefit from PSLC, and then exit in Dec-2007. Sounds as though our preferred approach is something up with which others will not put. Sorry, I've no clue about the pricing implications. -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
[EMAIL PROTECTED] wrote: Since you can't order Z/OS 1.5 any longer, you must order Z/OS 1.7 even if you don't implement it immediately. Z/OS 1.8 will not be able to come up into the sysplex with Z/OS 1.4 - this means you can't share DASD, JES2, etc. z/OS R6 is the currently orderable release. -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
On Wed, 29 Jun 2005 00:00:00 GMT, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >... >For example, I don't think IBM has officially announced an end-of-service >date for z/OS V1R5 yet, although the "projected" date is listed as March >31, 2007. >... > >Why would IBM expire two at the same time? >That's the EOS for 1.4! > Why not? IBM has done it many times before. Especially when they've extended the dates for a particular release or re-version the OS. IIRC, OS/390 1.3 (last V1 version), OS/390 2.4 and OS/390 2.5 all had an EOS date of 03/31/2001. Mark -- Mark Zelden Sr. Software and Systems Architect mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
... For example, I don't think IBM has officially announced an end-of-service date for z/OS V1R5 yet, although the "projected" date is listed as March 31, 2007. ... Why would IBM expire two at the same time? That's the EOS for 1.4! -teD (The secret to success is sincerity. If you can fake that, you've got it made!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
>Of itself, we are not concerned about running on an unsupported level of OS >for 6-9 months. I'm curious...why not? What government functions is that Sysplex supporting? Personally, I would be "concerned." What I would then do about that concern is a separate issue. >We are concerned about having to either >(1) conform, upgrade to z/architecture, and potentially move to a Group 80 >license on a z890 from our current Amdahl Group 70 license, or >(2) suffer expulsion from the sysplex by no longer being part of PSLC >pricing. >Our desire is to stay in the sysplex on an unsupported version of zOS, >continue to benefit from PSLC, and then exit in Dec-2007. >Sounds as though our preferred approach is something up with which others >will not put. What's "Plan B"? For example, I don't think IBM has officially announced an end-of-service date for z/OS V1R5 yet, although the "projected" date is listed as March 31, 2007. The dates are listed at: http://www-1.ibm.com/servers/eserver/zseries/zos/support/zos_eos_dates.html That *might* be a viable "Plan B" if the goal is more hardware life and if (big if) IBM moves that date. But then you'd have to weigh the labour costs of a V1R5 upgrade. So a "Plan C" would be in order. One suggestion for a Plan C would be to get out the spreadsheets and run some "what ifs?" On the software front, look at the list of products you're running now and determine which you don't need, which you can switch to lower-cost options (and at what effort, costed), etc. If you're not combining mainframe and non-mainframe software into one contract, check into that to see if it does anything. If there's any z/OS.e potential workload -- DB2 workload can fit into that category -- see if a z/OS.e LPAR helps. Do you get anything from workload-based licensing options (via SCRT)? The "technology dividend" might help. (More MIPS, lower MSUs on each new model.) Are you going to save some money moving workload to Linux on zSeries, where appropriate? (If you can eliminate 100 Windows file servers and associated labour, for example, that can help the financials.) Do you have any Java workload yet (or which is available for consolidation)? (Look at a zAAP.) Do you have any crypto processing now or in your future? (A z890 offloads that work better than prior hardware. That's hitting us hard in the U.S. because of privacy concerns.) Everything should be on the table. Hope that helps. - - - - - Timothy F. Sipples Consulting Software Architect, Enterprise Transformation IBM Americas zSeries Software Phone: (312) 245-4003 E-Mail: [EMAIL PROTECTED] (PGP key available.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
Had initially mentioned "only reference i've found so far is that z/OS 1.4 can coexist with z/OS 1.5, thru 1.7, but nothing about parallel sysplex". In hindsight that was obviously poorly proof-read. i had been unable to find anything stating that zOS 1.4 can co-exist in a parallel sysplex with 1.5-1.7 when zOS1.4 is no longer supported. My question should simply have been "does it make any difference to this level of co-existence if z/OS 1.4 is out of support?" i infer from Don's response that it does make a difference, in that if zOS 1.4 is unsupported as of 31/03/2007 then it is not allowed to co-exist with other environments in the sysplex that are at 1.5 thru 1.7 (let alone 1.8) Of itself, we are not concerned about running on an unsupported level of OS for 6-9 months. We are concerned about having to either (1) conform, upgrade to z/architecture, and potentially move to a Group 80 license on a z890 from our current Amdahl Group 70 license, or (2) suffer expulsion from the sysplex by no longer being part of PSLC pricing. Our desire is to stay in the sysplex on an unsupported version of zOS, continue to benefit from PSLC, and then exit in Dec-2007. Sounds as though our preferred approach is something up with which others will not put. thx for your interesting and informative replies. regards, peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
On Jun 28, 2005, at 3:00 AM, Vernooy, C.P. - SPLXM wrote: "Ted MacNEIL" <[EMAIL PROTECTED]> wrote in message news:<1100276174-1119943968-cardhu_blackberry.rim.net-8203- @engine143>... .. Only reference i've found so far is that z/OS 1.4 can coexist with z/OS 1.5, thru 1.7, but nothing about parallel sysplex. .. Interesting, because that is exactly what SYSPLEX co-existance means. Co-existence limitations do not need to be restricted to sysplex. Non-sysplex systems do also communicate and interact (JES, GRS etc. etc.) and the limitations also apply to that broader level, which include sysplex systems. Kees. Kees, Do you mean like NJE? Its been a while but AFAIK NJE never broke and we were able to talk to all levels of JES/POWER (and a few other). Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
The "supported" part of "all supported releases" is also important. As an example, when z/OS 1.6 came out, it co-existed with z/OS 1.3. But z/OS 1.3 went off support March 2005, so z/OS 1.3 can no longer co-exist with z/OS 1.6. Don Imbriale >-Original Message- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf >Of John Eells >Sent: Tuesday, June 28, 2005 12:49 PM >To: IBM-MAIN@BAMA.UA.EDU >Subject: Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007 > >Jim Ladouceur wrote: > >> If IBM really has changed the coexistence policy to "all supported >> releases" then 1.4 will coexist with 1.8 since they've extended the EOS >> date for 1.4 to 3/7 and 1.8 will be out 9/6. Can someone please point me >> to the doc with the policy change? >> > >As we announced, "Starting with z/OS V1.6, the >Coexistence-Migration-Fallback policy aligns with the Service >policy." > >z/OS R4, however, will coexist with z/OS R7, not with z/OS R8. >Each z/OS general availability announcement letter has a summary >of the supported coexistence combinations in it. Here is the >coexistence table from the z/OS R6 GA announcement (which I hope >will stay readable after posting): > >Release Coexistence-supported with release in column 1 > >z/OS V1.3 or OS/390(R) V2.9 (1), (z/OS V1.1 & OS/390 V2.10) (2,3), >z/OS.e V1.3 z/OS V1.2 (4), z/OS V1.3, z/OS.e V1.3 > >z/OS V1.4 or (z/OS V1.1 & OS/390 V2.10) (2,3), z/OS V1.2 (4), >z/OS.e V1.4 z/OS V1.3, z/OS V1.4, z/OS.e V1.3, z/OS.e V1.4 > >z/OS V1.5 or z/OS.e V1.3, z/OS.e V1.4, z/OS.e V1.5, >z/OS.e V1.5 z/OS V1.2 (4), z/OS V1.3, z/OS V1.4, z/OS V1.5 > >z/OS V1.6 z/OS.e V1.3, z/OS.e V1.4, z/OS.e V1.5, >or z/OS.e V1.6, >z/OS.e V1.6 z/OS V1.3, z/OS V1.4, z/OS V1.5, z/OS V1.6 > >z/OS V1.7 (5) z/OS.e V1.4, z/OS.e V1.5, z/OS.e V1.6, z/OS.e >or V1.7, >z/OS.e V1.7 z/OS V1.4, z/OS V1.5, z/OS V1.6, z/OS V1.7 > >z/OS V1.8 (5) z/OS.e V1.5, z/OS.e V1.6, z/OS.e V1.7, z/OS.e >or V1.8, >z/OS.e V1.8 z/OS V1.5, z/OS V1.6, z/OS V1.7, z/OS V1.8 > >z/OS V1.9 (5) z/OS.e V1.7, z/OS.e V1.8, z/OS.e V1.9 >or >z/OS.e V1.9 z/OS V1.7, z/OS V1.8, z/OS V1.9 > >The quote and table are from IBM z/OS V1.6: Integrating new >applications and Preview: z/OS V1.7, IBM United States Software >Announcement 204-180, dated August 10, 2004. > >-- >John Eells >z/OS Technical Marketing >IBM Poughkeepsie >[EMAIL PROTECTED] *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
Jim Ladouceur wrote: If IBM really has changed the coexistence policy to "all supported releases" then 1.4 will coexist with 1.8 since they've extended the EOS date for 1.4 to 3/7 and 1.8 will be out 9/6. Can someone please point me to the doc with the policy change? As we announced, "Starting with z/OS V1.6, the Coexistence-Migration-Fallback policy aligns with the Service policy." z/OS R4, however, will coexist with z/OS R7, not with z/OS R8. Each z/OS general availability announcement letter has a summary of the supported coexistence combinations in it. Here is the coexistence table from the z/OS R6 GA announcement (which I hope will stay readable after posting): Release Coexistence-supported with release in column 1 z/OS V1.3 or OS/390(R) V2.9 (1), (z/OS V1.1 & OS/390 V2.10) (2,3), z/OS.e V1.3 z/OS V1.2 (4), z/OS V1.3, z/OS.e V1.3 z/OS V1.4 or (z/OS V1.1 & OS/390 V2.10) (2,3), z/OS V1.2 (4), z/OS.e V1.4 z/OS V1.3, z/OS V1.4, z/OS.e V1.3, z/OS.e V1.4 z/OS V1.5 or z/OS.e V1.3, z/OS.e V1.4, z/OS.e V1.5, z/OS.e V1.5 z/OS V1.2 (4), z/OS V1.3, z/OS V1.4, z/OS V1.5 z/OS V1.6 z/OS.e V1.3, z/OS.e V1.4, z/OS.e V1.5, or z/OS.e V1.6, z/OS.e V1.6 z/OS V1.3, z/OS V1.4, z/OS V1.5, z/OS V1.6 z/OS V1.7 (5) z/OS.e V1.4, z/OS.e V1.5, z/OS.e V1.6, z/OS.e or V1.7, z/OS.e V1.7 z/OS V1.4, z/OS V1.5, z/OS V1.6, z/OS V1.7 z/OS V1.8 (5) z/OS.e V1.5, z/OS.e V1.6, z/OS.e V1.7, z/OS.e or V1.8, z/OS.e V1.8 z/OS V1.5, z/OS V1.6, z/OS V1.7, z/OS V1.8 z/OS V1.9 (5) z/OS.e V1.7, z/OS.e V1.8, z/OS.e V1.9 or z/OS.e V1.9 z/OS V1.7, z/OS V1.8, z/OS V1.9 The quote and table are from IBM z/OS V1.6: Integrating new applications and Preview: z/OS V1.7, IBM United States Software Announcement 204-180, dated August 10, 2004. -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
... If IBM really has changed the coexistence policy to "all supported releases" then 1.4 will coexist with 1.8 since they've extended the EOS date for 1.4 to 3/7 and 1.8 will be out 9/6. ... I never saw that doc either. And, I follow this quite closely since I am working for a back-levelled shop and am trying to bring us up to 1.6, DB2 V8, IMS V9, CICS V3, etc. In a parallel SYSPLEX. -teD (The secret to success is sincerity. If you can fake that, you've got it made!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
If IBM really has changed the coexistence policy to "all supported
releases" then 1.4 will coexist with 1.8 since they've extended the EOS
date for 1.4 to 3/7 and 1.8 will be out 9/6. Can someone please point me
to the doc with the policy change?
Jim
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ted MacNEIL
Sent: Monday, June 27, 2005 8:00 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
...
It used to be n-3. When IBM changed z/OS to an annual release schedule,
they also changed the coexistence policy to be "all supported releases".
...
Semantics.
1.4 through 1.7 is N-3 to N.
Do the math. (8-{]}
-teD
(The secret to success is sincerity.
If you can fake that,
you've got it made!)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
...
It used to be n-3. When IBM changed z/OS to an annual release schedule,
they also changed the coexistence policy to be "all supported releases".
...
Semantics.
1.4 through 1.7 is N-3 to N.
Do the math. (8-{]}
-teD
(The secret to success is sincerity.
If you can fake that,
you've got it made!)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
... Non-sysplex systems do also communicate and interact (JES, GRS etc. etc.) and the limitations also apply to that broader level, which include sysplex systems ... JES/NJE(P) is not restricted to n-3. It never has been. GRS does not communicate outside of an instance of MVS (SYSPLEX is considered an instance). Co-existance (in my mind) has always meant within a SYSPLEX. The original quote was a SYSPLEX one. If I wanted to, I could communicate with an XA system through NJE from a z/OS system. I would just have to ensure I don't use constructs that are not supported by XA. -teD (The secret to success is sincerity. If you can fake that, you've got it made!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
Ted MacNEIL wrote: It's N through N-3. It used to be n-3. When IBM changed z/OS to an annual release schedule, they also changed the coexistence policy to be "all supported releases". That simplification of the coexistence policy was (IMHO) the only really good thing that came from the release schedule change. -- .-. | Edward E. Jaffe|| | Mgr, Research & Development| [EMAIL PROTECTED]| | Phoenix Software International | Tel: (310) 338-0400 x318 | | 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801| | Los Angeles, CA 90045 | http://www.phoenixsoftware.com | '-' -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
Vernooy, C.P. - SPLXM wrote: "Ted MacNEIL" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... .. Only reference i've found so far is that z/OS 1.4 can coexist with z/OS 1.5, thru 1.7, but nothing about parallel sysplex. .. Interesting, because that is exactly what SYSPLEX co-existance means. Co-existence limitations do not need to be restricted to sysplex. Non-sysplex systems do also communicate and interact (JES, GRS etc. etc.) and the limitations also apply to that broader level, which include sysplex systems. Non-sysplex communication is usually less restricted. Obvious example would be TCP/IP connection, ftp transfer etc. but also NJE (JES) communication is much less restrictive - it support quite old releases (AFAIK MVS, pre-OS/390). What is usually restricted to N-3 it is all kinds of datasharing, using coupling facility (PSysplex) or just sharing of control datasets, like RACfdb, RMM, HSM, SMS CDSes, etc. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
"Ted MacNEIL" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > .. > Only reference i've found so far is that z/OS 1.4 can coexist > with z/OS 1.5, thru > 1.7, but nothing about parallel sysplex. > .. > > Interesting, because that is exactly what SYSPLEX co-existance means. Co-existence limitations do not need to be restricted to sysplex. Non-sysplex systems do also communicate and interact (JES, GRS etc. etc.) and the limitations also apply to that broader level, which include sysplex systems. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Running z/OS 1.4 on a G5/G6 after 31 March 2007
... Only reference i've found so far is that z/OS 1.4 can coexist with z/OS 1.5, thru 1.7, but nothing about parallel sysplex. ... Interesting, because that is exactly what SYSPLEX co-existance means. 1.3 cannot run in the same SYSPLEX as 1.7 & 1.4 cannot run with 1.8. It's N through N-3. What 'unsupported' means is if something breaks, IBM will not fix it. They may do it on a 'time & materials' basis; there's so guarantee that they will (or will still have the skills/knowledge to) do so. -teD (The secret to success is sincerity. If you can fake that, you've got it made!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
