DSXchange

Look in the job log to verify that the SQL statement that you think is being execute is, indeed, the one that is being executed. Sometimes they get changed in minor ways.

They're called Reject links in server job Transformer stages, and you can have more than one and, conditionally or unconditionally, they handle any row that has not been processed by a prior output. I might get a few spare cycles later in the week to test the parallel Transformer stage. But don't ho...

Create a Parameter Set (separate from the job). In the Parametet Set create the three parameter names, just as you would in a job. Create two "values files". Put the values into these values files (easiest for you is manually in the Parameter Set dialog). Add the Parameter Set to your job....

Could you enclose the whole thing in single quotes, since it contains double quotes?

That might be it, but I doubt it given the Template situation.

Could it be that the "too long" length was over 255 characters all up?

Use a UNIX (= MKS Toolkit) command such as ls -1 filepattern | wc -l

If doing this in a routine, call using DSExecute. Don't forget to lose the line terminator character, perhaps using Oconv(Result,"MCN") to achieve that.

Go to IOD conferences. You get to talk to the horse directly.

The fact that you don't see one doesn't mean that there isn't one. Do some research. Ask an expert.

What you are trying to do can not be done out-of-the-box. You need some kind of "rules dispatcher" routine that could be called from the Transformer stage. This would parse the logic expression and give effect to the logic.

Probably. But they're wrong. The new environment is a service-oriented architecture, whereas the old environment did not have a services layer between the client and the repository. Also the respository is using a different database. There's a couple of differences to start with.

It's always connected (via services) to XMETA. Your Information Server roles and DataStage credentials are stored in XMETA - you could not log in were they not there.

That means that your installation was performed by someone competent, who converted &PH& to Type 19 in the Template from which projects are created.

None is mandatory. Several are highly recommended, however.

Why not convert the @FM characters to commas? Then you would have a comma-delimited string that could be processed by the StartLoop activity.