Thanks. I see the following in the Services Guide for search order: The control program searches: 1. The requesting task's load list for an available copy. 2. The job pack area for an available copy. 3. The requesting task's task library and all the unique task libraries of its preceding tasks. (For the ATTACH or ATTACHX macro, the attached task's library and all the unique task libraries of its preceding tasks are searched.) 4. The step library; if there is no step library, the job library (if any). 5. The link pack area. 6. The link library.
Is it your impression that TASKLIB comes ahead of existing copies? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Attila Fogarasi Sent: Thursday, December 5, 2019 12:26 PM To: [email protected] Subject: Re: Trying to understand IDENTIFY and module re-usage issue TASKLIB on ATTACH is one reason that pops to mind; given you dont have source code, can you do GTF trace to confirm that ATTACH has occurred? There are probably several similar scenarios possible if not doing TASKLIB. On Fri, Dec 6, 2019 at 6:49 AM Charles Mills <[email protected]> wrote: > Program A issues a successful IDENTIFY for entry point ABC and then > transfers control to program XYZ. (I have no source code for nor ability to > fully understand the logic of program XYZ, nor to modify it.) Program XYZ > subsequently invokes entry point ABC but ends up with a new copy loaded > from > STEPLIB rather than using the IDENTIFY entry address. > > Why would that be? > > The documentation for IDENTIFY states that the entry point is always > treated > as RENT. The Services Guide says > > All reenterable modules (modules designated as reenterable using the > linkage > editor) from any library are completely reusable. Only one copy is normally > placed > in the link pack area or brought into your job pack area, and you get > immediate > control of the load module. However, there might be circumstances beyond > your > control that can cause an additional copy to be placed into your job pack > area. The > control program might do this, for example, to preserve system integrity. > > Can anyone elaborate? > > Charles > > ---------------------------------------------------------------------- > 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
