DSXchange

DataStage is not a reporting tool. Use a reporting tool for this task. Sure you could do it, with an Aggregator, a Sort and a Head stage (to suggest one method), but you really need to get your head around using the right tool for the right job. If you don't, "they" will be requiring you t...

chulett wrote:Still curious why the perceived need to update environment variables... to what purpose?

Curiosity exterminated the Dalek's cat.

Unable to reproduce this. What error message obtains? Have the routines been made "read only" in the 7.5 system?

It's done through the Web console for Information Server, Administration tab.

Tip: Administering through groups is much easier to maintain.

If it's exactly four times you could simply emplace four Job activities in the sequence. Otherwise your list needs to be more complex, for example "A1|A2|A3|A4,B1|B2|B3|B4,C1|C2|C3|C4,D1|D2|D3|D4", and decomposed within the loop, probably using Field() functions. $Counter will be "A1...

The fix to your parallel routine is trivial - you declared the function DSSetEnvVar to return an int result, but you never actually invoked the function. There is no function for setting an environment variable from DataStage BASIC, but you can execute the TCL command ENV SET name=value or an equiva...

Is the table partitioned?

Stop fretting that you are getting multiple values for single records (which is the "more than 80,000 records" being manifested). Imagine the left input has 80,000 records and the right input has two, with the same reference key. An inner join would be expected to return 160,000 values (re...

IN the server job you will need an interlude function to the DSSetUserStatus() routine.

Use slname.$Counter as the invocation ID, where slname is the name of the Start Loop activity.

Would it not have been easier to use Convert() to remove the "." character?

You don't actually seem to have invoked the DSSetEnvVar() function.

Remember that NAME is the name of an environment variable, while $NAME is a reference to the value of the environment variable. The GetEnvironment() function needs to be told the name of the environment variable from which it is expected to retrieve the value.

Can you find it in the Stage Types branch of your Repository, specifically \Stage Types\Parallel\Database folder?

Life isn't that simple. There will be system table entries (at the very least in UV.ACCOUNT and UV_SCHEMA) about which to be concerned. Existence of the project will also be recorded in the unified metadata repository (XMETA).