Problem resolved. Programmer error or ECC memory check in the programmer's brain (take your pick).
The "global application library" is actually TWO libraries, one PDSE (current application target library) and one PDS (modules not recently recompiled). The E15 / E35 exit programs are located in the PDSE library. Adding that library second in the STEPLIB using MODS with no DD name allows the alternate version in the first STEPLIB library allows the alternate version to be loaded. Apologies for wasted bandwidth and no disrespect to the vendor. Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Farley, Peter x23353 Sent: Friday, August 30, 2019 11:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYNCSORT and STEPLIB/JOBLIB/LINKLIB issue Thanks Peter. In this case both exit programs are resident in LINKLIST and the global application library in LINKLIST is (AFAIK) also LLA/VLF managed. The precise sequence is a little more complicated than I first thought. Here is the sequence: JCL Invokes SYNCSORT SYNCSORT invokes COBOL EXIT program from LINKLIST library COBOL EXIT program dynamically calls assembler subroutine (also in LINKLIST global application library) Assembler subroutine LOAD's a "data" load module containing a small amount of application-specific data and displays that data via WTO. The "data" load modules are the ones that are incorrectly coming from LINKLIST instead of from MODLIB/STEPLIB/JOBLIB where I provide an alternate version of the "data". The LINKLIST version of the "data" module is always loaded. I will open an issue with the vendor on this. Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Peter Relson Sent: Friday, August 30, 2019 8:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SYNCSORT and STEPLIB/JOBLIB/LINKLIB issue I know nothing about SYNCSORT, but it is possible (and if so they should document) that the way they ask the system to fetch the module specifically indicates not to use tasklib/steplib/joblib. When the system does that it is typically to be using its copy of the named module rather than someone else's (since you'd have to out of your way, for example, to get your copy into LPA or ahead of the system's copy in the LNKLST. Since in your case it is "your module", such program logic would seem kind of strange. Peter Relson z/OS Core Technology Design -- 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
