DSXchange

A Transformer stage in a parallel job generates C++ source code that has to be compiled and linked.

ODBC drivers ship with DataStage. They are in a directory called branded_odbc. You configure them the same way as you would on any other UNIX platform; that is, edit the $DSHOME/.odbc.ini file to create your DSNs and edit the uvodbc.config file in each project to determine which DSNs are to be visib...

Somewhere you are doing an AsInteger() function.

Not every 10-digit number can successfully be stored in an integer - the largest permissible int32 is 2147483647. It is the fact that you are being warned about.

How about using the wildcard as stdin for sed (so they work one at a time) and append-redirecting the output into your file? You could also parallelize the sed operations with a bit more scripting.

As they say in register arithmetic, "shift happens". The DS_AUDIT table keeps track of who deleted things. At least, it records the most recent deletion of various objects. Could it simply be that your repository indexes are out of date? Did you try reindexing before concluding that your jobs had be...

Read my post again. That's exactly what I found, which is why I suggested you contact your "official" support provider.

Well, there's some information there. The error code ought to make it possible to find some information in the Parallel Engine Message Reference manual. IIS = IBM Information Server DSEE = DataStage Enterprise Edition TFCM = class manager (I think) ... And that's where it all falls down. There are n...

The underlying architecture is that of the (new) service oriented architecture. Server jobs, as I understand matters, run in this environment (in order, for example, to use the metadata delivery service). That said, I have not yet had a play with version 8.0. It may be that the "traditional" reposit...

Welcome aboard. :D

There is not enough information in what you've posted. Please post the entire (detail) error message. In particular, we need to have some idea which stage type generated it. We then may have questions about the syntax you used within that stage.

In versions 7.5 and earlier, the server job runs as a server job. There is no "performance" difference if you happen to have Enterprise Edition (with server jobs licensed, of course). Server shared containers in parallel jobs will suffer the overheads of conversion to the "typeless" (DataStage BASIC...

That is not the score. Please provide the score, which is the only way to prove or disprove your earlier assertion.

For only three distinct values I would not bother with the Oracle table at all, unless the time ranges were likely to change - I'd just use a simple If..Then..Else construct.

Values that should be looked up successfully. Values that should fail to be looked up successfully (your job design appears simply to drop these - how will you reconcile row counts?). Null values in column(s) in the stream input used in the reference key expression. Rows that violate constraints in ...

I totally doubt that that is the case.
Post the score from the job so you can prove your assertion.

You could write an after-job subroutine to abort if the interim status is "has warning", but I'd prefer simply to detect the exit status in the job sequence itself, and make the decision there about whether to re-run J2. Use a Routine activity. FUNCTION TestJobStatus(TheJobName) $INCLUDE DSI...