Hi Allan, Thanks for your response. Here's where I am in regards to them.
1) I need to double check compatibility maintenance. The only initialization parameters listed in the migration guide as needing changes are optional (removing BROADCAST from OUTDEF and JCLERR from JOBDEF) and I did that. The incompatibilities associated with z2 versus z11 versus z22 mode all point to the fact that I'm running z11 mode. These are the SPOOLDEF LARGEDS=ALLOWED. If I do a $D CKPTSPACE,BERTUSE shows I am using about 500 BERTs and have over 17,000 free. 2) $BR1 in M&C gives me "lots" of good information <sarc>. The doc says "JES2 initialization processing encountered an error examining the BERT maps" and the resolution is " Use the indicative dump and the SVC dump (if any) to diagnose the error.". 3) That'll be happening probably today. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Thursday, January 05, 2017 7:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error I believe z/OS 2.2 fits within the N-2 compat/fallback range so: 1) verify all compat/fallback maint is installed on the 1.13 system. Check for incompatable initialization parameters in the 2.2 JESPARMS. 2) look up $BR1 in JES messages/codes to see if any insight can be gained there 3)Contact IBM for assistance... -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex Sent: Wednesday, January 4, 2017 9:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error Hello list, 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. I restarted JES2 bringing it up COLD and it came right up, in z22 mode. 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 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. TIA, Rex 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 ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- 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
