DSXchange

If you need a 'complex join' - whatever you consider that to be - then you need a complex join. Perhaps the 'logic' that would help would be a better understanding of the source database, your query may not need to be as complex as you think it does. Or perhaps you can break it up into logical separ...

AKUMAR21 wrote:Simply because using transformer is a costly process eating up a lot of resources and should only be selected for mutlipurpose utility

As noted, this information is out-of-date with the advent of the 7.5 version of PX.

How about you post the actual error rather than some made up abbreviated version? I'm supposed to run all the 25 jobs in parallel. Thats the business requirement. Cant change that Baloney. What would 'the business' say if that's not physically possible given the constraints of your system? I would c...

Curious which way worked for you - the pipe or the $Counter? And please mark this as Resolved now.

Then you want one loop, not two. And since (AFAIK) you can't iterate through linked lists of variables, you'll need to build your single list with both pieces. For example, the List Loop: Monday|01,Tuesday|02 Then use the Field() function to split around the pipe for each parameter value. Now, since...

Sounds to me like you should run fewer jobs at the same time.

Read the plug-in Installation and Configuration guide. Then make sure you have added all of the appropriate values to the dsenv file and that all are correct.

If you still have a problem after that, we can start with all of the 'post your dsenv file' shenanigans.

Looks like it's time to step in for Ray and asked you to mark this one as Resolved.

Depends. With a single table, no. With multiple tables where the column names are unique, no.

This morning it looks unresolved. [shrug] You've marked this as a 'TX' job and posted in the Server forum. Doesn't matter per se if you are asking about a Sequence (no 'r') job but make sure you set that appropriately in the future. Can you explain what your design is meant to do in words please? Be...

Ok, fair enough. Let us know what you find on Monday.

The job design could be anything. It is the last thing that would matter. Because i have many jobs and am facing problems with all jobs with varying complexity. 'the last thing'? And we would know this how? The fact that you are 'facings problems with all jobs with varying complexity' is a fact you...

That's the question - and the answer will drive your solution.

dsjob -lprojects

Vincent has blogged on the history of DataStage, he also does present and future. Keep in mind the present was 2006 when written.

http://blogs.ittoolbox.com/bi/websphere ... -past-8819

I assume there was a 1.0 version at some point, I got involved when 3.0 was the hot new product.