DSXchange

Status 2 (finished (see log)) is not counted as a failure. It is not handled by the Exception Handler. Therefore you need to code your own design. What do you want to do in these cases? One suggestion is to set up each Job Activity with multiple Triggers. OK and Warning go through an Any sequencer a...

If you enrol in the training classes - some of which can be delivered electronically - you get proper training manuals, with worked examples. I personally believe that instructor led training is preferable for DataStage, since you can get immediate feedback if you begin to do anything that won't wor...

Your SQL query includes a correlated subquery; that's probably the main culprit. Correlated subqueries must be executed for every row of the outer query; you are executing 380001 queries in the database. Create a job that runs this query into a Peek stage, and time just the query. Seek ways to write...

There are two main differences, and probably some minor ones as well. The two main differences are as follows. The Filter stage can send one input row to more than one output link. The Switch stage can not - the C switch construct has an implicit break in every case . The Switch stage is limited to ...

There's always the BASIC Transformer stage - acceptable in this case because the Sequential File target has to be sequential anyway, so collection of the Data Set must occur. The BASIC Transformer stage could have its "abort after rows" property set to 1.

It's not that simple. (It never is.) Your job designs need to be constructed so that they preserve enough knowledge to be able to restart, maybe even to restart part way through. This necessarily involves landing that information to disk, and it needs to be available everywhere (perhaps a File Set w...

Thanks, Daniel. I should have thought to ask about operating system patches - these are the bane of any programmer's existence, particularly when "they" move or rename libraries on which one's code depends.

RT_SCTEMP is a directory in the project in which various files used by PX reside, primarily the named pipe (or "fifo") files used for communication. Check that you have read, write and execute access to the RT_SCTEMP directory. Check that the command for creating named pipes (either mknod or mkfifo ...

Any time "check project is installed correctly" pops up, suspect that the repository indices have become out of date, and DS.REINDEX ALL.

Are any warning messages in the DataStage job log? For example, the parent directory of rb_tmu may not be in your PATH environment variable. Check the second logged event for the job to see the values that were assigned to environment variables.

Luk wrote:is it possible to get column names autoamaticaly (without writing their names manualy from keyboard)??

In a Pivot stage, there is no legal way. Unless you know how to extract column names from the metadata in the Repository, there is no available mechanism.

Maybe it's just your typing, but 20041231 is not a valid date (in ANY format), which might explain why you're having a problem. Certainly you can convert a valid date in YYYYMMDD format into internal format using Iconv(TheDate, "DYMD") , and convert this into any required external ...

What stage type are you using? Have you set the Data Element for the JOIN_DATE column? Is it generated or user-written SQL? What is the data type of both columns? Did you import the table definition and use the imported table definition? All of these factors affect the answer.

I also was surprised at the report of an empty "from previous run..." event, but let it go through to the catcher. But it is why I suggested explicitly looking in &PH&.

I never guarantee that it will be there - always use words like "may" or "should", because sometimes it's not there. Are there any preceding warnings? Is there anything to be found for this run in the &PH& directory (a subdirectory in your project) pertinent to the failure?