Right. Thus the complexity.
In my scenario you can assume V7R3 and higher.
There could be: DDL, DDS, add new fields, remove fields, resize fiels, add indexes, add logical files, the list is endless.......
And any one of these things can then cause level checks for RPG, COBOL or CL programs.
I knew this wouldn't be a simple question, but I'm curious where to start.
And in the end the answer may be: manually rename/move old table, manually stage the new table and copy data back, then recompile all the associated objects to avoid level checks.
Which also begs the question as to whether DSPPGMREF has any alternatives to id potentially affected changed programs.
I'm working with a IBMi dev team who is going from single box development to have a dev/test machine and production machine and trying to make their deployment options easier.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------
message: 6
date: Wed, 24 Nov 2021 14:37:37 +0000
from: Alan Shore via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: RE: Deploying DB2 Table Changes
Hi Richard
The answer to your question is tape recording number 26 It depends First - what release are you on? If you are on an extremely old (decades) release, you may have no choice What change are you doing?
Adding one or more new fields?
Changing an existing field - if so - from what to what
Alan Shore
Solutions Architect
IT Supply Chain Execution
[NHScsignaturelogo]
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx
midrange.com
