Use of dynamic system symbols in JCL

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

Rob

Post by Sean Gleann
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.
//OUTFILE DD DSN=BACKUP.USERDALY.D&LYYMMDD.TER,
// DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
// DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
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,

--
Rob Schramm

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

Sean Gleann

2018-06-06 14:35:14 UTC

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Lucas Rosalen

2018-06-06 14:36:44 UTC

Hello Sean,

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

Regards,

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

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

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Rob Schramm

2018-06-06 14:43:21 UTC

This post might be inappropriate. Click to display it.

Andrew Arentsen

2018-06-06 14:43:40 UTC

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" <***@GMAIL.COM>
To: IBM-***@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" <IBM-***@LISTSERV.UA.EDU>

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Carmen Vitullo

2018-06-06 14:48:57 UTC

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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....

Carmen Vitullo

----- Original Message -----

From: "Andrew Arentsen" <***@ACUITY.COM>
To: IBM-***@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" <***@GMAIL.COM>
To: IBM-***@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" <IBM-***@LISTSERV.UA.EDU>

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Jousma, David

2018-06-06 15:03:47 UTC

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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-***@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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....

Carmen Vitullo

----- Original Message -----

From: "Andrew Arentsen" <***@ACUITY.COM>
To: IBM-***@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" <***@GMAIL.COM>
To: IBM-***@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" <IBM-***@LISTSERV.UA.EDU>

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Ed Jaffe

2018-06-06 15:15:44 UTC

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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Carmen Vitullo

2018-06-06 15:18:01 UTC

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

Carmen Vitullo

----- Original Message -----

From: "David Jousma" <000001a0403c5dc1-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-***@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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....

Carmen Vitullo

----- Original Message -----

From: "Andrew Arentsen" <***@ACUITY.COM>
To: IBM-***@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" <***@GMAIL.COM>
To: IBM-***@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" <IBM-***@LISTSERV.UA.EDU>

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Sean Gleann

2018-06-06 15:18:43 UTC

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 <

Post by 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
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-----Original Message-----
Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....
Carmen Vitullo
----- Original Message -----
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
Date: 06/06/2018 09:35 AM
Subject: Re: Use of dynamic system symbols in JCL
I understand what you're saying Rob, but that was one of the variants I
tried. It still produces the same error
Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

IBM-MAIN

Post by Rob Schramm
--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
**********************************************************************
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,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected emails**
This e-mail transmission contains information that is confidential and may
be privileged. It is intended only for the addressee(s) named above. If
you receive this e-mail in error, please do not read, copy or disseminate
it in any manner. If you are not the intended recipient, any disclosure,
copying, distribution or use of the contents of this information is
prohibited. Please reply to the message immediately by informing the sender
that the message was misdirected. After replying, please erase it from your
computer system. Your assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Jousma, David

2018-06-06 15:27:41 UTC

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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Sean Gleann
Sent: Wednesday, June 06, 2018 11:19 AM
To: IBM-***@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

Post by 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
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f
616.653.2717
-----Original Message-----
On Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR //SYSTSPRT DD
DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....
Carmen Vitullo
----- Original Message -----
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
Date: 06/06/2018 09:35 AM
Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM
I understand what you're saying Rob, but that was one of the variants
I tried. It still produces the same error
Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
------------------------------------------------------------------
----
For IBM-MAIN subscribe / signoff / archive access instructions,

IBM-MAIN

Post by Rob Schramm
--
Rob Schramm
--------------------------------------------------------------------
-- For IBM-MAIN subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
**********************************************************************
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected emails**
This e-mail transmission contains information that is confidential and may
be privileged. It is intended only for the addressee(s) named above. If
you receive this e-mail in error, please do not read, copy or
disseminate it in any manner. If you are not the intended recipient,
any disclosure, copying, distribution or use of the contents of this
information is prohibited. Please reply to the message immediately by
informing the sender that the message was misdirected. After replying,
please erase it from your computer system. Your assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send

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

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

This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

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

Jerry Whitteridge

2018-06-06 15:49:27 UTC

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
***@ibm.com

IBM Services

