On Thu, 2 Dec 2021 14:59:30 -0400, Peter Relson wrote: >I am surprised at the vitriole regarding >IEFC657I THE SYMBOL xxx WAS NOT USED > >Every time I have seen that message it was because the proc creator (me) >screwed up (sometimes in a subtle way). > ... >Sure, one could ask for an option to "ignore" or "treat as warning" but if >you knew enough to include that option, wouldn't you just "fix" the proc >not to have extraneous unneeded stuff to help everyone not get confused? > The reference or absence of reference might be in an INCLUDE member, one of which refers to the symbol; another doesn't
//EXPORT SYMBOLS=* should imply a reference to every SYMBOL, JCL or parm.. >Asking for improvement in the detection of use of a proc symbol, such as >within the ParmDD SYSIN might be reasonable. It was implemented as it was >because it was practical to do so. And the limitation that exists can be >dealt with. It is not practical to have the system search through the Parm >DD if the Parm DD is not inline so could not be done "in general". What > Shouldn't you be discussing not just 'ParmDD", but any instream DD with the SYMBOLS= option such as BPXBATCH STDPARM or any SYSUT1? Substitution is performed only on instream data sets -- your "in general" is a red herring. >would you sacrifice our doing in order to accommodate? It is always fair >to ask; but it is also a requirement to understand that there are limited >resources to be parceled out among worthy causes. Maybe one could consider >an option such as "make a JCL symbol from every proc symbol, with some >naming convention" that could make it easier to use the symbols from the > Just do it! The "naming convention" should be "with the same name". Supporting proc symbols and JCL symbols with identical names but different values is inviting chaos. >... proc in a Parm DD without having to do extra stuff, possibly incorporating >"EXPORT SYMLIST=*" and the option (if needed) so that JCL symbols are >processed within Parm DD (such as the current SYMBOLS=JCLONLY). -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
