Re: Strange acting program in debug

Rick,
 
     Thanks for the response.  I did as you suggested but the member created is greater than the max allowed.....Seems as though I get deeper and deeper in muck. 

Warmest Regards,

Richard Reeve

From: "Rick.Chevalier@xxxxxxxxxxxxxxx" <Rick.Chevalier@xxxxxxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Sent: Tuesday, May 3, 2011 7:20 AM
Subject: RE: Strange acting program in debug

Richard,

The SQL per-compiler creates a source member after inserting its SQL code.  This is the source member you want to use when debugging.  Use the TOSRCFILE parameter on the compile command to store it in a library and file of your choosing.  By default it is stored in QTEMP which, if you compile in batch, is not available after the compile.

What you are seeing is the debugger making its way through the updated source member created by the pre-compiler but displaying your original source code.

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Monday, May 02, 2011 6:43 PM
To: RPG programming on the AS400 / iSeries
Subject: Strange acting program in debug

So, I have this large (20k + lines) program that has me perplexed.  I made some minor changes to a subroutine.  When testing, it did not perform as desired, so I put in debug.  This is where it gets very strange....The subroutine builds an SQL statement.  Then, as I step through in debug, the next statement is an SQL prepare - but instead the program goes to a subroutine that isn't even referenced in the subroutine from which it came.  It then goes through a few lines and oddly returns to the subroutine where it began (although not where it left off).  My initial thought was source/object mis-match so I recompiled, signed off & on and tried again, only to have the same result.

I have consulted with 4 programmers in house but we are all stumped.  Does this sound familiar to anyone?  Any suggestion/ideas would be much appreciated.

Thanks.

Warmest Regards,
Richard Reeve


Privileged and Confidential.  This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information.  If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail.  You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.