Can you explain the difference between SQL and stored procedures -- used in DB2 UDB 7.2 (Windows environment) and DB2/400 (iSeries environment)?
The DB2 UDB SQL stored procedure support for Windows & iSeries is virtually identical when comparing 7.2 with OS/400 V5R2. The DB2 Windows & UNIX versions do require a C compiler to be installed - while the iSeries does not have this requirement (starting with V5R1).
There's a small difference on the FOR loop support. The iSeries FOR statement does not yet allow unnamed expressions to be defined on the select list of the FOR cursor definition. Expressions can be included on the select list as long as the expressions are named.
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 online event, Getting the Most out of SQL & DB2 UDB for the iSeries.
Dig Deeper on iSeries SQL commands and statements
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.