That's what I had to do too. Fortunately, it was a small system, and a cold start was no big deal. I could have used the CKPT reconfig dialog. But it was easier for me to allocate new CKPT datasets, IPL, and COLD start with the new CKPT datasets.
Sent with Proton Mail secure email. ------- Original Message ------- On Friday, August 19th, 2022 at 3:17 PM, Carmen Vitullo <petevi...@gmail.com> wrote: > for me moving from 2.3 to 2.4, (I waiting some time to upgrade to Z22 > mode) , I have to enlarge my CKPT datasets then $ACTIVATE,LEVEL=Z22 > > you can $DACTIVATE to check if your current CKPT's meet the requirements. > > I performed the CKPT change using the checkpoint dialog to move to > newckpt1 and 2 (larger than ckpt1 and 2) , deleted old ckpt1 and 2 and > reallocated 1 and 2 larger and then used the dialog to get me back to > ckpt1 and 2 > > I cannot recall the last time a cold start being required, I've done > cold starts after offloading and reloading spool migrating to new DASD > perhaps before the migrate facility was available in JES2 > > Carmen > > On 8/19/2022 1:59 PM, Marna WALLE wrote: > > > Hello, > > A couple of questions I had in email, which I hope will help here: > > > > I was asked about if a COLD START was required in z/OS V2.5: There is NO > > COLD START required for z/OS V2.5. I haven’t seen a required COLD start, in > > like forever, and I can’t recall that we have needed it during my whole > > career, at least while working on z/OS migrations. I'm sure folks here go > > back further than I do, and probably will take up a thread on this :). > > > > What is really required on z/OS V2.5: Carefully read the z/OS V2.5 Upgrade > > Workflow (which was linked in a prior append), it says that z22 is > > required, but it should be done while still on your V2.3/V2.4 system. On > > those systems, you can fallback to z11 if you must while on z/OS V2.3/V2.4, > > but you have to be at z22 on those systems before you introduce V2.5. > > > > There was a defect in this area, but it didn't affect the z22 upgrade > > requirement. The APAR mentioned in a prior post was the one I was thinking > > of. I have not been aware of this z22 requirement being debated or possibly > > not happening in z/OS V2.5. I knew it was happening for quite a while, and > > it was in the z/OS V2.5 Upgrade Workflow even in the first version of it. > > And nicely, we've had a Health Check to do that encouragement for a long > > time now. > > > > I do know that z11 hasn’t been scrubbed from the z/OS V2.5 books – I’m not > > sure exactly why, so it may not be worth reading too much into it. Maybe it > > was an oversight or maybe it was intentional so that folks looking at V2.5 > > manuals while on V2.3/V2.4 still get the z11 updated information, since we > > don't update the V2.3/V2.4 books anymore. That’s something to do a Feedback > > on so it can get to the right manual writer for attention. They are pretty > > good about following up with Feedback from IBM Documentation, so it would > > be worth the comment, please. > > > > So let’s recap: with z/OS V2.5, z22 is absolutely required with no COLD > > start. Use the health check to get the a-ok before going to V2.5. > > > > Hope to see many of you at SHARE next week! > > -Marna WALLE > > z/OS Installation and Upgrade > > IBM Poughkeepsie > > > > ---------------------------------------------------------------------- > > 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
