Re: Help with diagnosing S0C4-03B
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 DB2 in amode 64, it does go there itself. It should be cleaning up the high halves of registers when it does so though. So you could be seeing an IBM bug, or more likely an overlay of some internal control block. In article <0b5901d4716b$52b12f10$f8138d30$@mcn.org> you 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 SANDBOX1 - ABEND=S0C4 U REASON=003B > 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. 0006Interruption Code. 003B > PSW. 078D2400 95E9D1B6 > GPR0. _0004 GPR1. _15E972F0 GPR2. > _15E6A4C8 GPR3. _00FC1D00 > GPR4. _009FE990 GPR5. _1560DDD0 GPR6. > _15E97200 GPR7. _0001 > GPR8. _15E972F4 GPR9. _0004 GPR10 > _ GPR11 _95E990A0 > GPR12 _95E9D148 GPR13 _15E9720C GPR14 > _95E972F4 GPR15 _00180705 > FPC.. > FPR0. 2610 FPR1. 41120DD7 50429B6D > FPR2. 1800 FPR3. 4116A09E 667F3BCD > FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 > FPR6. 40A2F983 6E4E4415FPR7. > FPR8. FPR9. > FPR10 FPR11 > FPR12 FPR13 > FPR14 FPR15 > > Storage dump near condition, beginning at location: 15E9D1A0 > +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 > D096 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 -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637Cary, NC 27513 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Help with diagnosing S0C4-03B
Well, I made it go away. Didn't really diagnose it, but made it go away hacking at the 87 different ways of linking or loading DSNULI/DSNALI/DSNRLI/DSNHLI2/DSNHLIR/DSNHLI/DSNWLI2/DSNWLIR/DSNWLI/DSNELI. G ... Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-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 [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 SANDBOX1 - ABEND=S0C4 U REASON=003B 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. 0006Interruption Code. 003B PSW. 078D2400 95E9D1B6 GPR0. _0004 GPR1. _15E972F0 GPR2. _15E6A4C8 GPR3. _00FC1D00 GPR4. _009FE990 GPR5. _1560DDD0 GPR6. _15E97200 GPR7. _0001 GPR8. _15E972F4 GPR9. _0004 GPR10 _ GPR11 _95E990A0 GPR12 _95E9D148 GPR13 _15E9720C GPR14 _95E972F4 GPR15 _00180705 FPC.. FPR0. 2610 FPR1. 41120DD7 50429B6D FPR2. 1800 FPR3. 4116A09E 667F3BCD FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 FPR6. 40A2F983 6E4E4415FPR7. FPR8. FPR9. FPR10 FPR11 FPR12 FPR13 FPR14 FPR15 Storage dump near condition, beginning at location: 15E9D1A0 +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 D096 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Help with diagnosing S0C4-03B
> 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 diagnosing S0C4-03B 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. 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 SANDBOX1 - ABEND=S0C4 U REASON=003B > > 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. 0006Interruption Code. 003B > > PSW. 078D2400 95E9D1B6 > > GPR0. _0004 GPR1. _15E972F0 GPR2. > _15E6A4C8 GPR3. _00FC1D00 > GPR4. _009FE990 GPR5. _1560DDD0 GPR6. > _15E97200 GPR7. _0001 > GPR8. _15E972F4 GPR9. _0004 GPR10 > _ GPR11 _95E990A0 > GPR12 _95E9D148 GPR13 _15E9720C GPR14 > _95E972F4 GPR15 _00180705 > FPC.. > > FPR0. 2610 FPR1. 41120DD7 50429B6D > > FPR2. 1800 FPR3. 4116A09E 667F3BCD > > FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 > > FPR6. 40A2F983 6E4E4415FPR7. > > FPR8. FPR9. > > FPR10 FPR11 > > FPR12 FPR13 > > FPR14 FPR15 > > > > Storage dump near condition, beginning at location: 15E9D1A0 > > +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 > D096 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 -- 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: Help with diagnosing S0C4-03B
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 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 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 SANDBOX1 - ABEND=S0C4 U REASON=003B >> >> 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. 0006Interruption Code. 003B >> >> PSW. 078D2400 95E9D1B6 >> >> GPR0. _0004 GPR1. _15E972F0 GPR2. >> _15E6A4C8 GPR3. _00FC1D00 >> GPR4. _009FE990 GPR5. _1560DDD0 GPR6. >> _15E97200 GPR7. _0001 >> GPR8. _15E972F4 GPR9. _0004 GPR10 >> _ GPR11 _95E990A0 >> GPR12 _95E9D148 GPR13 _15E9720C GPR14 >> _95E972F4 GPR15 _00180705 >> FPC.. >> >> FPR0. 2610 FPR1. 41120DD7 50429B6D >> >> FPR2. 1800 FPR3. 4116A09E 667F3BCD >> >> FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 >> >> FPR6. 40A2F983 6E4E4415FPR7. >> >> FPR8. FPR9. >> >> FPR10 FPR11 >> >> FPR12 FPR13 >> >> FPR14 FPR15 >> >> >> >> Storage dump near condition, beginning at location: 15E9D1A0 >> >> +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 >> D096 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
Re: Help with diagnosing S0C4-03B
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. 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 SANDBOX1 - ABEND=S0C4 U REASON=003B > > 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. 0006Interruption Code. 003B > > PSW. 078D2400 95E9D1B6 > > GPR0. _0004 GPR1. _15E972F0 GPR2. > _15E6A4C8 GPR3. _00FC1D00 > GPR4. _009FE990 GPR5. _1560DDD0 GPR6. > _15E97200 GPR7. _0001 > GPR8. _15E972F4 GPR9. _0004 GPR10 > _ GPR11 _95E990A0 > GPR12 _95E9D148 GPR13 _15E9720C GPR14 > _95E972F4 GPR15 _00180705 > FPC.. > > FPR0. 2610 FPR1. 41120DD7 50429B6D > > FPR2. 1800 FPR3. 4116A09E 667F3BCD > > FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 > > FPR6. 40A2F983 6E4E4415FPR7. > > FPR8. FPR9. > > FPR10 FPR11 > > FPR12 FPR13 > > FPR14 FPR15 > > > > Storage dump near condition, beginning at location: 15E9D1A0 > > +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 > D096 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Help with diagnosing S0C4-03B
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 SANDBOX1 - ABEND=S0C4 U REASON=003B 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. 0006Interruption Code. 003B PSW. 078D2400 95E9D1B6 GPR0. _0004 GPR1. _15E972F0 GPR2. _15E6A4C8 GPR3. _00FC1D00 GPR4. _009FE990 GPR5. _1560DDD0 GPR6. _15E97200 GPR7. _0001 GPR8. _15E972F4 GPR9. _0004 GPR10 _ GPR11 _95E990A0 GPR12 _95E9D148 GPR13 _15E9720C GPR14 _95E972F4 GPR15 _00180705 FPC.. FPR0. 2610 FPR1. 41120DD7 50429B6D FPR2. 1800 FPR3. 4116A09E 667F3BCD FPR4. 40517CC1 B727220BFPR5. 40B504F3 33F9DE65 FPR6. 40A2F983 6E4E4415FPR7. FPR8. FPR9. FPR10 FPR11 FPR12 FPR13 FPR14 FPR15 Storage dump near condition, beginning at location: 15E9D1A0 +00 15E9D1A0 D01407FE 58F0E018 EB66D000 0026B916 0066B218 F000EB66 D096 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
