RE: Deploying DB2 Table Changes

Hi Charles,

We are Remain have solutions for deploying large tables quickly too, and our solution works integrates perfectly with Git.

Take a look at https://remainsoftware.com/tdoms or reach out if you would like to see anything explained in more detail.

Cheers,
Karl.
              

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Wednesday, November 24, 2021 10:16 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Deploying DB2 Table Changes

Unless they've already built a solution...and it works perfectly for their needs and/or they want to dedicate a team to running and maintaining it.

Investing in a solution for deployment is a no-brainer IMHO. I first installed Aldon CMS in a shop where I was the only developer maintaining a customized vendor package. Besides handling vendor updates, it let me concentrate on adding business value, not worry about getting stuff deployed properly.

I'd expect a modern IBM i CMS to work just fine with Git...

I don't know it your client has large tables or not, but I just ran across this product..
https://www.midrangedynamics.com/mdrapid-deploy-database-changes/

Sounds pretty sweet, I might recommend my employer take a look...large tables are the bane of our deployment team.
The fact that it's certified for the new Db2 Mirror functionality is awesome to see.

And in fact their CMS product
https://www.midrangedynamics.com/change-management-details/

says:
Manage native source in source files or stream files, including automated integration with Git and SVN

Charles

On Wed, Nov 24, 2021 at 9:58 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

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
to GitHub.

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.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx


------------------------------

message: 4
date: Wed, 24 Nov 2021 16:23:41 +0000
from: Karl Haggart <karl.haggart@xxxxxxxxxxxxxxxxxx>
subject: RE: Deploying DB2 Table Changes

Hi Richard,

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.

Thanks,
Karl.

? ????????????

--
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,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com