Re: Save while active questions

Well if it's working it's working...

But seems sub optimal...you might consider a SAVACT(*LIB)...

That would mean every object in a single library uses the same checkpoint.
But objects in different libraries might have a different checkpoint.

SAVACT(*SYNCLIB) is useful in a production environment that spans libraries
so that you can ensure all the objects across libraries are at the same
checkpoint. I doubt that level is needed on a development box.

Charles


On Tue, Mar 1, 2016 at 12:48 PM, John R. Smith, Jr. <
smith5646midrange@xxxxxxxxx> wrote:

This is exactly what I needed to know. I guess I never read the secondary
text. Thank you.

As for all of the libraries, it is a dev machine and they turned on save
while active to reduce the amount of time that the developers would be
locked out. On the weekend, the full backup runs for about 11 hours and
who
knows when it will hit which libraries. This way we are only locked out
for
30 minutes at 04:30 when nobody is on anyhow instead of being locked out
all
morning.

Thanks again for the info.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Monday, February 29, 2016 5:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Save while active questions

Do you see
CPI3724 - 0 of 3 libraries processed.
CPI3724 - 1 of 3 libraries processed.
CPI3724 - 2 of 3 libraries processed.
CPI3725 - Save-while-active checkpoint processing in progress.
CPI3712 - Save-while-active checkpoint processing complete.


The text for CPI3724 is
Cause . . . . . : The save-while-active operation has now locked the
objects
in 1 libraries. Checkpoint processing will begin when objects in all 3

libraries have been locked.


vs CPI3725
Cause . . . . . : The save-while-active operation has now locked the
objects
to be saved in all the libraries.


So for the first 30min, the system is allocating all objects in a given
library one library at a time. Are you getting any objects not saved?

500 libraries is an awful lot for a *SYNCLIB save-while-active.

Are all 500 really active?

You might be better served by creating a SWA control group for the say 5
libraries that are active and the save the others without using SWA.

Charles



On Mon, Feb 29, 2016 at 5:10 PM, John R. Smith, Jr. <
smith5646midrange@xxxxxxxxx> wrote:

We are using BRMS and the control group does not allow me to see
keywords so I'm guessing at what you are asking. If I guessed wrong,
let me know.



PRECHK()

Object pre-check . . . . . . . . . . . . *NO



SAVACT()

Weekly Retain Save

Backup List ASP Activity Object While

Items Type Device SMTWTFS Detail Active

*ALLUSR *SYSBAS *DFTACT *YES *SYNCLIB



SAVACTWAIT()

Save active wait time:

Object locks . . . . . . . . . . . . 120

Pending record changes . . . . . . . 120

Other pending changes . . . . . . . . 120



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Monday, February 29, 2016 5:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: Save while active questions



What values do you have for

PRECHK()

SAVACT()

SAVACTWAIT()



Charles



On Mon, Feb 29, 2016 at 4:32 PM, John R. Smith, Jr. <
<mailto:smith5646midrange@xxxxxxxxx> smith5646midrange@xxxxxxxxx> wrote:

We have a backup that is using save while active. The backup starts

at

04:30 and there are about 500 libraries in the backup. About 05:00,

there is an entry in the joblog "Save-while-active checkpoint

processing in progress". About 5 minutes later there is an entry

Save-while-active checkpoint processing complete.

My question is during the 04:30 - 5:00 window, are the libraries

locked or can the system still function normally? Or, is the only

really unavailable window the 5 minutes at 5:00?

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list To post a message email: <mailto:MIDRANGE-L@xxxxxxxxxxxx>

MIDRANGE-L@xxxxxxxxxxxx To subscribe,

unsubscribe, or change list options,

visit: <http://lists.midrange.com/mailman/listinfo/midrange-l>

http://lists.midrange.com/mailman/listinfo/midrange-l

or email: <mailto:MIDRANGE-L-request@xxxxxxxxxxxx>

MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take

a moment to review the archives at

<http://archive.midrange.com/midrange-l>

http://archive.midrange.com/midrange-l.

Please contact <mailto:support@xxxxxxxxxxxx> support@xxxxxxxxxxxx
for

any
subscription related

questions.

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: <mailto:MIDRANGE-L@xxxxxxxxxxxx>
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,

visit: <http://lists.midrange.com/mailman/listinfo/midrange-l>
http://lists.midrange.com/mailman/listinfo/midrange-l

or email: <mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment
to review the archives at <http://archive.midrange.com/midrange-l>
http://archive.midrange.com/midrange-l.



Please contact <mailto:support@xxxxxxxxxxxx> support@xxxxxxxxxxxx for
any subscription related questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.