Well, in the early 1990s, my system had 1-2 hour delays on compiles. So while waiting, I wrote a clist to do the same thing. Allocate, error handling, and deallocate of a single file took about 30 lines, and a few iterations of debugging. So, once I had one file allocate, I went through all the files, executed the program, and deallocated, and proceeded with the next two steps. Got it working and would go get a new cup of coffee while it ran instead of having to wait.
On Tue, Aug 17, 2021 at 10:59 PM kekronbekron <[email protected]> wrote: > > Objectively, this has got to be madness. > Just look at the JCL that's being shoved into a horrid, horrid Python program. > ~200 lines to replace 18 lines of JCL. > > Oh.. and that's leaving aside the condescending tone about 'the old > mainframer'. > Whether a person wants to learn something or not (therefore choosing their > path) is up to them. > They don't need to be harassed/shamed about it. > Just because there were some people on mainframe forums consistently > harassing everyone with "check with your site's system programmer / RTFM / > etc.", it doesn't mean the woke folk need to return the favour by being > passive aggressive or insulting senior sysprogs for not wearing neon shorts > or whatever. > > If this is being paraded as simplification, now the mainframe is truly doomed. > > https://medium.com/theropod/the-journey-from-jcl-to-python-so-easy-even-an-old-mainframer-can-do-it-f088cc49366a > > - KB > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
