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 statement go? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Thursday, February 14, 2019 10:02 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PARMDD and Symbols in a Started PROC I know I am late to the party but I am just dipping my toe into the LONGPARM pool. I have a started PROC with the typical sort of symbols declared on the PROC statement. The PROC is two jobsteps, FWIW. The second step contains //stepname EXEC PGM=program,PARMDD=MYDDNAME And //MYDDNAME DD *,SYMBOLS=JCLONLY Various references to the PROC symbols /* I have a // EXPORT SYMLIST=*. I tried it before the first step, in the first step, and in the second step. The start fails with a JCL error and IEFC657I THE SYMBOL xxxxx WAS NOT USED for every single one of the symbols. z/OS V2R3. The program is APF authorized and linked with LONGPARM=YES. What am I doing wrong? Or is the big picture of what I am attempting to do hopeless? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
