Cango
Member
Did anybody investigate the Commitment Control setting for OneWorld running on AS400.
The reason for this question is that uncommitted changes can be seen already before commit. So other UBEs could select but not update/delete them. in some cases (e.g. interfaces via Interface Database Table) this could be critical. For me it looks like the session accessing a table has to have to the correct isolation level to not see changes/inserts before commited. And this setting in OneWorld is defaulted to *NONE I think. Also changes to ODBC settings have no effect.
And probably there is also no chance to change such a setting when the UBE runs on the AS400 without any ODBC connection.
Hope my question is not too confusing.
Any comments are appreciated.
The reason for this question is that uncommitted changes can be seen already before commit. So other UBEs could select but not update/delete them. in some cases (e.g. interfaces via Interface Database Table) this could be critical. For me it looks like the session accessing a table has to have to the correct isolation level to not see changes/inserts before commited. And this setting in OneWorld is defaulted to *NONE I think. Also changes to ODBC settings have no effect.
And probably there is also no chance to change such a setting when the UBE runs on the AS400 without any ODBC connection.
Hope my question is not too confusing.
Any comments are appreciated.
