Sv: COBOL compiler option to list libraries from which COPY members were loaded?
Thanks, tried it and, yes //Lasse -Ursprungligt meddelande- Från: IBM Mainframe Discussion List För Tom Ross Skickat: den 14 september 2021 02:13 Till: IBM-MAIN@LISTSERV.UA.EDU Ämne: Sv: COBOL compiler option to list libraries from which COPY members were loaded? >And You can't use coprocess if You are using EXCI. >//Lasse=20 That changed a couple of years ago for COBOL! (Still true for PL/I) https://www.ibm.com/support/pages/use-integrated-cics-translator-exci-batch-programs Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Sv: COBOL compiler option to list libraries from which COPY members were loaded?
>And You can't use coprocess if You are using EXCI. >//Lasse=20 That changed a couple of years ago for COBOL! (Still true for PL/I) https://www.ibm.com/support/pages/use-integrated-cics-translator-exci-batch-programs Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
On Fri, 10 Sept 2021 at 16:22, Lars Höglund wrote:
> And You can't use coprocess if You are using EXCI.
> //Lasse
Hi Lasse,
You *CAN* use the coprocessor when compiling an EXCI program. I am
specifying these compiler options on line 1 of my COBOL program:
PROCESS NODYNAM,RENT,CICS('EXCI')
Regards,
Peter
>
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List För
> Farley, Peter x23353
> Skickat: den 9 september 2021 21:08
> Till: IBM-MAIN@LISTSERV.UA.EDU
> Ämne: Re: COBOL compiler option to list libraries from which COPY members
> were loaded?
>
> 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 On Behalf
> Of Tom Ross
> Sent: Thursday, September 9, 2021 2:06 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Sv: COBOL compiler option to list libraries from which COPY members were loaded?
And You can't use coprocess if You are using EXCI. //Lasse -Ursprungligt meddelande- Från: IBM Mainframe Discussion List För Farley, Peter x23353 Skickat: den 9 september 2021 21:08 Till: IBM-MAIN@LISTSERV.UA.EDU Ämne: Re: COBOL compiler option to list libraries from which COPY members were loaded? 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 On Behalf Of Tom Ross Sent: Thursday, September 9, 2021 2:06 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
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 On Behalf Of Tom Ross Sent: Thursday, September 9, 2021 2:06 PM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 pa= >ge 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 >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
Thanks Sri. As a prior poster pointed out, it is already there. I just missed finding it in the listings that I browsed. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sri h Kolusu Sent: Sunday, September 5, 2021 8:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL compiler option to list libraries from which COPY members were loaded? > I was looking around at listings from multiple incarnations of COBOL > compilers and did not find any which listed the libraries from which > copy members were loaded, as HLASM does for macros and copy members. > > Has there ever been such a compiler option? Peter, You can use XREF(FULL) compiler option https://urldefense.com/v3/__https://www.ibm.com/docs/en/cobol-zos/6.3?topic=options-xref__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!Ym5rdXc2PlrfKhGjo5-AqV6Mny2uMooqRDoj1KZ0R8xkErmaW8TLfVL3TsGCX2_mnxilKg$ and here is an example of the output https://urldefense.com/v3/__https://www.ibm.com/docs/en/cobol-zos/6.3?topic=references-example-xref-output-copybasis-cross__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!Ym5rdXc2PlrfKhGjo5-AqV6Mny2uMooqRDoj1KZ0R8xkErmaW8TLfVL3TsGCX29p8X7-Xg$ Thanks, Kolusu -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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. Many thanks for enlightening me. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Vels Sent: Sunday, September 5, 2021 7:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL compiler option to list libraries from which COPY members were loaded? I use "IBM Enterprise COBOL for z/OS 6.3.0 P210301" and there is a "COPY/BASIS cross-reference of text-names, library names and dataset information" section near the bottom of the compiler listing. I also use "HLASM R6.0" and it has a "Macro and Copy Code Source Summary" near the bottom of the listing. > On Sun, Sep 5, 2021 at 13:57 Farley, Peter x23353 < > 031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: > > > I was looking around at listings from multiple incarnations of COBOL > > compilers and did not find any which listed the libraries from which > > copy members were loaded, as HLASM does for macros and copy members. > > > > Has there ever been such a compiler option? -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
> I was looking around at listings from multiple incarnations of COBOL > compilers and did not find any which listed the libraries from which > copy members were loaded, as HLASM does for macros and copy members. > > Has there ever been such a compiler option? Peter, You can use XREF(FULL) compiler option https://www.ibm.com/docs/en/cobol-zos/6.3?topic=options-xref and here is an example of the output https://www.ibm.com/docs/en/cobol-zos/6.3?topic=references-example-xref-output-copybasis-cross Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
On Sun, 5 Sep 2021 21:33:49 +, Farley, Peter x23353 wrote: >... >I know you have pointed out several flaws in that support already like needing >at least one (possibly empty) PDS/E in the concatenation ahead of the Unix >directories. > I encountered that problem/circumvention with Rexx SYSEXEC. Support says DSORG=PO is required. Alas, JCL makes DSORG mutex with PATH. HLASM SYSLIB works well after IBM fixed a couple APARS for nested COPYs in a mixed PDS/UNIX SYSLIB concatenation, And similar problem/circumvention with AMATERSE UNPACK SYSUT1. When I report such problems, Support tends to say, "That needs to be a data set." They are unmoved when I read them the definition from "Using Data Sets". >I think I will write my own test of that DESERV functionality just to see >where the bumps in the road are. > Good luck, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
On Mon, 6 Sep 2021 09:15:05 +1000, Peter Vels wrote: >I use "IBM Enterprise COBOL for z/OS 6.3.0 P210301" and there is a >"COPY/BASIS cross-reference of text-names, library names and dataset >information" section near the bottom of the compiler listing. > How are UNIX members reported? >I also use "HLASM R6.0" and it has a "Macro and Copy Code Source Summary" >near the bottom of the listing. > And HLASM re;ports UNIX members nicely. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
I use "IBM Enterprise COBOL for z/OS 6.3.0 P210301" and there is a "COPY/BASIS cross-reference of text-names, library names and dataset information" section near the bottom of the compiler listing. I also use "HLASM R6.0" and it has a "Macro and Copy Code Source Summary" near the bottom of the listing. > On Sun, Sep 5, 2021 at 13:57 Farley, Peter x23353 < > 031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: > > > I was looking around at listings from multiple incarnations of COBOL > > compilers and did not find any which listed the libraries from which copy > > members were loaded, as HLASM does for macros and copy members. > > > > Has there ever been such a compiler option? > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
My shop uses Enterprise COBOL 6.2 and that information appears in the compile listing. I am not sure which compiler option influences that behavior but it works by default. I rely on it often. On Sun, Sep 5, 2021 at 13:57 Farley, Peter x23353 < 031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: > I was looking around at listings from multiple incarnations of COBOL > compilers and did not find any which listed the libraries from which copy > members were loaded, as HLASM does for macros and copy members. > > Has there ever been such a compiler option? > > If not I suspect an RFE is in order. Business justification: Needed as an > aid to verification that the most recent COPY members were used during > compilation as part of SDLC promotion process to QA/UAT/production status. > Bonus points for listing the date/time of the member in each library (if > available) as part of the compile listing. > > Peter > > 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
"If the member is any PDSE member, the information should be available from FAMS." Or from DESERV for programmers whose company has not signed the NDA and paid the license fee to get FAMS documentation. And since DESERV FUNC=GET requires only an open BPAM DCB which can be for a DD concatenation which may include Unix directories, I would hope that at least some of the same information would also be available (at least modify time, though probably not many of the other ISPF statistics) for Unix files used as copy members. I know you have pointed out several flaws in that support already like needing at least one (possibly empty) PDS/E in the concatenation ahead of the Unix directories. I think I will write my own test of that DESERV functionality just to see where the bumps in the road are. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Sunday, September 5, 2021 3:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: COBOL compiler option to list libraries from which COPY members were loaded? On Sun, 5 Sep 2021 17:57:12 +, Farley, Peter x23353 wrote: >I was looking around at listings from multiple incarnations of COBOL compilers >and did not find any which listed the libraries from which copy members were >loaded, as HLASM does for macros and copy members. >... >... Bonus points for listing the date/time of the member in each library > (if available) as part of the compile listing. > I don't believe HLASM shows that information either. It would be useful. If the PDS/PDSE member was edited with ISPF, the information should be available from ISPF stats. If the member is a UNIX file, the informattion should be available from tne file timestamp. If the member is any PDSE member, the information should be available from FAMS. Perhaps an RFE should request an API to extract such information independent of ISPF for each of those cases. -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
The “Macro and Copy Code Cross Reference “ output of HLASM the concatenation number from which it is fetched is displayed. The MXREF(XREF) or MXREF(FULL) generates this section. Sent from my iPhone > On Sep 5, 2021, at 3:24 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> On Sun, 5 Sep 2021 17:57:12 +, Farley, Peter x23353 wrote: >> >> I was looking around at listings from multiple incarnations of COBOL >> compilers and did not find any which listed the libraries from which copy >> members were loaded, as HLASM does for macros and copy members. >> ... >> ... Bonus points for listing the date/time of the member in each library >> (if available) as part of the compile listing. >> > I don't believe HLASM shows that information either. It would be useful. > > If the PDS/PDSE member was edited with ISPF, the information should be > available from ISPF stats. > > If the member is a UNIX file, the informattion should be available from tne > file timestamp. > > If the member is any PDSE member, the information should be available > from FAMS. > > Perhaps an RFE should request an API to extract such information independent > of ISPF for each of those cases. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
I think it does unless that info was dropped since I wrote ASYSLIB and pointed out the data display was wrong, as in wrong PDS. ASYSLIB changed the concatenation via changing the DDNAME being used. That was back about 1996 or so. Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct mistaks > On Sep 5, 2021, at 3:25 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Sun, 5 Sep 2021 17:57:12 +, Farley, Peter x23353 wrote: > >> I was looking around at listings from multiple incarnations of COBOL >> compilers and did not find any which listed the libraries from which copy >> members were loaded, as HLASM does for macros and copy members. >> ... >> ... Bonus points for listing the date/time of the member in each library >> (if available) as part of the compile listing. >> > I don't believe HLASM shows that information either. It would be useful. > > If the PDS/PDSE member was edited with ISPF, the information should be > available from ISPF stats. > > If the member is a UNIX file, the informattion should be available from tne > file timestamp. > > If the member is any PDSE member, the information should be available > from FAMS. > > Perhaps an RFE should request an API to extract such information independent > of ISPF for each of those cases. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: COBOL compiler option to list libraries from which COPY members were loaded?
On Sun, 5 Sep 2021 17:57:12 +, Farley, Peter x23353 wrote: >I was looking around at listings from multiple incarnations of COBOL compilers >and did not find any which listed the libraries from which copy members were >loaded, as HLASM does for macros and copy members. >... >... Bonus points for listing the date/time of the member in each library > (if available) as part of the compile listing. > I don't believe HLASM shows that information either. It would be useful. If the PDS/PDSE member was edited with ISPF, the information should be available from ISPF stats. If the member is a UNIX file, the informattion should be available from tne file timestamp. If the member is any PDSE member, the information should be available from FAMS. Perhaps an RFE should request an API to extract such information independent of ISPF for each of those cases. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
COBOL compiler option to list libraries from which COPY members were loaded?
I was looking around at listings from multiple incarnations of COBOL compilers and did not find any which listed the libraries from which copy members were loaded, as HLASM does for macros and copy members. Has there ever been such a compiler option? If not I suspect an RFE is in order. Business justification: Needed as an aid to verification that the most recent COPY members were used during compilation as part of SDLC promotion process to QA/UAT/production status. Bonus points for listing the date/time of the member in each library (if available) as part of the compile listing. Peter 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
