DSXchange

In such a case, I think the best you can do to remove the warning is to introduce a new column (eg: diff_val_new) in the before link that has the same data as diff_val and pass it to the output. The same resolution will hold true for any other column on which the warning is seen. The problem with th...

Check if RCP is enabled in the job, if yes then disable it and run the job and verify if the warning still exists

Try using loop variables (if you are on 8.5 or above version of datastage) in the transformer stage to get the required output

Request for the passwords from the previous vendor

Check if there is any special character in the key value on which the data is being sorted

From the error message, it is clear that the input data from After link is not sorted. Before passing the data to the Difference stage, sort the data (preferably using sort stage)

Either use a execute command activity and get the current date OR If you want to use only user variable activity then try something with Oconv,Iconv

Oconv((Iconv(datehere,"D-YMD[4,2,2]")) ,"D-YMD[4,2,2]")

That should get you the date in the yyyy-mm-dd format.

I had a bad experience in extracting data from SAP BW Open Hub 4.3.2.1. Let me share my experience with you first :) It started with spending lots of time just setting up the open hubs,process chains and source system.Once the connection was setup properly, the next problem arose on extracting data ...

How are you passing columns via shell script? Also how is the shell script being executed in the job (I am assuming you are using Before Job Subroutine)?

Still no resolution found...this thread is very interesting

In your job, in the before job sub routine - use Execsh and try to echo the parameter value. Verify if the value has any spaces, extra characters etc. It could be possible that the connection information is being passed incorrectly by the sequence to the job. Also, by connection information - Is it ...

Please let us know if there are any parameter values being passed from the sequence to the job and their data types as well

In case of fatal errors, the status code is 3 which is correct.

Check in the datastage job log if there are really any fatal errors.
Also, run the dsjob command directly on the server and then use "echo $?" to check for exact status code.

Prefer AIX

Check the character set for the column , if its LATIN - change it to UNICODE and then verify again