DSXchange

If you have a 64bit hashed file then it will be able to store 18Gb of data. If your OS does not allow files larger than 2Gb then using a 64bit hashed file won't help; and this is what I think has happ ... I thought that the max limit for 64bit hash file is not more than 4GB. BTW..why won't the OS a...

I have data larger than 2GB to be stored into a hash file. The hash file I am using is 64bit. Still it is not able to store the data and the server job which does this aborts with WriteHash() error. Should I go for a PX job with datasets, or is there any way for making the hash file store that much ...

ray.wurlod wrote:The 32-bit DB2 library is required because DataStage IS a 32-bit client. The 32-bit DB2 library is entirely capable of communicating with a 64-bit DB2 instance. ...

In that case the job should not fail while trying to load a table.
Then why it is failing?

Need some more insight into this whole thing. I am still not clear. Can anyone provide any link or something which has information on this?

This is the complete error message Result = Could not load program /db2t/gtstinsa/sqllib/bin/db2: Could not load module /db2t/gtstinsa/sqllib/lib/libdb2.a(shr_64.o). Dependent module /usr/opt/db2_08_01/lib/libdb2trcapi.a(shr_64.o) could not be loaded. Member shr_64.o is not found in archive Could no...

I have modified the routine to Equate RoutineName To "ConnectToDB2" Equate DBNAME TO Arg1 DB2CntCmd = "db2 CONNECT TO ":DBNAME ResultText = @Null Call DSExecute("UNIX", DB2CntCmd, ResultText, SystemReturnCode) If SystemReturnCode <> 0 Then Ans = ResultText Return(Ans) E...

Hi Craig
It would be very helpful if you could rewrite that routine for me

I agree with you
But I have to convince my Lead that we can connect to a 64 bit server using a 32 bit DSjob

I have written a routine Equate RoutineName To "ConnectToDB2" Equate DBNAME TO Arg1 Equate DBSCHEMA TO Arg2 DB2CntCmd = "db2 CONNECT TO ":DBNAME ResultText = @Null Call DSExecute("UNIX", DB2CntCmd, ResultText, SystemReturnCode) If SystemReturnCode <> 0 Then Ans = "...

i have written a routine to connect to db2 Equate RoutineName To "ConnectToDB2" Equate DBNAME TO Arg1 Equate DBSCHEMA TO Arg2 DB2CntCmd = "db2 CONNECT TO ":DBNAME ResultText = @Null Call DSExecute("UNIX", DB2CntCmd, ResultText, SystemReturnCode) If SystemReturnCode <> 0...

Write a shell that invokes the db2 connect and runs the query via DSExecute() command. Ofcourse you can make it much easier and use a simple datastage job to do this. I need to do this because we are testing whether a routine in DataStage can connect to 64 bit DB2 server. The DataStage client is a ...

I need to connect to the DB2 using a routine
and then fire a query "select * from schema.table " and write the result to a delimited file

Since DataStage is 32-bit application you will have to install 32-bit DB2 client to connect to 64-bit DB2 database. In Oracle also you use lib32 libraries to connect to Oracle database from DataStage. Hope it helps....... How is that possible? We should connect through a 64 bit client to 64 bit ser...

But why is it that only before and after job script fails. If the DB2 table is accessed by a DS job, it does not fail? I am not able to understand this.

Btw, the script used is a Korn Shell Script and the DataStage server is on Unix. We connect through Windows

Recently, I worked on a project in my organization, in which we removed all such before job and after job scripts from DS jobs(server as well as PX), which were loading a DB2 table. The reason for this we were told that we were going in for a DB2 upgrade from 32 bit to 64 bit. So if there is a befor...