Do you have an INCLUDE for the CEESTART module? Does LE look for an eyecatcher that it recognises as CEESTART, not just an ENTRY which as Seymour says isn't the same.
Take LET off the bind in case there's another hidden problem. On Wed, Jul 12, 2023 at 5:18 AM Eric Erickson <esf...@windstream.net> wrote: > I know, but the CEESTART CSECT is included in the program object. On > another DLL, which is just 1 module with multiple functions, the CEESTART > CSECT is listed in the load map as such. > > > 0 CEESTART * CSECT B0 SYSLIB 03 CEESTART > > > > In my problem DLL its listed as: > > A48 CEESTART * CSECT B0 SYSLIB 03 > CEESTART > > Not sure what is going on here. Its my first foray into C DLLs and I > wonder if mixing in the C LE Assembler routines is causing an issue? > > If I don't but the Entry statement into the deck, I get one what looks to > be the module with the first alphabetically marked as the entry point. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
