Re: Best way to convert from source PF to IFS source

You can use my little tool from my github gist:

copy_source_to_ifs.sql

https://gist.github.com/NielsLiisberg/c028c3b5c8a31be227463fe0d677233b

Or if you want to make it a git repository:

export_source_to_git.sql

https://gist.github.com/NielsLiisberg/97cc1ff39a4e219927a70078ec05df61


On Tue, Feb 13, 2024 at 2:01 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

Unfortunately I don't think this question ended up offline. At least I
didn't see an email from you.

Anyway it's a good question.

Usually if a company has a home-grown source control system that does
object distribution as well, my first question would be:
What's wrong with your current system for source and object distribution?

You're correct a tool like iForGit is essentially a green screen command
driven git client that allows you to save and restore source members to a
git repository.

By default git nor the iForGit product does not do automated source build
or object distribution. It manages source members. (Although I am working
on an addon for this for iForGit plus there are other build systems
available).

In your company's situation I might mention that iForGit can extend your
existing source control system by adding git into the mix to also store
versions in a git repository. But won't currently replace you auto-build
system.

It augments instead of replaces your existing change management in this
example.

That may or may not check the box for all custom shops, but might make
sense to add some level of external audit control of source members if
auditors or other dev teams are mandating git.

Hope this made sense. Feel free to continue the discussion here or via
email.

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

message: 5
date: Mon, 12 Feb 2024 19:40:38 -0500
from: smith5646midrange@xxxxxxxxx
subject: RE: Best way to convert from source PF to IFS source

Offline question <<<<

The company I consult for wants their iSeries developers to use GIT. They
have a home grown change control system that installs source and objects
from environment to environment. I know you have a GIT product so I'm
thinking that you are a good person to ask this question.

Everything that I read about GIT says it is source control. I can't get
anyone at the company to walk me through a GIT "install". Is GIT strictly
source control or can it also handle object installation? If there is some
good documentation that you can point me toward, I have no problem reading
stuff.

Thanks for your time.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Richard Schoen
Sent: Monday, February 12, 2024 12:41 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Best way to convert from source PF to IFS source

FWIW: You don't have to move all your source to the IFS to get the goodness
of something like VS Code.

If you really just want to do a one time move I'm happy to give you a 7 day
trial license of iForGit to run the export process on your libraries.

You can export with or without source dates and source metadata info in the
headers. This can also set up structured repos for you in the IFS that you
can push to Github or any other remote git platform.

Then you just have to figure out the day-to-day compile processes all anew.

A more moderate approach would be to leave your source files intact and use
something like iForGit to export and manage your git source version
archival.

Then you can version to git equally from SEU, RDI or VS Code and even
custom
processes.

Or you can just roll your own utility or I recall Liam had something at one
point. Maybe even part of Code for IBMi for exporting.

https://www.iforgit.com

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

message: 6
date: Mon, 12 Feb 2024 11:19:55 -0600
from: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
subject: Re: Best way to convert from source PF to IFS source

Yea, I get that part, however one must move with current trends, and RDI is
becoming ever so difficult particularly with the latest disaster of moving
to 9.8, so we've moved on to VSCode for better or worse. Therefore the
direction that feels right is to use GIT, and that mostly eliminates your
need for source dates if implemented properly.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


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