If yes, can you provide a link to a manual that shows COBOL syntax?
Besides using the SQL call level interface APIs, another solution is having the stored procedure place the result set in a global temporary table. Then, the COBOL and RPG programs can process the data in the global temporary table after the stored procedure call completes. This result set technique is covered in more detail in the following IBM Redbook: Stored Procedures, Triggers, and User-Defined Functions on DB2 UDB for iSeries.
Dig deeper on iSeries COBOL programming
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ...continue reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ...continue reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.