Impacts of changing Buffering Policy
Posted: Mon Nov 09, 2015 11:11 am
Hi,
We are upgrading from DS8.1(Linux) to 11.3 (Windows). We have quite a few jobs that use a design similar to fork join. The jobs are getting into a deadlock situation and stuck with no progress. These jobs are running fine in 8.1(linux)
But when we change the buffering policy from automatic to force, they are running smooth. What is the impact of forcing buffering, with out the tool deciding it. we have other jobs also, that ran fine, so would forcing buffering to every job/link cause performance issues?
Has anyone come across this scenario? Planning to open a ticket with IBM,but wanted to get an expert opinion here.
We are upgrading from DS8.1(Linux) to 11.3 (Windows). We have quite a few jobs that use a design similar to fork join. The jobs are getting into a deadlock situation and stuck with no progress. These jobs are running fine in 8.1(linux)
But when we change the buffering policy from automatic to force, they are running smooth. What is the impact of forcing buffering, with out the tool deciding it. we have other jobs also, that ran fine, so would forcing buffering to every job/link cause performance issues?
Has anyone come across this scenario? Planning to open a ticket with IBM,but wanted to get an expert opinion here.