A new client is on what appears to be a rpgIII evolved system with a MAPICS type architecture (many control files).
I'm running across a few programs that have a file declared in the f-spec with Update/add specified.
In the program they do no updates or adds. Just a read.
After questioning a couple of the programmers, they mumble something about the "workflow" requires it sometimes to avoid a CPF error.
Is there a valid reason for this I am overlooking. Maybe a common industry practice that was implemented at one time - is it sill valid?
I'm running across a few programs that have a file declared in the f-spec with Update/add specified.
In the program they do no updates or adds. Just a read.
After questioning a couple of the programmers, they mumble something about the "workflow" requires it sometimes to avoid a CPF error.
Is there a valid reason for this I am overlooking. Maybe a common industry practice that was implemented at one time - is it sill valid?
Comment