DSXchange

No.

The philosophy of DataStage is one stage type, one task.

If you want to aggregate, use an Aggregator stage.

Welcome aboard.

This smacks of a poorly expressed interview question. The short answer is that there is not enough information. What is the record structure in each case?

You need to have the data sorted on Id, ID1 and Csid for the Remove Duplicates.

If you sort on Id, Eff_Date, ID1 and Csid your data will still be sorted on Id, ID1 and Csid. Ditto if you sort on Id, ID1, Csid and Eff_Date.

What happens if you convert each field to decimal using StringToDecimal() function then multiply the two together into an output field that has a scale of 3?

3) Change your expectations based on more knowledge - specifically that no rows can come out of the Sort stage till all rows have arrived into the stage.

I want to join three inputs on the same key using the Join stage with a Left Outer Join. If the key is not found in the intermediate link, will the data still be found on the right link? Scenario: File Key Value Left 1 One Left 2 Two Left 3 Three Intermediate 1 a Intermediate 3 c Right 1 x Right 2 ...

The number of nodes is determined absolutely by the number of node names in a syntactically valid parallel execution configuration file. As noted, a node is a logical construct, associated with a set of resources available when execution occurs on that node. So, if the job is run using a configurati...

If the Engine tier is UNIX, as you have marked your post, there is no telnet service. If the Engine tier is Windows, the telnet service exists because, historically, Windows did not have a telnet server - could not accept telnet connections. DataStage itself does not use the telnet service at all. I...

Assuming that you use an Execute Command activity to cat the file, bringing it into memory as a delimited string, for example using cat #dirpath#/#filename# | tr '\n' '\|' then you can use Field() functions in your User Variables activity to segregate the pipe delimited fields that were the lines of...

Then go with my other suggestion.

My point is that the partitioning is driven by the raw (binary) values.

Welcome aboard. That style of looping is available in version 8.5. In earlier versions the easiest approach is to re-parse the comma delimited field into separate fields (perhaps using Column Import stage) then Pivot.

There's no limit in DataStage.

There IS a limit imposed by the resources that the server(s) on which DataStage is running can deliver.

That's because a database connection does not exist. Maybe all available connections are in use, maybe the connection is not properly configured. It's up to you (maybe with DBA help) to determine why a database connection does not exist.

Do you have parallel (Enterprise Edition) installed? If so you can use UNIX commands on Windows. Otherwise you can create an after-job subroutine in DataStage BASIC that opens file using OpenSeq, uses the Status statement to determine the file size, closes the file then deletes the same if the size ...