Toolbox for Java: Beta Known Problems




Record-level database access

  • The server program for V3R2, V3R7 and V4R1 is submitted to run in job queue QSYSNOMAX. Any user profile connecting for record level access must have *USE authority to the QSYSNOMAX job queue.

VisualAge for Java

  • VisualAge for Java stores resource files in the file system. Instead of storing them in the workspace or the repository, VisualAge for Java creates a directory for each project and stores the resources in that directory. VisualAge for Java does not correctly search for resource files when there are multiple projects in the workspace. When a program in one project uses AS/400 Toolbox for Java classes imported into a different project, the AS/400 Toolbox for Java classes may not be able to find their resources. This will cause the AS/400 Toolbox for Java classes to fail. VisualAge for Java reports the error as "Uncaught exception (java.lang.ExceptionInInitializerError)"

    For example, suppose the AS/400 Toolbox for Java classes are imported to a project called 'jt400' and an application that uses these classes is imported to a project called 'myApp'. myApp will fail when it uses an AS/400 Toolbox for Java class.

    Refer to the Visual Age for Java documentation for a way to work around this problem. Here are a couple of suggestions:
     

    1. Update the classpath environment variable inside Visual Age for Java so it points to the toolbox resources. When you run your class inside Visual Age for Java, the first dialog provides an option to update classpath. Append ..\project_resources\jt400 to classpath where 'jt400' is the name of the Visual Age project containing the toolbox classes.

    2. Copy the property files from the AS/400 Toolbox for Java project to each application project. Suppose VisualAge for Java was installed to d:\vajava. To make myApp from the previous example work do the following:
          md d:\vajava\ide\project_resources\myApp\com
      
          md d:\vajava\ide\project_resources\myApp\com\ibm
      
          md d:\vajava\ide\project_resources\myApp\com\ibm\as400
      
          md d:\vajava\ide\project_resources\myApp\com\ibm\as400\access
      
          copy d:\vajava\ide\project_resources\jt400\com\ibm\as400\access\*.*
      
               d:\vajava\ide\project_resources\myApp\com\ibm\as400\access\*.*

  • The COM.ibm.as400.vaccess.IFSFileDialog class does not work inside VisualAge for Java. VisualAge for Java reports the error as "Uncaught exception (java.lang.InternalError: (Ex02))". We are investigating this problem but do not have a solution at this time. Programs using IFSFileDialog must be run outside of VisualAge for Java.

  • The system name and userid are not uppercased on the sign-on dialog. To work around this problem, AS/400 Toolbox for Java internally uppercases the system name and userid so that correct information is passed to the AS/400.