Discussion on "GitHub to IBMi: An incredible journey of RPG source"

Gajender Tyagi · 2022-11-14T12:05:48.565Z

Another blog post on the journey of IBMi modernization for code management. We will cover source hosting on GitHub, moving the source from GitHub to IBMi, and compiling all the sources. As we all must know that on IBMi we can natively do centralized ...

Gajender, good start here, can't wait until you show how to manage DDS ;) After all the primary strength of IBM i is DB2 and very few users have completed the conversion to DDL. Git can be used with ANY language since to Git it's just text files, the challenge is the Build.

Thanks Jeff

It will be a better idea to abandon DDS, and move to SQL for data base and HTML for user interface.

Could not agree more, but if I told a business, BEFORE you can use git you have to convert 1000 PF and LFs to SQL, then they wouldn't use git. Far better to say let's adopt git and manage the modernization with it because now you have one tool to manage your DB, your business logic and your interface. Git is fine with a conversion because it's a delete of DDS and a new SQL member and Make can handle the dependencies just fine once you've created the makefile. Git is fine with managing DDS and Make can handle it just fine as well once it has the appropriate instructions in the makefile Raul Alberto Jager Weiler

Jeff Tickner Thank you for the points you mentioned here. Maybe I will use a few DDS with program sources as a case study to show the build process and source management.

Search Hashnode

GitHub to IBMi: An incredible journey of RPG source

Responses1