Re: Save While Active problem

[NigsRpgId@xxxxxxx]

--
[ Picked text/plain from multipart/alternative ]

Hi Al,

What I was trying to say was that if three files are journalled to the same
journal, then if one save operation, with save-while-active, tries to save
just two of the files, the save will not complete if there are pending record
changes for the third file. Even though the third file is not being saved!

I just did the following experiment:

1. Create three files - FILEA, FILEB and FILEC
2. Journal all to JRNL001
3. savobj obj(FILEA FILEB) savact(*SYNCLIB)

If an RPG program is updating only FILEC, as long as there are pending
changes for FILEC, the savobj command will fail. The message issued will be
CPF377F "Save-while-active request prevented by pending record changes. "

If a large number of files are journalled to the same journal, and you are
trying to save a subset of them, SWA will wait for no-pending changes on ALL
files within the journal.

This caught us out last year !

I hope this expalins what I was trying to say more clearly :)

Rgds
Nigel



In a message dated 1/16/02 5:17:17 PM GMT Standard Time,
barsa@barsaconsulting.com writes:

With all due respect, the pending commit does have to do with the file that
is being journaled.  This is a SWA limitation, and it involves a specific
application design, and providing sufficient time in the SAVACTWAIT
parameter to let the commit cycle to complete.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC


                    NigsRpgId@aol.com
                    Sent by:            To:     midrange-l@midrange.com
                    midrange-l-admin@mi       cc:
                    drange.com                Subject:     Re: Save While
Active problem


                    01/16/02 10:53 AM
                    Please respond to
                  midrange-l



I don't know if this helps but we discovered that the file with pending
changes need not be one of the files being saved.

It seems that the OS/400 save object commands, when using
save-while-active,
can be held up by any file that is locked by a commitment control cycle,
when
that file is using the same journal as the objects being saved.  The
pending
commitment control cycle does not have to directly involve one of the
objects
being saved.

Rgds
Nigel

<snip....>
> Hello all,
>
> We are having a problem with our nightly backup. We are receiving a
CPF377F
> (Save-while-active request prevented by pending record changes) on our
> SAVLIB command. I'm assuming that there is commitment control over a file
> with pending changes but I cannot determine which file is causing the
> problem, if indeed that is the problem. Our backup log shows QUSRNOTES
> library as the last library saved. So I'm assuming, again, that the
> offending object is in QUSRSYS. Is there a way to shed more light on
this?
> The joblog doesn't tell me squat nor does a CL Dump.
>
>
> Thanks,
>
> Mark
>
<endsnip>