The javah tool facilitates the implementation
of Java™ native
methods. It is compatible with the javah tool that is supplied
by Sun Microsystems, Inc. with a few exceptions.
Note: Writing native methods means that your application is not 100% pure Java.
It also means that your application is not directly portable across platforms.
Native methods are, by nature, platform or system-specific. Using native methods
may increase your development and maintenance costs for your applications.
The javah tool is available using the Qshell Interpreter.
It reads a Java class file and creates a C-language header file
in the current working directory. The header file that is written is an iSeries™ Stream
File (STMF). It must be copied to a file member before it can be included
in a C program on the iSeries server.
The javah tool is compatible with the tool that is provided
by Sun Microsystems, Inc. If these options are specified, however, the iSeries server
ignores them.
- -td
- The javah tool on the iSeries server does not require a temporary
directory.
- -stubs
- Java on
the iSeries server
only supports the Java Native Interface (JNI) form of native methods.
Stubs were only required for the pre-JNI form of native methods.
- -trace
- Relates to the .c stub file output, which Java on the iSeries server does not support.
- -v
- Not supported.
Note: The -jni option must always be specified. The iSeries server does not support native
method implementations prior to JNI.
For more information about the javah tool, see the javah
tool by Sun Microsystems, Inc.