DSXchange

Ask your architect for proof of the assertion, preferably with a reference to some reputable documentation.

Please explain the logic that would yield your expected result. I can't figure out a single rule based on your example.

ERRORLEVEL is a shell variable that reports the success or otherwise of a command. Immediately after the dsjob command completes issue the command A value of 0 indicates success, any other value indicates a problem.

This is standard Windows shell programming technique.

Yes, because the Char data type exactly describes the fixed width fields.

Read the Programmer's Guide, in which there are examples of how to use the classes in the DataStage API.

You can have any stages you like downstream of the reject link (therefore you don't need another job). If you don't need the successful lookups, run them into a Copy stage that has no output links.

What is the value of ERRORLEVEL after the dsjob command?

Oops! Char(32) is space. (Craig's mixing it up with its hex representation 0x20, which you might use in APT_STRING_PADCHAR environment variable.)

If, on the other hand, you ask whether it is possible legally to change the value of a job parameter once the job is running, the answer is no. Therefore, you can safely assume that the job parameter value will have the same value when the job finishes as it had when the job started.

Use a reject link on the Lookup stage to capture the rejects.

How @FM is represented depends entirely on the viewer that you happen to be using. In many utilities it displays as the Icelandic thorn character. It may be displayed as an open rectangle, or a filled rectangle, or anything else, but it's always the same single-byte value on the server.

Please review this important information regarding the IBM Professional Certification Testing Policy. In order to ensure the validity and integrity of the IBM Certification Program, testing data and results are randomly audited. All test takers are required to agree to a confidentiality statement wh...

Start by checking your metadata to ensure that CuSTID is present (and correctly cased) everywhere it's needed.

Version upgrades are free if you're paying for support. And imho you'd be crazy not to pay for support.

While you're writing the v8 one, please check that the registry keys are correct. I suspect these will have been "blue washed".