Re: Compiling after file changes

On 28/05/2010, at 7:59 PM, David FOXWELL wrote:

Scott used getters, I believe, for each field of the file. Management doesn't like the look of all those getters, though. Now, if in place of the getters, a program could call a procedure in the i/o module that simply returned the file record in a DS....

Well accepted standard in the OO world. Common as mud and makes a lot of sense. Tell your management weenies that I said they were a bunch of numptys and it's time they got with the program.

<crunching noise as brains engages first gear>
1. Situation today : any file change means recompile all programs because of level, file is referenced in almost all programs.
2. Put the i/o module in a service program. Am I right in saying that now, DSPPGMREF will no longer find the file?

True, it will only be referenced in the service program module.

2a. If the procedure in the i/o module returned the file record in a DS, all callers will still need to be recompiled to change the DS in the caller?

Yes, but you resolve that by including a level request as part of the I/O interface so programs requesting level 1 get a data structure that is how the record looks today, those requesting tomorrow's level 2 will get a different structure with new fields added (or old ones removed, or both), and so on.

2b. If a getter is used for each field instead, there would be no reason to recompile the callers that did not use the field that changed in the file?

True, but also no reason to recompile callers if a DS level number is used either.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------