You are correct most of the Cobol programs I mess with are OPM. So the .cbl, cblle(ILE cobol with SQL) and SQLCBL have option to see the copy book. I find it hard to believe ILESQL would not have something OPM has, but COBOL on IBM is always a pain in trying to figure how to get the same thing in OPM working in ILE or Vice Versa. If I find something will post otherwise might need to send something to IBM and ask where that option is for SQLCBLLE....
JeffJeff Buening
Sr. Developer
P: 419.586.8599 F: 419.586.8997
Celina Insurance Group
800.552.5181 | 1 Insurance Square, Celina, Ohio 45822
www.celinainsurance.com
...........................................................................................
The information contained in this message (including any attachments) is confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited and may be unlawful.
If you are not the intended recipient, please delete this message and notify the sender.
-----Original Message-----
From: COBOL400-L <cobol400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Paul Nicolay
Sent: Tuesday, May 19, 2020 11:44 AM
To: COBOL Programming on the IBM i (AS/400 and iSeries) <cobol400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [COBOL400-L] Debugging COPY statements
Hi,
I'm using SQLCBLLE which uses CRTSQLCBLI... which only supports *SOURCE as DBGVIEW.
I can't enter *LIST on the command ?
Kind regards,
Paul
________________________________________
From: COBOL400-L <cobol400-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Jeff Buening <jeff.buening@xxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, May 19, 2020 17:00
To: COBOL Programming on the IBM i (AS/400 and iSeries)
Subject: Re: [COBOL400-L] Debugging COPY statements
It depends if you are compiling as OPM cobol(.cbl) or ILE Cobol(.cblle) or SQL(.SQLCBL or SQLCBLLE)?
OPM Cobol change the OPTION compile cmd to *LSTDBG instead of *SRCDBG. ILE Cobol or SQL(OPM or ILE) change the DBGVIEW compile cmd to *LIST instead of *SOURCE. Then you should see the copy books info in the PROCEDURE section when debugging.
Jeff Buening
Sr. Developer
P: 419.586.8599 F: 419.586.8997
Celina Insurance Group
800.552.5181 | 1 Insurance Square, Celina, Ohio 45822 www.celinainsurance.com
..........................................................................................
The information contained in this message (including any attachments) is confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited and may be unlawful.
If you are not the intended recipient, please delete this message and notify the sender.
-----Original Message-----
From: COBOL400-L <cobol400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Paul Nicolay
Sent: Tuesday, May 19, 2020 10:29 AM
To: cobol400-l@xxxxxxxxxxxxxxxxxx
Subject: [COBOL400-L] Debugging COPY statements
?Hi,
I'm using COPY (as well as INCLUDE) statements in my Cobol source but during debugging I don't see the contents.
Is there a method to see the contents and debug them ?
Kind regards,
Paul
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/cobol400-l.
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/cobol400-l.
--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/cobol400-l.
midrange.com
