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 [email protected] with the message: INFO IBM-MAIN
