Locks/Committed Read Problem

Gurus, I have a problem with ESQL/C applications trying to perform committed reads in a database that has transactions (but not ANSI compliant). I have a feeling that I am overlooking something obvious, but I don't know what it is. . . We have Online Version RSAM Version 5.03.UC1 on an HP-UX A.09.01 system. I have verified that the lock level for all of the tables (minus the system catalog tables) is "ROW". Yet, when our application is in the middle of a transaction and another application, say dbaccess, tries to do a committed read of the rows in the affected tables, we get 224: Could not do a physical-order read to fetch next row. 107: ISAM error: record is locked. If the second application was an ESQL program, we get 224 and 154 errors--essentially a timeout error. Performed tbcheck on the tables and revealed no problems or corruption. Again, I think I am overlooking something obvious. I hope you can enlighten me. . . . TIA, mgo