DSXchange

You would need to write one yourself. And this would be a script, so run at the operating system level in korn or bash or your shell of choice. Hmmm.... there is at least one posted here, probably way more than most people need but let me see if I can turn it up... Here: http://www.dsxchange.com/vie...

Simply don't include D and E in your target stage. Either that or specifically map NULL to them.

Sounds more like a DBA question. If you ask them and let us know the syntax you would need for that, we can help you get it into the stage properly...

You really can't compare Access behaviour with other databases like that. You should pre-screen your data and only issue the update for rows you know won't violate that contraint.

I don't believe so, have never heard of such capability... but then I've never done a crap-ton of ODBC. Anyone?

DataStage is just another application that AutoSys (or any other Enterprise scheduler) can control. And by 'control' I mean launch and monitor jobs and control dependancies between scheduled events - DataStage or otherwise. Most of us have some kind of "start DataStage job" script that wra...

Set the 'Data Element' to XML for the chunk data so it knows it is already XML and doesn't make that conversion.

What version would that be? Perhaps a fix pack or six is in your future.

Leave them blank there, no need to expose them. Create job parameters (or a parameter set) for the required information - database, user, password (etc) - and then leverage those parameters in your database stages, ODBC or otherwise.

I have no idea if this is the issue or not, but there seem to have been quite a number of patches for Connectors from what I've read here - are you up-to-date on your fix packs?

"Any table" - as long as it is in the connected database and you have the required permission, of course. Not necessarily "any SQL", however.

I don't know if it is "better" or not, but if their requirement is to do it "in job" then as anbu noted (with the caveat regarding their string format) what they are doing is just fine - dashes or no dashes.

So... you are looking for a way to... view job logs? Check job status? What are you after with this access?

adityavarma wrote:Can we write an unix script and call through the execute command activity?

Sure, but you don't even "need" a script for this - just do the cat work directly there.

If they are worried about not 'seeing' anything on the canvas, put an annotation there stating where/what is going on. Otherwise you'll need a single record source, a routine to call DSExecute() and then some kind of a target which could be a flat file directed to /dev/null, I suppose.