If specified after the Java method name in the EXTERNAL NAME clause of the CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature must correspond to the default Java type mapping for the signature specified after the procedure or function name. For example, the default Java mapping of the SQL type INTEGER is "int", not "java.lang.Integer".
|It is essential that the db2java.zip file used by the Java applet be at |the same FixPak level as the JDBC applet server. Under normal circumstances, |db2java.zip is loaded from the Web Server where the JDBC applet server is |running, as shown in Figure 22 of the book. This ensures a match. If, however, |your configuration has the Java applet loading db2java.zip from a different |location, a mismatch can occur. Prior to FixPak 2, this could lead to unexpected |failures. As of FixPak 2, matching FixPak levels between the two files is |strictly enforced at connection time. If a mismatch is detected, the connection |is rejected, and the client receives one of the following exceptions: |
| COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] | CLI0621E Unsupported JDBC server configuration.
| COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] | CLI0601E Invalid statement handle or statement is closed. | SQLSTATE=S1000|
|If a mismatch occurs, the JDBC applet server logs one of the following |messages in the jdbcerr.log file: |
| jdbcFSQLConnect: JDBC Applet Server and client (db2java.zip) | versions do not match. Unable to proceed with connection., einfo= -111
| jdbcServiceConnection(): Invalid Request Received., einfo= 0
|