During an apply of the latest maintenance for many CA products, including Endevor, all was well EXCEPT for S006486 which showed the following:
SO06486 CSIQI00 GIM23911E 41 LINK-EDIT PROCESSING FAILED FOR MODULE EONLYTBL IN LMOD EONLY IN THE CSIQAUTH
LIBRARY. THE RETURN CODE WAS 08. THE SEQUENCE NUMBER WAS 000071. THE SYSPRINT
FILE WAS SMP00033.
IEW2278I B352 INVOCATION PARAMETERS - NCAL,LIST,LET,XREF,RENT,AMODE=31,RMODE=24,CALL
IEW2322I 1220 1 INCLUDE SMPWRK3(EONLYTBL) SO06486 SEQ # 000068
IEW2322I 1220 2 IDENTIFY EONLYTBL('SO06486')
IEW2322I 1220 3 SETSSI 00018332
IEW2322I 1220 4 INCLUDE ASIQMOD(BSTPESET) LMODBLD
IEW2322I 1220 5 INCLUDE ASIQMOD(EONLY) LMODBLD
IEW2322I 1220 6 ORDER EONLY
IEW2322I 1220 7 ORDER EONLYTBL
IEW2322I 1220 8 ORDER BSTPMSET
IEW2322I 1220 9 ENTRY EONLY
IEW2322I 1220 10 NAME EONLY(R) MAX ACCEPTABLE RC=04
IEW2456E 9207 SYMBOL ESORTTBL UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
Module EONLY should not link with ESORTTBL.
As of release 18.0, it is linked with module EONLYTBL instead.
It is linked with ESORTTBL at the 17.0 GA level.
This indicates that SMP/E is pulling the incorrect (17.0) version of EONLY which most probably happens because the DDDEF entry for ASIQMOD in the target zone points to a release 17.0 ASIQMOD library.
In this specific case, V18 was installed in the same CSI as V17 so the DDDEFs are pointing to the V17 libraries.
CA Endevor SCM V18.0
Do a fresh V18.0 install in a new SMP/E environment.
Restore and Reject Endevor V18 from the V17 CSI.