DSXchange

Report a bug in the version 8 client to your support provider. It works fine in version 7.5.2.

NULL will be dropped because you can not transfer NULL into a not null field in DataStage. And primary key columns are ALWAYS not null. You need to intercept the null farther upstream in your job and direct it into an ODBC table. However, null primary key will not be allowed there either.

Did you reset the job, as I asked? How many messages were logged by the reset run?

OK, scrub it.

Yes it's possible. Open the stage properties, select the Inputs tab, select the Partitioning tab. Choose the partitioning algorithm from the drop-down list. On the Outputs tab you can set the Preserve Partitioning flag.

I got the feeling that what was required was a function with a repeatable algorithm. Yes this could be done with a string key and generated sequence column.

Try relying upon Runtime Column Propagation. You will, of course, need to specify the join key, so that may limit your flexibility somewhat.

What you are seeking to write is the first half of a hashing algorithm. There's nothing out of the box in DataStage. But you could write your own. CRC32() is dangerous with large volumes, as it carries approximately a one in four million chance of generating the same value for two different inputs. ...

Source code for the Stages is IBM proprietary information (intellectual property). Similarly source code for Orchestrate operators and APT classes is IBM intellectual property. None of it is in the public domain. If you look in $PXHOME/include you will encounter header files that will get you most o...

Go back to the machine where the routines were created and export them again, this time checking the Source Code box. Without that the source code is not exported, so you import only executable code.

Lookup against the hashed file and construct D then write back to the hashed file.
Disable both read cache and write cache, and lock for update when performing the lookup.

What is your jo design intended to do? Are there any business rules that have been implemented and which therefore need to be tested? Create a test plan, including test data with which to test the efficacy or otherwise of your implementation of those business rules.

Get the fixed widths RIGHT.

Curiously I answered the wrong question, yet the issue is now marked as resolved. What I advised was how to unprotect a project. Re-reading the original question, what I should have answered was how to change a job's status from readonly. That can be determined via a Search on READONLY. However, the...

That's not the same warning as your original post. Is it the same job?

Did you reset the job, as I asked? How many messages were logged by the reset run?