I love JCL (errr....at least I don't hate it quite as much as you). I guess I'm just used to it and its infrastructure, e.g. automatic SYSOUT archiving (admittedly beyond the scope of JCL itself, but based on JCL-specified SYSOUT to start with). Lots of other good options from you below for those yet to acquire a taste for it. I for one am very happy to have multi-line STDPARM which greatly increases the utility of BPXBATCH for me. JCL and shell scripts: best of both worlds if you do it right.
best regards, Peter On Tue, 1 Oct 2019 22:35:35 -0500, Paul Gilmartin <[email protected]> wrote: >On Tue, 1 Oct 2019 22:10:12 -0500, Peter Bishop wrote: > >>Thanks heaps. >> >Yaay! You're welcome. > >>Firstly, the inline 'no op' which is handy but needs care. >> >Oops! > >Other thoughts: > >BPXWUNIX supports DD:STDIN, DD:STDOUT, and DD:STDERR, for the >cost of a trivial Rexx driver. Then you get true multi-line code in >STDIN and comments work. But the FB80 afflicts you with trailing >blanks which interfere with continuation. > >(You can code such a Rexx driver instream and REPRO it into SYSEXEC, >or keep it in a library.) > >If you're using an editor such as ISPF that lets you insert binary >characters in hex, you can code: > SET NL='newline' >CHANGE 'newline' x'15' >... and use STDPARM SYMBOLS to insert linebreaks. You need >this only once, in a JCLLIB member. Code the &NL at the front >of each STDPARM line rather than the back to avoid leading blanks. > >I hate JCL! > >-- gil > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
