("Yes" only if you haven't been following my posts.)
On Mon, 16 May 2016 08:51:08 -0700, Ed Jaffe wrote:
>
>Made the mistake more than once of placing the EXPORT statement *after*
>the SET statements. But, really it's only counterintuitive if you're
>used to UNIX-style export (as apparently we both are). Otherwise, it's
>just "the way it works..."
>
I got accustomed to the "the way [EXPORT] works." But then I was truly
astonished by:
// SET X=BEFORE
//SYSUT1 DD *,SYMBOLS=JCL
&X
// SET X=AFTER
versus (untested; my guess):
// SET A=BEFORE
// SET X=&A (JCL Ref. is fuzzy about validity of this. RCF submitted.)
//SYSUT1 DD SYMBOLS=JCL
&X
// SET A=AFTER
And:
//SYSUT1 DD *
// SET X=BEFORE
// DD *,SYMBOLS=JCL /* (JCL error here; documented.) */
&X
versus:
//SYSUT1 DD *
//SYSUT1 DD *
// SET X=BEFORE
// DD *,SYMBOLS=JCL /* (JCL syntax OK.) */
&X
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
