It seems to me that "JVM translations of programs" refers to the translation that the JVM does from Java byte code to machine instructions, whether it be the JVM JIT or the JVM interpreter. The part "provided all of such translation is solely controlled by the JVM" tips it off, since the JVM doesn't do translation from the "Java programming language" to byte codes (that is done by a Java compiler, which is completely separate from the JVM - you don't even need to use IBM's Java compiler).
More practically, there isn't any difference between byte codes (class files) that originated from the "Java programming language" and any of the other dozens of languages that generate Java byte codes. Among those languages are a couple of COBOL compilers. So I think that this statement would be more accurate if "Java programming language" were changed to "the Java byte code format defined by the Java programming language". As currently written it doesn't quite make sense. Should there ever be a question, one could always demonstrate that your (Scala, etc) generated class files could be automatically translated to Java source code and then back to identical Java byte codes. It is also interesting that IBM itself uses the ASM byte code modification library internally in Websphere (and no doubt other products). ASM is a Java framework that allows for the dynamic modification of class files (byte codes). The resulting class byte codes didn't as a whole come from the Java programming language. Many of the JVM based languages use ASM as a convenience layer for generating Java byte codes. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Sep 6, 2016 at 3:03 PM, Tony Harminc <[email protected]> wrote: > On 6 September 2016 at 02:59, Timothy Sipples <[email protected]> wrote: > > If you're interested in Scala, just grab it and go. You'll also need the > latest Java SDK if you don't have it already. > > > > http://www.scala-lang.org/download/ > > http://www.ibm.com/systems/z/os/zos/tools/java/ > > > > The IBM Knowledge Center includes some references to deploying Scala > programs on z/OS. See here, for example (watch the wrap): > > > > http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/ > com.ibm.zos.v2r2.azkd100/azk_getting_started.htm > > Is there an IBM statement or addendum regarding running Scala code on > zAAP/zIIP engines? The current IBM Authorized Use Table for IBM > Machines (November 2015) > http://www-947.ibm.com/systems/support/machine_ > warranties/machine_code/aut.html > does not mention Scala, and is perhaps ambiguous about whether Java > bytecodes created by something other than a Java compiler are > eligible. The relevant (I believe) section says: > > "JVM translations of programs written in the Java programming > language, provided all of such translation is solely controlled by the > JVM;". > > One could argue that this precludes anything not actually written in > the Java language. Or one could argue that it's Java bytecodes or > class files that are or are not eligible, in which case Scala would be > fine. But any argument that says Scala is eligible would work just as > well to argue that COBOL compiled into a Java class would be eligible; > something I expect IBM would not agree to. > > I suppose the bottom line, as always, is that IBM can decide to > interpret this the way it wants at the time it wants. > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
