|
On May 21, 2019, at 8:00 PM, James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
On 5/21/19, 4:16 PM, Jon Paris wrote:
If you are allowed to, try it in debug on the original problem box
and stop through the individual field moves (this implies of course
that you have NOT specified NODebugIO). That at least would identify
the field in question.
Dear Mr. Paris, et al:
There is no question that I would be *permitted* to do as you describe; the program in question only *exists* on the original problem box; it was compiled on the original problem box, from source on the original problem box, and is specific to the customer who owns the original problem box (the program in question is an installation-specific exit program for our application).
The problem is that it happened exactly once, and when I attempted to duplicate the circumstances, the exit program behaved normally, without reproducing the problem.
That's the part that bothers me.
--
JHHL
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.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.