DSXchange

So why is this topic marked as "Not resolved but there is a workaround" - are we done discussing it? You've gotten everything you need from it? Ray's answer isn't any kind of a "workaround", it is one of the resolutions to your question.

In the source data this column equals 100600 In other words 100600.00 is what it sees coming in. And then you "pack it" and you end up with exactly the same output (as you should) - essentially it writes it out with the assumed decimal removed, i.e. as 10060000 which is why the View Data ...

I don't think it's related at all but why don't you give it a shot and let us know?

It's a BASIC Server function so not valid in a Parallel job unless you use it from the BASIC Transformer and understand all that brings along with it.

Why is your Job Type set to Parallel? I'm going to fix that in your first post and move this to the proper forum.

The dssearch command comes to mind. An exact search here for it should turn up conversations to that effect.

I was under the impression that MKS was out of the picture in the newer versions so perhaps the zip it was using is just what is built into Windows, the so-called 'compressed folders'?

What are your auto purge settings for the job?

Go me!

What parameter type? One that allows nulls?

You probably need to use the optional second argument of "allow8bits" for those functions to work properly with that value. Also wondering if there is a DB2 function equivalent to the Oracle DUMP function to get you the value via SQL.

It needs to be identified, not guessed at. Do you have a way to get its actual value, perhaps by writing it to a file? Then a hex editor (or an octal dump on UNIX) would tell you what it is.

For example: Generating surrogate keys.

Please tell us how this relates to DataStage and why you think you need to convert this and why it needs to happen via a shell script. Will this file be consumed by a DataStage job? At some point we may need to talk about why you think iconv is not giving you "the desired output" as conver...

Looking up nzconvert says that it is used "to convert between any two encodings, between these encodings and UTF-8, and from UTF-32, UTF-16, or UTF-8 to NFC, for loading with the nzload command or external tables". So I would imagine the solution in DataStage would be to use the proper cha...