DSXchange

The 'reset if required' comment wasn't specific to your problem, just a general note of a Best Practice.

So, Arnie... not going to take the pop quiz? :( I generally don't like to give pure code solutions for things like this as I'm afraid there's no learning going on, one can simply plug it in and move on without have to actually understand how it works. I feel like I'm handing out fish rather than a f...

Wouldn't that be scale?

So... is this a QualityStage job?

Sounds like somewhere in your job you have a Decimal field with no precision or scale defined, hence the reference to: "0,0" for schema type "decimal".

The trims may not be strictly needed but make this more fool-proof:
Pop quiz: what exactly is this doing?

I would wager you should be using "Reset if required then Run" in your Job Activity stages, otherwise you'll need to manually reset any aborted jobs. However... The 'Automatically handle activities that fail' option is your friend here to avoid the 'branch from all jobs' approach, but I'd ...

Are you trying to remove the last word from the field? Is what you need actually "QDL Marine and Static Diesel Engines" in this example?

There's no difference between your 'before' and 'after' examples that I can see. It looks like you tried to remove all of the 'n' characters but I can't see why. Yet.

Help us out here.

We've seen this in the past on occassion, I myself saw it a number of years ago but never was able to get an explanation from Ascential as to why it would happen. And then it stopped happening. You might have to work through much chaff to find the wheat but an exact search for "141" should...

A quick Google for "glibc detected double free or corruption" explains what it means but I'm not sure there's anything you can do about it. I assume you are running DataStage on Linux?

As to all of the startup stuff, that just seems to be how it works now.

Can you show us the actual calculation that gets you that value rather than something 'like' it? Still suggest you either up that max precision value or look into the 'string math' functions which are not bound by that setting.

Ah... forgot it was specific to those two stages.

That sounds... familiar. I'm pretty sure the issue has been posted before, along with something you can do to stop that behaviour.

I haven't personally, but sure, there are posts here discussing that. The API is published and generally involves using the 'dsjob' function from the command line. The actual code for dsjob is published as well, so some people have coded closer 'to the metal' as well, from what I recall. A search fo...