Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Elardus Engelbrecht]

Pommier, Rex wrote:

>No I didn't need to use TOLerate.  I'm assuming you meant TOL(ENQF).

Ok. thanks, I was not sure what type of COPY you used, but thanks.


> If I would need to use TOL(IOER) I have bigger problems.  :-)  

Indeed. To tolerate IO errors is asking for trouble... I will not tolerate that 
specific usage of TOL(IOER). (sorry, pun intended.)

Thanks Rex, you have cured my curiousity. I hope you can get your other 
production JES2 up and running on 2.2 (nice and WARM instead of ugly and COLD). 
 ;-D

Groete / Greetings
Elardus Engelbrech

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Elardus,

No I didn't need to use TOLerate.  I'm assuming you meant TOL(ENQF).  If I 
would need to use TOL(IOER) I have bigger problems.  :-)  And I just looked it 
up, it appears that TOL(ENQF) isn't even a viable option on a COPY FULL command.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, January 10, 2017 12:09 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:

>I had the same thoughts over the weekend and messing with it this morning, I 
>discovered the problem.  I had neglected to use the ALLD and ALLE parameters 
>in my DFDSS job to copy the spool and checkpoint volumes.  So DFDSS dutifully 
>copied the pointers to "empty" datasets.  

Excellent! ALLEXCP and ALLDATA! Thats them. You need them to clone [all] your 
JES2 data.

Perhaps a documentation update should be placed in JES2 migration guide and 
Program Directory about this?

Oh, BTW, did you also need to use TOLERATE? Just curious.


>Guessing I'm not going to forget this one!

Neither me, I remember that I also burned my fingers badly during cloning of a 
system for testing out Y2K... 

;-)

Groete / Greetings
Elardus Engelbrecht

How many electrical engineers does it take to change a light bulb? We don't 
know yet, they're still waiting for a part.
How many programmers does it take to change a light bulb? None - it is a 
hardware problem.

--
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Elardus Engelbrecht]

Pommier, Rex wrote:

>I had the same thoughts over the weekend and messing with it this morning, I 
>discovered the problem.  I had neglected to use the ALLD and ALLE parameters 
>in my DFDSS job to copy the spool and checkpoint volumes.  So DFDSS dutifully 
>copied the pointers to "empty" datasets.  

Excellent! ALLEXCP and ALLDATA! Thats them. You need them to clone [all] your 
JES2 data.

Perhaps a documentation update should be placed in JES2 migration guide and 
Program Directory about this?

Oh, BTW, did you also need to use TOLERATE? Just curious.


>Guessing I'm not going to forget this one!

Neither me, I remember that I also burned my fingers badly during cloning of a 
system for testing out Y2K... 

;-)

Groete / Greetings
Elardus Engelbrecht

How many electrical engineers does it take to change a light bulb? We don't 
know yet, they're still waiting for a part.
How many programmers does it take to change a light bulb? None - it is a 
hardware problem.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Tom et al,

We were off Friday afternoon so I didn't get your e-mail until this morning.  I 
had the same thoughts over the weekend and messing with it this morning, I 
discovered the problem.  I had neglected to use the ALLD and ALLE parameters in 
my DFDSS job to copy the spool and checkpoint volumes.  So DFDSS dutifully 
copied the pointers to "empty" datasets.  I discovered this when a test of 1.13 
produced the same catastrophic error.  Testing again after adding these parms 
to my DFDSS COPY commands got me past the error and I now have z/OS 2.2 up and 
running on a warm start.

Thank you - again - everybody for your efforts at helping me get past this 
issue.  Guessing I'm not going to forget this one!

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, January 06, 2017 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

On Fri, 6 Jan 2017 17:35:39 +, Pommier, Rex wrote:

