DSXchange

You'd have to explain what the heck "not working" means. Do you actually mean you can't compile a PX job with a transformer in it? If so, that requires an approved C++ compiler be installed and properly configured to work.

If they're all just using it for a lookup and not actually creating it each time, then no. What 'certain stages' does it not seem to be able to start?

The only place you'll find metrics from a previous run is in the job's log. What makes you sat there's "no information on the row count" there?

A search for 'DataStage architecture' turned up 30 matches, including this post in the FAQ forum. The Optimizing Performance chapter in the Server Job's Developer Guide pdf should help as well with understanding what's going on under the covers.

Are you trying to ask under what circumstances Entire partitioning would be appropriate to use?

So what's the DataStage equivalent of an Informatica 'workflow'? Job? Node?

Hmmm... I wonder which part of this puzzle constrains passwords to be 8 or fewer characters?

A date is a date, only date values in string fields have formats like you are showing. You can use "[]", the substring operators, to re-arrange the parts of those external dates or the StringToDate / DateToString functions.

You will first need to split up those "comma delimited columns" into individual columns first, but there are stages for that as well. You'll probably also need to constrain out any null values post pivot.

Use the Pivot stage. "Merging data from two or more columns to a single column" is exactly the same as "splitting into under same column multiple rows".

If you still have questions on your pivot question, post them in that thread.

You didn't get any reply from others? Seriously? Never mind the fact that you only wanted Ray to help you.

Come on, you can't just open up a single thread to play Twenty Questions.

1. Wherever you created the hashed file.

2. They don't really need to be 'kept' anywhere. I suspect you're referring to the 'DataStage Engine'.

Guessing it's not a 'union all' limitation but rather a length of the query limitation. Regardless, something like that should be asked of your official support provider.

Entire is entire just like it sounds, so your first paragraph is correct. I have no idea what you are asking in the second one, however.