On 6 January 2017 at 08:51, Pommier, Rex <rpomm...@sfgmembers.com> 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
