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 in each of the jobs that invoked the 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) IIRC, when you code a started job, you don't use PROC. When you start the task, specifying PARM1=value1,etc., it inserts a SET statement after the JOB card. I don't know how you would code default values for your parameters. >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,... I did something like that too, but then I found out (at the suggestion of IBM) that I could use the same symbol name, like this: // SET PARM1=&PARM1 It looks strange, but it works. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
