• Subject: RE: ILE Debug-bug-er?
  • From: "Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Wed, 14 Jan 1998 15:58 -0600

You have to call the program after adding your breakpoints and pressing   
F12.  It doens't have an invoke program parameter like STRISDB.


 ----------
From:  Tim Truax
Sent:  Wednesday, January 14, 1998 3:14 PM
To:  bvstone
Subject:  ILE Debug-bug-er?


Hi all,
I am starting to write ILE..ergo I have a perplexing situation dealing
with the ILE Debugger.
1) Have a very simple ILE program that I know works.
2) STRDBG (TIMLIB/ILE006) UPPROD(*YES)
3) Source is displayed beautifully, and I add my breakpoints.
4) Next I press F12-Resume and immediately I am back at the Menu.
5) Or.. I press F10-Step and immediately I am back at the Menu.
This is frustrating me... When I run this little program (ILE006) It
updates the little file I created.  But when I go through STRDBG and I
get unceremoniusly slammed back on the Menu no update has occurred.
I am definitely saying *yes to UPdate PRODuction Data.
Also.. my little file resides in a PROD type library.
 --
''''''''''''''''''''
: Tim & Dana Truax :
:                  :
''''''''''''''''''''
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to   
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:   
david@midrange.com
+---
uucp


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].