DSXchange

Segmentation Fault leading to a core dump. This is typically a software bug, either in DataStage itself or a driver that is in use. Contact your official support provider.

So... to stop the job you deleted the project it was part of?

At this point, just kill the darn thing.

From the same place you started or deployed it - from whatever the "RTI Console" is called nowadays.

Rather than repeat any or everything here, why not tell us what you've tried and why it didn't work for you? Anything come close?

So, part of the same issue you posted last month? Perhaps this might help. That or an exact search for "low values" to see if any previous conversation on the topic sheds some light on it.

You need to ask what is expected there when there is no value for that field. For COBOL and COMP-3 they may just want "low values", in any case there's no need to redefine anything.

I'm sure Ray will suggest using matches, hopefully this syntax is correct as I don't use it much:
I'm assuming you can't just substring out positions 3-5 and check for numeric as "US999ABC" would pass muster but would in fact be invalid.

Again, specifics would help. What is your source characterset? "Not written properly"? Can you post examples, please?

"Handle" in what sense? What specific issues are you seeing? What database?

You can't do any kind of true "redefines" as you've found. What kind of character value are you needing to pass, and what do you mean by "default" in this context?

The question isn't vague, it seems rather simple. He's asking if people who are building dimensions with DataStage are using the SCD stage or if they are rolling their own solution. And for those who have actually used the SCD stage to do the dirty work, how have they found the performance to be? I'...

Unfortunately, we can't see what's different either. I would suspect the same thing it sounds like you do - parameter values. Running a sequence manually rather than scheduled can mean two things: 1. The running user is different but I don't see how that would affect your OCI operation, that should ...

Leaving aside the issue of 'backwards compatability' (there is none) look at the "Tool Version" in a 7.5.3 export and edit the 8.x export to match. Then, for better or worse, it should import.

That or "Timed out while waiting for an event".

I'm curious why you think you need this. Intimate knowledge of the repository is not required to use the product.