Re: Use of dynamic system symbols in JCL

[Seymour J Metz]

Single ampersand is correct for temporary dataset names. With the advent of 
symbolic parameters circq OS/360 R14, double ampersand became valid as a symbol 
that expanded to a single ampersand.

\\fooPROC  bar=baz
...
\\SYSUT1   DD  DSN=&&

should request the temporary  I'd be interested to see if that actually 
works.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of Tom 
Brennan 
Sent: Saturday, June 9, 2018 5:25 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

And I'm one of the perpetrators!  For a long time I thought the single
asterisk was proper and whenever I saw the double I assumed it was a
mistake that just happened to work.

Tom Conley wrote:
> On 6/9/2018 2:24 PM, Ed Jaffe 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=  That's supposed to be DSN=&, but
>>> for
>>> whatever reason, the single-& version works, unless  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://secure-web.cisco.com/17SostiwRF4glBwCbQGN00grlR4ZOVHRcF4WVEacpIKb5xpeZmW91ak-fwttTKazaMniGXJ-IXbDupio6X8Nx94ypSi9sOeZVkacHTyBQHA2cA4UpVSxGby7BZF852syZg-h34iZQ9y_4I1Pb6LBYktA73idbRjCjVjU7TU85rUBE2mFzNVg_VRN3y8KMDuOcIpvWtd4ggTzTNEnqw7K6nC6VeSMOgaZ6ukq4PIQ0U4M_25EQ2sauzAnBaRlBeDPpD9_ZFZOenKK2YL7ADvuCzGxfOu_g20LqMi3l-Nm5XXEZIQ22ugCUPP5Wism7Z0jSHAIj4VTKqEvC9S-6eEMmg9KMldgxuM2KYW_7W7meV8y-pnSUjza6HY9-bpM53UZL_iVNqgmBW6wLgYxyCw9V303VSJgG7UsgYNsa1daV0b6ssG99i3py_XcAjA-fNZqS/https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.3.0%2Fcom.ibm.zos.v2r3.ieab600%2Fiea3b6_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.
>>
>
> That's not a bug, that's a FEATURE!
>
> --
> 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Seymour J Metz]

> What happens if JCL performs symbol substitution? 

I would expect that to be a valid temporary reference.

> R21.7 and later say use DSNAME=&dsname.

WTF is your e-mail clients doing with ampersands? It looks like it's trying to 
convert one of them to HTML but not the other. IAC, & evaluates to 
, which is a valid temporary as long as dsname adheres to the 
restrictions.

> //  SET A2='&TEMP'

I would expect that to be an invalid temporary reference.

> There's been enough confusion among experts in this forum that a clarifying
> RCF seems appropriate. 

Couldn't hurt.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Saturday, June 9, 2018 7:05 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
><http://secure-web.cisco.com/1kbHbNN0Khz9T3NKrHFBWAGWSoKIBMQnYXJseeVQHqjXS8-xUb-G0_5SLGhHTgA68rVUPiucTOurQKMSrP9eBk0Sgo1MuHBA1Zj3lUhEnNXbYxitjpcvCkIwegGS6YTGp6F98tjynb77DwL8zUphSE8QYnyaOLQHaYshouOuiCZM3fnpRn2P0MfAe--4Go1zNm15H6W1PN1M_ysAt1Adhj_S_wUV3yg4tD-UGRs0k5ZTNmuupQOg092x9HtPo8WYb-O2HSPBD0dsjZA9hTAmYYgRwLWJfiyCdlKIhjqkfDfyArSOQJm3_VOWko72uzEQ4Vm-qt_eNdcJ_Kp4rw4VlgdVnzmJjFUmyAK-RqIpnym3a7mI4ER7PJwr7Lsm6hCGSOuY1Hk0Nqr1hiw-RxX76smTjfzCEmE7Xlk2AUVlhCFqDetoED0LwXdG1mrbGWl8Y/http%3A%2F%2Fbitsavers.org%2Fpdf%2Fibm%2F360%2Fos%2FR01-08%2FC28-6539-4_OS_JCL_Mar67.pdf>
>
OK.  That says use DSNAME=  R21.7 and later say use DSNAME=&dsname.
What happens if JCL performs symbol substitution?  For example

//  SET A1=''
//  SET A2='&TEMP'
//*
//STEP  EXEC  PGM=IEFBR14
//D1  DD  DSN=   * Should be unsupported; only one ampersand after 
substitution.
//D1  DD  DSN=   * Should be accepted; two ampersands after substitution.

There's been enough confusion among experts in this forum that a clarifying
RCF seems appropriate.  The existing doc antedates and takes scant account of
symbol substitution

-- 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

Re: Use of dynamic system symbols in JCL

[Gerhard Adam]

I don't see what the issue is.  It simply says that if you code a DSN as a 
symbol and it is not resolved, then the symbol name itself becomes the 
temporary DSN

I'm not clear on why anyone would care about this behavior?

Sent from my iPhone

> On Jun 10, 2018, at 2:15 PM, Paul Gilmartin 
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> 
>> On Sat, 9 Jun 2018 16:13:34 -0700, Gerhard Adam  wrote:
>> 
>> This is the JCL Reference for z/OS 2.3 (page 183)
>> 
>> Note:
>> 1. In general, the system treats a single ampersand (&) followed by a 
>> character string of 1 to 8 characters as a symbolic parameter. (See “Using 
>> system symbols and JCL symbols” on page 38.) However, if you code a data set 
>> name as a symbolic parameter (by coding DSNAME=), and do not assign 
>> a value to or nullify the symbolic parameter, the system will process it as 
>> a temporary data set name.
> Yes.  Thanks.  And the previous page, Op. cit. 182:
> 
> Data set name for temporary data set
>...
> When you use DSNAME for a temporary data set, code the name as two ampersands 
> (&) followed by a character string 1 to 8 characters in length:
> o The first character following the ampersands must be alphabetic or 
> national..
> o The remaining characters must be alphanumeric or national.
> The more I think about this, the less I like it.  The Ref. gives a couple 
> examples
> in lieu of a formal rule, leaving it to the clever reader to infer that rule. 
>  There's
> been much stumbling toward that ojective in this thread with statements such
> as, "This seems to work, but I can't tell why."
> 
> Rather, I'd omit the "Note:" as quoted.  That information appears elswhere 
> the Ref.
> and needn't appear redundantly here.  Rather, page 182 should say:
> 
> Data set name for temporary data set
>...
> When you use DSNAME for a temporary data set, the equivalent JCL after symbol
> substitution (as described on page 45, "Determining equivalent JCL") should be
> a single ampersand (&) followed by a character string 1 to 8 characters in 
> length:
> o The first character following the ampersands must be alphabetic or national.
> o The remaining characters must be alphanumeric or national.
> 
> This covers cases not currently described such as:
>//  SET TEMP='Who cares, anyway?'
>//  SET TTT=''
>//SYSUT2  DD  DSN=,...
> 
> -- 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

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Sat, 9 Jun 2018 16:13:34 -0700, Gerhard Adam  wrote:
>
>This is the JCL Reference for z/OS 2.3 (page 183)
>
>Note:
>1. In general, the system treats a single ampersand (&) followed by a 
>character string of 1 to 8 characters as a symbolic parameter. (See “Using 
>system symbols and JCL symbols” on page 38.) However, if you code a data set 
>name as a symbolic parameter (by coding DSNAME=), and do not assign a 
>value to or nullify the symbolic parameter, the system will process it as a 
>temporary data set name.
> 
Yes.  Thanks.  And the previous page, Op. cit. 182:

Data set name for temporary data set
...
When you use DSNAME for a temporary data set, code the name as two ampersands 
(&) followed by a character string 1 to 8 characters in length:
o The first character following the ampersands must be alphabetic or national..
o The remaining characters must be alphanumeric or national.
>
The more I think about this, the less I like it.  The Ref. gives a couple 
examples
in lieu of a formal rule, leaving it to the clever reader to infer that rule.  
There's
been much stumbling toward that ojective in this thread with statements such
as, "This seems to work, but I can't tell why."

Rather, I'd omit the "Note:" as quoted.  That information appears elswhere the 
Ref.
and needn't appear redundantly here.  Rather, page 182 should say:

Data set name for temporary data set
...
When you use DSNAME for a temporary data set, the equivalent JCL after symbol
substitution (as described on page 45, "Determining equivalent JCL") should be
a single ampersand (&) followed by a character string 1 to 8 characters in 
length:
o The first character following the ampersands must be alphabetic or national.
o The remaining characters must be alphanumeric or national.

This covers cases not currently described such as:
//  SET TEMP='Who cares, anyway?'
//  SET TTT=''
//SYSUT2  DD  DSN=,...

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Gerhard Adam]

Sure.  From the JCL manual; DSNAME parameter

This is the JCL Reference for z/OS 2.3 (page 183)

Note:
1. In general, the system treats a single ampersand (&) followed by a character 
string of 1 to 8 characters as a symbolic parameter. (See “Using system symbols 
and JCL symbols” on page 38.) However, if you code a data set name as a 
symbolic parameter (by coding DSNAME=), and do not assign a value to 
or nullify the symbolic parameter, the system will process it as a temporary 
data set name.

Adam

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ed Jaffe
Sent: Saturday, June 9, 2018 3:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

On 6/9/2018 2:49 PM, Gerhard Adam wrote:
> 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.

