DSXchange

There is a separate CD for installation on UNIX. You need to obtain this from your DataStage vendor (or from Ascential if you are a DataStage vendor). There are separate CDs for the different flavours of UNIX (for example, Solaris, HP-UX, AIX, etc.) so make sure you order the correct one. Also make ...

Yeah, me too. Hence the [8D] - alas, the software moved it onto a line by itself, so it wasn't so obviously related to the text.

That can be a vital piece of knowledge for those on UNIX, particularly for things like cd &PH& ("escaping" the ampersand characters so that you don't go starting erroneous background processes. An alternative is to enclose the entire filename in "hard quotes" (single quote characters), for example c...

The required date format is the same as the one you would use in a manual INSERT statement.

This almost certainly means that the Informix database was created without logging, and therefore cannot accept COMMIT statements.
Create the database WITH logging, and the problem should go away.

Backslash followed by another character has a special meaning to the DOS shell. For example n is a newline, t is a horizontal tab. For this reason, the special construct means "a single backslash". It you don't do this, the shell will attempt to treat the backslash and following character as special...

On the other hand, you sometimes do want to be selective on values in the multi-valued fields, by adding WHEN clauses to the retrieval criteria. It's a matter of what you really need brought forward into your DataStage job. DataStage can handle multi-valued columns; it's then a case of whether the E...

There is no limit on the number of stages in a job. There is a limit on the number of links that a stage can handle; this varies between stages types and is a set of properties of the stage type. Best practice, on the other hand, dictates that you keep your jobs as simple as possible, and document t...

It's a warning in the Version Control manual that you must make sure that all the environment variables needed to execute the job in the PX environment are also promoted to the other project. These environment variables for PX mainly have names beginning with "APT_"; you can read about them in the P...

Sequential files can only be processed sequentially. What this means in practice is that you must read past every byte in the file to get to the next byte. You cannot ignore columns in a sequential file; but you can discard them in a following Transformer stage. The same is true of other stream-type...

The second argument to TRIM is the character to remove. You were asking to remove leading, trailing and multiple "R" characters! D'oh! Good that you have something working. I usually prefer to check for single space character as well, for example: If Trim(link.column) > " " Then link.column Else ...

The error was not in the Transformer stage (whose code you are inspecting from RT_BP1143) but, rather, in the subroutines DSD.Startup and DSD.WriteLog, both of which are part of DataStage and whose source code, therefore, you don't have. Do you keep your log files regularly purged? DSD.WriteLog (fai...

The error message says it all. Either the parameter name, or the value you are providing via resolving the parameter name, fails to satisfy the criteria indicated in the message. These rules are suggestive of the ODBC naming rules; it seems that the process that imports stored procedure definitions ...

Alternatively you CAN use Fmt() if you prefer (I always say if you can't think of at least two ways of doing something with DataStage BASIC, you're not thinking hard enough!). In your case, the expression 0 + Fmt(12.1234567, "20R4") would do the trick. The format specification dictates a field 20 ch...

I'd suggest, based on your recent posts, that attending the DataStage Essentials class (DS314Svr) would prove beneficial. There is a section in that class on handling dates. As with any other database, you can only compare apples with apples. The result of an Oconv function is always a string. That ...