Re: GENERATED STATEMENT!?

[Shmuel Metz (Seymour J.)]

In
,
on 05/27/2015
   at 04:54 PM, J O Skip Robinson  said:

>//SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)

>There is no space between asterisk and ampersand. Could that be
>right?

That depends on whether the JES expands the symbols or only the
Converter does.

If the first, it looks not only right but necessary. If the second,
BAD.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: GENERATED STATEMENT!?

[Shmuel Metz (Seymour J.)]

In <2133628351749565.wa.paulgboulderaim@listserv.ua.edu>, on
05/27/2015
   at 11:37 AM, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> said:

>Where does "41 //SYSIN DD *   GENERATED STATEMENT"
>come from? 

It used to come from the R/I, but in MVS I'm not sure if it's C/I or
JES[2|3].

>What does it mean? 

What it's always meant.

>(I had no stray data cards.)

Are you a betting man?

 1. Reproduce the problem with a program that echoes SYSIN

 2. Post the input here

 3. Look at SYSIN form SDSF.
 
 4. Check whether C/I or JES
a. Handles SYSIN
b. Expands symbols.

The most likely explanation is that JES handles SYSIN before the
symbols are substituted. 
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see <http://patriot.net/~shmuel/resume/brief.html> 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: GENERATED STATEMENT!?

[Itschak Mugzach]

Which job? This us a query scheduled frim a network pc.
בתאריך 28 במאי 2015 14:51,‏ "Steve Coalbran"  כתב:

> I missed the original of this.
> Is the original JCL for the job available?
> /steve
>
>
>
> From:   Doron Geva 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date:   2015-05-28 12:26
> Subject:Re: GENERATED STATEMENT!?
> Sent by:IBM Mainframe Discussion List 
>
>
>
> It seems like JES error.
> JES is the one that add the "//SYSIN DD *   GENERATED
> STATEMENT" before calling the MVS converter
> JES requires that the "*" will be separated by a comma or blank from the
> next JCL keyword
>
> ?Doron?
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
>
>
> Såvida annat inte anges ovan: / Unless stated otherwise above:
> IBM Svenska AB
> Organisationsnummer: 556026-6883
> Adress: 164 92 Stockholm
>
> --
> 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: GENERATED STATEMENT!?

[Charles Mills]

https://www.google.com/search?q=generated+statement+paul+gilmartin 

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Thursday, May 28, 2015 5:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GENERATED STATEMENT!?

Steve Coalbran wrote:

>Predictably stupid response. 

Not stupid response! In fact, it is the only place. [1] 

>Where do I find the archives?

Look in https://listserv.ua.edu/cgi-bin/wa?INDEX and scroll down for IBM-MAIN.

Groete / Greetings
Elardus Engelbrecht

[1] - Google Groups also mirrors this, but discussions there are not mirrored 
back to the main IBM-MAIN site.

--
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: GENERATED STATEMENT!?

[Lizette Koehler]

You could do an internet search for IBMMAIN ARCHIVES

Or use this URL
https://listserv.ua.edu/archives/ibm-main.html

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Steve Coalbran
> Sent: Thursday, May 28, 2015 5:27 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: GENERATED STATEMENT!?
> 
> Predictably stupid response.
> Where do I find the archives?
> /Steve  :-/
> 
> 
> 
> From:   Paul Gilmartin <000433f07816-dmarc-
> requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date:   2015-05-28 14:01
> Subject:Re: GENERATED STATEMENT!?
> Sent by:IBM Mainframe Discussion List 
> 
> 
> 
> On Thu, 28 May 2015 13:51:26 +0200, Steve Coalbran wrote:
> 
> >I missed the original of this.
> >Is the original JCL for the job available?
> >
> Yes.  It's in the archives.
> 
> -- gil

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

Re: GENERATED STATEMENT!?

[Elardus Engelbrecht]

Steve Coalbran wrote:

>Predictably stupid response. 

Not stupid response! In fact, it is the only place. [1] 

>Where do I find the archives?

