× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi, I have postet it yesterday, but I got some new information.

The following code works fine with V5R4 but not on V6R1
I have created Table:
drop table usraf.go1
create table usraf.GO1 (
govdc char(30)
)

executed InsertStatement:

AS400JDBCDataSource ds= new AS400JDBCDataSource("192.168.2.2" ,"XXX",
"XXX");
try{
ds.getConnection().createStatement().executeUpdate("INSERT INTO usraf.GO1
(govdc ) VALUES ('§ÄÄÄÖÖÖ' )",java.sql.Statement.RETURN_GENERATED_KEYS);
}
catch (SQLException e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}

the string i used is only for test purpose.
The column uses CCSID 273

The jt400.jar is the same.

After executing the statement on both servers I can find the entry but the
text is not
correct on V6R1. The carrecters I can see are:
@¢¢¢\\\
When using same code but with java.sql.Statement.NO_GENERATED_KEYS, or
without 2nd parameter, then everything is ok. All characters are correct.

Also on V5R4 everything is correct

Thanks in advanced for any advie or help.


Mit freundlichen Grüßen / Best regards

DI(FH) Andreas Fritz
Leitung Java-Entwicklung
__________________________________________
Vector SW DV GmbH
Ernst-Melchior-Gasse 20
1020 Wien / Austria
fon: +43 1 216 50 40 - 0
fax: +43 1 216 50 40 - 50
UID: ATU15116602
FB: 99492m
Firmenbuchgericht: Handelsgericht Wien
Besuchen Sie uns / visit us at http://www.vector.eu
__________________________________________


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.