Are you starting to see more locks on ITMMVT and STOCK tables? How about performance degradation in stock related functions?

Are you noticing more deadlocks?

You can review

https://sagecity.na.sage.com/support_communities/sage_erp_x3/b/sageerp_x3_product_support_blog/posts/do-users-receive-messages-about-locked-records-or-rollbacks-following-an-error-you-might-have-a-deadlock-problem

You may be seeing ramifications of a code change.

In the past, we have hardcoded a command lockwait = 3 in an effort to improve performance in:

• STKALL (2 places)
• STKMAJ (6 places)
• STKMAJC (5 places)
• STKMAJE (2 places)
• STKMAJS (4 places)

We are now removing these hardcoded values and allowing the general parameter for TIMLCK to manage this functionality. The TIMLCK parameter resides in the PRF Group of the SUP chapter. The default value is 5 and it is recommended to leave this value unchanged unless there is a technical reason.

Both the lockwait command and the TIMLCK parameter do the same thing. It works out to approximately the maximum number of seconds it will attempt to get a lock on the record. In actuality, if a lock is unable to be obtained, for example, during a readlock event, we will wait 1 second and then try again. If unsuccessful, we will wait another second before making the next attempt up the to value set in the lockwait command or the TIMLCK parameter.

This change takes place in Sage Business Cloud Enterprise Management (X3):