Look in https://listserv.ua.edu/cgi-bin/wa?INDEX and scroll down for IBM-MAIN.

Groete / Greetings
Elardus Engelbrecht

[1] - Google Groups also mirrors this, but discussions there are not mirrored 
back to the main IBM-MAIN site.

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

Re: GENERATED STATEMENT!?

[Steve Coalbran]

Predictably stupid response. 
Where do I find the archives?
/Steve  :-/



From:   Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Date:   2015-05-28 14:01
Subject:    Re: GENERATED STATEMENT!?
Sent by:IBM Mainframe Discussion List 



On Thu, 28 May 2015 13:51:26 +0200, Steve Coalbran wrote:

>I missed the original of this.
>Is the original JCL for the job available?
> 
Yes.  It's in the archives.

-- gil

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




Såvida annat inte anges ovan: / Unless stated otherwise above:
IBM Svenska AB
Organisationsnummer: 556026-6883
Adress: 164 92 Stockholm

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

Re: GENERATED STATEMENT!?

[Steve Coalbran]

Clearly this is not the case: 
   "JES requires that the "*" will be separated by a comma or blank from 
the next JCL keyword"

I knew this because just today I discovered the SYMBOLS,EXPORT SYMLIST JCL 
functions.
Well I have only been writing it for 40 years. 
I'm sure it wasn't there in OS/360 ?! :-/ 

//K248610S JOB (BSA0,P,B),'SYMBOLS TRY',CLASS=A,MSGCLASS=O, 
// NOTIFY=K248610,REGION=0M 
//*
// EXPORT SYMLIST=(SYSIN)   
// SET LIB='K248610.MBM.JCL'
// SET CPY=&LIB..COPY   
// SET DEL='(MOD,DELETE),SPACE=(TRK,0)' 
// SET SYSIN='  COPY I=I,O=O'   
//*
//CLEANUP  EXEC PGM=IEFBR14 
//DELETE01 DD DISP=&DEL,DSN=&CPY
//*
//COPYLIB  EXEC PGM=IEBCOPY 
//IDD DISP=SHR,DSN=&LIB 
//ODD DSN=&CPY, 
//DISP=(,CATLG,DELETE), 
//REFDD=*.I,
//DCB=*.I,  
//SPACE=(TRK,(25,5,30),RLSE),   
//DSNTYPE=LIBRARY   
//SYSPRINT DD SYSOUT=*  
//SYSOUT   DD SYSOUT=*  
//SYSINDD *,SYMBOLS=EXECSYS <=== COMMA FOLLOWS DD *
  &SYSIN
//  
//*
//E1   EXPORT SYMLIST=(JOBLIB)  
//S1   SET JOBLIB=&SYSUID..MBM.JCL  
//TSO  EXEC PGM=IKJEFT1A,COND=(0,LE)
//SYSTSPRT DD SYSOUT=*  
//SYSTSIN  DD *,SYMBOLS=EXECSYS 
  %JOBLIB &JOBLIB   
//* 
//*
//* 
/Steve



From:   Doron Geva 
To: IBM-MAIN@LISTSERV.UA.EDU
Date:   2015-05-28 12:26
Subject:Re: GENERATED STATEMENT!?
Sent by:IBM Mainframe Discussion List 



It seems like JES error.
JES is the one that add the "//SYSIN DD *   GENERATED
STATEMENT" before calling the MVS converter
JES requires that the "*" will be separated by a comma or blank from the
next JCL keyword

?Doron?

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




Såvida annat inte anges ovan: / Unless stated otherwise above:
IBM Svenska AB
Organisationsnummer: 556026-6883
Adress: 164 92 Stockholm

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

Re: GENERATED STATEMENT!?

[Paul Gilmartin]

On Thu, 28 May 2015 13:51:26 +0200, Steve Coalbran wrote:

>I missed the original of this.
>Is the original JCL for the job available?
> 
Yes.  It's in the archives.

-- gil

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

Re: GENERATED STATEMENT!?

