Glad to hear this solved the issue.
How VMware Support/IBM missed this, I have no idea!
Well, I guess the reason I thought of this was that I was just lucky (was it luck???) enough to troubleshoot/solve the same issue for a customer a few weeks ago.
André
