DSXchange

Similar, but not the same. C arrays depend on knowing the address in memory of each element. Dynamic arrays are navigated based on the character position in the string with respect to the beginning of the string (which, yes, is a position in memory, but not one that's stored as a pointer anywhere) (...

kumar_s wrote:

ray.wurlod wrote:I suspect kumar_s meant "linking" rather than "liking".

Problem with Keyboard and Chair.
Ray, You could have used atleast LoL emoticons.

Why? It was a serious observation (not a criticism).

DS_AUDIT preserves all history of modification, unless the component is actually deleted and re-created (exported and re-imported).

Server or Parallel?

The answer is different depending on job type.

Please post in the correct forum.

Your question will be answered when it appears on the Server or Parallel forum.

What is the NAME of the output file in your Survive stage? Can you use find on the server to see whether it exists anywhere there?

What check boxes did you check on the job run?

Did you do what I asked?

It's not a C array. It's a DataStage dynamic array, which is nothing more than a delimited string. The delimiter character is a "field mark" character, which is accessible as the system variable @FM.

Write the routine as a transform function; it can then be run from its Test grid. But some level of management supervision is still required to prevent misuse.

Yes it does.

Entire partitioning? With 16-way parallelism that would mean you're moving (16 * 1.22) MB of data.

You really haven't provided enough information for good diagnosis. Dump the score and post that.

A Sequential File stage supports parallel execution when reading multiple files. If you have only one File property and have not selected multiple readers per node, the parallel option will be disabled.

This is not a DataStage limit, but an operating system limit on the number of subdirectories in a directory. On Solaris, for example, it's 32K. Each job creates up to eight subdirectories, but more usually six or seven. Assuming eight, that's a limit of about 4K jobs on Solaris. For ease of manageme...

Put a big, brighty-coloured annotation on it

I'm working on this.
DO NOT change it!

If you set the Null Field Value property to "" you will get adjacent delimiters in your output file.

It's not normal. Can't say if you're doing something wrong because I don't know what you're doing. What other load exists on the machine? Is the Data Set being accessed by another job at the same time?