Date: 06/06/2018 08:35 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
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,

Carmen Vitullo

2018-06-06 15:50:59 UTC

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 &SYSNAME 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" <000001a0403c5dc1-dmarc-***@LISTSERV.UA.EDU>
To: IBM-***@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
***@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-***@LISTSERV.UA.EDU] On Behalf Of Sean Gleann
Sent: Wednesday, June 06, 2018 11:19 AM
To: IBM-***@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

Post by 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
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f
616.653.2717
-----Original Message-----
On Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR //SYSTSPRT DD
DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....
Carmen Vitullo
----- Original Message -----
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
Date: 06/06/2018 09:35 AM
Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM
I understand what you're saying Rob, but that was one of the variants
I tried. It still produces the same error
Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
------------------------------------------------------------------
----
For IBM-MAIN subscribe / signoff / archive access instructions,

IBM-MAIN

Post by Rob Schramm
--
Rob Schramm
--------------------------------------------------------------------
-- For IBM-MAIN subscribe / signoff / archive access instructions,

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

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

This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

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

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

Steve Smith

2018-06-06 15:51:40 UTC

This has been previously discussed. The main issue (as usual) is
incompatibility with an ancient bug (or feature). Specifically, temporary
dataset names such as DSN=&TMP. That's supposed to be DSN=&&TMP, but for
whatever reason, the single-& version works, unless &TMP is a symbol.

As to which system, that has obvious solutions.

sas

On Wed, Jun 6, 2018 at 11:27 AM, Jousma, David <

Post by 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?

Ed Jaffe

2018-06-09 18:24:49 UTC

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

Wow! I confirmed this is an exposure! I never knew!

IBM does not mention the single ampersand being valid temporary data set
name syntax in the description of the DSNAME parameter on the DD
statement and I have previously not seen it used that way.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieab600/iea3b6_Syntax25.htm

This reminds me of the rule in REXX where use of an uninitialized
variable results in the variable name itself being substituted. But,
that is documented behavior. This is just plain wrong.

It might be a good use of the common tracker component (GTZ) to help
identify JCL with such errors. Otherwise, every new symbol added -- to
the system, to a proc, to anything that might have visibility to a job
stream -- can lead to unexpected JCL errors.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

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

Sri h Kolusu

2018-06-06 15:58:25 UTC

Post by Sean Gleann
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Beesley, Paul

