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
