×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
midrange.com
