DSXchange

Extract -----> Sort -----> Aggregator -----> Sort -----> Tail -----> Load The first sort allows the Aggregator to use Sort mode; it sorts by the grouping keys. The second sort sorts by the grouping keys (sort mode = "don't sort (already sorted)" then by the count/sum in descending order. The Tail s...

You CAN copy the Data Sets, even though just copying the ".ds" file isn't how it's done. You can use the Data Set Management GUI (available from Designer, Manager or Director Tools menu) or the orchadmin command from the command line.

Range lookup is available in version 8.0.

I disagree about Usage Analysis, provided that you have been meticulous with your table definitions and not broken the nexus between the table definition in the repository and the Job(s) in which it has been used.

As others have noted, this is not an ETL task, and therefore DataStage is not the correct tool. Whatever tool you used to develop the logical model ought to have the capability to create a physical model, and to generate DDL from that. If not, find a tool that can, such as ERwin, ER/Studio, Rational...

The same way you'd reset a sequence from any other client application.

Perhaps use the "after SQL" in a job that does something else or, better, in a job that does nothing else. Then you can call the job ResetSequencexxxxxx as appropriate.

Define "batch" in your context.

2B or not 2B, that is the question...

JB Watson (vice president of IBM) asserted - I think it was in 1952 or thereabouts - that the world market for computers seemed to be "about five".

The { 0d } reported is a single carriage return character (Char(13), or Ctrl-M). That is, in this row there's a single carriage return character in this field. You need to handle that situation. Did the file come from a Windows source?

As far as I am aware there is nothing in DataStage that generates anything called "dbx". Check with your DB2 DBA whether there are dbx processes generated by that software. The bounce problem may have been a network port issue - did you check the output of netstat to see whether any process still ha...

... unless you have an Australian accent, in which case "to die" is the day between yesterday and tomorrow.

That would be the support organization who supplied the EPM components, presumably your PeopleSoft vendor.

The early Prime machines' disk drives came in 80MB (five 14 inch platters), 300MB (nineteen 14 inch platters) and 600MB (sealed). You had to undertake weight training before you could change packs in the 300MB drives. And on the very rare occasions they crashed, the noise was spectacular!!

Why not use a Link Partitioner feeding multiple database stages, rather than a loop?