DSXchange

From what has been posted here, that's just The Way It Works. Perhaps you can parse the Output variable and look for failure keywords?

What kind of 'load' are you doing? Perhaps what was inserts before are now all updates.

Use a Server job and put the id into the job's USERSTATUS area for easy access. Search here for DSSetUserStatus for examples of the wrapper routine you'll need for that.

Or that. :wink: :lol: Forgot I've done 'conditional counts' the same way - add a new field and conditionally set it to 1 or 0 (depending on if it should be 'counted' or not) and then sum the field. Typically this happens when a value could be conditionally counted in several groups and the counts be...

I had problems with MOD() on numbers over a certain size and I didn't see a need to bump up the EXACTNUMERIC value so I wrote an "SMOD" routine that used the string math functions I mentioned earlier to do a proper mod on any big ass number. Worked fine for me. Would you describe these, t...

Something is popping up in the back of my mind re: your SumIf situation. From what I recall, you can set up the Aggregator to do sums and then one of the 'sum' options is 'Count Non-Null occurances' in a certain field. I'm paraphrasing but that should be close. It can get a little tricky as there ar...

Those are them.

BASIC and all documented in the BASIC manual. So, rather than "div" to divide you would use "sdiv". Same for all of the other operations: sadd, ssub, etc. Build your own mod function that just uses string math.

I don't have access to any kind of DataStage server at the moment, so can't help with the sum/count issue but I remember thinking I had to do them separately as well but then could swear I managed to do both at once. Others will have to help with that. For the pivot, the aggregator output will be mu...

A little lost but the statement that the aggregator "cannot handle sum and count at once" is not true from what I recall. The types make it seem that way but I could swear I was able to combine the two when I needed to. :? That and your "SumIf/CountIf" functions are simple sums a...

Your script should just ask the job directly using dsjob -jobinfo to get the status of the most recent run, unless you need to look back further than that?

Not all by itself as it works on one specific job at a time. People will typically use another option to get a list of all job names in a project and then loop through that list. There is also an option to get all projects.

Sort of, the dsjob command line function has options to pull out log information: -logsum, -logdetail, -lognewest specifically. These are documented in the Command Line Interface chapter of the Server Job Developer's Guide pdf, amongst other places.

I had problems with MOD() on numbers over a certain size and I didn't see a need to bump up the EXACTNUMERIC value so I wrote an "SMOD" routine that used the string math functions I mentioned earlier to do a proper mod on any big ass number. Worked fine for me.

Sounds like a Known Workaround to me.

After you create the encrypted passwords in the Administrator, be sure to change their default value to $PROJDEF after you add them to any job.