DSXchange

There were vague mentions of a "DataStage lite" (their spelling) at last year's IOD conference. That's all I have. Don't ask.

7.5.anything where anything does not include "x" is a UNIX release. It's also a Windows release, but one that does not support compilation or execution of parallel jobs (though they can be designed). You would be very lucky to get Information Server on a DVD. IBM has a strong preference to...

A sequence.

A sequencer only makes an "any" or "all" decision about whether its inputs have fired. It's a component in a sequence.

"Supplied keys"? Supplied how (in a generic design)?

Every active stage has three phases of execution: "startup", "per row" and "shutdown". Operations like "truncate" or "clear" occur during the startup phase - you wouldn't really want them done per row, would you?!! The usual solution is two jobs, as ...

Routines are executed synchronously in the same process as the sequence itself. That is, the sequence waits for a routine to finish before moving on to any other activity.

Placing the routines in separate sequences obviates that wait in the master sequence.

No.

ASCII stops at 127.

ISO8859-1 (sometimes called "extended ASCII") stops at 255.

There is therefore no "ASCII equivalent" to ┐ character.

Do you have NLS enabled?

You may be able to fix it. Did the disk where the project is become full at any point? Take an operating system level backup of the DS_JOBOBJECTS directory and its contents. cp -ipr DS_JOBOBJECTS DS_JOBOBJECTS.BAK Run fixtool on DS_JOBOBJECTS. $DSHOME/bin/fixtool -file DS_JOBOBJECTS assuming that yo...

g++34, it turns out, is the 3.4 version of the compiler.

AHA!!!!! For some reason changes wrought in the Administrator client are (silently) not being saved in the DSParams file, even though I am the owner of that file with rwx access. Making the changes to DSParams using vi resolved the compilation problem. Now I have a different problem to look at, why ...

A curious development. Having struck this exact same problem, and searched to here to find the solution, I check in /usr/bin only to find the following: [DSEngine]$ ls -l /usr/bin/g++* -rwxr-xr-x 4 root root 221736 Apr 15 2008 /usr/bin/g++ -rwxr-xr-x 3 root root 103344 Aug 23 2006 /usr/bin/g++34 [DS...

A curious development. Having struck this exact same problem, and searched to here to find the solution, I check in /usr/bin only to find the following: [DSEngine]$ ls -l /usr/bin/g++* -rwxr-xr-x 4 root root 221736 Apr 15 2008 /usr/bin/g++ -rwxr-xr-x 3 root root 103344 Aug 23 2006 /usr/bin/g++34 [DS...

All calls through the UV and ODBC stages use BCI functions under the covers. The uvodbc.config file tells whether it is a UniVerse or an ODBC data source - in the former case it is not necessary to use an ODBC driver because the process is already connected to the "UniVerse" database. Only...

Please post the complete log message so we can get a better handle on the "it" that is logging the warning.

Please post the complete log message so we can get a better handle on the "it" that is logging the warning.