[Steve Coalbran]

I missed the original of this.
Is the original JCL for the job available?
/steve



From:   Doron Geva 
To: IBM-MAIN@LISTSERV.UA.EDU
Date:   2015-05-28 12:26
Subject:Re: GENERATED STATEMENT!?
Sent by:IBM Mainframe Discussion List 



It seems like JES error.
JES is the one that add the "//SYSIN DD *   GENERATED
STATEMENT" before calling the MVS converter
JES requires that the "*" will be separated by a comma or blank from the
next JCL keyword

?Doron?

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




Såvida annat inte anges ovan: / Unless stated otherwise above:
IBM Svenska AB
Organisationsnummer: 556026-6883
Adress: 164 92 Stockholm

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

Re: GENERATED STATEMENT!?

[Doron Geva]

It seems like JES error.
JES is the one that add the "//SYSIN DD *   GENERATED
STATEMENT" before calling the MVS converter
JES requires that the "*" will be separated by a comma or blank from the
next JCL keyword

​Doron​

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

Re: GENERATED STATEMENT!?

[Alan Haff]

That doesn't work either. As I said to Gil off list, the problem appears to be 
that the JCL parser is generating DD cards for instream data before it does 
symbol substitution. It should work the other way around: do symbol 
substitution first then generate DD cards as needed.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Farley, Peter x23353
Sent: Wednesday, May 27, 2015 13:16
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GENERATED STATEMENT!?

I would use this instead:

// SET INSTRM='* '  USE THIS ONE FOR PRE-JES2 2.1
// SET INSTRM='*,' USE THIS ONE FOR JES2 2.1
. . . .
//SYMS2 DD  &INSTRM.SYMBOLS=(EXECSYS,LOGDD2)

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, May 27, 2015 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GENERATED STATEMENT!?

In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=    GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)

I hate JCL!

-- gil

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

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
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: GENERATED STATEMENT!?

[Farley, Peter x23353]

I would use this instead:

// SET INSTRM='* '  USE THIS ONE FOR PRE-JES2 2.1
// SET INSTRM='*,' USE THIS ONE FOR JES2 2.1
. . . .
//SYMS2 DD  &INSTRM.SYMBOLS=(EXECSYS,LOGDD2)

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, May 27, 2015 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GENERATED STATEMENT!?

In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=        GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)

I hate JCL!

-- gil

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

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


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

Re: GENERATED STATEMENT!?

[Andy Higgins]

Would

//SYMS2 DD *,DSN=&&XX&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)

do?

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

Re: GENERATED STATEMENT!?

[Gross, Randall [PRI-1PP]]

From APAR OA45005:

Exported symbolic parameters must be set to a value in the
   job stream after the EXPORT statement.  Exported symbol
   values are resolved to the last value set prior to or
   within the current job step. JCL Converter processing
   generates EXPORT EXPSET statements to manage how exported
   JCL symbol values are resolved.  These statements appear
   in the job log. Reviewing the placement of EXPORT EXPSET
   statements in the job log may be helpful in understanding
   exported symbol resolution for a given job.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, May 27, 2015 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GENERATED STATEMENT!?

In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=    GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)

I hate JCL!

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu<mailto: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

IEB351I (was : GENERATED STATEMENT!?)

[Paul Gilmartin]

On 2015-05-27 13:46, Gross, Randall [PRI-1PP] wrote:
> If it makes you feel any better, I can reproduce your exact error on my 2.1 
> system
>  
Misery loves company?

And this one:  As submitted:

