Someone anonymous wrote: > I know what my end-game is -- a java class which will call an existing HLASM > module, which is _not_ XPLINK -- I wrote a dummy HLASM program called > JAVAOSLI, which simply does a WTO.
But your assembler module *is* LE? > It's my understanding that the only way to call HLASM from java is via an > intermediate C program, using JNI. I can't say you're wrong, but this seems like a very dodgy claim. What magic could C implement that assembler cannot? > My compile: > c89 -c -o sbjava_myc.o -W "c,langlvl(extended)" -W c,exportall -DNEEDSIEEE754 > -DNEEDSLONGLONG -I/usr/lpp/java/J7.0/include -I/usr/lpp/java/J7.0/include/zos > sbjava_myc.c The book claims that a JNI module invoked by Java must be a DLL. But the wording is somewhat confused: "Note: On z Systems [I think they mean z/OS, not zLinux], an executable program must be built as a Dynamic Link Library (DLL) in addition to export symbols, if an executable program packages JNI routines that the Java program must reference, by using static linking. If a z Systems executable program defines and exports JNI_OnLoad_testlibA, but is not itself built as a DLL (that is, -Wc,DLL is not specified), static linking is likely to fail, because the runtime is prevented from resolving the symbol back from the executable program." I don't know if this is really correct, but you don't seem to have specified -Wc,DLL . Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
