Time out issue on ibm db2 for iseries, SQL30081N A communication error has been detected. error code (10060)

[Shai_E]

When  getting the following error with your IBM DB2 for iseries: 

RetCode: SQL_ERROR SqlState: 40003 NativeError: -30081 Message: [IBM][CLI Driver] SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "IP Adress".
Communication function detecting the error: "recv".
Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001

Based on IBM official documentation this specific error code means:

A connection reaches the network timeout limit and is disconnected by the network. The timeout is initiated by TCP/IP layer. TCP/IP has a timeout value. If the open connection stayed too long, TCP/IP forces the connection off. In many cases, this disconnection is a network issue.

Environment:

• Qlik Replicate 2021.11

• Operating System: Windows

• Operating System Version: Server 2019

• Environment Type: Cloud

• Source: DB2 FOR ISERIES

• Target: SNOWFLAKE ON AZURE

Resolution

• For DB2i and if the timeout is in Full Load you can increase the "executeTimeout" internal parameter from 60 to    1800.
• For CDC on the source you can increase internal parameter "cdcTimeout".
• We do recommend checking with your networking team why you are getting so many time-outs.

If the issue is not improved, we suggest logging a support ticket and including the required logs (after setting executeTimeout with Stop/Resume Task) and setting SOURCE_CAPTURE component to TRACE (if the timeout is in DB2i).