Thanks for the info. We're currently on 4.0.1
I put in an RFE yesterday asking if there might be a way for the Rational Folks to update RDP to allow me to open a local source member from the PC and do a simple save as to the i.
This would streamline the interaction between PC directory and i. If anyone thinks this would be useful, go and vote for the feature at the IBM RFE site. Search on SVN
Or maybe I'm just missing something. It seems so easy. Open source. Save as or push to i. :-)
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Fri, 18 Jan 2013 14:09:08 -0500
from: Jeffrey Tickner <jtickner@xxxxxxxxxxxxxxxxx>
subject: RE: Retrieve Source change informatio
Rational Team Concert is good for task and requirements tracking as we use it, but klunky for source management. I've tested the SCM component and you have to set up i projects with RDP >and check out ALL members.
Richard, take a look at sparse loading in RTC 4.
In RTC 3 sparse loading was a painful process that required that you create the iProject correctly, load the individual source member and then load the individual source metadata (each time keying in the iProject directory location correctly) before you could compile and build the changed source.
In RTC 4 once it's configured you do a Source Code Data Query, right click the member in the resulting view and choose load..., select the workspace on the prompt, select the iProject associated with the workspace and the source (with all metadata) will be loaded in the iProject.
Even better, if there is no iProject associated with the workspace one will be created dynamically and correctly!
When your done editing and compiling the source and you've checked in and delivered, you can just delete the source member or even the whole iProject.
The member will NOT show up in pending changes as a deleted member like in RTC 3.
Very easy to work with a subset of source and keep the amount of source on your workstation under control.
Now configuring a stream so that the Source Code Data Query actually returns results, not easy.
It was the article on the dependency build that helped me figure it out.
as the same metadata about your source that supports the Source Code Scanners is also what makes the Source Code Data Query work.
I really haven't played with the Dependency Build itself as the Arcad Rational Power Pack is a more intelligent tool for that and supports ILE without a build script.
Please only print this email if really necessary
55, rue Adrast?e - Parc Altais F-74650 1, Phoenix Mill Lane - Suite 203 -
CHAVANOD Peterborough NH 03458 - USA
Tel. +33 (0)4 50 57 83 96 Tel. + 1 603 371 9074 ext 505
Cell. +33 (0)6 11 15 69 59 Toll. free +1 800 676 4709 ext 505
***This e-mail and its attached documents are confidential and intended solely for the use of the addressee(s). ARCAD Software can in no way be held responsible for any damage resulting from an incident involving security, integrity, virus or transmission delay. As the integrity of this message cannot be guaranteed on Internet, the ARCAD Software company cannot be held responsible for its contents. Any unauthorized use or dissemination is prohibited.***