You didn't quote the context, so I don't know what the OP's environment was, but there have, historically, been DASD fallback issues both within and between sysplexes.
Has there been a JES level set in z/OS V2 that changed the checkpoint or SPOOL structure automatically rather than upon explicit request, e.g., $ACTIVATE, $T, $T CKPTDEF, $T SPOOLDEF? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Brian Westerman <brian_wester...@syzygyinc.com> Sent: Friday, September 6, 2019 6:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 2.1 to 2.4 [EXTERNAL] Not between 2.1 and 2.4. The incompatibilities are between JES level sets. Those kinds of problems (when things are actively shared through the sysplex) are where being a sysplex can make a difference, the solution in those cases is that you end up with two sysplexes for the duration of your conversion. The basic process still remains about the same for a long jump with a sysplex and one without, it's just a bit more complex because as you are populating the new sysplex, you are depopulating the old one. In this case though, the OP is in LPAR mode with (maybe or maybe not) shared resources (DASD, tapes, etc,) but not a sysplex. The issue came up when someone, who should have known better, stepped in and suggested that if they did not install an intermediate release (i.e. 2.2 or 2.3) that they could be asking for trouble. The suggestion was ludicrous. 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
