RE: Record Locking. -- MIDRANGE-L

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

A couple of possibilities..  Both use the error indicator, retrieve the
user(s) with the lock, and offer a retry/cancel option.
1.      If an interactive job, display a message indicating the problem
to the user.
2.      If a batch job, send a message to the *SYSOPR message queue
through the *PSSR.

Regards,
~~~~~~~~~~~~~~~~~~~~~
Jon A. Erickson
Viking Industries, Inc.
http://www.vikingindustries.com
~~~~~~~~~~~~~~~~~~~~~
 <<Jon Erickson.vcf>> 


                -----Original Message-----
                From:   Erick Garske [mailto:egarske@cts.com]
                Sent:   Wednesday, September 02, 1998 6:59 AM
                To:     Midrange List
                Subject:        Record Locking.

                 << File: Card for Erick Garske >> How should you best
deal with updating a record that may be locked by
                another user? Use the error indicator in the update and
place in a do 
                loop? 

                Thank you for your help.

                Erick

Jon Erickson.vcf

This mailing list archive is Copyright 1997-2025 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.