Re: Stored Procedures

[DLee@xxxxxxxx]

Hello

In talking to one of my fellow programmers, he tells me stored procedures 
can't be used to retreive data file data from th iSeries to a network 
server.  He says they can only be used to pass parameter type data back a 
forth.

To me the term SQL means I can select and pull data files back a forth. In 
different examples I see on the web, it looks like data can be moved back 
and forth.
Since I don't work with the pc world much, only iSeries, I'm not real 
expert in that area.

I have an application coming up where I where I was planning to use stored 
procedures to allow a C# programmer to retreive database data from the 
iSeries, so I'm kind of interested in wanting this to work.
What's the real scoop?

Appreciate any help.

Darrell Lee
Information Technology
Extension 17127



rpg400-l-request@xxxxxxxxxxxx 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/17/2009 12:01 PM
Please respond to
rpg400-l@xxxxxxxxxxxx


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
RPG400-L Digest, Vol 8, Issue 198






Send RPG400-L mailing list submissions to
                 rpg400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
                 http://lists.midrange.com/mailman/listinfo/rpg400-l
or, via email, send a message with subject or body 'help' to
                 rpg400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
                 rpg400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of RPG400-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text 
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

   1. Re: New parameter needed for a subprocedure (rob@xxxxxxxxx)


----------------------------------------------------------------------

message: 1
date: Tue, 17 Mar 2009 10:54:18 -0400
from: rob@xxxxxxxxx
subject: Re: New parameter needed for a subprocedure

If it makes reasonable sense to me to use a return variable, then I'll use 

a return variable.  This allows me to:
- use it in a expression
- make an SQL UDF out of that expression, if needed.
http://faq.midrange.com/data/cache/185.html

I see a lot of stuff (even here) still created as separate program calls. 
Where there are multiple parameters and only one of them is expected to be 

returned.  I say make it a subprocedure with a return variable.  Then, if 
you have the dinosaur that will only use a subprocedure at gunpoint then 
simply wrap the subprocedure with the separate called program and they can 

use that.  It shouldn't be the other way around.

Rob Berendt