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
> Jeff answered most of your questions, I'll deal with the QUSRSYS and
> 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
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact