DSXchange

What happens why you try running the 'Wincommand' manually? Does it work then?

Arnd, PLEASE use indentation in your code to make it readable.

First step would be to tell us which plug-in you are using. Second step would be to let us know if you've ever used that plug-in successfully before, like in a job. Silly things like that. Details, man!

Of course you can! That's not the problem. You've used three parameter markers in your SQL and dollars-to-doughnuts you don't have:

1) Three columns defined in the stage
2) First column marked as a Key

The first one is the real culprit, I'd wager.

I've had no reason to handle the encrypted params - the only ones I use are always $PROJDEF - no exceptions - ever. We know you didn't need it, but others would. Tons of peoples, like my current client, started on a version that didn't support $PROJDEF so didn't have the luxury of your 'no exceptio...

If you want it to start from 1 each time, there's absolutely no reason to use that function. Why not simply use @INROWNUM for the surrogate?

No. How exactly did you 'perform a stored procedure in before subroutine'?

I suddenly find myself coveting a utility like this. Any clue what it would take to handle encrypted parameters?

Fully path the bat file.

The patch is pretty well version agnostic. I think all versions up to 7.5.1A need the patch, no clue on 7.5.2 but it couldn't hurt to err on the side of caution.

This is the post I was thinking of.

Have you tried the UNIX command 'diff'?

Welcome! First step is that you would have to actually purchase the 'SOA Edition' of the product. This is what allows you to take a 'normal' Server or PX job and 'SOA Enable' it. Not sur how much useful information there is there, but here is a link to the official site for the product. Nothing abou...

Ok... and have you looked in the log of the 'Dim' job to see why it finished with warnings?

You are getting this where exactly? Sequence job? Batch job?