Whats the API flag makeup of these type of transactions:
SHAPSHOT
CONCURRENCY
CONSISTENCY
READ COMMITTED


How would I setup my transaction (API transaction flags) to allow the
clients to be able to select data (Read Commited w/Rec. Version I guess) but
when client "A" updates and commits a record all other clients would
recieve some type of error if they now try to update that same record?

ex.
1. Client "A" Selects from table TA
2. Client "B" Selects from table TA
3. Client "A" Updates table TA
4. Client "C" Selects from table TA (I want this client to get the same
result set as client "A" originally did)
5. Client "A" Commits (Commits fine.)
5. Client "B" tries to Update and Commit table TA <--I want this one to
error with some type of message stating that the record has already been
modified.
6. Client "C" tries to Update and Commit table TA <--I want this one to
error with some type of message stating that the record has already been
modified.

Is this possible, if so, what transaction settings do I need (API
transaction flags)?

Thanks