DSXchange

You might need some small changes for Parameter Sets and Connectors.

That's OK - for new people we understand it can be bewildering (for experienced posters we get a bit more harsh!). This forum (General) is for when you don't know where to post a question. The moderator may "relocate" this thread to the forum (Enterprise Edition) that is specifically for parallel jo...

"" is not valid as a Decimal data type. You are supplying "" and asking for it to be treated as Decimal. This is neither permitted nor possible.

Depends. How much caffeine do you have on board?

Put a Column Generator on each input to the join stage, in each of which you generate the same constant (a cycle with only one value). Use that as the join key.

No. DataStage generates decimal numbers with leading and trailing zeroes as specified by the precision and scale. Remember, too, that text files do not really have data types - everything in them is "string" or "text". So changing your metadata is, in this case, slightly more correct from a technica...

It is resolved in version 8. You must have MQ client (obviously), but the MQ server no longer needs to be co-located with the DataStage server.

As the others have said, your user ID (nor any group of which it is a member) does not have write permission to the project directory on the server. Gaining that permission is the only solution to this particular problem.

Multiple segments can occur when a segment reaches 2GB (not the case here) or when a Data Set is appended to. The former case allows Data Sets to exist on operating systems that impose a 2GB maximum file size limit.

You have to click Apply to get anything saved. I would recommend editing the table definition in the Repository to add the Occurs value, and then to load the table definition into your job from there. You might also try editing the column definition on the other end (the passive stage end) of its li...

Since it's in a job sequence, making use of the test command in an Execute Command activity is a convenient way to check for existence and/or size of a file. On Windows it's marginally more indirect - you can use DIR command in your Execute Command activity and parse the result using an expression b...

Just as a test, try using a Failure trigger (this can be a separate trigger from your custom trigger, and can lead nowhere, for example into a sequencer) - it is the existence of explicit failure handling that overrides automatic error handling.

There are some things one does not need to know. ....There are some things one does not need, or even bother, to know. There are no such things in this world to be as no-need-to-know things but are things which are least importantly to be known mainly which are according to who sees its importance ...

In version 6 DSAttachJob() incorporates the functionality of DSLockJob().

As a general principle, change only one thing at a time, and test it.
If it doesn't work, your search for the cause is far smaller.