Can you elaborate on this at all? Is there any further information on this release?This release includes a JVM startup diagnostic loadlib.
JZOS 1.1.2
JZOS 1.1.2
I see there is a new release of JZOS out (1.1.2), but I haven't been able to find any info beyond this little snippet on the front page:
There were no major functional changes in this release, which is why we didn't place an announcement in the forum. The release primarily contains tools that will help us diagnose a problem that some of our users are having with slow startup times.
If you are not seeing this problem, you can continue to run version 1.1.1.
If you are not seeing this problem, you can continue to run version 1.1.1.
There is some new JCL in the JZOS Sample JCL (RUNINV13 and RUNINV14). These jobs don't run the JZOS launcher, but instead run a slightly modified version of IBM's sample JNI launcher "invocationApi.C", which has been built as an MVS Load module.
We have put this together so that we can have a complete example of the JVM performance problem using a small example MVS load module launcher (using IBM's own sample code). This way we can eliminate the JZOS launcher from the equation and focus on the real problem, which is that some installations (two now that we know of) see JVM performance problems when running under a batch load module.
If you are still having performance problems, please run this job and send (all) of the output to me at dev@jzos.com. I'll check that you have the problem and I can send you the modified IBM source and build JCL so that you can open a problem with IBM against the JDK or LE (we are not really sure what the problem is). We will eventually be putting this source code into the JZOS build so that it is readily available.
I almost forgot.. after you run the job once and verify that the JVM is still slow, you will want to run it again with the following at the end of //STDENV.... this was give to us by IBM support as helpful in capturing diagnostic info, so you will want to send it to them when you open a problem.
IBM_JAVA_OPTIONS=-verbose:class,jni,Xclassdep
This option will itself slow things down, so you want to run once without this to verify that you still have a performance problem when running IBM's launcher code.
We have put this together so that we can have a complete example of the JVM performance problem using a small example MVS load module launcher (using IBM's own sample code). This way we can eliminate the JZOS launcher from the equation and focus on the real problem, which is that some installations (two now that we know of) see JVM performance problems when running under a batch load module.
If you are still having performance problems, please run this job and send (all) of the output to me at dev@jzos.com. I'll check that you have the problem and I can send you the modified IBM source and build JCL so that you can open a problem with IBM against the JDK or LE (we are not really sure what the problem is). We will eventually be putting this source code into the JZOS build so that it is readily available.
I almost forgot.. after you run the job once and verify that the JVM is still slow, you will want to run it again with the following at the end of //STDENV.... this was give to us by IBM support as helpful in capturing diagnostic info, so you will want to send it to them when you open a problem.
IBM_JAVA_OPTIONS=-verbose:class,jni,Xclassdep
This option will itself slow things down, so you want to run once without this to verify that you still have a performance problem when running IBM's launcher code.