//JCLSYMJOB  505303JOB,'Paul Gilmartin',
// MSGLEVEL=(1,1),REGION=16385K
//*
//* Doc: experiment with instream symbol substitution.
//*
//USERCOUTPUT JESDS=ALL,DEFAULT=YES,
//  CLASS=R,PAGEDEF=V0648Z,CHARS=GT12
//*
//  EXPORT SYMLIST=*
//*
//*.+|+|+|+|+|+|+|+|
//  SET X='This is a long symbol value.'
//STEP1EXEC  PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=(,)
//SYSIN DD  DUMMY
//SYSUT2DD  SYSOUT=(,)
//SYSUT1DD  *,SYMBOLS=CNVTSYS,DCB=LRECL=222
Lots of data to fill up a line, followed by a long symbol to see &X.
//*.+|+|+|+|+|+|+|+|
//
In SYSPRINT:
* TOP OF DATA 
***
DATA SET UTILITY - GENERATE
IEB352I WARNING: ONE OR MORE OF THE OUTPUT DCB PARMS COPIED FROM INPUT

IEB351I I/O ERROR ,JCLSYM  ,STEP1   ,JES ,D,SYSUT1  ,READ  ,WRONG LEN 
RECRD,**,BSAM
 BOTTOM OF DATA 
*

I might understand it if my coded LRECL weren't ample to hold the line
after substitution.

-- gil

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

Re: GENERATED STATEMENT!?

[Gross, Randall [PRI-1PP]]

If it makes you feel any better, I can reproduce your exact error on my 2.1 
system

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, May 27, 2015 2:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GENERATED STATEMENT!?

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 //LOGDD1DD  SYSOUT=(,) 
 000181 //* 
 000182 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2) 
 000183 Try &SYMVAL
 000184 Short line 
 000185 //LOGDD2DD  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 
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: GENERATED STATEMENT!?

[Paul Gilmartin]

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 //LOGDD1DD  SYSOUT=(,) 
 000181 //* 
 000182 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2) 
 000183 Try &SYMVAL 
 000184 Short line 
 000185 //LOGDD2DD  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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GENERATED STATEMENT!?

[Lizette Koehler]

One options I like is the HILITE in EDIT or VIEW for JCL.

It will usually show me most of my JCL issues.

While in EDIT or VIEW type HILITE on command line, select 11 - JCL

Lizette



