|
Hi All,I have found a "solution" to our problem, but I can't see how it would be the "cause" of the problem.
Basically, the display file indicator DS (indds) had four indicators defined which were not in the display file. The programmer who wrote the program/display file had copied one of my programs and modified it to create a new program. As a result he had left these four indicators in the indds, but removed them from the DDS. In the program these indicators were still getting updated - and consequently some portion of the internals of the display file was being overwritten.
I removed the fields from the indds and made them standalone indicators and recompiled - all worked fine. This isn't the solution, and the programmer is now working on removing the indicators and all references from the program "as I type", but it begs the question: How can this happen? I assumed that the indds was contiguous. There are fields defined before and after these fields in the indds so I would have thought that the memory affected by these indicators would be "safe". Can we really completely corrupt a display file by setting on an indicator sitting in an indds DS within a RPG program, which is not defined within the display file?
Cheers Larry Ducie
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.
midrange.com
