Good points.  However I have a concern with some of the prerequisite 
checking.  I have a package (Domino) that doesn't check at install time 
but checks at run time.  They kind of half ...ed implemented the JAVA_HOME 
environment variable in their notes.ini.  I say only "half" because they 
still hardcode checking the java version to an ancient version.  So, while 
it is well documented that you can use the JAVA_HOME environment variable 
if you DLTLICPGM the version of Java you no longer want them to use some 
parts of Domino (definitely HTTP) will not start.  And if you use the 
domino command "show jvm" it will abort if you've removed the obsolete 
java but will tell you the contents of the Java home if you leave the 
obsolete java on there. 
Being one of those kind of people who likes to push the envelop I tend to 
try to run a version of Java which is no longer supported on the latest 
OS.  It's always this Java issue.
Had to go to Domino 9 to run on 7.2.  Why?  Because they hard coded 
checking for 5761JV1 and at 7.2 it changed from 5761JV1 to 5770JV1.  That 
one popped right up in the joblog.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.