<snip>Turns out we had an old, old version of EDGSOCE get put in a library ahead of SYS1.LINKLIB on the linklist, and it finally bit us. (From 2004! How the hell it ran this long, I ahven't got the first clue.) </snip> The only intended way to accomplish having a library ahead of SYS1.LINKLIB in the LNKLST is to have used the SYSLIB LNKLST statement of PROGxx.
DISPLAY PROG,LNKLST,NAME=CURRENT can be used to display the complete current LNKLST concatenation. You had written that you had checked all of the LNKLST libraries. But apparently that wasn't the case since a library ahead of SYS1.LINKLIB is still part of the LNKLST. SETPROG LNKLST,TEST,NAME=CURRENT,MOD=xxxxx can also be used to see if something is in the current LNKLST (and tell you within which data set). If you do place a library ahead of SYS1.LINKLIB in order to "subvert" the system's intended processing, you should not expect correct behavior. That functionality is provided for test environments. And I would not expect IBM service to be willing to do much about that unless you can demonstrate that the undesired behavior occurs without that having been done. Peter Relson(ex) z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
