|
Here are two simple ways to debug your SQL COBOL program 1). Change your source type from SQLCBL to SQLCBLLE. You now have a compile option (keyword is DBGVIEW) that you can use. Set this option to *SOURCE. You will now be able to do a source debug using the command STRDBG and then calling your program. 2). The create SQLCBLPGM command has a compile option TOSRCFILE. Set this option to YOURLIB/QSQLTEMP. This will generate a source member of the type CBL. Compile this source with the option *SRCDBG and debug the new object you have created just as you would any other CBL program. Good Luck! Ash Nirody Project Leader Popular Club -----Original Message----- From: cobol400-l-request@xxxxxxxxxxxx [mailto:cobol400-l-request@xxxxxxxxxxxx] Sent: Monday, September 22, 2003 1:00 PM To: cobol400-l@xxxxxxxxxxxx Subject: COBOL400-L Digest, Vol 1, Issue 279 Send COBOL400-L mailing list submissions to cobol400-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/cobol400-l or, via email, send a message with subject or body 'help' to cobol400-l-request@xxxxxxxxxxxx You can reach the person managing the list at cobol400-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of COBOL400-L digest..." Today's Topics: 1. Debugging SQL COBOL 400 (D Meza) ---------------------------------------------------------------------- message: 1 date: Mon, 22 Sep 2003 06:54:25 -0700 (PDT) from: D Meza <mezazerlin@xxxxxxxxx> subject: Debugging SQL COBOL 400 Hello, I am new to the AS400. Could someone please advise me on how to test a SQL COBOL program on the AS400. I have tried using "*SRCDBG" as a compile option and it is not valid. I could use step by step instructions for example what parameters to use and how to invoke debug using SQL COBOL. I thank you for your help. --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design softwareFrom casey_r@xxxxxxxxxxxxxxxx Mon Sep 22 11:12:18 2003 Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by linux.midrange.com (8.12.8/8.12.8) with ESMTP id h8MGCCE5028273 for <cobol400-l@xxxxxxxxxxxx>; Mon, 22 Sep 2003 11:12:17 -0500 Received: from user160.net585.fl.sprint-hsd.net ([65.41.6.160] helo=rc600xl) by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1A1TIJ-0002kM-00 for cobol400-l@xxxxxxxxxxxx; Mon, 22 Sep 2003 09:12:11 -0700 From: "Richard Casey" <casey_r@xxxxxxxxxxxxxxxx> To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx> Date: Mon, 22 Sep 2003 12:12:05 -0400 Message-ID: <DHEKJHMBPPGODHNBIOKIMEFICNAA.casey_r@xxxxxxxxxxxxxxxx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20030922135425.49482.qmail@xxxxxxxxxxxxxxxxxxxxxxx> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Mid-MailScanner-Info: Virus scanned at midrange.com X-Mid-MailScanner: Clean X-Mid-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.9, required 5, BAYES_30 -0.93, IN_REP_TO -0.37, MSGID_GOOD_EXCHANGE -0.14, ORIGINAL_MESSAGE -0.50) Subject: RE: Debugging SQL COBOL 400 X-BeenThere: cobol400-l@xxxxxxxxxxxx X-Mailman-Version: 2.1.2+ Precedence: list Reply-To: COBOL Programming on the iSeries/AS400 <cobol400-l@xxxxxxxxxxxx> List-Id: COBOL Programming on the iSeries/AS400 <cobol400-l.midrange.com> List-Unsubscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@xxxxxxxxxxxx?subject=unsubscribe> List-Archive: <http://archive.midrange.com/cobol400-l> List-Post: <mailto:cobol400-l@xxxxxxxxxxxx> List-Help: <mailto:cobol400-l-request@xxxxxxxxxxxx?subject=help> List-Subscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>, <mailto:cobol400-l-request@xxxxxxxxxxxx?subject=subscribe> Hi! What I do is create another source file and then use the TOSRCFILE parameter of the CRTSQLCBL command to save the output of the SQL precompiler. I then compile that source code with the normal COBOL compiler (CRTCBLPGM) using the *SRCDBG compile option. Once that compile is done, I can use STRISDB or STRDBG just fine. I've created a few PDM options to simplify the two-step process. You could also create a small CL program to combine the two compiles into a single step. Hope this helps! Richard -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx]On Behalf Of D Meza Sent: Monday, September 22, 2003 9:54 AM To: cobol400-l@xxxxxxxxxxxx Subject: Debugging SQL COBOL 400 Hello, I am new to the AS400. Could someone please advise me on how to test a SQL COBOL program on the AS400. I have tried using "*SRCDBG" as a compile option and it is not valid. I could use step by step instructions for example what parameters to use and how to invoke debug using SQL COBOL. I thank you for your help. ------------------------------ _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) digest list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. End of COBOL400-L Digest, Vol 1, Issue 279 ******************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.