It's all about the answers!

Ask a question

Is RCT a good replacement for Harvest + Endeavor?


Shahzad Chaudhry (111) | asked Dec 08 '10, 12:11 p.m.
My client is using Harvest and Endeavor as SCMs for non-Mainframe and Mainframe code. I would like to propose RTC but the question is whether RTC will remove the need for keeping two separate SCMs (Harvest and Endeavor).

Any expert advice will be really appreciated.

Regards,
Shaz

2 answers



permanent link
Bernd van Oostrum (21724565) | answered Dec 08 '10, 12:43 p.m.
Hi Shaz,

I would say 'yes', but all depends on the specific environment and the habits of the customer. RTC is very good to keep track of versions, builds and issues (workitems). Everything is integrated. In our solution that is running in production for several customers now, we only store sourcecode in the RTC-repository. Everything that can be reproduced isn't in RTC and gets compiled on the mainframe on manual or scheduled request (standard build functionality).
http://www.asist.be/v1/solutions/documents/ASISTRBDRTCIntegration1.0.pdf contains a general description about our solution that was build to support EGL-code, but it can be adapted for any type of source-code.


Regards,
Bernd
www.asist.be




My client is using Harvest and Endeavor as SCMs for non-Mainframe and Mainframe code. I would like to propose RTC but the question is whether RTC will remove the need for keeping two separate SCMs (Harvest and Endeavor).

Any expert advice will be really appreciated.

Regards,
Shaz

permanent link
Geoffrey Clemm (30.0k23035) | answered Dec 09 '10, 1:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In most cases, I would say "yes".
Unlike Harvest (which does not run on mainframes) and Endeavor (which
only runs on mainframes), RTC is designed to run natively on both
mainframes and non-mainframes (allowing you to decide where you want
your server to run, and then allowing both mainframe and non-mainframe
clients to talk to that same common server).

Cheers,
Geoff

On 12/8/2010 12:53 PM, berndyman wrote:
Hi Shaz,

I would say 'yes', but all depends on the specific environment and the
habits of the customer. RTC is very good to keep track of versions,
builds and issues (workitems). Everything is integrated. In our
solution that is running in production for several customers now, we
only store sourcecode in the
RTC-repository. Everything that can be reproduced isn't in RTC and
gets compiled on the mainframe on manual or scheduled request
(standard build functionality).
http://www.asist.be/v1/solutions/documents/ASISTRBDRTCIntegration1.0.pdf
contains a general description about our solution that was build to
support EGL-code, but it can be adapted for any type of source-code.


Regards,
Bernd
www.asist.be




ShahzadChaudhrywrote:
My client is using Harvest and Endeavor as SCMs for non-Mainframe and
Mainframe code. I would like to propose RTC but the question is
whether RTC will remove the need for keeping two separate SCMs
(Harvest and Endeavor).

Any expert advice will be really appreciated.

Regards,
Shaz

Your answer


Register or to post your answer.