Don - question, accepting completely the NOTIFY locks used by ADS across
pseudo-converse. Here's a scenario.
1) The dialog does OBTAIN on record types A, B and C, and a MODIFY of C in
the premap. At the pseudo-converse the update of C must be COMMITTED when
the FINISH of the run unit occurs - but ADS maintains NOTIFY locks on the 3
record types.
2) Now - in the response process the dialog does an OBTAIN and MODIFY of
record type D - when ADS BINDs the Run Unit would it not re-acquire the
NOTIFY locks as database run unit locks PRIOR to doing the OBTAIN and MODIFY
of record type D?
3) So it would be possible for the A, B or C record types to interact with
other active tasks - thus causing confusion for the developer who only sees
record type D referenced in the response process code?
Just curious - as this is the sort of scenario that I believe the CAS user
is seeing.
Cheers - Gary