DSXchange

U can ask ur DBAs to set up a federated database which will have version 8.2 pointing to the version 7.1.
DataStage can talk to the DB2 mainframe(v7.1) thru the federated database link set up on the AIX machine.
This way, u can have datastage pointing to version 8.2 all talk to 2 diff versions of DB2.

First, make sure the DB2 date is in a format of mm/dd/ccyy. Then in the transformer right before the load to SQL sever, use the following datatype in "data element" column: SQL.SMALLDATETIME. The length is 16 and display size is 19. using this datatype in the target column, will make ensur...

DB2 v8 u are talking about is the DB2 client on the Unix box. u will need a catalog entry on the UNIX box to the DB2 server on mainframe.
DB2 Connect is software that is designed to leverage your enterprise information no matter where it is stored.

Since u are reading COBOL output, u might be running into EBCDIC to ASCII conversion issues.

U could be having a memory leak when you're job is running and the operating system is issuing a hard kill when all the memory is chewed up by the datastage process. U shd monitor memory usage when ur job starts up.
As the others suggested, u shd contact IBM tech support and send them the job log.

We migrated from 7.0 to 7.5 successfully on 3 AIX machines and we did not face any issues. Since u are moving to 7.5, u might want to consider moving to 7.5.1A, which has all the fixes and patches applied. Most of holes and errors are fixed in 7.5.1A.

Nagesh To use the Enterprise stage of DB2, the DB2 source database shd be of enterprise edition. If it is not, then there is really no use of using it. U shd check with ur DB2 DBAs and see what version of DB2 u have. If u do have DB2 EE, then u shd definetly use the enterprise stage, which is a para...

Vinod U also need to be aware of the stage u are going to use to load data into SQL server -DRS stage or ODBC enterprise stage. There is a problem of memory leak with DRS stage and ODBC enterprise stage when u use data types of type timestamp and decimal. U will see this leak especially if u try to ...

Same here Ray, i do not have access to DS from home. I will research it tomorrow and get back to the group.

Thnx
Bindu

I did go back and run this job with a smaller sample of data (just 1 record) and i still get the size difference. after compressing white spaces the PX file is still bigger, but not twice as big when i started. Here are some of the differences i observed betn server and PX files: Char fields: Compre...

I have observed that a sequential file created with the same properties and same formats in PX and server have different output sizes. The size of the PX file is approx. double the size of the server seq. file. In my case, the server file size is approx. 40 Gig and the PX file size is approx. 80 Gig...

Try this. This works for us: .odbc.ini file entries ============== [<enter DataBaseName>] Driver=/usr/ascential/Ascential/DataStage/branded_odbc/lib/VMdb220.so Description=DataDirect 4.20 DB2 Wire Protocol D20ver Database=<enter DataBaseName> GrantAuthid=PUBLIC GrantExecute=1 IpAddress=<enter IP add...

If u are going to use the DB2/UDB plug-in, u do not need to make any entries in the .odbc.ini and unconfig files for the DB2 server u are accessing. All u need to do is catalog the DB2 instance on the AIX server. Whatever was suggested by "lstsaur" shd be sufficient to get u going. Bindu M...

U can build a FUNCTION like this and call it in ur transformer: i=1 Len1=Len(Arg1)+1 loop while(i<Len1) str1 = Iconv(Arg1[i,1],"MY") if(str1 NE '0D') Then Arg1[i,1] = Oconv(str1,"MY") End Else Arg1[i,1] = Oconv("20","MY") i=i+1 Arg1[i,1] = Oconv("20"...

One of your Sybase columns u are pulling is a VarChar field and it has a carriage return in it. U may have to write a small basic routine to convert it.

Bindu Madhav