|
Hello,
When IBM added null-capable support to RPG they added it only for externally described file specs, they did not add it for internally described file specs. (No, I don't know why.) Since WRKDBF must be generic and cannot possibly know what file will be used at execution time, I have coded a long internally described "F" spec to cover all the possible files that might be used. However, doing so makes nulls problematic.
Instead of using a long program-described F-spec, you'd be better off calling the _Ropen() and _Rreadn(), etc, APIs from the ILE C runtime library. Although designed for C, you can call and use these from an ILE RPG program without any problems.
They allow you to check the null map, do keyed operations, all sorts of things. You can do all of that without any need to know what the file will be at compile-time.
Of course, you're abandoning the project and not allowing anyone to take it over in your stead, so I'm really wasting my time posting this message. Too bad!
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
