RE: BRMS Backup Strategy and Implementation -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

<<So operator errors are eliminated.>>

You're making the assumption that the knuckleheads remember to flip the
write-protect switch on the tape cartridges. Ah, the joys of an outsourced
data center.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Voris, John
Sent: Wednesday, February 05, 2014 3:41 PM
To: midrange-l@xxxxxxxxxxxx
Subject: BRMS Backup Strategy and Implementation

. . . perm saves mixed with saves that expire

Also, when speaking of the virutes of BRMS, I don't think that anyone has
mentioned one other saving grace of BRMS.

When you install the BRMS software onto the box, anytime you "save-to-tape"
- - even when using a non-BRMS command like SAVOBJ and SAVLIB,
the BRMS database of tapeID's is checked, and if the tape is not yet expired
or has a *PERM retention date, the IBM commands will not allow you to
continue.
So operator errors are eliminated.

And how? The IBM commands that have anything to do with Save-to-Tape are
modified during the installation of BRMS. That is how they accomplish that
piece of magic.

- John Voris

This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.