On Wed, 6 Nov 2013 08:32:41 -0800, Jon Perryman wrote: >2. It is the only tool where we can easilyt segregate interactive versus long >running programs. This allows WLM give more resources to interactive users >because they are personally waiting. Sysprog's encourage it's use by setting >WLM such that a user get's less than batch priority when they use to many >resources. > How does WLM depend on JCL? Doesn't it work alike for TSO and UNIX sessions?
3. It allows you the ability to look at how a job is proceeding (SDSF). > "tail -f" allows monitoring any output file, not those arbitrarily designated as "spool" files. I find the entire distinction between "spool" files and other data sets artificial and obstructive. >4. It segregates output into job steps and DD's making it easier to find the >information you desire. Much more difficult to do in TSO. > Characteristic of the declarative as opposed to procedural nature of JCL, yes. >5. It has a job log which usually contains a summary of return codes to >quickly determine if anything failed. (IEFACTRT). > In a procedural scripting language, I can log what I want, in the format I want. And I truly wish I could direct the JES logs to UNIX files as an alternative to the "spool". -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
