RE: Backup strategy -- MIDRANGE-L

Subject: RE: Backup strategy
From: <lgoodbar@xxxxxxxxxxxxxx>
Date: Thu, 7 Jun 2007 16:11:04 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I agree here. We leave the system console (twinax) on the BRMS console
screen 24/7. No problems in 3 years, using V5R2 and V5R4. I don't
understand how/why one would "deploy" the BRMS console.

Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, June 07, 2007 08:36
To: 'Midrange Systems Technical Discussion'
Subject: RE: Backup strategy

I was taking issue with this statement:

BRMS console was a nasty hack that required manual interaction with
the system - thus, completely unusable for deployment.

Our backups were working fine under V5R3 with BRMS console. And I
ass-u-me
there were thousands of other BRMS users out there besides me, so the
"completely unusable for deployment" part sorta piqued my interest.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.