DSXchange

Nsg wrote: if sorted data is input to aggregator / funnel / join / merge stage, will the output data from these stages be also sorted ?a

Yes. Per node. Provided conditions are met such as Sort mode for Aggregator, Sort mode for Funnel.

In UNIX use dsjob -jobinfo command. This reports about five lines of information including the start and end timestamps. You can parse these with UNIX commands such as grep and cut.

This makes them "subsequently created" jobs.

I assume you are using ODBC as the data connection. Have you imported the table definition from Excel? Tip: you must check the "include system tables" option.

Sort and partition by F_N. In stage variables: Map ID to svID if element_name is "ID" otherwise leave svID untouched. svID <== If InLink.element_name = "ID" Then InLink.ID Else svID Map Name to svName if element_name is "Name" otherwise leave svName untouched. Map Value...

The -domain option must name the machine on which the services tier is installed (and listening on port #9080).

So run the legal XML through one of the "pretty print" utilities. DataStage is an ETL tool.

Welcome aboard. If you have another table-importing product in the suite, such as Information Analyzer or DataStage or Data Architect then, yes, you can create mappings using those shared table definitions directly. That's one of the reasons for having a common metadata repository; ease of collabora...

Can you please post what the "resolution" is? My point made earlier is that you should NOT remove the newline, at least not without the customer's approval - it's part of the data. So you have to find a mechanism for loading the data in which any character is legitimate. I suspect you've u...

Feeling mellow. Went to awesome CS&N concert last night.

Welcome aboard.

You can't do that with DataStage.

You might try creating the large file then using a UNIX command like split to break it up. This will work even though you are executing on a Windows server - every DataStage installation has MKS Toolkit (UNIX emulator).

Look at the option for preserving data type in the Aggregator stage.

You can do this using log-interrogation functions DSGetNewestLogId(), DSGetLogSummary() and DSGetLogDetail() - these names may not be totally correct (I'm not using DataStage at the moment).

One...

Two...

Many...

LOTS!!!

You might also consider changing the Sequential File stage to use DOS style record delimiter string.