The syntax using stepname (not procstep name) is used because there is no
nested procedure in that refer back. By that I mean, the reference is not to a
DD within a proc invoked by the procedure. That is how I've always viewed it.
I reread the JCL manual concerning backward references and it
first introduced.
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Wednesday, July 11, 2018 3:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Overrides (was: REXX as JCL replacement)
On Wed, 11 Jul 2018 19
On Wed, 11 Jul 2018 19:30:16 +, Clifford McNeill wrote:
>The proc author probably wouldn't do in that manner. Look at excerpt below,
>notice how LKED SYSLIN is referencing a dsn from a previous step?
>
,DELETE)
Cliff McNeill
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, July 11, 2018 2:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Overrides (was: REXX as JCL replacement)
O
On Wed, 11 Jul 2018 10:35:08 -0700, Lizette Koehler wrote:
>I would include the caveat
>
>Even though it is available, do not use Nested procs. Trying to override a
>proc within a proc within a proc .. rarely succeeds.
>
I can't decide whether the author of the original RFE overlooked a
