×
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.
Hi Paul
I suppose there is a data area for each for job that is currently running.
One thing might be to try and get all the data areas out into a separate
library of their own and save it separately, but I guess you are trying to
lock all the libraries at the same time in order to get a consistent save
point.
If you need the data areas to be part of the save and consistent with it
then you either need to quiesce the application or stall it for long enough
for the checkpoint to be reached or else live with the occasional failure.
Given that the data areas are holding a before image of a journal, I'd
almost be tempted to exclude them from the save depending on what my
application guys had to say about it. Seems to me if the application was
restarted due to a failure, any transaction in progress would have been
rolled back, so the data areas should be blank at that point.
I did start thinking of imaginative things like holding all the jobs that
would be using those data areas at the start of the save and then releasing
them immediately the checkpoint is reached, but I am really stretching
there.
On Wed, Sep 9, 2020 at 11:48 AM Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
They don't.
It's a combination of 3rd party vendor app and our add-ons.
Paul
midrange.com
