On Fri, 22 Jan 2021 01:06:10 +0000, CM Poncelet wrote: >The "END <whatever CSECT>" should always be coded to ensure that the >beginning of "<whatever CSECT>" is also the entry point. > How does this play with SMP/E service which regularly scrambles CSECTs and doesn't AFAIK generate INCLUDE -ATTR? Would the programmer more safely code in //SYSLIN either: ENTRY whatever or ORDER whatever ??? I had a co-worker who supplied an exhaustive ORDER mentioning every CSECT, knowing that his code would not be tested in-house with every permutation (N!) that SMP/E might create.
>On 21/01/2021 20:54, Jesse 1 Robinson wrote: >> Without some kind of explicit ENTRY indicator within the source--like END >> BAMKAPP--there was no ENTRY point generated in the app module. Hence >> specifying ENTRY BANKAPP to the linker got 'not found'. Maybe today's binder >> takes care of this, but in the 80s we could not find an obvious way to solve >> it. >> >> Given more time we might have come to a resolution, but at the time we were >> stumped. >> >> >> -----Original Message----- >> From: Steve Smith >> Sent: Thursday, January 21, 2021 12:44 PM >> >> *** EXTERNAL EMAIL - Use caution when opening links or attachments *** >> >> No one knew how to code an ENTRY statement? >> >> Personally, I'd make that message the Binder emits about defaulting the >> entry point to be an RC=8 level error. I usually discover this oversight >> when something crashes after an APPLY, and by then, it's not so simple to >> add the ENTRY. > Can you name the vendor? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
