They told me they would get back to me today
> On Aug 26, 2019, at 8:51 AM, David Crayford <dcrayf...@gmail.com> wrote: > > A Sev 1 PMR? They're quite rare and usually used for important stuff like > "DB2 is hosed and I can't run production work" :) > > On 2019-08-25 10:29 PM, Joseph Reichman wrote: >> JUST CODED region=1000M same abend opened up SEV 1 PMR with IBM but I told >> them they could wait till Monday >> >> >> thanks >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of >> Lizette Koehler >> Sent: Sunday, August 25, 2019 10:03 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: S0C4 XL C Compiler >> >> Sometimes 0M or 0G will cause problems with RTM. You might want to try a >> real larger number like 512M or 1000M >> >> If there is no below the line storage available for recovery then 0M can >> cause some really strange occurrences. >> >> What does your virtual storage look like when your job ends? >> >> Lizette >> >> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >>> Behalf Of Charles Mills >>> Sent: Sunday, August 25, 2019 6:58 AM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Re: S0C4 XL C Compiler >>> >>> REGION=0G will give you a thousand times more. >>> >>> Seriously, I had one of these the other day. I ran a C++ compile -- >>> not with my usual JCL -- and got a S0C4. Like you, I went "I can't >>> believe this!" I tried something simple and the problem went away -- >>> don't recall what it was that I did, so thought perhaps it was that I >>> had increased the region. The problem was so out of left field and so >>> quickly fixed that I do not recall the circumstances. Was within the >>> last month, so perhaps some recent maintenance broke the compiler. >>> >>> Charles >>> >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >>> On Behalf Of Joseph Reichman >>> Sent: Saturday, August 24, 2019 6:40 PM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Re: S0C4 XL C Compiler >>> >>> REGION=0M I Think that's the max >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On >>> Behalf Of Charles Mills >>> Sent: Saturday, August 24, 2019 9:36 PM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Re: S0C4 XL C Compiler >>> >>> Try increasing the region. >>> >>> Charles >>> >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >>> On Behalf Of Joseph Reichman >>> Sent: Saturday, August 24, 2019 6:27 PM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: S0C4 XL C Compiler >>> >>> >>> >>> Simple little program cannt believe it >>> >>> >>> >>> #include <ctest.h> >>> >>> #include <ceeedcct.h> >>> >>> #include <string.h> >>> >>> #include <stdio.h> >>> >>> #include <stdlib.h> >>> >>> #include <dll.h> >>> >>> #pragma map(__ceetest,"CEETEST") >>> >>> #pragma linkage(CEETEST,OS_NOSTACK) >>> >>> main( int argc, char* argv[]) >>> >>> { >>> >>> typedef int (DLL_FN)(char *) >>> >>> dllhandle* dllHandle; >>> >>> DLL_FN* fn; >>> >>> _VSTRING commands; >>> >>> _FEEDBACK fc; >>> >>> >>> CEETEST(&commands,&fc); >>> >>> dllHandle = dllload("SYSADATA"); >>> >>> fn = (DLL_FN*) (dllqueryfn(dllHandle, "opendata")); >>> >>> fn("SYSADATA"); >>> >>> return; >>> >>> } >>> >>> >>> >>> CEE3204S The system detected a protection exception (System >>> Completion Code=0C4). >>> >>> From entry point >>> dtFuncDeclarator::BeginNestedFunc(sFuncSymbol*) >>> at statement 729 at compile unit offset >>> >>> +00000510 at entry offset +00000510 at address 21DEB1B8. >>> >>> ---------------------------------------------------------------------- >>> 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 >> >> ---------------------------------------------------------------------- >> 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
