One caveat Had an experience running under test The program I was running had the same name as the one I was attaching to
The attach had taskib and dcb pointing to a different library because the parent task was linked as REUS it attached the copy in core Had to relink without REUS to get library from DCB= TASKLIB= Thanks > On Feb 7, 2021, at 12:53 PM, Seymour J Metz <[email protected]> wrote: > > No, but IMHO a warn option would be highly desirable. > > Why JOB instead of EXEC? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Paul Gilmartin [[email protected]] > Sent: Sunday, February 7, 2021 12:46 PM > To: [email protected] > Subject: Re: LINK vs LOAD/CALL > >> On Sun, 7 Feb 2021 16:52:55 +0000, Seymour J Metz <[email protected]> wrote: >> >> ..., I suspect that at some point REFRPR"OT will be mandatory. >> > The effect of REFRPROT has long been enforced for modules loaded > from APF libraries. IBM suspects that there are so many dusty-deck > modules incorrectly marked REFR in non-APF libraries that REFRPROT > would be catastrophic. Does REFRPROT have a "warn" setting? > > REFRPROT should be an opt-in (but not opt-out) option on the JOB > statement. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