>Yes, I am using FlashCopy to create the clones.  I'm re-flashing the 
>spool and checkpoint volumes for subsequent tests because I have others 
>doing other testing of the z/OS 2.2 upgrade so I'm bringing it up cold 
>so they can do their testing.  Once I get a new idea based on the 
>feedback I'm getting, I'll shut it down and reflash my 5 spool volumes 
>and 2 checkpoints and re-IPL.  Much faster than re-flashing the entire 
>LPAR.

I didn't notice, did you try to IPL z/OS 1.13 with the cloned spool?
If so, were there any problems?

--
Tom Marchant

--
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Rebecca Martin]

I went from 1.13 to 2.2 last May without any issue.  You probably have already 
done this several times, but double check your parmlib members - IEAFIXxx, 
IEALPAxx, PROGxx.  Any chance you have one that includes modifications of an 
exit or module from JES2 1.13?  Also, perhaps review any jobs where you may 
have linked any JES2 exits or modifications to ensure you only picked up the 
2.2 libraries.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Tony Harminc]

On 6 January 2017 at 08:51, Pommier, Rex  wrote:

>> What's the reason code with the $BR1?
> 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

Glancing at the code (yes, JES2 is still mostly not OCO), it appears
that for a catastrophic ERROR (vs ABEND) only a reason code of 0 leads
to this format of the $HASP095 message. For a non-zero reason code it
would be e.g.
$HASP095 JES2 CATASTROPHIC ERROR.  CODE = $BR1 (004)

Reason code 0 for a $BR1 is reached only by one path in HASPCKPT, and
that is a non-zero RC from the $DOGBERT service. If I'm right, that RC
is in R15 and survives to be displayed in the $HASP088, and is 8.
Which in turn means that $DOGBERT had to $WAIT (presumably for
checkpoint I/O), but the caller could not tolerate such a wait. There
are at least six ways to get to this RC=8 within $DOGBERT and the
routines it calls.

And that's about as far as I'm going with this, since (a) I'm not IBM
support, (b) I have a day job, (c) I'm a couple of decades out of
doing JES2 stuff, and (d) I my analysis could be anywhere up to 100%
wrong, and I don't want to send you off on a wild goose chase. Fun
while it lasted...

Tony H.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Art Gutowski]

On Thu, 5 Jan 2017 12:19:38 -0600, Tom Marchant  
wrote:

>On Thu, 5 Jan 2017 11:26:51 -0600, Art Gutowski wrote:
>
>>... it probably wouldn't hurt to do a REPORT SYSMODS <1.13 zone> 
>>COMPAREDTO(<2.2 zone>) and vice versa.
>
>Is that going to give you any useful information, Art? I believe that it is 
>possible to code the ++VER in a PTF so that the same PTF can be applied 
>to two different FMIDs, but I can't remember ever seeing it.
>
>Of course, I have been wrong before...

Duh, yes, I meant:

REPORT CROSSZONE
lists conditional requisites that must be installed in certain
zones because of SYSMODs that are installed in other zones. 
 

If memory serves, I did once upon a midnight dreary use multiple ++VER for a 
USERMOD.  Not quite sure why, but I think it was due to sharing a GLOBAL zone 
for multiple releases, and didn't want to have to change USERMOD names nor 
REJECT/RECEIVE during parallel testing/deployment.  REPORT SYSMODS would be 
marginally useful in this specific case.

Also, glad someone else pointed out LARGEDS=ALLOWED.  I thought that was a 
prereq for MODE=z11, so I neglected to mention it.

Regards,
Art Gutowski
General Motors, LLC

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Tom Marchant]

On Fri, 6 Jan 2017 17:35:39 +, Pommier, Rex wrote:

>Yes, I am using FlashCopy to create the clones.  I'm re-flashing the 
>spool and checkpoint volumes for subsequent tests because I have 
>others doing other testing of the z/OS 2.2 upgrade so I'm bringing it 
>up cold so they can do their testing.  Once I get a new idea based 
>on the feedback I'm getting, I'll shut it down and reflash my 5 spool 
>volumes and 2 checkpoints and re-IPL.  Much faster than re-flashing 
>the entire LPAR.

