DSXchange

Seems pretty straight-forward to me. The failure trigger on the FTP stage fires when that job fails - the first time, the third time, anytime it fails. How is it supposed to know that you only really want it to pay attention after three trips around the block? Change your logic around. Exit from the...

how can i do this ? Start by reading the replies already posted, your basic solution is there. If what you have just added is the 'else abort the job' part, then you'll need to clarify some things. First, what exact version of DataStage 7.x do you have? Exception handling in Sequencers changed sign...

They just swapped out 'Ascential' for 'IBM WebSphere' in all the names. You can find out the latest availability information here:

http://www.ascential.com/eservice/produ ... ability.do

No, you've got it right.

Doh... at first I thought you meant 'Guinea' as in pig, but had checked that before posting. Finally dawned on me I was closer to Warlord than to Wurlod.

Sorry about that Chief... corrected.

dspxlearn - Please don't hijack other peoples threads. If you've got an new question, start a new post. Ken, agree on your 'point of style'. Was primarily looking for a clarification / confirmation on how the stage actually works as I don't have access to a PX server. Just have a Ray Wurlod Guinea ...

Instantly costs extra.

ray.wurlod wrote:Ah, introspection. Or is it introrogation?

Introrogation? Nice play on words there, Mr Ray.

kduke wrote:I would think it probably needs to be

Ans = Trim(Output<1>)

Agree.

I don't recall the 'reject method' causing any warnings. It will rather happily process any records that fail the metadata check into oblivion without raising any kind of a fuss.

Perhaps it's only after you actually setup a reject link? In this case, it doesn't sound like that would be needed.

Do you really need to do that in PX? The metadata won't match for the header and trailer records (assuming you are using the metadata from the detail records) so the Sequential stage should automatically 'reject' those two... right?

Sure you can, now that 'hanging links' are allowed it is fairly straight-forward. While technically you don't determine the attachment point you can control the execution order by connecting them back in the desired order. It also (typically) has the added bonus of making the 'visual order' match th...

... or I was going to say the one that lives between the keyboard and the chair. Wetware based.

"Self?" I said...

Set a job parameter that is the number of rows to skip during the load. Default it to zero. Put a constraint in that says, in essence:

@INROWNUM > JOB_PARAMETER

Set it to 50000 and rerun. Note that there is a little bit more to it than that, but that is the gist of it.