RE: Save while active gotchas: RTVTCPINF times

Thanks so much!


-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Thursday, April 25, 2019 2:03 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Save while active gotchas: RTVTCPINF times

SAVLIB(*LIB) means each library is only concurrent to itself, true. There is a STRSAVSYNC which is supposed to help with that.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaiu/rzaiusavewhileactivesynch.htm

But "ragged" is a whole different thing. With "ragged" not even the objects within a single library is concurrent.
You cannot get a guaranteed concurrent save with SWA without disruption.
Ok, here is a clarification. SAVACT(*SYSDFN) is the "ragged" SWA. This is what we used to use. No checkpoint processing is used. No disruption to business activities.
SAVACT(*LIB) means that only at the library level are the objects in sync. This can be alleviated with STRSAVSYNC. You will have disruption.
SAVACT(*ALL) means that all the objects in all the libraries will reach checkpoint together. While waiting for checkpoint you will have disruption.

Why would you use SAVACT(*LIB) with STRSAVSYNC instead of SAVACT(*ALL)? If you wanted to run multiple saves at the same time. Perhaps to different media libraries or drives within a single media library.

Performance considerations for save-while-active https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaiu/rzaiurzaiu334.htm