× 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.



Hi Willie,

For RPGLE programs, use the following H-spec:

h option(*srcstmt: *nodebugio)

The *srcstmt option will show the source statement numbers both in debug and any error messages in the joblog.

The *nodebugio option will prevent it from stepping through the I-specs whenever you do an I/O operation such as READ. It can be interesting, but most of the time it's not what I'm interested in.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Willie J. Moore wrote:
When an error is received on a program. A message is sent to the console and displayed. You can move the curser over the error and press F1 to show the line number in error. But unless you have a compiled listing, you have no reference for that line of code in the source. I have looked at the Create RPG Program option hoping that there was an option to put the compiled line number in the source. Does not look like there is an option for that.
So now we have to either use the Joblog or re-compile the program and look at the compiled listing to find the reference number of the line of code that failed. We then have to go and see what data was enter or ask the user what they entered. Most of the time they do not remember.
I would like to know how others handle this?
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii


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.