Stored procedures with commit and rollback statements don't seem to work if they are created from Operations Navigator or STRSQL. The only way I can get it to work is to use the "RUNSQLSTM" with the "COMMIT(*CHG)" option. How can I get it work from Operations Navigator or STRSQL?
RUNSQLSTM SRCFILE(TEST/QTXTSRC) SRCMBR(COMMITALL) COMMIT(*CHG) NAMING(*SQL) ERRLVL(10) DFTRDBCOL(TESTCOL) CLOSQLCSR(*ENDMOD) DBGVIEW(*LIST) OUTPUT(*PRINT)
You need to embed a SET OPTION COMMIT=*CHG clause into the stored procedure source.
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
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.