Gil, I didn't mean to be unclear. I didn't have a successor in mind; I was thinking about updating and improving JCL itself. They've managed to add a few useful features without breaking old JCL code -- the IF and SET statements, I have in mind as examples -- but they can't afford to fix the syntax of the COND test (always a problem for me) without breaking those bazillions of lines I mentioned. A successor...sure, why not? Try it and see. Though I'd guess that momentum will keep JCL going for quite a few decades no matter how brilliant the next one will be.
--- Bob Bridges, [email protected], cell 336 382-7313 /* Rule One: If you pull into my driveway and honk you'd better be delivering a package, because you're sure as heck not picking anything up. -from "8 Rules for Dating my Daughter" by W Bruce Cameron */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Thursday, January 6, 2022 21:21 > That's a fallacy akin to asserting that Rexx or Python could not be adopted without invalidating bazillions of lines of existing Assembler code. JCL could coexist with its successor. --- On Thu, 6 Jan 2022 20:40:16 -0500, Bob Bridges wrote: > ..., and very few improvements can be made to it without invalidating > bazillions of lines of existing JCL code, ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
