We have some files at work that have fixed length physical file fields of type 'S' with length 5. Well the completely unexpected thing happened (sarcasm) where you eventually run out of numbers.
Is there a way to update the physical file fields' type without having to re-compile every RPG program that references that file? Another issue is the display files were set to mimic that field length as well.
Is there an 'easy' way to accomplish this? I mean, there are a TON of programs, CL programs, query procedures and etc. This is a system that has been developed and has had modules added to it since the early 80's.
The solution proposed is to simply add a separate key field that is used to further extend the use of those 99,999 unique id annually.
I kind of feel like this is just helping it limp along until the next time it 'breaks'.
Thanks for any help,
Justin
I'm a .NET developer and use SQL Server frequently.
Is there a way to update the physical file fields' type without having to re-compile every RPG program that references that file? Another issue is the display files were set to mimic that field length as well.
Is there an 'easy' way to accomplish this? I mean, there are a TON of programs, CL programs, query procedures and etc. This is a system that has been developed and has had modules added to it since the early 80's.
The solution proposed is to simply add a separate key field that is used to further extend the use of those 99,999 unique id annually.
I kind of feel like this is just helping it limp along until the next time it 'breaks'.
Thanks for any help,
Justin
I'm a .NET developer and use SQL Server frequently.
Comment