NP Jerry. I *suspect* what Tom suggested would work and would be simpler than what I did.
// SET PARM1=&PARM1 Rather than // SET $PARM1=&PARM1 Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jerry Whitteridge Sent: Thursday, February 14, 2019 1:16 PM To: [email protected] Subject: Re: PARMDD and Symbols in a Started PROC I'm keeping this as my set of examples - Thanks Charles <grin> Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile [email protected] IBM Services IBM Mainframe Discussion List <[email protected]> wrote on 02/14/2019 02:07:07 PM: > From: Charles Mills <[email protected]> > To: [email protected] > Date: 02/14/2019 02:07 PM > Subject: Re: PARMDD and Symbols in a Started PROC > Sent by: IBM Mainframe Discussion List <[email protected]> > > @Tom's got it. Thanks. > > EXPORT works in a PROC and so forth but must come before the > definition of the symbols it exports. (Again, seems kind of > backwards, but what do I know?) > > I think I could have done > > //jobname JOB ... > // EXPORT SYMLIST=* > //procname PROC ... > > But I have never coded a started PROC with a JOB (and I know you > can, but it was just a wormhole I did not want to go down at this > moment) so I did more or less what Tom suggests. > > //procname PROC PARM1=value1,PARM2=value2 > // EXPORT SYMLIST=* > // SET $PARM1=PARM1 > // SET $PARM2=PARM2 > ... > //MYPARMDD DD *,SYMBOLS=JCLONLY > $PARM1,$PARM2,... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
