Cursors for updating

It points to the next row to be passed to the application program. At DB2 precompile time, the definition of the CURSOR is stored in the bindfile, and the statement is commented.The primary steps for using any cursor are as follows: Step1. FETCH is the only way to get the result into application program Host variable.If there are a lot of rows, you can use the "with hold option" and do intermediate commits without automatically closing the cursor. Is a Commit done automatically when I close the Cursor or do I have to explicitly issue a commit? The stored value is essentially an incrementing counter that I don't want read or altered by concurrent requests. "Mark A" Hi All, I've been tasked with writing a z/OS C program to read and update a table (DB/2 v8).If there are a lot of rows, you can use the "with hold option" and do intermediate commits without automatically closing the cursor. Is a Commit done automatically when I close the Cursor or do I have to explicitly issue a commit? The stored value is essentially an incrementing counter that I don't want read or altered by concurrent requests.Everything works as expected, but I'm not sure if concurrency has been addressesed.

Also we need to use WHERE CURRENT OF to update or delete the last row fetched.

If you are at the conference, drop into the Groundbreaker area and say Hello.

Check out all our database development sessions at OOW19 Thanks for the question, Gunjeet.

There can be instances where we need to modify the data in db2 table based on some values in a programmatic way.

Had it been a spufi or QMF we have our update and delete statements ready to run and modify. Nevertheless we can do the same modifications using cursors again.!!