In the end this was not solvable on our end. We had to contact IBM and some fix was later deployed on problematic machine. Problem is I do not know details of this fix.