In the z/OS dlls that we have built that contain C, C++, and Assembler routines we don't reference CEESTART *anywhere* in our source tree.
- Did you compile with: -W "c,dll,expo" ? - We bind our dll with z/OS Unix make using c++ (or c89, xlc) command as shown in "z/OS XL C/C++ User's Guide" using "-W l,dll". Take a look at that book and try to build a tiny Hello Word dll first. Kirk Wolf Dovetailed Technologies http://coztoolkit.com On Tue, Jul 11, 2023, at 1:52 PM, Eric Erickson wrote: > I've a LE C DLL I've built that contains a several modules. It has both C and > a LE callable Assembler routines. When I first bound the moudle, it did not > set CEESTART as the entry point, so I added an ENTRY CEESTART to the binder > input deck. This results in a load module that shows the following in the > map. > > > ENTRY POINT AND ALIAS SUMMARY: > > NAME: ENTRY TYPE AMODE C_OFFSET CLASS NAME STATUS > > CEESTART MAIN_EP 31 00000A48 B_TEXT > > But when I call one of the exported functions in DLL I get a CEE3350S > > CEE3550S DLL ZDPUTILS does not contain a CEESTART CSECT. > > Binder options are: > > TEST,LET,LIST,MAP,RENT,DYNAM(DLL),CASE(MIXED),XREF > > The binder output for the routine that calls the DLL function shows the > called function as imported. > > Not sure what is going on here. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
