On Thu, 2 Dec 2021 11:48:11 -0800, Charles Mills wrote:
>Does
>
>// SET ACTVAR=&ACTION
>
>work? Or do you indeed need to quote &ACTION? (If you do, I heartily endorse
>@Gil's &Q trick. I have used that.)
>
Did I copy that from you?
It may fail ifi &ACTION contains an unbalanced apostrophe.
JCL sorely needs HLASM'S (DOUBLE bif) et al.
I've further perused the JCL Ref. which seems to imply:
// SET NULL=''
// SET ACTVAR=&NULL'&ACTION'
I hate JCL!
>-----Original Message-----
>From: Paul Gilmartin
>Sent: Thursday, December 2, 2021 9:37 AM
>
>On Thu, 2 Dec 2021 10:29:00 +0000, Seymour J Metz wrote:
>
>>I believe that the problem is a combination of an error in your JCL and an
>>error in the Converter. &ACTION is a symbolic parameter but not a symbol. Try
>>
>>// SET ACTIONVAR='&ACTION'
>>...
>That doesn't work:
><https://www.ibm.com/docs/en/zos/2.5.0?topic=jcl-coding-symbols-in-apostrophes>
>
>You can code symbols in apostrophes on [only --gil] the following keywords:
> The DD statement AMP parameter
> The DD statement PATH parameter
> The DD statement SUBSYS parameter
> The EXEC statement ACCT parameter
> The EXEC statement PARM parameter.
>
>Not SET. I believe the following works:
>
>// SET Q=''''
>// SET ACTIONVAR=&Q&ACTION&Q
>
>Is this well-documented?
>
>I hate JCL!
>
>Does "ACTIONVAR" have too many characters?
>
>>//PARMDD DD *,SYMBOLS=JCLONLY
>>SH /u/mqweb3/conf/ccc.sh aa &T2 x &ACTIONVAR y &ACTIONVAR z
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
