RE: Stored Procedure? with Result Set.

Great Link....  I think I saw an example in the book, that will allow me to
do what I need, thank you.

tim

> -----Original Message-----
> From: keith_mccully@xxxxxxxxxxxxxxx [SMTP:keith_mccully@xxxxxxxxxxxxxxx]
> Sent: Tuesday, March 11, 2003 2:18 AM
> To:   rpg400-l@xxxxxxxxxxxx
> Subject:      Re: Stored Procedure? with Result Set.
> 
> 
> >I would like to issue a sql command (my guess is, a stored procedure),
> but
> I
> >might be wrong...  But I would like to execute a RPGLE program, that
> would
> >create a muliple line result set, that can be passed pack to the calling
> SQL
> >statement.   But I would like to use native IO commands in the RPG
> program,
> >reade and chains...
> 
> Tim,
> 
> To do this you need to create an EXTERNAL stored procedure in SQL RPG.
> This
> is just an SQL RPG program (optionally using native IO commands) which is
> fronted by a SQL CREATE PROCEDURE statement.The RPG returns a declared
> multi-occur data structure as the result set.
> 
> For a good RPG ref check the red book 'stored procedures and triggers'.
> 
> http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246503.htm
> l?Open
> 
> 
> The only problem I have with this is that it seems that you are forced to
> declare the result set size ie. no of data structure occurances at compile
> time. Fortunately, my result sets are small! However, I seem to remember a
> previous discussion on dynamically allocating size or perhaps not??
> 
> Cheers,
> 
> Keith
> 
> 
> 
> 
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review, use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.