Daron,
Would you be willing to share how you're managing your IBM I source within RTC ?
It appears that you have to put all your source into an IBM I project on the PC and then push stuff up to the I when needed.
I would be interested in doing a Gotomeeting session if you're open to it since we've not been able to find anyone who has been able to demonstrate a real-world scenario to us.
Your team's knowledge could help others of us who are struggling to see how exactly it fits.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----Original Message-----
message: 1
date: Fri, 21 Oct 2011 18:30:04 +0000
from: Daron Whitehouse <dwhitehouse@xxxxxxxxxx>
subject: Re: [WDSCI-L] Rational Team Concert / Jazz
We've been using RTC for nearly 2 years now and I can say we are not using it to its fullest just yet (just a matter of free time to learn/explore). It has been very helpful for promoting changes into production using the build COMPILE method (we only compile what is need instead of the whole component or entire application). This means we have to hand code out COMPILE build each time (using snippets). Our downtime window for planned and unplanned upgrades on production is less than 2 minutes total time getting users off the system and then running the COMPILE build since the COMPILE build has already been proven when promoting into the Q/A environment.
Unlike Turnover, RTC does not know and subsequently recompile dependant objects. It is up to the developer to build the COMPILE script if dependant objects needs to be compiled also. This has not been too significant for us since our changes tend involve few objects at a time. Having vendor software - which we do freely modify- tends to minimize any drastic changes that require system-wide recompiles.
Watching the "Block comment" thread exemplifies just one area which RTC - and other SCM's - come in handy... When we encounter code that has become deprecated, we freely delete the code knowing that RTC maintains visibility via Show History.
RTC really shines with our Java and EGL projects. Delivering change sets from one developer to the team is a synch. I favor the optimistic locking especially with modularized RPGLE sub-procedures and java packages as it is feasible for two developers to be in the same source code at the same time but making changes to completely different sections of the code (i.e. 2 different procedures). Those times when changes to the same section of code occur, RTC's auto merge capabilities has done well for us.
We're using SQL much more than traditional AS/400 shops and I'd like to hear from those who have incorporated SQL and the Data Perspective into RTC. I can visualize using a Data Project with RTC, but have been unsatisfied with the Data Perspectives lack of IBM i specific syntax; particularly with Stored Procedures and Functions which we rely on quite a bit.
FWIW,
Daron
midrange.com
