Datastage throws error while running jobs using zOS DB

[mchivuku]

Datastage is running on zLinux and DB2 on zOS.
Connection between these two server is fine.
Some of the Ds jobs are running fine.
Some of them throw communication failure error in DS.
The same shows the following error in the DB2 log.

07.13.41 STC07895 DSNL027I -DBP1 SERVER DISTRIBUTED AGENT WITH 756
756 LUWID=G9D48B2D.E940.091023050339=4816
756 THREAD-INFO=ARWDS1:ariw:arwds1:osh
756 RECEIVED ABEND=04E
756 FOR REASON=00D3003B
07.13.41 STC07895 DSNL028I -DBP1 G9D48B2D.E940.091023050339=4816 757
757 ACCESSING DATA FOR
757 LOCATION ::9.212.139.45
757 IPADDR ::9.212.139.45

Can anybody give some ideas on why exactly this issue persists?

Regards,
Murali

[aanderson@bcbsal.org]

Hi,
I ran across an old post from 2009 where you were having the timeout issue connecting to zos. Did you ever get a resolution? We are new to Datastage and are having the same issue.
Thanks.

[FranklinE]

There are too many possibilities. If you can, please post the actual error messages. Also, answers to the following may help us help you:

What is your connection method, and do you see any messages specific to the method?

Have you looked in detail at the connections that work vs. the ones that don't work -- or are they all failing?

In my environment, we routinely have bandwidth problems that can be solved by either increasing the load limit or rescheduling jobs to not use it up.