DSXchange

The message suggests that there's more data in your line than is described by your record schema - don't be locked in by the fact that it's reporting on the final column - that's only where it found the problem by parsing all the previous columns. You need to check every field to make sure that none...

Have you made sure that "a column that contains the repetition path is set as key in the output link table definition." ?

It's the same in all editions. Check the checkbox in the job sequence's job properties. While there, click Help to see what effect this will have.

You are aware that you can not have weeks numbered 0 through 53 ? You are also aware, I trust, that the last week of your year will be a short week, so that your end users can not legitimately "roll up" on weeks? The point about WEEK.TAG is that every week has seven days, so that "roll up" is a mean...

It would appear that such may be the case.

Shane is correct. A lookup in a server job is automatically a left outer join if the Transformer output is unconstrained. It returns NULL for every column on the reference input link (including the key column(s)) if the lookup fails. You don't even have to "set" the null - it already happens.

Is this a parallel job or a server job? You specified "parallel" as the job type but posted in the server forum. Last time I responded to this question I said you would need to determine your business rule as to the definition of week #1 in any calendar year. It is not sufficient to state "is not gi...

poornimajayan wrote: I found the same Que posted earlier for which Ray replied like --"Verify that you are a member of the Administrators group for that machine (i.e. not from the domain)."

That was NOT about installing on Vista.

BASIC Transformer stage can be used in MPP environments, but only in a node pool that contains only the node on which the DataStage server is installed (usually but not necessarily the conductor node).

Welcome aboard. :D Parallel routines (callable from parallel Transformer stage) must be written in C++. This stage type does not support DataStage BASIC routines. In any version of DataStage. If you want to call a BASIC routine you need a BASIC Transformer stage. But this, too, has its downsides (Se...

As it tells you: "Add an index option or drop indexes". Have you left the Index option as "Maintenance" or changed it?

I think you'll find that the key is J\1515\V0S47, not J\1515\V0547. The "J" indicates that the object being referred to is in a job, rather than in a shared container (type "C"). "V" is "view" (effectively a Designer palette picture) and "S" is stage. "V0" is the base view (the job itself) while hig...

I reckon that would work.

No. Helper subroutines have names beginning with "DSR_". Most of the ones you have cited are specific routines exposed by passive stages for fulfil the generic tasks (like "get", "get by key" and "put") that can be requested by active stage types. The "$" prefix indicates that they are written in C,...