That APAR is ancient. The current numbers APAR numbers are OA6xxxx. Seems like OA25662 would be circa z/OS 1.4 vintage.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Friday, January 6, 2017 8:50 AM To: [email protected] Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error You did not indicate if you have MVS Solutions Thruput Manager. If you do, I found this on their website PR08075 TR62009 $ADD LOADMOD(DTMJ2MV6) command fails with a $BR1 ABEND after IBM APAR OA25562. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Pommier, Rex > Sent: Friday, January 06, 2017 6:51 AM > To: [email protected] > Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 > catastrophic error > > Hi Tony, > > There wasn't one. The manual says the reason code is optional and for > $BR1, it got optioned out. > > *21.10.54 *$HASP493 JES2 ALL-MEMBER WARM START IS IN PROGRESS - > * z11 MODE > *21.10.54 *$HASP095 JES2 CATASTROPHIC ERROR. CODE = $BR1 > $HASP088 HASPIRDA 165B7690 + 000F8C OA49165 BERTMAP > $HASP088 HASPIRA 165B5000 + 0004FC OA47827 IRDA > $HASP088 PCE = INIT (165B6008) > $HASP088 R0 = 00000000 3A54502C 0000342C 00000000 > $HASP088 R4 = 16CA7000 000073B7 00007718 48B4CC30 > $HASP088 R8 = 3A545018 009FE980 16642BD0 00007000 > $HASP088 R12 = 1647B098 165B6008 9647B144 00000008 > > This was followed by the 02D abend. > > Thanks, > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Tony Harminc > Sent: Thursday, January 05, 2017 7:02 PM > To: [email protected] > Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 > catastrophic error > > On 5 January 2017 at 12:38, Pommier, Rex <[email protected]> wrote: > > 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.". > > What's the reason code with the $BR1? > > Tony H. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN
