No, the ENTRY statement and the entry parameter on the END statement should 
only be coded in the source for a main program or main CSECT of a secondary 
load module or program object.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of CM 
Poncelet [[email protected]]
Sent: Thursday, January 21, 2021 8:06 PM
To: [email protected]
Subject: Re: Isolating a CSECT within a load module

The "END <whatever CSECT>" should always be coded to ensure that the
beginning of "<whatever CSECT>" is also the entry point.

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.
>
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office ⇐=== NEW
> [email protected]
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
> Steve Smith
> Sent: Thursday, January 21, 2021 12:44 PM
> To: [email protected]
> Subject: (External):Re: Isolating a CSECT within a load module
>
> *** 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.
>
> sas
>
>
> On Thu, Jan 21, 2021 at 3:22 PM Jesse 1 Robinson <[email protected]>
> wrote:
>
>> ...
>> As long as the program was compiled and linked in the same run, the
>> END statement picked up BANKAPP as entry point and everything was
>> cool. But when run separately, the entry point was indeterminate, so link 
>> failed.
>> Source of course was not available so we could not add
>>
>>   END BANKAPP
>> ...
>>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to