RE: Source Change Tracking/Dependencies

For this particular use case, perhaps a combination of DSPPGMREF, DSPFFD, DSPDBR, etc. along with some SQL might be a viable option.


Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Saturday, January 21, 2023 2:17 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Source Change Tracking/Dependencies

Hello Jim,

Am 21.01.2023 um 22:34 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:

Honestly Patrik, given your skills in Linux and most likely GIT I would set
that up using shares to the source files for source control.

Git doesn't help me with the task I have described. Allow me to explain.

I'm changing a physical file. E. g. making a field larger. That PF might be referenced by LFs, by DSPFs, by PRTFs and finally by PGMs.

I want to lessen the thinking effort about which objects need to be recreated after that change. This is a routine task. Routine tasks are usually perfect candidates for being automated. :-)

I'm not talking about source change tracking (git, cvs, etc.). What might come close is TMKMAKE, which I'm currently looking at closer.

Just wanted to get some input if there are other possibilities available.

That software from IBM was interesting however I don't know anyone that actually used it.

Interesting!

:wq! PoC