×
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.
We have an application database library. In addition to our application,
it may also, depending on the customer, have customer-specific
inbound-data propagation programs (triggers, periodic update programs,
maybe even exit programs, or any combination thereof) accessing it.
The library itself is on the library list of our application's master
server job (which does nothing but spawn off child-server jobs whenever
a client connects).
Now, we want to do an update to that library, adding fields to one or
more of the files, with a CL program. We're holding the master server
job, and checking for any child-server jobs before we start, in order to
keep our application out.
But any ideas on what we could put an *EXCL lock on, that would lock out
any of the inbound data-propagation without forcing us to kill the
master server job outright?
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
