Re: Something to read overlunch: Eclipse IDE in thebrowser

It IS possible simply to call any iSeries program from SQL - they are all implicit stored procedures. There are limitations here, however. I think you can add parameters and use parameter markers, which helps a lot. Then you don't need to explicitly create a stored procedure in the catalog.

Using stored procedures, whether implicit or explicit ones, protects your data, and that's a good idea.

Vern
-------------- Original message --------------
From: "Luis Colorado" <LuisC@xxxxxxxxxxxxxxxx>

So, do you mean that you are thinking about calling RPG programs using stored
procedures?

Well, IMHO you are just adding an extra layer of complexity that you don't need.
You are adding another piece that needs to be created, moved, tested, maintained
and tracked, and, thus, another possible source of errors.

On the other hand, if you think that using JDBC is user than JT400, you might
want to consider creating your own wrapper classes to make your life easier.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Thorbjørn Ravn Andersen
Sent: Wednesday, February 06, 2008 12:31 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Something to read overlunch: Eclipse IDE
in thebrowser

dnitke skrev den 06-02-2008 04:38:

a Rich Client product. The business logic is mostly RPG Stored procedures

mostly because its more effecient (current OS400 of course since V6.1 from what
I have read has more JVM memory for SQL) and it allowed us to re-use existing
logic (some). We use both JDBC to call the stored procedures and JT400
I'd like to hear your opinion on calling stored procedures as opposed to
doing ProgramCall's. Advantages beyond having easy access through SQL,
disadvantages, ease of debugging.

This is because I am considering if it would be an advantage for us to
investigate this more.

--
Thorbjørn