Eric, To the best of my knowledge SYS1.SIEALNKE members are not intended to be linked directly into programs. SYS1.CSSLIB (or other component-specific libraries like LE's CEE.SCEELKED) should have the stubs for their functions. SYS1.SIEALNKE is one of the datasets which are by default part of the LNKLST concatenation, specifically: SYS1.LINKLIB, SYS1.MIGLIB, SYS1.CSSLIB, SYS1.SIEALNKE, and SYS1.SIEAMIGE
Barry On Wed, 11 Aug 2021 15:37:42 -0400 Eric D Rossman <[email protected]> wrote: > Reply > > I would like to point out that the stubs in SCSFSTUB use OS linkage and > the entry points in CSFDLL31 use LE linkage. You should use whichever > matches the linkage declared (or defaulted) for the ICSF callable > services. > > It is never correct to specify both SCSFSTUB and an ICSF side-deck in the > same link operation. It might work but it might not. > > As to what I meant by static, I suspect that I might be using the wrong > terminology for this and perhaps I am misremembering how it works. I > thought you could directly linkedit a shared object [like > SIEALNKE(CSFDLL31)] into a load module and it would be treated as if it > were an archive (.a) instead of shared object/DLL (.so). > > Eric Rossman, CISSP^62^AF > ICSF Cryptographic Security Development > z/OS Enabling Technologies > [email protected] > Tieline: 295-6882 or (845) 435-6882 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