2018-06-07 07:27:17 UTC

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-***@LISTSERV.UA.EDU] On Behalf Of Jousma, David
Sent: Wednesday, June 06, 2018 4:04 PM
To: IBM-***@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 ***@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-***@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo
Sent: Wednesday, June 06, 2018 10:49 AM
To: IBM-***@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.&SYSNAME..IPLINFO'
/*
//IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO',
// DYNAMNBR=99
//SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR
//SYSTSPRT DD DSN=ATTS.PROD.&SYSNAME..IPLINFO,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.&SYSNAME..PARMLIB
//SYSUT2 DD DISP=(,CATLG),
// DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB,
// UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE)
of course STC ....

Carmen Vitullo

----- Original Message -----

From: "Andrew Arentsen" <***@ACUITY.COM>
To: IBM-***@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" <***@GMAIL.COM>
To: IBM-***@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" <IBM-***@LISTSERV.UA.EDU>

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

Sean

Post by Rob Schramm
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
--------------------------------------------------------------------
-- For IBM-MAIN subscribe / signoff / archive access instructions,

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

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

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

This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at Second Floor, Mid City Place, 71 High Holborn, London, WC1V 6EA. The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

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

Vernooij, Kees - KLM , ITOPT1

2018-06-06 14:37:06 UTC

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

Kees.

-----Original Message-----
Behalf Of Rob Schramm
Sent: 06 June, 2018 16:29
Subject: Re: Use of dynamic system symbols in JCL
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Sean Gleann

2018-06-06 14:40:07 UTC

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 <

Post by Vernooij, Kees - KLM , ITOPT1
I only get this error if the variable has not been defined. Have you defined it?
Kees.

-----Original Message-----
Behalf Of Rob Schramm
Sent: 06 June, 2018 16:29
Subject: Re: Use of dynamic system symbols in JCL
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't see

the

--
Rob Schramm
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

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

Vernooij, Kees - KLM , ITOPT1

2018-06-07 06:17:51 UTC

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

Kees.

-----Original Message-----
Behalf Of Sean Gleann
Sent: 06 June, 2018 16:40
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 <

Post by Vernooij, Kees - KLM , ITOPT1
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-
Behalf Of Rob Schramm
Sent: 06 June, 2018 16:29
Subject: Re: Use of dynamic system symbols in JCL
You need 2 dots after symbol.. otherwise nodeis GT 8 characters
Rob

Post by Sean Gleann
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.

Post by Sean Gleann
//OUTFILE DD DSN=BACKUP.USERDALY.D&LYYMMDD.TER,
// DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
// DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD
I've tried numerous variants of this statement, but I always get

the

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't

see

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
------------------------------------------------------------------

----

Post by Sean Gleann
For IBM-MAIN subscribe / signoff / archive access instructions,

MAIN

--
Rob Schramm
--------------------------------------------------------------------

For IBM-MAIN subscribe / signoff / archive access instructions,

MAIN

Post by Vernooij, Kees - KLM , ITOPT1
********************************************************
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only.

Post by Vernooij, Kees - KLM , ITOPT1
you are not the addressee, you are notified that no part of the e-mail

Post by Vernooij, Kees - KLM , ITOPT1
any attachment may be disclosed, copied or distributed, and that any

other

Post by Vernooij, Kees - KLM , ITOPT1
action related to this e-mail or attachment is strictly prohibited,

and may

Post by Vernooij, Kees - KLM , ITOPT1
be unlawful. If you have received this e-mail by error, please notify

the

Post by Vernooij, Kees - KLM , ITOPT1
sender immediately by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or

its

Post by Vernooij, Kees - KLM , ITOPT1
employees shall not be liable for the incorrect or incomplete

transmission

Post by Vernooij, Kees - KLM , ITOPT1
of this e-mail or any attachments, nor responsible for any delay in

receipt.

Post by Vernooij, Kees - KLM , ITOPT1
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal

Dutch

Post by Vernooij, Kees - KLM , ITOPT1
Airlines) is registered in Amstelveen, The Netherlands, with

registered

Post by Vernooij, Kees - KLM , ITOPT1
number 33014286
********************************************************
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,

Beesley, Paul

2018-06-07 07:23:11 UTC

It's in my 2.1 system

Symbol Value Type
&LYR4. 2018 Dynamic
&LYYMMDD. 180607 Dynamic

Paul

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOPT1) - KLM
Sent: Thursday, June 07, 2018 7:04 AM
To: IBM-***@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-----
On Behalf Of Sean Gleann
Sent: 06 June, 2018 16:40
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 <

Post by Vernooij, Kees - KLM , ITOPT1
I only get this error if the variable has not been defined. Have you defined it?
Kees.

Post by Sean Gleann
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.

the

same

Post by Sean Gleann
failure.
I'm almost certainly doing something stupid, but right now I can't

see

the

Post by Sean Gleann
wood for the trees...
Help... Please...
Sean Gleann
----------------------------------------------------------------
--

----

Post by Sean Gleann
For IBM-MAIN subscribe / signoff / archive access instructions,

MAIN

--
Rob Schramm
------------------------------------------------------------------
--

For IBM-MAIN subscribe / signoff / archive access instructions,

MAIN

Post by Vernooij, Kees - KLM , ITOPT1
you are not the addressee, you are notified that no part of the e-mail

Post by Vernooij, Kees - KLM , ITOPT1
any attachment may be disclosed, copied or distributed, and that any

other

Post by Vernooij, Kees - KLM , ITOPT1
action related to this e-mail or attachment is strictly prohibited,

and may

Post by Vernooij, Kees - KLM , ITOPT1
be unlawful. If you have received this e-mail by error, please notify

the

Post by Vernooij, Kees - KLM , ITOPT1
sender immediately by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or

its

Post by Vernooij, Kees - KLM , ITOPT1
employees shall not be liable for the incorrect or incomplete

transmission

Post by Vernooij, Kees - KLM , ITOPT1
of this e-mail or any attachments, nor responsible for any delay in

receipt.

Post by Vernooij, Kees - KLM , ITOPT1
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal

Dutch

Post by Vernooij, Kees - KLM , ITOPT1
Airlines) is registered in Amstelveen, The Netherlands, with

registered

Post by Vernooij, Kees - KLM , ITOPT1
number 33014286
********************************************************
--------------------------------------------------------------------
-- For IBM-MAIN subscribe / signoff / archive access instructions,

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send

********************************************************
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at Second Floor, Mid City Place, 71 High Holborn, London, WC1V 6EA. The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

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

Jesse 1 Robinson

2018-06-06 16:28:18 UTC

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
***@sce.com

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

Post by Sean Gleann
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Paul Gilmartin

2018-06-06 17:26:17 UTC

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=&TMP 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 &SYUID'
//SET RFM=FB
//SYSUT2 DD DISP=(,PASS),DSN=&&TMP,RECFM=&RFM,

... 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Seymour J Metz

2018-06-06 18:02:23 UTC

Post by Paul Gilmartin
Except, does support of DSN=&TMP 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 <IBM-***@listserv.ua.edu> on behalf of Paul Gilmartin <0000000433f07816-dmarc-***@listserv.ua.edu>
Sent: Wednesday, June 6, 2018 1:26 PM
To: IBM-***@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

Post by Paul Gilmartin
This has been previously discussed. The main issue (as usual) is
incompatibility with an ancient bug (or feature). Specifically, temporary
dataset names such as DSN=&TMP. That's supposed to be DSN=&&TMP, but for
whatever reason, the single-& version works, unless &TMP is a symbol.

Paul Gilmartin

2018-06-06 17:47:02 UTC

This post might be inappropriate. Click to display it.

Paul Gilmartin

2018-06-06 18:52:45 UTC

Post by Seymour J Metz

Post by Paul Gilmartin
Except, does support of DSN=&TMP 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>

Seymour J Metz

2018-06-06 19:06:30 UTC

As I recall they came in with R14.

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

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

Post by Paul Gilmartin
Except, does support of DSN=&TMP 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=&name" the only use of "&" in JCL at that OS release?

-- gil

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

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

Lizette Koehler

2018-06-06 22:17:14 UTC

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-----
Sean Gleann
Sent: Wednesday, June 06, 2018 7:27 AM
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.
//OUTFILE DD DSN=BACKUP.USERDALY.D&LYYMMDD.TER,
// DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE),
// DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024
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

Steve Coalbran

2018-06-08 13:43:43 UTC

Hi Lizette,
I have a UDLC (User Defined Line Command) for our group.
DJ - Displays Job status info.
It creates a list of assignment SET statements in JCL for each of: SYSVAR, MVSVAR, MVSVAR SYMDEF, and then does the same for System Symbols (trapped from SDSF command -D SYMBOLS).
Then I extract only the ones which get SUBSTITUTION values in the Job.
I place a dummy TYPRUN=SCAN jobcard ahead.
Then it proceeds to SCAN the actual JOB JCL (omitted)...
(use a non-proportional font to read the output...)

VIEW N472730.USER.JCL(UDLCTEST) - 01.62 Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
000001 //UDLCTEST JOB (SJ,T),'UDLC TEST CASES',
000002 // MSGCLASS=X,
000003 // CLASS=A,
000004 // SCHENV=UMVS0,
000005 //* SCHENV=UMVS0NO, NOTFOUND
dj // NOTIFY=&SYSUID, SYMBOLS
000007 // TYPRUN=COPY

Here it may be issued on any Job line except those with: CLASS, MSGCLASS, or SCHENV.
These jump to trap SDSF an ÅD JOBCLASS(*),MSGCLASS,SCHENV command (Å is the JES prefix here, Å≡$)
I have a string of other UDLCs performing different functions.

gives...

VIEW SDSF SUBSTITUTION FOR SYMBOLS SYMBOL SUBSTITUTION
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
000013 //*------- SYSVARS -------------------------------------------
000017 IEFC653I SUBSTITUTION JCL - SYSUID=N472730
000047 //*------- MVSVARS -------------------------------------------
000052 IEFC653I SUBSTITUTION JCL - SYSNAME=MVS0
000058 IEFC653I SUBSTITUTION JCL - SYSCLONE=M0
000060 //*------- SYMDEFS -------------------------------------------
000061 IEFC653I SUBSTITUTION JCL - SYSPLEX=UPLEX
000063 IEFC653I SUBSTITUTION JCL - SYSALVL=2
000065 IEFC653I SUBSTITUTION JCL - SYSCLONE=M0
000067 IEFC653I SUBSTITUTION JCL - SYSNAME=MVS0
000069 IEFC653I SUBSTITUTION JCL - SYSOSLVL=Z1020200
000071 IEFC653I SUBSTITUTION JCL - SYSPLEX=UPLEX
000073 IEFC653I SUBSTITUTION JCL - SYSR1=Z51YP1
000075 IEFC653I SUBSTITUTION JCL - CCC=Z
000077 IEFC653I SUBSTITUTION JCL - CEC=32
000079 IEFC653I SUBSTITUTION JCL - CNMVER=Y
000081 IEFC653I SUBSTITUTION JCL - CNMVOL=Z51YP1
000083 IEFC653I SUBSTITUTION JCL - COMCEC=C
000085 IEFC653I SUBSTITUTION JCL - COMMSUF=00
000087 IEFC653I SUBSTITUTION JCL - COUNTRY=SE
000089 IEFC653I SUBSTITUTION JCL - DB2VER=d
000091 IEFC653I SUBSTITUTION JCL - HRDWNAME=CE32CB
000093 IEFC653I SUBSTITUTION JCL - ICSFPROG=CSFINIT
000095 IEFC653I SUBSTITUTION JCL - JESSVOL=SPL06
000097 IEFC653I SUBSTITUTION JCL - JES2APPL=SENBNJE0
000099 IEFC653I SUBSTITUTION JCL - JES2NODE=SENBSU0
000101 IEFC653I SUBSTITUTION JCL - LOC=V
000103 IEFC653I SUBSTITUTION JCL - LPARNAME=LP3206
000105 IEFC653I SUBSTITUTION JCL - MASMEM=2
000107 IEFC653I SUBSTITUTION JCL - MQEXIT=01
000109 IEFC653I SUBSTITUTION JCL - MQLVL=800C
000111 IEFC653I SUBSTITUTION JCL - MST1=0020
000113 IEFC653I SUBSTITUTION JCL - OM=22
000115 IEFC653I SUBSTITUTION JCL - OSLEVEL=020200
000117 IEFC653I SUBSTITUTION JCL - PLEXID=UP
000119 IEFC653I SUBSTITUTION JCL - PLPASUF=00
000121 IEFC653I SUBSTITUTION JCL - PLX=51
000123 IEFC653I SUBSTITUTION JCL - RMFOPT1=
000125 IEFC653I SUBSTITUTION JCL - SMFID=MVS0
000127 IEFC653I SUBSTITUTION JCL - SYSCAT=UCATUP
000129 IEFC653I SUBSTITUTION JCL - SYSNBR=0
000131 IEFC653I SUBSTITUTION JCL - SYSR2=Z51YP1
000133 IEFC653I SUBSTITUTION JCL - USRPLEX=PLEX51
000135 IEFC653I SUBSTITUTION JCL - USSROOT=Z51YP1
000137 IEFC653I SUBSTITUTION JCL - VMUSERID=+++++
000139 IEFC653I SUBSTITUTION JCL - ZVER=Y
000141 //*------- SYMBOLS -------------------------------------------
000142 IEFC653I SUBSTITUTION JCL - JOBNAME=JES2
000144 IEFC653I SUBSTITUTION JCL - SYSALVL=2
000146 IEFC653I SUBSTITUTION JCL - SYSCLONE=M0
000148 IEFC653I SUBSTITUTION JCL - SYSNAME=MVS0
000148 IEFC653I SUBSTITUTION JCL - SYSNAME=MVS0
000150 IEFC653I SUBSTITUTION JCL - SYSOSLVL=Z1020200
000152 IEFC653I SUBSTITUTION JCL - SYSPLEX=UPLEX
000154 IEFC653I SUBSTITUTION JCL - SYSR1=Z51YP1
000156 IEFC653I SUBSTITUTION JCL - ASNVER=a
000158 IEFC653I SUBSTITUTION JCL - CCC=Z
000160 IEFC653I SUBSTITUTION JCL - CEC=32
000162 IEFC653I SUBSTITUTION 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=0000
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 <IBM-***@LISTSERV.UA.EDU> on behalf of Lizette Koehler <***@MINDSPRING.COM>
Sent: 06 June 2018 22:17
To: IBM-***@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

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

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

R.S.

2018-06-07 11:23:17 UTC

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=&S1..&S2..&S3..
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

======================================================================

--
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: ***@mBank.plSąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Steve Horein

2018-06-07 12:39:35 UTC

I used this JCL:
//<job card>
//*
//SYMBOLS EXPORT SYMLIST=*
//STEP1 EXEC PGM=IEFBR14
//*
//ISUP DD DISP=(NEW,CATLG),
// DSN=SH71167.IS.ACTIVE.ON.&SYSNAME..D&LYYMMDD.,
// 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 0000

Are you specifying "EXPORT SYMLIST" in your JCL?

Peter Hunkeler

2018-06-07 19:34:19 UTC

Post by Steve Horein
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Steve Horein

2018-06-07 23:05:40 UTC

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.

Post by Peter Hunkeler

Post by Steve Horein
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,

Paul Gilmartin

2018-06-07 13:50:56 UTC

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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Jesse 1 Robinson

2018-06-09 18:41:54 UTC

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
***@sce.com

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

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

Paul Gilmartin

2018-06-09 22:05:08 UTC

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.

Post by Paul Gilmartin

Except, does support of DSN=&TMP 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>

(See Page 23. There were *no* symbols in JCL then!)

-- gil

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

Paul Gilmartin

2018-06-09 22:14:48 UTC

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

Except, does support of DSN=&TMP 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>

(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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Paul Gilmartin

2018-06-09 23:06:06 UTC

Post by Seymour J Metz

Post by Paul Gilmartin
Except, does support of DSN=&TMP 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>

OK. That says use DSNAME=&name. R21.7 and later say use DSNAME=&&dsname.
What happens if JCL performs symbol substitution? For example

// SET A1='&TEMP'
// SET A2='&&TEMP'
//*
//STEP EXEC PGM=IEFBR14
//D1 DD DSN=&A1 * Should be unsupported; only one ampersand after substitution.
//D1 DD DSN=&A2 * 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

Seymour J Metz

2018-06-10 21:17:59 UTC

Post by Paul Gilmartin
What happens if JCL performs symbol substitution?

I would expect that to be a valid temporary reference.

Post by Paul Gilmartin
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, &&dsname evaluates to &dsname, which is a valid temporary as long as dsname adheres to the restrictions.

Post by Paul Gilmartin
// SET A2='&&TEMP'

I would expect that to be an invalid temporary reference.

Post by Paul Gilmartin
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 <IBM-***@listserv.ua.edu> on behalf of Paul Gilmartin <0000000433f07816-dmarc-***@listserv.ua.edu>
Sent: Saturday, June 9, 2018 7:05 PM
To: IBM-***@listserv.ua.edu
Subject: Re: Use of dynamic system symbols in JCL

Post by Paul Gilmartin

Post by Paul Gilmartin
Except, does support of DSN=&TMP 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>

Paul Gilmartin

2018-06-10 19:15:20 UTC

This is the JCL Reference for z/OS 2.3 (page 183)
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=&xxxxxxxx), 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='&TEMP'
//SYSUT2 DD DSN=&TTT,...

-- gil

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

Gerhard Adam

2018-06-10 20:57:55 UTC