Citation, please...

--
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

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
>
>
OK.  That says use DSNAME=  R21.7 and later say use DSNAME=&dsname.
What happens if JCL performs symbol substitution?  For example

//  SET A1=''
//  SET A2='&TEMP'
//*
//STEP  EXEC  PGM=IEFBR14
//D1  DD  DSN=   * Should be unsupported; only one ampersand after 
substitution.
//D1  DD  DSN=   * Should be accepted; two ampersands after substitution.

There's been enough confusion among experts in this forum that a clarifying
RCF seems appropriate.  The existing doc antedates and takes scant account of
symbol substitution

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Tom Brennan]

Ampersand, not asterisk!
Eating hamburger while typing.  Yes that's my excuse.

Tom Brennan wrote:
And I'm one of the perpetrators!  For a long time I thought the single 
asterisk was proper and whenever I saw the double I assumed it was a 
mistake that just happened to work.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Sat, 9 Jun 2018 15:02:31 -0700, Ed Jaffe wrote:

>On 6/9/2018 2:49 PM, Gerhard Adam wrote:
>> 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.
>
>Citation, please...
> 
I'm lost.  Neither Ed's ply nor Adam's informs me clearly of the antecedent of 
"it".
Does Shmuel's citation help:

On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
>
>
(See Page 23.  There were *no* symbols in JCL then!)

[1116 bytes of lawyer crap snipped!]

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Sat, 9 Jun 2018 14:25:56 -0700, Tom Brennan wrote:

>And I'm one of the perpetrators!  For a long time I thought the single
>asterisk was proper and whenever I saw the double I assumed it was a
>mistake that just happened to work.
> 
No, conventional behavior nowadays.  JCL collapses a double ampersand to
a single, but supprsses symbol substitution.

>>> 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=  That's supposed to be DSN=&TMP, but 
 for
 whatever reason, the single-& version works, unless  is a symbol.
>>>
Aboriginal behavior:
On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
>
>
(See Page 23.  There were *no* symbols in JCL then!)

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Ed Jaffe]

On 6/9/2018 2:49 PM, Gerhard Adam wrote:

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.


Citation, please...

--
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

Re: Use of dynamic system symbols in JCL

[Gerhard Adam]

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  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=  That's supposed to be DSN=&, but for
>> whatever reason, the single-& version works, unless  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

Re: Use of dynamic system symbols in JCL

[Tom Brennan]

And I'm one of the perpetrators!  For a long time I thought the single 
asterisk was proper and whenever I saw the double I assumed it was a 
mistake that just happened to work.


Tom Conley wrote:

On 6/9/2018 2:24 PM, Ed Jaffe 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=  That's supposed to be DSN=&, but 
for

whatever reason, the single-& version works, unless  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.




That's not a bug, that's a FEATURE!

--
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

Re: Use of dynamic system symbols in JCL

[Tom Conley]

On 6/9/2018 2:24 PM, Ed Jaffe 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=  That's supposed to be DSN=&, but for
whatever reason, the single-& version works, unless  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.




That's not a bug, that's a FEATURE!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Jesse 1 Robinson]

One modest step we take to avoid conflicts is to prefix installation-defined 
symbols with our SHARE installation code. That does not guarantee uniqueness, 
but no ISV is likely to stumble in, and I've never seen a production proc 
symbolic like that. This practice shortens the string of 'meaningful' 
characters, but programmers are a wily tribe. 

Alternatively, a single national character prefix would likely ensure 
uniqueness as well. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Ed Jaffe
Sent: Saturday, June 09, 2018 11:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Use of dynamic system symbols in JCL

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=  That's supposed to be 
> DSN=&, but for whatever reason, the single-& version works, unless  
> 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/


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Ed Jaffe]

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=  That's supposed to be DSN=&, but for
whatever reason, the single-& version works, unless  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

Re: Use of dynamic system symbols in JCL

[Steve Coalbran]

TITUTION JCL - CNMVER=Y
000164   IEFC653I SUBSTITUTION JCL - CNMVOL=Z51YP1
000166   IEFC653I SUBSTITUTION JCL - COMCEC=C
000168   IEFC653I SUBSTITUTION JCL - COMMSUF=00
000170   IEFC653I SUBSTITUTION JCL - COMODE=R
000172   IEFC653I SUBSTITUTION JCL - COUNTRY=SE
000174   IEFC653I SUBSTITUTION JCL - DB2VER=d
000176   IEFC653I SUBSTITUTION JCL - HRDWNAME=CE32CB
000178   IEFC653I SUBSTITUTION JCL - ICSFPROG=CSFINIT
000180   IEFC653I SUBSTITUTION JCL - IMSLVL=RSU1703
000182   IEFC653I SUBSTITUTION JCL - IMTOOLVL=V002
000184   IEFC653I SUBSTITUTION JCL - JESSVOL=SPL06
000186   IEFC653I SUBSTITUTION JCL - JES2APPL=SENBNJE0
000188   IEFC653I SUBSTITUTION JCL - JES2NODE=SENBSU0
000190   IEFC653I SUBSTITUTION JCL - LFM1MB=
000192   IEFC653I SUBSTITUTION JCL - LFT1MB=2000
000194   IEFC653I SUBSTITUTION JCL - LOC=V
000196   IEFC653I SUBSTITUTION JCL - LPARNAME=LP3206
000198   IEFC653I SUBSTITUTION JCL - MASMEM=2
000198   IEFC653I SUBSTITUTION JCL - MASMEM=2
000200   IEFC653I SUBSTITUTION JCL - MQEXIT=01
000202   IEFC653I SUBSTITUTION JCL - MQLVL=800C
000204   IEFC653I SUBSTITUTION JCL - MST1=0020
000206   IEFC653I SUBSTITUTION JCL - OM=22
000208   IEFC653I SUBSTITUTION JCL - OSLEVEL=020200
000210   IEFC653I SUBSTITUTION JCL - PLEXID=UP
000212   IEFC653I SUBSTITUTION JCL - PLPASUF=00
000214   IEFC653I SUBSTITUTION JCL - PLX=51
000216   IEFC653I SUBSTITUTION JCL - RMFOPT1=
000218   IEFC653I SUBSTITUTION JCL - SMFID=MVS0
000220   IEFC653I SUBSTITUTION JCL - SYSCAT=UCATUP
000222   IEFC653I SUBSTITUTION JCL - SYSNBR=0
000224   IEFC653I SUBSTITUTION JCL - SYSR2=Z51YP1
000226   IEFC653I SUBSTITUTION JCL - USRPLEX=PLEX51
000228   IEFC653I SUBSTITUTION JCL - USRTADZ=ENSH
000230   IEFC653I SUBSTITUTION JCL - USSROOT=Z51YP1
000232   IEFC653I SUBSTITUTION JCL - VMUSERID=+
000234   IEFC653I SUBSTITUTION JCL - ZVER=Y
000236   //*--- END SYM ---
000237   //*
000238   //*--- JOB JCL ---
...JCL resolved from job...

Un-shown lines are there but eXcluded with a HIDE X.

All of these symbols one can see are available to JCL interpretation?





From: IBM Mainframe Discussion List  on behalf of 
Lizette Koehler 
Sent: 06 June 2018 22:17
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

Just in case it was not mentioned,

If you have scheduling software, you might be able to get what you want.

Or you can write a rexx to create the JCL with what you want.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Sean Gleann
> Sent: Wednesday, June 06, 2018 7:27 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Use of dynamic system symbols in JCL
>
> Can anyone point out what I'm doing wrong here, please?
>
>
> I'm trying to create a file with a name that features today's date.
> My statement is:
> //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
>
> When I submit the job to the system, I get:
>
> IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
>
> I've tried numerous variants of this statement, but I always get the same
> failure.
> I'm almost certainly doing something stupid, but right now I can't see the
> wood for the trees...
>
>
> Help...  Please...
>
> Sean Gleann
>
> --
> 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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Steve Horein]

Thanks!
I commented out that statement and got the same results to see with my own
eyes.
I also missed Sean's confirmation that "all is well" based on jobclass
updates.

On Thu, Jun 7, 2018 at 2:34 PM Peter Hunkeler  wrote:

> >Are you specifying "EXPORT SYMLIST" in your JCL?
>
>
> That one is not needed for system symbols to become available in batch
> JCL. It the jobclass SYSSYM=ALLOW | DISALLOW that decides. BTW, the symbols
> are resolved at conversion time.
>
>
> The EXPORT SYMLIST is needed so that JCL symbols can be used on // DD *
> data. You also need SYMBOLS=JCLONLY | CNVTSYS | EXECSYS on the DD *
> statement. The later two enable system symbol replacement in DD * data
> irrespective of the SYSSYM= setting on the jobclass (IIRC).
> --
> Peter Hunkeler
>
> --
> 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

Re: Use of dynamic system symbols in JCL

[Peter Hunkeler]

>Are you specifying "EXPORT SYMLIST" in your JCL?


That one is not needed for system symbols to become available in batch JCL. It 
the jobclass SYSSYM=ALLOW | DISALLOW that decides. BTW, the symbols are 
resolved at conversion time.


The EXPORT SYMLIST is needed so that JCL symbols can be used on // DD * data. 
You also need SYMBOLS=JCLONLY | CNVTSYS | EXECSYS on the DD * statement. The 
later two enable system symbol replacement in DD * data irrespective of the 
SYSSYM= setting on the jobclass (IIRC).
--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Thu, 7 Jun 2018 12:51:52 +, Allan Staller wrote:

