DSXchange

Or you can set that in the start of your shell script.

Check whether you have the dir.

Check whether you have the permission. You need to be the root user.

I am not asking you to verify anything in the DataStage job. What I am trying to convey is that there may be some environment values set in the session where the script was successfully run and tested which are now missing in the DataStage session's environment. But before you start changing anythin...

Check whether the shell variable uses / assumes any environment variable(s).

You may also have to set the commit size.

Search the forum for more info.

The idea is very good.

You may also need to ensure dates are converted correctly in source and target.

You need to check the values being stored in hash file. Especially, check the format of date you are passing in.

I have tried it and it works. Can you please let me know your job design and the error you received.

You need to do a
sort -t"," -k4,7 <filename>

Try deleting the hash-file and create it fresh or use a different hash file (name).

Try to isolate lookup to confirm its working.

If you are happy to have the fields retain their length, you can write as a fixed width file and read as a single column file delimited by some char not found in the file.

Did you check whether the rows are inserted in SQL Server for table1? How are you doing the lookup? Are you referencing from SQL Server or writing to an interim hash-file? In general, I think it is because your insert in source is not committed till the end and hence you are not able to see the chan...

What is your column delimiter?

That is an AS/400 DB2 error message.

Go into a search engine like google and try to locate it. One search returned the following.

http://networking.ittoolbox.com/groups/ ... font=fixed