Problems converting from S.E. to On-Line

Hello, We have recently moved our 4GL application from an AT&T 6386 running S.E. to an IBM RS/6000 370 using On-Line. We are having problems with key locks and long transactions which remain therefore locking users out from updating those records. The code seemed to work properly when running S.E. but is having a lot of problems with On-Line. We have tried to set ISOLATION TO DIRTY READ but this has not solved all of the problems. My questions are: How do we handle the key locks and long transactions so they do not lock users out of those records? Is there a way to set the high water mark for a single log that may solve the above problem? What other ideas, problems, suggestions should we be aware of when converting from S.E. to On-Line? Any advice would be greatly appreciated. Thanks in advance. ============================================================================ Marty Bland Information Systems Reynolds Automation Center, R-1-8 (804) 281-4485 6605 West Broad Street Internet: gmbland@IndSysC.rmc.com Richmond, Va. 23261-7003 ============================================================================