On Fri, 12 Dec 2014 17:04:38 -0500, Rob Schramm wrote: > >Rob >On Dec 12, 2014 4:44 PM, "Nims,Alva John (Al)" <[email protected]> wrote: > >> So as you can see, syntax checking and substitution processing is >> different between SET and the PARM= >>
z/OS MVS JCL Reference SA23-1385-00 http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/iea3b6_Rules_for_coding_symbols_in_JCL.htm z/OS 2.1.0>z/OS MVS>z/OS MVS JCL Reference>Procedures and symbols>Using system symbols and JCL symbols>Coding symbols in JCL>Rules for coding symbols in JCL z/OS MVS JCL Reference SA23-1385-00 Note: JCL supports substringing of system symbols but not JCL symbols. Why make such a distinction? Substringing could be similarly valuable for JCL symbols. z/OS 2.1.0>z/OS MVS>z/OS MVS JCL Reference>Procedures and symbols>Using system symbols and JCL symbols>What are JCL symbols?>Defining and nullifying JCL symbols o Do not specify JCL symbols within other JCL symbols. The results can be unpredictable, especially if the imbedded JCL symbol is not previously defined. Are some of the suggestions earlier in this thread at risk for this? I have an RCF on this, pending resolution. z/OS 2.1.0>z/OS MVS>z/OS MVS JCL Reference>Procedures and symbols>Using system symbols and JCL symbols>Determining equivalent JCL>Coding symbols in apostrophes You can code symbols in apostrophes on 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. Why not resolve symbols wherever they appear, not merely on five particular parameters of two JCL statements? There's a value in consistency leading to easy assimilation by a novice, and brevity of the Reference Manual. ... The system treats a string beginning with an ampersand but not meeting these criteria as a literal sequence of characters. Thus the system does not substitute text for symbols and does not issue error messages. I would be delighted if, rather, the parser reported a reference to an undefined apparent symbol as a syntax error. Someone asked recently in this thread what I think of the design of MVS JCL. Guess. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
