In order to convert existing CALL DML statements to work with the SQL interface, it is advisable to perform the steps in a given order. Below you can find a brief summary of the most important steps listed in accordance with the type of application or statement.
TIAM application
If you want to convert a CALL DML transaction into a TIAM statement for use with the SQL interface, proceed as follows:
One at a time, replace all CALL DML statements other than BTA, ETA and RTA with SQL statements
Then replace the BTA, ETA and RTA statements:
delete BTA without replacement
replace ETA with COMMIT WORK
replace RTA with ROLLBACK WORK
openUTM application
If you want to convert a CALL DML transaction into an openUTM application for use with the SQL interface, proceed as follows:
One at a time, replace all CALL DML statements other than BTA, ETA and RTA with SQL statements
Then replace the BTA, ETA and RTA statements:
delete BTA without replacement
delete ETA without replacement
replace RTA with RSET (RSET is a function at the openUTM KDCS interface)
CALL DML statements outside a CALL DML transaction
In order to convert CALL DML statements which are issued outside of CALL DML transactions for use at the SQL interface, you must replace them by the corresponding SQL statements. In this case, there are no restrictions concerning permitted SQL statements. Note that most SQL statements implicitly open a transaction. This must be closed before the next CALL DML statement.