Re: PARMDD and Symbols in a Started PROC

2019-02-15 Thread Seymour J Metz
From: IBM Mainframe Discussion List on behalf of Tom Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu> Sent: Thursday, February 14, 2019 4:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC On Thu, 14 Feb 2019 13:07:07 -0800, Charles Mills wrote:

Re: PARMDD and Symbols in a Started PROC

2019-02-15 Thread Allan Staller
SYSSYM=ALLOW in JESPARMS? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, February 14, 2019 12:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC OK, I am making some progress. I got past the JCL error

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Paul Gilmartin
On Thu, 14 Feb 2019 14:28:35 -0600, Tom Marchant wrote: >On Thu, 14 Feb 2019 13:54:58 -0600, Paul Gilmartin wrote: > >>>// SET PARM2=&PARM2 >> >>Doesn't this run afoul of a rule elsewhere in the Ref. that symbols >>are not to be defined in terms of other symbols. > >What rule is that? Where is i

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
dge Sent: Thursday, February 14, 2019 1:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC I'm keeping this as my set of examples - Thanks Charles Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile jerry.whitteri...

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Tom Marchant
On Thu, 14 Feb 2019 13:07:07 -0800, Charles Mills wrote: >I think I could have done > >//jobname JOB ... >// EXPORT SYMLIST=* >//procname PROC ... Maybe. I had a similar problem a few years ago, but in my case, I had a PROC that was used in some jobs. I don't remember if I tried using the EXPORT

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Jerry Whitteridge
gt; To: IBM-MAIN@LISTSERV.UA.EDU > Date: 02/14/2019 02:07 PM > Subject: Re: PARMDD and Symbols in a Started PROC > Sent by: IBM Mainframe Discussion List > > @Tom's got it. Thanks. > > EXPORT works in a PROC and so forth but must come before the > definition of the s

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
ERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC >The start fails with a JCL error and IEFC657I THE SYMBOL x WAS NOT USED >for every single one of the symbols. > .. Tnat message has struck me as insane design since I first encountered it over 40 years ago. Completely ba

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
ry 14, 2019 11:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC On Thu, 14 Feb 2019 11:01:44 -0800, Charles Mills wrote: >> // EXPORT gets specified first before any // SET stmts > >How do I do that in a PROC where the SETs are implicit in the PROC

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Tom Marchant
On Thu, 14 Feb 2019 13:54:58 -0600, Paul Gilmartin wrote: >>// SET PARM2=&PARM2 > >Doesn't this run afoul of a rule elsewhere in the Ref. that symbols >are not to be defined in terms of other symbols. What rule is that? Where is it documented? -- Tom Marchant

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Paul Gilmartin
On Thu, 14 Feb 2019 10:57:06 -0800, Charles Mills wrote: > ... >Would it kill IBM to have some meaningful examples in the JCL reference? > The JCL Ref. contains a section: Using symbols in started task JCL Example: using JCL symbols Prepare to be disappointed. I see no meaningful exam

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Paul Gilmartin
On Thu, 14 Feb 2019 10:02:26 -0800, Charles Mills wrote: > ... >I have a started PROC with the typical sort of symbols declared on the PROC >statement. >... >The second step contains //stepname EXEC PGM=program,PARMDD=MYDDNAME > >//MYDDNAME DD *,SYMBOLS=JCLONLY > >I have a // EXPORT SYMLIST=*. I tr

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Tom Marchant
On Thu, 14 Feb 2019 11:01:44 -0800, Charles Mills wrote: >> // EXPORT gets specified first before any // SET stmts > >How do I do that in a PROC where the SETs are implicit in the PROC >statement, which is the very first statement? > >//procname PROC PARM1=value,PARM2=value Try this: //procname

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Farley, Peter x23353
rsday, February 14, 2019 2:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC > // EXPORT gets specified first before any // SET stmts How do I do that in a PROC where the SETs are implicit in the PROC statement, which is the very first statement? //procname PROC PAR

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Rich Tabor
ame PROC PARM1=value,PARM2=value Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rich Tabor Sent: Thursday, February 14, 2019 10:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC Hadn

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
ist [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rich Tabor Sent: Thursday, February 14, 2019 10:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC Hadn't seen SYMLIST=* learn something new every day... // EXPORT gets specified first before any // SET stmts -

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Rich Tabor
Rich Tabor Sent: Thursday, February 14, 2019 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC Do you really have // EXPORT SYMLIST=* or something like // EXPORT SYMLIST=(PARM1,PARM2) -- For IBM

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC Do you really have // EXPORT SYMLIST=* or something like // EXPORT SYMLIST=(PARM1,PARM2) -- For IBM-MAIN subscribe / signoff / archive access

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
OK, I am making some progress. I got past the JCL error by coding a bunch of dummy // SET FOO=&PARM1 statements. I am not getting errors from the program. I can see that no symbol substitution has been done. Is there any restriction on DD *,SYMBOLS in a started PROC? Where should the EXPORT stat

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
Sent: Thursday, February 14, 2019 10:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC Do you really have // EXPORT SYMLIST=* or something like // EXPORT SYMLIST=(PARM1,PARM2) -- For IBM-MAIN subs

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
-MAIN@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC How do you have your parms set in the PARMDD input? I was told each parm needs to be on a separate line. Not sure how accurate that is. Have you tried individual lines? Which way is your input coded? //MYDDNAME DD

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Lizette Koehler
Try doing each one on one line Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Charles Mills > Sent: Thursday, February 14, 2019 11:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: PARMDD and Symbols in a Started PROC > > C

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Rich Tabor
@LISTSERV.UA.EDU Subject: Re: PARMDD and Symbols in a Started PROC How do you have your parms set in the PARMDD input? I was told each parm needs to be on a separate line. Not sure how accurate that is. Have you tried individual lines? Which way is your input coded? //MYDDNAME DD *,SYMBOLS=JCLONLY

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Charles Mills
: PARMDD and Symbols in a Started PROC How do you have your parms set in the PARMDD input? I was told each parm needs to be on a separate line. Not sure how accurate that is. Have you tried individual lines? Which way is your input coded? //MYDDNAME DD *,SYMBOLS=JCLONLY PARM1,PARM2,PARM3

Re: PARMDD and Symbols in a Started PROC

2019-02-14 Thread Lizette Koehler
How do you have your parms set in the PARMDD input? I was told each parm needs to be on a separate line. Not sure how accurate that is. Have you tried individual lines? Which way is your input coded? //MYDDNAME DD *,SYMBOLS=JCLONLY PARM1,PARM2,PARM3,etc Or //MYDDNAME DD *,SYMBOLS=J