DSXchange

Welcome aboard! :D
At a guess, you lack write permission in the folder for your output file from the STAN

An extra button on the Columns tab in all passive stage types that allows the columns in the grid to be resynchronized against the table definition in the Repository from which they were drawn. This would be useful, for example, after changes to data type, precision, scale, etc. Name changes are per...

Fewer rows in the same amount of time means a lower rate of rows per second.
The first stage constraints its input, so that fewer rows are output.
It's simple arithmetic. Don't worry about it. Rows/sec is fairly meaningless as a general indicator of performance in any case.

Now show us with dscmdexport command. This is the command about which it is asserted that individual jobs can not be exported, not dsexport.

Export, then conduct a search on the export file. It's ugly, but it's about all you've got. You (they?) have failed to maintain the linkages upon which Usage Analysis relies. You could, of course, search DS_JOBOBJECTS, looking for an OLETYPE of SeqInput or SeqOutput. But that won't help you to find ...

Found it! The problem is the mixed case table name. UniVerse (DataStage) puts the quotes on when there's a non-all-upper-case name. This also occurs through the Command window of the Administrator client. Can't find a solution using COUNT verb, but you can use quoted identifiers in SQL. For example ...

Alas there are no silver bullets. You need to analyze what the job is doing and find the hot spots (that is, those parts of the job that consume the most resources). Capturing performance statistics (see Tracing tab in Job Run Options dialog) can help here. Closing the Director and not showing perfo...

removes all non-numeric characters. Beware that this will remove any sign from the number.

The Transformer stage uses non-SQL pattern matching. Read about pattern matching in the on-line help or the DataStage BASIC manual. Example: inlink.Desc Matches "...T..." (the three dots is a wildcard matching any number of characters) inlink.ProdCode Matches "2A3N..." (ProdCode must begin with two ...

Yes.

Even faster would be to use sequential files for staging.

Do all your validation checking within DataStage.

Because you're using fixed width, the representation of NULL will differ in different columns (since it has to be the same width as the column). In the Columns grid you can specify column-specific representations of NULL; scroll right until you find it.

Yes, provided your metadata management has been disciplined and you have table definitions in the Repository for these sequential files and that the linkages between these and the jobs that used them have not been broken, then you can use Usage Analysis in the Manager client.

Where's the error? You have posted two informational messages.

Command = "COUNT " : Arg1 Call DSExecute("UV", Command, Output, Code) Call DSLogInfo("Command = ": Command, "CountHashedFile") Call DSLogInfo("Output = " : Quote(Output) : @FM : "Code = " : Code, "CountHash...

But you can't do it with the client-based dscmdexport command. If you disagree with that assertion, please supply the method.