MULTI-ROW-UPD, MULTI-ROW-DEL when Db2 for z is Data Server
As part of the JDBC interface to the Db2 / z, it is possible for JAVA applications to request multiple operations against the Db2 / z within a call. These include INSERT, UPDATE, and DELETE. If there are problems within these processes, such as For example, if deadlocks occur, the Db2 / z will work as follows in the case of insert. With the parameter 'atomicMultiRowInsert' one can control the behavior and determine whether after the first SQL error the INSERT processing is to be aborted or the other INSERTs should also be tried. With the GET DIAGNOSTICS the SQLCODES can be queried in the NOT ATOMIC case.
In the case of UPDATES or DELETES, the JDBC works differently. Regardless of the atomicMultiRowInsert value, NOT ATOMIC is always used. This currently leads to long DEADLOCK chains.
The solution would therefore depend on the value 'atomicMultiRowInsert' to control the behavior of MULTI-ROW-UPDATES or MULTI-ROW-DELETES. Although this is a bit confusing because of the term 'insert' in the control variable, it is based on the behavior of the Db2 / LUW.