DSXchange

Right click on the red expression and choose "Validate Derivation" from the menu; the expression editor will tell you what it thinks is wrong with the syntax - for example field and link names are case sensitive. Maybe you mis-spelled "Count" as "Cont".

A couple of weeks is NOT enough to make any comments about stability.

That claim was also made in 1999, so that COBOL programmers commanded huge prices preparing for the Year 2K squib.

What do you infer from "waitForWriteSignal"?

If you're using an ODBC Connector you can change the properties so that metadata mismatches cause Warning rather than Failure.

Manually for me too, after performing a Usage Analysis so that I can recompile any jobs that use the Parameter Set once changed. (This is one of the few times we compile in production, and it requires an extra step in the approvals processes.)

You could try using a Modify stage. Every specification in a Modify stage can be a job parameter.

Still a few sites left using mainframe jobs here and there around the world.

I'm not at a DataStage machine at the moment, but I seem to recall there's a parameter in uvconfig relating to handling of the Euro character.

... with just a little added complexity if your definition of "does not have a value" includes the possibility of NULL.

There are no mainframe jobs in version 11.3. There are mainframe jobs in version 9.1.

Then I can only suggest that it was not done properly. Or perhaps you also have to configure access to the Scheduling Service on Windows (on the Engine machine).

Meanwhile you can query the DS_JOBOBJECTS records for that particular job number. SELECT * FROM DS_JOBOBJECTS WHERE JOBIDNO = (SELECT JOBNO FROM DS_JOBS WHERE NAME = '<<Job name>>') AND EVAL "@RECORD" LIKE '%<<string>>%'; This query can be run from a dssh shell or, if you have DataStage Ad...

Check with IBM Support. Engine tier installation should include a product selection window.

Does the rexec session require a password? Authentication key?