× 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.



Kevin,

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

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Kevin Monceaux
Sent: Thursday, May 16, 2019 8:14 PM
To: Midrange L
Subject: BRMS PTF Interpretation

Midrange Fans,

I think I'm in the home stretch preparing to start getting our LPARs up to
date on PTFs. I red through more cover letters than one can shake a stick
at today.

The cover letter for SI68855 includes this:

DESCRIPTION OF PROBLEM FIXED FOR APAR SE70391 :
-----------------------------------------------
It is important to keep all systems in a BRMS network at the
same level of BRMS PTFs.
Fixes included in this PTF may reference enhancements. More
information on these enhancements can be found on the BRMS web
page: ....

It goes on to list various fixes in the PTF.

It looks like it's describing the importance of keeping all systems in a
BRMS network at the same level of BRMS PTFs as a problem. And that could be
a problem for some. Is that the description of a problem, or a warning?
I'd love to keep all of the BRMS PTFs on my LPARs at the same level, but I
also need to be able to apply PTFs on my development LPAR and run with them
there for a while to make sure no issues are encountered before applying
them to my other LPARs.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.