Jim,
What WAS installations we have configured apparently we are not using. It is a total mess. I fell into the trap that you could do OS upgrades and clean this up later. I am finding out a lot of stuff really doesn't work this way. For example
Missing JDK6:
If you try to run
STRQSH
./managesdk -setNewProfileDefault -sdkname 1.8_64
to change some defaults from JDK 6 to JDK 8 (64 bit) it will complain that JDK6 is missing.
Moral of that story is to install JDK8 on 7.1 and above and convert your WAS servers JDK to JDK 8 before much else.
Trying to do the WAS upgrade without upgrading JDK first will abort.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Monday, April 29, 2019 7:51 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: WAS minimums for V7R4
I've tried to find the answer but was looking during IBMs web fiasco last
week so I may have missed it.
What is the minimum WAS level for V7R4. Is it still 8.5?
As usual the IBM web site runs in circles and does not have a "minimum
software requirement" page that's findable.
--
Jim Oberholtzer
Agile Technology Architects
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
