On Thu, 2 Dec 2021 20:15:29 +0000, Seymour J Metz wrote:
>> That doesn't work
>
>It should work with a shorter name:
>
Mutatis mutandis.
> Special characters and blanks
> : When a parameter value contains special characters or blanks, enclose
> the value in apostrophes. The enclosing apostrophes are not considered part
> of the value. For example:
> //SP2 SET PARM3='3400-6'
>
>> // SET Q=''''
>> // SET ACTIONVAR=&Q&ACTION&Q
>
>I beleibe that that will give you apostrophes in the value rather than
>delimiting ot.
>
I believe not.
On parameters that are not in the list, the system correctly resolves a
symbol
that is enclosed in apostrophes when the symbol is immediately preceded by
a symbol that is not enclosed in apostrophes. For example, both A and B are
substituted correctly in:
//DD1 DD &A'&B',DISP=OLD
I believe the "immediately" doesn't belong or is misleading.
The apostrophes, double apostrophes, and double ampersands seem to bee resolved
in a later scan; the double ampersands much later -- they still appear double in
the SUBSTITUTION JCL message but passed collapsed to the PGM.
>________________________________________
>From: Paul Gilmarti
>Sent: Thursday, December 2, 2021 12:37 PM
>
>That doesn't work:
><https://www.ibm.com/docs/en/zos/2.5.0?topic=jcl-coding-symbols-in-apostrophes>
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
