RTC 3 on Power - what licences
![](http://jazz.net/_images/myphoto/79760cdcf5a1e5baf98449484df1ad70.jpg)
Hi
I am looking through the info on jazz.net, and wanted to clarify usage of licenses for Power developers. Can we mix and match developers licenses - so can some users who do not builds, can they use "normal" developers licenses, and then the people doing builds use the Enterprise Developer licenses?
thanks
anthony
I am looking through the info on jazz.net, and wanted to clarify usage of licenses for Power developers. Can we mix and match developers licenses - so can some users who do not builds, can they use "normal" developers licenses, and then the people doing builds use the Enterprise Developer licenses?
thanks
anthony
2 answers
![](http://jazz.net/_images/myphoto/79760cdcf5a1e5baf98449484df1ad70.jpg)
Power Systems developers (IBM i, AIX, Linux on Power) can use a Developer or Developer for Workgroups licenses along with Rational Developer for Power as their IDE and have access to all the capabilities provided by those licenses.
They would not have access to the advanced Power capabilities provided by the Developer for IBM Enterprise Platforms license like the ability to do a dependency based build on IBM i. So they would need to compile their changes for unit testing outside of RTC or use an Ant or command line build definition. They would also not be able to query the build dependency information to know which other members need to be compiled as a result of the change.
Once the changes are delivered into a stream, someone with an RTC Developer for IBM Enterprise platforms license could then do a team build that uses the IBM i build specification and dependency analysis.
You can mix and match developer licenses on a single server; keeping in mind that mixing Developer for Workgroups with Developer or Developer for IBM Enterprise Platforms licenses disables distributed SCM capability for all the licenses.
They would not have access to the advanced Power capabilities provided by the Developer for IBM Enterprise Platforms license like the ability to do a dependency based build on IBM i. So they would need to compile their changes for unit testing outside of RTC or use an Ant or command line build definition. They would also not be able to query the build dependency information to know which other members need to be compiled as a result of the change.
Once the changes are delivered into a stream, someone with an RTC Developer for IBM Enterprise platforms license could then do a team build that uses the IBM i build specification and dependency analysis.
You can mix and match developer licenses on a single server; keeping in mind that mixing Developer for Workgroups with Developer or Developer for IBM Enterprise Platforms licenses disables distributed SCM capability for all the licenses.
![](http://jazz.net/_images/myphoto/79760cdcf5a1e5baf98449484df1ad70.jpg)
Yes, you can freely mix'n'match Developer licenses with Enterprise
Developer licenses. (At least, I have done so in my testing).
Cheers,
Geoff
On 11/10/2010 4:38 AM, kesterto wrote:
Developer licenses. (At least, I have done so in my testing).
Cheers,
Geoff
On 11/10/2010 4:38 AM, kesterto wrote:
Hi
I am looking through the info on jazz.net, and wanted to clarify usage
of licenses for Power developers. Can we mix and match developers
licenses - so can some users who do not builds, can they use
"normal" developers licenses, and then the people doing
builds use the Enterprise Developer licenses?
thanks
anthony