I can give better wordy description...

I have a standard IBMi RDi project with several IBMi source physical files defined. There are a couple of hundred source members in those source files. For this problem, there's no IFS involved. These have at some stage been pushed to a library on the IBMi. However, this workspace is out of date i.e some source files in the IBMi library contain members with newer change dates. I want to sync these so that the latest version is imported into my RDi project from the IBMi. Essentially I want to compare my RDi project with the associated IBMi library contents. Now, what I can do is push the project files to a different IBMi library and do a compare and then figure out what to do but I was hoping there was an invisible feature to do this.

On 3/10/2023 4:40 PM, Jack Woehr via MIDRANGE-L wrote:
Can you draw a diagram in ASCII of what you're trying to do here?

If it's just a question of "how do I get one more source member into the
IFS to join its friends?" the answer is CPYTOSTMF.
If the question is, "I have a mixed project, how do I get a source member
into the RDi workspace to join the stuff in the IFS folder?" ask on the
WDSCI list where the RDi team hangs out: wdsci-l@xxxxxxxxxxxxxxxxxx

On Fri, Mar 10, 2023 at 4:45 AM Tim Bronski <tim.bronski@xxxxxxxxx> wrote:

Thanks Jack,

I did have a look at the iForGit. The issue I have is (probably) a one
time thing. Most of the source code is in IFS but in this case I
inherited an older RDi workspace that has this project in it. I think
it's a little out of date and out of sync with the source on the IBMi. I
could just recreate the project using the IBMi source but I was hoping
RDi had a better way to load or import a source member individually.

On 3/10/2023 2:42 AM, Jack Woehr via MIDRANGE-L wrote:
If it's in the IFS you can revision control the whole project.
You can also mount the IFS directories on your local disk using SSHFS and
operate revision control in that fashion.
And you can use iForGit for the OFS portions and separately check in the
project data from your RDi workspace in another dir and use the same
origin
repository as the main repo.
There's all sorts of way to do this.
Rule 1: Forget the classic inflexibility of IBM i development. Open
Source
has opened up our legacy box.

On Thu, Mar 9, 2023 at 6:17 PM Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hey Jack!! I wonder if I see a bit of a challenge here. Tim said he is
using an RDi project - the challenge might be integrating that with git.
Richard talks about his iForGit can work with RDi, but with projects?

Just askin'!!

Cheers
Vern

On 3/9/2023 10:57 AM, Jack Woehr via MIDRANGE-L wrote:
This is called "revision control" and that's what Git is for.

- If you move to working in the IFS, it's a no-brainer.
- If you want to stay in source physical files in the OFS, then
iForGit
<https://www.iforgit.com/> can offer you Git revision control on
those
objects.


On Thu, Mar 9, 2023 at 8:50 AM Tim Bronski <tim.bronski@xxxxxxxxx>
wrote:
I've got a source file on the IBMi with some source members that have
been edited separately, and more recently, than the copy I have in a
project in rdi. Is there an automated way to update the local source
file in a project from the remote copy, if the remote has a newer
timestamp?
--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.