Re: What Programs are using my service program? (changes to a PF)

I feel I need to explain why my reaction as my mind was a bit blown.

I also had a  Never Ever.   Never Ever change an attribute of a field in a PF.  Only ever add a new field to the back of the list of fields so that no existing fields displacement is affected,
I implemented that protocol to solve the Y2K issue.  All new date fields had a YYYYMMDD format.  In that manner only programs that output the dates and programs that needed to do date calculations needed modification.

Combining the two Never Ever protocols would have made data base changes so much very very simpler.

Frank



On 15/08/2020 8:35 pm, Frank Kolmann wrote:

WOW.  So simple.  After 30 years of RPG coding the PF trick NEVER occurred to me. WOW only ever use lgl files.    KISS, I am so stupid.

Frank



On 15/08/2020 3:25 pm, D*B wrote:

There is no need to change a procedure interface - never ever. The clean way is, to add a new pocedure with the modified interface, after this making changes where ever the modification is needed, if nobody is using the (deprecated) procedure it could be removed if somebody wants to remove. As a note aside: the new peocedure and the deprecated procedure could share most of the implementation logic.

BTW: same is true for most changes to PFs: use views only to access tables and don't change a view - never ever!!!

D*B