3 ms·
JCL isn't scary. Think environment variables plus shell scripting. I wager you didn't see it abused. I actually hold ignoble honor of reverse engineering and i
by le-mark 8y ago
JCL isn't scary. Think environment variables plus shell scripting.
I wager you didn't see it abused. I actually hold ignoble honor of reverse engineering and implementing a complete JCL parser, validated on a million line batch system. The most egregious thing I saw there was; there were a set of jobs that essentially processed tree data structures as flatfiles, by building flat files of sub trees and resubmitting themselves. I really lol'd when I saw that.
- DrScump 8y agoSomebody had an IEBGENER fetish, maybe? Speaking of ugly JCL, it was typical of my environment for production jobs to not bother with cosmetics and comments since changing anything was a manual process requiring either sitting at the keypunch or writing it out in character grid boxes for keypunch operators. This made meaningful comments rare and (when present) hard to find or read. When I redid all our jobs' JCL via ISPF, I could not only easily reformat it all for readability and clarity, but I described all the passable parameter switch options right in the JCL right in context.