DSXchange

Who woulda thunk it!

Please mark the post as Resolved using the button at the top of the screen.

I don't want to use a "Look Up" to know if the row i want to update exists in the table because of the performances. That's what hashed files exist for. They are the heart and soul of the Server product. Done properly, there's no performance penalty. So i would like to know if it's possible to disa...

What he means is it won't stop you from doing it, will not abort, but rather will just trash the sequential file.

From the Administrator or TCL prompt: CLEAR.FILE HashedFileName works for an account based hashed file. Pathed file? Delete it from the O/S.

A couple of tips...

Always 'Preview' your posts so you know what they will look like.

Next time you have this problem, enable the 'Disable Smilies in this post' option.

So... do we have to guess why the job aborted?

Sounds just like this problem:

http://www.dsxchange.com/viewtopic.php?t=123054

How strange. Exactly the same but for the column name.

Ok, however you marked your DataStage Release as 8x so that's why I answered as I did. Why not go to Ken's website and get it from there directly? From what I recall:

http://www.kennethbland.com

If you are asking if you can clear job logs from the UNIX command line, the answer is no. Best to get your Auto Purge settings right and let that happen automatically.

That's how the split command works, it adds a suffix to whatever filename you tell it to use. So, for you, leave the extension off of the split output filename and then add it back on after the split is complete.

:? There's no "then" in a constraint expression as expressions just evaluate to true or false. A "then" only has a place in an assignment, something you would use in a derivation. That's not correct - not sure what Craig was thinking at the time. Maybe this. The IF expression must have both a THEN ...

Please mark the topic as Resolved using the button at the top of the page.

Which is exactly what the Pivot stage does. Don't confuse "key" with "index" or "primary key" or anything of that ilk. For the Pivot stage, you mark as "Key" the base column(s) that should be included in every row it pivots out. This is all documented in the pivot.pdf manual in your Docs directory. ...

There's no such thing as an "indirect" load. There is either a direct load (DIRECT=TRUE) or a conventional load (DIRECT=FALSE) and only the conventional load support commits.

Yes. Sequential files by their very sequential nature can support multiple readers but only one writer process. This is not a "DataStage issue", they have worked that way since they first crawled out of the primordial muck. Write to two files.