The PSW is amode 31, so there's something odd going on. I'd look at the
system trace to see if the PGM 03B really occurred at that spot. The LE
dumps can be nice for simple errors, but when it gets weird like this,
it's better to use SYSMDUMP and IPCS to see what happened. Although you
can't call
-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Wednesday, October 31, 2018 3:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Help with diagnosing S0C4-03B
Correcting the subject line. Sorry. Please reply to this one if possible.
Charles
-Original Message-
From: Charles Mills
> What butt-stupid program ... ?
Umm, Language Environment
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Smith
Sent: Wednesday, October 31, 2018 4:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Help with diagnos
I better correct that... I get Region 1 2 & 3 mixed up, so I can't
definitively say which bits are corrupt... but it may well be all of them.
I got this (and its sisters, 39 & 3A (maybe)) a few times after I turned on
the DIAG trap to catch bad register save/restore hygiene.
sas
On Wed, Oct 31,
What butt-stupid program decided you didn't need to see the high-order
words of the registers?
Your abend is due to a dirty high register... the 3b indicates pollution in
the high-order 11 bits.
sas
On Wed, Oct 31, 2018 at 6:45 PM Charles Mills wrote:
> Correcting the subject line. Sorry.
Correcting the subject line. Sorry. Please reply to this one if possible.
Charles
-Original Message-
From: Charles Mills [mailto:charl...@mcn.org]
Sent: Wednesday, October 31, 2018 3:43 PM
To: IBM Mainframe Discussion List (IBM-MAIN@listserv.ua.edu)
Subject: Help with diagnosing
