Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
> Why? Because it treats trailing commas as continuation chararacters. > I find Rexx pleasantly consistent there: I find REXX unpleasantly consistent there; I find, e.g., PL/I, pleasantly consistent in the use of semicolons. > Compare POSIX shell conventions. Why? The Bourne shell and its children are poster children for bad language design. I'd rather compare REXX continuation to, e.g., Algol 60, C, Pascal, PL/I, Ruby. Personally, I believe that nobody understands a language unless he can identify the flaws in it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, August 30, 2019 6:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend On Fri, 30 Aug 2019 17:33:56 +, Seymour J Metz wrote: >Be careful what you ask for - you might get it. It's one of the things that I >don't like about REXX. > >ObHamlet "And make us rather bear those semicolons we have, then fly to >continuation conventions that we know not of" > ( C 'then' 'than') Why? I find Rexx pleasantly consistent there: An instruction is terminated by: o A newline not preceded by a comma o Or a semicolon Spaces are irrelevant Newline and semicolon are highly interchangeable. Compare POSIX shell conventions. Are they even documented? For example: 542 $ for I in 1 2 > do > echo $I > done OK, but: 544 $ for I in 1 2; do; echo $I; done -sh: syntax error near unexpected token `;' -- gil -- 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: Case TS002648607 (PMR 76523,082,000) - Compiler abend
And then your successor can modify and debug it! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Frank Swarbrick Sent: Friday, August 30, 2019 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend Swift is even smarter. It seems like even a newline doesn't absolutely indicate the end of a statement, as long as the compiler can infer that a statement absolutely has not completed. You can (but I don't recommend it) even do something like this: let a = 1 print ( a ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Swift is even smarter. It seems like even a newline doesn't absolutely indicate the end of a statement, as long as the compiler can infer that a statement absolutely has not completed. You can (but I don't recommend it) even do something like this: let a = 1 print ( a ) From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, August 30, 2019 4:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend On Fri, 30 Aug 2019 17:33:56 +, Seymour J Metz wrote: >Be careful what you ask for - you might get it. It's one of the things that I >don't like about REXX. > >ObHamlet "And make us rather bear those semicolons we have, then fly to >continuation conventions that we know not of" > ( C 'then' 'than') Why? I find Rexx pleasantly consistent there: An instruction is terminated by: o A newline not preceded by a comma o Or a semicolon Spaces are irrelevant Newline and semicolon are highly interchangeable. Compare POSIX shell conventions. Are they even documented? For example: 542 $ for I in 1 2 > do > echo $I > done OK, but: 544 $ for I in 1 2; do; echo $I; done -sh: syntax error near unexpected token `;' -- gil -- 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: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Gil, I agree with you on Rexx, writing it since it first came out on VM. Some of the other languages are a bit funky. Scott On Fri, Aug 30, 2019 at 6:04 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Fri, 30 Aug 2019 17:33:56 +, Seymour J Metz wrote: > > >Be careful what you ask for - you might get it. It's one of the things > that I don't like about REXX. > > > >ObHamlet "And make us rather bear those semicolons we have, then fly to > continuation conventions that we know not of" > > > ( C 'then' 'than') > > Why? I find Rexx pleasantly consistent there: > An instruction is terminated by: > o A newline not preceded by a comma > o Or a semicolon > Spaces are irrelevant > Newline and semicolon are highly interchangeable. > > Compare POSIX shell conventions. Are they even documented? For example: > 542 $ for I in 1 2 > > do > > echo $I > > done > OK, but: > 544 $ for I in 1 2; do; echo $I; done > -sh: syntax error near unexpected token `;' > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Scott Ford IDMWORKS z/OS Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
On Fri, 30 Aug 2019 17:33:56 +, Seymour J Metz wrote: >Be careful what you ask for - you might get it. It's one of the things that I >don't like about REXX. > >ObHamlet "And make us rather bear those semicolons we have, then fly to >continuation conventions that we know not of" > ( C 'then' 'than') Why? I find Rexx pleasantly consistent there: An instruction is terminated by: o A newline not preceded by a comma o Or a semicolon Spaces are irrelevant Newline and semicolon are highly interchangeable. Compare POSIX shell conventions. Are they even documented? For example: 542 $ for I in 1 2 > do > echo $I > done OK, but: 544 $ for I in 1 2; do; echo $I; done -sh: syntax error near unexpected token `;' -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Be careful what you ask for - you might get it. It's one of the things that I don't like about REXX. ObHamlet "And make us rather bear those semicolons we have, then fly to continuation conventions that we know not of" -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Frank Swarbrick Sent: Thursday, August 29, 2019 5:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend One reason to love Swift. No semicolons required!!! From: IBM Mainframe Discussion List on behalf of Matt Hogstrom Sent: Thursday, August 29, 2019 12:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend I always knew semi-colons were dangerous. Most people butcher their usage in grammar and now abends … who knows what mischief they will stir up next. Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://secure-web.cisco.com/1z1khwa-EVxDj_4NZq5nLiY2pjKbrUDBfyj848DcAPOhYYlsqNBoq1RV1bxB7gHW1CAqZrB-ymcqLMzatQcqGxg32voBFTrpiNRoKMOueNuLNejT-uU_F_sd04c_L0CqwRu4LM8AL31o-s09C0c3KBx2ZfleZBd1FYuKbhCIhPbVLHvBZ0qCHlNUP_394BCOxIeW2Mp6uY70LpbNTSJh4FXc3w-j7ue5_MgEURsQLuzzumUkcszReveVS3mfUJY9CKtEQQrttnjal0ruephNoBdOAsXxd3rGRHOJOU_qv9UyqJAJqaK_YwRYofLBl52wRtpq2Gcxat-niDCFecKvF9eSXHuyzGybUgV-TjpfLr6SkhK8S3c4ZyRsvtNAWFI-yBNN25Hk9pV_82tWS6ZbcGTjZ6ibCDjL3MMDo2GXqvp4JH_pON9FPI7xzNUVYxTR6/https%3A%2F%2Ffacebook.com%2Fmatt.hogstrom> LinkedIn <https://secure-web.cisco.com/1OxM3dHfCL09H1FniDjnokzAJLK_AfxnIQT0H45JZlSsamHqNvo76h96Kl4urnoRf1HEaW1wJR6UHWVCSIoAJL0eCOC8nAQpV20lTv0eOMYfP3RHvYyB-LQi4bcgnSdLeTjpXu1EIOL2FTgdtXIGZie4FUN6YluSKXJyx8Fg-QAdn7v6tCCvN9fwdZPSvn_SwWmucy0LHOraBlmBfLBUanG1HnKLIK8ZJlg1cDm8-2QwnYtvcvgbaz9TqH_lFwJcZLFyv320vFqNKngtS7FUjp8IpPrsYal6XR1By45mh_g-1dyxeovQKYYKMsEu43BXhH6_5eVCMOaB9ZqDdGPxTKpgtvRiRmutSI5vWqidML-SZ2GO9YZjYAhODUJR0h5mPum9_NcTnxenWg3JG4TWKKc80Dt0M965mje_QEE16eNk/https%3A%2F%2Flinkedin%2Fin%2Fmhogstrom> Twitter <https://secure-web.cisco.com/1aj1-8tqjePkx5clruKgCKAq3bOBloEeNq_QrX6DvXaWu-1jEIiyLkIs11FIzmId8h1bfLD3r63UVBoM9AlwMoidy4Qq5pjkr5A9tkFv9pi4BbRtHg1iKiY5Zi2uqNi_uNSWRNFQRlIbSKjhG6UOTr9RTglJlLV1jCvFPJV1ODdqCaIlcQ7e4LAwKJ8CiUoSOJkwbK_778cdav7XJSAcBWYVW5KgG3gqtTpcLN3q0WxsEMNZ2Vcz4xX2T_esJnJEXFMGG2bbopUYJFdxpC-nHdfycWKwwiz3MJR43RVNiWMEW1ubKgRzE1_CIdMhvw_Af3cFsFB_W4wbinYpHjV0KRoloTWhe4CfdxfZjtn9iFSqDrii047QrgIBDz_fqU8iGql58qqo0gg8ResI9gTIXK3WZO0z6KnrXt0FDjP9hHQbjkq7bm_0p-if08SHAgpDt/https%3A%2F%2Ftwitter.com%2Fhogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On Aug 29, 2019, at 1:37 PM, Charles Mills wrote: > > Amazing! > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joseph Reichman > Sent: Thursday, August 29, 2019 10:27 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Begin forwarded message: > >> From: "Basil Kanneth" >> Date: August 29, 2019 at 11:01:57 AM EDT >> To: "Joseph Reichman" >> Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend >> >> Hi Joseph, >> >> It turns out the system protection exception occurred because of a missing >> semicolon after the following line in the code: >> typedef int (DLL_FN)(char *) >> >> So it should be: >> typedef int (DLL_FN)(char *); >> >> If you make the above changes, your test case should compile fine. >> >> We agree the compiler should not abend in this situation and we are >> investigating a potential fix. >> >> I will provide you with another update by Thursday, September 5th, 2019. >> >> Regards, >> >> Basil Kanneth, PMP® >> IBM XL C,C++, Fortran & COBOL Compilers Service Team >> IBM Software Group - Toronto Lab -- 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
Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
It was in the early 80s. And, it might have been the Capex Optimizer we used then. Problem went away when he changed the installation option. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Mark Jacobs > Sent: Thursday, August 29, 2019 1:56 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Surprising that the configuration of a COBOL compiler would care about a > TMS, but OK. > > Mark Jacobs > > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - https://urldefense.proofpoint.com/v2/url?u=https- > 3A__api.protonmail.ch_pks_lookup-3Fop-3Dget-26search-3Dmarkjacobs- > 40protonmail.com=DwIFaQ=C3yme8gMkxg_ihJNXS06ZyWk4EJm8Ldrrv > xQb- > Je7sw=u9g8rUevBoyCPAdo5sWE9w=U2qQccZtMsqQaoMNAbjWOR02 > Qp8atllxid3_qEwkxU8=fw2jjw9a8rDskHNADpjpMFMsqVNhDGnEvi0_fmTs > T4U= > > ‐‐‐ Original Message ‐‐‐ > On Thursday, August 29, 2019 4:48 PM, Gibney, Dave > wrote: > > > Very early. Fairly new at the job COBOL programming. Compiler was > updated and started dying. I went a couple weeks round and round with the > guy who did the install, trying to get him to open the issue with IBM. We > were kind of formal in those days and he didn't believe the young > newcomer. > > I finally got him to let me see the installation options he'd used. One > > stood > right out. There was a "tape management system' yes or no. He had no. I > asked him what he thought CA-1 (well, then UCC-1) was.. > > > > > -Original Message- > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > > > Behalf Of Edward Finnell > > > Sent: Thursday, August 29, 2019 1:32 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler > > > abend I saw one as lab assistant. The bright young thing came > > > tromping in 'the eight's broken, I need it fixed'. Turns out she was > > > right! The adder's carry bit wasn't propagating. 3+3=6, 3+4=7, 4+4=7? > Whoa nelly call the CE. > > > In a message dated 8/29/2019 3:16:16 PM Central Standard Time, > > > t...@tombrennansoftware.com writes: > > > And I'm sure you can guess exactly how many of those times the > > > system really turned out to be broken :) > > > > > > 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
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
One reason to love Swift. No semicolons required!!! From: IBM Mainframe Discussion List on behalf of Matt Hogstrom Sent: Thursday, August 29, 2019 12:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend I always knew semi-colons were dangerous. Most people butcher their usage in grammar and now abends … who knows what mischief they will stir up next. Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On Aug 29, 2019, at 1:37 PM, Charles Mills wrote: > > Amazing! > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joseph Reichman > Sent: Thursday, August 29, 2019 10:27 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Begin forwarded message: > >> From: "Basil Kanneth" >> Date: August 29, 2019 at 11:01:57 AM EDT >> To: "Joseph Reichman" >> Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend >> >> Hi Joseph, >> >> It turns out the system protection exception occurred because of a missing >> semicolon after the following line in the code: >> typedef int (DLL_FN)(char *) >> >> So it should be: >> typedef int (DLL_FN)(char *); >> >> If you make the above changes, your test case should compile fine. >> >> We agree the compiler should not abend in this situation and we are >> investigating a potential fix. >> >> I will provide you with another update by Thursday, September 5th, 2019. >> >> Regards, >> >> Basil Kanneth, PMP® >> IBM XL C,C++, Fortran & COBOL Compilers Service Team >> IBM Software Group - Toronto Lab -- 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: Case TS002648607 (PMR 76523,082,000) - Compiler abend
I've had the COBOL compiler abend during the SQL preprocessor step with a malformed EXEC SQL statement. From: IBM Mainframe Discussion List on behalf of Allan Staller Sent: Thursday, August 29, 2019 11:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend Found another instance of the same thing many years ago. I forget if it was COBOL-E or COBOL-F. A missing period caused the compiler to abend. Ah! The good old days. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, August 29, 2019 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend Amazing! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joseph Reichman Sent: Thursday, August 29, 2019 10:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend Begin forwarded message: > From: "Basil Kanneth" > Date: August 29, 2019 at 11:01:57 AM EDT > To: "Joseph Reichman" > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Hi Joseph, > > It turns out the system protection exception occurred because of a missing > semicolon after the following line in the code: > typedef int (DLL_FN)(char *) > > So it should be: > typedef int (DLL_FN)(char *); > > If you make the above changes, your test case should compile fine. > > We agree the compiler should not abend in this situation and we are > investigating a potential fix. > > I will provide you with another update by Thursday, September 5th, 2019. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team IBM Software > Group - Toronto Lab > > > > From:"Joseph Reichman" > To: "'Basil Kanneth'" > Date:08/29/2019 08:16 AM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > Any updates > > thanks > > -- 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 ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- 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: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Surprising that the configuration of a COBOL compiler would care about a TMS, but OK. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Thursday, August 29, 2019 4:48 PM, Gibney, Dave wrote: > Very early. Fairly new at the job COBOL programming. Compiler was updated and > started dying. I went a couple weeks round and round with the guy who did the > install, trying to get him to open the issue with IBM. We were kind of formal > in those days and he didn't believe the young newcomer. > I finally got him to let me see the installation options he'd used. One stood > right out. There was a "tape management system' yes or no. He had no. I asked > him what he thought CA-1 (well, then UCC-1) was.. > > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On > > Behalf Of Edward Finnell > > Sent: Thursday, August 29, 2019 1:32 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > I saw one as lab assistant. The bright young thing came tromping in 'the > > eight's broken, I need it fixed'. Turns out she was right! The adder's > > carry bit > > wasn't propagating. 3+3=6, 3+4=7, 4+4=7? Whoa nelly call the CE. > > In a message dated 8/29/2019 3:16:16 PM Central Standard Time, > > t...@tombrennansoftware.com writes: > > And I'm sure you can guess exactly how many of those times the system > > really turned out to be broken :) > > > > 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
Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Very early. Fairly new at the job COBOL programming. Compiler was updated and started dying. I went a couple weeks round and round with the guy who did the install, trying to get him to open the issue with IBM. We were kind of formal in those days and he didn't believe the young newcomer. I finally got him to let me see the installation options he'd used. One stood right out. There was a "tape management system' yes or no. He had no. I asked him what he thought CA-1 (well, then UCC-1) was.. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Edward Finnell > Sent: Thursday, August 29, 2019 1:32 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > I saw one as lab assistant. The bright young thing came tromping in 'the > eight's broken, I need it fixed'. Turns out she was right! The adder's carry > bit > wasn't propagating. 3+3=6, 3+4=7, 4+4=7? Whoa nelly call the CE. > > In a message dated 8/29/2019 3:16:16 PM Central Standard Time, > t...@tombrennansoftware.com writes: > And I'm sure you can guess *exactly* how many of those times the system > really turned out to be broken :) > > -- > 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: [External] Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
I saw one on a BUNCH machine compiler, except that it didn't fail, it just gave the wrong result. It was a fairly straightforward COMPUTE statement, something along the lines of COMPUTE D=C-(A*B). The result came back as D=C+(A*B). Didn't take the company long to produce a fix for that one! Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Brennan Sent: Thursday, August 29, 2019 3:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend So many times I worked on a script or compiled/assembled code, got an error that made no sense, and then complained to anyone who would listen, "The system is obviously broken". And I'm sure you can guess *exactly* how many of those times the system really turned out to be broken :) On 8/29/2019 10:27 AM, Joseph Reichman wrote: > Begin forwarded message: > >> From: "Basil Kanneth" >> Date: August 29, 2019 at 11:01:57 AM EDT >> To: "Joseph Reichman" >> Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend >> >> Hi Joseph, >> >> It turns out the system protection exception occurred because of a missing >> semicolon after the following line in the code: >> typedef int (DLL_FN)(char *) >> >> So it should be: >> typedef int (DLL_FN)(char *); >> >> If you make the above changes, your test case should compile fine. >> >> We agree the compiler should not abend in this situation and we are >> investigating a potential fix. >> >> I will provide you with another update by Thursday, September 5th, 2019. >> >> Regards, >> >> Basil Kanneth, PMP® >> IBM XL C,C++, Fortran & COBOL Compilers Service Team IBM Software >> Group - Toronto Lab The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
I saw one as lab assistant. The bright young thing came tromping in 'the eight's broken, I need it fixed'. Turns out she was right! The adder's carry bit wasn't propagating. 3+3=6, 3+4=7, 4+4=7? Whoa nelly call the CE. In a message dated 8/29/2019 3:16:16 PM Central Standard Time, t...@tombrennansoftware.com writes: And I'm sure you can guess *exactly* how many of those times the system really turned out to be broken :) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
So many times I worked on a script or compiled/assembled code, got an error that made no sense, and then complained to anyone who would listen, "The system is obviously broken". And I'm sure you can guess *exactly* how many of those times the system really turned out to be broken :) On 8/29/2019 10:27 AM, Joseph Reichman wrote: Begin forwarded message: From: "Basil Kanneth" Date: August 29, 2019 at 11:01:57 AM EDT To: "Joseph Reichman" Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend Hi Joseph, It turns out the system protection exception occurred because of a missing semicolon after the following line in the code: typedef int (DLL_FN)(char *) So it should be: typedef int (DLL_FN)(char *); If you make the above changes, your test case should compile fine. We agree the compiler should not abend in this situation and we are investigating a potential fix. I will provide you with another update by Thursday, September 5th, 2019. Regards, Basil Kanneth, PMP® IBM XL C,C++, Fortran & COBOL Compilers Service Team IBM Software Group - Toronto Lab From:"Joseph Reichman" To:"'Basil Kanneth'" Date: 08/29/2019 08:16 AM Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend Any updates thanks -- 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: Case TS002648607 (PMR 76523,082,000) - Compiler abend
I expected this to be a missing paren causing the S0C4 but a semicolon is surprising. Usually you get a confusing message for a missing semicolon. Notice that IBM says they will get back to you by Sept 5. You caused this guy extra work by declaring this a sev 1. I don't know about today but in the past, they were usually helpful without declaring an unnecessary sev 1. In the future, try sev 2 and only raise to a sev 1 if you really need it. Jon. On Thursday, August 29, 2019, 10:27:36 AM PDT, Joseph Reichman wrote: Begin forwarded message: > From: "Basil Kanneth" > Date: August 29, 2019 at 11:01:57 AM EDT > To: "Joseph Reichman" > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Hi Joseph, > > It turns out the system protection exception occurred because of a missing > semicolon after the following line in the code: > typedef int (DLL_FN)(char *) > > So it should be: > typedef int (DLL_FN)(char *); > > If you make the above changes, your test case should compile fine. > > We agree the compiler should not abend in this situation and we are > investigating a potential fix. > > I will provide you with another update by Thursday, September 5th, 2019. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > From: "Joseph Reichman" > To: "'Basil Kanneth'" > Date: 08/29/2019 08:16 AM > Subject: [EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > Any updates > > thanks > > -- 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: Case TS002648607 (PMR 76523,082,000) - Compiler abend
I always knew semi-colons were dangerous. Most people butcher their usage in grammar and now abends … who knows what mischief they will stir up next. Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On Aug 29, 2019, at 1:37 PM, Charles Mills wrote: > > Amazing! > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joseph Reichman > Sent: Thursday, August 29, 2019 10:27 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Begin forwarded message: > >> From: "Basil Kanneth" >> Date: August 29, 2019 at 11:01:57 AM EDT >> To: "Joseph Reichman" >> Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend >> >> Hi Joseph, >> >> It turns out the system protection exception occurred because of a missing >> semicolon after the following line in the code: >> typedef int (DLL_FN)(char *) >> >> So it should be: >> typedef int (DLL_FN)(char *); >> >> If you make the above changes, your test case should compile fine. >> >> We agree the compiler should not abend in this situation and we are >> investigating a potential fix. >> >> I will provide you with another update by Thursday, September 5th, 2019. >> >> Regards, >> >> Basil Kanneth, PMP® >> IBM XL C,C++, Fortran & COBOL Compilers Service Team >> IBM Software Group - Toronto Lab -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Found another instance of the same thing many years ago. I forget if it was COBOL-E or COBOL-F. A missing period caused the compiler to abend. Ah! The good old days. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, August 29, 2019 12:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend Amazing! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joseph Reichman Sent: Thursday, August 29, 2019 10:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend Begin forwarded message: > From: "Basil Kanneth" > Date: August 29, 2019 at 11:01:57 AM EDT > To: "Joseph Reichman" > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Hi Joseph, > > It turns out the system protection exception occurred because of a missing > semicolon after the following line in the code: > typedef int (DLL_FN)(char *) > > So it should be: > typedef int (DLL_FN)(char *); > > If you make the above changes, your test case should compile fine. > > We agree the compiler should not abend in this situation and we are > investigating a potential fix. > > I will provide you with another update by Thursday, September 5th, 2019. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team IBM Software > Group - Toronto Lab > > > > From:"Joseph Reichman" > To: "'Basil Kanneth'" > Date:08/29/2019 08:16 AM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > Any updates > > thanks > > -- 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 ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Amazing! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joseph Reichman Sent: Thursday, August 29, 2019 10:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend Begin forwarded message: > From: "Basil Kanneth" > Date: August 29, 2019 at 11:01:57 AM EDT > To: "Joseph Reichman" > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Hi Joseph, > > It turns out the system protection exception occurred because of a missing > semicolon after the following line in the code: > typedef int (DLL_FN)(char *) > > So it should be: > typedef int (DLL_FN)(char *); > > If you make the above changes, your test case should compile fine. > > We agree the compiler should not abend in this situation and we are > investigating a potential fix. > > I will provide you with another update by Thursday, September 5th, 2019. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > From:"Joseph Reichman" > To: "'Basil Kanneth'" > Date:08/29/2019 08:16 AM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > Any updates > > thanks > > -- 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
Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Begin forwarded message: > From: "Basil Kanneth" > Date: August 29, 2019 at 11:01:57 AM EDT > To: "Joseph Reichman" > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Hi Joseph, > > It turns out the system protection exception occurred because of a missing > semicolon after the following line in the code: > typedef int (DLL_FN)(char *) > > So it should be: > typedef int (DLL_FN)(char *); > > If you make the above changes, your test case should compile fine. > > We agree the compiler should not abend in this situation and we are > investigating a potential fix. > > I will provide you with another update by Thursday, September 5th, 2019. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > From:"Joseph Reichman" > To: "'Basil Kanneth'" > Date:08/29/2019 08:16 AM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > Any updates > > thanks > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Fwd: Case TS002648607 (PMR 76523,082,000) - Compiler abend
Begin forwarded message: > From: "Basil Kanneth" > Date: August 26, 2019 at 12:03:13 PM EDT > To: Joseph Reichman > Subject: RE: Case TS002648607 (PMR 76523,082,000) - Compiler abend > > Thanks Joseph. > So I'll go ahead and reduce it to a Sev2 then. Let me know if you have any > concerns with that. > > I'll follow-up by Wednesday otherwise. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > From:Joseph Reichman > To:Basil Kanneth > Date: 08/26/2019 11:44 AM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > No as you can have it please let me know > I need it to finish my project but I have other things to do > It’s a simple program surprised it has not come up before > > Thanks > > > > > On Aug 26, 2019, at 11:34 AM, Basil Kanneth wrote: > > Hi Joseph, > > To provide you with an update, I was able to reproduce the system protection > error in my USS environment as shown below. > I have opened an internal workitem for further investigation. > > May I know the reason for this being a Sev1 issue? Is this blocking a > deadline of some sort? > > $ xlC test.c > ERROR CCN3485 ./test.c:11Parameter declaration list is incompatible with > declarator for DLL_FN. > ERROR CCN3172 ./test.c:11Parameter type list for function DLL_FN contains > parameters without identifiers. > CEE3204S The system detected a protection exception (System Completion > Code=0C4). > From entry point dtFuncDeclarator::BeginNestedFunc(sFuncSymbol*) at > statement 729 at compile unit offset > +0510 at entry offset +0510 at address 283938A8. > FSUM3224 xlC: Fatal error in /usr/lpp/cbclib/xlc/exe/ccndrvr: signal 9 > received. > $ > > I'll follow-up by Wednesday, August 28th, 2019 otherwise. > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > From:Basil Kanneth/Toronto/IBM > To:Joseph Reichman > Date:08/24/2019 10:35 PM > Subject:Re: [EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > Hi Joseph, > > Thanks. Yes, I got the 3 files. > > I'll have a look on Monday and update you. > > Regards, > ____________ > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > > From:Joseph Reichman > To:Basil Kanneth > Date:08/24/2019 10:32 PM > Subject:[EXTERNAL] Re: Case TS002648607 (PMR 76523,082,000) - > Compiler abend > > > > It’s z/os 2.3 > > yeah ok you can get to it Monday > > Just let me know if you got my three files > > JCL, C code, and the abend > > Thanks > > > > > > On Aug 24, 2019, at 10:28 PM, Basil Kanneth wrote: > > Hi Joseph, > > I am Basil Kanneth from the Compiler Service Team and I have received the > subject case. > > I see that you are encountering a compile time system protection error for > the submitted test case. > > Can you please confirm which z/OS level you are compiling this on? > > Also, I noticed that this is marked as a Sev1 issue. May I know the reason? > Can this be looked at during regular business hours on Monday? > > Regards, > > Basil Kanneth, PMP® > IBM XL C,C++, Fortran & COBOL Compilers Service Team > IBM Software Group - Toronto Lab > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
