Re: Migrating extant system to new hardware -- 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.

Subject: Re: Migrating extant system to new hardware
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 20 Dec 2017 13:31:30 -0500
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Oh, and the little stuff, like changing your line descriptions from CMN02
to CMN01 or some such thing, is just something you can do after the
restore. No big deal. Either change the configuration object or wizard
yourself around in SST to change the resource name. (I've done it both
ways.) Like I always change TAPMLB01 resource to something to match what
I want.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Migrating extant system to new hardware , Jack Woehr

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.