Re: CPF377F Save ended. Unable to reach checkpoint

IBM “tolerates” this situation because they have a mandate that says if you put it on tape we will maintain the referential integrity of the data. If there is an open commit, they cannot do that.



Jim Oberholtzer
Agile Technology Architects
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Rob Berendt <robertowenberendt@xxxxxxxxx>
Date: Wednesday, March 25, 2026 at 8:56 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CPF377F Save ended. Unable to reach checkpoint

And some might argue why are people not committing their transactions in a
timely basis? This may be what you really need to do. This may be
difficult in some situations. Thinking on your specific example and the
client based program involved, you might need to train that developer to
commit on a frequent basis, or to do their updates WITH NC. Or to change
their odbc connection to one which can be defaulted to WITH NC

On Wed, Mar 25, 2026 at 9:36 AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Thanks Jim, Rob

I just wonder why IBM tolerates a situation
when an object cannot be saved because it's locked for other reasons.
- by issuing a CPF3761 Cannot use XXX in Library YYY

and do not tolerate a locked object by "commit pending"


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