Ha! Makes perfect sense.... in a weird Java sort of way...
jvmap3270sr10fp1-20170215_012.6.
jvmap - Java map
32 - 32 bit version
70 - Java 7
sr10 - service release 10
fp1 - fix or feature pack 1
20170215 - Date... Feb 15 2017 ie.. the build date.
The IBM i Java page on Developer works has all the latest updates and
schedules. There has been a couple of updates since that level. So you
may want to consider getting the latest Java PTF Group.
Tim
Tim Rowe, timmr@xxxxxxxxxx
Business Architect Application Development & Systems Management for IBM i
IBM i Development Lab, Rochester, MN
(507) 253-6191 (Tie) 553-6191
http://www-03.ibm.com/systems/power/software/i/are/index.html
message: 1
date: Fri, 16 Mar 2018 12:55:23 -0700
from: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
subject: Anybody know how to make sense out of OS/400 JVM
designations?
Ladies and Gentlemen:
I'd post this to the Java-400 List, but that's so low-traffic, the last
thing I posted there seems to have died of loneliness.
Does anybody know what the various OS/400 JVM designations mean in
general?
And in particular for jvmap3270sr10fp1-20170215_012.6, what the "3270"
means? (And yes, I know "3270" is a terminal standard for IBM
mainframes, but I don't think that applies here.)
We've got a situation in which our latest Tomcat webapp context works
fine in every JVM it's been tried in, with a single exception:
jvmap3270sr10fp1-20170215_012.6.
--
JHHL
midrange.com
