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, 2018 at 7:08 PM Steve Smith <sasd...@gmail.com> wrote: > 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 <charl...@mcn.org> wrote: > >> 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 S0C4-038 >> >> I am getting the following error: >> >> IEF450I xxxxxxxx SANDBOX1 - ABEND=S0C4 U0000 REASON=0000003B >> >> S0C4-3B is documented in part as >> >> Region-Third exception. While running in 64-bit addressing mode, one of >> the >> following errors occurred: >> - A program attempted to reference storage that had not been obtained. To >> correct the error, allocate the storage before attempting to reference it. >> - A program used a 31-bit pointer that had the high order bit on. >> >> The error occurs during a call from an LE C++ program to the DB2 interface >> module DSNWLI. It works when the DB2 subsystem is V10 but not when it is >> V11, so the error is something fairly subtle, not that the program is 100% >> wrong. >> >> Here is an exact cut-and-paste from the LE diagnostic dump. (IOW don't >> blame >> me for that funky register display.) >> >> Machine State: >> >> ILC..... 0006 Interruption Code..... 003B >> >> PSW..... 078D2400 95E9D1B6 >> >> GPR0..... ********_00000004 GPR1..... ********_15E972F0 GPR2..... >> ********_15E6A4C8 GPR3..... ********_00FC1D00 >> GPR4..... ********_009FE990 GPR5..... ********_1560DDD0 GPR6..... >> ********_15E97200 GPR7..... ********_00000001 >> GPR8..... ********_15E972F4 GPR9..... ********_00000004 GPR10.... >> ********_00000000 GPR11.... ********_95E990A0 >> GPR12.... ********_95E9D148 GPR13.... ********_15E9720C GPR14.... >> ********_95E972F4 GPR15.... ********_00180705 >> FPC...... 00000000 >> >> FPR0..... 26100000 00000000 FPR1..... 41120DD7 50429B6D >> >> FPR2..... 18000000 00000000 FPR3..... 4116A09E 667F3BCD >> >> FPR4..... 40517CC1 B727220B FPR5..... 40B504F3 33F9DE65 >> >> FPR6..... 40A2F983 6E4E4415 FPR7..... 00000000 00000000 >> >> FPR8..... 00000000 00000000 FPR9..... 00000000 00000000 >> >> FPR10.... 00000000 00000000 FPR11.... 00000000 00000000 >> >> FPR12.... 00000000 00000000 FPR13.... 00000000 00000000 >> >> FPR14.... 00000000 00000000 FPR15.... 00000000 00000000 >> >> >> >> Storage dump near condition, beginning at location: 15E9D1A0 >> >> +000000 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 >> D0000096 17FF58E0 |.....0..............0.. >> >> Questions: How do I interpret that PSW display in light of an ABEND that >> is >> specific to AMODE 64? Any clues as to how I might diagnose this? >> >> Charles >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > > -- > sas > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
