DSXchange

Nope. Especially without the design time information in Prod. If you did have it, the only mechanism in your version is a manual comparison of the exported jobs. One by one.

Same dang problem as before, the space in the pathname.

The only thing I can think of that would do that is matches but the problem is I don't believe it is a valid PX function. You'd have to use a BASIC Transformer or a Server Shared Container to bring that functionality into your job from what I recall.

Can you let us know what it was, please?

Ah... the wonders of an Enterprise Scheduler.

maheshkumar.bm wrote:This is my actual input data....

OK... this statement worries me and makes me harken back to my first statement. Are you saying that if you open your file in Windows using Notepad, what you posted is exactly what you see?

Asked and answered here many times. An exact search for "Controller problem: Unhandled failure" will reveal all.

Any particular reason you posted this question three times?

ps. I deleted the other two, in case you were wondering.

There's also the @INROWNUM and @OUTROWNUM system variables that can be leveraged. All solutions need to take your paritioning into account as you would be capturing the Nth row per node otherwise.

Use a Server job, the Sequential File stage there has a 'Contains Terminators' option the PX one doesn't for some reason, it will easily read your 9 records properly.

That could be one way if that works for you. Another would be to leave it as a PIC X field in the CFF and then test for spaces later. If not spaces, use the SDK transform/routine to unpack the real value. I don't have any DataStage access to check on the exact name but those routines are all there i...

Nope, it all depends on your commit level (i.e. how often you commit) and whether the job aborts or not. Only an Abort will result in a rollback and then only for any uncommitted records, this regardless of the delete method used.

Those Segment Violation error signals can be tough to track down. Have you done an exact search for SIGSEGV here? Can you post the complete, unedited error message here?

True... not sure why I felt like pointing that out. Guess just wanted to be clear that's not the actual source file that was posted but rather a dump of it, what with it being all hexy and such.

That would typically mean your XPath Expressions, the values you loaded into the Description column that tell the parser how to generate the XML, are not correct. How did you generate the metadata you are using for your target file? Do you have an xsd that defines what the output needs to look like,...