DSXchange

The Notification Activity stage will include that information when you check the 'Include Job Status in email' option.

Thanks for posting the resolution to this.

There are no parameters inside those double-quotes, they make them a literal string. You'd need to build it in pieces, text and parameters separately and then concatenate things together. For example: Ans = DSSendMail("From:aaa.xxx.com\nTo:":#Recipients#:"\nSubject:Job Failure\nBody:H...

'Fetch' why, for what purpose?

That or add it to the table, apparently.

The uvodbc.config changes need to be made in the project.

Couldn't tell from your post, but did you Reset the aborted job? Sometimes that logs a 'From previous run...' message with more diagnostic information in it.

EXECUTE_COMMAND (Uses wildcard to get files and uses the ls -m parameter in the command syntax ----> This produces a list of files but without a comma Then it sounds like you're not executing the command properly. If you are using parameters in the Execute Command stage, then they will need to be i...

BIuser wrote:When I add it to my sequence job, there are no options for me to add user variables.

It is a little odd that it starts out so... empty, but it is a standard grid widget so simply right-click on it and then select 'New' or 'Insert'. Don't remember which but it should be obvious once you've done it.

You get those integer values when using Date as the data type, change it to Varchar and use TO_CHAR() with the appropriate mask in the select statement. I don't know what they are, but they're not DataStage internal values so OConv is not the right thing to use with them.

There shouldn't be any need to use 'OConv' on dates coming from a select, they should be usable directly. What does the date look like before you OConv it? What data type are you using for it?

What exactly is in your External Source stage? Check Ernie's blog post on the subject if you haven't already:

http://dsrealtime.wordpress.com/2007/12 ... -a-source/

That's certainly one way to solve the problem. Another is to use the technique described in the online help - use two triggers from the routine, typically an OK and an Otherwise, both sent to a Sequencer set to 'Any' before moving on to the next stage in the flow. The code generator notices that you...

Ah... I grok. I was thinking that overriding the value would also change the value of the variable in the job's environment, but you're saying that's not the case - it would just pass the 'new' value in as the parameter's value. Is there some other way to bring that parameter set value into a transf...

Still... would that not be the current value of the parameter in the job's runtime environment?