FairCom RTG V3 Release Notes

Fixed Locking Issue Reading Record Updated under Transaction

A program rewrote a record in a transaction then tried to read it with another logical FD. All reads were performed without locking, and the following configuration was active:

• <detectlock>yes</detectlock> - To test if read records are locked by someone.
• <locktype>0</locktype> - To read the content of locked records.
• <runitlockdetect anyunlock="yes">no</runitlockdetect> - To avoid record locking between programs in the same run unit.

In this scenario, the read performed via a separate FD did not retrieve the record content but it also did not get a record locked error. The logic has been modified to correct this.