Just to be clear, there is no case to ever include SYS1.SCSFMOD0. That dataset should never be in any since HCR77D0 (z/OS V2R4) because it is not a programming interface. Everything that was in there that was intended as a programming interface is now in SYS1.SCSFSTUB.
ASM programs should be using SYS1.SCSFSTUB (static) or LOAD/LINK (dynamic) LE programs (such as C) should be using SYS1.SIEASID (dynamic) or SYS1.SIEALNKE (static). I'd love to help. Do you have a simple test (source and link job) that replicates this error? Eric Rossman, CISSP® ICSF Cryptographic Security Development z/OS Enabling Technologies [email protected] "IBM Mainframe Discussion List" <[email protected]> wrote on 08/10/2021 05:41:46 PM: > From: "Frank Swarbrick" <[email protected]> > To: [email protected] > Date: 08/10/2021 05:42 PM > Subject: [EXTERNAL] Re: DLL linkage vs static linkage > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > Hi Barry, > > Interesting. But I can't quite get it to work. What's bizarre is > that the DLL linkage seems to get resolved: > > IMPORT/EXPORT TYPE SYMBOL DLL > DDNAME SEQ MEMBER > ------------- ------ ---------------- ---------------- > -------- --- --------- > IMPORT CODE CSNBRNGL CSFDLL31 > SIEASID 01 CSFDLL31 > > But the binder is still giving me an error: > > IEW2455W 9205 SYMBOL CSNBRNGL UNRESOLVED. NOCALL OR NEVERCALL > SPECIFIED. > IEW2638S 5384 AN EXECUTABLE VERSION OF MODULE *NULL* EXISTS AND > CANNOT BE REPLACED BY THE NON-EXECUTABLE MODULE JUST > CREATED. > > Very odd! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
