The CallProgram activity always timeouts at 3 minutes if the call takes longer than 3 minutes at IBM i side.
This is because there is no "timeout" implementation on the CallProgram activity for the current BW IBM i plug-in versions thus the global 3 minutes timeout from BW engine level will be applied against all program calls made by CallProgram activity.

ALL

Change waitTime property from BW engine level:

1. If the BW application with CallProgram activity is running from TIBCO BusinessStudio, append the property -Dbw.engine.activity.async.waitTime=<timeout value in milliseconds> in the "VM Arguments" section of the "Run Configuration" dialog.

2. For runtime/deployed application, add the following property in the config.ini for the appspace or appnode:
bw.engine.activity.async.waitTime=<timeout value in milliseconds>

There is side effect in using this resolution that the other async type BW activities without timeout implementation will have to be applied with the new waitTime value since the change is made from BW engine level.

 

How to resolve the issue that CallProgram activity always timeouts at 3 minutes if the call takes longer than 3 minutes at IBM i side

CallProgram timeout, 3 minutes, BW IBM i Plug-in.