DSXchange

It's a bit of a kluge, but the following will work. Stage variable svStringValue contains the raw result of the DFloatToStringNoExp() function. svStringValue <== DFloatToStringNoExp(InLink.TheDecimal) Field(svStringValue, ".", 1, 1) : "." : Left(Field(svStringValue, "."...

Shut down DataStage and perform a normal system backup.
Restart DataStage and export each project. (This will be the source for most of the restores you need.)

Nothing of DataStage is stored outside the file system.

Note that backup/restore becomes way more complex when you move to version 8.

As far as I am aware there is no such document, probably because there are far too many variables. As a rule of thumb, construct classes of job. For example, jobs that extract to or load from a staging area performing little or no transformation should, if the metadata are available, be able to be d...

Yes, cleaning &PH& still helps in version 8.1 and 8.5. Job processes redirect stdout and stderr into a file in &PH&. (Some other files, like admin captures and stage trace files, are also captured into &PH&.) When a job starts it has to scan past all the entries in &PH&am...

If you make changes from the Administrator client that affect DSParams (such as log purge settings, environment variables), DSParams is deleted and re-written.

Double in, VarChar out, no conversion function. What happens then?

These are being sorted correctly, on two nodes. You will notice two sorted sub-lists. If you need to sort across the entire data, run the whole thing on one node or in sequential mode.

name1=value1
name2=value2
name3=value3

That is, one name/value pair per line. No -param at all.

What happens if you just allow an implicit conversion to occur?

Routines are separately-callable components - so the answer to your question is "yes". Manuals are the DataStage Programmer's Guide and the DataStage BASIC manual.

Probably not. Provided that the reader can keep up with the writer, the size of the pipe should be largely immaterial. Your default (5120 bytes) means that that many bytes would fill the pipe if the reader stopped. As a general rule you want to know about that fairly quickly.

How (by what method) is the Oracle table partitioned?

Execute the ${DSHOME}/dsenv script. Make sure that APT_ORCHHOME is correctly set (to the PXEngine directory).

The backquote characters are an essential part of the syntax.