SAVACT *SYSDFN tells the system to save each object when it can get a clean lock on it for backup.
SAVACT *LIB tells the system you want -all- objects in sync with each other ("all objects... reach a checkpoint together"), so it grabs them all at once.
SAVACT *SYNCLIB is the same as *LIB, but -all- libraries in the save reach a checkpoint at once. Fun getting all those locks!
Only *LIB and *SYNCLIB will 'guarantee' that your objects are in sync with each other. *SYSDFN saves everything, but you're on your own when it comes to things that don't quite line up...
Which one you need to use depends on how critical aligning the data is.
If there aren't a lot of transactions, *SYSDFN is reasonably safe...
In a perfect world you'd kick the users off of the machine every night and run an Option/21 backup. -Guaranteed- sync point!
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, March 02, 2012 5:23 PM
To: Midrange Systems Technical Discussion
Subject: Save While Active
I'm a neophyte when it comes to save while active. I want to save a
smallish production library (under 100GB) during production to replicate
it for testing on another machine. I want to do this daily during
offpeak (but still production) hours. I noticed a couple of options on
the SAVACT: *LIB vs *SYSDFN. Since I'm only saving one lib, *SYNCLIB