Lock Manager


Reputable Poster
Hi there!

Did anybody enabled and successfully used [LOCK MANAGER] settings
on the JDE.INI?
As far as I know, its function is to keep transaction integrity, but
does it work?

Thanks to all, Sebastian

Sebastian Sajaroff
[email protected]
B7321 to Xe, NT/W2K/SQL, JAS, Citrix, Interop

B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
[email protected]
Grupo ASSA - Application Software SA


Legendary Poster

As you know, LOCK MANAGER isn't available under B7321 but starting from B733x.

Yes, we (our tech guys) already enabled it on more installations and did not experience any problem. All platform was NT based with SQL or Oracle.
Unfortunately I haven't enough time yet to make experiments with this feature (although I am very interested in it) and check how does it work.
As far as I have seen, OW doesn't used the Transcation Processing possibility under B7321. As higher the release and ESU level as frequentlier used Transaction Processing in APPLs, UBEs and BSFNs.

This were my 2 cents.


B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)


Active Member
There was a very interesting discussion by our more advanced colleagues. You
can look for thread "Transaction processing - COMMIT/ROLLBACK ...". It does
not answer your question though :-(
If I understand it correctly, it's not exactly for transaction integrity;
more like to inform a user that the record he is trying to change was
changed already by another person (like optimistic locking in SQL Server). I
still recommend reading the whole thread - it was fun to read.

My 2 cents,
Vladimir Ponomarev


Legendary Poster
Re: RE: Lock Manager

Sebastian, Vladimir

Vladimir is right in the part about "optimistic locking" but the enabled LOCK MANAGER is required for transaction integrity too.

If you want to use transaction handling in OW then you have to make some settings explicitily in the application(s).
For example you can set "Transaction" property for Forms and UBEs, further you can mark a check-box "Include Transaction" at Form/UBE interconnects or BSFN calls in the Event Rules.
To read more about it, please check the "Transaction Processing" chapter under "Additional Features" section of Development Tools documentation on the documentation CD.


B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
Discover how to build no-code data integrations and business process automations.


Well Known Member
See document oti-99-0024 (Server Performance and UBE's) on the Knowledge
Garden. We made this change and did receive a performance improvement.

Dave Rammer
Sheboygan County IS
B7331 SP11.2 / HP-UX 11.0 / Oracle 8.0.6


Active Member
RE: RE: Lock Manager


Honestly speaking, I do not know for sure, because I never tested it.

It was my understanding that LOCK MANAGER is not required for basic
transaction processing (like include in transaction option you mentioned) -
for me it's basic service of RDBMS, which it provides at no additional cost.
Again in the documentation it does not mention it explicitly, but it only
describes TS (time-stamping) service, which is not required for
commit/rollback process.

In my personal view (I do not dare to recommend ANYBODY to act based on
these assumptions):
In older versions of OW (prior to B733) they had [TP MONITOR something]
section, where you could enable or disable transaction processing. Starting
from B733 it is always on. It is mentioned in Developers Tools guide (XE),
when they explain why this section is no longer needed, and also in CNC
guide (XE), when they describe JDEBase, they simply state that JDEBase
handles transaction processing... That simple. But... in OneWorld "You never
know until you test it".

I would like to read from anyone who had contradicting experience, really.

Vladimir Ponomarev
B733, B7331, B7332, XE (mostly XE at the moment); SQL 7.0, Oracle 8.1.5,
DB/400 (mostly SQL); Wintel, HP, AS/400 (mostly Wintel)


Legendary Poster
Re: RE: RE: Lock Manager

Thanks for your update.
Yes, JDE documentations are really not unambiguous relating to this issue, although it is a very important issue, so any experience, clear documentation, etc. would be very apprecited.

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)