DSXchange

ray.wurlod wrote:Even if it doesn't annoy moderators, it will definitely annoy me!

We know, we know.

Too bad there's no Moderator here or I'd move this dang post. What's so hard about putting them in the right place, peoples?

Why specifically "Orchestrate"? At a high level it's the underpinnings of the parallel engine, a product that was aquired from Torrent Systems in 2001. If you are new to DataStage, first order of business would be the guides that ship with the product, for example the Parallel Job Develope...

Nope, it's simply the fact that all colums in the stage must be bound into the query. Each must mention all four, so if you don't want to update all fields you'll need to pre-qualify your actions and use two separate links.

priyadarshikunal wrote:But still there is no answer to the question asked in first post as it is.

Ah... but there is, and it has been answered.

I'm trying to help you help us and all you've done is repeat yourself. Have you considered the fact that perhaps posting the actual error message you are receiving might help?

Still, doesn't matter. Having an "identity column" (or any other surrogate value) with a 3 in it doesn't make it "the third row". It's not sequential media, after all. That's not to say that based on very specific conditions and/or sort orders, you couldn't identify the third rec...

Define "not working".

Technically, your first question is irrelevant.

It's a trick question!

mczern wrote:I would have thought this would be a fairly common use for the looping construct.

Yah... not so much.

I'm not quite sure why you added your question at the end of a completely unrelated post, regardless here you are split out into your very own.

Turn off buffering.

viewtopic.php?t=141746

Either do the 'max key' work in the current job or a separate followup job, I would consel against the 'after job routine' approach.

Split from this five year old topic.

I for one have no clue. All the docs mention is actions being "logged" which I assume means the job's log. Why not ping your official support provider, let us know what you find out?