DSXchange

dr.murthy, your question is not the same as the original, because they are on UNIX and you are on Windows. You really ought to have begun a new thread.

Welcome aboard. One of the things we can't deal with is "it doesn't work". You must be more specific. HOW doesn't it work? What were the expected and actual results? When you test the routine, does it generate the expected result? Certainly the $ReturnValue activity variable is the correct...

Did you deploy as "always running"? How many instances did you deploy?

It must be executed while attached to a project directory.

Possibly JobA finishes in less than one second. So they appear to start in the same clock second.

There are not. You install with, or you install without, NLS.

director.exe (on the client)

Try it.

Bonne chance!

Since you have version 8, you can use the resource estimator to indicate the likely resources to be consumed by each job. Then assemble them so that any dependencies are addressed, and the total demand for resources remains under 100% of available resources.

Search DSXchange for "The specified module could not be found." It's been addressed on a number of prior occasions.

No, just use the cat command as the Filter command of the Sequential File stage, which will then read the output of the cat command. Handle the column headings either in the Filter command (perhaps using head +2) or within your job. Use @OUTROWNUM to generate the line numbers.

Quality Stage US area rule set will do the same but you will need to customize the Rule Set because the data does not have a separator between tokens (words), so you will need to adjust the rule a little bit to parse this kind of record for you Not true. You can define the data to be fixed width an...

Add a new column to your input. This column has the same value, say "X", in every row. A Column Generator stage would be ideal. Create a Data Set containing pairs of values, "X" and a value, for example X,100; X,125; X,150 and so on up to the largest possible value. Permit duplic...

QualityStage has this functionality straight out of the box, and can handle misspelled entries as well. You would simply insert a standardization stage that uses the USAREA rule set into your job. If you don't have QualityStage licensed then the MatchField() function may stand you in good stead in s...

A good place to look would be the chapter on the modify operator in the Orchestrate Operators manual. This shows how the arguments to the Modify stage's string_trim() function work.