Yes, but it is of little use if you are stuck using the DB2 and/or CICS preprocessor utilities (instead of the coprocessor facilities in the compiler) and use EXEC SQL and/or EXEC CICS statements in COPY members extensively. All COPY members containing EXEC SQL / CICS must be pre-resolved before the preprocessor utility reads the source to be translated.
All of which is a really good argument to use the coprocessor facilities, but institutional resistance to change is powerful and often both entrenched and intransigent. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Tom Ross Sent: Thursday, September 9, 2021 2:06 PM To: [email protected] Subject: Re: COBOL compiler option to list libraries from which COPY members were loaded? ><*Doh!*> > >I missed seeing that part of the listings entirely. And it has the >same page title back at least as far back as ECOBOL V4.1.0. You guys are great! I added "cross reference of library names" to the COBOL compiler listings years ago, glad it is getting used, and thank you for pointing it out to help each other out! Cheers, TomR -- 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