I didn't notice, did you try to IPL z/OS 1.13 with the cloned spool?
If so, were there any problems?

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

$DEXIT,STATUS=ENABLED gives me exits 0,1,15,40 are active in production, and 
only 0 on the sandbox.  My JES2PARM shows nothing for exit 0.

From the sandbox:

$DEXIT,STATUS=ENABLED 
$HASP823 EXIT(0) 211  
$HASP823 EXIT(0)STATUS=ENABLED,ENVIRON=JES2,ROUTINES=(),  
$HASP823SPLEVEL=CHECK,TRACE=YES,USECOUNT=0


This is my JES2PARM for production 1.13:

LOADMOD(JES2XIT1) 
LOADMOD(JESXIT15) 
LOADMOD(JS2XIT40) 
EXIT(1)  ROUTINE=JS2XIT1,TRACE=NO 
EXIT(15) ROUTINE=JS2XIT15,TRACE=NO
EXIT(40) ROUTINE=JS2XIT40,TRACE=NO

For 2.2, we have removed exit 40 because we don't use it.  

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 11:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

Just for giggles, do a $DEXIT(*) (check my memory for correct command) and see 
if there are any exits active

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 9:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
> catastrophic error
> 
> Interesting idea, Lizette.  I just tried again, after removing all 
> EXIT statements from my JES2PARM.  Same result, $BR1 catastrophic error.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, January 06, 2017 10: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
> 
> Allan,
> 
> True.  The intent was to think about
>  1) Any JES2 Exits in place that might be causing the issue
>  2) Are all Vendor related fixes for JES2 installed for the migration.
> 
> Just because something is old, does not mean it could not provide 
> insight on an issue.
> 
> :-D
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller
> > Sent: Friday, January 06, 2017 7:54 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
> > catastrophic error
> >
> > That APAR is ancient. The current numbers APAR numbers are OA6.
> > Seems like
> > OA25662 would be circa z/OS 1.4 vintage.
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler
> > Sent: Friday, January 6, 2017 8:50 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex
> > > Sent: Friday, January 06, 2017 6:51 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > 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   =   3A54502C  342C  
> > >   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
> > >   $HASP088 R8   = 3A545018  009FE980  16642BD0  00007000
> > >   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> > >
> > > This was followed by the 02D abend.
> > >
> > > Thanks,
> > >
> > > Rex
> > >
> > > -Origin

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Hi Dale,

Yes, I am using FlashCopy to create the clones.  I'm re-flashing the spool and 
checkpoint volumes for subsequent tests because I have others doing other 
testing of the z/OS 2.2 upgrade so I'm bringing it up cold so they can do their 
testing.  Once I get a new idea based on the feedback I'm getting, I'll shut it 
down and reflash my 5 spool volumes and 2 checkpoints and re-IPL.  Much faster 
than re-flashing the entire LPAR.  :-)

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dale R. Smith
Sent: Friday, January 06, 2017 10:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

On Thu, 5 Jan 2017 03:49:42 +, Pommier, Rex <rpomm...@sfgmembers.com> wrote:

>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

I reply to posts using the web interface and when I tried to use your latest 
post and quote the text for a reply, it came out in 64encode format, so I went 
back to your original entry!

In all your tests since the original one, are you using the same cloned system? 
 I was wondering if you try a new clone of the production system whether it 
will work or not.  There is a possibility of some kind of error due to timing 
of the clone.  I assume the clone was done with a snapshot?

--
Dale R. Smith

--
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Lizette Koehler]

