DSXchange

An error status from an 'After Job' subroutine will only log a warning.

Confusing. Why don't you have a 'good solution' for inserts? There is an 'Insert' action that just does that and should be what you are using. And you need to do something to 'pre-qualify' each record so you know which link it needs to go down and that is typically done via a hashed file lookup.

Because that is the only column marked as a Key, so it must be used in the 'WHERE' clause. And your SQL is incorrect in spite of the fact that it 'works'. You should remove the AND JOB_NAME = '#JobName#' part as that should be in the Key Expression of your lookup link. And I'll bet it already is or ...

You don't want to 'release' jobs. Use Version Control, it is built into the promotion process.

As noted several times now, all you should have to do is compile the 'ExecuteSQL' routine. Please make sure you do that before we go around in any more circles.

Ex: If 1 sequence had total 6 subsequences but 4,5 subsequences are failed So,while restarting I need to excutre that 4&5 only. How can i do that Not only must your 'sub' sequence jobs be restartable but your main sequence job must be as well. And any checkpointed Sequence must have aborted to ...

Is there any way to abort the sequence if any of the job activities finish with warnings! The answer depends on your version of DataStage. For 7.5.x all you have to do enable the option to 'Automatically handle activities that fail'. If all you have is an 'OK (Conditional)' trigger then anything ot...

Do you know the maximum number of values you could receive in one string? Your example shows 8 for example.

That would be the CLICK PACK, Ray.

Basically - RTI allows you to deploy your ETL jobs *as* web services. The PACK allows an ETL job to *call* a web service.

You're correct in your conversion of the timestamp. What makes you think it is in any way related to your constraint violation problem? You need to look at the definition of the constraint being violated - like ETQ.PK_VALIDATION_VALUES for example - and see what field(s) make up that constraint. All...

They are always necessary. So, you good now?

Where are your parameter markers? It is expecting as many bind variables as you have columns in the stage when the job runs.

With generated sql, yes, it wants an ISO standard value: YYYY-MM-DD. And there's only about a billion posts on this, including multiple versions of my standard rant on the subject.

I should write a frelling FRAQ.

There are also some recent posts on developerWorks regarding dynamic configurations in a GRID environment, from what I recall. Just checked and they are here with a nice explanation from Patrick (Danny?) Owen at IBM, along with a mention of the "the internal software we have that is only availabe th...