OS/390 ODBC connection setup problems

yakiku · Post by **yakiku** » Thu Jun 08, 2006 9:09 am

Hi,

I am trying to set up ODBC connection to a DB2 database on a OS/390 system.

When i tried to do 'bind20 DB2DSN', I am getting the error:
Package creation failed!: 1242.
1242 in LC_Messages is expanding to: "Remote Database Not Found"

Does anyone know how to address this problem?
Here is the .odbc.ini entry i created for this connection:

---------------------------------------------
[DB2DSN]
Driver=/opt/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.xxx.xx.x
IsolationLevel=CURSOR_STABILITY
Location=OS/390
LogonID=
Password=
Package=DSPKG
PackageOwner=REVDDR
TcpPort=xxx
WithHold=1
--------------------------------------------

Appreciate any pointers toward solving this problem.

TIA,
Yakiku

ray.wurlod · Post by **ray.wurlod** » Thu Jun 08, 2006 3:06 pm

Is a "/" permitted in the Location field? (I don't know the answer to this, but the rest of the definition (except, maybe, Collection and for the same reason) looks OK. Does what's in the ODBC data source definition match what's possible in your DB2 client configuration?

Eric · Post by **Eric** » Fri Jun 09, 2006 5:31 am

Yes Ray, you must complete the Name of the DB2 'collection' and 'location'.

yakiku, talk to your OS/390 Administrator to find the correct values.

ray.wurlod · Post by **ray.wurlod** » Fri Jun 09, 2006 7:00 am

I know you must complete it. My question was whether "/" is a valid character in this field's value.

Eric · Post by **Eric** » Mon Jun 12, 2006 4:39 am

Ah, sorry

I don't beleive that "/" is a permitted value in the connection parameters for DB2 on Z/os. The "OS/390" is a default value for the parameters which are only relevent for Z/os DB2 connections.

yakiku · Post by **yakiku** » Wed Jul 19, 2006 7:52 am

Got the connection to work and here is the update. "/" was one of the problems.

[DB2MC]
QEWSD=38879
Driver=/opt/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=DSDEW
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.xxx.xxx.xxx
IsolationLevel=CURSOR_STABILITY
Database=DBDB2
Location=DB2MC
LogonID=
Password=
Package=DSDB2
PackageOwner=lmnr
TcpPort=446
WithHold=1

ray.wurlod · Post by **ray.wurlod** » Wed Jul 19, 2006 8:00 am

I can see that Collection, Location, Package, Package Owner and TCP Port have changed. Can you shed any light on why the new values are good and the old values are bad?

yakiku · Post by **yakiku** » Wed Jul 19, 2006 8:10 am

Collection and Location: "/" is not a valid character. Worked with the DB2 DBA and gave the names as per suggestion.
Package and Package owner: These changes were for permissions. The owner mentioned in the first post did not have the permissions to create a package.. hence the change.
TCP Port: This has not changed.. i unmasked it in my last post. thats all.

Thanks to everyone who responded. Appreciate your help.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 19, 2006 5:17 pm

And thank you - anyone who has the same issue in future can now find a solution, with reasoning to convince their DBA.

anupam · Post by **anupam** » Fri Feb 06, 2009 4:17 am

What is QEWSD used for?

I wanted to know what is the significance of this value...

ray.wurlod · Post by **ray.wurlod** » Fri Feb 06, 2009 2:53 pm

As far as I can recall it's something to do with the licensing of the Data Direct ODBC driver - a way for DataStage to identify itself to the driver licensing mechanism. (But I'm not 100% certain on this and would be happy to be corrected.)