Firstly, my recommendation was not COBOL nested programs, but rather was two individual COBOL programs stored in the same member and compiled in the same compile step.
Anyway, I've not tried recently, but I don't believe that you can point an ENTRY or procedure-pointer to a nested COBOL subprogram. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Farley, Peter x23353 <[email protected]> Sent: Thursday, August 11, 2016 10:16 AM To: [email protected] Subject: Re: How does COBOL detect a recursive call? John, Using the COBOL "nested programs" approach (as opposed to an ENTRY) does not result in more than one load module / program object, only one. Any competent source management system should handle that setup. We do that here with no issue (though we are not an Endeavor shop). And the nested program does have access to the main program's WORKING-STORAGE items declared as GLOBAL, so they can share data too. The question is whether or not the LE condition handler actually requires a directory entry in the PDS/E for the entry point of the condition handler code. If the "SET procedure-pointer" operation results in an address acceptable to the LE register-condition-handler operation, then there should be no issue at all. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Thursday, August 11, 2016 8:07 AM To: [email protected] Subject: Re: How does COBOL detect a recursive call? <Snipped> > Excluding cursing, and including recursing. > > Any IT management who chooses that route over > TwoSimpleProgramsWithNothingButOrdinaryCodeCompile/ > LinkProcessingAndOrdinaryRunTime. is... well, choose your own ending. > > Remember, there is Frank's suggestion to have the two programs in one > source and compile them together, like they have some deep affinity > just through proximity, that may serve the "do it the way I say" people. > Hum, that wouldn't work here. I'm fairly sure the CA-Endevor will barf up its lungs if you try to put two source modules, which create two load modules / program objects, into a single source member. It wouldn't be able to 1:1 track an executable and associated source member. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
