Re: CPF377F Save ended. Unable to reach checkpoint.

A workaround might be not keeping your journal receivers in your data
library.
A common practice is to keep your journal receivers in a library beginning
with a special character to ensure it's one of the first libraries restored
on a system during a full system restore.
One company uses $$ to prefix the journal receiver library. Another uses #
to prefix the receiver library.
There is also a practice I suspect predates RAID or faster disk drives. It
has you store your journal receivers into a different ASP. This way, if
the data ASP gets whacked, you can restore your data and apply journal
changes from the journal ASP. Also, transactional load from receiver
updates are not affecting data updates. You have to balance that with
you'd now have less disk arms processing data because you've now broken
them into separate pools. The performance, in our case, was better handled
by just installing the "HA Journal Performance" option. I think it's a no
charge item now.
Aren't most commitment control blocks on the receivers themselves and not
the tables? If so (and I believe they are) then busting them out like this
will allow you to save the data library message free. And your receiver
library might just skip the current receiver. Which, doing a CHGJRN
JRN(...) JRNRCV(*GEN), right before your save may be a very good idea.

On Tue, Mar 24, 2026 at 2:53 PM x y <xy6581@xxxxxxxxx> wrote:

When doing a save-while-active, journaled objects have to be at a
consistent state, meaning there are no pending (database) changes. I've
received this message in the past and my investigation has undercovered
programs that ended without executing a ROLLBACK or COMMIT, or otherwise
cleaning up database operations with non-journaled files, or an open source
member somewhere.

On Tue, Mar 24, 2026 at 5:42 AM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

https://www.ibm.com/support/pages/commitment-control-during-save-while-active-operation

https://www.ibm.com/support/pages/msgcpf7024-rc2msgcpf7018-rc2-determining-open-commit-definition

On Tue, Mar 24, 2026 at 8:17 AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Hello guys

In the last couple of months there were 3 failures of a nightly SAVLIB
LIB(*ALLUSR).
The CMD was
SAVLIB LIB(*ALLUSR) DEV(TAP01) ENDOPT(*LEAVE) SAVACT(*LIB) PVTAUT(*YES)
OMITLIB(WWLLIBD QSRVAGT DWHD URPS)

The error was: CPF377F Save ended. Unable to reach checkpoint.

Looking for CPI8365/CPI836B in DSPLOG, I found:
CPI8365 99 INFO Save-while-active request requires commit or rollback

for

job 429718/QUSER/QZDASOINIT

Now,
is there a way to prevent such failures when executing a SAVLIB with
SAVACT(*LIB)?
What I aim to is receiving something akin to the MSGs received for

locked

objects
CPF3761 Cannot use XXX in Library YYY

and then CPF3771 999 objects saved from LIBXXX. 3 not saved.

at the end of the save operation.


Can it be done?


TIA


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.

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