>No impact unless you happen to have conflicting symbols.
> 
That shouldn't matter.  If CA7 substitutes a symbol, downstream processors
will never see it as a symbol.  However if CA7 does not perform a substitution
it's exposed for SYSSYM substitution.

>-Original Message-
>From: Beesley, Paul
>Sent: Thursday, June 7, 2018 2:27 AM
>
>Yes, we've only just turned it on in a couple of test systems.
>My concern is what impact it will have on systems where the job scheduler does 
>its own symbolic substitution (e.g.CA7) and I will follow this thread with 
>interest

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Allan Staller]

No impact unless you happen to have conflicting symbols.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Beesley, Paul
Sent: Thursday, June 7, 2018 2:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

Yes, we've only just turned it on in a couple of test systems.
My concern is what impact it will have on systems where the job scheduler does 
its own symbolic substitution (e.g.CA7) and I will follow this thread with 
interest

Paul

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jousma, David
Sent: Wednesday, June 06, 2018 4:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

Is anyone else pushing back on turning on batch system symbol support?   We've 
yet to do so, for the very reasons that IBM hadn’t supported in batch all 
along.  My main concern is unpredictable results.

Am I worrying for nothing?

_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H p 616.653.8429 f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Yep, need to make sure SYSSYM=ALLOW for that jobclass,



CLASS og XBMProc DupJob JobRC Active SysSym
1 PIN) NO MAXRC YES ALLOW
2 PIN) NO MAXRC YES ALLOW




in a STC I run at IPL time I do about the same



//CLEAN EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *,SYMBOLS=EXECSYS
DEL 'ATTS.PROD.'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG),
// UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE),
// RECFM=FBA,LRECL=134,BLKSIZE=0
//SYSTSIN DD DUMMY
//*
//IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=SYS1.
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC 



Carmen Vitullo

- Original Message -

From: "Andrew Arentsen" 
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, June 6, 2018 9:43:25 AM
Subject: Re: Use of dynamic system symbols in JCL

In my JES2PARM, in the definition of the job class that I'd run this job in, I 
specify SYSSYM=ALLOW. I'm sure you could put this in dynamically with a $T of 
some sort. You'll also need the two periods as Rob stated.

Andrew Arentsen
Senior Mainframe Systems Engineer




From: "Sean Gleann" 
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 06/06/2018 09:35 AM
Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM Mainframe 
Discussion List" 



I understand what you're saying Rob, but that was one of the variants I tried. 
It still produces the same error

Sean

On 6 June 2018 at 15:29, Rob Schramm  wrote:

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters
>
> Rob
>
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
>
> > Can anyone point out what I'm doing wrong here, please?
> >
> >
> > I'm trying to create a file with a name that features today's date.
> > My statement is:
> > //OUTFILE DD DSN=BACKUP.USERDALY.D,
> > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> >
> > When I submit the job to the system, I get:
> >
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> >
> > I've tried numerous variants of this statement, but I always get the
same
> > failure.
> > I'm almost certainly doing something stupid, but right now I can't
> > see
> the
> > wood for the trees...
> >
> >
> > Help... Please...
> >
> > Sean Gleann
> >
> > 
> > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO
> > IBM-MAIN
> >
> --
>
> Rob Schramm
>
> --
> 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


*

Re: Use of dynamic system symbols in JCL

[Steve Horein]

I used this JCL:
//
//*
//SYMBOLS  EXPORT SYMLIST=*
//STEP1EXEC PGM=IEFBR14
//*
//ISUP DD   DISP=(NEW,CATLG),
// DSN=SH71167.IS.ACTIVE.ON.,
// SPACE=(TRK,(0,1)),
// LRECL=133,BLKSIZE=1330,RECFM=FB,
// VOL=SER=,
// UNIT=SYSDA

And got these results:
IEF236I ALLOC. FOR SH71167T STEP1
IGD101I SMS ALLOCATED TO DDNAME (ISUP)
DSN (SH71167.IS.ACTIVE.ON.CP9S.D180607   )
STORCLAS (PERF1) MGMTCLAS (TMAMLYBW) DATACLAS ()
VOL SER NOS= SH9DAU
IEF142I SH71167T STEP1 - STEP WAS EXECUTED - COND CODE 

Are you specifying "EXPORT SYMLIST" in your JCL?

On Wed, Jun 6, 2018 at 9:26 AM Sean Gleann  wrote:

> Can anyone point out what I'm doing wrong here, please?
>
>
> I'm trying to create a file with a name that features today's date.
> My statement is:
> //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
>
> When I submit the job to the system, I get:
>
> IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
>
> I've tried numerous variants of this statement, but I always get the same
> failure.
> I'm almost certainly doing something stupid, but right now I can't see the
> wood for the trees...
>
>
> Help...  Please...
>
> Sean Gleann
>
> --
> 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

Re: Use of dynamic system symbols in JCL

[R.S.]

The problem is you cannot use it in batch job. The documentation is 
*incorrect* - among many "working" symbols it provides few actually not 
working.
Simple test: copy all of the symbols to a job, make DSN=  
etc. Don't worry about DSNname syntax. Then submit the job with 
TYPRUN=SCAN and watch the output. You will see which symbols were 
substituted and which symbols left unrecongnized.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 2018-06-06 o 16:26, Sean Gleann pisze:

Can anyone point out what I'm doing wrong here, please?


I'm trying to create a file with a name that features today's date.
My statement is:
//OUTFILE DD   DSN=BACKUP.USERDALY.D,
//  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
//  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024

When I submit the job to the system, I get:

IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD

I've tried numerous variants of this statement, but I always get the same
failure.
I'm almost certainly doing something stupid, but right now I can't see the
wood for the trees...


Help...  Please...


==


   --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych.
   


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Vernooij, Kees (ITOPT1) - KLM]

I look at 'd symbols', but that only displays static symbols.
SDSF shows me all the symbols and these are there too.

Thanks,
Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Beesley, Paul
> Sent: 07 June, 2018 9:23
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
> 
> It's in my 2.1 system
> 
> Symbol Value  Type
>   2018   Dynamic
>180607 Dynamic
> 
> Paul
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Thursday, June 07, 2018 7:04 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
> 
> Hi Sean,
> It is not in my 2.2 system. Are you at 2.3?
> 
> Kees.
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Sean Gleann
> > Sent: 06 June, 2018 16:40
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Use of dynamic system symbols in JCL
> >
> > Hi Kees
> >
> > "Have I defined it"?In a SET statement you mean?
> > I didn't think you had to, LYYMMDD is a system-defined dynamic symbol,
> > isn't it?
> >
> > Sean
> >
> > On 6 June 2018 at 15:36, Vernooij, Kees (ITOPT1) - KLM <
> > kees.verno...@klm.com> wrote:
> >
> > > I only get this error if the variable has not been defined. Have you
> > > defined it?
> > >
> > > Kees.
> > >
> > >
> > > > -Original Message-
> > > > From: IBM Mainframe Discussion List [mailto:IBM-
> > m...@listserv.ua.edu] On
> > > > Behalf Of Rob Schramm
> > > > Sent: 06 June, 2018 16:29
> > > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > > Subject: Re: Use of dynamic system symbols in JCL
> > > >
> > > > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> > > >
> > > > Rob
> > > >
> > > > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann 
> > wrote:
> > > >
> > > > > Can anyone point out what I'm doing wrong here, please?
> > > > >
> > > > >
> > > > > I'm trying to create a file with a name that features today's
> > date.
> > > > > My statement is:
> > > > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > > > >
> > > > > When I submit the job to the system, I get:
> > > > >
> > > > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > > > >
> > > > > I've tried numerous variants of this statement, but I always get
> > the
> > > > same
> > > > > failure.
> > > > > I'm almost certainly doing something stupid, but right now I
> > > > > can't
> > see
> > > > the
> > > > > wood for the trees...
> > > > >
> > > > >
> > > > > Help...  Please...
> > > > >
> > > > > Sean Gleann
> > > > >
> > > > > 
> > > > > --
> > 
> > > > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > > > send email to lists...@listserv.ua.edu with the message: INFO
> > > > > IBM-
> > MAIN
> > > > >
> > > > --
> > > >
> > > > Rob Schramm
> > > >
> > > > --
> > > > --
> > --
> > > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-
> > MAIN
> > > 
> > > For information, services and offers, please visit our web site:
> > > http://www.klm.com. This e-mail and any attachment may contain
> > > confidential and privileged material intended for the addressee
> only.
> > If
> > > you are not the addressee, you are notified that no part of the
> > > e-mail
> > or
> > > any attachment may be disclosed, copied or distributed, and that any
> > other

Re: Use of dynamic system symbols in JCL

[Beesley, Paul]

Yes, we've only just turned it on in a couple of test systems.
My concern is what impact it will have on systems where the job scheduler does 
its own symbolic substitution (e.g.CA7) and I will follow this thread with 
interest

Paul

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jousma, David
Sent: Wednesday, June 06, 2018 4:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

Is anyone else pushing back on turning on batch system symbol support?   We've 
yet to do so, for the very reasons that IBM hadn’t supported in batch all 
along.  My main concern is unpredictable results.

Am I worrying for nothing?

