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



Are you sure your debug job and the production job have the same library
list?




From:
"John Furniss" <JFurniss@xxxxxxxxxxxxxxxxx>
To:
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Date:
03/27/2009 10:40 AM
Subject:
Runs in debug only
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



List



I have a very simple RPGLE program that simply does a READ to get the
one and only record in a file, then uses that value to CHAIN to another
file, then if the CHAIN fails, does an EXCEPT to print a line on a
report. Very simple. I noticed that the verbiage was not being printed
when I knew it should have been, so I put it in DEBUG mode, stopped it
at the READ statement (which is in a group of LR statements if that
makes any difference) then stepped through with F10. When I do this the
program works as designed. But, when I run the job without debug, the
EXCEPT is never called. Has anyone seen this? I noticed this same
problem a few times in the past, but when I ran it in debug, it seemed
to 'flip a switch' and any subsequent runs would work fine. But this
only works in debug mode. I searched the archives but came up empty.
What am I missing?



Thanks much,



John Furniss

Applications Programmer

Allied Machine & Engineering, Corp

Phone: 330-343-4283, ext. 8371

email: jfurniss@xxxxxxxxxxxxxxxxx




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.