Is there a setting in WebLogic 7.0 that will cause database updates to be written to the buffer pool before the transaction is committed so that other threads/transactions can do a dirty/uncommitted read of the uncommitted data? The system basics are Java/WebLogic front end, connecting to a legacy mainframe that houses a DB2 database. The problem is that the front end updates a table before starting a CICS transaction on the mainframe. Once inside the transaction in CICS a COBOL program tries to do an uncommitted read of that table and gets a row not found. At the end of the web transaction a tx.commit is executed and then the data can be read by any application. If anyone has any ideas that would be great.
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.