DB2(OS/390)-Parallel odbc connection filling security logs
Posted: Thu Oct 26, 2006 1:11 pm
Hi,
I am facing an issue with using parallel odbc connections to a DB2 database( my source) on an OS/390.
I have DS EE 7.5.1 on an AIX 5.3 box.
Source DB2 is on an OS390/ZOS.
When I use an odbc connection to the source,the dba's are complainig the security logs get filled up ( more specifically the password has expired and hence the security logs on the source DB2 getting filled Up).
here is my .odbc.ini entry for
------------------------------------
[csd]
QEWSD=38864
Driver=/dstage/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
#SecurityMechanism=2
AlternateID=
Collection=nullid
Database=CDNXDB1Q
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=10.1.1.5
IsolationLevel=CURSOR_STABILITY
#Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=*****
Password=******
Package=CSDDV
PackageOwner=******
TcpPort=347
WithHold=1
------------------------------------
We haven't changed any password for the userdid that I am using.
Couple of times the job runs successfully.
Has anyone experienced this issue .
Any help is greatly appreciated.
Thanks,
MB
I am facing an issue with using parallel odbc connections to a DB2 database( my source) on an OS/390.
I have DS EE 7.5.1 on an AIX 5.3 box.
Source DB2 is on an OS390/ZOS.
When I use an odbc connection to the source,the dba's are complainig the security logs get filled up ( more specifically the password has expired and hence the security logs on the source DB2 getting filled Up).
here is my .odbc.ini entry for
------------------------------------
[csd]
QEWSD=38864
Driver=/dstage/Ascential/DataStage/branded_odbc/lib/VMdb220.so
Description=DataDirect 5.00 DB2 Wire Protocol Driver
AddStringToCreateTable=
#SecurityMechanism=2
AlternateID=
Collection=nullid
Database=CDNXDB1Q
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=10.1.1.5
IsolationLevel=CURSOR_STABILITY
#Location=OS/390 and AS/400 (Remove for DB2 UDB)
LogonID=*****
Password=******
Package=CSDDV
PackageOwner=******
TcpPort=347
WithHold=1
------------------------------------
We haven't changed any password for the userdid that I am using.
Couple of times the job runs successfully.
Has anyone experienced this issue .
Any help is greatly appreciated.
Thanks,
MB