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



We went ahead Friday and deleted Java 6. I had set the JAVA_HOME
to 7.0. We had already
upgraded Domino to 9.01 FP9 so when we use WRKJVMJOB
it shows Domino using JDK 1.8. I compared that to the production
box and QSRVMON doesn't show up as well as ADMIN1 & 5.
Other than those the system appears to be working (or not working
depending on how you look at it).
I'm pretty sure QSRVMON is something important.
Using QSH I show the Java version to be 1.7.0 so I'm not sure
why the service monitor didn't star or for that matter ADMIN1.

Bill Roehmer
Senior Pgmr/Analyst
The C.D. Hartnett Company




"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments
accompanying it) contain confidential information belonging to the sender.
The information is intended only for the use of the intended recipient.
If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the law.
If you have received this transmission in error, please promptly notify
the sender by reply e-mail, and then destroy all copies of the
transmission."






From: "Rob Berendt" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 05/07/2018 07:08 AM
Subject: Re: Java - 6
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Many have pitched in. I'll offer a continuation.
After doing the WRKJVMJOB,
and after figuring how to change as many defaults as possible,
then, if you really want to push the envelop there is an additional step
you can do.
CRTSAVF MYLIB/JDK6
SAVLICPGM LICPGM(5769JV1) DEV(*SAVF) OPTION(...) SAVF(MYLIB/JDK6)
DLTLICPGM LICPGM(5769JV1) OPTION(...)
I forget what option(s) there are for JDK6 back on 7.1. That was a LONG
time ago for me.

I actually did this before upgrading to 7.3.
I found one program which didn't appear to be using JDK6, and even had a
JAVA_HOME environment variable to allow me to use different java stuff.
However at startup they did this insanely stupid prerequisite check to see

if stuff was there. And, one of the things they checked was for JDK 6.
IBM Domino.
7.2 was a show stopper for them because their existence check was for
5769JV1 and IBM renamed Java to 5770JV1 at 7.2. Took a new version of
Domino to get past that.
7.3 was a show stopper for them because their existence check was for JDK
6 and they ignored their JAVA_HOME environment variable on their existence

check. Took a new version of Domino to get past that.
IBM never has Domino ready at day 1 of a new release of IBM i. I am
hoping the change to HCL will have Domino ready for rNext of IBM i.
Sucks that I pressure vendors hard to be ready at day 1 and I can't even
get IBM to be ready.
I literally had to create a separate sandbox of IBM i just for the Domino
delays.
I moved all Domino servers to their own lpars of IBM i. A major reason
why I have 15 lpars of IBM i. Yes, I do still run multiple Domino servers

in a single lpar of IBM i.
This has the additional benefit of being more flexible when I do HA
switches of DB2 and still leave the Domino servers running.



Rob Berendt

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.