Hi Elardus, <your question> What do you see if you issue $D ACTIVATE during that disastrous IPL?
I couldn't do a $D ACTIVATE because JES was down. Once it came up cold, it shows that I'm in Z22 mode. <your comment> This is documented and WAD, but very very disruptive! Yup, and not something I want to do. There is documented a way around this, where you can bring JES up cold in Z11 mode, that is to put in the OPTSDEF JES2PARM COLD_START_MODE=Z11. That allows compatibility to older JES releases but doesn't fix the problem of needing a cold start. The only migration action required going from 1.13 to 2.2 is to be a1 z11 mode which we are. Output from a $D ACTIVATE on my 1.13 system shows: $HASP895 $DACTIVATE 751 $HASP895 JES2 CHECKPOINT MODE IS CURRENTLY Z11 $HASP895 THE CURRENT CHECKPOINT: $HASP895 -- CONTAINS 18100 BERTS AND BERT UTILIZATION IS 2 $HASP895 PERCENT. $HASP895 -- CONTAINS 1283 4K RECORDS. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Thursday, January 05, 2017 1:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error Pommier, Rex wrote: >Upgrading from z/OS 1.13 to 2.2. Attempted to IPL it tonight in our >sandbox using a clone of one of our production LPARs. Tried to bring >JES2 up warm and got a $HASP095 catastrophic error code=$BR1. We are >running z11 mode on 1.13 and the $HASP493 warm start message verified >z11 mode. I got a system dump of JES2 when it failed and will attempt >to figure out something in it tomorrow, but was wondering if anybody has seen anything like this. What do you see if you issue $D ACTIVATE during that disastrous IPL? > I restarted JES2 bringing it up COLD and it came right up, in z22 mode. This is documented and WAD, but very very disruptive! >Does anybody know offhand if JES2 needs to be brought up cold when migrating >from 1.13 to 2.2 or what might be the problem. I have RTFM, but could not find any such requirements, unless I missed something. >I didn't quiesce JES2 on the current 1.13 system before creating the clone for >the sandbox, but we've not had issues with doing this before for DR testing >(not moving to a new release). >Any thoughts/ideas would be most welcome. Check Health Checker - JES2_UPGRADE_CKPT_LEVEL_JES2 Also check OA48823 (about $IV8, not about your $BR1) and similar APARs. There are a few of them for JES2. I believe I have seen discussions about this (upgrade and toleration of JES2) previously. You should check out the migration actions needed all the way from z/OS v1.13 to v2.2 for JES2. PS: we are not at 2.2 at all, because we are still dragging a 1.13 LPAR... don't ask. ;-) Good luck! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
