Re: Exit point programs -- 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: Exit point programs
From: rob@xxxxxxxxx
Date: Thu, 26 Jul 2007 10:41:41 -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>

So, does anyone have a good checklist of obscure little ditties like this
they have to catch in a HA environment? Like, if I add an exit point
program on the source system, make sure I get it on the target system.
System values and so forth... Or do all HA vendors just catch this?

This discussion opened up my eyes to some stuff that I've missed in our HA
environment.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Exit point programs , Steve Moland

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.