AS/400 Toolbox for Java -- Beta 1 Readme
Workstation Requirements
- Intel based workstation running Windows 95 or Windows NT Workstation 4.0.
The workstation must have a TCP/IP connection to the AS/400.
- JDK 1.0.2
- JDBC 1.22 or later (if using JDBC)
- Netscape Navigator 3.0
OS/400 Requirements
- OS/400 Version 3 Release 2 or OS/400 Version 3 Release 7
- For V3R2, OS/400 at cumulative PTF level C6165320 or later
- For V3R7, OS/400 at cumulative PTF level C7042370 or later
- Host Servers option of OS/400 loaded on the AS/400
- TC1 Product (TCP/IP Connectivity Utilities for AS/400) installed and
configured on the AS/400.
Client Setup
Configuration
- Download tb400.exe. This is the self-extracting zip file that contains
the client code.
- Run tb400.exe to copy the class files to the workstation.
When prompted, specify the location of the files. The
default is c:\tb400.
- Add AS/400 Toolbox for Java to your classpath. For example, add the
following to your classpath:
c:\tb400\classes\ibmtb400.zip
- Class documentation is in javadoc output and an API Reference.
The starting point for this information is c:\tb400\doc\api_users_guide.html.
Java Applications
The only requirement is to change the classpath environment
variable so it also points to the AS/400 Toolbox for Java
classes.
Java Applets
-
Browsers running on Windows 95 allow connecting to one server when
the classes are accessed via a drive. This means the AS/400 Toolbox
for Java classes can be on a local or network drive and can still
create a socket connection to an AS/400 system.
-
Browsers running on Windows NT Workstation 4.0 require that
applets create socket connections only to the server the page
and classes are read from. This means the AS/400 Toolbox for Java classes
must be on the AS/400 they connect to.
Restrictions
National Language Enabling
- Only English-to-English character data conversion is supported.
This is client code page 437 or unicode to
AS/400 code page 037.
JDBC
The following methods on the DatabaseMetaData class
are not supported in this beta version:
getBestRowIdentifier(String, String, String, int, boolean)
getColumnPrivileges(String, String, String, String)
getCrossReference(String, String, String, String, String, String)
getExportedKeys(String, String, String)
getImportedKeys(String, String, String)
getIndexInfo(String, String, String, boolean, boolean)
getPrimaryKeys(String, String, String)
getProcedureColumns(String, String, String, String)
getProcedures(String, String, String)
getTablesPrivileges(String, String, String)
getTypeInfo()
getVersionColumns(String, String, String)
DatabaseMetaData.getColumns() returns a value for every parameter, but in some cases
the returned value is an empty string or a 0. These values are returned
as specified by the JDBC API:
TABLE_CAT - returns the table catalog
TABLE_SCHEMA - returns the table schema
TABLE_NAME - returns the table name
COLUMN_NAME - returns the column name
TYPE_NAME - returns the data source type name
COLUMN_SIZE - returns the column size
BUFFER_LENGTH - per API, not used, returns 0
DECIMAL_DIGITS - returns the number of fractional digits
NUM_PREC_RADIX - returns the radix
SQL_DATA_TYPE - per API, not used, returns 0
SQL_DATATIME_SUB - per API, not used, returns 0
These values are always returned as follows:
DATA_TYPE - returns 0
NULLABLE - returns 0
REMARKS - returns empty string
COLUMN_DEF - returns empty string
CHAR_OCTET_LENGTH - returns 0
ORDINAL_POSITION - returns 0
IS_NULLABLE - returns empty string
The following are not supported in the JDBC driver at this time:
- Julian date format
- Data truncation warnings are not posted
- ResultSet.getUnicodeStream() and PreparedStatement.setUnicodeStream()
do not support Unicode. Instead they support ASCII.
Known Problems
OS/400 Configuration Notes