Re: Adoption of RPG OA (Summary)

Hi Joe,

<snip>
Why is the chain better than the call? The more I see this, the more I
have a problem with usurping a known opcode. Prior to this, READ/CHAIN
was getting data from a database. Now I'm not really sure what it's doing.
</snip>

It isn't. It is just an alternative. You play to your audience I guess. If you work in a shop where service programs and encapsulation are new then maybe a chain with a handler will do the trick.

I would imagine that this is at the heart of what Henrik was driving at - we SHOULD teach the developers about service programs and encapsulation rather than "usurp" the chain op-code.

On a professional level I totally agree with him on the point about training and development. But where I work we DO teach our developers these things. This doesn't stop us evaluating what IBM offers. Stricly speaking we are evaluating RPG OA to see if there is anything it offers that we can use. We have no "plans' to use it. Two developers are evaluating it as part of their professional development plan. They wanted to see if they could do something with it, and it is possible that the company may benefit from their endeavours. Sometimes something really good comes out of these things. Its a win - win. If we don't use it at least the developers gain knowledge in new areas, which still benefits the development pool.

<snip>
Anyway, enough on this particular topic. Either way works, and they're
both doing essentially the same thing. I think it really is opinion at
this point.
</snip>

I think the heart of the issue with RPG OA is that it may well be a solution looking for a problem, and I'm just be doing my best to find one! :-)

But Vern sems to be doing great things with RPG OA so there is still hope.

Its been a very stimulating thread.

Cheers

Larry Ducie