• Subject: RE: help with applets...
  • From: dawall@xxxxxxxxxx
  • Date: Wed, 22 Sep 1999 16:43:43 -0500

I opened up the exception file and saw the following stack trace.
     java.io.UnsupportedEncodingException: Cp037 [Could not load class:
sun.io.ByteToCharCp037]
     at sun/io/ByteToCharConverter.getConverter
     at java/io/InputStreamReader.<init>
     at com/ibm/as400/access/ConvTable.<init>
     at com/ibm/as400/access/ConvTable.getTable
     at com/ibm/as400/access/Converter.<init>
     at com/ibm/as400/access/Converter.getConverter
     at com/ibm/as400/access/Converter.getConverter
     at com/ibm/as400/access/DataStream.<clinit>
     at com/ibm/as400/access/AS400.<clinit>
     at java/lang/ClassLoader.findSystemClass
     ....

This stack trace indicates you are using a very old version of the Toolbox.  We
saw this behavior with the original Toolbox (the one that came out with OS/400
V4R2).  The first or second Toolbox PTF fixed this problem and it has been fixed
in all Toolbox releases since v4r2.  Please load the latest PTF or upgrade to a
newer version of the Toolbox and try again.

FYI - the problem is browsers do not ship EBCDIC to/from unicode conversion
tables.  Your program (or via the Toolbox sign-on dialog) a userid in Unicode (a
Java String) is delivered to the Toolbox.  It must convert the Userid to EBCDIC
before sending it to the AS/400.  The client JVMs (Sun's Win32 and Solaris JVMs,
IBM's Win 32, AIX and AS/400 JVMs, etc.) ship conversion tables, browsers don't.
In 'normal' cases the Toolbox can handle this.  We get a conversion table from
the AS/400.  We have the chicken and egg problem at signon time, however.  We
cannot get a conversion table unless we communicate (signon) with the AS/400 but
we can't signon unless we convert the UserID.  We fixed this by shipping a
Unicode to 37 (ebcdic) table with the Toolbox.  UserIDs can contain only a small
subset of characters and we make sure we can convert them.

I hope this helps,

David Wall
AS/400 Toolbox for Java


"Gunda, Praveen (CTS)" <GPraveen@dbss.com> on 09/22/99 02:36:13 AM

Please respond to JAVA400-L@midrange.com

To:   "'JAVA400-L@midrange.com'" <JAVA400-L@midrange.com>
cc:
Subject:  RE: help with applets...




Hi,

    We are facing some problems at run time in accessing the AS/400 database
from an applet. The applet & Html  are written, compiled & reside  on
AS/400(V4R2M0) only. Also both the applet & Database reside on the same
AS/400. We are on an V4R2M0 m/c & are using an HTTP Server which comes along
with the AS/400. The browser i used to access the HTML was Internet Explorer
5.0 .

The attached document contains the source code of :
 applet : applet.java
 Html   : applet.html
 Errors : Exception.txt
We have also tried using the following :
     a.  Classpaths on the AS/400 :
         1.
/qibm/proddata/http/public/jt400/lib/jt400.jar
         2.
/qibm/proddata/http/public/jt400/lib/jt400.zip
     b.  using archive key word in the Applet tag of Html & specified the
above two paths of JT400.jar & JT400.zip


We are just trying to display a panel with 3-buttons. When the user clicks
the Connect button the applet is supposed  to connect to the AS/400, But it
is throwing Exceptions(attached in Exception.txt).

The same code is working  fine when written as an application either on
AS/400 or PC .


It would be Great! if u can help us..

Thanks & Regards
Praveen


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.