I think you should stick with CEEENTRY as that's runtime environment agnostic. CEEENTRY works in batch, IMS, OMVS, DB2 Stored Procs, etc.
Regards, Dougie On 18 July 2017 at 17:11, John McKown <[email protected]> wrote: > I have gotten into the habit of using CEEENTRY MAIN=YES for my HLASM main > routines and MAIN=NO for subroutines (exit code excluded, of course). But I > was just wondering if there would be any advantage to using EDCPRLG instead > of CEEENTRY. > > The book that I'm reading is not really explicit about whether EDCPRLG can > be used for an HLASM "main" routine which invokes C subroutines, or is only > for HLASM "subroutines" which are invoked by C routines (and I guess can > invoke C subroutines in turn). > > I'm guessing that CEEENTRY is "better" in the general case. I.e. something > which is to be callable from C, FORTRAN, COBOL, or PL/I. > > -- > Veni, Vidi, VISA: I came, I saw, I did a little shopping. > > Maranatha! <>< > John McKown > -- http://twitter.com/DougieLawson
