Apparently this is like accessing the database via Uncommitted Read isolation level, where no locks are taken. There is no way that I know of to do this at the database or table level in DB2. One can set the default isolation level to UR for the client, or for statically bound packages, or in an individual SQL by specifying "WITH UR" at the end of the statement (this last method is usually the most popular).
There are also some environment variables to improve concurrency that can be turned on with the db2set command at the instance level (not at database level):
db2set DB2_SKIPINSERTED=ON
db2set DB2_SKIPDELETED=ON
db2set DB2_EVALUNCOMMITTED=ON
In version 9.7 there is a new parameter that is the default for newly created databases call cur_commit which will allow DB2 to select the previous state of a any locked data from the transaction log instead of waiting for a lock to be released.