Paul,

No, the PROC referback does NOT need to know the step name that invoked the 
PROC.  It is the nearest prior procstepname that is referenced, so multiple 
compile PROC executions in the same job work just fine and refer to the correct 
dataset.

AFAIK , that's been the case since PROC's were 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:30:16 +0000, 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?
>------------------------------------------------------------------------
>SYS1.PROCLIB(IBMZCPLG) - 01.01                          Columns 0000
> ===>                                                          Scroll ==
>//*********************************************************************
>//* PRE-LINK-EDIT STEP
>//*********************************************************************
>//PLKED    EXEC PGM=EDCPRLK,COND=(8,LT,PLI)
>//    ...
>//SYSMOD   DD  DSN=&&PLNK,DISP=(,PASS),UNIT=SYSALLDA,SPACE=(CYL,(1,1)),
>//             DCB=(RECFM=FB,LRECL=80,BLKSIZE=&SYSLBLK)
>//*********************************************************************
>//* LINK-EDIT STEP
>//*********************************************************************
>//LKED     EXEC PGM=IEWL,PARM='XREF',COND=((8,LT,PLI),(8,LE,PLKED))
>//    ...
>//SYSLIN   DD  DSN=*.PLKED.SYSMOD,DISP=(OLD,DELETE)
> 
Suppose the end user calls this with:
//FOOBAR  EXEC  PROC=IBMZXPLG,...

Doesn't the referback need to cite the job step, as in:
//SYSLIN   DD  DSN=*.FOOBAR.PLKED.SYSMOD,DISP=(OLD,DELETE)

... but the author of the PROC can't know a priori the callers jobstep name.

--


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

Reply via email to