AW: DB2 Stored Procedures

Stored Procedures are nothing else than programs written in either an HLL
(such as RPG, COBOL or even CL) or with pure SQL, that can be called from
any interface that supports (embedded) SQL. For to use programs (or
Procedures without return value) written in an HLL as stored procedures,
those programs must or at least should be registered with the SQL Command
CREATE PROCEDURE.

In this way RPG programs can be easily called from languages such as JAVA or
PHP.

Stored Procedures written with pure SQL will be converted into C-Programs
with embedded SQL. (iSeries Navigator debugger allows you to either debug
the SQL or C code).
SQL supports everything you can use with embedded SQL plus several control
statements, such as WHILE, LOOP or REPEAT to loop through the data or IF and
CASE for conditions etc.)

Using stored procedures within client server application will reduce the
traffic between client and server, because in an stored procedure several
actions/steps are bundled.
That means a single call versus a several actions.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Dan Rasch
Gesendet: Saturday, 06. November 2010 03:53
An: midrange-l@xxxxxxxxxxxx
Betreff: DB2 Stored Procedures



I am researching the used of DB2 Stored Procedures,
and from what I have seen, the look very similar to SQL scripts.

What are the advantages / trade-offs?

How do they compare to internal SQL, or even API's
for retrieving/modifying records?

Thanks,
- Dan