DSXchange

I'm not sure how the pipe plays a role here - do you want to reject rows where a given column has more than 2 decimal places or is there more involved?

At the beginning of the job log the environment variables are listed. What is your value for NLS_LANG. In this case the warning is because the two don't match, but as NLS_LANG is used by Oracle you can deprecate the warning to an informational message by using the message handler. It would be best t...

What if you try the select on just one column, PSD_STR_ID, do you get the same error?

Can you post the select statement (and tell us which DB you are using ODBC to go to). Are there any data types or sizes that aren't common?

That message is usually seen when you have an Oracle stage in the job - is that the case?

After the job aborts with 139, do a reset in the director and see if you get a message titled "From previous run..."

Yes, but you can use the CHAR() function and drop the multibyte character.

Nope, those are your two options - FTP stage or shelling out somewhere to execute a script that uses FTP commands. If you have scp enable then you can do the transfer all on one line without a script.

2ksaint - you need to tell DataStage the correct encoding that is being used by the file.

Please try using the "code" tags to make the program legible. I would suggest that you put "PRINT" statements in to ensure that the values are as you expect before the IF-THEN-ELSE parts.

I played around in Server and had the same issues with the characters in the upper range of ASCII. Have you tried to see what happens when the FTP program takes care of the conversion from EBCDIC to ASCII - it might handle the characters appropriately. Finally, you might have to revert to what Phil ...

code page 874 is Thai. Either set your current client to that page, or you might try to edit the .dsx and change the codepage to 1252 in the header. But that might cause some issues if you used Thai characters in the jobs.

Do you have a SELECT clause? If yes, does it return data when used in your favorite SQL tool? What happens if you run the job instead of using view-data?

Umm, I already apologized once...

Oopsie, thanks for correcting me. UNIX "diff" is your friend here.