RE: Does BRMS know about saves done outside of BRMS?

Jim, Kirk - thanks for the info. Luckily we do have access to the CL source so maybe we'll see about changing this to use SAVOBJBRM.

Scott

________________________________________
From: midrange-l-bounces@xxxxxxxxxxxx [midrange-l-bounces@xxxxxxxxxxxx] on behalf of Jim Oberholtzer [midrangel@xxxxxxxxxx]
Sent: Monday, October 03, 2011 2:31 PM
To: Midrange Systems Technical Discussion
Subject: Re: Does BRMS know about saves done outside of BRMS?

BRMS does not know about the periodic journal receiver saves and
therefore would be unable to help you with your recovery. The good news
is all you have to do is create a control group that has the save
operations you want in it, and then use the STRBKUBRM command to run
it. Another option would be to change the SAVOBJ command in the control
language programs to SAVOBJBRM. Both will accomplish the same thing.
If you are appending saves onto the same tape today, you can replicated
that in BRMS by setting the appropriate switches in the control group or
on the SAVOBJBRM command.

In both cases the media management needs to be done to the tapes are
ready but that's the easy part.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 10/3/2011 1:50 PM, Lindstrom, Scott R. wrote:

My recently inherited system is now operational and I am refreshing my memory of BRMS from years ago.

While we use BRMS for the daily and weekly saves, we have vendor software that saves Journal Receivers all day long to tape (using SAVOBJ). When I run the STRRCYBRM *REPORT command I don't see any reference to those. Does BRMS know about saves done with the native commands? In the event of recovery I would certainly need to know about those objects.

Scott Lindstrom

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