DSXchange

Of course. Depends on what exactly you need, especially from a concurrent usage standpoint. Check out the 'KeyMgt' routines in the sdk category, they can either be used directly or copied and modified to suit your needs. Some people simply leverage one of the @ROWNUM system variables, seeded from a ...

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

The .odbc.ini entry in what directory? The uvodbc.config (not .ini) in what directory? The former should be in $DSHOME and the latter in your Project.

Or perhaps... oh, I don't know... a Job Activity stage?

It's not. And the 'Cleanup Resources' option doesn't store or log anything.

Yes, as Ray is wont to point out - it's called 'Print to file'.

Somewhat bogged down?

If what you really have on the Oracle side is a flavor of TIMESTAMP you'll need to use the TO_TIMESTAMP function rather than TO_DATE. And the first documentation you should be looking for is the Oracle documentation.

Or substitute 'mate' for 'worker', makes even more sense that way.

Or use a single target stage, not two.

Does it work if you disable the 'stage write cache' option?

UPS wrote:stage_value.cmd.$ReturnValue

Is that a typo? You should be using "stage_value.$ReturnValue" - there's no ".cmd" in there.

I'd also suggest you do a search on 'bind bombed' to learn how to start that process in debug mode to learn why it won't start.

Oh, in a job posting. I thought you meant in some DataStage documentation. Seems like something they made up to me.

Do you mean the Winter and Summer Solistices? The shortest and longest days of the year? That depends on where you are.

I'm not aware of how one would calculate that. I would normally just look such a thing up in an almanac or ephemeris. Perhaps a Google search on 'solstice' would help.