On Thu, 6 Jan 2022 16:28:42 +0000, Jeremy Nicoll wrote: > ... >Absolutely. But what's a decent alternative to JCL? > o Forgo compatibility. Whip sockets were long ago removed from automobile dashboards. They are no longer mourned. (But provide a conversion tool.)
o Free-form input. No special treatment of column 72. (Think Rexx.) o Eliminate special cases of symbol substitution. Simply substitute for any instance of "&name[.]". Then report as an error any reference to an undefined symbol. Forgo re scan of text substituted for symbols. I find such rescan a PITA, never useful. (Think Rexx, not CLIST.) o Support overrides and refer backs to any supported depth of nested PROC calls. But are overrides needed? Might they all be replaced by symbol references? An override can modify an item that is not explicitly a parameter. Is that disciplined or chaotic language design? (Think CPP.) o SYSDSN ENQ is essential. Keep it. o Others? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