Just for giggles, do a $DEXIT(*) (check my memory for correct command) and see 
if there are any exits active

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 9:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2
> catastrophic error
> 
> Interesting idea, Lizette.  I just tried again, after removing all EXIT
> statements from my JES2PARM.  Same result, $BR1 catastrophic error.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Friday, January 06, 2017 10: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
> 
> Allan,
> 
> True.  The intent was to think about
>  1) Any JES2 Exits in place that might be causing the issue
>  2) Are all Vendor related fixes for JES2 installed for the migration.
> 
> Just because something is old, does not mean it could not provide insight on
> an issue.
> 
> :-D
> 
> Lizette
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Allan Staller
> > Sent: Friday, January 06, 2017 7:54 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2
> > catastrophic error
> >
> > That APAR is ancient. The current numbers APAR numbers are OA6.
> > Seems like
> > OA25662 would be circa z/OS 1.4 vintage.
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Lizette Koehler
> > Sent: Friday, January 6, 2017 8:50 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex
> > > Sent: Friday, January 06, 2017 6:51 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > 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   =   3A54502C  342C  
> > >   $HASP088 R4   = 16CA7000  73B7  00007718  48B4CC30
> > >   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
> > >   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> > >
> > > This was followed by the 02D abend.
> > >
> > > Thanks,
> > >
> > > Rex
> > >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List
> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc
> > > Sent: Thursday, January 05, 2017 7:02 PM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > 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 <rpomm...@sfgmembers.com> wrote:
> > > > 2)  $BR1 in M gives me "lots" of good information .
> > > > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Jesse 1 Robinson]

I missed the mention of a 'clone'. We migrate system software via cloning, but 
we clone and migrate only code, e.g. the sysres volume containing (in this 
case) all of JES2. We migrate to a long existing sandbox system that has its 
own spool and checkpoint, which would have been shut down normally via $P JES2 
before IPLing the new level. 

If OP has also cloned the JES2 checkpoint and spool, there could be some 
internal inconsistency that the 2.1 level happens to fall victim to. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dale R. Smith
Sent: Friday, January 06, 2017 8:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
catastrophic error

On Thu, 5 Jan 2017 03:49:42 +, Pommier, Rex <rpomm...@sfgmembers.com> wrote:

>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

I reply to posts using the web interface and when I tried to use your latest 
post and quote the text for a reply, it came out in 64encode format, so I went 
back to your original entry!

In all your tests since the original one, are you using the same cloned system? 
 I was wondering if you try a new clone of the production system whether it 
will work or not.  There is a possibility of some kind of error due to timing 
of the clone.  I assume the clone was done with a snapshot?

--
Dale R. Smith

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Dale R. Smith]

On Thu, 5 Jan 2017 03:49:42 +, Pommier, Rex  wrote:

>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

I reply to posts using the web interface and when I tried to use your latest 
post and quote the text for a reply, it came out in 64encode format, so I went 
back to your original entry!

In all your tests since the original one, are you using the same cloned system? 
 I was wondering if you try a new clone of the production system whether it 
will work or not.  There is a possibility of some kind of error due to timing 
of the clone.  I assume the clone was done with a snapshot?

-- 
Dale R. Smith

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Jesse 1 Robinson]

We have several JES2 exits crucial to running business-as-usual in our shop. 
Over the years, problems with exits in a new release have generally been of two 
types:

-- Data that used to be reached one way now has to be reached another way. 
Unless thoroughly documented, this sort of change can be difficult to diagnose. 
In the best of cases, JES2 developers will have removed or renamed old control 
block labels so that exit assembly gets an error. The fix may be quite complex, 
but at least there is an upfront warning. 

-- Data that used to be contained in, say, a halfword, now occupies a fullword. 
Fortunately JES2 developers have been conscientious in renaming such fields so 
that exit assembly gets an error--an unmistakable pointer to a change that 
requires (usually minor) recoding. 

In the current case, OP has disabled all exits to no avail. Assuming that all 
JES2 mods are true exits with no inline tweaks, my post is probably moot. There 
is however the possibility that some data written to checkpoint or spool was 
itself modified by some exit code such that turning exits off cannot dodge the 
problem.

Knowing nothing else, I'm leaning toward some kind of 1.13/2.1 compatibility 
issue. I would expect JES2 Level 2 to figure this out.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pommier, Rex
Sent: Friday, January 06, 2017 8:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
catastrophic error

