LPA JDBC\DB2Connect to Mainframe DB2

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?

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!

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.

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)

Hi Erin,

So... It's working now?

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)