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>
