RE: Save While Active problem

["Graap, Ken" <keg@xxxxxxxxxxxxx>]

This illustrates why it is important to quiesce the system for a few minutes
during the synchronization phase of a SWA process... If all application
activity is stopped for a short time at the beginning of a SWA save, all
these kinds of issues disappear.

Kenneth

****************************************
Kenneth E. Graap
IBM Certified Specialist
AS/400e Professional System Administrator
NW Natural (Gas Services)
keg@nwnatural.com
Phone: 503-226-4211 x5537
FAX:    603-849-0591
****************************************


-----Original Message-----
From: barsa@barsaconsulting.com [mailto:barsa@barsaconsulting.com]
Sent: Wednesday, January 16, 2002 8:03 AM
To: midrange-l@midrange.com
Subject: Re: Save While Active problem



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

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    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






--
[ Picked text/plain from multipart/alternative ]
Hi Mark,

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>

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.