LOCK – Batch Loader locking

Whether to enable the extended Batch Loader locking for the DBMODE UPDATE and DBMODE COPY statements.

YES
Extended locking is enabled (default).
NO
Extended locking is not enabled.

The extended locking for DBMODE UPDATE and DBMODE COPY performs a lock before the record is read. This ensures that, if you are in the process of editing an object, the update or copy process does not read the record until you complete your changes.

If you disable the extended locking, the object is immediately read from the database even if you are modifying it, without taking into account the unsaved changes.

Extended locking is not compatible with the INIT DATINT(Y) statement, because this setting creates an additional lock inside the PIF at update time, which will conflict with the extended locking taken at read time. It is recommended that you use INIT DATINT(N) when running Workload Automation Programming Language; if you set INIT DATINT(Y), any changes made while editing are not take into account.