I need to call a DB2 SQL stored procedure with one in parameter from a CL program. For example:
CALL LIBRARY/PROGRAM PARM(variable)If use this command, it doesn't work because of the parameter. What's the best way to handle stored procedures?
Stored procedures must be called with an SQL call statement because there are hidden internal parameters that DB2 must pass on the stored procedure call. The CL Call command cannot pass the special internal parameters. That's why you're seeing an error on the CL Call command.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this Search400.com Featured Topic: Database issues resolved
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
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
IBM did not change the default of the reuse deleted files function to YES for physical files in order to minimize the impact on any existing ... 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.