I've never had issues with inlined code when using IBM Debugger. I've never explicitly checked its behavior, but I've never run in to an issue. We use OPT(1) [for some probably bad reason not OPT(2)].
The only times I've seen the issue Tom is referring to are: 1. We backed out the latest production version and replaced it with the previous version. We then can no longer see the source code of the failed (backed out) version. 2. When testing we've already implemented an updated version and are trying to analyze the dump from a prior version. Using IBM Fault Analyzer for both. I don't consider them to be huge problems, and certainly not a reason to, say, have multiple versions of the load module and/or debug information. Just something to be aware of and live with, as little as it happens. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Farley, Peter <[email protected]> Sent: Friday, April 7, 2023 1:06 PM To: [email protected] <[email protected]> Subject: Re: LE runtime That would be a failure of your development lifecycle process. Anything running in production MUST have compile listings available of the exact version running in production, and it doesn't hurt to retain the binder listing too. If you are still running an "older version" in production and you also have a newer version in production at the same time without retaining the older version listing somewhere, that's a process failure. As for debugging production COBOL code, there are hurdles there too even if your listing is available. In my experience, the compiler option INLINE (default for higher levels of OPTIMIZE) absolutely prevents interactively stopping in any inlined paragraph. At least not using the CA Intertest debugger, which is all we have available to us at my employer's site, so I don’t know what the IBM debugger is capable of. I have found that using compiler option TEST(SOURCE) in production compiles subtracts very little from optimization and greatly aids debugging of production code (except for INLINE's - nothing helps that except re-compiling in test with NOINLINE and hoping the bug doesn't disappear with the test version). Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom Marchant Sent: Friday, April 7, 2023 2:41 PM To: [email protected] Subject: Re: LE runtime Yes, it will. And if you are debugging an abend that occurred with an older version of the program, the listing is no longer available in the program object. -- Tom Marchant On Fri, 7 Apr 2023 18:33:18 +0000, Seymour J Metz <[email protected]> wrote: >Won't that replace the NOLOAD segments with the new ones? > > >-- >Shmuel (Seymour J.) Metz >________________________________________ >From: IBM Mainframe Discussion List [[email protected]] on >behalf of Tom Marchant [[email protected]] >Sent: Friday, April 7, 2023 2:31 PM >To: [email protected] >Subject: Re: LE runtime > >Until the program is recompiled and relinked. > >-- >Tom Marchant > >On Fri, 7 Apr 2023 10:48:04 -0700, Tom Ross <[email protected]> >wrote: > >>With the >>NOLOAD class program segmenets in new COBOL the debugging data is >>always available, always in sync -- 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
