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.
> >
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
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.
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
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
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 sys
ecember 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
@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
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
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
gt; 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.1
@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 resou
S 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 T
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
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
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
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
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 -
18 matches
Mail list logo
