DSXchange

command: source
parameter: cd #pathname# && ls -1|grep "xyz"|sort -u -r -t"." +5|head -1

command: cd pathname && ls -1|grep "xyz"|sort -u -r -t"." +5|head -1
parameter:etl/source/data

ODBC standards specify yyyy-mm-dd as the required format for dates. Try supplying your date in that format, rather than mm/dd/yyyy.

Did you read the link the Craig suggested (though that resulted from a search on function call is illegal at this point).

WHY is Sequential File stage not reading the compressed file? What error message is generated? What record schema are you using?

Have you considered using a Filter command (uncompress filename.Z) in the Sequential File stage?

The Sequential File stage that writes the file will have Format properties that specify fixed width. The data types will not include VarChar (or any other variable-width data type). You may, therefore, need an intermediate Copy, Modify or Transformer stage to map the column data types.

Each partition has a pointer to the string, which happens to be stored in the same location in shared memory in an SMP environment. Therefore the pointers on each partition happen to be identical. In an MPP/grid environment each partition has a pointer to the string (in memory, in a virtual Data Set...

What I had in mind was a Cycle with only one value, and that a job parameter (but I'm not 100% sure you can do that). But you could certainly generate a constant Char(1) value of "X" and join that to a single row virtual Data Set keyed by "X" and containing the job parameter value, probably created ...

quiztime wrote:The the lookup used to run at 10000 rows per second on the Test server and suddenly started running at 350 rows per second FOR THE SAME DATA - yes we are rerunning identical data.

What changed? "Nothing" is not correct answer. Something changed on the system somewhere.

When you run the job enable stage tracing on the Transformer stage, and capture performance statistics. These are logged as a tab-delimited report in a log entry; copy it from there and paste it into Excel. The two time columns (Minimum and Average) are in microseconds. Add a column that is Count x ...

What stage type? What are the data types of each column? Have you used data elements for any of the columns?

I prefer to maintain separate uvodbc.config files per project. That way the development project can not "accidentally" see production DSNs (and vice versa).

Welcome aboard. You need to determine how "high values" is stored. If, for example, the database uses the high bit set and all other bits reset in the matissa, this would be interpreted as the decimal value -0.00. DataStage is clever enough to ignore the sign of "minus zero". Another possibility is ...

Wasn't Windows 95 supposed to ship in 1995 and Windows 98 in 1998?

Wasn't the next version of the SQL CAE Access Group standard for SQL supposed to come out in 1998?

There is ALWAYS partitioning. Even if it's done logically using shared memory. Which only happens in the case of the Entire algorithm. (Auto) will apply Entire if on the reference input link of a Lookup stage. The reason that Entire is the default is that, no matter on which processing node a key fr...