Does anyone know where this went for v8?

No !

Can you explain what it does? (did!)

HTH

This registry parameter set next key locking guarantee the repeatable read isolation level by locking the next key for all insert and delete statements and the next highest keyvalue above the result set for Select statement.

I think after type 2 indexes introduced in ver 8, this may become obselete.

Regards,

mujeeb

Hi,

FYI..

This parameter is still available in DB2 V8, and as mentioned it could not be all that applicable since DB2 V8 provides type 2 indexes but given the isolation level of RR by default we have set the same to avoid frequent locking.

dbforums sure has been flakey lately!

Anyway, type 2 indexes have gone a long way to resolving locking issues, but it's still nice to be able to force RS as the maximum isolation level. RR is rarely required.

db2set -lr
-> doesn't show DB2_RR_TO_RS as a possibility though... but when I set it there are no complaints! So I guess it does still exist.