+1 And easy for me to say but wouldn't it be trivial to fix? Just pull out the code that checks for unused symbols? No compatibility issues -- no one is conceivably COUNTING ON a JCL error in that situation.
Wasn't assembler the model for JCL? Assembler allows unreferenced fields. (Although interestingly my C++ compiler warns me about unused stack and formal parameter variables.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Thursday, February 14, 2019 11:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC >The start fails with a JCL error and IEFC657I THE SYMBOL xxxxx WAS NOT USED >for every single one of the symbols. > .. Tnat message has struck me as insane design since I first encountered it over 40 years ago. Completely backwards. What sane language designer would allow reference to an undefined symbol but fail definition a symbol with no references. (Perhaps a warning, not an error, on the latter would be a courtesy to the programmer.) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
