DSXchange

Excellent. :D

Have you verified the deadlock? If so, then you'll probably need to set the Transaction Size of the delete link to 1 so it gets commited and is out of the way of the inserts. Problem is the fact that they won't be there if you need to rollback... hmmm...

Based on the names we've been seeing, I'm going to hazard a guess that your job is a Parallel job... and the consensus seems to be that PX jobs can't make use of the User Status area. So, as previously mentioned - can you make it a Server job?

No problem... it's all part of the learning process.

Oddly enough, the StringToDate function.

You don't know how happy I am, too.

One way would be to add a call to DSLogInfo in your User Status routine, then the value will be in the Sequence job's log after it finishes.

You don't know how happy I am, too.

One way would be to add a call to DSLogInfo in your User Status routine, then the value will be in the Sequence job's log after it finishes.

Um... let me think... No. Your problem is the delete sql, it has no bind variables and you need one for every column in the link. Make sure the link has one column, put the '20' in its derivation, switch the update action to ' Delete existing rows only ' and mark the field as a Key field. You should...

It works just fine, it just sounds like you're not checking to see if your script had any issues when it ran. You need to check and see if your SystemReturnCode variable came back with a zero or non-zero value. You need to check the contents of your Output variable, which is where anything the scrip...

Ok... the name of the stage variable doesn't matter. The name of the transformer doesn't matter. What you need to use in the custom trigger expression is again exactly what I wrote - but perhaps more specifics are needed. In the trigger, use: JobActivityStageName.$UserStatus Replace JobActivityStag...

That would imply you are using User-defined sql and it isn't setup correctly. Post your sql and any information we'd need to understand it. Either that or switch to generated sql.

You are going to have to manage this. Assemble the record in a single large field, delimeters and all - then write it out to a Sequential File stage with one Varchar field and the Quote Character set to '000'.

The fact that you get ExecSH (rather than ExecDOS) should mean your Server product is installed on a UNIX server unless I am sadly mistaken. One last time - what platform is your server installed on? How hard is that question to answer? I'm afraid we are on what is known as a wild goose chase here...

Can you please confirm your DataStage server is actually installed on a Windows server? Are there any other 'Exec' routines in your drop-down? If so, please list them.

Perhaps somone should actually post a resolution first? What would you suggest as an alternative? I'd hate to see Tracy's first foray into DSXchange end with what basically amounts to a one word answer - 'nope'.