Attunity Connection issue after zOS 2.4 Upgrade

[singadurai]

Hello Team ,

We need some help on the attunity connection .Since we don’t know the support id for the open system where the attunity is running .In one of client attunity is running on the Open system and communicating to the DB2 .

After the ZOS 2.4 upgrade we are hitting issues on the Attunity connection to the  mainframe .Can you shed some light on the same .

[Albert_Candelario]

Hello @singadurai ,

We have moved the discussion into the Data Integration forum, so it has more visibility.

Cheers,

Albert

[john_wang]

Hello @singadurai ,

Not sure what's the exact problem. Is Replicate cannot connect to DB2z, or the R4Z does not work on zOS 2.4? I'd like suggest you open a support case with:

1- Detailed information of the problem

2- The Replicate version, R4Z version

3- DB2z version

4- The task Diag Packages

thank you,

John.

[singadurai · Accepted solution]

Hello John ,

Thanks for taking this question .We have resolved the issue by the below .Our Attunity team perform the action .

changed the value of "executeTimeout" internal parameter from 900 to   1800 and launched a Full Load. It seems to work properly without any error message till now.

Thanks and seems after zOS 2.4 the timeout parameter in Attunity  need some increase time out parameter .

Thanks

Singa

[john_wang]

Hello Singa,

Thank you so much for the great information. If the MF is loaded, or some reason (eg network traffic etc) leads the read operation take longer time then increasing the executeTimeout helps.

Good luck and Best Regards,

John.

[Albert_Candelario]

Thanks @singadurai  to let us know is now resolved.

Cheers,

Albert

[Bill_Steinagle]

Singa,

Thank you for the post to the QDI Forums. I would also check the Z/OS for this DB2 connection issue to also check the DDF Details from the system you are connecting too. The Admin for Z/OS can check as well and share if this relates to the connection issue.

-DIS DDF DETAIL

and check the output below as these are the Max Connections and Active Connections

DSNL090I DT=A CONDBAT= 400 MDBAT= 200
DSNL092I ADBAT= 45 QUEDBAT= 203 INADBAT= 0 CONQUED= 0

CONDBAT and MDBAT: These refer to two parameters, CONDBAT and MAXDBAT, in the Db2 subsystem's ZPARM module (think of the ZPARMs as Db2 for z/OS configuration parameters):

• CONDBAT - sets the maximum number of concurrent inbound DDF connections that are to be allowed. 
• MAXDBAT - specifies the maximum number of database access threads (DBATs) that are allowed to be concurrently active

Thanks!

Bill