KMoody
Member
I have two programs:
test.p
test2.p
When test.p pauses, both ITEM and SYSMSTR tables are locked.
test.p
Code:
FIND item WHERE item.part-num = "4M5"
AND item.cto-code = ""
EXCLUSIVE-LOCK NO-ERROR.
RUN test2.
PAUSE.
test2.p
Code:
FIND sysmstr WHERE coname = "NEXTWO"
EXCLUSIVE-LOCK NO-ERROR.
When test.p pauses, both ITEM and SYSMSTR tables are locked.
- Why is SYSMSTR still locked after leaving test2.p? Isn't an external procedure a separate transaction? Is the ITEM exclusive lock in test.p changing the locking scope?
- How can I unlock SYSMSTR in test2.p?