)Why don't we just skip the JCL, and write our jobs in REXX? The two Here, here!! Actually, there is one thing that is critical to retiring JCL. It's a host command that allows a REXX program to list and wait for all it's datasets and their enqueues to be available. This is not trivial, so that's why no installation has taken it on. I don't know why IBM keeps shoe-horning new features with big astonishment factors into JCL. z/OS is the only major platform with a separate batch-only language.
Anyone want to write sn RFE? On 21 Jun 2018 9:48 pm, "Andrew Rowley" <and...@blackhillsoftware.com> wrote: On 22/06/2018 11:21 AM, Steve Smith wrote: > Why don't we just skip the JCL, and write our jobs in REXX? The two > main things JCL does, EXEC and DD, are just as easy in REXX, (call, > alloc) with a ton more flexibility. EXPORT, SET, IF, and symbols are > lipstick for a pig. I actually like JCL. One of the things it does so well that no-one even notices is allocation of resources. In a previous job I tried to write scripts on a unix system to try to fix tasks that had a tendency to open one file and then wait for another, where multiple tasks were deadlocking. This is so simple with JCL because you don't get one allocation until you get them all. The connection between program (DDNAME) and resources (dataset etc.) is nice too. In something like Rexx you need to pass the names as arguments (JCL is much better than one long command line) or hard code them. -- Andrew Rowley Black Hill Software +61 413 302 386 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
