Save while active gotchas: RTVTCPINF times

One needs to understand the complexity of save while active, and the documented way of how you are supposed to do it.
There is "save while active" and there is "ragged save while active".
Ideally one should cease all activities against the data until a checkpoint message is received at the appropriate message queue. Then a program, which waits on that message queue, is supposed to start operations back up and allow people in.
Not to get the absolutists mad at me but it's sort of like a point in time flash copy.
If you fail to do it this way you face real risks of data not being at a "point in time" on your save media. For example if I update OrderLine and that transaction is supposed to also update OrderHeader, ItemMaster, CustomerMaster, etc, there is a risk of them not being at the same point with a save while active.
Before we started doing our saves from our HA machine we were using a ragged save while active. My boss said there will be no ceasing of operations on a nightly basis. We were to take the risks. Keep in mind that at that time we also did no journaling.

Main gotcha on SAVACT(*LIB) vs SAVACT(*SYSDFN): If you have interschema dependencies you are then doing a ragged save while active. For example, if a transaction is supposed to update ERPSchema.OrderLine and at the same time update AccountingSchema.GLTransaction SAVACT(*LIB) will not get a point in time capture between the two. Especially if you do not quiesce operations.

But, in general, if you are going to do a ragged save while active and forego ceasing operations until the checkpoint message is received do you care? It's only data and it's expendable.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Thursday, April 25, 2019 1:16 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: RTVTCPINF times

But of course... :D

SAVACT(*LIB) flew right thru. Without it, I gave up and cancelled the save, due to locks.


Any gotchas with SAVACT(*LIB)?




-----Original Message-----
From: Craig Richards [mailto:craig@xxxxxxxxxxxxxxxx]
Sent: Thursday, April 25, 2019 11:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: RTVTCPINF times

Save While Active?

On Thu, 25 Apr 2019 at 17:45, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I don't know what you mean by "SWA".

8 minutes for your QUSRSYS?!? On a good night, our entire SAVLIB
LIB(*ALLUSR) takes just over 8 minutes.



-----Original Message-----
From: Steinmetz, Paul via MIDRANGE-L
[mailto:midrange-l@xxxxxxxxxxxxxxxxxx]

Sent: Thursday, April 25, 2019 10:21 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx

Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: RTVTCPINF times

Justin,

As a test, do a save of QUSRSYS, but using SWA.
Don't end any processes.
I think you will see a big difference.

SAVLIB LIB(QUSRSYS) SAVACT(**LIB)

My save of QUSRSYS is a bit longer, (8 minutes), cause I also save
spoolfiles, and most of my spoolfiles are in QUSRSYS.

SAVLIB LIB(QUSRSYS) SAVACT(*LIB) SPLFDTA(*ALL)

Message . . . . : 3977 objects saved from QUSRSYS. 0 not saved.

Cause . . . . . : -- 3977 objects were saved. -- 251537 spooled files
were
saved. -- 0 objects were not saved. -- 6 spooled files were not saved.
Data
was saved from library QUSRSYS on volumes 001396 sequence number
273828 at
04/24/19 23:07:54. The save operation ended on volume 001396. If

UPDHST(*YES) was specified, the save/restore history information was
updated


Cause . . . . . : 1093471 blocks were processed for file label QUSRSYS,

sequence 273828 for volume 001396 loaded on device TAPMLB01. The
maximum
block size is 262144. The tape file was opened at 04/24/19 23:09:10
and

closed at 04/24/19 23:17:39. The total time the file was open was
510

seconds. If the device is a tape library the cartridge is 001396 and
the
resource is TAP01.


Paul

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com