×
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.
Are you talking about this announcement
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Java%20products%20and%20options%20on%20IBM%20i
or some other announcement that actually mentions 7.3? If so, show me
where.
One could easily test on a 7.2 lpar. Simply perform the following steps:
CRTSAVF FILE(MYLIB/F5770JV111)
CRTSAVF FILE(MYLIB/F5770JV112)
SAVLICPGM LICPGM(5770JV1)
DEV(*SAVF)
OPTION(11)
SAVF(MYLIB/F5770JV111)
SAVLICPGM LICPGM(5770JV1)
DEV(*SAVF)
OPTION(12)
SAVF(MYLIB/F5770JV112)
DLTLICPGM LICPGM(5770JV1) OPTION(11)
DLTLICPGM LICPGM(5770JV1) OPTION(12)
Perform testing.
If all goes to hell then RSTLICPGM from the save files.
QED.
For 7.1 replace 5770JV1 with 5761JV1.
For 6.1 you're screwed. You can't put a newer version of Java than 6 on.
This may be a REAL issue for those migrating from 6.1 to iNext.
Read your vendor requirements first. Many hardcode to a particular
release.
When we upgraded from 7.1 to 7.2 older releases of Domino would not work
because they actually checked for 5761JV1 and it had changed to 5770JV1.
HTTP job log showed that quite clearly. It's not like they were checking
for a particular Java version. It was just their idea of a "prerequisite
check".
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.