_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H p 616.653.8429 f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Yep, need to make sure SYSSYM=ALLOW for that jobclass,



CLASS og XBMProc DupJob JobRC Active SysSym
1 PIN) NO MAXRC YES ALLOW
2 PIN) NO MAXRC YES ALLOW




in a STC I run at IPL time I do about the same



//CLEAN EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *,SYMBOLS=EXECSYS
DEL 'ATTS.PROD.'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG),
// UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE),
// RECFM=FBA,LRECL=134,BLKSIZE=0
//SYSTSIN DD DUMMY
//*
//IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=SYS1.
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC 



Carmen Vitullo

- Original Message -

From: "Andrew Arentsen" 
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, June 6, 2018 9:43:25 AM
Subject: Re: Use of dynamic system symbols in JCL

In my JES2PARM, in the definition of the job class that I'd run this job in, I 
specify SYSSYM=ALLOW. I'm sure you could put this in dynamically with a $T of 
some sort. You'll also need the two periods as Rob stated.

Andrew Arentsen
Senior Mainframe Systems Engineer




From: "Sean Gleann" 
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 06/06/2018 09:35 AM
Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM Mainframe 
Discussion List" 



I understand what you're saying Rob, but that was one of the variants I tried. 
It still produces the same error

Sean

On 6 June 2018 at 15:29, Rob Schramm  wrote:

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters
>
> Rob
>
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
>
> > Can anyone point out what I'm doing wrong here, please?
> >
> >
> > I'm trying to create a file with a name that features today's date.
> > My statement is:
> > //OUTFILE DD DSN=BACKUP.USERDALY.D,
> > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> >
> > When I submit the job to the system, I get:
> >
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> >
> > I've tried numerous variants of this statement, but I always get the
same
> > failure.
> > I'm almost certainly doing something stupid, but right now I can't
> > see
> the
> > wood for the trees...
> >
> >
> > Help... Please...
> >
> > Sean Gleann
> >
> > 
> > -- For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO
> > IBM-MAIN
> >
> --
>
> Rob Schramm
>
> --
> 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


**
This e-mail is confidential. If you are not the intended recipient, you must 
not disclose or use the information contained in it. If you have received this 
e-mail in error, please tell us immediately by return e-mail and delete the 
document.

-

Re: Use of dynamic system symbols in JCL

[Beesley, Paul]

It's in my 2.1 system

Symbol Value  Type
  2018   Dynamic
   180607 Dynamic

Paul

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Thursday, June 07, 2018 7:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

Hi Sean,
It is not in my 2.2 system. Are you at 2.3?

Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Sean Gleann
> Sent: 06 June, 2018 16:40
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
>
> Hi Kees
>
> "Have I defined it"?In a SET statement you mean?
> I didn't think you had to, LYYMMDD is a system-defined dynamic symbol,
> isn't it?
>
> Sean
>
> On 6 June 2018 at 15:36, Vernooij, Kees (ITOPT1) - KLM <
> kees.verno...@klm.com> wrote:
>
> > I only get this error if the variable has not been defined. Have you
> > defined it?
> >
> > Kees.
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List [mailto:IBM-
> m...@listserv.ua.edu] On
> > > Behalf Of Rob Schramm
> > > Sent: 06 June, 2018 16:29
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: Use of dynamic system symbols in JCL
> > >
> > > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> > >
> > > Rob
> > >
> > > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann 
> wrote:
> > >
> > > > Can anyone point out what I'm doing wrong here, please?
> > > >
> > > >
> > > > I'm trying to create a file with a name that features today's
> date.
> > > > My statement is:
> > > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > > >
> > > > When I submit the job to the system, I get:
> > > >
> > > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > > >
> > > > I've tried numerous variants of this statement, but I always get
> the
> > > same
> > > > failure.
> > > > I'm almost certainly doing something stupid, but right now I
> > > > can't
> see
> > > the
> > > > wood for the trees...
> > > >
> > > >
> > > > Help...  Please...
> > > >
> > > > Sean Gleann
> > > >
> > > > 
> > > > --
> 
> > > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > > send email to lists...@listserv.ua.edu with the message: INFO
> > > > IBM-
> MAIN
> > > >
> > > --
> > >
> > > Rob Schramm
> > >
> > > --
> > > --
> --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-
> MAIN
> > 
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee only.
> If
> > you are not the addressee, you are notified that no part of the
> > e-mail
> or
> > any attachment may be disclosed, copied or distributed, and that any
> other
> > action related to this e-mail or attachment is strictly prohibited,
> and may
> > be unlawful. If you have received this e-mail by error, please
> > notify
> the
> > sender immediately by return e-mail, and delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
> > and/or
> its
> > employees shall not be liable for the incorrect or incomplete
> transmission
> > of this e-mail or any attachments, nor responsible for any delay in
> receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch
> > Airlines) is registered in Amstelveen, The Netherlands, with
> registered
> > number 33014286
> > 
> >
> >
> > 
> > -- For IBM-MAIN subscribe / signoff / archive access instru

Re: Use of dynamic system symbols in JCL

[Vernooij, Kees (ITOPT1) - KLM]

Hi Sean,
It is not in my 2.2 system. Are you at 2.3?

Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Sean Gleann
> Sent: 06 June, 2018 16:40
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
> 
> Hi Kees
> 
> "Have I defined it"?In a SET statement you mean?
> I didn't think you had to, LYYMMDD is a system-defined dynamic symbol,
> isn't it?
> 
> Sean
> 
> On 6 June 2018 at 15:36, Vernooij, Kees (ITOPT1) - KLM <
> kees.verno...@klm.com> wrote:
> 
> > I only get this error if the variable has not been defined. Have you
> > defined it?
> >
> > Kees.
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List [mailto:IBM-
> m...@listserv.ua.edu] On
> > > Behalf Of Rob Schramm
> > > Sent: 06 June, 2018 16:29
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: Re: Use of dynamic system symbols in JCL
> > >
> > > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> > >
> > > Rob
> > >
> > > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann 
> wrote:
> > >
> > > > Can anyone point out what I'm doing wrong here, please?
> > > >
> > > >
> > > > I'm trying to create a file with a name that features today's
> date.
> > > > My statement is:
> > > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > > >
> > > > When I submit the job to the system, I get:
> > > >
> > > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > > >
> > > > I've tried numerous variants of this statement, but I always get
> the
> > > same
> > > > failure.
> > > > I'm almost certainly doing something stupid, but right now I can't
> see
> > > the
> > > > wood for the trees...
> > > >
> > > >
> > > > Help...  Please...
> > > >
> > > > Sean Gleann
> > > >
> > > > --
> 
> > > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-
> MAIN
> > > >
> > > --
> > >
> > > Rob Schramm
> > >
> > > 
> --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-
> MAIN
> > 
> > For information, services and offers, please visit our web site:
> > http://www.klm.com. This e-mail and any attachment may contain
> > confidential and privileged material intended for the addressee only.
> If
> > you are not the addressee, you are notified that no part of the e-mail
> or
> > any attachment may be disclosed, copied or distributed, and that any
> other
> > action related to this e-mail or attachment is strictly prohibited,
> and may
> > be unlawful. If you have received this e-mail by error, please notify
> the
> > sender immediately by return e-mail, and delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
> its
> > employees shall not be liable for the incorrect or incomplete
> transmission
> > of this e-mail or any attachments, nor responsible for any delay in
> receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch
> > Airlines) is registered in Amstelveen, The Netherlands, with
> registered
> > number 33014286
> > 
> >
> >
> > --
> > 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

For information, services and offers, please visit our web site: 
http://

Re: Use of dynamic system symbols in JCL

[Lizette Koehler]

Just in case it was not mentioned, 

If you have scheduling software, you might be able to get what you want.

Or you can write a rexx to create the JCL with what you want.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of
> Sean Gleann
> Sent: Wednesday, June 06, 2018 7:27 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Use of dynamic system symbols in JCL
> 
> Can anyone point out what I'm doing wrong here, please?
> 
> 
> I'm trying to create a file with a name that features today's date.
> My statement is:
> //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> 
> When I submit the job to the system, I get:
> 
> IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> 
> I've tried numerous variants of this statement, but I always get the same
> failure.
> I'm almost certainly doing something stupid, but right now I can't see the
> wood for the trees...
> 
> 
> Help...  Please...
> 
> Sean Gleann
> 
> --
> 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

Re: Use of dynamic system symbols in JCL

[Seymour J Metz]

As I recall they came in with R14.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, June 6, 2018 2:52 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
><http://secure-web.cisco.com/1uov7rGc-t0NPyZsdcMnPGPEeDQO1mJSyuzQD7x1uxGpsYyGjc7Iepvum1y25CxN8SM-En7FCoESH2X34K1Kmw_nXv-X0jrcA3cceOBT9GfIrad06DY3-cnOW_gf4j7DBj80PDAelaETSvzgg8xwpzZpzB_FIpVdCicFi3Zx1EFxJXdbM0L2bj6HICWwvxMm0xiNfGCn3vLgOjEDPG7oWle5zhotRGEnmDz3uhIYuzy57DwYjlqrnXn6WKS4y4AvStjKNzXvwItWdNjBrhwXxOHqjBFtue-TZUoy_7SsQhufxJqXfgaoEUY_iVbvICHMdd2TnSz4kdMm8oeblEdb_F5T64imeJ-CGJsfXWKS2fQKV9_a8vOyhXe9daMkZsg0sqZqn7l3XEdFLxtZHkF8Di1ueP1W9tPwPrDFxG4YmeQJkuAhZ9Ng9oj2Xhn-rMdoq/http%3A%2F%2Fbitsavers.org%2Fpdf%2Fibm%2F360%2Fos%2FR01-08%2FC28-6539-4_OS_JCL_Mar67.pdf>
>
Thanks.  Do I correctly see:

