To continue reading for free, register below or login
To read more you must become a member of Search400.com
On DB2 UDB for iSeries, stored procedures result sets can only be accessed by clients utilizing the ODBC, JDBC, or CLI programming interfaces. This means High Level Languages (HLL) such as RPG and COBOL cannot fetch the result sets generated by an invoked stored procedure. Your COBOL program could utilize CLI APIs to invoke the stored procedure and process the result set. Another workaround is to use global temporary tables to simulate a stored procedure result set. A global table is used to hold temporary data for a database connection (job) or application. Instead of an SQL procedure returning data via a result set, that same data could be placed in a global temporary table and then the invoking COBOL program would just have to know the name of the temporary table in order to access the result set data. ==================================
MORE INFORMATION ON THIS TOPIC
==================================
Visit the ITKnowledge Exchange and get answers to your DB2 questions fast.
Check out this Search400.com Featured Topic: Expert advice on DB2
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: Tips, tutorials and more.
|
