DSXchange

Search would be a good idea. There are very few reasons why an operating system file (in this case RT_CONFIG20857) can not be created. In summary they are (a) permissions, (b) disk full, (c) disk quota exceeded or (d) limit on number of subdirectories in a directory exceeded. Do you really have mor...

It is because DataStage Designer can not communicate with the performance monitor application (a separate Java application) that the row counts are unable to be displayed in Designer. If you set the indicated environment variable to the location of PXEngine, then DataStage Designer will be able to f...

Do you have NLS enabled? Can you create a job that generates the code point for those particular characters, using the Seq() function? Put strings containing those characters in a file, and view the result of the function. Curiously, I note that neither Char() nor Seq() is mentioned in the Appendix ...

Have you done any QualityStage training. It requires the result of a Match in order to do Survivorship.

You could profitably have posted this question in the QualityStage forum.

And "" is not a possible value for a Char(3) column. A Char(3) column must have precisely three characters, or be null. (If one or more of the characters is 0x00 then the field can appear to be shorter, but this is merely an artifact of how C handles strings.)

What do you mean by "(hex)" in the original question?

What makes you think that you'll get a performance boost? Indeed, how do you define "performance" in such a vague context. You certainly get a functionality boost - quite a few new toys and a common Repository that can be shared (to some extent) with other tools. Therefore arguably there is a potent...

Prayer is apparently beneficial.

They are somewimes written to the scratch disk defined in your configuration file for the node in question.

Only by checking for existence of the value within your DataStage job.

The one without the "$" character is a "regular" job parameter. The one with the "$" character is a job parameter that is a reference to the environment variable called PARAM1.

You might consider using server jobs, or parallel jobs with a low degree of parallelism, to keep the startup time as short as possible. Another possibility is an "always running" job using WISD to publish your DataStage job as a web service that the Perl application could invoke. In this case startu...

The second person personal pronoun in English is spelled "you", not "u".

The error is actually thrown by APT_CombinedOperatorController - you have no idea which stage is to blame. That's why we rarely attempt to diagnose errors from this operator. It may even be that the heap problems come from an inserted tsort operator.

Answers to all of these can be found using Search