DSXchange

What if you were to change your job and all stages in it to UTF-8 to avoid convertions altogether, does the warning still appear?

Yes, so look for "BANANA " and/or " BANANA" to avoid that type of error.

p.s. Rob - I'm here because my compiles are taking 30 minutes or longer today

will return 0 if the string is not found, or a numeric start position.

Ok, what about looking at it differently. What should the string be after the date? It looks like it is garbled, with single-byte extended Latin characters instead of initial bytes of multibyte Chinese ones.

In the extended attribute for the string do you have "unicode" set?

Now add "APT_DISABLE_COMBINATION" to your job and set the value to "true" for one run and the warning will tell you the actual stage generating the message, please post that.

Please post your complete and unedited warning message.

The stage is not too much more than a front-end for the OS compression algorithm you choose, "compress" or "gzip"; you can read up on the differences between the two in the manpages. No stage that process column values will be able to process compressed data. Your sample data is ...

I've only used "test -s" in scripts and don't know how it can be used in a single command line to delete zero length files, which is why I reverted to the time-honored and much distinguished "find" command. Do you have an example of how to use "test" without writing or ...

Does that mean that the lookup works when it is not defined as sparse?

Which operator? (hint: post the full error message).

Except in this case the source is a sequential file.

Instead of complicated workaround, put in an after-job call to SH and execute "find . -name {YourFileName} -size 0 -exec rm -f {} \;" . I am sure that the real UNIX experts will suggest a more efifacious command, but this should work well enough.

This is tougher to do in PX than in server - I would use a server job, where missing columns at the end of a line can be handled automatically - a functionality not present in PX jobs. The Server job could read & reformat the file and then a PX job could do the real processing.

should suffice to see if any artefacts are left.