DSXchange

that is not enough to help you.
open datastage director and try to trace down to what stage failed, where, and why.

The above, of course, is only doing 1 letter at a time. It isn't as slick to do string replacements; you can't use a lookup table for that as easily. Here is the issue: if you do a pure routine that is exactly like erep, then you have to use the failed logic of iterating the same string one time for...

Ive forgotten the details of e-replace, but it may matter in your real code that the result of the inner e-replaces is replaced by the outer calls if it matches. my code here does NOT do that; this code is for a simple this letter to that letter without any internal overlap. If that matters, I can s...

I can't speak to solving the issue as you describe it. but if you did something robust to the keys yourself, like a SHA of the keys that you have on both sides, then it should redistribute clumpy keys evenly and make it perform solidly. I don't think there is anything usable built in; you may need t...

are you doing something with that aggregator stage that could be hand-rolled in a transformer instead? That might resolve it. You may still want to sort the data. also, before you go 2M to 64M, is there something you are doing there that is being undone later? Is the part that blows it up to 64M ove...

you can also use the (? logwarn ?) datastage capability to throw a warning on the log after the run command stage, using its output or whatever to (bypass or trigger?) the warning. This may be what you said you didn't want.

I would say this is a security problem. One can argue that datastage itself is a security problem though.. a run command stage has near root, and you can always find a piece of a job to hijack that can do something inappropriate. You can even get the logs to show your passwords, and steal datastage'...

if you run into something that cannot be set as a parameter, and there are a very few things that are like this, you can make 2 copies of the parallel job with the different setups and call the one you want dynamically in the sequence job. that said I can't recall if this is something you can stuff ...

right, what I was saying is you can just craft the text you need for small xml/json etc files. Its easier and more efficient than parsing and scheming and whatnot so long as you are ok with having to fix it if the fields change. The markup generation stages are a big hammer and your problem may be a...

for small, non nested, extremely simple markup files, I am often willing to just generate them directly without any parsing/thinking/schema/etc. Its faster, easier to code, etc but its no good if you need to change it a lot over time. Most of this stuff does not change over time though. Just a thoug...

what do you already have? Several stages will let you inject a column at will in 11.x. You can also add them to your extract if its from a database, just add a column as type & name to the select (does not have to be null, are you allowed to inject a non-null column?). Transformers used to be a ...

we only ever get them when a job crashes hard and leaves a thread outstanding. I would advise focus on finding out why you have such a high number of them -- see if its one or three or whatever small # of specific jobs doing most of it, maybe -- and work it from that angle. I don't know if this can ...

Like I said we had so much trouble we made a job for it.
it just calls a tcl command 'unlock all'. I don't know if there is a lock all or what available; this is above my digging around.

Dastastage can lock jobs to prevent multiple people editing at once. You can manually lock and unlock them yourself, but I am advising against this as a form of code repository control because locks would not always imply repository lock / failure to check the code out, but could be caused by networ...

transformer loops are really for splitting 1 record into multiples.

what I think you might want here would be a row-generator, and a stage variable. The stage variable would increment the date each time, and the row generator would be your loop counter of sorts...