The EXPORT needs to precede the PROC statement, but I am not sure if that is legal for a STARTed PROC. In my experience at z/OS level 2.2, for regular batch JCL you must put the EXPORT prior to any SET's **and** prior to any PROC *execution* in order to catch the PROC default values.
And I agree it would be helpful for IBM to supply specific examples for this area. Most of what I know about the subject is via trial-and-error. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Thursday, 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 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't seen SYMLIST=* learn something new every day... // EXPORT gets specified first before any // SET stmts -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Charles Mills Sent: Thursday, February 14, 2019 10:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] PARMDD and Symbols in a Started PROC I tried EXPORT SYMLIST=(PARM1,PARM2) No difference. Would it kill IBM to have some meaningful examples in the JCL reference? 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: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) -- 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
