Re: ZOS 1.13 2.2 2.3 in the same sysplex
Have you tried to run it on z/OS 2.1 / 2.2 / 2.3? That is a supported combination. On Wed, Dec 18, 2019 at 3:09 PM Gibney, Dave wrote: > > Their app not supporting z/OS 2.2 in not necessarily equal to won't run on > z/OS 2.2 > > > -Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of R Hey > > Sent: Wednesday, December 18, 2019 12:51 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex > > > > Yes, HSM is used, but not installed/used during my tests. > > I didn't do much with zos 2.3, didn't create new DS in CAT's, etc. > > Just log'd on to TSO/SDSF to look at syslog. > > Client is forced to use 1.13 due to their APP not supporting zos 22. They > > are > > planning to upgrade it, but could take a while. > > Decision has been made to move all zos 1.13 LPARs to a separate plex. > > > > cheers > > > > -- > > 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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Their app not supporting z/OS 2.2 in not necessarily equal to won't run on z/OS 2.2 > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of R Hey > Sent: Wednesday, December 18, 2019 12:51 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex > > Yes, HSM is used, but not installed/used during my tests. > I didn't do much with zos 2.3, didn't create new DS in CAT's, etc. > Just log'd on to TSO/SDSF to look at syslog. > Client is forced to use 1.13 due to their APP not supporting zos 22. They are > planning to upgrade it, but could take a while. > Decision has been made to move all zos 1.13 LPARs to a separate plex. > > cheers > > -- > 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: ZOS 1.13 2.2 2.3 in the same sysplex
Yes, HSM is used, but not installed/used during my tests. I didn't do much with zos 2.3, didn't create new DS in CAT's, etc. Just log'd on to TSO/SDSF to look at syslog. Client is forced to use 1.13 due to their APP not supporting zos 22. They are planning to upgrade it, but could take a while. Decision has been made to move all zos 1.13 LPARs to a separate plex. cheers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Right, they don't say it won't work, but if it doesn’t, and something breaks, they aren't going to do anything to help you put the pieces back together. Wayne Driscoll Rocket Software Note - All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Tuesday, December 17, 2019 7:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex EXTERNAL EMAIL Until some shared resource breaks. Not saying it'll happen, but it might. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.comdata=02%7C01%7C%7Cf2eba82a1290450ea67f08d782f2018e%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C637121848241109558sdata=riBz9F0SVKo%2BUu8M4cc7hwOWImz51OdErToR8cVTz9o%3Dreserved=0 ‐‐‐ Original Message ‐‐‐ On Tuesday, December 17, 2019 3:14 AM, Brian Westerman wrote: > I don't think there is any check for that. I believe that z/OS isn't that > smart when it comes to figuring that stuff out, and actually I can't really > think of a reason why it wouldn't work. Remember, just because IBM doesn't > say they "support" something, doesn't necessarily mean it doesn't work. > > 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 Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Out of curiosity: what is the reason? Why to connect 3 different system levels in one sysplex? It is unsupported - we know that. It is somehow hard. It is somehow risky - we are aware about that also . Why not upgrade 1.13 system to current one and then connect it to the sysplex? Yes, upgrade require some work to do, but it is IMHO much more straightforward than connecting unsupported system to unsupported and delicate, and complex configuration. -- Radoslaw Skorupka Lodz, Poland == 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.2019 r. wynosi 169.347.928 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.347.928 as at 1 January 2019. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
the error description indicates that 1.13 is too downlevel for the aggregate version: Description: New version aggregates cannot be processed on this system. Action: If this is a primary mount, re-issue the mount on a system that supports higher version aggregates. If this is a catchup mount, no action is needed. z/OS UNIX will function ship operations to the z/OS UNIX owner. -- Artificial Intelligence is no match for Natural Stupidity - Unknown On Wed, Dec 18, 2019 at 7:35 AM Allan Staller wrote: > TSO BPXMTEXT EF096A32 will tell you exactly why the file system was not > mounted. > I haven't looked, but IIRC error code 79 indicates some sort of "file not > found" (???) error. > > HTH, > > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of R Hey > Sent: Tuesday, December 17, 2019 5:59 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex > > I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, > etc, with only 1 LPAR in it. > IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with > zos 23 sysres/Mcat: OK IPL’d the same LPAR with zos 22 sysres/Mcat: OK > > IPL’d the same LPAR with zos 1.13 sysres/Mcat: NOT OK ! > Failed to mount plex root ZFS, ETC, VAR, … BPXF002I code 79 reason > EF096A32 > > Created new ZFS, IPL 1.13 : OK > > cheers > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ::DISCLAIMER:: > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain > viruses in transmission. The e mail and its contents (with or without > referred errors) shall therefore not attach any liability on the originator > or HCL or its affiliates. Views or opinions, if any, presented in this > email are solely those of the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, distribution and / or > publication of this message without the prior written consent of authorized > representative of HCL is strictly prohibited. If you have received this > email in error please delete it and notify the sender immediately. Before > opening any email and/or attachments, please check them for viruses and > other defects. > > > -- > 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: ZOS 1.13 2.2 2.3 in the same sysplex
TSO BPXMTEXT EF096A32 will tell you exactly why the file system was not mounted. I haven't looked, but IIRC error code 79 indicates some sort of "file not found" (???) error. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of R Hey Sent: Tuesday, December 17, 2019 5:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc, with only 1 LPAR in it. IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 23 sysres/Mcat: OK IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 1.13 sysres/Mcat: NOT OK ! Failed to mount plex root ZFS, ETC, VAR, … BPXF002I code 79 reason EF096A32 Created new ZFS, IPL 1.13 : OK cheers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
So, you just found an incompatibility in ZFS, and found a way out, luckily. It’s the other resources that are shared that are going to cause you problems. Are you a DFHSM user? How current are you on maintenance in your lpars? I will tell you for fact that if you are an HSM user, there was maintenance in V2.2/V2.3 about a year or so ago that changed the structure of the MCDS. Datasets would not recall on systems that do NOT have that maintenance, or the toleration for it.I suspect that those PTF's never got pushed down to V1.13. The reason I know this, is that there was a period of time where IBM got the hold data on the toleration PTF's wrong, and the minute the maintenance hit the first systems in the plex we had the problem. *These* are the kinds of problems you will run into. If it were me, and I think Brian Westerman probably would say the same, is to put whatever application is requiring you to keep 1.13 into its own stand-alone environment. Of course that adds to the complexity of the situation if you are sharing DASD. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of R Hey Sent: Tuesday, December 17, 2019 6:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc, with only 1 LPAR in it. IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 23 sysres/Mcat: OK IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 1.13 sysres/Mcat: NOT OK ! Failed to mount plex root ZFS, ETC, VAR, … BPXF002I code 79 reason EF096A32 Created new ZFS, IPL 1.13 : OK cheers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
That wait state only applies due to some APAR inconsistencies which don't apply to this OP. They already have 1.13 through 2.2 running together so we can safely assume that they complied with the new function APAR issue. I don't see how they can get the wait 082 with just 1.13 and 2.3 (with 2.2 mixed in there somewhere). It's not that 2.3 didn't have any new functions, just none that would make this wait state apply. I would give it a shot, you really don't have anything to lose and so long as you do the normal system compatibility stuff (CF's etc.) you should be okay to go. Remember that the levels supported by 2.3 will be higher than 1.13, so you have to run at the levels that match between those two, but you obviously know about this as you are already running a mixed release sysplex. Let me know how it goes, Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
I had build a new plex on zos 1.13, new CF, XCF CDS, SMS, RMM, RACF, Mcat, etc, with only 1 LPAR in it. IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 23 sysres/Mcat: OK IPL’d the same LPAR with zos 22 sysres/Mcat: OK IPL’d the same LPAR with zos 1.13 sysres/Mcat: NOT OK ! Failed to mount plex root ZFS, ETC, VAR, … BPXF002I code 79 reason EF096A32 Created new ZFS, IPL 1.13 : OK cheers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
If you try and add an LPAR to a sysplex without having applied the relevant coexistence maintenance, you get a 082 wait state at IPL. See description below. If you try to add a system that is not even in the compatibility matrix, I would guess the same... 082 Explanation The system entering the sysplex is removed to prevent console sysplex data corruption. The system being partitioned either requires maintenance to be installed to be able to coexist with the other systems in the sysplex, or a system already active in the sysplex requires maintenance to be installed to be able to coexist with the failing system. For example, the failing system does not have a necessary consoles compatibility APAR installed. System action The system entering the sysplex is partitioned from the sysplex and wait state X'082' is loaded on that system to prevent global console sysplex data corruption. Message IEA002I is issued to indicate which system requires maintenance to be applied and the appropriate APAR to apply. On Tue, 17 Dec 2019, 17:16 Charles Mills, wrote: > I am not at all an expert on Sysplex compatibility. I bring to the table > only the knowledge of the IBM policy and years of experience with "how > things work." > > I think the answer is very simple: it might work and it might not. Or, > more correctly, it might IPL, and if it does, then everything YOU care > about might work, or on the other hand something might not work. > > You have three requirements: > > - z/OS 1.13 > - z/OS 2.3 > - Implicitly, mainframe-level quality of service > > One of those has to go. Pick one. I would pick 2.3 as the one to go -- you > may *think* you need it, but I am going to guess you don't need it, you > want it. And if management insists that 2.3 is not the one to go, then > mainframe quality of service is going to be the one to go, because > SOMETHING has to go. When JES2 or RESERVE or whatever breaks, what the heck > are you going to do? > > I'm just re-phrasing what @Mark says below. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mark Jacobs > Sent: Tuesday, December 17, 2019 5:06 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex > > Until some shared resource breaks. Not saying it'll happen, but it might. > > -- > 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: ZOS 1.13 2.2 2.3 in the same sysplex
I am not at all an expert on Sysplex compatibility. I bring to the table only the knowledge of the IBM policy and years of experience with "how things work." I think the answer is very simple: it might work and it might not. Or, more correctly, it might IPL, and if it does, then everything YOU care about might work, or on the other hand something might not work. You have three requirements: - z/OS 1.13 - z/OS 2.3 - Implicitly, mainframe-level quality of service One of those has to go. Pick one. I would pick 2.3 as the one to go -- you may *think* you need it, but I am going to guess you don't need it, you want it. And if management insists that 2.3 is not the one to go, then mainframe quality of service is going to be the one to go, because SOMETHING has to go. When JES2 or RESERVE or whatever breaks, what the heck are you going to do? I'm just re-phrasing what @Mark says below. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Jacobs Sent: Tuesday, December 17, 2019 5:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex Until some shared resource breaks. Not saying it'll happen, but it might. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Add to this the H/W and CFCC levels of the different systems. While the 'newest' release of z/OS in the Sysplex will support the highest level of the CFCC level in the Sysplex, does 1.13 support it? IBM normally tests up to n-2 levels/generations of OS and H/W. Combination of older levels MAY work. If it doesn't, then you are on your own. Regards Parwez Hamid From: IBM Mainframe Discussion List on behalf of Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> Sent: 17 December 2019 13:06 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ZOS 1.13 2.2 2.3 in the same sysplex Until some shared resource breaks. Not saying it'll happen, but it might. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, December 17, 2019 3:14 AM, Brian Westerman wrote: > I don't think there is any check for that. I believe that z/OS isn't that > smart when it comes to figuring that stuff out, and actually I can't really > think of a reason why it wouldn't work. Remember, just because IBM doesn't > say they "support" something, doesn't necessarily mean it doesn't work. > > 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Until some shared resource breaks. Not saying it'll happen, but it might. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Tuesday, December 17, 2019 3:14 AM, Brian Westerman wrote: > I don't think there is any check for that. I believe that z/OS isn't that > smart when it comes to figuring that stuff out, and actually I can't really > think of a reason why it wouldn't work. Remember, just because IBM doesn't > say they "support" something, doesn't necessarily mean it doesn't work. > > 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: ZOS 1.13 2.2 2.3 in the same sysplex
I don't think there is any check for that. I believe that z/OS isn't that smart when it comes to figuring that stuff out, and actually I can't really think of a reason why it wouldn't work. Remember, just because IBM doesn't say they "support" something, doesn't necessarily mean it doesn't work. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Not only is z/OS 1.13 not supported in the same sysplex with z/OS 2.3, I am pretty sure it won’t work. Every release has sysplex changes which often (always?) require PTFs to the prior 2 releases to participate in the same sysplex. Even if no PTFs are required, I suspect z/OS checks to see the release levels in the sysplex members and would not allow this configuration. Regards, Jim -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
Thanks Mark, Yes, I know. My client is forced to use zos 1.13 for a while, they use it with with zos 2.2 in the same plex, which needs to be moved to zos 2.3. Cheers -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ZOS 1.13 2.2 2.3 in the same sysplex
I assume you know that it's not a supported configuration. z/OS 1.13 is also out of support and there's no compatibility maintenance with z/OS 2.3 available (AFAIK). Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Sunday, December 15, 2019 6:59 PM, R Hey <00bb27d4e6cb-dmarc-requ...@listserv.ua.edu> wrote: > Hi, > Has anybody used these 3 versions of zos in 1 sysplex (CF, SMS, HSM, Ucats, > etc ...) ? > Cheers, > Reza > > > > 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
ZOS 1.13 2.2 2.3 in the same sysplex
Hi, Has anybody used these 3 versions of zos in 1 sysplex (CF, SMS, HSM, Ucats, etc ...) ? Cheers, Reza -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
