My only point was the SET wasn't needed the way I used symbols.  It's hardly any big deal if it's needed for  library PROCs.  The fact that there doesn't seem to be any obvious logical reason for it, is just one of things you take for granted with JCL.

Why don't we just skip the JCL, and write our jobs in REXX?  The two main things JCL does, EXEC and DD, are just as easy in REXX, (call, alloc) with a ton more flexibility.  EXPORT, SET, IF, and symbols are lipstick for a pig.

All you must keep in JCL is the JOB card, and a standard EXEC PGM=IRXJCL + SYSEXEC DD.  Everything else you can code in an actual programming language.

JCL is fun as a puzzle-solving activity (sometimes), but for busy people trying to get their work done, it's been a black cloud since 1964.  Even Fred P. Brooks said he didn't like it.

sas


On 6/21/2018 20:50, Paul Gilmartin wrote:
On Fri, 22 Jun 2018 10:34:54 +1000, Andrew Rowley 
<and...@blackhillsoftware.com> wrote:

On 21/06/2018 11:05 PM, Steve Smith wrote:
I've gotten good results with the EXPORT before the PROC
Which means the EXPORT needs to be in the calling job, not the PROC. My
examples used inline PROCs for convenience, but I was trying to do it
with a PROC in a PROCLIB. If the EXPORT needs to be before the PROC, the
job needs to know exactly which variables the PROC needs exported, which
negates some of the convenience of abstracting stuff into a PROC.

Does it not suffice to code EXPORT before SET, but in the PROC?
(But then are symbols exported to open code, outside the PROC?)

The best solution seems to be SET VAR=&VAR in the PROC.

Hardly practical if the vaue of VAR contains metacharacters.  JCL
sorely needs HLASM's DOUBLE BIF.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to