-Original Message-
>From: retired mainframer 
>Sent: May 27, 2015 10:25 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: GENERATED STATEMENT!?
>
>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 /*.
>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>> Behalf Of Paul Gilmartin
>> Sent: Wednesday, May 27, 2015 9:37 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: GENERATED STATEMENT!?
>> 
>> In my JESJCL listing I see:
>>   ...
>>33 //  EXPORT SYMLIST=*
>>34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
>>35 //IFSYMEXPORT EXPSET=GENERATED 
>> STATEMENT
>>    36 //  SET  SYMVAL='Symbol value longer than name.'
>>37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED
>> STATEMENT
>>   //*
>>38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
>>39 //LOGDD1DD  SYSOUT=(,)
>>   //*
>>    40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
>>   IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
>>    41 //SYSIN DD *   GENERATED STATEMENT
>>42 //LOGDD2DD  SYSOUT=(,)
>>   //*
>>43 //
>> 
>> Where does "41 //SYSIN DD *   GENERATED STATEMENT"
>> come from?  What does it mean?  (I had no stray data cards.)
>> 
>> I hate JCL!
>> 
>> -- gil

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

Re: GENERATED STATEMENT!?

[retired mainframer]

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 /*.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Wednesday, May 27, 2015 9:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: GENERATED STATEMENT!?
> 
> In my JESJCL listing I see:
>   ...
>33 //  EXPORT SYMLIST=*
>34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
>35 //IFSYM    EXPORT EXPSET=GENERATED 
> STATEMENT
>36 //  SET  SYMVAL='Symbol value longer than name.'
>    37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED
> STATEMENT
>   //*
>38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
>39 //LOGDD1DD  SYSOUT=(,)
>   //*
>40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
>   IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
>41 //SYSIN DD *   GENERATED STATEMENT
>42 //LOGDD2DD  SYSOUT=(,)
>   //*
>43 //
> 
> Where does "41 //SYSIN DD *   GENERATED STATEMENT"
> come from?  What does it mean?  (I had no stray data cards.)
> 
> I hate JCL!
> 
> -- 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: GENERATED STATEMENT!?

[John McKown]

On Wed, May 27, 2015 at 11:54 AM, J O Skip Robinson <
jo.skip.robin...@sce.com> 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?
>

​Sure. If IFSYM is equal to a 0-length string like: // SET IFSYM='' ​, then
the phrase: ",SYMBOLS=(EXECSYS,LOGDD)" will abut the * and be recognized as
part of the JCL statement as an operator. OTOH, if IFSYM is one or more
blanks: // SET IFSYM=' ', then the phrase mentioned will be separated from
the * by a space and be recognized as a comment. We do this all the time
for "DUMMYing" out a DD statement:

//SYSUT2 DD &DUMMY.DSN=

If we have a JCL statement: "// SET DUMMY='DUMMY,' " then the DD is a DD
DUMMY. If we have "// SET DUMMY='' ", then the DD references the
appropriate DSN.



>
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 626-302-7535 Office
> 323-715-0595 Mobile
> jo.skip.robin...@sce.com
>
> --
My sister opened a computer store in Hawaii. She sells C shells down by the
seashore.

If someone tell you that nothing is impossible:
Ask him to dribble a football.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

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

Re: GENERATED STATEMENT!?

[Staller, Allan]

Appears to be a missing comma   on statement 40


40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)

s/b

40 //SYMS2 DD  *,&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  ^

HTH,


In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=        GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN     DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)


I hate JCL!

-- 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: GENERATED STATEMENT!?

[J O Skip Robinson]

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?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, May 27, 2015 9:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GENERATED STATEMENT!?

In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=        GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)

I hate JCL!

-- gil

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

Re: GENERATED STATEMENT!?

[David Betten]

I there a blank line between SYSMS2 and LOGDD2 statements?


Have a nice day,
Dave Betten
z/OS Performance Specialist - HiPODS
Open Technology and Cloud Performance
IBM Corporation
email:  bet...@us.ibm.com
1-301-240-3809

IBM Mainframe Discussion List  wrote on 
05/27/2015 12:37:18 PM:

> From: Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 05/27/2015 12:37 PM
> Subject: GENERATED STATEMENT!?
> Sent by: IBM Mainframe Discussion List 
> 
> In my JESJCL listing I see:
>   ...
>33 //  EXPORT SYMLIST=*
>34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
>    35 //IFSYMEXPORT EXPSET= 
> GENERATED STATEMENT
>36 //  SET  SYMVAL='Symbol value longer than name.'
>37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... 
> GENERATED STATEMENT
>   //*
>38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
>39 //LOGDD1DD  SYSOUT=(,)
>   //*
>40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
>   IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
>41 //SYSIN DD *   GENERATED STATEMENT
>42 //LOGDD2    DD  SYSOUT=(,)
>   //*
>43 //
> 
> Where does "41 //SYSIN DD *   GENERATED STATEMENT"
> come from?  What does it mean?  (I had no stray data cards.)
> 
> I hate JCL!
> 
> -- 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

GENERATED STATEMENT!?

[Paul Gilmartin]

In my JESJCL listing I see:
  ...
   33 //  EXPORT SYMLIST=*
   34 //  SET  IFSYM=''  (Blank for pre-JES2 2.1.)
   35 //IFSYMEXPORT EXPSET=    GENERATED 
STATEMENT
   36 //  SET  SYMVAL='Symbol value longer than name.'
   37 //SYMVAL   EXPORT EXPSET=Symbol value longer than... GENERATED 
STATEMENT
  //*
   38 //SYMS1 DD  *,SYMBOLS=(EXECSYS,LOGDD1)
   39 //LOGDD1DD  SYSOUT=(,)
  //*
   40 //SYMS2 DD  *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2)
  IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2)
   41 //SYSIN DD *   GENERATED STATEMENT
   42 //LOGDD2DD  SYSOUT=(,)
  //*
   43 //

Where does "41 //SYSIN DD *   GENERATED STATEMENT"
come from?  What does it mean?  (I had no stray data cards.)

I hate JCL!

-- gil

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