Re: RDi licensing - single PC and multiple AS400's

Joe Pluta wrote:

So anyway, long story short, RDi is what *you* used WDSC for, Buck. It was *not* what WDSC is. RDi-SOA for Java is what WDSC really is.

Yes, thank you.

Message ID . . . . . . : EDT0630
Message . . . . : Have you tried the modern alternative to SEU? Press F1 for more details.
Cause . . . . . : WEBSPHERE DEVELOPMENT STUDIO CLIENT is part of the tool set that you already own.

Yup, *at the time* WDSC was the replacement for ADTS.

That time was this morning.

The only thing you're complaining about is that you have to pay for RDi.

Yes. Given the ten year odyssey and the likely fact that RDi (let's call it Lpex; that and RSE are all most RPG programmers need) Lpex isn't going to get any significant enhancements over the next ten years, it seems a lot of money to spend to tread water.

I love Lpex, use it every day. When I switch editors it's most often Code/400 because I get 2 things from it that I lost with Lpex: Integration with Windows (I can click on a file in Explorer and invoke Code/400) and Rexx macros.

After a decade of using IBM's GUI tooling, my considered opinion is that a simple Code/400 + PDM integration is very appropriate for many RPG programmers. In my opinion, IBM would have had more luck deprecating (charging for) SEU, giving away Code/400 and spending their development dollars on RDi-SOA. Us green screeners just aren't going to get much oomph out of all the stuff in RDi - the whole Eclipse workbench is too much... stuff. That's an opinion, not a challenge.

Once people were comfortable with Code (it is extremely stable now) the advanced companies could move up to (and pay for) RDi-SOA and leave us backward folks alone with Code, just like IBM are doing with SEU today.

Keeping (er... skulking back) to the subject:

Let's say I want to get into contracting and I buy a retail copy of RDi. Can I use that to connect to multiple client i machines, or does each client need to install something before that will work?

Everybody needs the back-end component, just like every client you talked to originally had to install 5722WDS feature 60.

The issue is the licensing has changed to a per-seat license. Do I personally own that license to option 60? Can I load that on a dozen IBM i machines, or must I buy a dozen 'per-seat' licenses, one for each i? I haven't had much luck with my BP. We are a small fish in his very big pond, so thought I'd ask here. It might end up on the TODO list if I'm lucky.