| Author |
Message
|
| pakya |
 Posted: Tue Nov 16, 2004 6:20 am Post subject: jdbc conectivity for As400 (error) |
 |
|
Novice
Joined: 22 Mar 2004
Posts: 14
|
While connecting broker to db2/400 database. The Broker toolkit is not able to make successful connection. It goes in Loop.
We check the job performance on As400 machine. The log is populated as below. This keeps on running. I looked for this error onm Google. The doc
http://www-912.ibm.com/s_dir/slkbase.NSF/0/2baf94c1a1ddbef48625660a0075db8a?OpenDocument
Says its memory leak. Do you have any idead about this error.
-------------------------------------------------------------------------------
Display Job Log
System: SYSTEMC
Job . . : QZDASOINIT User . . : QUSER Number . . . : 130877
Job 130877/QUSER/QZDASOINIT started on 11/15/04 at 10:55:52 in subsystem
QSERVER in QSYS. Job entered system on 11/15/04 at 10:55:52.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Additional 16 megabytes of storage allocated for this job.
Bottom
Press Enter to continue.
F3=Exit F5=Refresh F10=Display detailed messages F12=Cancel
F16=Job menu F24=More keys |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Tue Nov 16, 2004 6:39 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
How many different SQL statements are you running on the database?
Are you using parameters in your SQL queries? |
|
| Back to top |
|
|
| pakya |
| Posted: Tue Nov 16, 2004 7:02 am Post subject: |
|
|
Novice
Joined: 22 Mar 2004
Posts: 14
|
This is on connectecting the first screen with database where we spicified
at Database node.
when connecting to Mapping in datainsert node.
We say set RDB and the screen is populated.
database Name: WFMDATA
Username:XYZ
password:ABC
Database Vendor Type: DB2 univesal Data for iseries , V5/R1
JDBC Driver: As400 tool Box for Java jdbc Driver
Host: 10.1.1.1
Class Driver : jt400.jar
on connection its not able to populated the recoed. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Nov 16, 2004 7:24 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| All I can suggest is trying different ODBC drivers, or contacting IBM support. |
|
| Back to top |
|
|
| SixBlade |
| Posted: Thu Nov 18, 2004 3:58 am Post subject: |
|
|
Apprentice
Joined: 03 Dec 2003
Posts: 26
Location: UK
|
| Just in case you don't know, and as far as I can remember : db2 on mainframe creates a bunch of files/datasets when clients connect, differents sets for the differrent kinds of clients. You may need certain "admin access" to the server the first time the broker connects, in order to create nescessary files. I know I had to do that once. I can certainly help to try with another driver as well, I got stuck on one driver once, then..I think it was Merants driver that worked better. |
|
| Back to top |
|
|
| GYR |
| Posted: Thu Nov 18, 2004 6:49 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
| Pakya - what broker are you trying to connect, i.e what platform is the broker on ? have you created all the other stuff on the As400 that is needed to run a sucessful ODBC from the broker to the AS400? You should have a RDB directory entry of the database as *LOCAL i.e if your machine is called FRED than create an RDB enry called FRED for example, you also need to have a empty library called NULLID, you also need to ensure that your tables ypu are going to access have a CCSID value of 037 (american english) and you need to be running the STRHOSTSVR *DATABASE (cos it uses part of DDM) and also the TCP server STRTCPSVR *DDM. The onlt thing i am not sure if you still need now in V8 is the CCSID but that was definetely the case in V7 and we have stuck with it like this and have many ODBC connections to AS400. If you have doe all that and it still isn't working reply here cos dependant on your platform there are different drivers for the AIX for example to try other than the ones defaulted. Hope it helps |
|
| Back to top |
|
|
| pakya |
| Posted: Mon Nov 22, 2004 9:37 pm Post subject: |
|
|
Novice
Joined: 22 Mar 2004
Posts: 14
|
MY broker is on Solaris machine and I am trying to connect by help of WBI toolkit to an AS400 database.
One more dificulity as added to the problem . The column name is having # caracter which is creating problem as syntax error of ESQL
Is there any successful scienrio of connectiong As400 database from solaris machine.
Can any send the detials about it |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Nov 23, 2004 9:02 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| One more dificulity as added to the problem . The column name is having # caracter which is creating problem as syntax error of ESQL |
This should only be a Warning, and can be ignored.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
