Explanation | XD functionality is disabled on the server. |
Action | Enable XD functionality. |
Explanation | XD JMS Proxy cannot run in dmgr or nodeagent process. |
Action | none. |
Explanation | Error while starting XD JMS message pacing controller. Instance of controller already registered with Messaging Engine. |
Action | Report program defect to IBM. |
Explanation | XD JMS message pacing controller successfully started on the server. |
Action | none. |
Explanation | XD JMS message pacing controller successfully stopped on the server. |
Action | none. |
Explanation | Internal error happened while handling incoming request. |
Action | Report program defect to IBM. |
Explanation | Internal error happened in post processing the request. |
Action | Report program defect to IBM. |
Explanation | JMS message batch size is set by XD JMS message pacing controller. |
Action | none |
Explanation | XD JMS functionality is disabled on the server. |
Action | Enable XD JMS functionality. |
Explanation | XD JMS System internal error occurred. |
Action | Report program defect to IBM. |
Explanation | Services needed for XD JMS functionality are not currently running. |
Action | Report program defect to IBM. |
Explanation | XD JMS classification service started successfully on the server. |
Action | none. |
Explanation | XD JMS classification service stopped successfully on the server. |
Action | none. |
Explanation | XD JMS request control service started successfully on the server. |
Action | none. |
Explanation | XD JMS request control service stopped successfully on the server. |
Action | none. |
Explanation | XD JMS WSMM service started successfully on the server. |
Action | none. |
Explanation | Error while initializing odc tree inside request queue filter. |
Action | Report program defect to IBM. |
Explanation | Classification information for the destination is missing in the current context. |
Action | Report program defect to IBM. |
Explanation | Error while resuming the suspended request. |
Action | Report program defect to IBM. |
Explanation | Work is delivered before XD JMS message pacer initialization completed. Work will not be throttled by XD. |
Action | Deliver messages after server initialization completes. |
Explanation | Unable to determine module using the current destination and bus. |
Action | Make sure destination and bus name being consumed is configured in work class of the application. |
Explanation | Destination is being used by more than one module. Optimal solution is provided when a destination is consumed by a single module. |
Action | Make sure a given destination is consumed by a single module for optimal results. |