That is one possible way to go. But most like it does not work for larger projects with more programmers. In that casee one would have to use a batch job to check in all changed source members at the end of the day. But that is not how SVN or Git is intended to be used.
I considered to wrap each CRT* command to copy the source from a stream file to a source physical file before compiling it. But that is a lot of work and does not solve the problem of lost references to the stream file. Having an object reference to the temporary source physical file is useless.
So again, I wished IBM improved the existing CRT* commands to work with stream files. I wonder why they changed CRTBNDRPG and CRTRPGMOD but did not touch for example CRTDSPF and CRTPRTF, etc.
Maybe, they did it before they had the idea of i Projects. From the point of view i Projects are the way to go. I assume I have to try that with out ERP application.
Thomas.
-----Ursprüngliche Nachricht-----
Von: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im Auftrag von John Yeung
Gesendet: Dienstag, 31. März 2015 09:38
An: RPG programming on the IBM i (AS/400 and iSeries)
Betreff: Re: Standard source file names?
On Tue, Mar 31, 2015 at 2:27 AM, Thomas Raddatz <thomas.raddatz@xxxxxx> wrote:
Too bad, that most CL commands do not accept a stream file path name to compile the object. Also the object description lacks an attribute where the stream file name could be saved as a reference to the source file. I wished, IBM would change that.
Hm. Well, CRTBNDRPG and CRPRPGMOD both accept SRCSTMF. I tried it just now on an extremely simple program. It works. But I didn't see anything with DSPOBJD or DSPPGM which indicated the stream file which was used, so yeah, that's one downside.
I actually have a project which has all kinds of stuff (CL, RPG, Python, documentation in Markdown), and I've been using Mercurial as my version control. I don't use RDi. I've been keeping the CL and RPG stuff in source physical files and just downloading the date and data fields to my PC whenever I change them. (In other words, I keep local copies of the source as stream files for version control purposes, but I actually edit the source PFs, not IFS stream files.) It's definitely on the clunky and annoying side, but it's manageable for small to medium projects, in my opinion.
More significantly for most folks on this list: I am actually pretty happy with the way it's working out for me, so I can only imagine that something similar to my scheme would be even better using RDi and git.
John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
midrange.com
