RE: Communicating between java & rpg?

Simpler?  How?

        parms[0].setInputData(data);
        if (call.run() == false) {
                throw new Exception("Receive failed.");
        } else {
                data = parms[0].getOutputData();
        }

This is as simple as you can get, and it's bidirectional.  It passes data to
and from the program.  And evidently you misread the code, because it
doesn't pass 2200 parameters, it passes a single parameter of 2200 bytes.

No need for error trapping?  Are your stored procedures calling HLL programs
or executing SQL statements?  For the former, what do you do if your program
name is wrong, or your program ends in error?  For the latter, what happens
if the SQL statement fails?  How do you catch those conditions?  In my case
I could ignore the errors, but that's a pretty poor programming practice.

Performance?  Performance of native I/O is often much better than SQL,
especially when writing data - I recently posted the results of a test that
shows that updating data with an RPG program is five times faster than using
embedded SQL.  From what I understand, the JDBC driver is even slower.

If, on the other hand, you're calling an RPG program that does native I/O,
you have to parse the SQL statement and, for inquiries, build a result set
in your program.  I don't have to do that in mine.

No, native I/O is simpler, faster and more flexible than SQL.

Joe


> -----Original Message-----
> From: Tanveer, Mohammad
>
> Thanks,  I think stored procedures are much simpler than this.
> No need for
> error trapping and waiting for data (performance), debugging is much
> simpler, I am not sure why people want to pass 2200 parameters.  May be a
> old design concept. Anyways at least I know how to call an AS/400 program
> and pass parameters.  Thanks a lot.