Re: Open Access for RPG

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

It can process anything any way.

While this may not be the "best" approach - one could for example  
define a logical where the key fields were the WHERE clause values in  
an SQL SELECT. The RPG program then does a CHAIN or a SETLL/READE  
using those key values and under the covers SQL is used (against a SQL  
Server or whatever) to retrieve the data. If a result set is returned  
the handler can buffer the records and feed them back one at a time on  
the READs.

You would have to add a lot more code to your example to achieve what  
you get from OAR. For instance the key field names and values, the  
data field names, types, and values etc. etc. And it still wouldn't  
have the "RPG Feel" that the OAR solution has. And that is the  
important bit.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On Jul 22, 2010, at 11:51 AM, rpg400-l-request@xxxxxxxxxxxx wrote:

> if I read this is correct ...
>
> The RPG OA handler approach is like a simple file server for
> traditional RPGLE opcodes, but not for processing RPGLE Native
> SQL.
>
> It could as well be done like this ....
>
>              eval     FILE = 'MYTABLE'
>              eval     OPCD = 'CHAIN'
>              call     'MYHANDLER'
>              parm     FILE    // file
>              parm     OPCD    // operationcode
>              parm     RTCD    // returncode
>              parm     BUFFER  // datainterface
>              if       OPCD = '*OK'
>                ***   do something
>              else
>                ***   do something else
>              endif