Re: Symbols and ampersands

2016-09-19 Thread Steve Smith
I did try it, and I agree with Gil, and would add that the whole EXPORT facility is rather bizarre. First, the SYSUT1 SYSIN received 'AFTER' for the &S symbol. I suppose that means it is substituted sometime after the JCL is interpreted. Maybe it was easiest to implement it this way (along with w

Re: Symbols and ampersands

2016-09-16 Thread Paul Gilmartin
On Fri, 16 Sep 2016 23:37:57 +, Frank Swarbrick wrote: > >Maybe this isn't a real enough situation to matter, but it seems odd to me. >... Also, I was astonished by the behavior of (try it!) //STEP EXEC PGM=IEBGENER //SYSIN DD * //SYSPRINT DD SYSOUT=(,) //* // EXPORT SYMLIST=S

Re: Symbols and ampersands

2016-09-16 Thread Paul Gilmartin
On Fri, 16 Sep 2016 23:37:57 +, Frank Swarbrick wrote: >We just upgraded from z/OS 1.13 to z/OS 2.2 and I'm experimenting with using >symbols in in-stream data. Here is some JCL: > >//SYSUT1 DD *,SYMBOLS=(EXECSYS,SYMBLOG) >&&SYSNAME = &SYSNAME >... >The output is as follows: ... >&

Symbols and ampersands

2016-09-16 Thread Frank Swarbrick
We just upgraded from z/OS 1.13 to z/OS 2.2 and I'm experimenting with using symbols in in-stream data. Here is some JCL: //SYMBTST1 JOB ,'SYMBOLS TESTING',NOTIFY=&SYSUID // EXPORT SYMLIST=SYM1 // SET SYM1='THIS IS A TEST' // SET COPYPGM=IEBGENER //COPY EXEC PGM=©PGM