D'accord - and the next 'complaint' will be about that pesky machine code and how to get rid of it. Those who find JCL challenging argue that it is not needed. As Aesop's fox said, "the grape is sour." My ha'penny. CP
On 02/07/2018 19:41, Steve Smith wrote: > There appears to be a visceral urge in some to force others to conform to > their great vision of the new and better way (ergo DST). That isn't at all > necessary in this case (nor DST). Just do it. Yourself. Now, or whenever > you have the time. > > The simultaneous enqueue issue seems to be the biggest technical issue. I > see these possible solutions: > a) Use JCL... > b) Write a utility that will do it. > c) Avoid the need for it. > > JCL is not ever going away, and to interact with the system as it exists, > some JCL is going to be needed. A JOB card, an EXEC PGM=IRXJCL (a somewhat > ironic name), and //SYSEXEC DD. But that would be a generic template, > depending on what you need to do with JOB card parameters. > > Start small... you don't have to build Rome in one day, or boil the ocean. > > sas > > On Mon, Jul 2, 2018 at 2:26 PM, Paul Gilmartin < > [email protected]> wrote: > >> On Mon, 2 Jul 2018 11:10:31 -0700, Charles Mills wrote: >> >>> Oh my gosh, you would have to maintain JCL forever for that and a dozen >> other reasons. >>> BUT! Conceivably ... conceivably ... you might stabilize it and do >> everything new in Rexx going forward. >> If the replacement had a superset of JCL function, providing a >> JCL-to-replacement >> translation utility would allow discarding direct support for JCL. >> >>> -----Original Message----- >>> From: John Melcher, Jr >>> Sent: Monday, July 2, 2018 10:46 AM >>> >>> Once upon a time a LONG time ago this was a GUIDE requirement. It was >>> voted down due to the amount of automated systems that generated JCL. >>> You'd have to keep JCL, probably forever, because of those systems. >> -- gil >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