o No PROC statement?

o No instream PROCs?

Was "DSN=" the only use of "&" in JCL at that OS release?

-- 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

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Wed, 6 Jun 2018 18:02:13 +, Seymour J Metz wrote:

>>Except, does support of DSN= antedate any support of symbols in JCL,
>> not only by SET but also as PROC parameters?
>
>Yes. Bitsavers is your friend. 
>
> 
Thanks.  Do I correctly see:

o No PROC statement?

o No instream PROCs?

Was "DSN=" the only use of "&" in JCL at that OS release?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Seymour J Metz]

>Except, does support of DSN= antedate any support of symbols in JCL,
> not only by SET but also as PROC parameters?

Yes. Bitsavers is your friend. 
<http://bitsavers.org/pdf/ibm/360/os/R01-08/C28-6539-4_OS_JCL_Mar67.pdf>


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, June 6, 2018 1:26 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

On Wed, 6 Jun 2018 11:51:30 -0400, 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=  That's supposed to be DSN=&TMP, but for
>whatever reason, the single-& version works, unless  is a symbol.
>
Bug?  Feature?  I call it a primeval bad design.  Any use of an undefined symbol
should always have resulted in a JCL error.

Except, does support of DSN= antedate any support of symbols in JCL,
not only by SET but also as PROC parameters?

When to double ampersands and apostrophes get resolved?  I believe that
regardless of MSGLEVEL, when I code:
//EXEC   PGM=IEFBR14,PARM='O''Reilly &SYSUID '
//SET  RFM=FB
//SYSUT2  DD  DISP=(,PASS),DSN=&TMP,RECFM=,

... I still see double ampersands and double apostrophes in the JCL
substitution messages, but they are collapsed by the time the program
inspects its PARM.

-- 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

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Wed, 6 Jun 2018 16:28:06 +, Jesse 1 Robinson wrote:

>To summarize IBM's long-standing reticence on system symbols in batch.
>
>-- A system symbol might clash with ae existing JCL proc symbol with 
>unpredictable results.   
>-- A system symbol in batch may get resolved/substituted at an unexpected 
>point in processing.  
> 
This could have dreadful consequences for an ISV who can't control any 
customer's
setting of SYSSYM or of particular symbols.

The maxim is, "Define all symbols you use and double all ampersands not intended
to introduce symbols."

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Paul Gilmartin]

On Wed, 6 Jun 2018 11:51:30 -0400, 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=  That's supposed to be DSN=&TMP, but for
>whatever reason, the single-& version works, unless  is a symbol.
> 
Bug?  Feature?  I call it a primeval bad design.  Any use of an undefined symbol
should always have resulted in a JCL error.

Except, does support of DSN= antedate any support of symbols in JCL,
not only by SET but also as PROC parameters?

When to double ampersands and apostrophes get resolved?  I believe that
regardless of MSGLEVEL, when I code:
//EXEC   PGM=IEFBR14,PARM='O''Reilly &SYSUID '
//SET  RFM=FB
//SYSUT2  DD  DISP=(,PASS),DSN=&TMP,RECFM=,

... I still see double ampersands and double apostrophes in the JCL
substitution messages, but they are collapsed by the time the program
inspects its PARM.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Jesse 1 Robinson]

To summarize IBM's long-standing reticence on system symbols in batch.

-- A system symbol might clash with an existing JCL proc symbol with 
unpredictable results.   
-- A system symbol in batch may get resolved/substituted at an unexpected point 
in processing.  

By contrast, there is less danger in allowing symbols in STC or TSO because (a) 
substitution is immediate on the current LPAR and (b) STC and TSO JCL is owned 
by sysprogs who have the knowledge and power to fix any problems.  

By allowing symbols on a class by class basis, IBM has placed the onus on each 
shop to determine suitability and move as fast or slow as feels comfortable. 
Given the complexity of possible problems, I personally think the solution as 
delivered is both safe and comprehensive. Turning symbol substitution on or off 
is simple and dynamic. But not 'automatic'. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sri h Kolusu
Sent: Wednesday, June 06, 2018 8:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Use of dynamic system symbols in JCL

>>> I'd like to see the idea extended to cover 'yesterday', 'previous 
>>> work
day', 'beginning of the month', etc.

Sean,

You can currently use DFSORT to generate these dates as SET variables for you 
and then have it in a PDS member so that you can use it as an INCLUDE 
statements. This will work with any given date.

NEXTDday can be used to calculate the next specified day for a date field.
So for example if you wanted the next Friday then you would use NEXTDFRI

PREVDday can be used to calculate the previous specified day for a date
field.   So for example if you wanted the previous Wednesday , then you
would use PREVDWED.

LASTDAYW, LASTDAYM, LASTDAYQ or LASTDAYY can be used to calculate the last day 
of the week, month, quarter or year for a date field.

Thanks,
Kolusu
DFSORT Development
IBM Corporation


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Sri h Kolusu]

>>> I'd like to see the idea extended to cover 'yesterday', 'previous work
day', 'beginning of the month', etc.

Sean,

You can currently use DFSORT to generate these dates as SET variables for
you and then have it in a PDS member so that you can use it as an INCLUDE
statements. This will work with any given date.

NEXTDday can be used to calculate the next specified day for a date field.
So for example if you wanted the next Friday then you would use NEXTDFRI

PREVDday can be used to calculate the previous specified day for a date
field.   So for example if you wanted the previous Wednesday , then you
would use PREVDWED.

LASTDAYW, LASTDAYM, LASTDAYQ or LASTDAYY can be used to calculate the last
day of the week, month, quarter or year for a date field.

Thanks,
Kolusu
DFSORT Development
IBM Corporation

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Steve Smith]

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=  That's supposed to be DSN=&, but for
whatever reason, the single-& version works, unless  is a symbol.

As to which system, that has obvious solutions.

sas

On Wed, Jun 6, 2018 at 11:27 AM, Jousma, David <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:

> Ok, wasn’t the issue all those years ago with regards to *when* the system
> symbols get resolved?  Interpreter time vs execution time and those things
> occurring on potentially two different systems in the plex?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Carmen Vitullo]

I do recall one issue with NDM batch, when we moved the NDM workload to use 
both systems in the MAS, symbols get resolved at interpreter/conversion time, 
we submit on system A, and it's setup to run on system B, using  was 
the issue, so some job class rules needed to be added to make sure specific 
workloads were submitted and run on the correct system using these symbols 



Carmen Vitullo 

- Original Message -

From: "David Jousma" <01a0403c5dc1-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Wednesday, June 6, 2018 10:27:28 AM 
Subject: Re: Use of dynamic system symbols in JCL 

Ok, wasn’t the issue all those years ago with regards to *when* the system 
symbols get resolved? Interpreter time vs execution time and those things 
occurring on potentially two different systems in the plex? 

I could *easily* be mis-remembering. 
_ 
Dave Jousma 
Manager Mainframe Engineering, Assistant Vice President 
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H 
p 616.653.8429 
f 616.653.2717 


-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sean Gleann 
Sent: Wednesday, June 06, 2018 11:19 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Use of dynamic system symbols in JCL 

**CAUTION EXTERNAL EMAIL** 

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails** 

Thanks all - the SYSSYM bit was the missing link. 

I've defined that and now all is well. 

Dave's last comment regarding 'unpredictable results' is a bit worrying. 
Have there been problems with using these symbols? 

Personally I feel it's a pity that SYSSYM has to be specifically turned on or 
off at all. These dynamic symbols are SO useful! 
I'd like to see the idea extended to cover 'yesterday', 'previous work day', 
'beginning of the month', etc. 

Thanks once again 

Sean 

On 6 June 2018 at 16:03, Jousma, David < 
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: 

