SKIPUNCI—Ignore uncommitted inserts
Use the Modify Ignore Uncommitted Inserts panel or the SKIPUNCI command to specify whether cursors that are bound with read or cursor stability will ignore uncommitted inserts that are made by other transactions.
Modify Ignore Uncommitted Inserts panel
Command ===> _________________________________________________________________
Command: CURRENT
Description . . . . . . . . : IGNORE UNCOMMITTED INSERTS
Type the new Ignore Uncommitted Inserts value you wish to change to. Then press Enter.
Ignore Uncommitted Inserts Parameter
Ignore Uncommitted Inserts . Y (Y or N)
Command syntax and parameters
Value | Description |
|---|---|
DB2ssid | Db2 subsystem ID or the name of the Db2 data sharing group to which the command applies. |
opertuneID | OPERTUNE system profile name (if OPERTUNE is running as a started task) or the batch job name (if OPERTUNE is running as a batch job). |
Y | Uncommitted inserts are treated as if they have not arrived yet. In a data sharing environment, uncommitted inserts of transactions that were designated as spawning transactions will be treated in this manner. Immediate write occurs for inserts, updates, and deletes, but readers do not wait for the outcome of uncommitted inserts. |
N | Uncommitted inserts are evaluated for return with or without waiting for committedness according to the value that you set in the EVALUATE UNCOMMITTED field. |
NORESET | The changes you request remain in effect until the Db2 subsystem is cycled. |
Db2 parameter values
Field | Installation panel | CLIST parameter | ZPARM macro | ZPARM parameter |
|---|---|---|---|---|
Skip uncomm inserts | DSNTIPB | None | DSN6SPRM | SKIPUNCI |