DSXchange

Please post this question in the Parallel Extender forum.
Someone who lurks there may have an answer.
It's more likely to be possible in PX than the "not at all" in server jobs!

No they're not. Spaces are not permitted in stage names and link names.

You can organize for default values to be set in the target database itself. Every column definition is able to have a DEFAULT clause. Other than that, if the column is updated by DataStage, then DataStage must generate a value with which to update that column. It doesn't matter what you do or how y...

The ABAP code is sent to SAP R/3 either via FTP or via RFC. You get the choice.

ABAP code is, as far as I am aware, regenerated each time the job is run, so your question about "promoting it" is moot.

What do you mean by "real time"? Yes, you can use stored procedures, subject to some restrictions (for example the SP must process a record set). The stored procedure definition must first be imported into the DataStage Repository (so that DataStage can check that the correct number of arguments is ...

This has always been tricky. The only time I've seen this actually working was on Notes version 4.?, with a user ID that had an empty password. Most Notes administrators won't allow this.

Link Collector requires row buffering enabled.

(You can know this because of the call to ipcopen() in the error message - ipc is "inter process communication".) Also, it's in the manual.

Prevention is better than cure. If you begin by preparing the metadata (in this case importing the table definitions) then metadata mismatches ought never to occur. In practice they can under controlled circumstances, such as importing using ODBC stage then using the table definitions in an OCI stag...

A Job Sequence is a graphical way to design what ends up being a job control routine, so ultimately they're the same thing. In fact you can view the generated job control code (in the Job Properties window) after you have compiled a job sequence. Triggers are a means whereby conditional dependency i...

From the Parallel Job Developer's Guide:
The modify stage alters the record schema of its input data set. The modified data set is then output. You can drop or keep columns from the schema, or change the type of a column. (Emphasis mine.)

The format may not be wrong. For example, 20041010 can be interpreted as April 20, 1010 if the second argument to Iconv is "DDMY". Iconv() can be extremely flexible about how a string can be interpreted as a date. This is fully described at Date Conversion Demystified under the Iconv section.

The word "subsequently" in my earlier post was intentional. You can't determine the final number of rows (lines in a file) until it's completely loaded. This means that you would not use DSGetLinkInfo() in a Transformer stage. Two reasons; the current count increments for every row processed, and it...

If all your DataStage developers have the same primary group, the setgid bit ought not to be required.

Recommended umask is 002. This means that everyone in the same group as the user who creates an object (such as an RT_CONFIGxxx file) will have all access to that object. Permissions on the VOC file should be -rw-rw-r-- for similar reasons. Permissions on the project directory should be drwxrwxr-x w...

Remove them when importing the table definitions is best. Otherwise it's a manual process or a hack of an export file.

Some stage types allow you to specify qualified or unqualified table names when importing. Choose unqualified if that's your need.