Good to hear, Gary
I'm not sure about the views - I know that if you are in the
green-screen debugger that F15 lets you choose which view to use. I
think there is something similar in the graphical debugger, whether out
of RDi or out of Navigator.
DBGVIEW *SOURCE when creating embedded SQL programs is really DBGVIEW
*ALL for all intents and purposes, IIRC.
On 9/3/2014 9:15 AM, Gary Thompson wrote:
Thanks Vern, that gives me a better 'picture' of the need for the 10's of key presses -
SQL procedures are black boxes for me - which is why I included one in this project.
I think because I created the SQL Proc with DBGVIEW *SOURCE I was able to see
the SQL Script code, but not the CLE code - is that possible ?
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Tuesday, September 02, 2014 5:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: testing an SQL procedure
Hi Gary - if you've ever walked an RPG program with embedded SQL - or just read the compile listing - you've seen that each statement results in multiple EVALs and some calls to various SQL programs - so i'm not surprised that a C/C++ program will have lots of steps.
In green-screen, at least, there is a view of the code that lets you debug from the SQL statements - at least in RPGLE - not sure about it for C/C++.
On 9/2/2014 5:08 PM, Gary Thompson wrote:
Thanks again to Rob, Chuck and Buck.
Setting Break Points in the SQL proc worked but I was surprised at the
number of F10-Step and F12-Resume key presses needed to run the proc ?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.