Interesting idea, Lizette.  I just tried again, after removing all EXIT 
statements from my JES2PARM.  Same result, $BR1 catastrophic error.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 10: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

Allan,

True.  The intent was to think about
 1) Any JES2 Exits in place that might be causing the issue
 2) Are all Vendor related fixes for JES2 installed for the migration.

Just because something is old, does not mean it could not provide insight on an 
issue.

:-D

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Allan Staller
> Sent: Friday, January 06, 2017 7:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
> catastrophic error
> 
> That APAR is ancient. The current numbers APAR numbers are OA6. 
> Seems like
> OA25662 would be circa z/OS 1.4 vintage.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, January 6, 2017 8:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex
> > Sent: Friday, January 06, 2017 6:51 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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   =   3A54502C  342C  
> >   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
> >   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
> >   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> >
> > This was followed by the 02D abend.
> >
> > Thanks,
> >
> > Rex
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc
> > Sent: Thursday, January 05, 2017 7:0

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Interesting idea, Lizette.  I just tried again, after removing all EXIT 
statements from my JES2PARM.  Same result, $BR1 catastrophic error.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 10: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

Allan,

True.  The intent was to think about
 1) Any JES2 Exits in place that might be causing the issue
 2) Are all Vendor related fixes for JES2 installed for the migration.

Just because something is old, does not mean it could not provide insight on an 
issue.

:-D

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Allan Staller
> Sent: Friday, January 06, 2017 7:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
> catastrophic error
> 
> That APAR is ancient. The current numbers APAR numbers are OA6. 
> Seems like
> OA25662 would be circa z/OS 1.4 vintage.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, January 6, 2017 8:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pommier, Rex
> > Sent: Friday, January 06, 2017 6:51 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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   =   3A54502C  342C  
> >   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
> >   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
> >   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> >
> > This was followed by the 02D abend.
> >
> > Thanks,
> >
> > Rex
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc
> > Sent: Thursday, January 05, 2017 7:02 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 <rpomm...@sfgmembers.com> wrote:
> > > 2)  $BR1 in M gives me "lots" of good information .
> > > 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 
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

OK, sounds good.  I'm sure glad we have this list to bounce issues off.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Friday, January 06, 2017 10:20 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 saw from your original post you were z11 mode, I was curoius of BERTS were 
exhausted . 
OK, still scratching my head 


- Original Message -

From: "Rex Pommier" <rpomm...@sfgmembers.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, January 6, 2017 10:16:14 AM
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Carmen, 

I'm already at z11 mode. I'm using about 500 BERTs and have about 17000 free 
BERTs. 

Rex 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Friday, January 06, 2017 9:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

since your skipping a release , there were some 1.13 to 2.1 pre install actions 
to take, may be related to your $BR1 abends Before issuing the 
$ACTIVATE,LEVEL=z11 command, review the current utilization of BERT data to 
determine whether there are sufficient BERTs 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0zm100/checkbert.htm
 



- Original Message - 

From: "Rex Pommier" <rpomm...@sfgmembers.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, January 6, 2017 9:18:50 AM
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Lizette. 

No, we don't have Thruput Manager. Thanks, though. 

Rex 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 =  3A54502C 342C 
> $HASP088 R4 = 16CA7000 73B7 7718 48B4CC30
> $HASP088 R8 = 3A545018 009FE980 16642BD0 7000
> $HASP088 R12 = 1647B098 165B6008 9647B144 0008
> 
> This was followed by the 02D abend. 
> 
> Thanks,
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc
> Sent: Thursday, January 05, 2017 7:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rpomm...@sfgmembers.com> wrote: 
> > 2) $BR1 in M gives me "lots" of good information . 
> > 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 
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, whethe

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Carmen Vitullo]

I saw from your original post you were z11 mode, I was curoius of BERTS were 
exhausted . 
OK, still scratching my head 


- Original Message -

