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



You can keep paying on your maintenance agreement. (Of course, you're sort of paying for nothing--at least until you upgrade. But maybe the finances would be an incentive to let you do the upgrade.) Then you don't have to double up on payments later on. For other non-technical reasons we had to put off an upgrade a few years back. We kept paying the maintenance and it ended up being helpful when we finally reached the point we could upgrade.

Michael Quigley
Computer Services
The Way international
www.TheWay.org


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Steve Pitcher
Sent: Friday, October 2, 2020 8:16 AM
To: Midrange Systems Technical Discussion <midrange-
l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Upgrade Question

We do about 400 upgrades a year. Option 2 is the preferred choice. It's the
absolute safest way to go.

Option 3 is a mixed mode migration. We're OFTEN called in to clean those
up after they go sideways.

Option 1 is great if you want to pay twice your software maintenance next
year and not get any new features and fixes in the new releases.

Steve Pitcher

iTech Solutions Group, LLC

p: (203) 744-7854 Ext. 176 | m: (902) 301-0810

www.itechsol.com | www.iInTheCloud.com



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Steve M via MIDRANGE-L
Sent: Thursday, October 1, 2020 7:25 PM
To: 'Midrange Systems Technical Discussion' <midrange-
l@xxxxxxxxxxxxxxxxxx>
Cc: Steve M <txpenguin1@xxxxxxxxxxx>
Subject: Upgrade Question

We are preparing to setup a new LPAR and I have an on-going battle with
management (surprise, eh?).

Three options:
1. Load the new LPAR with 7.2 (our current O/S) and not worry about it
being no longer supported after 4/30/21.
2. Load the new LPAR with 7.2, then later, do an upgrade to 7.4.
3. Load the new LPAR with 7.4 (and then load the backup created from the
7.2 system).

Obviously the first one is stupid, but at the moment their one of choice.
The third one is the right choice, but they don't want to have to do
regression testing after loading to make sure everything works on the new
LPAR. The middle one gives them a new LPAR that will run immediately,
but later bite-the-bullet on upgrading and ensuring all the applications still
work.

Here are my questions.
1. Those who have made the 7.2 to 7.4 jump, after all of the vendors say we
have compliant software installed, have you had any issues? If so, what kind
of pitfalls would be ahead?
2. What was your system outage time when upgrading from 7.2 to 7.4? I
am trying to use this to leverage the third option that they'll have a future
extended outage if they take option 2.
3. Any other issues anyone encountered during either a clean 7.4 load from
7.2 backup or during a 7.2 to 7.4 upgrade?

I would have thought that all of the enhancements (both security and
coding) and the loss of support would have been convincing enough but,
alas, I have yet to succeed in selling them on option 3.

As always, thanks to all for taking the time to share your experiences.

Steve Meisinger


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit:
https://url.emailprotection.link/?bAncuoXZnqCUcaMP1y9_Vy4mA238WJyRc
0I8PCKF6U9fHOB7USL8o9LIjNnrhOJEAi3TdOb-G5vau-
B83VyfmjkcCaxU0pJleTMyCCTW9Gu_cvvOIO3HD73g0V2T8lSNs
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://url.emailprotection.link/?bg3JjUAS7FimdYyLHsRj55dyDH2GIgsXgg_1
-7Sba-glStbGmeg_qPpBRVN13Yniv2RhSUJ8GiBJ_EYDWbUA6qQ~~.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://url.emailprotection.link/?bw8w48TccQ5CGr-
yc6E2hKHQEBExR0kQBX7bTe_H0E2zpd8tD53U-
Vab_twbySYxaxCFGDnSUOyTTYRM3hwrj-Q~~
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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.