On Sun, 1 Jul 2018 13:11:27 -0400, Hobart Spitz wrote: >)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? > Have you a realistic alternative? In one case, I was able to enumerate a superset of the DSNs I might want to allocate in a Rexx step. I added EXEC PGM=IEFBR14,COND=(0,LE) with DD statements for those at the end of the job just to avoid ENQ surprises. JCL automates the enumeration of the ENQs; DYNALLOC, a newcomer, doesn't play by the old rules.
I could envision an alternative to S99WTDSN, not requiring authorization, which would cause a wait unless that created a deadlock (recognizable as a cycle in the ENQ graph) and fail immediately if a deadlock was created. Still, lots of questions. Which job should fail? The newcomer to the party? Why? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