From: "Rex Pommier" <rpomm...@sfgmembers.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Friday, January 6, 2017 10:16:14 AM 
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Carmen, 

I'm already at z11 mode. I'm using about 500 BERTs and have about 17000 free 
BERTs. 

Rex 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Friday, January 06, 2017 9:49 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

since your skipping a release , there were some 1.13 to 2.1 pre install actions 
to take, may be related to your $BR1 abends Before issuing the 
$ACTIVATE,LEVEL=z11 command, review the current utilization of BERT data to 
determine whether there are sufficient BERTs 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0zm100/checkbert.htm
 



- Original Message - 

From: "Rex Pommier" <rpomm...@sfgmembers.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Friday, January 6, 2017 9:18:50 AM 
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Lizette. 

No, we don't have Thruput Manager. Thanks, though. 

Rex 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler 
Sent: Friday, January 06, 2017 8:50 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex 
> Sent: Friday, January 06, 2017 6:51 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> 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 =  3A54502C 342C  
> $HASP088 R4 = 16CA7000 73B7 7718 48B4CC30 
> $HASP088 R8 = 3A545018 009FE980 16642BD0 7000 
> $HASP088 R12 = 1647B098 165B6008 9647B144 0008 
> 
> This was followed by the 02D abend. 
> 
> Thanks, 
> 
> Rex 
> 
> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc 
> Sent: Thursday, January 05, 2017 7:02 PM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> 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 <rpomm...@sfgmembers.com> wrote: 
> > 2) $BR1 in M gives me "lots" of good information . 
> > 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 
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 


-

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Hi Carmen,

I'm already at z11 mode.  I'm using about 500 BERTs and have about 17000 free 
BERTs.  

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Friday, January 06, 2017 9:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

since your skipping a release , there were some 1.13 to 2.1 pre install actions 
to take, may be related to your $BR1 abends Before issuing the 
$ACTIVATE,LEVEL=z11 command, review the current utilization of BERT data to 
determine whether there are sufficient BERTs 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0zm100/checkbert.htm
 



- Original Message -

From: "Rex Pommier" <rpomm...@sfgmembers.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, January 6, 2017 9:18:50 AM
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Lizette. 

No, we don't have Thruput Manager. Thanks, though. 

Rex 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 =  3A54502C 342C 
> $HASP088 R4 = 16CA7000 73B7 7718 48B4CC30
> $HASP088 R8 = 3A545018 009FE980 16642BD0 7000
> $HASP088 R12 = 1647B098 165B6008 9647B144 0008
> 
> This was followed by the 02D abend. 
> 
> Thanks,
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc
> Sent: Thursday, January 05, 2017 7:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rpomm...@sfgmembers.com> wrote: 
> > 2) $BR1 in M gives me "lots" of good information . 
> > 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 
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 


--
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, y

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Lizette Koehler]

Allan,

True.  The intent was to think about 
 1) Any JES2 Exits in place that might be causing the issue
 2) Are all Vendor related fixes for JES2 installed for the migration.

Just because something is old, does not mean it could not provide insight on an 
issue.

:-D

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Allan Staller
> Sent: Friday, January 06, 2017 7:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2
> catastrophic error
> 
> That APAR is ancient. The current numbers APAR numbers are OA6. Seems like
> OA25662 would be circa z/OS 1.4 vintage.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Friday, January 6, 2017 8:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Pommier, Rex
> > Sent: Friday, January 06, 2017 6:51 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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   =   3A54502C  342C  
> >   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
> >   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
> >   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> >
> > This was followed by the 02D abend.
> >
> > Thanks,
> >
> > Rex
> >
> > -----Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Tony Harminc
> > Sent: Thursday, January 05, 2017 7:02 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 <rpomm...@sfgmembers.com> wrote:
> > > 2)  $BR1 in M gives me "lots" of good information .
> > > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Carmen Vitullo]

