from: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
subject: RE: Deploying DB2 Table Changes
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
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.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.