× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jerry

A crazy thought - WRKOBJPDM QRPLOBJ and look for items with your program name in the text field. Delete all of them. I can't swear to it, but when things get weird with the debugger, this seems to help at times. Your job may still have an object resolution to the previous version.

Vern

GKern@xxxxxxxxxxxxxxxx wrote:
I just was debugging again and noticed something strange which led me to recompile the program again. Looking at the spool file listing I searched for 026500 (line number on the left in the spool file), and in the listing it shows three times, once as the line number of a procedure (from a different copybook), again as a BEGSR statement that is in my copybook, and the third is an ENDIF in the parent source member.

So is it possible the debugger is getting confused on multiple occurrences of the same the line numbers (in the different members)?

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please inform the sender by reply e-mail and destroy this and all copies of this message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.