I was responding to 'The "END <whatever CSECT>" should always be coded to ensure that the beginning of "<whatever CSECT>" is also the entry point.' That relates to the HLASM source, not to SYSLIN.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Friday, January 22, 2021 12:39 PM To: [email protected] Subject: Re: Isolating a CSECT within a load module On Fri, 22 Jan 2021 11:24:40 -0600, Joe Monk wrote: >There are many SVCs and service routines that have multiple ENTRY >statements.... > z/OS Version 2 Release 4 MVS Program Management: User's Guide and Reference IBM SA23-1393-40 ... ENTRY statement ... An ENTRY statement should be used whenever a module is *reprocessed* by the binder... [emphasis added] Note: 1. If you provide more than one ENTRY statement, the main entry point specified on the last statement is used. [That ought to generate a warning. How does ENTRY interact with INCLUDE -ATTR?] Perhaps you were thinking of Assembler See also ALIAS. >On Fri, Jan 22, 2021 at 9:37 AM Seymour J Metz wrote: > >> 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. -- gil ---------------------------------------------------------------------- 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
