ODBC.ini File Help
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
ODBC.ini File Help
Hi All,
My requriement is to connect to a DB2/400 (iSeries) & SQL Server sources with the Datastage server in AIX 5.3. and the target is DB2 UDB which is installed in the server itself. I'm a bit confused about the odbc.ini file settings. I herewith attach the sample odbc.ini file I'd modified based on my understanding of the documentations available. Kindly requesting to correct me if I'm wrong in any of the settings.
[DB2 Wire Protocol]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (Remove for DB2 UDB)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.x.xxx.xx
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=xyz123
Password=xxxxxx
Package= xxxxxx
PackageOwner= idb2dev1
TcpPort=8471
WithHold=1
[SQLServer]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=recovery
LogonID=xxxxxxxx
Password=xxxxxxx
Address=sql2k5pmlo1,1433
QuotedId=No
AnsiNPW=No
Thanks in Advance...
My requriement is to connect to a DB2/400 (iSeries) & SQL Server sources with the Datastage server in AIX 5.3. and the target is DB2 UDB which is installed in the server itself. I'm a bit confused about the odbc.ini file settings. I herewith attach the sample odbc.ini file I'd modified based on my understanding of the documentations available. Kindly requesting to correct me if I'm wrong in any of the settings.
[DB2 Wire Protocol]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (Remove for DB2 UDB)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.x.xxx.xx
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=xyz123
Password=xxxxxx
Package= xxxxxx
PackageOwner= idb2dev1
TcpPort=8471
WithHold=1
[SQLServer]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=recovery
LogonID=xxxxxxxx
Password=xxxxxxx
Address=sql2k5pmlo1,1433
QuotedId=No
AnsiNPW=No
Thanks in Advance...
Re: ODBC.ini File Help
Is there any error encountered,if so can you post the error information here, usually we just need add coresponding DSN entry in the .odbc.ini file under $DSHOME....
antonyraj.deva wrote:Hi All,
My requriement is to connect to a DB2/400 (iSeries) & SQL Server sources with the Datastage server in AIX 5.3. and the target is DB2 UDB which is installed in the server itself. I'm a bit confused about the odbc.ini file settings. I herewith attach the sample odbc.ini file I'd modified based on my understanding of the documentations available. Kindly requesting to correct me if I'm wrong in any of the settings.
[DB2 Wire Protocol]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (Remove for DB2 UDB)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.x.xxx.xx
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=xyz123
Password=xxxxxx
Package= xxxxxx
PackageOwner= idb2dev1
TcpPort=8471
WithHold=1
[SQLServer]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=recovery
LogonID=xxxxxxxx
Password=xxxxxxx
Address=sql2k5pmlo1,1433
QuotedId=No
AnsiNPW=No
Thanks in Advance...
Last edited by hailun on Sat Sep 12, 2009 7:21 am, edited 1 time in total.
Let's Progress Together....
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
Yes /datastage/dsadm/Ascential/DataStage/DSEngine is the home path for Datastage, the .odbc.ini file you are modifying is under this path,right...
Now you need add approciate DSN entry in that file.
[a]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (Remove for DB2 UDB)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.x.xxx.xx
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=xyz123
Password=xxxxxx
Package= xxxxxx
PackageOwner= idb2dev1
TcpPort=8471
WithHold=1
[c]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=recovery
LogonID=xxxxxxxx
Password=xxxxxxx
Address=sql2k5pmlo1,1433
QuotedId=No
AnsiNPW=No
After that you need add entry a and c to another file named uvodbc.config under the same path also the uvodbc.config file under project path if not newly created after modifying $DSHOME level uvodbc.config file....
Then you can add odbc stage in your job before uisng the DSN a or c....
Now you need add approciate DSN entry in that file.
[a]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (Remove for DB2 UDB)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=xxx.x.xxx.xx
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=xyz123
Password=xxxxxx
Package= xxxxxx
PackageOwner= idb2dev1
TcpPort=8471
WithHold=1
[c]
Driver=/datastage/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=recovery
LogonID=xxxxxxxx
Password=xxxxxxx
Address=sql2k5pmlo1,1433
QuotedId=No
AnsiNPW=No
After that you need add entry a and c to another file named uvodbc.config under the same path also the uvodbc.config file under project path if not newly created after modifying $DSHOME level uvodbc.config file....
Then you can add odbc stage in your job before uisng the DSN a or c....
antonyraj.deva wrote:There's no error so far since I haven't tried to run any job using ODBC till now. Do I need to create the ODBC profiles also on the local system where the DS client is installed? and $DSHOME points to /datastage/dsadm/Ascential/DataStage/DSEngine> is this the default location for DSHOME?
Last edited by hailun on Mon Sep 14, 2009 7:23 pm, edited 2 times in total.
Let's Progress Together....
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata