× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Commitment control
  • From: pytel@xxxxxxxxxx
  • Date: Thu, 2 Mar 2000 15:28:15 -0600

Since there are two separate activation groups involved, there will be two
separate commitment definitions.
If first activation group updates a record, record is locked until COMMIT
or ROLLBACK.
Second activation group should not be able to update the record.

You can have job-level comitment definition, which spans all activation
groups.
In this case you will be able to update record from another activation
group.

    Alexei Pytel


Klein Ron <ron.klein@brctsg.com> on 03/02/2000 08:50:14 AM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L (E-mail)" <MIDRANGE-L@midrange.com>
cc:
Subject:  Commitment control




In a new application we are developing everything uses commitment control
that possibly can.  However, we continue development we have run in to an
interesting question.  We have not tried it yet since the specs for the
modules are still being written.  I was hoping to find an answer before we
actually try to code the modules to find out if we will run amuck with our
plans or if they are doable.

One process running in it's our activation group creates a record in a file
under commitment control.  Now this process calls another in a different
activation group.  The second updates the record created in the first and
also needs commitment control.  Will we have any conflicts because of the
journaling or the use of different activation groups?

TIA
Ron
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.