DSXchange

Even though it's Windows, you might also try using forward slashes.

Would you mind informing us how you resolved this?

Maybe also an input text override to pick up the RICAHRD token and replace it with RICHARD as its standardized form?

Good, that's one possibility eliminated. Now check your 9.x rule set as per my second question.

I've never seen that, but I've not played much with version 9 (only 8 and 11 of late).

The full version, to replace every occurrence, would have the form

The full version, to replace every occurrence, would have the form

Did you have any overrides in your v8.1 rule set?
You also need to find out why ROAD was classed as V in your v9.1 rule set. Again, do you have any overrides, particularly classification overrides?

It's probably sufficient to select "Procedure status to link" on the output link from the Stored Procedure stage. ProcCode and ProcMess are ordinarily automatically mapped to the output link when you do this, though you can remove them, for example if you were only interested in ProcCode.

It's probably the missing quotes, as Craig noted. If not, please also provide the error message that gets generated.

You could try switching the order of the input links to the stage.

Typically you map input columns to the stage onto IN and INOUT parameters, and output columns from the stage onto INOUT and OUT parameters.

Actually the documentation on the XML Output stage is fairly comprehensive.

Just out of curiosity, why did this particular task have to be done with a stored procedure? There's a perfectly adequate pair of functions in DataStage for obtaining the weekday of the current date. Also review the "%eeee" and "%eee" format strings.

How did you insert the job parameter reference into the stage (manually, or using the Insert Job Parameter tool)?