DSXchange

You need to roll your own. I haven't had to worry about TZ yet, so just putting a 'T' where the space was worked for my processes.

Dang, right out of the freaking manual.

That's more like what I was looking for... curious where you found it. Can you post a link?

I've been all over Tom's you-know-what but couldn't really seem to find a definitive answer. And it's not like you can ask anything new, there's always a huge backlog it seems.

So I thought I would ask here.

Just curious if any Oracle peoples out there have any thoughts on using a MERGE for pure deletes? While it is great for "upsert" type operations, it doesn't really seem to provide a pure delete functionality. From what I can tell, you have an optional DELETE WHERE clause that can be added to the WHE...

DSguru2B wrote:USER STATUS is not present in parallel jobs.

So? Use a Server job to get the max value. Have it pass the value via Sequence job and USERSTATUS to the PX job.

You've made assumptions and used relative paths in your script. You'd either need to 'cd' to the proper location first or use absolute paths.

Have you found your "file.log" file? It will be in the job's Project as noted.

DataStage *is* running your script: i am getting this info : testjob2..BeforeJob (ExecSH): Executed command: /dev/dsdd/data/files/xyz.sh *** No output from command *** Just because it shows "no output" doesn't mean it didn't run it, it means the script doesn't echo anything to standard out - i.e. to...

If you go to Kim Duke's website, there is a loverly older Ascential document on XML 'Best Practices' that does a great job of illustrating these techniques. Free for the downloading.

From a TCL prompt using the DEADLOCK.MENU functions is the best answer. You need to not be connected to a particular Project, from what I recall, if you're not sure do a "LOGTO UV" command first. Or I believe you can just edit the value of the Start boolean in the config file and it will notice.

Prove it for us. Try it again with spaces between the arguments and post the messages that configuration generates.

You said your three arguments in the stage were 'separated by spaces , as required by the shell script' and yet this seems to show you actually have commas there.

No, just the deadlock daemon itself.

I went fishing for an Uber, can't help who takes the hook.

Sorry, I'm not familiar with that version or if it is supported by DataStage. Have you asked this question of your Support provider?