On Wed, 27 May 2015 12:41:36 -0400, David Betten wrote:
>I[s] there a blank line between SYSMS2 and LOGDD2 statements?
>
I said:
>> From: Paul Gilmartin
>> Date: 05/27/2015 12:37 PM
>>
>> ... (I had no stray data cards.)
On 2015-05-27 10:54, J O Skip Robinson wrote:
> I copy pasted the JCL into a real editor, i.e. ISPF, and noticed an oddity in
> this line:
>
> //SYMS2 DD *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
>
> There is no space between asterisk and ampersand. Could that be right?
>
Yes.
On 2015-05-27 10:56, Staller, Allan wrote:> Appears to be a missing comma on
statement 40
>
There is not.
> 40 //SYMS2 DD *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
>
> s/b
>
> 40 //SYMS2 DD *,&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
> ^
>
> HTH,
>
It doesn't
On Wed, 27 May 2015 10:25:13 -0700, retired mainframer wrote:
>Submit the job in hold status and use SDSF to look at the data card(s) in the
>SYSIN "member". Then find that data in the dataset you submitted and
>determine why it was not recognized as JCL. One common reason is that columns
>1 and 2 do not contain // or /*.
>
Even better, copied and pasted from SDSF SJ panel:
...
000172 //*
000173 // EXPORT SYMLIST=*
000174 // SET IFSYM='' (Blank for pre-JES2 2.1.)
000175 // SET SYMVAL='Symbol value longer than name.'
000176 //*
000177 //SYMS1 DD *,SYMBOLS=(EXECSYS,LOGDD1)
000178 Try &SYMVAL
000179 Preset LRECL with longer line .........
000180 //LOGDD1 DD SYSOUT=(,)
000181 //*
000182 //SYMS2 DD *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
000183 Try &SYMVAL
000184 Short line
000185 //LOGDD2 DD SYSOUT=(,)
000186 //*
000187 //
...
Do you see anything wrong?
On Wed, 27 May 2015 12:14:42 -0500, John McKown wrote:
>
> ... We do this all the time ...
>
Thank you for understanding JCL syntax better than most of the followups.
--gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
