DSXchange

At least for testing add environment variable $LD_LIBRARY_PATH as a parameter to your job and make its default value the special token $UNSET.

Short answer is "no". But you DO need to specify how NULL will be represented in the text file. This can be done with a global property on the Format tab or differently for individual columns.

No.

The join won't be costly. It relies on the fact that its inputs are sorted not to be costly. "End of data" appearing on LN_PERSONAL will mean that the Join stage gets to close without doing anything.

Nothing of this kind exists.

Does not the -matches argument require a value?

The second error is being thrown by SQL Server, not by DataStage. Can you insert these long strings by any other means (for example manually)?

You could follow the Notification activity with a Terminator to force the sub-sequence to abort. But you don't really need to - the parent sequence can detect if a sub-sequence finished with warnings, and can (be programmed to) react accordingly.

No you don't. You don't need this at all. The problem with SELECT * is that it is dynamic; the number of columns returned will vary. Therefore it is not a routine for a beginner to create. Start with something simpler, and work up. What did you envisage doing with the results of this SQL in your rou...

Not natively in Windows, as far as I am aware.

If that's a valid license file, and you have correctly identified it to the installer, then it's time to contact your official support provider. They will help you to ascertain the reason why the license could not be applied. In the interim I suggest you research the Must Gather topic, since IBM sup...

IA jobs run as parallel jobs. Therefore the answer is "yes". Even better, apart from providing a valid configuration file, you don't have to do anything to take advantage of this functionality.

Yes. Click on Options folder, find Filter in available properties to add.

Yes. This character may be generated using the Char(0) function. You can trim these characters from your string. Problem is, you have to be able to read the string (the file) first, to do this in DataStage. You may find it easier to remove them with a tr command in a Filter command on your Sequentia...

It's still looking for the record delimiter specified in your metadata and not finding it. Rather than make it look further, why not check that your record delimiter (or record delimiter string) property is correctly set?

Does this happen every time you run the job, or has it occurred only once? If it has occurred only once, then you can safely ignore it. If it's every run, I would be investigating (probably with the orchadmin command) why this particular Data Set can not properly/fully be deleted. Presumably it's a ...