Is there a way to find what file(s) / member(s) might have this problem?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Monday, August 7, 2023 11:15 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SAVOBJ checkpoint failure
Someone might have had commitment control active (STRCMTCTL) in their job, for testing, and then opened some of those source members in SEU ...?
I think that when it says it "failed to reach a checkpoint" that means there is some commitment control going on ...
On Monday, August 7, 2023 at 10:21:46 AM EDT, smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx> wrote:
We have a process that backs up our dev source and pushes it over to our prod machine for offsite backup. This has been running for about 6 months with no problem. We are doing a SAVOBJ to a *SAVF with SAVACT(*LIB) and now it is failing on one library with the message
Save ended. Unable to reach checkpoint.
I just did the command manually and got the same error. I immediately did a WRKOBJLCK on the library and there are no locks on it. This process works on other libraries so it is just one specific library that is "broken".
Since the library only contains source, there shouldn't be anything using it.
I recommended opening a ticket with IBM but the admins want to have a meeting first to discuss this and that is not going to happen until tomorrow which means we lose another night's backup.
Does anyone have any idea what I can look at in advance?
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.