Recommendations Recommend cursor processing options (SENSITIVE/INSENSITIVE, SCROLL/NO SCROLL, WITH HOLD/WITHOUT HOLD, FOR UPDATE) for the following database applications: Online application for...

1. Recommend cursor processing options
Applications with minuscule outcome tables and regular volatile route through the information, similar to screen-based applications, benefit enormously from the utilization of scrollable cursors.
Method.
To boost the usefulness of your scrollable cursors:
Find out when scrollable cursors are best for you.
· Contrasted with non-scrollable cursors, scrollable cursors request more Db2 handling. Utilize non-scrollable cursors assuming your applications call for huge outcome tables or on the other hand on the off chance that you can emphasize successively over the information.
· Possibly mark scrollable cursors as SENSITIVE on the off chance that you should see the latest information. Utilizing a cursor that you indicate as INSENSITIVE requirements less handling from Db2 on the off chance that you don't have to see changes made by different cursors or application processes.
Pronounce scrollable cursors as SENSITIVE STATIC in the event that you simply have to see a piece of the latest changes and don't have to notice the results of supplement tasks.
Announce scrollable cursors as SENSITIVE DYNAMIC in the event that you really want to see the latest changes in general and embeds.
· While restricting bundles and plans that have updatable scrollable cursors, give ISOLATION(CS) and CURRENTDATA(NO) to guarantee most extreme simultaneousness while involving a scrollable cursor for situated update and erase tasks.
· While utilizing scrollable cursors, utilize the FETCH FIRST n ROWS ONLY condition. Bring FIRST n ROWS ONLY can upgrade the effectiveness of disseminated questions that utilize DRDA access in a circulated climate when just few columns should be recovered.In a nearby setting, you might utilize FETCH FIRST n ROWS Just to decrease the size of the outcome table in the event that you just have to peruse over a little part of a table's columns.
· Do your cursor handling in a put away strategy in a circulated climate on the off chance that you don't have to use your scrollable cursors to alter information.
· Your application's requirement for network traffic can be decreased by utilizing put away cycles.
· Make table spaces in a work document data set large to the point of taking care of your scrollable cursors.
· The accompanying classes of scrollable cursors are handled by Db2 utilizing expressed impermanent tables:
· Wonderful STATISTIC SCROLL
· Shocking SCROLL
· Assuming the cursor awareness is INSENSITIVE, utilize ASENSITIVE SCROLL. The viable responsiveness of a cursor that fulfills the necessities for a read-just cursor is INSENSITIVE.
Make continuous changes for the accompanying reasons:
· Scrollable cursors should as often as possible be left open longer than non-scrollable cursors.
· Scrollable cursors make it conceivable to access and refresh columns...