You are not logged in.
i have a problem with my AS400 connection, it is not possible to be connected with talend.
I use jt400 in other app (/ex ireport) and it's work fine but i get an SQL error with Talend.
it's SQL901 error, this mean that connection is done but not a correct "communication"
i don't know where i can found log for this error in my AS400.
i don't understand why it's working with ireport and not with talend.
i need help
Which version of Talend are you using? There have been a lot of work on AS400 related issues between V2.1.4 and V2.2.1. I currently have had no problems with AS400 connections, except for tCreateTable component. The tCreateTable issue should be corrected in the next release. I would only use V2.2.1 for AS400 connections.
You didn't mention if the problem was with Metadata or a specific component. If you are having problems with the tAS400Output component, you might want to change the 'use commitment control' check box. If your file isn't set to use commitment control on the AS400 (journaled files) the box should not be checked. If they are under commitment control, check that box. I think the defaults were changed in Talend V2.2.1 to not use commitment control by default.
Hope that helps, and if it doesn't, leave a bit more detail about what component you are using and when the error occurs.
hi, thanks to reply jerry
On my PC or any other metadata connection or tdbinput connection or dbjdbcinput give me the same bad result.
jdbc connection work very well with other app : ireport, kettle, jasperserver...
does i need a special setup with my as400 to work with talend ?
1) Are you using a Perl or Java Project. The Java project have AS400 specific connectors, tAS400Input and tAS400Output. And the Metadata create connection wizard will create AS400 specific connections.
I don't think Perl projects are really set up to handle AS400. If you are able to get to an AS400 in a Perl project, I think you end up going through the JDBC:ODBC bridge; something that APITA as far as I'm concerned. Java Projects will give you direct connections through the JT400 JDBC driver which probably is what's working fine for you with other products.
I didn't need any special setup. I would guess that all the applications you have made AS400 jdbc connections use the JT400 driver, just like Java project do in Talend.
If you really, really want to work in a Perl project, I'd start by creating an OBDC connection to the AS400. Once you get that working, then I'd try setting up a generic OBDC connection in Metadata. I wouldn't recommend it though...
Last edited by jleeper (2007-11-16 00:51:37)
it's ok like this
i just connect a tinputas400 and toutputdelimited, run it ..............
and it's work.
the probleme is just at the connection test ?
i am not able to open the tinputas400's sql builder.
i am not able to define a data connection.
thanks for help
it's a V5R3 version
is there a way to bypass the problem or am i obliged to migrate to V5R4 ?
Last edited by chris doudet (2007-11-29 09:38:50)
In fact it seems there is a problem either in the V5R3 or in the jt400 driver with the V5R3 with the option "libraries". (this option should be the same it seems for R3 & R4 version)
To keep the compatiblity with the V5R3, we "must" remove the option "libraries" used in the connection or sql builder.
The problem is that if we do that, when you will list all the tables from the connection, it will list all the tables from all the libraries.
So instead of have for example 10 tables listed in the selected library, you will see maybe 500.. 1000 tables maybe (or far more depends your system), so of course it's not really convenient to select the table you want.
- We add a "flag" to be able to keep the compatibility with R3 version (remove the option libraries for connection/sqlbuilder).
- We "force" to use the R4 version. (difficult to know if there is the same problems in R2 or lower versions)
The problem you had is described here in fact: http://talendforge.org/bugs/view.php?id=1996
jsleeper had the same problem before, but after he changed to version R4 it works.