Evan,
There is only one data area for this entire process, all jobs use this data area.
I thought of excluding the data area from the save, but then when I refresh my R&D environment with last night's save, that data area would be missing on R&D.
Would also impact the recovery of Production LPAR, data area would be missing.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Evan Harris
Sent: Tuesday, September 08, 2020 8:18 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: BRMS SWA creates object lock causing application to fail with CPF1063 followed by RNQ0431
________________________________
CAUTION: This email originated from outside of the PENCOR network. Do not click on any links or open attachments unless the sender is known, and the content is verified as safe.
________________________________
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
--
Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
