Re: BRMS PTF Interpretation -- 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: BRMS PTF Interpretation
From: Kevin Monceaux <Kevin@xxxxxxxxxxxxxx>
Date: Thu, 16 May 2019 19:53:25 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Paul,

On Fri, May 17, 2019 at 12:45:33AM +0000, Steinmetz, Paul via MIDRANGE-L wrote:

I've applied the BRMS PTFs to DEV/R&D, production was always done weeks/months later.
Never had an issue.

That's good to hear. Thinking back to when we first migrated to our
8286-41A, we had BRMS running on a mix of OS versions, both 7.1 and 7.2.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: BRMS PTF Interpretation , Rob Berendt

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.