|
A couple of possibilities to check; did you resequence when saving, and when you compile I have found it best to do an F4 and put *XREF on the OPTION field and *ALL on the DBGVIEW options; this has saved me many times while debugging ILE. Also to help in debugging, place the following in a /copy member and bring it into your ILE code /Copy MWSRCLIB/QCPYLESRC,H_Spec <<<-statement in your ILE H Option(*SrcStmt:*NoDebugIO) <<<-member code This will help you in not "getting stuck" on the F spec for disk I/O HTH and welcome to the wonderful, fun, and fascinating world of ILE Mark A. Manske [mailto:mmanske@minter-weisman.com] Sr. Project Lead Minter-Weisman -----Original Message----- From: owner-rpg400-l@MIDRANGE.COM [mailto:owner-rpg400-l@MIDRANGE.COM]On Behalf Of Nilda Mejias Sent: Friday, October 20, 2000 1:20 PM To: AS400-MIDRANGE (E-mail) Subject: TWO QUESTION ABOUT RPGILE Hi everybody, I am new working with RPGILE, if somebody has an answer for the following questions that I have about RPGILE I will appreciated. The statement numbers in a compiled RPGILE program do not correspond to the statement numbers in the source code. This make it confusing when debugging the program. Is there a way of relating the statement numbers in the compiled program to the statement in the source code ? Thanks in advance Nilda. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.