Toolbox for Java™ & JTOpen

Overview

Downloads

Support

News

Are you having trouble with the IBM Toolbox for Java? Check the following:

• Service Packs
• Required i5/OS PTFs
• Client/Server Communication
• JDBC
• Record-level access
• Integrated file system
• Graphical Toolbox
• Java Related
• Taking a trace
• Reporting problems

Required i5/OS PTFs
Are the required i5/OS PTFs on your system?

Client/Server Communication

• Is there an active TCP/IP connection between your client and i5/OS system? 'Ping' your i5/OS system from your workstation to see if the connection is active. Also 'ping' your workstation from the i5/OS system. The Toolbox also provides a class called, JPing, in the utilities package which can be use to determine if a TCP/IP connection can be made to the i5/OS host servers.
• Are the i5/OS host servers started ? The IBM Toolbox for Java classes use the i5/OS host servers as the access point to i5/OS data. Use "STRHOSTSVR *ALL" from an i5/OS command prompt to start the servers. The file and database servers run in the QSERVER subsystem. If not already started, run "STRSBS QSERVER" from an i5/OS command prompt to start the subsystem before starting the servers.
• Is the QUSER user profile enabled and does it have a valid password? The i5/OS host servers pre-started jobs begin under the QUSER profile. Once the Toolbox connects to the host server, the server job swaps to the user profile supplied by the Java program or entered on the toolbox sign-on dialog. QUSER must be enabled and have a valid password.

Back to top

Troubleshooting JDBC

• Does your program receive exception "No suitable driver found" when it tries to access an i5/OS database?

  You must you register the IBM Toolbox for Java JDBC driver with the DriverManager class. To register the driver add DriverManager.registerDriver(new com.ibm.as400.access.AS400JDBCDriver()); to your program, or add com.ibm.as400.access.AS400JDBCDriver to the JDBC.drivers property.

  Class.forName(new com.ibm.as400.access.AS400JDBCDriver()) does not register the JDBC driver on some JVMs. See Sun's JDBC FAQ for more details.

• Does your program receive "com.ibm.as400.access.AS400JDBCException: [PWS0001] Function did not complete successfully" when it accesses an i5/OS database file?
  Make sure the latest i5/OS database server PTFs are applied to the i5/OS system. This message usually indicates an error in the database server.
• Does your program fail when it tries to execute a stored procedure using the Toolbox JDBC driver? Does your program receive "java.sql.SQLException: Descriptor index not valid"?
  • Make sure the procedure exists on the i5/OS.
  • For the location of the procedure, make sure the schema name is used, not the library name.
  • Make sure the procedure being called does not expect input parameters.

Back to top

Troubleshooting Record-Level Database Access

• The record-level access classes will not function if the host servers aren't started on the i5/OS system. Run "STRHOSTSVR SERVER(*ALL)" from an i5/OS command prompt to start the servers.
• For V4R2 and later, the record-level access classes will not function if the DDM server is not started on the i5/OS system. Run "STRTCPSVR SERVER(*DDM)" from an i5/OS command prompt to start the server.
• The record-level access classes will not function if the "DDM Request Access" network attribute is set to *REJECT. Run "DSPNETA" from an i5/OS command prompt to make sure this attribute is set to *OBJAUT.
• By default, the record-level access server runs in the QSYSWRK subsystem. Run "STRSBS QCMN" from an i5/OS command prompt to start the server.
• When using KeyedFile, the key value for character fields that are not variable length must be blank padded to the fixed length of the field.

Back to top

Troubleshooting Integrated File System Classes

• What object types in the QSYS.LIB directory can be manipulated? In general, the file server on i5/OS does not allow objects in the QSYS.LIB file system to be opened for data access. The contents of these objects (such as user profiles, job descriptions, data queues, device descriptions, etc.) cannot be read or written. The exception is source physical file members and user spaces. The data in these two types of objects can be read and written.

Back to top

Troubleshooting the Graphical Toolbox

• Instructions for non-English Graphical Toolbox Developers

  For non-English Graphical Toolbox developers, there is a problem where the message viewer will display properly with the correct translated strings, but the panel is constructed using the English layout. Using the English layout means that strings on the panel will be truncated for NLVs that require that the panel be enlarged to accommodate longer strings (for example, Germany).

  To correct this, Non-English Graphical Toolbox developers must copy two files from the Toolbox directory on the i5/OS system to their local machines.

  To correct this, Non-English Graphical Toolbox developers need to manually copy the following files from the Toolbox directory on the i5/OS system ( /QIBM/ProdData/HTTP/Public/jt400/MRI29xx/ )
  to their local machines:

  • IDD_CM_MESSAGE_DETAILS_locale.pdml.ser
  • IDD_CM_MESSAGE_VIEWER_locale.pdml.ser

Back to top

Java Related

• Your Java Virtual Machine must support JVM 1.1.8 or later.
• If accessing the class files from a Java program, jt400.jar must be in your classpath.
• When running an applet in a browser, do you see error java.io.FileNotFoundException for "/com/ibm/as400/access/MRI.class"? You can ignore this error. The Toolbox uses property resource bundles for its messages. When the Toolbox loads its messages, the browser first tries to find file MRI.class before it looks for MRI.properties. The messages are in MRI.properties. The Toolbox will function properly even though the error is displayed.

Back to top