|
|
|
Data loss was reported when using <batchaddition> on files OPEN WITH ROLLBACK. In particular, when explicit transactions were not used, the last records may have been lost (the number of records lost depended on the batchaddition “records” value).
Internal testing showed other vulnerabilities on files OPEN WITH ROLLBACK when using explicit transactions: the record rolled back may not be removed and the record committed may be removed.
This behavior on files OPEN WITH ROLLBACK has now been fixed by adjusting the logic to properly operate when no transaction has been started at the application level and not permitting addition when transactions are started by the application.
Note: Adding records using <batchaddition> on a file OPEN WITH ROLLBACK within transactions started by the application is not supported.
If a file is OPEN WITH ROLLBACK and it is configured for <batchaddition>, any WRITE operation that adds a record within an active transaction will fail. To add records to a file with OPEN WITH ROLLBACK and <batchaddition> enabled, perform WRITE operations without starting a transaction.
Because it is not possible to control the transaction start in ExtFH, adding records using <batchaddition> on a file OPEN WITH ROLLBACK is not supported in ExtFH.
