DSXchange

Craig - you gave away the secret

I wrote a test job, simple row generator -> BASIC transform -> Peek and used the value of the parameter as the output row value from the BASIC transform. When calling up with multiple instances I have absolutely no issues and the values are correct and as expected.

I wrote a test job, simple row generator -> BASIC transform -> Peek and used the value of the parameter as the output row value from the BASIC transform. When calling up with multiple instances I have absolutely no issues and the values are correct and as expected.

That is a downside of the modify operator in that it doesn't allow such nested functions.

Mark at least two projects as protected. Execute the numeric values should be the same for the two or more protected projects and different for the non-protected ones. Is that the case?

What both Ray and I are driving at is that the BASIC stage has no "memory" of past instance values. If the value used in the run is different from what is passed into the job at runtime then you have most likely hard-coded it somewhere. Does this mean that if you call your job 3 times, the...

StringToTimestamp(DSLink316.DATE[1,10]:' ':DSLink316.DATE[12,12],"%yyyy-%mm-%dd %hh:%nn:%ss.3")

Ok, then could you show what your actual output is and what you expect for some example row?

In the case where you think that the stage is getting the wrong parameter, go to your job log and check the 1st entry for that run to make 100% sure that you are actually using the value you expect.

Since you are working with X(10) fixed with character, there is no pad character used anywhere, likewise your SELECT won't return any values since you are using just the 2 characters. I am not sure if DB2 Char(10) means 10x 1byte or 10 unicode characters. You have 10 bytes in your source. The initia...

Just add it to your job parameters, then change the runtime value from the default of "false" to "true".

koolsun85 - the execute command stage is very simple and well documented. Perhaps you could try to use it and, if you have problems, you could post specific questions to this thread.

If you think about it, having 8 processes on an 8 CPU system might not really be using the CPU capacity of the machine, since much process time is spent in "wait" states (waiting for data from input or for output data to be confirmed, or for disk I/O or database I/O to complete), so in som...

If you turn on OSH_PRINT_SCHEMAS and check your log entry, you might find that the schema going between the link contains a VarChar() instead of your expected Char() field, which would explain part of the problem. Does your schema leading out of your transform stage have the field(s) in question as ...

I think that the document is misleading and using "partition" when it should be using "nodes". While the number of parititions that data is distributed into is equal to the number of nodes, the driver is the number of nodes in the configuration file.