This post is part of a series exploring the unique aspects and capabilities of WebSphere Liberty when running on z/OS.
We'll also explore considerations when moving from WebSphere traditional on z/OS to Liberty on z/OS.

The next post in the series is here.

To start at the beginning, follow this link to the first post.

---------------

Next up in the header is the Java stuff.  When you open a problem to support they are going to want to know at least three things:  what Liberty level are you on (see the ‘product’ message from the previous blog post), what Java version and level you have, and what the problem is.  This next chunk of messages helps you answer that second question (or just send in the log file and support will easily find it right there at the top).

The very first Java message tells you what java.home is set to (or I suppose more properly, to what path java.home is set – as Winston Churchill supposedly said about ending sentences with prepositions, “That is something up with which I will not put.”). 

Anyway…java.home gives you the path the server is using to find the JVM.  Looking at that message, your first reaction should be, “Well yes, of course.”  If it is instead a phrase that starts with “What?” (perhaps followed by some stuff inappropriate to a family friendly blog) then that’s why the message is there.  Are you getting Java from where you think you are? 

Following that are two lines that tell you the Java level.  The first is java.version which very tersely tells you what Java you’ve got.  Something like 17.0.12 for the log I was looking at as I wrote this.  The java.runtime message which follows the version is essentially the proper full name for the java.version.  The one I’m looking at reads, “IBM Semeru Runtime Certified Edition for z/OS (17.0.12+7)”. 

And that’s all there really is to it for the Java information.  What level is it (short version and full version) and where are you getting it from.  Told you some of these posts would be quick.