DataStage doesn't respond to call backs

actiview · Post by **actiview** » Thu Oct 14, 2010 4:07 am

Hi,
We have just upgraded to a new DS server and we encounter a strange problem:
DS is calling a procedure in another server (AS/400), and waiting for it to respond. After 2 hours of wait, it aborts for connection timeout reason.
When looking at the AS/400 log file, we see that it returned an answer after a half an hour, which, for some reason, didn't arrive to DS.
Infrastructure guy revealed that AS/400 returnes an answer on a different port (random one) than the one initiated by DS (and this is OK since this is the way it works also on the old DS server) but oddly, DS doesn't respond to the new port calls.
We removed the firewall completely from the DS server, and still, the problem remains.

Has anyone experienced something like that before?
We are completely lost here.
Thanks.

chulett · Post by **chulett** » Thu Oct 14, 2010 5:25 am

How exactly are you 'calling a procedure in another server'? I suspect you'll end up needing to send this to your official support provider, but let's start with that.

actiview · Post by **actiview** » Thu Oct 14, 2010 5:41 am

chulett wrote:How exactly are you 'calling a procedure in another server'?

Hi,
We exeute: call qsys.qcmdexc('CALL .....',xxxxxx)
in the "Before" section of the DSDB2 Stage's SQL tab.

Again, this is working fine on the OLD DS server. We didn't modify any job. So we think this has something to do with the DSEngine definitions of ports/listeners/sniffers/etc that might not have been configured correctly.

Thanks again.