RE: Post-mortem on v7r1 to v7r3 upgrade -- 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.

I'd say it's a lot like manning the tech support help line. No one's going to call to say all is well. I'm sure lots of people upgrade without serious issues. Our BP has done plenty of these without major problems.

My BP and I both dotted the I's and crossed the t's, but unfortunately sometimes things just go wrong.

PSA:
One of our emergency IPL's was to run a RCLSTG for the DB (I don't remember the exact parm). There's a known issue that IBM never patched for 7.1. When we did the upgrade, it struck us before it could be patched by the 7.3 PTF's.

-----Original Message-----
From: Krill, Coy [mailto:CKrill@xxxxxxxxxxx]
Sent: Thursday, November 02, 2017 6:57 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Post-mortem on v7r1 to v7r3 upgrade

You guys are making me paranoid. I'm upgrading our DR box this weekend and plan to do our production box next weekend after switching our environment over to our DR box. We're going from V7R2 to V7R3, has anyone had better experience with that upgrade?

Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank

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.