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, <charl...@mcn.org> 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
