DSXchange

Variable names beginning with "$" are not supported. To extract the value of an environment variable job parameter call DSGetParamInfo() with InfoType argument DSJ.PARAMVALUE.

Test the value of ErrCode after DSSetParam() returns. A negative integer indicates a problem of some kind.

You have a data type CHAR in your data, which DataStage has padded with the default string pad character 0x00 because of how the environment variable APT_STRING_PADCHAR has been set.

Either change the data type to VARCHAR and trim it, or specify " " as the pad character for CHAR data type.

Welcome aboard.

Please tell us how your Aggregator stage properties are set up, and how the input data are partitioned and sorted.

Welcome aboard.

Use a job sequence. Have an Execute Command activity execute the find command. Its output is available through an activity variable that can be interrogated in downstream activities.

Don't forget to code for the possibility that the file is not found at all.

Make the key column nullable.

"Key" here does not mean primary key, it means "search key" and will return a NULL if the lookup fails. So it has to be nullable.

Local message handlers are in the msh files. Global (named) message handlers are in the directory Arnd mentioned. You can migrate the files - they are pure text. The main issue is getting the correct msh file into the correct job SC directory on the target. I believe istool is better at picking thes...

UniVerse - and therefore DataStage server jobs - use a base date (day 0) of 1967-12-31.

Delete and re-populate.

Please wrap your "ASCII art" in Code tags. It makes it easy to read.

(1) Yes.
(2) Which part of "internally" is unclear?

Have DataStage create the XML files that Maximo consumes.

You need to generate a row to have DataStage trigger the insert. Unless you want to generate a dummy column that will also be inserted, I feel it's just as easy to generate the date. You MUST have two jobs if you are using parallel jobs. Blocking operations (writing to and reading from the same stag...

Welcome aboard.

The error has come from the Teradata MLoad stage, in particular from the script that it has generated. Please verify that all settings in this stage are correct.

Neither - it's the handle to the job, allocated by an earlier DSAttachJob() call.

I have one customer using only server jobs (multi-instance, admittedly) to process HUGE volumes of data in near real time. They also use row buffering to great advantage. Server jobs will not be going away, for several reasons foremost among which is that sequences are server jobs. Another set of re...