Who's On?

	Membership:
	Latest: Starr
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5327

	People Online:
	Visitors: 409
	Members: 0
	Total: 409

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3293
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244

LPA JDBC\DB2Connect to Mainframe DB2

6 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

Erin

Advanced Member

Posts: 24

6/19/2013 6:57 PM

We have LPA Designer version 10.0.2.8..5466 (2012).
I have JDBC drivers on my PC and also DB2Connect.

However, no matter what I do the connection via JDBC\DB2Connect is not connecting so I can test my process flow. The DBA's assure me that JDBC and DB2Connect is set up correctly on my PC. Even when I move it up the Landmark server it does not connect.

Driver I am using: COM.ibm.db2.jcc.DB2Driver
Database URL: jdbc:db2//db2connect_test.[my company].com:50001/DSNT

Can anyone point me in the right direction in order to get it to connect either on my PC for testing and the Landmark server?

Tags: LPA DB2Connect JDBC

Woozy

Veteran Member

Posts: 709

6/19/2013 7:48 PM

Hi Erin,

I'm not sure what your OS is - we're running Unix, so some of these may be different. I'm also not familiar with DB2Connect, so I can't give you any pointers there.

Just a couple of thoughts.
- For the driver, did you try "com.ibm.db2.jcc.DB2Driver" instead of "COM.ibm.db2.jcc.DB2Driver"?
- Confirm you have both the db2jcc_license_cu.jar and the db2jcc4.jar drivers on your machine, and that you have your designer pointed to them: (menu>>Window>>Preferences>>Lawson Process Designer>>External Jars)
- Did you double- and triple-check your URL, including port?
- Did you confirm that the user is configured and has access and that you are using the correct password? (Can you query the tables as that user using a different query tool?)

These all may sound like obvious things, but I've been bitten by all of them when trying to get this working in our environment.

What is the error you are getting?

Woozy

Veteran Member

Posts: 709

6/19/2013 7:59 PM

Oh...one other thing. Be sure you didn't fat-finger the password. :-)

I've learned from terrible experience to cut-and-paste from a text editor or password safe.

Good Luck!

Kyle Jorgensen

Veteran Member

Posts: 122

6/20/2013 12:14 PM

We use DB2 on zOS. For what it's worth, the format of the URL we use is "jdbc:db2:". For example, "jdbc:db2:lawv9tdb". Also, the "com" in our driver is lower-case.

Erin

Advanced Member

Posts: 24

6/28/2013 10:46 PM

Thank you to Woozy and Kyle.
We are on zOS and I had "com" lower case instead of upper case (not using the app driver).
We also checked the Class Path and didn't have the correct license in the classpath (db2jcc_license_cisuz.jar)

Woozy

Veteran Member

Posts: 709

6/29/2013 1:54 AM

Hi Erin,

So... It's working now?

Erin

Advanced Member

Posts: 24

7/12/2013 7:41 PM

Woozy,
Yes, we finally got it working. We added db2jcc_license_cisuz.jar to the CLASSPATH (and I fixed the "typo" that I did with the word COM and yes, you were right, I have fat fingers!)
We have a lot of legacy systems on DB2 that need interfaces to/from Lawson (ahem, I mean S3)