since your skipping a release , there were some 1.13 to 2.1 pre install actions 
to take, may be related to your $BR1 abends 
Before issuing the $ACTIVATE,LEVEL=z11 command, review the current utilization 
of BERT data to determine whether there are sufficient BERTs 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0zm100/checkbert.htm
 



- Original Message -

From: "Rex Pommier" <rpomm...@sfgmembers.com> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Friday, January 6, 2017 9:18:50 AM 
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error 

Hi Lizette. 

No, we don't have Thruput Manager. Thanks, though. 

Rex 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler 
Sent: Friday, January 06, 2017 8:50 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex 
> Sent: Friday, January 06, 2017 6:51 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> 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 =  3A54502C 342C  
> $HASP088 R4 = 16CA7000 73B7 7718 48B4CC30 
> $HASP088 R8 = 3A545018 009FE980 16642BD0 7000 
> $HASP088 R12 = 1647B098 165B6008 9647B144 0008 
> 
> This was followed by the 02D abend. 
> 
> Thanks, 
> 
> Rex 
> 
> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc 
> Sent: Thursday, January 05, 2017 7:02 PM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> 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 <rpomm...@sfgmembers.com> wrote: 
> > 2) $BR1 in M gives me "lots" of good information . 
> > 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 
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 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Hi Lizette.

No, we don't have Thruput Manager.  Thanks, though.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 06, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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   =   3A54502C  342C  
>   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
>   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
>   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> 
> This was followed by the 02D abend.
> 
> Thanks,
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc
> Sent: Thursday, January 05, 2017 7:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rpomm...@sfgmembers.com> wrote:
> > 2)  $BR1 in M gives me "lots" of good information .
> > 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 
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Allan Staller]

That APAR is ancient. The current numbers APAR numbers are OA6. Seems like 
OA25662 would be circa z/OS 1.4 vintage.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 6, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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   =   3A54502C  342C  
>   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
>   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
>   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> 
> This was followed by the 02D abend.
> 
> Thanks,
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Tony Harminc
> Sent: Thursday, January 05, 2017 7:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rpomm...@sfgmembers.com> wrote:
> > 2)  $BR1 in M gives me "lots" of good information .
> > 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 
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Lizette Koehler]

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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Pommier, Rex
> Sent: Friday, January 06, 2017 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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   =   3A54502C  342C  
>   $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30
>   $HASP088 R8   = 3A545018  009FE980  16642BD0  7000
>   $HASP088 R12  = 1647B098  165B6008  9647B144  0008
> 
> This was followed by the 02D abend.
> 
> Thanks,
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Tony Harminc
> Sent: Thursday, January 05, 2017 7:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rpomm...@sfgmembers.com> wrote:
> > 2)  $BR1 in M gives me "lots" of good information .
> > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

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   =   3A54502C  342C   
  $HASP088 R4   = 16CA7000  73B7  7718  48B4CC30 
  $HASP088 R8   = 3A545018  009FE980  16642BD0  7000 
  $HASP088 R12  = 1647B098  165B6008  9647B144  0008 

This was followed by the 02D abend.  

Thanks,

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tony Harminc
Sent: Thursday, January 05, 2017 7:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 <rpomm...@sfgmembers.com> wrote:
> 2)  $BR1 in M gives me "lots" of good information .
> 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 
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Tony Harminc]

On 5 January 2017 at 12:38, Pommier, Rex  wrote:
> 2)  $BR1 in M gives me "lots" of good information .
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Longabaugh, Robert E]

A sysmod can have more than one ++VER.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Thursday, January 05, 2017 4:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

We’re drifting a bit here, but I had to look up ++VER to see whether a single 
PTF could be installed on more than base FMID. I find 

'-FMID--(--sysmod_id--)-'

I have never made peace with railroad track diagrams, but I think this means 
that only one base FMID can be specified. I don't see recursion. (Hate RR.)   

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Thursday, January 05, 2017 10:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
catastrophic error

On Thu, 5 Jan 2017 11:26:51 -0600, Art Gutowski wrote:

