Doug ... The process used by BRMS would probably be the implementation
of a Save_While_Active process.
Prior to doing the save you would run some CLP that would quiesce the
system for a few minutes thereby releasing any object locks. As soon as
the SWA backup process has reached a checkpoint (i.e. CPI3712 -
Save-while-active checkpoint processing complete.) then your users could
use the application again while the backup continues. It works really
slick!
The resident SWA expert on this list is Mr. Barsa, if you want more
details on how this works.
Kenneth
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hart, Doug
Sent: Monday, May 14, 2007 7:37 AM
To: Midrange Systems Technical Discussion
Subject: BRMS and Object Locks
Does BRMS have built in functionality to manage object locks encountered
during library backups?
We have some very old code that looks at libraries before backups start
and kills jobs holding locks. It then sets a dataarea to flag the lib
is in use so new jobs don't start. This is old green screen logic and
we now run web enabled products that don't look like standard
interactive jobs. I would think BRMS could handle issues with files in
use. Can anyone point me toward the technique?
--
Doug Hart
midrange.com
