DSXchange

Well... allegedly it runs fine on one server and not the other. I've seen that when the 'works fine' one is 64bit and the 'not so fine' one is 32bit. Any chance of that?

Does the stage even support sftp? OK, a quick check of the docs show it does, have you enabled that option?

But using both doesn't cause an error from what I recall, just confusion. Can you post the current version of your dsjob command and the latest error you are getting?

You don't have a library error. All the "unhandled failure" means is your command did not return a zero and you have the "Automatically handle activities that fail" option enabled in the Sequence. You didn't specify what to do on failure so it handled it. You'll need to dig into ...

SPuneet wrote:please help..how should i rectify this

Begin by starting your own post. Your issue isn't "similar" to the post you jumped on the end of, so I split you out so we could keep the two unrelated conversations... unconnected.

[-param <name>=<value>]

Either pass a name/value pair or don't include the "-param" if you don't need to pass a parameter. Also, use either -wait or -jobstatus, not both.

There's information on HA over in the IBM Information Center, for example this topic, specifically Planning Step 3 and the "High availability configurations" section.

With this additional information, I'm going to agree with Arnd that you need to put this in front of your official support provider.

Examine the sequence job's logs, the answer should be readily apparent.

So what was your "workaround"?

Any chance you could expand on what you mean by "using bundled websphere"?

I'm just going to echo what Ray said but add that you should think of this as if you were converting from a completely different tool to another, which basically you are. Make sure you thoroughly understand what the Server job does and then build an equivalent Parallel job. Much the same as if you'd...

Nop instead of IDENT1 we are getting "TRANSFORMER STAGE1:Pin 2 not initialized" Which is to be expected if this didn't solve the problem as now the transformer has a name. Odd that it didn't change at all as it seems like you would need to drop and re-establish all of the links between th...

times29 wrote:i did try payr_vblnr is not null or payr_vblnr <>' ' but same result

Unless that's a typo, there's a space between those two quotes in what you posted so that (a space) is what it is attempting to filter. Just use two quotes to represent the empty string.

That would imply they're not nulls but rather empty strings. It works in Oracle because Oracle treats them as equivalent but DS does not. Try filtering for empty strings ('') or both and see if that works.