DSXchange

1) Yes.
2) Yes.

If you search for USERSTATUS you should find a number of discussions on how to use it and some code to make it easier as well.

A couple of problems. 1) You can't use a parameter in a parameter. 2) You can't set the value of a parameter 'before job' as the job has already started. It's not as before as you may think. Now, you may be able to simply reference @USER0 inside your job without the hashes, but no guarentees there, ...

Ok. What exactly do you need help with, where are you stuck? Building the job? Hand coding something in BASIC using functions?

Well, there are functions (OPENSEQ,WRITESEQ,etc) but wondering if that's really what is wanted here or if a simple job would do the trick.

Why not just create a job to do this for you?

Unless you want to preserve the current content of those columns, in which case you'd need to get them from a lookup first and supply them when you don't have new data coming in.

Have you setup all of the ODBC configuration info this new server needs in the DSEngine and Project directories?

You could do the same, if you like, via the Stored Procedure stage. Or via the Aggregator stage (perhaps multiple), though I daresay it may not be all that speedy unless your data is presorted per grouping column(s). Or I would assume that the 'aggregation' could be done using straight sql in your s...

Performance of what, exactly?

Right. Make sure you understand the 'new' part of that advice, as it won't help with any current jobs but will be used going forward.

So, in other words you have no 'junk character' issue but rather an issue handling multi-byte characters?

No, while the body text you supply in the stage would be 'static', checking the 'Include job status' option would dynamically include the error text as well.

Have you actually tried it with a failing sequence? Did your experience not match the advice given?

Are you not using the Director's Auto Purge functionality? Logs can be purged based on the number of retained days or runs, and that number could be one if so desired.

Unfortunately, seeing as how I know nothing about DB2, that's about all the help I can give here. Other than asking - Have you read the 'Configuration Guide' for the plugin or the specific plugin pdf manual? They should include everything needed configuration-wise to get you going. Lastly, engage yo...

clarcombe wrote:On a related issue, I have noticed that when my job finishes with warnings, the exception handler is not invoked. How can I get it to do this ?

Basically, you can't. A job has to abort to trigger the Exception Handler.