Re: BRMS - full save with least amount of restricted time

Hi JIm

I recall being unable to save QUSRSYS using SWA on V5R4 while TCP was
active. More accurately I seem to remember that some items just would
not restore correctly even though the save seemed to complete OK.
These items seemed to be associated with TCP jobs. The SWA was a case
of quiescing user applications until the checkpoint (*SYNCLIB) was
reached, except for downing TCP. To get around it I modified the save
regime to save QUSRSYS weekly or monthly when TCP was down.


On Tue, Jan 22, 2013 at 10:09 AM, Jim Oberholtzer
<midrangel@xxxxxxxxxxxxxxxxx> wrote:

Jeff answered most of your questions, I'll deal with the QUSRSYS and
recoverability.

Yes the system is completely recoverable with the SWA on QUSRSYS, in
fact I have performed many recovery tests using BRMS, and in many ways
it works better than the manual recovery. Were you using BRMS for the
SWA processing? If not I suspect that the checkpoint processing my not
have been done quite right leaving some objects out of synchronization.

It is also true that a slowdown in normal activity will make the SWA
work much better as well. The best situation is to be able to quiesce
the the system for a short time (about 5 minutes in my experience) while
the checkpoints are taken, particularly with *SYNCLIB or *SYSDFN check
points.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 1/21/2013 12:38 PM, Evan Harris wrote:

<snip>
Hi Jeff

thanks for sharing, I'm following this with some interest.

2 questions:

- You say all the rest are save while active - what kind of save while
active are you doing ? What is the sync type ? Are you using a message
queue monitor to restart normal processing ?

- By my reckoning QUSRSYS will get saved via SWA. Is this going to be
OK in a recovery scenario ? My experience is not good using SWA on
QUSRSYS.


On Tue, Jan 22, 2013 at 5:24 AM, Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx> wrote:

All,

I tested this BRMS control group on Saturday:

10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 *SAVSYS *DFTACT
40 UPSLIB *SYSBAS *DFTACT *YES *NO
50 QMPGDATA *SYSBAS *DFTACT *YES *NO
60 *EXIT *DFTACT
70 *IBM *DFTACT *YES *LIB
80 *ALLUSR *SYSBAS *DFTACT *YES *LIB
90 *ALLDLO *DFTACT *YES *YES
100 *LINK *ALLAVL *DFTACT *YES *YES
110 ALLSPLF *SPL *DFTACT
120 *EXIT *DFTACT
130 *EXIT *DFTACT

</snip>
--
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.