DSXchange

What are the permissions on dsjob.exe ?

Ah, I comprehend.

You've missed the vital step of publishing the results in IA. Once you've done this the information you want will appear in the Table Definition in DataStage.

So the burning questions are:

Which table definitions from the IA store?

How are they viewing the data in these tables?

Ultimately there's a java.lang.NullPointerException.

Report it to your official support provider who will help you to find out the solutions. The amount of Java in these clients makes diagnosis without the specialist tools and knowledge in the support group almost impossible.

There isn't, because Data Set Management uses a common dialog and that dialog remembers the most recently used directory path. Further, the same common dialog is used by other tools in the DataStage client suite (such as Configurations editor).

You could lodge an enhancement request.

Except when they're not, such as the Oracle OCI stage.

Build the whole entry as a single VarChar column including the linefeed characters. Write this to the Sequential File specifying no delimiter and no quote character. Ignore what View Data shows you - look at the actual file that gets generated.

To which configuration file are you referring? (There is more than one.)

When's the interview?

Or transport buffer size was somehow misconfigured.

Or use DataStage and declare the structure to be a single VarChar field with no quote character.

Now, what value is returned by each DSSetParam call?

I note in passing that there are "=" characters in the value of Value5 (you will need the fourth argument of the Field() function to be greater than 1 - any large number will do).

They're not stored in DataStage, so can't be accessed easily from there. Intermediate results are stored in IADB, final results are stored in XMETA. Use the reporting console to viewInformation Analyzer reports (which have to be created within IA).

Use either of the Key Management routines in the SDK.

Test the value of ErrCode after each call to DSSetParam(). I presume that hJob is the result of an earlier successful DSAttachJob() call - did you check that it was successful?