Thanks for the note Karl.--
I already told them there are commercial packages for getting the
change control/object deployment thing done, but they are already
invested in GitHub for other platforms and are implementing Git using
my iForGit client
(http://www.iforgit.com) to manage capturing the IBM i source changes
The managing source to GitHub piece works fine, but now they really
want to manage the object deployment process but don't want to invest
in a full blown solution.
Their overall dev process is pretty simple. It's just coming up with a
way to manage a few of the gaps like object deployment and making sure
all objects that might be affected are identified. DSPPGMREF seems to
do a good job of illuminating some of that info.
If at some point they decide to go another direction I will certainly
let you know. But for the time being it's homegrown object deployment.
date: Wed, 24 Nov 2021 16:23:41 +0000
from: Karl Haggart <karl.haggart@xxxxxxxxxxxxxxxxxx>
subject: RE: Deploying DB2 Table Changes
Have you and the team considered a change control solution to manage
all of the complexity?
It does free up a lot of time for the development team and resolves
all of the issues you mentioned with copying data and recompiling
related objects, alongside the distribution of the changes to the test
and production machines.
Very cost effective too.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.