SKIP UNCOMM INSERTS field (SKIPUNCI subsystem parameter)
The SKIPUNCI subsystem parameter specifies whether statements ignore a row that was inserted by another transaction if the row has not yet been detected as committed. A newly inserted row can be detected as committed only after the lock held on the row has been released.
| Acceptable values: | NO, YES |
|---|---|
| Default: | NO |
| Update: | option 29 on panel DSNTIPB |
| DSNZPxxx: | DSN6SPRM SKIPUNCI |
SKIP UNCOMM INSERTS applies only to statements running with row-level locking and read stability or cursor stability isolation level.
- NO
- Db2 waits for the inserted row to be committed or rolled back. It then processes the row if the insert commits, or it moves on to find another row if the insert is rolled back. If a transaction performs one or more inserts, and then spawns a second transaction, specify NO for SKIP UNCOMM INSERTS if the first transaction needs the second transaction to wait for the outcome of the inserts.
- YES
- Until the lock held on a newly inserted row is released, Db2 behaves as though the newly inserted row has not yet arrived and the row is skipped. Specifying a value of YES offers greater concurrency than the default value of NO.