DSXchange

deanwalker wrote:You can see that information in the RT_CONFIGnnn file, or export the executable and it is visible in the DSX too.

This is news to me. Can you please elaborate?

An alternative command is

You have not control over the file pattern, unless you can dream up a regular expression that assembles the file names in date order. Prefer a File property with a Filter command that issues a cat command to assemble the data in date order.

It's DataStage BASIC, not a shell script. Comments do not begin with "#" in DataStage BASIC. Comments in DataStage BASIC can be specified in three ways: a statement beginning with "*" and containing at least one space a statement beginning with "!" and containing at least one space a statement begin...

Beware that Modify stage uses zero-based counting. So, if you want the leftmost 100 characters, the Specification should be of the form

Group by Status summing Sal, then vertical pivot.

Ah, you didn't mention that you'd also specified it as a blocking field.

Calls to DSLogInfo() will serve in place of PRINT statements.

"Not working" is meaningless.

Is it compiling (which is the only thing I addressed)?

What do you want the routine to do, what is it producing (if anything)? What is appearing in the log (or in the Results window in the test grid)?

The Index() function may be faster. For example: If Index("8000,8100,8300,8301,8302,8400,8401,8402,8403,8404,8500,8520", InLink.col1, 1) Then "1100" Else ... That having been done, arrange the comparison string in order of likelihood of occurrence to get optimum speed of ...

The language is DataStage BASIC, not C. Therefore you must use BASIC-style comments, not C-style comments. The "/*" characters are the immediate cause of your failure to compile.

These do not have a regular/consistent row pattern, so you will need to figure out your own rules for parsing them. You can then implement these as a DataStage job, a DataStage routine (or more than one), some combination thereof, or a solution that does not involve DataStage at all. Begin by analys...

Welcome aboard.

It's not DataStage doing that, it's Outlook (or Outlook Express).

Use a different mail client (such as blat) to avoid it.

Welcome aboard.

DataStage does not "run" files. Do you mean "read" or do you mean "write"? By default each operation is sequential. However parallel reading is possible.

Parallel writing to one file is prohibited, not by DataStage but by the operating system.