Hi Richard,

All makes sense for sure, and using Git is a great idea too.

Have you taken a look at the catalog views:-


There is a lot there that you can use to build a routine that identifies all related objects to table/file changes.

Hope that helps too,

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Richard Schoen
Sent: Wednesday, November 24, 2021 8:58 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Deploying DB2 Table Changes

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.

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.


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

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.