Actually it is documented as well as using double ampersands for symbols 
(deferred usage) and the use of the ampersand as a part of the name.

Adam

Sent from my iPhone

> On Jun 9, 2018, at 11:24 AM, Ed Jaffe <edja...@phoenixsoftware.com> wrote:
> 
>> On 6/6/2018 8:51 AM, Steve Smith wrote:
>> This has been previously discussed.  The main issue (as usual) is
>> incompatibility with an ancient bug (or feature).  Specifically, temporary
>> dataset names such as DSN=&TMP.  That's supposed to be DSN=&&TMP, but for
>> whatever reason, the single-& version works, unless &TMP is a symbol.
> 
> Wow! I confirmed this is an exposure! I never knew!
> 
> IBM does not mention the single ampersand being valid temporary data set name 
> syntax in the description of the DSNAME parameter on the DD statement and I 
> have previously not seen it used that way. 
> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieab600/iea3b6_Syntax25.htm
> 
> This reminds me of the rule in REXX where use of an uninitialized variable 
> results in the variable name itself being substituted. But, that is 
> documented behavior. This is just plain wrong.
> 
> It might be a good use of the common tracker component (GTZ) to help identify 
> JCL with such errors. Otherwise, every new symbol added -- to the system, to 
> a proc, to anything that might have visibility to a job stream -- can lead to 
> unexpected JCL errors.
> 
> -- 
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> http://www.phoenixsoftware.com/
> --------------------------------------------------------------------------------
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
> 
> ----------------------------------------------------------------------
> 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

Reply via email to