>... it probably wouldn't hurt to do a REPORT SYSMODS <1.13 zone>
>COMPAREDTO(<2.2 zone>) and vice versa.

Is that going to give you any useful information, Art? I believe that it is 
possible to code the ++VER in a PTF so that the same PTF can be applied to two 
different FMIDs, but I can't remember ever seeing it.

Of course, I have been wrong before...

--
Tom Marchant


--
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Jesse 1 Robinson]

We’re drifting a bit here, but I had to look up ++VER to see whether a single 
PTF could be installed on more than base FMID. I find 

'-FMID--(--sysmod_id--)-'

I have never made peace with railroad track diagrams, but I think this means 
that only one base FMID can be specified. I don't see recursion. (Hate RR.)   

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Thursday, January 05, 2017 10:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 
catastrophic error

On Thu, 5 Jan 2017 11:26:51 -0600, Art Gutowski wrote:

>... it probably wouldn't hurt to do a REPORT SYSMODS <1.13 zone>
>COMPAREDTO(<2.2 zone>) and vice versa.

Is that going to give you any useful information, Art? I believe that it is 
possible to code the ++VER in a PTF so that the same PTF can be applied to two 
different FMIDs, but I can't remember ever seeing it.

Of course, I have been wrong before...

--
Tom Marchant


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Tom Marchant]

On Thu, 5 Jan 2017 11:26:51 -0600, Art Gutowski wrote:

>... it probably wouldn't hurt to do a REPORT SYSMODS <1.13 zone> 
>COMPAREDTO(<2.2 zone>) and vice versa.

Is that going to give you any useful information, Art? I believe that it is 
possible to code the ++VER in a PTF so that the same PTF can be applied 
to two different FMIDs, but I can't remember ever seeing it.

Of course, I have been wrong before...

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

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 gives me "lots" of good information .  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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Art Gutowski]

From "Pommier, Rex"  on Thu, 5 Jan 2017 17:17:01 +:

>Thanks for the suggestion.  We are already running MODE=DUPLEX.

We had one or two systems where we had to make this change, and a couple that 
we had to migrate to z11 checkpoint format.  Other than that, no issues with 
upgrade and downgrade via WARMSTART between 1.13 and 2.2.

As others suggested, verify your toleration maintenance, and it probably 
wouldn't hurt to do a REPORT SYSMODS <1.13 zone> COMPAREDTO(<2.2 zone>) and 
vice versa.  I've been burned by "missing" PTFs before that make incompatible 
changes (e.g., previously mentioned incompatible parameters, though these 
usually are resolved via startup prompts).

Finally, do you have any exits installed?  We had to rewrite a few of our exits 
for 2.2.  I don't know which (I'm not on the upgrade project), but I can find 
out.

Regards,
Art Gutowski
General Motors, LLC

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Hi Ravi,

Thanks for the suggestion.  We are already running MODE=DUPLEX.


CKPTDEF  CKPT1=(DSNAME=SYS1.HASPCKPA,
 VOLSER=Z1PG02,  
 INUSE=YES), 
 CKPT2=(DSNAME=SYS1.HASPCKPB,
 VOLSER=Z1PG03,  
 INUSE=YES), 
 DUPLEX=ON,  
 LOGSIZE=2,  
 MODE=DUPLEX,
 VERSIONS=(NUMBER=0, 
WARN=80),
 VOLATILE=(ONECKPT=WTOR, 
ALLCKPT=WTOR)

Rex



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ravi Gaur
Sent: Thursday, January 05, 2017 7:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic 
error

Also not to miss if you have MODE=DUAL have it changed to MODE=DUPLEX  
...There's an APAR regarding it with zOS2.2

--
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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

Hi Elardus,

  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.

  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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Ravi Gaur]

Also not to miss if you have MODE=DUAL have it changed to MODE=DUPLEX  
...There's an APAR regarding it with zOS2.2

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Allan Staller]

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

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Elardus Engelbrecht]

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

IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

[Pommier, Rex]

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