> Is anyone else pushing back on turning on batch system symbol support? 
> We've yet to do so, for the very reasons that IBM hadn’t supported in 
> batch all along. My main concern is unpredictable results. 
> 
> Am I worrying for nothing? 
> 
> _ 
> Dave Jousma 
> Manager Mainframe Engineering, Assistant Vice President 
> david.jou...@53.com 
> 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 
> 616.653.2717 
> 
> -Original Message- 
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Carmen Vitullo 
> Sent: Wednesday, June 06, 2018 10:49 AM 
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: Use of dynamic system symbols in JCL 
> 
> **CAUTION EXTERNAL EMAIL** 
> 
> **DO NOT open attachments or click on links from unknown senders or 
> unexpected emails** 
> 
> Yep, need to make sure SYSSYM=ALLOW for that jobclass, 
> 
> 
> 
> CLASS og XBMProc DupJob JobRC Active SysSym 
> 1 PIN) NO MAXRC YES ALLOW 
> 2 PIN) NO MAXRC YES ALLOW 
> 
> 
> 
> 
> in a STC I run at IPL time I do about the same 
> 
> 
> 
> //CLEAN EXEC PGM=IDCAMS 
> //SYSPRINT DD SYSOUT=* 
> //SYSIN DD *,SYMBOLS=EXECSYS 
> DEL 'ATTS.PROD.' 
> /* 
> //IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO', 
> // DYNAMNBR=99 
> //SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR //SYSTSPRT DD 
> DSN=ATTS.PROD.,DISP=(,CATLG), 
> // UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE), 
> // RECFM=FBA,LRECL=134,BLKSIZE=0 
> //SYSTSIN DD DUMMY 
> //* 
> //IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=* 
> //SYSUT1 DD DISP=SHR,DSN=SYS1. 
> //SYSUT2 DD DISP=(,CATLG), 
> // DSN=ATTS.PROD.SYSA.D, 
> // UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE) 
> of course STC  
> 
> 
> 
> Carmen Vitullo 
> 
> - Original Message - 
> 
> From: "Andrew Arentsen"  
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Sent: Wednesday, June 6, 2018 9:43:25 AM 
> Subject: Re: Use of dynamic system symbols in JCL 
> 
> In my JES2PARM, in the definition of the job class that I'd run this 
> job in, I specify SYSSYM=ALLOW. I'm sure you could put this in 
> dynamically with a $T of some sort. You'll also need the two periods as Rob 
> stated. 
> 
> Andrew Arentsen 
> Senior Mainframe Systems Engineer 
> 
> 
> 
> 
> From: "Sean Gleann"  
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Date: 06/06/2018 09:35 AM 
> Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM 
> Mainframe Discussion List"  
> 
> 
> 
> I understand what you're saying Rob, but that was one of the variants 
> I tried. It still produces the same error

Re: Use of dynamic system symbols in JCL

[Jerry Whitteridge]

Yes - and that's why we also haven't turned the use on.

Jerry Whitteridge
Delivery Manager / Mainframe Architect
GTS - Safeway Account
602 527 4871 Mobile
jerry.whitteri...@ibm.com

IBM Services

IBM Mainframe Discussion List  wrote on
06/06/2018 08:27:28 AM:

> From: "Jousma, David" <01a0403c5dc1-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/06/2018 08:35 AM
> Subject: Re: Use of dynamic system symbols in JCL
> Sent by: IBM Mainframe Discussion List 
>
> Ok, wasn’t the issue all those years ago with regards to *when* the
> system symbols get resolved?  Interpreter time vs execution time and
> those things occurring on potentially two different systems in the plex?
>
> I could *easily* be mis-remembering.
> _
> Dave Jousma
> Manager Mainframe Engineering, Assistant Vice President
> david.jou...@53.com
> 1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
> p 616.653.8429
> f 616.653.2717
>
> --
> 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

Re: Use of dynamic system symbols in JCL

[Jousma, David]

Ok, wasn’t the issue all those years ago with regards to *when* the system 
symbols get resolved?  Interpreter time vs execution time and those things 
occurring on potentially two different systems in the plex?

I could *easily* be mis-remembering.
_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sean Gleann
Sent: Wednesday, June 06, 2018 11:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Thanks all - the SYSSYM bit was the missing link.

I've defined that and now all is well.

Dave's last comment regarding 'unpredictable results' is a bit worrying.
Have there been problems with using these symbols?

Personally I feel it's a pity that SYSSYM has to be specifically turned on or 
off at all. These dynamic symbols are SO useful!
I'd like to see the idea extended to cover 'yesterday', 'previous work day', 
'beginning of the month', etc.

Thanks once again

Sean

On 6 June 2018 at 16:03, Jousma, David < 
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:

> Is anyone else pushing back on turning on batch system symbol support?
>  We've yet to do so, for the very reasons that IBM hadn’t supported in 
> batch all along.  My main concern is unpredictable results.
>
> Am I worrying for nothing?
>
> _
> Dave Jousma
> Manager Mainframe Engineering, Assistant Vice President 
> david.jou...@53.com
> 1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H p 616.653.8429 f 
> 616.653.2717
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Carmen Vitullo
> Sent: Wednesday, June 06, 2018 10:49 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
>
> **CAUTION EXTERNAL EMAIL**
>
> **DO NOT open attachments or click on links from unknown senders or 
> unexpected emails**
>
> Yep, need to make sure SYSSYM=ALLOW for that jobclass,
>
>
>
> CLASS og XBMProc DupJob JobRC Active SysSym
> 1 PIN) NO MAXRC YES ALLOW
> 2 PIN) NO MAXRC YES ALLOW
>
>
>
>
> in a STC I run at IPL time I do about the same
>
>
>
> //CLEAN EXEC PGM=IDCAMS
> //SYSPRINT DD SYSOUT=*
> //SYSIN DD *,SYMBOLS=EXECSYS
> DEL 'ATTS.PROD.'
> /*
> //IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
> // DYNAMNBR=99
> //SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR //SYSTSPRT DD 
> DSN=ATTS.PROD.,DISP=(,CATLG),
> // UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE),
> // RECFM=FBA,LRECL=134,BLKSIZE=0
> //SYSTSIN DD DUMMY
> //*
> //IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=*
> //SYSUT1 DD DISP=SHR,DSN=SYS1.
> //SYSUT2 DD DISP=(,CATLG),
> // DSN=ATTS.PROD.SYSA.D,
> // UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
> of course STC ....
>
>
>
> Carmen Vitullo
>
> - Original Message -
>
> From: "Andrew Arentsen" 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Wednesday, June 6, 2018 9:43:25 AM
> Subject: Re: Use of dynamic system symbols in JCL
>
> In my JES2PARM, in the definition of the job class that I'd run this 
> job in, I specify SYSSYM=ALLOW. I'm sure you could put this in 
> dynamically with a $T of some sort. You'll also need the two periods as Rob 
> stated.
>
> Andrew Arentsen
> Senior Mainframe Systems Engineer
>
>
>
>
> From: "Sean Gleann" 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/06/2018 09:35 AM
> Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM 
> Mainframe Discussion List" 
>
>
>
> I understand what you're saying Rob, but that was one of the variants 
> I tried. It still produces the same error
>
> Sean
>
> On 6 June 2018 at 15:29, Rob Schramm  wrote:
>
> > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> >
> > Rob
> >
> > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann 
> wrote:
> >
> > > Can anyone point out what I'm doing wrong here, please?
> > >
> > >
> > > I'm trying to create a file with a name that features today's date.
> > > My statement is:
> > > //OUTFILE DD DSN=BACKUP.USERDALY.D,
> > > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > >
> > > When I submit the job to the system, I get:
> >

Re: Use of dynamic system symbols in JCL

[Sean Gleann]

Thanks all - the SYSSYM bit was the missing link.

I've defined that and now all is well.

Dave's last comment regarding 'unpredictable results' is a bit worrying.
Have there been problems with using these symbols?

Personally I feel it's a pity that SYSSYM has to be specifically turned on
or off at all. These dynamic symbols are SO useful!
I'd like to see the idea extended to cover 'yesterday', 'previous work
day', 'beginning of the month', etc.

Thanks once again

Sean

On 6 June 2018 at 16:03, Jousma, David <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:

> Is anyone else pushing back on turning on batch system symbol support?
>  We've yet to do so, for the very reasons that IBM hadn’t supported in
> batch all along.  My main concern is unpredictable results.
>
> Am I worrying for nothing?
>
> _
> Dave Jousma
> Manager Mainframe Engineering, Assistant Vice President
> david.jou...@53.com
> 1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
> p 616.653.8429
> f 616.653.2717
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Carmen Vitullo
> Sent: Wednesday, June 06, 2018 10:49 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
>
> **CAUTION EXTERNAL EMAIL**
>
> **DO NOT open attachments or click on links from unknown senders or
> unexpected emails**
>
> Yep, need to make sure SYSSYM=ALLOW for that jobclass,
>
>
>
> CLASS og XBMProc DupJob JobRC Active SysSym
> 1 PIN) NO MAXRC YES ALLOW
> 2 PIN) NO MAXRC YES ALLOW
>
>
>
>
> in a STC I run at IPL time I do about the same
>
>
>
> //CLEAN EXEC PGM=IDCAMS
> //SYSPRINT DD SYSOUT=*
> //SYSIN DD *,SYMBOLS=EXECSYS
> DEL 'ATTS.PROD.'
> /*
> //IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
> // DYNAMNBR=99
> //SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
> //SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG),
> // UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE),
> // RECFM=FBA,LRECL=134,BLKSIZE=0
> //SYSTSIN DD DUMMY
> //*
> //IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=*
> //SYSUT1 DD DISP=SHR,DSN=SYS1.
> //SYSUT2 DD DISP=(,CATLG),
> // DSN=ATTS.PROD.SYSA.D,
> // UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
> of course STC 
>
>
>
> Carmen Vitullo
>
> - Original Message -
>
> From: "Andrew Arentsen" 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Wednesday, June 6, 2018 9:43:25 AM
> Subject: Re: Use of dynamic system symbols in JCL
>
> In my JES2PARM, in the definition of the job class that I'd run this job
> in, I specify SYSSYM=ALLOW. I'm sure you could put this in dynamically with
> a $T of some sort. You'll also need the two periods as Rob stated.
>
> Andrew Arentsen
> Senior Mainframe Systems Engineer
>
>
>
>
> From: "Sean Gleann" 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/06/2018 09:35 AM
> Subject: Re: Use of dynamic system symbols in JCL
> Sent by: "IBM Mainframe Discussion List" 
>
>
>
> I understand what you're saying Rob, but that was one of the variants I
> tried. It still produces the same error
>
> Sean
>
> On 6 June 2018 at 15:29, Rob Schramm  wrote:
>
> > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> >
> > Rob
> >
> > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann 
> wrote:
> >
> > > Can anyone point out what I'm doing wrong here, please?
> > >
> > >
> > > I'm trying to create a file with a name that features today's date.
> > > My statement is:
> > > //OUTFILE DD DSN=BACKUP.USERDALY.D,
> > > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > >
> > > When I submit the job to the system, I get:
> > >
> > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > >
> > > I've tried numerous variants of this statement, but I always get the
> same
> > > failure.
> > > I'm almost certainly doing something stupid, but right now I can't see
> > the
> > > wood for the trees...
> > >
> > >
> > > Help... Please...
> > >
> > > Sean Gleann
> > >
> > > --
>
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO
> IBM-MAIN
> > >
> > --
> >
> > Rob Schramm
> >
> > 

Re: Use of dynamic system symbols in JCL

[Carmen Vitullo]

I moved slowly, changing test jobclasses first, found no issue, and went full 
out with no issues 



Carmen Vitullo 

- Original Message -

From: "David Jousma" <01a0403c5dc1-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Wednesday, June 6, 2018 10:03:36 AM 
Subject: Re: Use of dynamic system symbols in JCL 

Is anyone else pushing back on turning on batch system symbol support? We've 
yet to do so, for the very reasons that IBM hadn’t supported in batch all 
along. My main concern is unpredictable results. 

Am I worrying for nothing? 

_ 
Dave Jousma 
Manager Mainframe Engineering, Assistant Vice President 
david.jou...@53.com 
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H 
p 616.653.8429 
f 616.653.2717 

-Original Message- 
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo 
Sent: Wednesday, June 06, 2018 10:49 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Use of dynamic system symbols in JCL 

**CAUTION EXTERNAL EMAIL** 

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails** 

Yep, need to make sure SYSSYM=ALLOW for that jobclass, 



CLASS og XBMProc DupJob JobRC Active SysSym 
1 PIN) NO MAXRC YES ALLOW 
2 PIN) NO MAXRC YES ALLOW 




in a STC I run at IPL time I do about the same 



//CLEAN EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD *,SYMBOLS=EXECSYS 
DEL 'ATTS.PROD.' 
/* 
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO', 
// DYNAMNBR=99 
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR 
//SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG), 
// UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE), 
// RECFM=FBA,LRECL=134,BLKSIZE=0 
//SYSTSIN DD DUMMY 
//* 
//IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=* 
//SYSUT1 DD DISP=SHR,DSN=SYS1. 
//SYSUT2 DD DISP=(,CATLG), 
// DSN=ATTS.PROD.SYSA.D, 
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE) 
of course STC  



Carmen Vitullo 

- Original Message - 

From: "Andrew Arentsen"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Wednesday, June 6, 2018 9:43:25 AM 
Subject: Re: Use of dynamic system symbols in JCL 

In my JES2PARM, in the definition of the job class that I'd run this job in, I 
specify SYSSYM=ALLOW. I'm sure you could put this in dynamically with a $T of 
some sort. You'll also need the two periods as Rob stated. 

Andrew Arentsen 
Senior Mainframe Systems Engineer 




From: "Sean Gleann"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Date: 06/06/2018 09:35 AM 
Subject: Re: Use of dynamic system symbols in JCL 
Sent by: "IBM Mainframe Discussion List"  



I understand what you're saying Rob, but that was one of the variants I 
tried. It still produces the same error 

Sean 

On 6 June 2018 at 15:29, Rob Schramm  wrote: 

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters 
> 
> Rob 
> 
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote: 
> 
> > Can anyone point out what I'm doing wrong here, please? 
> > 
> > 
> > I'm trying to create a file with a name that features today's date. 
> > My statement is: 
> > //OUTFILE DD DSN=BACKUP.USERDALY.D, 
> > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE), 
> > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024 
> > 
> > When I submit the job to the system, I get: 
> > 
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD 
> > 
> > I've tried numerous variants of this statement, but I always get the 
same 
> > failure. 
> > I'm almost certainly doing something stupid, but right now I can't see 
> the 
> > wood for the trees... 
> > 
> > 
> > Help... Please... 
> > 
> > Sean Gleann 
> > 
> > -- 
> > For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 
> > 
> -- 
> 
> Rob Schramm 
> 
> -- 
> 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 


** 
This e-mail is confidential. If you are not the intended recipient, you must 
not disclose or use the information contained in it. If you have received this 
e-mail in error, please tell us immediately by return e-mail and delete the 
document. 

-- 
For IBM-MAIN subscri

Re: Use of dynamic system symbols in JCL

[Ed Jaffe]

On 6/6/2018 8:03 AM, Jousma, David wrote:

Is anyone else pushing back on turning on batch system symbol support?   We've 
yet to do so, for the very reasons that IBM hadn’t supported in batch all 
along.  My main concern is unpredictable results.


Unpredictable results in what way? If your JCL doesn't use the support 
then where's the exposure?


Of course, if your JCL does try to use the support and you haven't 
enabled it, then you definitely have predictable results -- predictably 
bad. LOL


--
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

Re: Use of dynamic system symbols in JCL

[Jousma, David]

Is anyone else pushing back on turning on batch system symbol support?   We've 
yet to do so, for the very reasons that IBM hadn’t supported in batch all 
along.  My main concern is unpredictable results.

Am I worrying for nothing?

_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Use of dynamic system symbols in JCL

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

Yep, need to make sure SYSSYM=ALLOW for that jobclass, 



CLASS og XBMProc DupJob JobRC Active SysSym
1 PIN) NO MAXRC YES ALLOW
2 PIN) NO MAXRC YES ALLOW 




in a STC I run at IPL time I do about the same 



//CLEAN EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *,SYMBOLS=EXECSYS
DEL 'ATTS.PROD.' 
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG),
// UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE),
// RECFM=FBA,LRECL=134,BLKSIZE=0
//SYSTSIN DD DUMMY
//*
//IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=SYS1.
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC  



Carmen Vitullo 

- Original Message -

From: "Andrew Arentsen" 
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, June 6, 2018 9:43:25 AM
Subject: Re: Use of dynamic system symbols in JCL 

In my JES2PARM, in the definition of the job class that I'd run this job in, I 
specify SYSSYM=ALLOW. I'm sure you could put this in dynamically with a $T of 
some sort. You'll also need the two periods as Rob stated. 

Andrew Arentsen
Senior Mainframe Systems Engineer 




From: "Sean Gleann"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Date: 06/06/2018 09:35 AM 
Subject: Re: Use of dynamic system symbols in JCL 
Sent by: "IBM Mainframe Discussion List"  



I understand what you're saying Rob, but that was one of the variants I 
tried. It still produces the same error 

Sean 

On 6 June 2018 at 15:29, Rob Schramm  wrote: 

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters 
> 
> Rob 
> 
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote: 
> 
> > Can anyone point out what I'm doing wrong here, please? 
> > 
> > 
> > I'm trying to create a file with a name that features today's date. 
> > My statement is: 
> > //OUTFILE DD DSN=BACKUP.USERDALY.D, 
> > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE), 
> > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024 
> > 
> > When I submit the job to the system, I get: 
> > 
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD 
> > 
> > I've tried numerous variants of this statement, but I always get the 
same 
> > failure. 
> > I'm almost certainly doing something stupid, but right now I can't see 
> the 
> > wood for the trees... 
> > 
> > 
> > Help... Please... 
> > 
> > Sean Gleann 
> > 
> > -- 
> > For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 
> > 
> -- 
> 
> Rob Schramm 
> 
> -- 
> 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 


** 
This e-mail is confidential. If you are not the intended recipient, you must 
not disclose or use the information contained in it. If you have received this 
e-mail in error, please tell us immediately by return e-mail and delete the 
document. 

-- 
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
**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links fro

Re: Use of dynamic system symbols in JCL

[Carmen Vitullo]

Yep, need to make sure SYSSYM=ALLOW for that jobclass, 



CLASS og XBMProc DupJob JobRC Active SysSym 
1 PIN) NO MAXRC YES ALLOW 
2 PIN) NO MAXRC YES ALLOW 




in a STC I run at IPL time I do about the same 



//CLEAN EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD *,SYMBOLS=EXECSYS 
DEL 'ATTS.PROD.' 
/* 
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO', 
// DYNAMNBR=99 
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR 
//SYSTSPRT DD DSN=ATTS.PROD.,DISP=(,CATLG), 
// UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE), 
// RECFM=FBA,LRECL=134,BLKSIZE=0 
//SYSTSIN DD DUMMY 
//* 
//IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 
//SYSPRINT DD SYSOUT=* 
//SYSUT1 DD DISP=SHR,DSN=SYS1. 
//SYSUT2 DD DISP=(,CATLG), 
// DSN=ATTS.PROD.SYSA.D, 
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE) 
of course STC  



Carmen Vitullo 

- Original Message -

From: "Andrew Arentsen"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Wednesday, June 6, 2018 9:43:25 AM 
Subject: Re: Use of dynamic system symbols in JCL 

In my JES2PARM, in the definition of the job class that I'd run this job 
in, I specify SYSSYM=ALLOW. I'm sure you could put this in dynamically 
with a $T of some sort. You'll also need the two periods as Rob stated. 

Andrew Arentsen 
Senior Mainframe Systems Engineer 




From: "Sean Gleann"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Date: 06/06/2018 09:35 AM 
Subject: Re: Use of dynamic system symbols in JCL 
Sent by: "IBM Mainframe Discussion List"  



I understand what you're saying Rob, but that was one of the variants I 
tried. It still produces the same error 

Sean 

On 6 June 2018 at 15:29, Rob Schramm  wrote: 

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters 
> 
> Rob 
> 
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote: 
> 
> > Can anyone point out what I'm doing wrong here, please? 
> > 
> > 
> > I'm trying to create a file with a name that features today's date. 
> > My statement is: 
> > //OUTFILE DD DSN=BACKUP.USERDALY.D, 
> > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE), 
> > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024 
> > 
> > When I submit the job to the system, I get: 
> > 
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD 
> > 
> > I've tried numerous variants of this statement, but I always get the 
same 
> > failure. 
> > I'm almost certainly doing something stupid, but right now I can't see 
> the 
> > wood for the trees... 
> > 
> > 
> > Help... Please... 
> > 
> > Sean Gleann 
> > 
> > -- 
> > For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 
> > 
> -- 
> 
> Rob Schramm 
> 
> -- 
> 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 


** 
This e-mail is confidential. If you are not the intended recipient, you must 
not disclose or use the information contained in it. If you have received this 
e-mail in error, please tell us immediately by return e-mail and delete the 
document. 

-- 
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

Re: Use of dynamic system symbols in JCL

[Rob Schramm]

What you have coded will produce more than 8 characters in the last node.

Have you verified the symbol works?

Maybe use a SET XXX =   ?

Rob


On Wed, Jun 6, 2018, 10:35 AM Sean Gleann  wrote:

> I understand what you're saying Rob, but that was one of the variants I
> tried. It still produces the same error
>
> Sean
>
> On 6 June 2018 at 15:29, Rob Schramm  wrote:
>
> > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> >
> > Rob
> >
> > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
> >
> > > Can anyone point out what I'm doing wrong here, please?
> > >
> > >
> > > I'm trying to create a file with a name that features today's date.
> > > My statement is:
> > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > >
> > > When I submit the job to the system, I get:
> > >
> > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > >
> > > I've tried numerous variants of this statement, but I always get the
> same
> > > failure.
> > > I'm almost certainly doing something stupid, but right now I can't see
> > the
> > > wood for the trees...
> > >
> > >
> > > Help...  Please...
> > >
> > > Sean Gleann
> > >
> > > --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> > >
> > --
> >
> > Rob Schramm
> >
> > --
> > 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
>
-- 

Rob Schramm

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Andrew Arentsen]

In my JES2PARM, in the definition of the job class that I'd run this job 
in, I specify SYSSYM=ALLOW. I'm sure you could put this in dynamically 
with a $T of some sort. You'll also need the two periods as Rob stated.

Andrew Arentsen
Senior Mainframe Systems Engineer




From:   "Sean Gleann" 
To: IBM-MAIN@LISTSERV.UA.EDU
Date:   06/06/2018 09:35 AM
Subject:        Re: Use of dynamic system symbols in JCL
Sent by:"IBM Mainframe Discussion List" 



I understand what you're saying Rob, but that was one of the variants I
tried. It still produces the same error

Sean

On 6 June 2018 at 15:29, Rob Schramm  wrote:

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters
>
> Rob
>
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
>
> > Can anyone point out what I'm doing wrong here, please?
> >
> >
> > I'm trying to create a file with a name that features today's date.
> > My statement is:
> > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> >
> > When I submit the job to the system, I get:
> >
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> >
> > I've tried numerous variants of this statement, but I always get the 
same
> > failure.
> > I'm almost certainly doing something stupid, but right now I can't see
> the
> > wood for the trees...
> >
> >
> > Help...  Please...
> >
> > Sean Gleann
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> --
>
> Rob Schramm
>
> --
> 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


**
This e-mail is confidential. If you are not the intended recipient, you must 
not disclose or use the information contained in it. If you have received this 
e-mail in error, please tell us immediately by return e-mail and delete the 
document.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Sean Gleann]

Hi Kees

"Have I defined it"?In a SET statement you mean?
I didn't think you had to, LYYMMDD is a system-defined dynamic symbol,
isn't it?

Sean

On 6 June 2018 at 15:36, Vernooij, Kees (ITOPT1) - KLM <
kees.verno...@klm.com> wrote:

> I only get this error if the variable has not been defined. Have you
> defined it?
>
> Kees.
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Rob Schramm
> > Sent: 06 June, 2018 16:29
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Use of dynamic system symbols in JCL
> >
> > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> >
> > Rob
> >
> > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
> >
> > > Can anyone point out what I'm doing wrong here, please?
> > >
> > >
> > > I'm trying to create a file with a name that features today's date.
> > > My statement is:
> > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > >
> > > When I submit the job to the system, I get:
> > >
> > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > >
> > > I've tried numerous variants of this statement, but I always get the
> > same
> > > failure.
> > > I'm almost certainly doing something stupid, but right now I can't see
> > the
> > > wood for the trees...
> > >
> > >
> > > Help...  Please...
> > >
> > > Sean Gleann
> > >
> > > --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> > >
> > --
> >
> > Rob Schramm
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
>
>
> --
> 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

Re: Use of dynamic system symbols in JCL

[Vernooij, Kees (ITOPT1) - KLM]

I only get this error if the variable has not been defined. Have you defined it?
 
Kees.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Rob Schramm
> Sent: 06 June, 2018 16:29
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Use of dynamic system symbols in JCL
> 
> You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> 
> Rob
> 
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
> 
> > Can anyone point out what I'm doing wrong here, please?
> >
> >
> > I'm trying to create a file with a name that features today's date.
> > My statement is:
> > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> >
> > When I submit the job to the system, I get:
> >
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> >
> > I've tried numerous variants of this statement, but I always get the
> same
> > failure.
> > I'm almost certainly doing something stupid, but right now I can't see
> the
> > wood for the trees...
> >
> >
> > Help...  Please...
> >
> > Sean Gleann
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> --
> 
> Rob Schramm
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Lucas Rosalen]

 Hello Sean,

Are you sure you're running on a z/OS version AND class that allows symbols
substitution? Apparently the original  was no replaced.

Regards,

---
*Lucas Rosalen*
rosalen.lu...@gmail.com / lucas.rosal...@ibm.com
http://br.linkedin.com/in/lrosalen


2018-06-06 16:35 GMT+02:00 Sean Gleann :

> I understand what you're saying Rob, but that was one of the variants I
> tried. It still produces the same error
>
> Sean
>
> On 6 June 2018 at 15:29, Rob Schramm  wrote:
>
> > You need 2 dots after symbol.. otherwise nodeis GT 8 characters
> >
> > Rob
> >
> > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
> >
> > > Can anyone point out what I'm doing wrong here, please?
> > >
> > >
> > > I'm trying to create a file with a name that features today's date.
> > > My statement is:
> > > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> > >
> > > When I submit the job to the system, I get:
> > >
> > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> > >
> > > I've tried numerous variants of this statement, but I always get the
> same
> > > failure.
> > > I'm almost certainly doing something stupid, but right now I can't see
> > the
> > > wood for the trees...
> > >
> > >
> > > Help...  Please...
> > >
> > > Sean Gleann
> > >
> > > --
> > > For IBM-MAIN subscribe / signoff / archive access instructions,
> > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> > >
> > --
> >
> > Rob Schramm
> >
> > --
> > 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
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Use of dynamic system symbols in JCL

[Sean Gleann]

I understand what you're saying Rob, but that was one of the variants I
tried. It still produces the same error

Sean

On 6 June 2018 at 15:29, Rob Schramm  wrote:

> You need 2 dots after symbol.. otherwise nodeis GT 8 characters
>
> Rob
>
> On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:
>
> > Can anyone point out what I'm doing wrong here, please?
> >
> >
> > I'm trying to create a file with a name that features today's date.
> > My statement is:
> > //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> > //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> > //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
> >
> > When I submit the job to the system, I get:
> >
> > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
> >
> > I've tried numerous variants of this statement, but I always get the same
> > failure.
> > I'm almost certainly doing something stupid, but right now I can't see
> the
> > wood for the trees...
> >
> >
> > Help...  Please...
> >
> > Sean Gleann
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> --
>
> Rob Schramm
>
> --
> 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

Re: Use of dynamic system symbols in JCL

[Rob Schramm]

You need 2 dots after symbol.. otherwise nodeis GT 8 characters

Rob

On Wed, Jun 6, 2018, 10:27 AM Sean Gleann  wrote:

> Can anyone point out what I'm doing wrong here, please?
>
>
> I'm trying to create a file with a name that features today's date.
> My statement is:
> //OUTFILE DD   DSN=BACKUP.USERDALY.D,
> //  DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
> //  DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
>
> When I submit the job to the system, I get:
>
> IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
>
> I've tried numerous variants of this statement, but I always get the same
> failure.
> I'm almost certainly doing something stupid, but right now I can't see the
> wood for the trees...
>
>
> Help...  Please...
>
> Sean Gleann
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 

Rob Schramm

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN