DSXchange

Your mail adminstrators look after lists. They may or may not have configured your email server to allow you to create your own lists.

Your understanding about the automatic distribution via a list is correct.

Conversion raw to ustring has to be specified as an explicit conversion function RawToString()?

What is the data type of the incoming field? For example if it is int32 or decimal, you don't need to check - it can not but be numeric.

LittelTony wrote:For all the jobs we've to count all the stages that are without comment.

This could be performed with a query against DS_JOBOBJECTS table where DSRID is of the form VnSm. This restricts the query to stages.

But every pin (link end) also has documentation. Do you need to worry about these too?

It does restrict sorting to sequential if you include only one node in the sort pool as you have done.

The default conductor node is the first-named node that is in the default node pool. In your case this is node node1 because you have all nodes in the default node pool.

Have you read the Release Notes for 8.7? They include "what's new in this release". They're available from IBM Information Center for InfoSphere Information Server version 8.7

Without knowing your exact configuration it's impossible to say, but most stage types are forwards compatible. So my guess is "yes". What should happen is that your DRS stage will be converted to a DRS Connector.

Without knowing your exact configuration it's impossible to say, but most stage types are forwards compatible. So my guess is "yes".

@FM is not a function - it is a system variable, and is preloaded with the ASCII code 254. Historically, in the UniVerse database, this character is the principal delimiter in a special kind of delimited string called a "dynamic array". Since DataStage was originally built on UniVerse, @FM...

What's different between DEV and QA?

Until we know that, there's not a lot we can advise.

Assuming that the list of addressees and CC addressees will be fairly static, create that list in your mail server and send to the list.

What does "not working" mean?

What's different between DEV and QA? (Hint: "nothing" is not the correct answer.)

It was certainly true when the CFF stage first appeared that only one ODO clause was supported. We would need to trawl through release notes for later versions to get a definitive answer unless it's somewhere in a recent manual.

Send to an email list that has direct and CC addresses in it.

Other than in the first two rows your example does not appear to be doing what you describe. Can you please clarify? In general DataStage does not have a lookahead capability; you may need to design to update the first row (of each pair?) subsequently.