I worked on a big project for over 1/2 year, and used iProjects, it was a life-saver! I had to distribute and compile the code to 3 different IBM i boxes. Testing on Development/Q.A. And also a "Testing area" on production for beta testing/roll-out.
Using iProject is a little different, in that the master copy is on the PC/Network. Which breaks the typical paradigm of working directly on the source on the IBM i. That was biggest initial learning curve.
I pushed compiled from my PC, which in my case, it was perfect.
We wipe out our "Sand-box" Quality-Assurance box, and "flashed" with production data for testing. So, our source files were wiped out. And I did a few clicks and was able to push my approximately 40 objects to the box and compile. And I picked up where I left off!
Sure beats trying to manually do a SNDNETF for every member, receive them. And then manually do a 14-compile on the yucky Green Screen...
Using the "Remote Reconciler" view helps me to manage which source files I might have out of synch. Normally, not a problem. Because if using iProjects, I stay using in iProjects.
Using the Red-book and practice labs to explorer how iProjects works is very helpful, and that takes some time. The best way is get instructed by a professional Trainer with experience. But, that is not always available. But STRONGLY recommended! <Hint Hint>
Here is a short list why I love iProjects:
1.) Few clicks to push and compile 1 to 100's of objects! Awesome
2.) Able to compare source with previous History changes.
Right-click on member in iProject, and select:
>Compare with > Local History... (Every time you save, it has history)
That has saved my bacon a few times!!!
3.) Integration with our change management tool, Softlanding/Turnover.
4.) Back up remote source to project Archive. >Import remote source
5.) When using Service programs, copy-books, modules, etc. When I compile in iProjects. I get a list of all errors in a single window across all Members in my project. Very helpful when I missed a copy-book, and "fat-Finger" a prototype for a service program. I know it would have taken me much longer WITHOUT iProjects.
I guess my only minor annoyance, is I have to do a few extra clicks to push & compile, instead of doing my favorite shortcut key Ctrl+C to compile in Normal LPEX mode outside of iProject. <LOL>
But, that is okay, because it reminds me that I am working on the code I the iProject, instead of the old paradigm of editing the member directly.
I think my only stumble point, is working with Service programs within iProjects. I know about the "Compile.CLLE" to create my objects. But, I guess there is another "BIND.CLLE" program to create your service programs. That is the part I missing for some reason. Maybe because that is more manual.
I am one of those "strange ones", that likes those labs. To me, I learn by doing samples. Which is why I love IBM labs. But, I am the exception to rule on that. I probably should re-do the practice lab again! <grin>
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Wednesday, April 19, 2017 6:21 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Rob Cecco <cecco@xxxxxxxxxx>
Subject: [WDSCI-L] Feedback on iProjects - good, bad and ugly
As RDi architect, I want to make sure that I don't get out of touch with your experience in using RDi in the trenches.
For example, I might think that i Projects are a perfect way for people to be able to use Git on IBM i and maybe I am missing some reason why people are not adopting i Projects.
So please set me straight.
Who is using i Projects and if so how do you like it?
If you have tried i Projects and abandoned them, let me know why?
I am very thankful to have access to such a vocal group of customers that I can get unfiltered, immediate feedback from.
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l
As an Amazon Associate we earn from qualifying purchases.