Thanks, Steven, for the response. We are planning to open a ticket with IBM, or alternatively apply the latest iFix as you suggested, to try to see if that resolve this issue. In the meantime, if you find any additional information, please share it with ...