More benefits of Rational Developer for i
As we continue to explore the merits of Rational Developer for i, one of the handy features (at least from your boss's perspective) is the ability to develop offline. In RDi, you may create any number of containers known as iProjects. These are created from within Remote Systems Explorer by clicking File, New, Project and IBM i Project (which you may have to drill down to). Any source physical file and/or any of the members contained within may be downloaded to an iProject by simply right clicking on it and selecting "Add to iProject". Choose your desired iProject and the source is magically downloaded to your hard drive. The iProjects themselves are simply folders contained within your Windows Documents and Settings directory, buried inside the IBM folder tree.
The Projects perspective allows you to navigate through your locally stored iProjects, much like RSE allows you to navigate libraries and files contained on System i. The big difference is that you need not be connected to your System i. You can be at 33,000 feet and still writing code instead of just reading SkyMall magazine and munching on oversalted peanuts. The LPEX editor will not care - it will provide the same syntax checking and outline capabilities you'd have in your cubicle.
Of course, one thing you cannot do is compile. Sorry, but the compiler exists only on System i. Don't expect that to ever change. However, RSE does allow you to verify your source code, which is the next best thing. Problem is, what about all those externally described data and device files that the compiler ever so nicely imports for you? IBM thought of that, fortunately. Any physical or device file object in your Remote Systems pane or Table View can be right clicked on and selected for "Cache File Descriptions". This little gem will import all record layouts in a manner which is friendly to the source code verifier. So while we can't compile and test from the road, we can at least do the majority of our coding and get those pedantic syntax errors cleaned up before we start chewing up CPU cycles with the host compilers.
After you've arrived safely back at the orifice, right click on any iProject or any of the components contained within, then select Remote Actions and Push Changes to update your source to System i. Naturally, the larger your programming staff, the more complex the issue of change management and version control gets, so most of the vendors in this arena provide plug-in products for RDi to officiate this more effectively. Rational has their own offering, known as Team Concert for i, although it is still in its infancy.
So would you consider cranking out RPG once the captain has turned off the seat belt sign ?
Thanks for sharing. Chris.
