When using complex deployments that include multiple database interactions, your WebSphere Message Broker (WMB) message flow might receive a NULL result set in response to an Informix query, because a database row was locked at the time of the request.
To avoid this problem, can you access the database in a READ ONLY mode by setting the isolation level of the database to Dirty Read?
You can specify "SET ISOLATION TO DIRTY READ" as part of a WMB PASSTHRU statement, but you cannot include any other SQL statements.
By setting the isolation level in a separate statement, Dirty Read should remain in effect for the life of the connection, and allow you to read data in subsequent statements without encountering locked database rows.
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI