RE: SAVOBJ checkpoint failure

I was under the impression that if a file was open, there would also be some type of lock on the library. Maybe that was a bad assumption.

I just did a WRKOBJLCK on both of the files in the library and there are no locks on the file or the members.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Monday, August 7, 2023 10:37 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SAVOBJ checkpoint failure

Yeah, checking for a lock on the library is normally a waste of time.

On Mon, Aug 7, 2023 at 10:35 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Usually that is an individual file or member that is open and locked. I
would check to see if there are any communications open from RDi,
VSCode or other that appear to be moving data. We just had a similar
circumstance at a customer this weekend although that was with an NFS
transfer that had stalled.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Mon, Aug 7, 2023 at 9:21 AM <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.

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