× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2015

Coding for commitment control.

Note to developers: When coding for commitment control I can understand
not wanting to commit too often because of performance considerations.
However, you may wish to commit before 'risky' operations or before you
ever present a user with F3 or some other such exit.
I have one IBM package that leaves way too many hanging commits. SOP is
to sign off and sign back on again and cross your fingers that doesn't
cause a roll back of your most recent updates.

What's a "risky" operation? How about committing before trying to connect
to a remote system in SQL?


Rob Berendt

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.