DSXchange

Yes, you would have to do the check on the DataStage server, not your local PC. That or transfer the file to your PC and then check it there. Going to take a wild guess here that you have not removed the double-quotes in the file and they are causing your trigger expression to fail. Change the trim...

Lost on what your problem is. You've told it to "clear the table" every time the job runs and it will do that regardless of the state of your source, zero records or not. First empty the table then start loading records. Is that really what you want to be doing? :? Are you trying to find a...

Go out to a DOS prompt (Start / Run / cmd) and then execute that same type command. If you've made the proper change to the file, it should output:

UnMatched

-not-

"UnMatched"

OK, that's good and what it should have shown. Your trigger condition looks fine, too. You have that in a link between the Command and Notification stages? Seems to me that should work fine, or at least trigger an attempt to send the email. Hmmm... maybe try trimming the output as well: Trim(Convert...

Post the Execute Command stage's log entry, the one that shows it being executed and what the output was.

Come on, this isn't all that difficult or complex. The command is literally "type" and that's what you put there, the four letters t-y-p-e. Simple as that. And then the full pathname to your file, which can go into the Parameters box or right after the type command, doesn't matter since yo...

No, the Command is "type" and the Parameter box should hold the filename.

Switch to "ExecSH" and you'd have a better ability to answer to your question. The "silent" version is really meant for operations where you don't want to expose sensitive information like passwords.

No, it doesn't need to be a batch file.

chulett wrote:Use the Execute Command stage to "type <filename>"

More than one way to do this. One DOS solution would be to write the condition to a file, "matched" or "not matched". Use the Execute Command stage to "type <filename>" and then the trigger to the Email stage would be something like: Convert(@FM,"",StageName.$...

Have the job populate a flat file when the data is 'unmatched'. A Sequence job can then check the file and, if populated, send an email.

This help at all?

http://www-01.ibm.com/support/docview.w ... wg21320296

As far as I recall, yes. Have you tried it yet?

You may be thinking of a Server reject link where it logs a warning at the end of the run with a count of the rejected records.

Isn't there an option in the Remove Duplicates stage to 'retain last'?