SET may not be in the list, but this text is quite clear: 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'
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [0000000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Thursday, December 2, 2021 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Trying to use long parm= in started task On Thu, 2 Dec 2021 20:37:01 +0000, Seymour J Metz wrote: >> I've further perused the JCL Ref. which seems to imply: >> // SET NULL='' >> // SET ACTVAR=&NULL'&ACTION' > >Not this? > > // SET NULL='' > // SET ACTVAR='&NULL.&ACTION' > No: On parameters that are not in the list, the system correctly resolves a symbol that is enclosed in apostrophes [only] when the symbol is immediately [? -- gil] preceded by a symbol that is *not* enclosed in apostrophes. SET is "not in the list". I hate JCL! >>>... >>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 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
