DSXchange

I think that would fall into the 'landing' camp.

Seen that before with a buggy Oracle client. Ask.

Well... in general, 'cross platform' is not an issue. Again, from what I'm reading, this is a restriction put in place by the AS/400 and mainframe environments only. And again, no clue how "DPF" affects this answer, knowing less than nothing about it.

karthi_gana wrote:Resolved.

:D There's actually a big button at the top of the screen for that.

Could you post the resolution, please? That and marking your post as Resolved would be helpful as well.

OK. That answer is specific to the difference in the AS/400 and mainframe platforms... so it's only an issue if your database is on one of those.

No clue how the "DPF" part affects this answer but outside of that it's still a "no". There's no database that needs to be "co-resident" to work with DataStage that I am aware of. Or to utilize DB2 parallelism.

Operation timed out: connect:could be due to invalid address

Have you... checked this? Verified in another tool the service you are attempting to connect to?

And 'blank' means what here, exactly?

Ah, yes... revisionist history.

Have you asked your official support provider? What was their advice? No, you shouldn't have to do anything like that on a regular basis.

I don't see him saying any such thing. Can you point out the part you are referring to, please?

That should be fine, however... did you run this latest version from the CMD line yourself? Did it stop and ask you any questions? If so, that's one typical reason for a 'hang' in job, there's no-one to answer the question.

And in case that doesn't make any sense, it's equivalent to doing the Oconv/Iconv pair 'standalone' and then using the DIGITS transform to get it stripped down to just the numbers.

Right, that's the biggest difference to me - one exists while the other doesn't.