BIP2000-2999: Runtime components - Broker
- BIP2001
- The WebSphere Message Broker service has started at version <insert_2>; process ID <insert_1>.
- Severity
- 0 : Information
- Explanation
- The WebSphere Message Broker service executable has been started.
- Response
- No user action required.
- BIP2002
- The WebSphere Message Broker service has stopped.
- Severity
- 10 : Warning
- Explanation
- The WebSphere Message Broker service has been stopped.
- Response
- No user action required.
- BIP2003
- The WebSphere Message Broker service has paused.
- Severity
- 10 : Warning
- Explanation
- The WebSphere Message Broker service has paused.
- Response
- Restart the WebSphere Message Broker service as soon as possible.
- BIP2004
- The WebSphere Message Broker service is continuing.
- Severity
- 0 : Information
- Explanation
- The WebSphere Message Broker service is now running.
- Response
- No user action required.
- BIP2005
- Unsuccessful WebSphere Message Broker service initialization.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker service could not be registered.
- Response
- Check that the machine has adequate memory and that the userid and password used to start the broker are correct and that the userid is a member of the mqbrkrs group.
- BIP2006
- Unable to start executable <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker service could not start an executable.
- Response
- Make sure that the executable is in the correct directory and that the WebSphere Message Broker service userid has permission to start the executable. Ensure that there is adequate memory available on the system. Reissue the command.
- BIP2007
- The WebSphere Message Broker service has detected that its child process has ended abnormally, process ID <insert_1>.
- Severity
- 20 : Error
- Explanation
- An executable started by the WebSphere Message Broker service terminated abnormally.
- Response
- Review any other messages written to the system log to determine the cause of the failure. If you are unable to determine the cause of failure, contact your IBM support center.
- BIP2009
- The WebSphere Message Broker service detected an unknown serviceHandler request.
- Severity
- 20 : Error
- Explanation
- An unknown request was directed to the WebSphere Message Broker service.
- Response
- Trace the problem and contact your IBM support center.
- BIP2010
- The WebSphere Message Broker service has stopped, process ID <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker service has stopped.
- Response
- Restart the WebSphere Message Broker service when required.
- BIP2011
- The WebSphere Message Broker service has been shutdown, process ID <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The WebSphere Message Broker service has stopped.
- Response
- Restart the WebSphere Message Broker service when required.
- BIP2014
- The WebSphere Message Broker service was unable to start executable <insert_1> due to a lack of system storage.
- Severity
- 20 : Error
- Explanation
- The system is short on storage.
- Response
- Enable more system storage.
- BIP2015
- The WebSphere Message Broker service detected that executable <insert_1> terminated, exit code <insert_2>.
- Severity
- 20 : Error
- Explanation
- An executable terminated unexpectedly.
- Response
- The WebSphere Message Broker service will restart the executable automatically unless the broker is currently shutting down. Determine the reason for the unexpected termination of this executable.
- BIP2016
- Unable to start <insert_1> thread.
- Severity
- 30 : Severe error
- Explanation
- A thread cannot be started because <insert_2> returned <insert_3>.
- Response
- Increase the operating system settings. Stop and restart the broker. If the problem continues, restart the operating system. If the problem still continues, contact your IBM support center.
- BIP2017
- Unable to redirect stdout and stderr for <insert_1>, <insert_2>.
- Severity
- 10 : Warning
- Response
- A user response is not required. The process will proceed without redirecting the output.
- BIP2030
- Execution Group <insert_1> could not be created, unable to open its process handle.
- Severity
- 20 : Error
- Explanation
- The Broker could not create an Execution Group process.
- Response
- Ensure that the system has adequate system resources and that the Execution Group executable is available. Contact your IBM support center if this does not resolve the problem.
- BIP2031
- Unable to start Execution Group executable <insert_1>.
- Severity
- 20 : Error
- Explanation
- The Broker could not create an Execution Group process.
- Response
- Ensure that the system has adequate system resources and that the Execution Group executable is available. Contact your IBM support center if this does not resolve the problem.
- BIP2033
- The broker was forced to stop an execution group process. The process ID was <insert_1>.
- Severity
- 0 : Information
- Explanation
- The execution group process would not stop normally and was forced to terminate.
This might be because the WebSphere Message Broker executable bipbroker failed unexpectedly. During the automatic restart of bipbroker by the bipservice executable, all execution groups are stopped and then restarted. If executable bipbroker fails during normal shutdown, execution groups might be left running. When the broker restarts, these execution groups are terminated and a new set of execution groups started. A system log message indicating that executable bipbroker failed unexpectedly indicates this type of problem.
This should be treated as an abnormal termination of the execution group and handled accordingly.
- Response
- Investigate why the executable bipbroker stopped unexpectedly.
Ensure that any database in-doubt or uncommitted locks that are held by the execution group are dealt with.
Use the WebSphere Message Broker documentation together with your database documentation to determine the best course of action for dealing with 'in-doubt' units of work.
Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP2034
- An unexpected exception was thrown.
- Severity
- 20 : Error
- Explanation
- An unexpected event occurred and an exception was created.
- Response
- Contact your IBM support center.
- BIP2037
- The internal configuration message has been discarded.
- Severity
- 20 : Error
- Explanation
- An internal configuration message could not be processed to completion, even though multiple attempts were made to process the message.
- Response
- Review any other messages written to the system log to determine the cause of the failure. If you are unable to determine the cause of failure, contact your IBM support center.
- BIP2038
- The internal configuration message was rejected due to broker persistent store problem.
- Severity
- 0 : Information
- Explanation
- The broker's persistent store could not be updated; the internal configuration message was rejected because of this.
- Response
- Review any other messages written to the system log to determine the cause of the failure. If you are unable to determine the cause of failure, contact your IBM support center.
- BIP2045
- Broker <insert_1> running on WebSphere MQ queue manager <insert_3> did not process a deployment message, because it was addressed to a broker with a different identifier.
- Severity
- 20 : Error
- Explanation
- This is an internal error, which means that the broker has been previously configured using old, internal interfaces. (Supplied UUID=<insert_4>, expected UUID=<insert_2>)
- Response
- Ensure that the broker is only accessed through supported interfaces that are based on the CMP API.
- BIP2046
- Broker <insert_1> detected that a configuration request contained a missing XML tag (<insert_3>).
- Severity
- 20 : Error
- Explanation
- A configuration message could not be processed and was rejected.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2047
- Broker <insert_1> (UUID <insert_2>) could not process an internal configuration message because the broker name received in the message (<insert_3>) did not match that of this broker.
- Severity
- 20 : Error
- Explanation
- An internal configuration message could not be processed and was rejected.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2050
- Broker <insert_1> (UUID <insert_2>) received an internal configuration message that specified version <insert_3>, this broker is only capable of supporting up to and including version <insert_4>.
- Severity
- 20 : Error
- Explanation
- The versions of internal configuration message that the broker supports is dependent upon the WebSphere Message Broker product that is installed.
- Response
- Ensure that the component that is sending the internal configuration message is capable of sending an internal configuration message with the correct version. Consult the WebSphere Message Broker online documentation book for migration guidance. Contact your IBM support center if you are unable to resolve the problem.
- BIP2051
- Broker <insert_1> (UUID <insert_2>) could not process an internal configuration message to completion, the problem was caused by <insert_3>.
- Severity
- 20 : Error
- Explanation
- The configuration message could not be processed and was rejected.
- Response
- Use the inserts within this message to determine the cause of the problem. Correct the broker's configuration and redeploy using the Message Broker Toolkit, mqsideploy command or a CMP application. Contact your IBM support center if you are unable to resolve the problem.
- BIP2052
- Broker <insert_1> (UUID <insert_2>) could not process an internal configuration message to completion: the problem was caused by XML tag <insert_3>; value <insert_4>.
- Severity
- 20 : Error
- Explanation
- An internal configuration message could not be processed and was rejected.
- Response
- Contact your IBM support center.
- BIP2054
- Unable to allocate memory for an internal function.
- Severity
- 20 : Error
- Explanation
- There is a shortage of memory on the system.
- Response
- Increase the amount of memory available to the system.
- BIP2056
- Broker <insert_1> successfully processed the entire internal configuration message.
- Severity
- 0 : Information
- Explanation
- An internal configuration message was processed to completion.
- Response
- No user action required.
- BIP2057
- Execution Group <insert_1> could not be started: broker name <insert_2>; UUID <insert_3>; label <insert_4>; Pub-Sub server <insert_5> (1=Yes, 0=No).
- Severity
- 20 : Error
- Explanation
- The broker was unable to start an execution group process.
- Response
- Ensure that the executable is available and that the broker's service userid has permission to run the executable.
- BIP2059
- The broker has detected that the Execution Group <insert_1>, process ID <insert_2>, has shut down abnormally.
- Severity
- 20 : Error
- Explanation
- An Execution Group process ended abnormally.
- Response
- Investigate the reasons for the problem.
- BIP2060
- The broker has detected that the Execution Group <insert_1>, process ID <insert_2>, has shutdown.
- Severity
- 10 : Warning
- Explanation
- An Execution Group has shutdown. A new instance of the execution group will be started in approximately <insert_3> seconds.
- Response
- Investigate any prior system log messages for possible problems. Contact your IBM support center if you are unable to determine the cause of the shutdown.
- BIP2061
- Broker <insert_1> execution group <insert_3> (UUID <insert_4>) detected that a configuration request contained an unsupported XML tag.
- Severity
- 20 : Error
- Explanation
- A configuration message could not be processed and was rejected.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2062
- Broker <insert_1> (UUID <insert_2>) execution group <insert_3> (UUID <insert_4>) detected that the deployed configuration message received contained an XML tag that is not applicable to the current broker state.
- Severity
- 20 : Error
- Explanation
- The configuration message received could not be applied to the broker's configuration. This could occur for either of the following reasons: (a) The configuration message XML tag directs an execution group to be created but the execution group already exists. (b) The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
- Response
- Use the Message Broker Toolkit, mqsideploy command or a CMP application to redeploy to the execution group. Contact your IBM support center if you are unable to resolve the problem.
- BIP2063
- Broker <insert_1> execution group <insert_3> (UUID <insert_4>) detected that the deployed configuration message that was received would cause an uninitialized object to be created.
- Severity
- 20 : Error
- Explanation
- A configuration message could not be processed and was rejected.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2064
- Broker <insert_1> (UUID <insert_2>) Execution Group <insert_3> (UUID <insert_4>), deployed configuration message rejected.
- Severity
- 0 : Information
- Explanation
- This Execution Group's configuration message was rejected because the deployed configuration message would have caused more serious errors in other Execution Groups. This Execution Group was not the primary cause for the rejection of this configuration message.
- Response
- Look at all the messages that were listed and resolve the problems that they describe. The Execution Group mentioned in this message can be deployed individually.
- BIP2065
- Broker <insert_1> has processed a request against its internal configuration.
- Severity
- 0 : Information
- Explanation
- The Message Broker Toolkit, a command or a CMP application has made a request against the brokers internal configuration.
- Response
- Determine if the request was successful by analyzing the messages following this message.
- BIP2066
- Broker <insert_1> was unable to retrieve an internal configuration response message for execution group <insert_3> within the <insert_4> second configuration timeout.
- Severity
- 20 : Error
- Explanation
- The execution group did not respond within the time period set by the broker's ConfigurationChangeTimeout parameter. This defines the maximum length of time in which an execution group can apply a configuration change, and the default value is 300 seconds.
- Response
- Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if a problem with the execution group has been reported. Check that your system is not running short of resources; you might need to increase the WebSphere MQ log size, for example.
You can increase the ConfigurationChangeTimeout parameter by using the mqsichangebroker command. Reducing the complexity of the deployment might also solve this problem.
Correct the problem and resubmit the configuration request. Contact your IBM support center if you are unable to resolve the problem.
- BIP2067
- Broker <insert_1> (UUID <insert_2>) unable to get internal configuration response message for Execution Group <insert_3> from WebSphere MQ queue <insert_4>.
- Severity
- 20 : Error
- Explanation
- The Execution Group internal configuration response message queue has failed.
- Response
- Investigate why the WebSphere MQ queue failed. Use the system log messages to determine and correct the problem. Redeploy the broker configuration message from the Message Broker Toolkit, mqsideploy command or a CMP application.
- BIP2068
- The broker was unable to put an internal configuration message to message queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message could not be sent because the message queue was not available.
- Response
- Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the broker's configuration.
- BIP2069
- The broker attempted to put an internal configuration message to a reserved message destination <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message destination is reserved for use by the broker only.
- Response
- Investigate why the internal configuration's reply message destination name was sent to a reserved destination.
- BIP2070
- A problem was detected with WebSphere MQ while issuing <insert_1> for WebSphere MQ queue <insert_2>, WebSphere MQ queue manager <insert_3>. MQCC=<insert_4>, MQRC=<insert_5>.
- Severity
- 20 : Error
- Explanation
- The operation on the specified queue or queue manager returned with the indicated WebSphere MQ completion and reason code.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If an MQOPEN was unsuccessful because the queue manager or queue did not exist, then define these objects to WebSphere MQ. If the problem was because incorrect object names were specified, then the message broker will try to recover, if the problem persists it may be necessary to restart the message broker.
- BIP2071
- A problem was detected on WebSphere MQ while issuing <insert_1> for WebSphere MQ queue <insert_2>, queue manager <insert_3>. WebSphere MQ property <insert_4> had an unsupported value of <insert_5>.
- Severity
- 20 : Error
- Explanation
- The operation on the specified queue was not successful because the message being received contained a WebSphere MQ property that is not supported.
- Response
- Investigate why the unsupported property was being used.
- BIP2074
- A problem was detected with WebSphere MQ while issuing <insert_1> for WebSphere MQ Queue Manager <insert_2>. MQCC=<insert_3>, MQRC=<insert_4>.
- Severity
- 20 : Error
- Explanation
- The operation on the specified queue manager returned with the indicated WebSphere MQ completion and reason code.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If an MQOPEN was unsuccessful because the queue manager did not exist, then define this object to WebSphere MQ. If the problem was because incorrect object names were specified, then the message broker will try to recover, if the problem persists it may be necessary to restart the message broker.
- BIP2075
- The broker was unable to send an internal configuration <insert_1> message to Execution Group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message could not be sent.
- Response
- Investigate why the Execution Group message queue was not available by reviewing messages issued to the system log. Resolve the problem described in the system log. The broker will retry this operation.
- BIP2076
- The broker was unable to get an internal configuration <insert_1> message response from Execution Group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message response could not be retrieved.
- Response
- Investigate why the Execution Group was not able to respond by reviewing messages issued to the system log. Resolve the problem described in the system log. The broker will retry this operation.
- BIP2077
- The broker received a negative response to an internal configuration <insert_1> message from Execution Group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message response indicates that the Execution Group is not able to either start processing message flows or to stop processing message flows. If the negative response was for a start message then the operation will be retried later. If the negative response was for a stop message then this would indicate the Execution Group was being deleted or the broker was attempting to shutdown, restarting the broker will correct this problem, (you may need to use the -i flag on mqsistop)
- Response
- Investigate why the Execution Group response was negative by reviewing messages issued to the system log. Resolve the problem described in the system log.
- BIP2078
- The broker was unable to get an internal configuration message from message queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message could not be retrieved because the message queue was not available.
- Response
- Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the broker's configuration.
- BIP2079
- The broker received a response without data for an internal configuration <insert_1> message from Execution Group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The internal configuration message response had no data with its structure, so, the broker was unable to determine if the Execution Group acted upon the configuration message. This operation will be retried later.
- Response
- Investigate why the Execution Group response contained no data by reviewing messages issued to the system log. Resolve the problems described in the system log. If this problem persists contact your IBM support center.
- BIP2080
- Execution group <insert_1> failed to return an internal configuration <insert_2> message response within a <insert_3> second time period.
- Severity
- 20 : Error
- Explanation
- The internal configuration message response could not be retrieved. The execution group therefore failed to move to the state described by the internal configuration message.
- Response
- Review messages issued to the system log to investigate why the execution group internal configuration message response was not returned within the allowed time period. Additionally, you can increase (or decrease) the timeout using the mqsichangebroker parameter, InternalConfigurationTimeout. The timeout period is automatically extended during broker startup based on the number of execution groups which a broker contains. At this time, the timeout period reported may not match the value configured for the InternalConfigurationTimeout parameter. Changing the timeout does not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time, or to allow for large and complex deployments. Resolve any problems described in the system log. This internal configuration operation is retried automatically; if you continue to see this message, you should investigate the reason for the execution group's failure to respond.
- BIP2081
- Execution Group <insert_1> process ID <insert_2> could not be stopped by the broker.
- Severity
- 20 : Error
- Explanation
- An attempt was made by the broker to stop an Execution Group process. This may have been as a result of deleting and deploying the Execution Group or a failed attempt at creating and deploying the Execution group. After one of these actions the broker attempted to force the Execution Group process to stop but was unable to carry out this action.
- Response
- Investigate the reason why the broker user ID lacked the permissions to stop the stalled Execution Group process. Reviewing messages issued to the system log may give some indication of why this occurred. Resolve the problem described in the system log. It is required that the user stop the Execution Group process using either mqsistop with the -i flag selected or the KILL function.
- BIP2082
- Broker <insert_1> could not process part of an internal configuration message. WebSphere Message Broker no longer supports publish subscribe topology deployment. This part of the configuration message has been ignored.
- Severity
- 10 : Warning
- Explanation
- Publish subscribe is no longer supported within WebSphere Message Broker. Any attempt to deploy topology, topic definitions, or ACL information from a previous level of the product will be ignored. This part of the deploy failed.
- Response
- Manage your existing publish subscribe topology on this queue manager using the administration tools available in WebSphere MQ.
- BIP2086
- Broker <insert_1> could only process parts of the internal configuration message.
- Severity
- 20 : Error
- Explanation
- Parts of the internal configuration message were not processed successfully.
- Response
- This response indicates that one or more Execution Groups could not process the internal configuration message. Analyze all of the following messages to determine why the internal configuration message could not be processed.
- BIP2087
- Broker <insert_1> was unable to process the internal configuration message.
- Severity
- 20 : Error
- Explanation
- The entire internal configuration message failed to be processed successfully.
- Response
- Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
- BIP2088
- An unexpected exception <insert_1> was caught.
- Severity
- 20 : Error
- Explanation
- The broker caught an unexpected exception.
- Response
- Use the information in this message and previous messages to determine the cause of the problem, correct the error. A redeploy will be required if this error occurred as a result of a deploy operation.
- BIP2089
- An internal configuration message was received but it contained no data.
- Severity
- 20 : Error
- Explanation
- The internal configuration message contained no data, the message was treated as a null operation.
- Response
- Contact your IBM support center.
- BIP2091
- The broker has reconnected to WebSphere MQ successfully.
- Severity
- 0 : Information
- Explanation
- The broker was unable to communicate via WebSphere MQ transports, communication has been reestablished.
- Response
- Investigate the reasons for the WebSphere MQ product termination.
- BIP2099
- Unable to initialize a Parser Factory.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst initializing its parser factory environment. Examine previous error messages for details of the cause of this problem.
- Response
- Contact your IBM support center.
- BIP2101
- Unable to allocate memory.
- Severity
- 20 : Error
- Explanation
- An operation was performed which needed to allocate virtual memory, but the request failed because not enough memory was available. Operation of the message broker will probably be unpredictable. Other messages may indicate similar problems or provide additional information.
- Response
- Since this is indicative of a shortage in virtual memory, then after performing initial problem determination, it may be necessary to either increase the amount of memory available or reduce the requirements for memory on the system. The former might involve increasing the available RAM or increasing the amount of swap or paging space. The latter might involve stopping applications which are not required, that have high memory requirements or reducing the amount of broker processes or instances running on the system.
- BIP2102
- Invalid value (<insert_1>) for attribute (<insert_2>); node class=<insert_3>.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified a value for the indicated attribute of the node class. However, this value could not be converted to a wide string. The configuration request is terminated.
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request.
- BIP2103
- Internal broker error; condition=<insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An internal software error has occurred in the message broker. The operation of the message broker is likely to be affected and may now be unpredictable. An internal condition is displayed which describes the internal error situation which occurred.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2104
- Error whilst retrieving username for uid <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The message broker caused an exception whilst retrieving the username for uid <insert_1>. Check the userid setup for the uid listed.
- Response
- On Distributed check that the userid listed has a default group. On z/OS check that the userid has a default GID and an OMVS segment.
- BIP2105
- Multiple messages with the same identifier have been received when the order mode on the MQInput node is set to 'By User ID'; Condition = <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. The operation of the message broker is likely to be affected and might be unpredictable. This error can occur when the unique identifier of the message has already been used by this thread.
- Response
- Ensure that a new unique identifier is generated for each message that you are passing to the MQInput node when you set the order mode to 'By User Id'.
- BIP2106
- Unable to allocate memory during operation performed by object <insert_1>.
- Severity
- 20 : Error
- Explanation
- An Execution Group performed an operation which needed to allocate memory, but the request failed because insufficient memory was available. The execution group process will be stopped and an attempt made to restart it.
- Response
- Since this is indicative of a shortage of memory, it may be necessary (after performing initial problem determination) to either increase the amount of memory available or reduce the system's requirement for memory. The former might involve increasing the available RAM or increasing the amount paging space. The latter might involve stopping applications which are not required or which have high memory requirements and reducing the amount of broker processes running on the system.
- BIP2107
- An error occurred when trying to load a resource bundle containing <insert_1> appropriate to the current locale. The default resource bundle will be used instead.
- Severity
- 10 : Warning
- Explanation
- The resource bundle for the current locale could not be loaded. The principal reasons that this can happen are because the current locale is invalid or not supported, because the user does not have the correct file permissions, or because of a faulty installation.
- Response
- Check that current locale is in the list of supported locales. Ensure that the user has the correct authorities and permissions. Check that the installation was successful and has not been corrupted. If the problem persists contact your IBM support center.
- BIP2108
- An error occurred when trying to load a resource bundle containing <insert_1> appropriate to the current locale. No resource bundles could be found.
- Severity
- 20 : Error
- Explanation
- Neither the resource bundle for the current locale or the default resource bundle could be loaded. The principal reasons that this can happen are because the user does not have the correct file permissions, or because of a faulty installation.
- Response
- Ensure that the user has the correct authorities and permissions. Check that the installation was successful and has not been corrupted. If the problem persists contact your IBM support center.
- BIP2109
- An error occurred while retrieving a value from a resource bundle. Lookup of <insert_1> <insert_2> from resource <insert_3> in locale <insert_4> failed with error <insert_5>.
- Severity
- 20 : Error
- Explanation
- The value could not be found in the resource bundle using the specified lookup information. This may be because the lookup information is wrong, because the value does not exist in the resource bundle, because the user does not have the correct file permissions, or because of a faulty installation.
- Response
- Ensure that the lookup information is valid. Check that current locale is in the list of supported locales. Ensure that the user has the correct authorities and permissions. Check that the installation was successful and has not been corrupted. If the problem persists contact your IBM support center.
- BIP2110
- Message broker internal program error.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. There is no diagnostic information associated with this message
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2111
- Message broker internal error: diagnostic information <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: <insert_1>.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2112
- Message broker internal error: diagnostic information <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2113
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2114
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2115
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2116
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2117
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2118
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2119
- Message broker internal error: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2120
- Either the message tree has a properties folder that is not the first element of the message tree, or it has two properties folders.
- Severity
- 20 : Error
- Explanation
- The Properties folder holds information about the characteristics of the message. If present, there must be only one properties folder and it must be the first element of the message tree, otherwise its fields will not have the desired effect.
- Response
- Review the message flow and ESQL that caused this error and make sure that only one properties folder has been created, and that it is the first element of the message tree. By default, every occurrence of OutputRoot has a properties folder created automatically and a user should not create an additional one.
- BIP2121
- The thread bootstrap code caught an unhandled exception on thread number <insert_1> with name <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread number <insert_1> with name <insert_2>. Further information may be in the exception information associated with this message: <insert_3>.
- Response
- Restart the broker. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.
- BIP2122
- An exception has been caught in thread clean up: diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.
- BIP2123
- Thread terminate handler invoked: execution group will end; diagnostic information <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.
- BIP2124
- The execution group has detected a condition on thread number <insert_1> with name <insert_2>, which requires it to shutdown and restart.
- Severity
- 20 : Error
- Explanation
- The execution group has detected a condition which requires it to shut down and restart. Further messages will indicate the cause of this condition. An exception was issued on thread number <insert_1> with name <insert_2>. Further information may be in the exception information associated with this message: <insert_3>.
- Response
- Check the system log for messages that indicate the cause of this condition. Resolve the issue that caused the condition, and check the system log to ensure that the execution group starts again without error.
- BIP2125
- The monitoring profile referenced in flow <insert_1> by node <insert_2> contains a query expression: <insert_3> that is not valid.
- Severity
- 10 : Warning
- Explanation
- An event message emitted by node <insert_2> in flow <insert_1> is incomplete because the query <insert_3> cannot be used to update the contents of the event message.
- Response
- Refer to the following messages for details of the error.
- BIP2126
- The monitoring profile: <insert_1> referenced in message flow <insert_2>, is either incorrectly named or has not been created.
- Severity
- 10 : Warning
- Explanation
- The message flow attribute 'monitoringProfile' has been set, but there is no monitoring profile with the specified name. The message flow continues to use the monitoring properties on its nodes, if any have been set.
- Response
- Set the message flow attribute 'monitoringProfile' to the correct value, or create and populate a monitoring profile with the specified name.
- BIP2127
- The maximum column size for the broker has been exceeded.
- Severity
- 20 : Error
- Explanation
- An attempt was made to access a column of size <insert_1> .
- BIP2130
- Error <insert_2> converting a character string to or from codepage <insert_1>.
- Severity
- 20 : Error
- Explanation
- A character conversion between codepages has failed. This may be due to an invalid codepage being specified in the header of a message, or may be due to a character being present in a message that does not appear in the required codepage conversion table.
- Response
- Check that the application that generated the message is using a valid codepage in the message header and that all characters used are valid in that codepage.
- BIP2131
- A character codepage conversion error has occurred.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the message broker.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP2132
- Invalid codepage <insert_1> or conversion table <insert_2> missing or invalid.
- Severity
- 20 : Error
- Explanation
- A codepage is being used for which there is no corresponding character conversion table, or the conversion table cannot be used, or the conversion table is invalid.
- Response
- Check that the application generating the source message is using the correct code page within the message.
- BIP2133
- Source field <insert_1> is too long for a target field of length <insert_2> when converting from Unicode to codepage <insert_3>.
- Severity
- 20 : Error
- Explanation
- When the character data in the source field is converted to the target codepage, the resulting character string is longer than the defined length of the target field.
- Response
- Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified, bearing in mind the codepage required for the message, and check that the origin of the data within the source field is providing correct data.
- BIP2134
- Source field <insert_1> is too long for a target field of length <insert_2> when converting to Unicode from codepage <insert_3>.
- Severity
- 20 : Error
- Explanation
- An internal processing error has occurred.
- Response
- Contact your IBM support center.
- BIP2135
- Source character <insert_1> in field <insert_2> cannot be converted to Unicode from codepage <insert_3>.
- Severity
- 20 : Error
- Explanation
- The source character is an invalid code point within the given codepage.
- Response
- Correct the application that generated the message.
- BIP2136
- Source character <insert_1> in field <insert_2> cannot be converted from Unicode to codepage <insert_3>.
- Severity
- 20 : Error
- Explanation
- The source character is an invalid code point within the given codepage.
- Response
- Correct the application or message flow that generated the message to ensure that all data within the message can be represented in the target codepage.
- BIP2137
- A call to create a new thread has failed.
- Severity
- 20 : Error
- Explanation
- This can be caused by insufficient kernel resources.
- Response
- Please check and if necessary increase the max_thread_proc setting in your kernel to at least the value specified in the Information Center (topic au16640_).
- BIP2141
- Unable to open WebSphere MQ queue manager object; MQCC=<insert_1>, MQRC=<insert_2>2
- Severity
- 20 : Error
- Explanation
- An attempt to open the connected WebSphere MQ queue manager to inquire about its settings failed. The WebSphere MQ completion code and reason code returned are as displayed. Recovery processing of a backed out message may not work as expected.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2142
- Unable to issue MQINQ to inquire on WebSphere MQ queue; queue=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 20 : Error
- Explanation
- An attempt to issue an MQINQ function to inquire about the status of the specified queue failed. The WebSphere MQ completion code and reason code returned are as displayed. Recovery processing of a backed out message will not work as expected.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2143
- Unable to close WebSphere MQ queue manager object; MQCC=<insert_1>, MQRC=<insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt to close the connected WebSphere MQ queue manager failed. The WebSphere MQ completion code and reason code returned are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2144
- Node <insert_1> received conversion error on either WebSphere MQ queue manager or queue name.
- Severity
- 20 : Error
- Explanation
- The specified node was unable to convert the WebSphere MQ queue manager or queue name to a wide string. The current message flow is terminated.
- Response
- Check the message flow to determine the cause of the error.
- BIP2145
- Failed to connect to WebSphere MQ queue manager <insert_1>; MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 20 : Error
- Explanation
- The specified node failed to connect to the indicated WebSphere MQ queue manager. The completion and reason codes returned by the MQCONN are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If the open failed because the queue manager did not exist, then define this object to WebSphere MQ. If the failure of the open was because an incorrect queue manager name was specified, then correct the message flow configuration and attempt to redeploy the message broker.
- BIP2146
- A required property <insert_1> was not specified in the DataCapture API request.
- Severity
- 20 : Error
- Explanation
- A DataCapture API request was made which requires a mandatory parameter <insert_1> which was not provided. Refer to the information center topic on "Data Capture" and the Message Broker API Documentation.
- Response
- Provide the missing property and attempt the request again. If the problem persists, contact your IBM support center.
- BIP2147
- A DataCapture API request was made with a parameter <insert_1> that has an invalid value <insert_2>.
- Severity
- 20 : Error
- Explanation
- A DataCapture API request was made which contained a parameter <insert_1> which was was invalid. Refer to the information center topic on "Data Capture" and the Message Broker API Documentation.
- Response
- Correct the property value and attempt the request again. If the problem persists, contact your IBM support center.
- BIP2148
- DataCapture API request contained a reference to a non-existent configurable service <insert_1> of type <insert_2>.
- Severity
- 20 : Error
- Explanation
- A DataCapture API request was made, which names a configurable service <insert_1> which does not exist. Refer to the information center topic on "Data Capture" and the configurable service settings.
- Response
- Define the configurable service and retry the request. If the problem persists, contact your IBM support center.
- BIP2149
- A DataCapture request was made for data of type <insert_1> associated with message <insert_2> but no data matched the criteria.
- Severity
- 20 : Error
- Explanation
- A request was made using the DataCapture API for message data associated with message <insert_2>, but no data could be provided for the specified filter <insert_1>. Refer to the information center topic on "Data Capture" and the configurable service settings.
- Response
- Check that the API request is valid for the message concerned and that the requested data was correctly recorded. If the problem persists, contact your IBM support center.
- BIP2150
- About to load <insert_1>.
- Severity
- 0 : Information
- Explanation
- An execution group is about to load a library. Includes IBM and non IBM user defined nodes and parsers.
- Response
- No user action required.
- BIP2151
- Loaded library <insert_1>.
- Severity
- 0 : Information
- Explanation
- An execution group has loaded a library.
- Response
- No user action required.
- BIP2152
- Configuration message received from broker.
- Severity
- 0 : Information
- Explanation
- An execution group received a command from the Broker.
- Response
- No user action required.
- BIP2153
- About to <insert_1> an execution group.
- Severity
- 0 : Information
- Explanation
- An execution group is about to perform an action.
- Response
- No user action required.
- BIP2154
- Execution group finished with Configuration message.
- Severity
- 0 : Information
- Explanation
- A command response will be sent to the broker.
- Response
- No user action required.
- BIP2155
- About to <insert_1> the deployed resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- Explanation
- An execution group is about to perform an action.
- Response
- No user action required.
- BIP2156
- Web user interface did not initialize because the listening port <insert_1> could not be started.
- Severity
- 0 : Information
- Explanation
- The web user interface attempted to start, but the HTTP listener <insert_1> could not be started. It is likely that another broker has already created a listener on this port. You can change the port number for the web user interface by using the Message Broker Explorer or the command 'mqsichangeproperties [broker] -b webadmin -o HTTP[S]Connector -n port -v [new port]'
- Response
- Check that the port is not already in use and that the user ID under which Message Broker is running has the necessary permission to open that port.
- BIP2157
- A recorded message has been backed out to the backout queue <insert_1>
- Severity
- 0 : Information
- Explanation
- The DataCapture store was unable to process a message and so has sent the message to the backout queue <insert_1>.
- Response
- Examine previous messages and your DataCapture Store to determine why the message is being backed out. Defining the 'backoutQueue' will cause messages which cannot be processed by the DataCapture Store to be sent to this queue.
- BIP2158
- Execution group <insert_1> has no data capture stores configured for recording.
- Severity
- 0 : Information
- Explanation
- The data capture recording process has been started. However, the DataCaptureSource and DataCaptureStore configurable services have been checked and the execution group <insert_1> has no valid data capture stores that require the recording process to start. A valid data capture source must specify a valid data capture store, for which the 'egForRecord' setting specifies an execution group.
- Response
- Ensure that the API request is valid for the message and that the requested data was recorded correctly. For more information, see the information center topics on "Recording data" and "Configurable services properties". If the problem persists, contact your IBM support center.
- BIP2159
- Execution group <insert_1> is now recording data for the following data capture stores: <insert_2>.
- Severity
- 0 : Information
- Explanation
- The data capture recording process has been started. The DataCaptureSource and DataCaptureStore configurable services have been checked, and the execution group <insert_1> will record data for data capture stores <insert_2>. A valid data capture source specifies a valid data capture store, for which the 'egForRecord' setting specifies an execution group.
- Response
- None
- BIP2160
- Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: <insert_1>.
- Severity
- 20 : Error
- Explanation
- A broker process is terminating abnormally.
- Response
- Contact your IBM support center.
- BIP2161
- Broker process terminating abnormally (stack full): diagnostic information for IBM <insert_1>.
- Severity
- 20 : Error
- Explanation
- A broker process is terminating abnormally because its stack is full. For execution group processes, this may be caused by message flows containing loops or more than 500 nodes in series. Otherwise the following information will be required when contacting IBM: <insert_1>.
- Response
- Check the definitions of all message flows deployed on the named execution group for loops and excessive path length. If this does not resolve the problem, contact your IBM support center.
- BIP2162
- Header invalid, structure identifier incorrect at offset <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A parser was constructed to process part of a message. That part of the message does not appear to be a valid bitstream for the parser constructed.
- Response
- Contact your IBM support center.
- BIP2163
- User environment is invalid.
- Severity
- 30 : Severe error
- Explanation
- The user environment was not adequately prepared to continue execution. Locate and run the profile supplied with the product. This file is called mqsiprofile, and is located in the bin subdirectory for the product.
- Response
- Run the product profile. Also ensure that the user environment is prepared for database access. Use the Documentation supplied with this product and the database to complete this operation.
- BIP2164
- An error occurred while opening registry file <insert_1> to read it : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The program cannot proceed, because it cannot read the value in the registry for this key.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2165
- An error occurred while reading registry file <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker cannot proceed, because it cannot read the value in the registry for this key.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2166
- An error occurred while opening registry file <insert_1> to write it : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The program cannot proceed, because it cannot record the value in the registry for this key.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2167
- An error occurred while writing registry file <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The program cannot proceed, because it cannot write the value in the registry for this key.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2168
- An error occurred while deleting files from registry directory <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- Some of the files in the broker registry have not been deleted.
- Response
- Ask your WebSphere Message Broker administrator to check why the files could not be deleted, then retry the mqsidelete command.
- BIP2169
- An error occurred while deleting the registry directory <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker registry has not been deleted.
- Response
- Ask your WebSphere Message Broker administrator to check why the registry directory could not be deleted, then retry the mqsidelete command.
- BIP2170
- The registry is already locked.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2171
- An error occurred while opening the registry lock file <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- You do not have sufficient UNIX file system permissions to administer the broker.
- Response
- Ask your WebSphere Message Broker administrator to add you to the 'mqbrkrs' group on UNIX systems or to a group that has the correct authorities on z/OS. After this has been done, log in again and reissue the command.
- BIP2172
- An error occurred while locking the registry file <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2173
- An error occurred while writing to the registry lock file <insert_1> : <insert_2>.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2174
- The registry was not locked.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2175
- An error occurred while unlocking the registry lock file : <insert_1>.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2176
- Could not find message <insert_1> in catalogue <insert_2>, inserts are <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9>.
- Severity
- 30 : Severe error
- Explanation
- The required message could not be located in the specified catalogue.
- Response
- Ensure that the message catalogue is available. This failure usually occurs if the environment variable NLSPATH is not correctly set.
- BIP2177
- Tried to create two name managers
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Broker administrator.
- BIP2178
- Failed to create a UUID (Error code = <insert_1>).
- Severity
- 20 : Error
- Explanation
- The system could not create a UUID.
- Response
- None.
- BIP2179
- Failed to convert an ImbWstring to an ImbUuidValue (Error code = <insert_1>).
- Severity
- 20 : Error
- Explanation
- The system could not convert the input ImbWstring to an ImbUuidValue.
- Response
- Make sure the input is valid.
- BIP2180
- Failed to convert a UUID string to an ImbUuidValue (Error code = <insert_1>).
- Severity
- 20 : Error
- Explanation
- The system could not convert the input UUID string to an ImbUuidValue.
- Response
- Make sure the input UUID string is in the right format.
- BIP2181
- Failed to convert a UUID string to an ImbByteArray (Error code = <insert_1>).
- Severity
- 20 : Error
- Explanation
- The system could not convert the input UUID string to an ImbByteArray.
- Response
- Make sure the input UUID string is valid.
- BIP2182
- Failed to convert an ImbByteValue to a string (Error code = <insert_1>).
- Severity
- 20 : Error
- Explanation
- The system could not convert the input ImbByteValue to a string.
- Response
- Make sure the input ImbByteArray is valid.
- BIP2183
- The beta license for this product has expired.
- Severity
- 30 : Severe error
- Explanation
- The license for the beta version of this product has expired. Please contact your IBM representative for a full (GA) version of this product.
- Response
- Please contact your IBM representative for a full license.
- BIP2184
- The license for the beta version of this product will expire in <insert_1> days.
- Severity
- 10 : Warning
- Explanation
- Please contact your IBM representative to obtain the full (GA) version of this product before this time. After <insert_1> days have passed, this product will cease to function.
- Response
- Please contact your IBM representative to obtain the GA version of this product before this time.
- BIP2185
- Unable to redirect <insert_1> to file <insert_2>. The broker was unable to open <insert_2>. The operating system return code <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The broker was unable to redirect <insert_1> as it was unable to open the redirect file.
- Response
- Check the return code and restart the broker.
- BIP2186
- A component attempted to read a log file that was too large for it to handle.
- Severity
- 10 : Warning
- Explanation
- A request was sent to a component to read its log. While preparing the resulting output to send back, it detected that it was over the maximum message size for the transport used.
- Response
- To read the log directly from the file, please issue the mqsireadlog command, specifying the -f flag.
- BIP2187
- The stack space limit (<insert_1>) was exceeded during flow processing.
- Severity
- 20 : Error
- Explanation
- Stack space is limited to a fixed amount, and the flow exceeded that amount. This problem might be due to a loop in the flow, terminals wired incorrectly, or the flow requiring more stack space than is configured.
- Response
- Fix faulty loops or other invalid flow behavior. If the flow is working as designed, you can increase the amount of stack space by setting the environment variable MQSI_THREAD_STACK_SIZE.
- BIP2188
- The stack space limit was exceeded during the handling of a stack overflow exception.
- Severity
- 20 : Error
- Explanation
- Stack space is limited to a fixed amount, and the flow exceeded that amount. During processing of the resulting exception, the extra stack space reserved for exception handling was also used up.
- Response
- Fix the original stack overflow. Change the exception-handling flow to use fewer nodes and simpler constructs.
- BIP2189
- ActivityLog configurable service <insert_1> property <insert_2> has an invalid value <insert_3>.
- Severity
- 20 : Error
- Explanation
- The ActivityLog configurable service definition <insert_1> has an invalid value. The log defined by this configurable service has been disabled. Correct the property <insert_2> to allow this log to be enabled.
- Response
- Correct the configurable service property and restart the message broker. If the problem still continues to occur contact your IBM support center.
- BIP2190
- ActivityLog configurable service <insert_1> has a fileName property <insert_3> which conflicts with configurable service <insert_2>.
- Severity
- 20 : Error
- Explanation
- The ActivityLog configurable service definition <insert_1> defines a fileName property with value <insert_3> which is already defined in another ActivityLog configurable service <insert_2>. It is not valid to define two ActivityLog configurable services to write to the same file. Modify one of these configurable service definitions to avoid this conflict.
- Response
- Correct the configurable service property and restart the message broker. If the problem still continues to occur contact your IBM support center.
- BIP2191
- ActivityLog configurable service <insert_1> is missing a mandatory property <insert_2>.
- Severity
- 20 : Error
- Explanation
- The ActivityLog configurable service definition <insert_1> requires property <insert_2> to be set. The configurable service is therefore ignored and the file log has been disabled.
- Response
- Correct the configurable service property and restart the message broker. If the problem still continues to occur contact your IBM support center.
- BIP2192
- The message flow, <insert_1>, could not be deployed because the required subflow, <insert_2>, is not deployed.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to deploy message flow, <insert_1>, but the required subflow, <insert_2>, is not deployed.
- Response
- Deploy the required subflow, <insert_2>, and then redeploy the message flow, <insert_1>. If the problem persists contact your IBM support center.
- BIP2193
- Data capture has been disabled in this execution group.
- Severity
- 0 : Information
- Explanation
- The execution group has been explicitly configured to disable data capture support. This overrides any settings in the DataCaptureSource and DataCaptureStore configurable services.
- BIP2194
- The value of property <insert_1> in configurable service <insert_2> of type <insert_3> is not valid.
- Severity
- 20 : Error
- Explanation
- The configurable service <insert_2> has a property <insert_1> that contains an invalid value. Refer to the information center topic on "Data Capture" and the configurable service settings.
- Response
- Correct the named property on the configurable service and restart the execution group. If the problem persists, contact your IBM support center.
- BIP2195
- Startup of DataCapture configurable service <insert_1> of type <insert_2> has resulted in a WebSphere MQ failure. The WebSphere MQ Completion code is <insert_3> and the reason code is <insert_4>.
- Severity
- 20 : Error
- Explanation
- There is a DataCapture configurable service called <insert_1> of type <insert_2>. During startup processing, the execution group has received a failure when calling WebSphere MQ, with completion code <insert_3> and reason code <insert_4>.
- Response
- Check the WebSphere MQ resources or correct the configurable service and restart the execution group. If the problem persists, contact your IBM support center.
- BIP2196
- A database error occurred when processing a message for the data capture store <insert_1>.
- Severity
- 20 : Error
- Response
- Check that the database is correctly defined and available, and that the ODBC definition is correct. Review any other messages written to the system log and check the database logs to determine the cause of the failure. If the problem persists, contact your IBM support center.
- BIP2197
- A parsing error occurred when processing a message for data capture store <insert_1>. The error was <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message was placed on the backout queue.
- Response
- The message could not be parsed correctly and thus could not be recorded to the database. The message has been placed on the backout queue for manual processing. If the problem persists, contact your IBM support center.
- BIP2198
- An MQ Subscription could not be removed. The subscription is called <insert_1> and the MQ Reason code was <insert_2>.
- Severity
- 20 : Error
- Explanation
- A Data Capture Source configurable service represents a durable WebSphere MQ Subscription to a publish-subscribe topic. This configurable service is being deleted and the associated subscription could not be removed. The subscription is called <insert_1> and the MQ Reason code was <insert_2>.
- Response
- The MQ reason code should resolve the reason why the subscription could not be removed. Either remove the subscription manually or resolve the issue and retry deleting the configurable service. If the problem persists, contact your IBM support center.
- BIP2201
- Execution group (32) started: process <insert_11>; thread <insert_12>; additional information: brokerName <insert_1> (operation mode <insert_14>); executionGroupUUID <insert_2>; executionGroupLabel <insert_3>; queueManagerName <insert_4>; trusted <insert_5>; userId <insert_6>; migrationNeeded <insert_7>; brokerUUID <insert_8>; filePath <insert_9>; workPath <insert_10>; ICU Converter Path <insert_13>; ordinality <insert_15>.
- Severity
- 0 : Information
- Explanation
- The execution group has started and will now start to process messages.
- Response
- No user action required.
- BIP2202
- Administrative agent to execution group communication error: invalid value <insert_2> supplied for execution group parameter <insert_1>.
- Severity
- 20 : Error
- Explanation
- The invalid value <insert_2> was supplied for the execution group parameter <insert_1>.
- Response
- Stop and restart the broker. If the problem persists, stop, delete, recreate and then restart the broker.
- BIP2203
- An execution group has encountered a problem whilst starting.
- Severity
- 20 : Error
- Explanation
- An execution group has encountered a problem whilst starting and is unable to continue.
- Response
- Check the following error messages to try to identify the cause of the problem. If it is unclear what the cause is, and the problem occurs continually after restarting the message broker contact your IBM support center.
- BIP2204
- Execution group using process <insert_1> thread <insert_2> stopped.
- Severity
- 0 : Information
- Explanation
- The execution group using process <insert_1> and thread <insert_2> has stopped. This may be because it has been instructed to do so or because it has encountered a problem.
- Response
- No user action required. The execution group will be restarted automatically if need be.
- BIP2208
- Execution group (64) started: process <insert_11>; thread <insert_12>; additional information: brokerName <insert_1> (operation mode <insert_14>); executionGroupUUID <insert_2>; executionGroupLabel <insert_3>; queueManagerName <insert_4>; trusted <insert_5>; userId <insert_6>; migrationNeeded <insert_7>; brokerUUID <insert_8>; filePath <insert_9>; workPath <insert_10>; ICU Converter Path <insert_13>; ordinality <insert_15>.
- Severity
- 0 : Information
- Explanation
- The execution group has started and will now start to process messages.
- Response
- No user action required.
- BIP2209
- Invalid configuration message: attribute <insert_1> must be set when attribute <insert_2> has value <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message setting attribute <insert_2> to value <insert_3>. This setting requires a value for attribute <insert_1>.
- Response
- Set the value of <insert_1> and redeploy.
- BIP2210
- Invalid configuration message: attribute name <insert_1> not valid for target object <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing the attribute name <insert_1> which is not valid for the target object <insert_2>. This can be caused by a mismatch in levels between the Message Broker Toolkit and the broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Message Broker Toolkit.
- Response
- Ensure that the levels of code installed at the Message Broker Toolkit and broker are consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
- BIP2211
- Invalid configuration message containing attribute value <insert_2>, which is not valid for target attribute <insert_1>, object <insert_4>; valid values are <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing the attribute value <insert_2>, which is not valid for the target attribute <insert_1>, on object <insert_4>. Valid values are <insert_3>. This can be caused by a mismatch in levels between the Message Broker Toolkit and the broker. Or it can be caused as a result of a node defined by a user, or written by a third party, where the implementation library installed at the broker does not match the node definition held at the Message Broker Toolkit.
- Response
- Ensure that the levels of code installed at the Message Broker Toolkit and broker are consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
- BIP2212
- Invalid configuration message containing action <insert_1> which is not valid for target object <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing the action <insert_1> which is not valid for the target object <insert_2>. This can be caused by a mismatch in levels between the Message Broker Toolkit and the broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Message Broker Toolkit.
- Response
- Ensure that the levels of code installed at the Message Broker Toolkit and broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
- BIP2213
- Invalid configuration message containing folder <insert_1> which is not valid for target object <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing the folder <insert_1> which is not valid for the target object <insert_2>. This can be caused by a mismatch in levels between the Message Broker Toolkit and the broker, or as a result of a user or third party written plug-in node where the implementation library installed at the broker does not match the node definition held at the Message Broker Toolkit.
- Response
- Ensure that the levels of code installed at the Message Broker Toolkit and broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
- BIP2214
- Invalid configuration message with no value for attribute <insert_1>, object <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker received a configuration message which failed to supply a value for the attribute <insert_1>, on object <insert_2>. This can be caused by a mismatch in levels between the Message Broker Toolkit and the broker, or as a result of a user or third party written user-defined node where the implementation library installed at the broker does not match the node definition held at the Message Broker Toolkit.
- Response
- Ensure that the levels of code installed at the Message Broker Toolkit and broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this is IBM, contact your IBM support center.
- BIP2215
- Node <insert_3> property <insert_1> has been overridden by the value <insert_2> from the LocalEnvironment.
- Severity
- 0 : Information
- Explanation
- Local environment variables override their corresponding node attributes.
- Response
- None.
- BIP2216
- Node <insert_4> could not use the value <insert_2> from the LocalEnvironment for overriding property <insert_1>. The value is not valid; valid values are <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The value is not valid for that property.
- Response
- Make sure only one of the <insert_3> values is used.
- BIP2217
- File name <insert_1> is invalid for resource manager <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker is given a file name <insert_1> which is not valid for the resource manager <insert_2>. This may be an invalid/unknown file name extension or simply an invalid file path.
- Response
- Ensure a valid file name is provided.
- BIP2218
- Node <insert_2> could not use the value <insert_1> from the LocalEnvironment for overriding property 'messageDomainProperty'. The value is not valid.
- Severity
- 10 : Warning
- Explanation
- The value is not valid for that property.
- Response
- Ensure that the value of the attribute is correct and that all the required parse implementation libraries have been installed, then redeploy the message flow.
- BIP2222
- Invalid state: no records found for resource <insert_1>, <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker could not locate records for the resource <insert_1>, <insert_2> within its configuration store. The active state of the broker might not be as expected.
- Response
- Check for previous errors in the system event log, which might describe the cause of failure. Redeploying the complete broker configuration by using the Message Broker Toolkit, the mqsideploy command, or the Message Broker Administration API, might solve the problem. If the problem persists, contact your IBM support center.
- BIP2225
- An unexpected return code <insert_1> was received from a thread state change callback function.
- Severity
- 10 : Warning
- Explanation
- A function which registered for thread state change callback with user context <insert_2> and state type <insert_3> has returned a value of <insert_1>.
- Response
- If you have a user-defined extension running within the execution group, ensure that any callbacks return one of the expected values.
- BIP2226
- firstAbort specified - calling abort()
- Severity
- 20 : Error
- Explanation
- An abnormal event has taken place, and the specified abend action was firstAbort. A core file should have been generated.
- Response
- Examine any core files produced.
- BIP2227
- Error encountered during abend processing: <insert_1> - terminating.
- Severity
- 20 : Error
- Explanation
- An abnormal event has taken place, and the diagnostic routines could not complete successfully.
- Response
- None
- BIP2228
- Severe error: <insert_1> <insert_2> <insert_3> Abend file: <insert_4> action: <insert_5>.
- Severity
- 20 : Error
- Explanation
- An abnormal event has taken place. See the referenced abend file for details
- Response
- Correct the problem that caused the abnormal event.
- BIP2229
- <insert_1> <insert_2>.
- Severity
- 20 : Error
- Explanation
- An abnormal event has taken place, and the diagnostic routines could not complete successfully.
- Response
- Ensure that the standard location for the storage of abend files is writable.
- BIP2230
- Error detected whilst processing a message in node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst processing a message in node <insert_1>. An exception has been thrown to cut short the processing of the message.
- Response
- See the following messages for details of the error.
- BIP2231
- Error detected whilst processing a message in node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst processing a message in node <insert_1>. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
- Response
- See the following messages for details of the error.
- BIP2232
- Error detected whilst handling a previous error in node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker has detected an error in node <insert_1> whilst handling a previous error.
- Response
- See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
- BIP2233
- Invoking user-defined extension <insert_1>(<insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>).
- Severity
- 0 : Information
- Explanation
- About to invoke the specified user-defined extension with the specified parameters.
- Response
- No user action required.
- BIP2234
- Returned from user-defined extension <insert_1> with result: <insert_2>.
- Severity
- 0 : Information
- Explanation
- The execution of the specified user-defined extension has been completed with the specified result.
- Response
- No user action required.
- BIP2235
- An error occurred while opening LIL directory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An error occurred while opening LIL directory <insert_1>. This directory may not exist, or may be unreadable by the broker.
- Response
- Ensure that all directories contained in the LIL path are valid and readable by the broker.
- BIP2236
- Product LIL directory <insert_1> is not the first entry in LIL path <insert_2>.
- Severity
- 10 : Warning
- Explanation
- Product LIL directory <insert_1> is not the first entry in LIL path <insert_2>. This may interfere with core broker functionality, and cause unexpected behavior during broker operation.
- Response
- Change the broker LIL path to include the product LIL directory as the first entry.
- BIP2237
- Product LIL directory <insert_1> is not included in LIL path <insert_2>.
- Severity
- 20 : Error
- Explanation
- Product LIL directory <insert_1> is not included in LIL path <insert_2>. Core broker functionality may be not be available during broker operation, and unexpected behavior may result.
- Response
- Change the broker LIL path to include the product LIL directory.
- BIP2238
- LIL <insert_1> has been unloaded.
- Severity
- 10 : Warning
- Explanation
- LIL <insert_1> has been unloaded. This could be because it contained no resources, or because the resources were already provided by another LIL.
- Response
- Ensure that all LILs contain valid, non-duplicate resources.
- BIP2239
- LIL <insert_1> contains no valid resource entry points.
- Severity
- 10 : Warning
- Explanation
- LIL <insert_1> contains at least one entry point, but none are valid. See earlier messages for more details on the exact error.
- Response
- Please ensure that the specified LIL contains only valid, non-duplicate resources.
- BIP2240
- Existing message flow <insert_3> already contains message flow node <insert_2> (uuid=<insert_1>).
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create the message flow node <insert_2> (uuid=<insert_1>), but this node already exists in the message flow <insert_3>.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2241
- A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type <insert_1> in message flow <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker received an instruction to create a message flow node of type <insert_1>, in message flow <insert_2>. The broker cannot create nodes of this type because an implementation library for this node type does not exist in the LIL path.
- Response
- Ensure that the LIL path is correct, and that it contains all the required node implementation libraries, including those supplied by IBM. The node name is case sensitive, therefore check that the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode', ensure that when the node was registered with the toolkit the name registered did not end in 'Node'.
Also ensure that you have saved the message flow, and any nested message flows. Redeploy the new configuration to the broker, specifying a complete configuration. If the LIL file is correct, check that the message node type is correct.
- BIP2242
- Message flow <insert_2> could not be reconfigured because it remained busy for longer than the timeout period of <insert_1>
- Severity
- 20 : Error
- Explanation
- A request to reconfigure the message flow <insert_2> was received but this could not be processed because it remained busy processing a message for longer than the timeout specified.
- Response
- This can be caused by the timeout being too short considering the complexity of the flow and the size of the messages being processed. In such cases the timeout should be increased. It can also be caused by message flows containing infinite loops. In such cases the SQL should be corrected.
- BIP2243
- Message flow <insert_2> cannot find message flow node <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to handle the message flow node <insert_1>, but this node does not exist in the message flow <insert_2>.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2244
- Request to create a connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: connection already exists in message flow <insert_7>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but this connection already exists in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2245
- Request to create connection between node uuid=<insert_1> (label unknown) terminal <insert_2>, and node <insert_4> (uuid=<insert_3>) terminal <insert_5>: source could not be found in message flow <insert_6>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but the source node could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2246
- Request to create connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: source terminal could not be found in message flow <insert_7>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but the source terminal could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2247
- Request to create connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node uuid=<insert_4> (label unknown) terminal <insert_5>: target cannot be found in message flow <insert_6>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but the target node could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2248
- Request to create connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>;', and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: terminal cannot be found in message flow <insert_7>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but the target terminal could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2249
- Request to create connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: connection does not exist in message flow <insert_7>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two node terminals, but this connection does not exist in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2250
- Request to delete connection between node uuid=<insert_1> (label unknown) terminal <insert_2>, and node <insert_4> (uuid=<insert_3>) terminal <insert_5>: source does not exist in message flow <insert_6>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete a connection between two node terminals, but the source node could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2251
- Request to delete connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: source terminal does not exist in message flow <insert_7>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete a connection between two node terminals, but the source terminal could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2252
- Request to delete connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node uuid=<insert_4> (label unknown) terminal <insert_5>: target node does not exist in message flow <insert_6>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete a connection between two node terminals, but the target node could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2253
- Request to delete connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6>: target terminal does not exist in message flow <insert_7>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete a connection between two node terminals, but the target terminal could not be found in the message flow.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2254
- Message flow node <insert_3> (uuid=<insert_2>) type <insert_1> in message flow <insert_4> successfully created.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to create a message flow node in the message flow and successfully performed this action.
- Response
- No user action required.
- BIP2255
- Message flow connection successfully created between node <insert_2> (uuid=<insert_1>) terminal <insert_3> and node <insert_5> (uuid=<insert_4>) terminal <insert_6>.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action.
- Response
- No user action required.
- BIP2256
- Attribute of message flow node <insert_2> (uuid=<insert_1>) in message flow <insert_3> successfully changed.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to change an attribute of the message flow node <insert_2> (uuid=<insert_1>,) in the message flow <insert_3> and successfully performed this action.
- Response
- No user action required.
- BIP2257
- Request to change an attribute of message flow node <insert_1>: node does not exist in message flow <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to change an attribute of the message flow node <insert_1>, but this node does not exist in the message flow <insert_2>.
- Response
- Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2258
- Message flow node <insert_2> (uuid=<insert_1>) in message flow <insert_3> successfully deleted.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to delete the message flow node <insert_2> (uuid=<insert_1>), in the message flow <insert_3> and successfully performed this action.
- Response
- No user action required.
- BIP2259
- Connection between node <insert_2> (uuid=<insert_1>) terminal <insert_3>, and node <insert_5> (uuid=<insert_4>) terminal <insert_6> successfully deleted.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to delete the connection between two nodes and successfully performed this action.
- Response
- No user action required.
- BIP2260
- Invalid node class name <insert_1> in loadable implementation library <insert_2>
- Severity
- 20 : Error
- Explanation
- The message broker detected the node factory attempting to register an invalid node class name. Node class names must end in 'Node'.
- Response
- Contact the author or supplier of the loadable implementation library and obtain a version which satisfies the node class name requirement.
- BIP2261
- Node class name <insert_1> for use in library <insert_2> already registered in library <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker detected the node factory in loadable implementation library <insert_2> attempting to register the node class name <insert_1>, but this name has already been registered with the broker by the node factory in the library <insert_3>.
- Response
- If the two loadable implementation libraries are different instantiations of the same node, then remove one of the two from the 'bin' directory for the message broker. If the two loadable implementation libraries are for different nodes, then contact the author or supplier of the nodes and request that one changes the registered node class name.
- BIP2262
- Request to create deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>): deployed resource already exists.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an instruction to create the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>), but this deployed resource already exists.
- Response
- Ensure that the deployed resource, and any nested deployed resources have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2263
- Request to delete deployed resource <insert_1> of type <insert_2> : deployed resource does not exist.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete the deployed resource <insert_1>, but this message flow does not exist.
- Response
- Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2264
- Deployed resource <insert_2> (uuid=<insert_1>, type=<insert_3>) successfully created.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to create the deployed resource <insert_2> (uuid=<insert_1>, type=<insert_3>), and successfully performed this action.
- Response
- No user action required.
- BIP2265
- Attribute in deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) successfully changed.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to change an attribute in the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) and successfully performed this action.
- Response
- No user action required.
- BIP2266
- Request to change attribute in deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>): deployed resource does not exist or is predefined.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to change an attribute in the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) but this can not be completed because the deployed resource either does not exist or is predefined.
- Response
- Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2267
- Deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) successfully deleted.
- Severity
- 0 : Information
- Explanation
- The message broker received a configuration message containing an instruction to delete the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>), and successfully performed this action.
- Response
- No user action required.
- BIP2268
- Request to report on deployed resource <insert_1> of type <insert_2> : deployed resource does not exist.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to obtain a report of the deployed resource <insert_1>, but this deployed resource does not exist.
- Response
- Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2269
- Deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) started successfully.
- Severity
- 0 : Information
- Explanation
- The message broker received an operational control message containing an instruction to start the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) and successfully performed this action.
- Response
- No user action required.
- BIP2270
- Request to start deployed resource <insert_1> of type <insert_2> : deployed resource does not exist.
- Severity
- 10 : Warning
- Explanation
- The message broker received an operational control message containing an instruction to start the deployed resource <insert_1>, but this deployed resource does not exist.
- Response
- Ensure that the deployed resource, and any nested deployed resources have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2271
- Deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) successfully stopped.
- Severity
- 0 : Information
- Explanation
- The message broker received an operational control message containing an instruction to stop the deployed resource <insert_2> (uuid=<insert_1>,type=<insert_3>) and successfully performed this action.
- Response
- No user action required.
- BIP2272
- Request to stop deployed resource(s) in parent <insert_1>: deployed resource(s) do not exist.
- Severity
- 10 : Warning
- Explanation
- The message broker received an operational control message containing an instruction to stop one or more deployed resources in <insert_1>, but these deployed resources do not exist.
- Response
- Determine whether or not the deployed resource(s) should exist at the broker. If they should, ensure that the deployed resource(s), and any nested resources have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
- BIP2273
- Request to report on deployed resource <insert_1> of type <insert_2> : deployed resource does not exist.
- Severity
- 10 : Warning
- Explanation
- The message broker received an operational control message containing an instruction to report the status of the deployed resource <insert_1>, but this deployed resource does not exist.
- Response
- No user action required.
- BIP2274
- Invalid database state.
- Severity
- 20 : Error
- Explanation
- The message broker found a configuration record associated with its persistent state of its deployed resource to be empty. The active state of the message broker may be incomplete.
- Response
- Redeploy the broker's configuration from the Message Broker Toolkit, mqsideploy command or a CMP application. If the problem persists contact the IBM support center.
- BIP2275
- Error loading deployed resource <insert_1> of type <insert_2>.
- Severity
- 20 : Error
- Explanation
- The broker's internal record for the deployed resource with internal ID <insert_1> is not valid. The active broker state might not be as expected.
- Response
- See the subsequent message or messages for further details of the error. Restart the broker in a refreshed mqsiprofile environment. If you can identify the failing message flow from the subsequent messages, redeploy the message flow. If the problem persists, contact your IBM Support Center for assistance.
- BIP2276
- The flow <insert_2> which includes a message flow of node type <insert_1> cannot be deployed because the current fix pack function level of <insert_3> does not support this node. To enable this functionality, run the following command: mqsichangebroker <brokerName> -f all
- Severity
- 20 : Error
- Explanation
- The broker received an instruction to create a message flow node of type <insert_1>, in message flow <insert_2>. The broker cannot create nodes of this type because new functionality has not been enabled for this broker. To enable this (and all other) functionality, run the following command: mqsichangebroker <brokerName> -f all
- Response
- Either change the flow to avoid using the unavailable node, or enable new functionality by using the mqsichangebroker command.
- BIP2277
- An error occurred while opening user exit directory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An error occurred while opening the user exit directory <insert_1>. This directory might not exist, or might be unreadable by the broker.
- Response
- Ensure that all directories contained in the user exit path are valid and can be read by the broker. The broker property UserExitPath defines the list of directories, separated by colons (semi-colons on Windows), that are used to search for user exits. Use the -x parameter on the mqsichangebroker command to change this property. You can also set the user exit path by using the environment variable MQSI_USER_EXIT_PATH that is associated with the environment in which the broker is running.
- BIP2278
- An exception was thrown from the user exit <insert_1> function. Details are: user exit name = <insert_2>; source node = <insert_3>; source terminal = <insert_4>; target node = <insert_5> target terminal = <insert_6>.
- Severity
- 20 : Error
- Explanation
- An exception was thrown during the processing of the user exit given above. See the previous exceptions for details of the error. The most likely cause is an error in parsing the message data.
- Response
- Review previous errors to see if the problem can be resolved. If it cannot be resolved, contact the provider of the user exit.
- BIP2279
- The directory <insert_1> has been stated twice or more in the user exit path <insert_2>.
- Severity
- 10 : Warning
- Explanation
- Only the first instance of the directory name will be used, and all others will be ignored.
- Response
- To prevent this warning, remove the second instance of the directory name. The broker property UserExitPath defines the list of directories, separated by colons (semi-colons on Windows), that are used to search for user exits. Use the -x parameter on the mqsichangebroker command to change this property. The user exit path can also be set by using the environment variable MQSI_USER_EXIT_PATH that is associated with the environment in which the broker is running.
- BIP2280
- Invalid installation.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst loading a loadable implementation file. The resource has not been registered.
- Response
- See the following messages for details of the error.
- BIP2281
- Resource name <insert_1> for use in library <insert_2>: name already registered in library <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker detected the resource in loadable implementation library <insert_2> attempting to register the resource name <insert_1>, but this name has already been registered with the broker by the resource in the library <insert_3>.
- Response
- Contact the authors or suppliers of the loadable implementation libraries to resolve the duplicate name situation. Install a new version of at least one of the loadable implementation libraries.
- BIP2283
- The user exit file <insert_1> in directory <insert_2> cannot be loaded because another version of the same user exit file has already been loaded from the directory <insert_3>.
- Severity
- 10 : Warning
- Explanation
- Only the first instance of the user exit file will be used; all others will be ignored.
- Response
- Remove the second instance of the user exit file to prevent this warning.
- BIP2284
- The user plug-in node LIL library <insert_1> in directory <insert_2> cannot be loaded because another version of the same user plug-in node has already been loaded from a different directory.
- Severity
- 10 : Warning
- Explanation
- Only the first instance of the user plug-in node will be used; all others will be ignored.
- Response
- Remove the second instance of the user plug-in node file to prevent this warning.
- BIP2285
- An exception was thrown from the user exit <insert_1> function. Details are: user exit name = <insert_2>; node = <insert_3>.
- Severity
- 20 : Error
- Explanation
- An exception was thrown during processing of the user exit named above. See the previous exceptions for details of the error. The most likely cause is an error in parsing the message data.
- Response
- Review previous errors to see if the problem can be resolved. If it cannot be resolved, contact the provider of the user exit.
- BIP2286
- Terminal <insert_1> is not attached to node <insert_2> in message flow <insert_3>. The message will be propagated to the Failure terminal if the terminal is attached or an exception will be thrown.
- Severity
- 0 : Information
- Explanation
- The broker detected an exception whilst processing a message in node <insert_2> in message flow <insert_3>. The message has been augmented with an exception list that should have been propagated to terminal <insert_1>. However this terminal is not attached. If the Failure terminal is attached, the message will be propagated to it, otherwise the exception will be re-thrown.
- Response
- This message is for information only.
- BIP2289
- All input nodes (<insert_2>) have started for flow <insert_1>, and are now ready to receive messages.
- Severity
- 0 : Information
- Explanation
- The message flow has started, and all <insert_2> input node(s) are now ready to begin receiving and processing messages.
- Response
- None.
- BIP2290
- Parser class name <insert_1> for use in library <insert_2>: name already registered in library <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker detected the parser factory in loadable implementation library <insert_2> attempting to register the parser class name <insert_1>, but this name has already been registered with the broker by the parser factory in the library <insert_3>.
- Response
- Contact the authors or suppliers of the loadable implementation libraries to resolve the duplicate name situation. Install a new version of at least one of the loadable implementation libraries.
- BIP2291
- No constant for parser class name for root element name <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker could not locate a constant for a parser class name for a root element name.
- Response
- Contact the author or supplier of the loadable implementation library implementing the parser to check whether or not the constant has been registered. If it has not, install an updated version of the loadable implementation library. If registration has taken place, contact your IBM support center.
- BIP2292
- Constant for a parser class name for the root element name <insert_1>: constant is not valid.
- Severity
- 20 : Error
- Explanation
- The message broker located a constant defining a parser class name for the root element name <insert_1> but it was invalid.
- Response
- Contact the author or supplier of the loadable implementation library implementing the parser to check the definition of the parser class name. If the definition is invalid, install an updated version of the loadable implementation library. If the definition is correct, contact your IBM support center.
- BIP2293
- Invalid configuration message containing attribute value <insert_1>: not valid for target attribute 'messageDomainProperty' on object <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker received a configuration message containing an attribute value which is not valid for the target attribute 'messageDomainProperty' on an object on this broker. The value is case sensitive and must match one of the parsers registered with this broker.
- Response
- Ensure that the value of the attribute is correct and that all the required parser implementation libraries have been installed, then redeploy the message flow.
- BIP2294
- The parser <insert_1> is not a valid message domain option on object <insert_2> because the current fix pack function level of <insert_3> does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality.
- Severity
- 20 : Error
- Explanation
- A configuration message was received, which had parser <insert_1> as the message domain option on object <insert_2>. The message cannot be processed because the current fix pack function level of <insert_3> does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this (and all other) functionality.
- Response
- Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.
- BIP2295
- No constant was found for a parser class name for root element name <insert_1>. This parser is not available at the current fix pack function level of <insert_2>. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality.
- Severity
- 20 : Error
- Explanation
- The message broker could not locate a constant for a parser class name for a root element name <insert_1>. This parser is not available at the current fix pack function level of <insert_2>, but is available if new fix pack functionality is enabled. Use 'mqsichangebroker <brokerName> -f all' to enable this (and all other) functionality.
- Response
- Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.
- BIP2301
- File <insert_1> does not contain suitable entry points.
- Severity
- 20 : Error
- Explanation
- The message broker loaded the implementation file <insert_1> but this could not find any suitable entry points in it.
- Response
- Contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
- BIP2302
- File <insert_1> contains insufficient resources.
- Severity
- 20 : Error
- Explanation
- The message broker loaded the implementation file <insert_1> and found entry points in it but could it not find either any node factories, parser factories, or any other kind of resource within it.
- Response
- Contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
- BIP2303
- File <insert_1> could not be unloaded; operating system return code <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The message broker detected the loadable implementation library <insert_1> but this could not be unloaded by the operating system. The operating system return code was <insert_2>.
- Response
- Contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
- BIP2304
- Exception caught whilst loading file <insert_1>, the broker will operate with reduced capability.
- Severity
- 10 : Warning
- Explanation
- The message broker caught an exception whilst loading the implementation file <insert_1>. The broker will continue to operate but with reduced capabilities. See the following messages for details of the error.
- Response
- See your system log for other messages associated with this one to establish and correct the cause of the problem.
- BIP2305
- Exception caught whilst loading file <insert_1>, the broker will restart.
- Severity
- 20 : Error
- Explanation
- The message broker caught an exception whilst loading the implementation file <insert_1>. The broker will restart. See the following messages for details of the error.
- Response
- See your system log for other messages associated with this one to establish and correct the cause of the problem.
- BIP2306
- Exception <insert_2> caught whilst loading file <insert_1>, the broker will restart.
- Severity
- 20 : Error
- Explanation
- The message broker caught an exception whilst loading the implementation file <insert_1>. The information contained within this exception is <insert_2>. The broker will restart.
- Response
- Establish and correct the cause of the problem.
- BIP2307
- Unknown exception caught whilst loading file <insert_1>, the broker will restart.
- Severity
- 20 : Error
- Explanation
- The message broker caught an unknown exception whilst loading the implementation file <insert_1>. The broker will restart.
- Response
- Establish and correct the cause of the problem.
- BIP2308
- File <insert_1> could not be loaded; operating system return code <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker detected the loadable implementation file <insert_1> but this could not be loaded by the operating system. The operating system return code was <insert_2>.
- Response
- Determine the cause of the load failure by analyzing the operating system return code. If necessary contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier is IBM, contact your IBM support center.
- BIP2310
- The broker is not capable of handling a message of data type <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker received a message that requires the handling of data of type <insert_1>, but the broker does not have the capability to handle data of this type.
- Response
- Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the broker.
- BIP2311
- Program error in library <insert_1> whilst creating parser on behalf of node <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker detected a program error in a parser library whilst attempting to create a parser. This happened when processing a message on behalf of node <insert_2>.
- Response
- Contact the author or supplier of the parser to resolve the problem. If the parser was supplied by IBM, contact your IBM support center.
- BIP2312
- About to load file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The message broker is about to load the implementation file <insert_1>.
- Response
- No action need be taken.
- BIP2313
- About to call <insert_2> in file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The message broker is about to call initialization function <insert_2> in implementation file <insert_1>.
- Response
- No action need be taken.
- BIP2314
- User Exit <insert_1> not found. Registered User Exits - <insert_2>.
- Severity
- 20 : Error
- Explanation
- A User Exit name <insert_1> has been specified as active or inactive but that user exit was not provided by any library loaded by this execution group. No user message flows will be started until this is resolved. The list of user exits registered in this execution group is <insert_2>.
- Response
- Review the name provided. If the name is incorrect, reissue the relevant command with the correct name. If the user exit was set at the broker level, then run mqsichangebroker to correct it. If it was set at the execution group level, then run mqsichangeflowuserexit to correct it. Issue mqsireportflowuserexit to help determine where the invalid user exit name was set. If the name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes the directory containing the user exit library. Check system log when execution group starts for errors loading the user exit library.:EURESP.
- BIP2315
- User Exit <insert_1> not found for flow <insert_2>. Registered User Exits - <insert_3>.
- Severity
- 0 : Information
- Explanation
- A UserExit name <insert_1> has been specified as active or inactive for message flow <insert_2> but that user exit was not provided by any library loaded by this execution group. This message flow will not be started until this is resolved. The list of user exits registered in this execution group is <insert_3>.
- Response
- Review the name provided. If the name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes the directory containing the user exit library. Check system log when execution group starts for errors loading the user exit library.
- BIP2316
- User Exit <insert_1> caused exception from the node completion callback function.
- Severity
- 0 : Information
- Explanation
- A UserExit named <insert_1> has thrown an exception, or has caused one to be thrown. The exception occurred during a call to the node completion callback function while the flow was handling a previous exception. The flow continues to handle the original exception. Following messages indicate the cause of this latest exception.
- Response
- No action required.
- BIP2318
- User Exit <insert_1> not being invoked because no callback is registered for <insert_2>
- Severity
- 0 : Information
- Explanation
- A UserExit named <insert_1> is active for the current flow and the relevant event has occurred. However, the User Exit has not provided a function for this event so will not be invoked.
- Response
- No action required.
- BIP2319
- Error casting <insert_3> to a timezone. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- The given string is not a valid timezone.
- Response
- Please correct the string and re-issue the cast operation.
- BIP2321
- Database error: ODBC return code <insert_1> using ODBC driver manager <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker encountered an error when processing a database operation. The ODBC return code was <insert_1>. See the following messages for information obtained from the database concerning this error.
- Response
- Use the following messages to determine the cause of the error. Typical problems are an incorrect datasource or table names. Correct either the database or message broker configuration.
- BIP2322
- Database error: SQL State <insert_1>; Native Error Code <insert_2>; Error Text <insert_3>.
- Severity
- 20 : Error
- Explanation
- The error has the following diagnostic information: SQL State <insert_1> SQL Native Error Code <insert_2> SQL Error Text <insert_3>
- Response
- This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error. Use the mqsicvp command to test connectivity to this database.
- BIP2323
- DBMS <insert_1> is not supported for a coordinated transaction.
- Severity
- 20 : Error
- Explanation
- A message flow has been configured for a globally coordinated transaction, and a message processing node has specified a database connection target as a participant in the global transaction. However, this DBMS is not supported by WebSphere Message Broker as a participant in a globally coordinated transaction. The message flow is terminated and the input message is backed out.
- Response
- Because this target DBMS is not supported as a participant in a coordinated transaction, the node can use this database only outside a global transaction.
- BIP2324
- Unsupported datatype <insert_2> fetched from database table column <insert_1>.
- Severity
- 20 : Error
- Explanation
- A message flow node which performs a database fetch returned a datatype not supported by the message broker. The database table column <insert_1> contain an unsupported datatype identified by <insert_2>.
- Response
- Either update the message flow to eliminate the reference to the database column with the unsupported datatype, or modify the database schema to change the column to be of a type supported by the message broker.
- BIP2325
- Invalid datatype <insert_1> encountered.
- Severity
- 20 : Error
- Explanation
- An invalid datatype identified by <insert_1> was encountered during the processing of a message flow. This indicates that an internal software error has occurred.
- Response
- Restart the broker. If the problem continues to occur contact your IBM support center.
- BIP2326
- Error casting <insert_3> hours <insert_4> minutes <insert_5> seconds to a TIME. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- Numbers may only be converted to a time if they conform to the constraints of the 24 hour clock.
- Response
- Ensure that the values being cast have valid values.
- BIP2327
- Error casting <insert_3> years <insert_4> months <insert_5> days to a DATE. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- Numbers may only be converted to a date if they conform to the constraints of the Gregorian calendar.
- Response
- Ensure that the values being cast have valid values.
- BIP2328
- A value of SQL datatype <insert_1> encountered when datatype <insert_2> expected.
- Severity
- 20 : Error
- Explanation
- The value of SQL datatype <insert_1> was encountered, but a value of SQL datatype <insert_2> was expected.
- Response
- This message will be accompanied with others which will give the higher level context for this error. Look at these other messages to determine the root source of the problem.
- BIP2329
- An unexpected NULL value was encountered.
- Severity
- 20 : Error
- Response
- This message will be accompanied with others which will give the higher level context for this error. Look at these other messages to determine the root source of the problem.
- BIP2330
- Field <insert_4>[<insert_5>]' within field <insert_1> does not exist; diagnostic information <insert_2>, <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker attempted to locate the field <insert_4>[<insert_5>]' contained within the field <insert_1> but the message did not contain this field. Additional diagnostic information is <insert_2> <insert_3>.
- Response
- Check the message flow definition and the messages being processed by the message flow to ensure that the referenced field has been correctly specified. If necessary change the message flow to eliminate the reference to the nonexistent field.
- BIP2331
- Field <insert_2> within field <insert_1> does not exist.
- Severity
- 20 : Error
- Explanation
- The message broker attempted to locate the field <insert_2> contained within the field <insert_1> but the message did not contain this field.
- Response
- Check the message flow definition and the messages being processed by the message flow to ensure that the referenced field has been correctly specified. If necessary change the message flow to eliminate the reference to the nonexistent field.
- BIP2332
- Error attaching field <insert_2> to field <insert_1> which already has a parent.
- Severity
- 20 : Error
- Explanation
- The message broker attempted to attach the field <insert_2> to the field <insert_1> but the latter field already has a parent field.
- Response
- This error can arise as a result of an error in a the use of the SQL ATTACH statement. Examine the logic of the SQL statements, correct it and redeploy.
- BIP2333
- Error attaching field <insert_2> as a sibling of field <insert_1>, which has no parent.
- Severity
- 20 : Error
- Explanation
- The message broker attempted to attach the field <insert_2> as a sibling of the field <insert_1> but the latter field does not have a parent field.
- Response
- If the error results from an ESQL Compute node or JavaCompute node, review the node to make sure that the element being modified has a parent element. If the error results from a user-defined extension (UDE), such as a Java plug-in node, contact the author or supplier of the UDE and obtain a corrected version.
- BIP2334
- Unable to resolve union for the <insert_3> child of element <insert_2>. Additional diagnostic information is <insert_1>
- Severity
- 10 : Warning
- Explanation
- An incoming message contained a union which was neither resolved by the message's tagging nor by the accesses made by SQL statements. Either the message was of an unexpected type or there is an error in the SQL. See earlier messages for details of the node in which this error occurred and the action taken as a result.
- Response
- Check that the incoming messages are of the correct type and that the logic of the SQL of the node in which the error occurred
- BIP2335
- Unable to perform copy. Element <insert_2> is a child of element <insert_4>. Additional diagnostic information is <insert_1> <insert_3>
- Severity
- 10 : Warning
- Explanation
- A recursive copy was attempted but these are not allowed as they lead to indeterminate results. See earlier messages for details of the node in which this error occurred and the action taken as a result.
- Response
- Check the logic of the SQL of the node in which the error occurred
- BIP2336
- Error attaching field <insert_2> to field <insert_1>. Field <insert_1> is a child of field <insert_2>.
- Severity
- 20 : Error
- Explanation
- A field cannot be attached as a child or sibling of one of its own children as this would create a closed loop within a message tree. The broker does not support such structures.
- Response
- This error can arise as a result of an error in a the use of the SQL ATTACH statement. Examine the logic of the SQL statements, correct it and redeploy.
- BIP2337
- Attempt to use an unsuitable domain in a shared tree.
- Severity
- 20 : Error
- Explanation
- In this release, shared trees are restricted in the message domains that can be used. For example, you can use the Properties, MQMD, MQRFH2C, XMLNSC, DFDL, JSON and most WebSphere MQ headers, but not the MQRFH2, XML, XMLNS, and MRM domains.
- Response
- Correct the logic of the message flow and redeploy it.
- BIP2338
- The data type <insert_1> is not supported by the <insert_2> database.
- Severity
- 20 : Error
- Explanation
- When queried the <insert_2> database manager did not return a value for the SQL type <insert_1>1 indicating that it does not support this data type.
- Response
- Check that the datatype <insert_1> is the correct data type for your user database. Do not use Informix or DB2 IICF databases for the broker database.
- BIP2339
- A deployed resource has been created with the same name as an existing deployed resource. (New resource=<insert_1>,<insert_2>,<insert_5>. Existing resource=<insert_3>,<insert_4>,<insert_6>).
- Severity
- 10 : Warning
- Explanation
- This is an internal error.
- Response
- Contact your IBM support center for assistance.
- BIP2340
- Error attaching field <insert_2> to field <insert_1> which belongs to a message in a different group.
- Severity
- 20 : Error
- Explanation
- The message broker attempted to attach the field <insert_2> to the field <insert_1> but the latter field belongs to a message in a different group.
- Response
- This error can only arise as a result of an error in a node or parser implementation library. Contact the author or supplier of the loadable implementation library and obtain a correct version.
- BIP2341
- A problem was encountered with statement handle <insert_1>.
- Severity
- 20 : Error
- Explanation
- A problem with the database statement handle <insert_1> was encountered. This indicates that an internal software error has occurred.
- Response
- If the problem continues to occur contact your IBM support center.
- BIP2342
- A connection has been made to the datasource <insert_1>, using the ODBC driver manager <insert_2>, with globally coordinated transaction ('XA') status of <insert_3>.
- Severity
- 0 : Information
- Explanation
- This message means that the broker has connected to the specified datasource for the first time.
- Response
- None.
- BIP2343
- When attempting to use the DataDirect <insert_1> ODBC driver a licensing error has occurred. This will not immediately stop the broker from accessing your data sources. You now have 14 days to rectify the problem or access to your data sources will stop. Contact your IBM support center.
- Severity
- 20 : Error
- Explanation
- A licensing error has occurred for the DataDirect ODBC drivers. The error code is <insert_2>
- Response
- Contact your IBM support center.
- BIP2345
- The environment variable 'IE02_PATH' has been set to a value that is not valid.
- Severity
- 20 : Error
- Response
- The broker has detected that the environment variable 'IE02_PATH' does not not point to a valid installation of WebSphere Message Broker Database Extender.
Check the installation of WebSphere Message Broker Database Extender.
If WebSphere Message Broker Database Extender is not installed, the environment variable should not be set.
- BIP2346
- The broker cannot handle a message of data type <insert_1> because the current fix pack function level of <insert_2> does not support this parser. Use 'mqsichangebroker <brokerName> -f all' to enable this functionality.
- Severity
- 20 : Error
- Explanation
- The message broker received a message that requires the handling of data of type <insert_1>. The broker cannot handle messages of this type because new functionality has not been enabled for this broker. Use 'mqsichangebroker <brokerName> -f all' to enable this (and all other) functionality.
- Response
- Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.
- BIP2347
- Database error: SQL State <insert_1>; Native Error Code <insert_2>; Error Text 'System information file not found. Please check the ODBCINI and the ODBCSYSINI environment variables are correctly set.'
- Severity
- 20 : Error
- Explanation
- The error has the following diagnostic information: SQL State <insert_1> SQL Native Error Code <insert_2>
- Response
- This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error. Use the mqsicvp command to test connectivity to this database.
- BIP2348
- Error detected while attempting to obtain a connection to data source <insert_1> of type <insert_2> using userid <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error while attempting to obtain a connection to data source <insert_1> of type <insert_2> with userid <insert_3>. If your broker is running on z/OS, it is possible for the userid to be blank, which results in a connection attempt using the userid of the started task.
- Response
- See the following messages for details of the error, or use the mqsicvp command to verify the database configuration.
- BIP2350
- Unable to convert <insert_1> from Unicode to the local code page.
- Severity
- 20 : Error
- Explanation
- The broker was unable to convert the value <insert_1> from Unicode to the local code page.
- Response
- Check that the source of the data containing the value that cannot be converted is intended to be displayed in the local code page. If you expect the data never to be displayed in the local codepage, modify the message flow to eliminate the cause of conversion. If you expect the data to be displayed, check the origin of the data to ensure that only characters capable of being displayed in the local code page are generated.
- BIP2351
- Unable to convert <insert_1> from local code page to Unicode.
- Severity
- 20 : Error
- Explanation
- The broker was unable to convert the value <insert_1> from the local code page to Unicode.
- Response
- This is an internal processing error. Contact your IBM support center.
- BIP2352
- Unable to convert <insert_1> to an integer from the local code page.
- Severity
- 20 : Error
- Explanation
- The message broker was unable to convert the value <insert_1> from the local code page to an integer.
- Response
- Check the source of the data for the value to determine why the value is not suitable for conversion to an integer.
- BIP2353
- Unable to convert <insert_1> to a real number from the local code page.
- Severity
- 20 : Error
- Explanation
- The message broker was unable to convert the value <insert_1> from the local code page to a real number.
- Response
- Check the source of the data for the value to determine why the value is not suitable for conversion to a real number.
- BIP2358
- The DB2 64-bit ODBC driver (DSNAO64C) was not found.
- Severity
- 20 : Error
- Explanation
- DB2 is not defined in the STEPLIB of the broker's started task JCL. Database nodes require DB2 in order to connect to a datasource.
- Response
- Stop the broker, edit the broker's started task JCL, adding DB2 to the BROKER STEPLIB. Then restart the broker.
- BIP2360
- Syntax error in path specification missing ')' after type specification.
- Severity
- 20 : Error
- Explanation
- A ')' must close a type specification. A path string has been specified using an invalid syntax. The path was specified as <insert_1>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2361
- Syntax error in path specification, no closing ']' in index specification.
- Severity
- 20 : Error
- Explanation
- A ']' must close an index specification. A path string has been specified using an invalid syntax. The path was specified as <insert_1>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2362
- Syntax error in path specification missing '.' after index specification.
- Severity
- 20 : Error
- Explanation
- A '.' must follow an index specification. A path string has been specified using an invalid syntax. The path was specified as <insert_1>.
- Response
- This is an internal error. Contact your IBM support center.
- BIP2370
- Transaction compromised: message flow thread already connected to DSN <insert_1> in a different coordination mode.
- Severity
- 20 : Error
- Explanation
- A thread executing a message flow node attempted to connect to a database. However, the message flow thread already had a connection to the same data source name (DSN) <insert_1> in a different coordination mode. On UNIX and Windows platforms, this request cannot be granted because this would compromise the integrity of a globally coordinated transaction and would result in XA protocol errors and/or unpredictable behavior. This can occur if a message flow has been configured with the Coordinated Transaction property of 'yes' and the nodes specifies a property which indicate that a commit to that database is to be performed.
- Response
- Correct the message flow and redeploy the message broker.
- BIP2371
- Database statement <insert_1> could not be executed.
- Severity
- 20 : Error
- Explanation
- An attempt to execute a database statement <insert_1> has failed (the database returned an error).
- Response
- Identify the cause of the problem and correct it before trying again. If relevant, correct the message flow and redeploy the message broker.
- BIP2372
- Exception thrown by pattern instance; text is <insert_1>.
- Severity
- 20 : Error
- Explanation
- A pattern instance has thrown an exception. The message text associated with this exception is <insert_1>.
- Response
- Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.
- BIP2373
- A mismatched XA Connection has been detected.
- Severity
- 20 : Error
- Explanation
- A mismatch between the XA connections to the data source <insert_1> has been detected. The connections to the data source will now be recreated.
- Response
- None
- BIP2374
- Problem configuring XA Coordination for JDBC.
- Severity
- 10 : Warning
- Explanation
- An error occurred when configuring XA Coordination for JDBC. The error reported was <insert_1>. XA functionality on JDBC connections is disabled. This warning can be ignored for Execution Groups which do not require XA Coordination with JDBC.
- Response
- If XA Coordination with JDBC is required by the Execution Group reporting this warning, on Unix systems check that the Broker's user ID has permission to read from and write to the /var/mqm filesystem, or on Windows systems confirm that the Broker's MQ QueueManager has the same administrative ID as the Broker's service ID. If the Execution Group reporting this warning does not require XA Coordination with JDBC then no user response is required.
- BIP2380
- WMB message flow statistics.
ProcessID=<insert_1>,
Key=<insert_2>,
Type=<insert_3>,
Reason=<insert_4>,
BrokerLabel=<insert_5>,
BrokerUUID=<insert_6>,
ExecutionGroupName=<insert_7>,
ExecutionGroupUUID=<insert_8>,
MessageFlowName=<insert_9>,
StartDate=<insert_10>,
StartTime=<insert_11>,
EndDate=<insert_12>,
EndTime=<insert_13>,
TotalElapsedTime=<insert_14>,
MaximumElapsedTime=<insert_15>,
MinimumElapsedTime=<insert_16>,
TotalCPUTime=<insert_17>,
MaximumCPUTime=<insert_18>,
MinimumCPUTime=<insert_19>,
CPUTimeWaitingForInputMessage=<insert_20>,
ElapsedTimeWaitingForInputMessage=<insert_21>,
TotalInputMessages=<insert_22>,
TotalSizeOfInputMessages=<insert_23>,
MaximumSizeOfInputMessages=<insert_24>,
MinimumSizeOfInputMessages=<insert_25>,
NumberOfThreadsInPool=<insert_26>,
TimesMaximumNumberOfThreadsReached=<insert_27>,
TotalNumberOfMQErrors=<insert_28>,
TotalNumberOfMessagesWithErrors=<insert_29>,
TotalNumberOfErrorsProcessingMessages=<insert_30>,
TotalNumberOfTimeOuts=<insert_31>,
TotalNumberOfCommits=<insert_32>,
TotalNumberOfBackouts=<insert_33>.
AccountingOrigin=<insert_34>.
- Severity
- 0 : Information
- Explanation
- Statistical information for message flow <insert_9> in broker <insert_5>.
- Response
- This is an information message produced by WMB statistics.
- BIP2381
- WMB thread statistics.
ProcessID=<insert_1>,
Key=<insert_2>,
Number=<insert_3>,
TotalNumberOfInputMessages=<insert_4>,
TotalElapsedTime=<insert_5>,
TotalCPUTime=<insert_6>,
CPUTimeWaitingForInputMessage=<insert_7>,
ElapsedTimeWaitingForInputMessage=<insert_8>,
TotalSizeOfInputMessages=<insert_9>,
MaximumSizeOfInputMessages=<insert_10>,
MinimumSizeOfInputMessages=<insert_11>.
- Severity
- 0 : Information
- Explanation
- Statistical information for thread <insert_3>.
- Response
- This is an information message produced by WMB statistics.
- BIP2382
- WMB node statistics.
ProcessID=<insert_1>,
Key=<insert_2>,
Label=<insert_3>,
Type=<insert_4>,
TotalElapsedTime=<insert_5>,
MaximumElapsedTime=<insert_6>,
MinimumElapsedTime=<insert_7>,
TotalCPUTime=<insert_8>,
MaximumCPUTime=<insert_9>,
MinimumCPUTime=<insert_10>,
CountOfInvocations=<insert_11>,
NumberOfInputTerminals=<insert_12>,
NumberOfOutputTerminals=<insert_13>.
- Severity
- 0 : Information
- Explanation
- Statistical information for node <insert_3>.
- Response
- This is an information message produced by WMB statistics.
- BIP2383
- WMB terminal statistics.
ProcessID=<insert_1>,
Key=<insert_2>,
Label=<insert_3>,
Type=<insert_4>,
CountOfInvocations=<insert_5>,
- Severity
- 0 : Information
- Explanation
- Statistical information for terminal <insert_3>.
- Response
- This is an information message produced by WMB statistics.
- BIP2384
- Error updating the statistics message flow transaction container for message flow <insert_1>. Node <insert_2> was not found.
- Severity
- 20 : Error
- Explanation
- The container used to gather statistics for a message flow transaction does not match the shape of the message flow that processed the input message. Statistics gathering is unable to continue for this message flow.
- Response
- Check that the deploy of the message flow was successful. If the problem persists then you should contact your IBM Support center.
- BIP2385
- Error updating the statistics message flow transaction container for message flow <insert_1> and node <insert_2>. The terminal <insert_3> was not found.
- Severity
- 20 : Error
- Explanation
- The container used to gather statistics for a message flow transaction does not match the shape of the message flow that processed the input message. Statistics gathering is unable to continue for this message flow.
- Response
- Check that the deploy of the message flow was successful. If the problem persists then you should contact your IBM Support center.
- BIP2386
- Error writing statistics collector record for message flow <insert_1>. The <insert_2> writer was not available.
- Severity
- 20 : Error
- Explanation
- The statistics writer associated with the specified output format was either not found or there is a problem with the output medium. Statistics output is unable to continue for this message flow.
- Response
- Check that the media for the required statistics output format is available and correctly configured. If the problem persists then you should contact your IBM Support center.
- BIP2387
- Error encountered during <insert_1> operation for a statistics message flow transaction container for message flow <insert_2>.
- Severity
- 20 : Error
- Explanation
- The statistics conveyor was not found for the operation specified or it was left in a locked state as the result of a previous system error.
- Response
- Check the broker system error logs for previous errors. If the problem persists then you should contact your IBM Support center.
- BIP2388
- Unable to obtain a statistics message flow transaction container for message flow <insert_1>.
- Severity
- 20 : Error
- Explanation
- The pool for the statistics message flow transaction containers was unable to create and dispense a new container for the statistics gathering process.
- Response
- Check that the deploy of the message flow was successful. If the problem persists then contact your IBM Support center.
- BIP2389
- Exception condition detected in statistics and accounting
- Severity
- 20 : Error
- Explanation
- The XML writer for statistics and accounting detected an error writing to it's output. Following messages will indicate the cause of this exception.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2390
- Internal Error in WMB Statistics and Accounting <insert_1> <insert_2> <insert_3>3
- Severity
- 20 : Error
- Explanation
- A processing error occurred while gathering statistics data for the message flow.
- Response
- Check that the deploy of the message flow was successful. If the problem persists then you should contact your IBM Support center.
- BIP2391
- DB2 wrapper (64-bit) could not load the DB2 implementation library <insert_1> using the shared library search path, or from the location specified by the MQSI_64BIT_DB2_LIBRARY_NAME environment variable. DB2 will not be accessible in this process.
- Severity
- 20 : Error
- Explanation
- The ODBC driver manager is attempting to load the DB2 application binding library using a 64-bit DB2 wrapper. The wrapper has loaded correctly, but is itself unable to load the actual DB2 implementation library needed for operation. See the Standard Output (stdout) and Standard Error (stderr) for this process for any additional information.
- Response
- Ensure DB2 is accessible to the broker user id, and that the shared library search path is set to include the DB2 64-bit library location. Setting MQSI_64BIT_DB2_LIBRARY_NAME to point to libdb2.so (or .a on AIX) may help this problem.
- BIP2392
- DB2 wrapper (64-bit) could not find the function <insert_1> in the DB2 implementation library <insert_2>. This function will not be available to broker code in this process.
- Severity
- 20 : Error
- Explanation
- The ODBC driver manager has loaded the DB2 application binding library using a 64-bit DB2 wrapper, but the wrapper cannot find the function <insert_1> which is needed for the broker to operate completely correctly. Subsequent database errors may be caused by this problem.
- Response
- Ensure the DB2 wrapper library can find the correct DB2 application binding library. Setting MQSI_64BIT_DB2_LIBRARY_NAME to point to the correct libdb2.so (or .a on AIX) may help this problem.
- BIP2393
- Database error: ODBC return code <insert_1> from data source <insert_2> using ODBC driver manager <insert_3>.
- Severity
- 20 : Error
- Explanation
- The broker received an error when processing a database operation. The ODBC return code was <insert_1>. See the following messages for information obtained from the database about this error.
- Response
- Use the following messages to determine the cause of the error. Typical problems are an incorrect data source, or table names. Correct either the database or the broker configuration. Use the mqsicvp command to test connectivity to this database.
- BIP2394
- Informix wrapper (64-bit) could not load the Informix implementation library using library locations <insert_1>, <insert_2>, or the location specified by the MQSI_64BIT_INFORMIX_LIBRARY_NAME environment variable. Informix will not be accessible in this process.
- Severity
- 20 : Error
- Explanation
- The ODBC driver manager is attempting to load the Informix application binding library using a 64-bit Informix wrapper. The wrapper has loaded correctly, but is itself unable to load the actual Informix implementation library needed for operation. See the Standard Output (stdout) and Standard Error (stderr) for this process for any additional information.
- Response
- Ensure Informix is accessible to the broker user id, and that the shared library search path is set to include the Informix 64-bit library location. Setting MQSI_64BIT_INFORMIX_LIBRARY_NAME to point to iclit09b.so (or .a on AIX) may help this problem.
- BIP2395
- Informix wrapper (64-bit) could not find the function <insert_1> in the Informix implementation library <insert_2>. This function will not be available to broker code in this process.
- Severity
- 20 : Error
- Explanation
- The ODBC driver manager has loaded the Informix application binding library using a 64-bit Informix wrapper, but the wrapper cannot find the function <insert_1> which is needed for the broker to operate completely correctly. Subsequent database errors may be caused by this problem.
- Response
- Ensure the Informix wrapper library can find the correct Informix application binding library. Setting MQSI_64BIT_INFORMIX_LIBRARY_NAME to point to the correct iclit09b.so (or .a on AIX) may help this problem.
- BIP2396
- The ODBC driver manager loader cannot find the function <insert_1> in the ODBC driver manager implementation library <insert_2>. This function will not be available to broker code in this process. Native error text: <insert_3>3
- Severity
- 20 : Error
- Explanation
- The specified ODBC driver manager has been loaded, but the loader cannot find the specified function that is needed for the broker to operate completely correctly. Subsequent database errors might be caused by this problem.
- Response
- This error suggests that the specifed driver manager implementation library is not a supported driver manager. Ensure that the broker is configured to load only supported driver managers.
- BIP2397
- The environment variables 'ODBCINI' and 'ODBCUOINI' point to the same file.
- Severity
- 10 : Warning
- Explanation
- The environment variables 'ODBCINI' and 'ODBCUOINI' must point to different ODBC driver manager configuration files.
- Response
- Ensure, either that you point the 'ODBCINI' and 'ODBCUOINI' environment variables to separate ODBC driver manager configuraton files, or that you have not set these two environment variables.
- BIP2398
- A failure occurred during the process of committing or rolling back a database transaction, therefore the execution group will be restarted.
- Severity
- 20 : Error
- Explanation
- A failure occurred when a database transaction was being committed or rolled back. The execution group is now in an undefined state and must be restarted.
- Response
- Check the database completion and reason codes to establish the cause of the error, taking appropriate action. You might need to restart the message broker after you have completed this recovery action.
- BIP2401
- (<insert_1>, <insert_2>) : Syntax error : expected <insert_3> but found <insert_4>.
- Severity
- 20 : Error
- Explanation
- The expected token was not found.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2402
- (<insert_1>, <insert_2>) : Syntax error : <insert_3>.
- Severity
- 20 : Error
- Explanation
- The token caused a syntax error.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2403
- (<insert_1>, <insert_2>) : An interval qualifier is not allowed here.
- Severity
- 20 : Error
- Explanation
- An interval qualifier was specified after a pair of parentheses which did not contain a subtraction expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2404
- Illegal reference use.
- Severity
- 20 : Error
- Explanation
- A reference variable has been used when the entity to which it refers no longer exists.
- Response
- Correct the logic of the SQL program and redeploy the message flow.
- BIP2405
- (<insert_1>, <insert_2>) : Syntax error : <insert_3> is a keyword , an identifier was expected.
- Severity
- 20 : Error
- Explanation
- The token caused a syntax error.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2406
- (<insert_1>, <insert_2>) : Syntax error : cannot specify '[]' in the middle of a field reference.
- Severity
- 20 : Error
- Explanation
- The list specifier ('[]') can only be used at the end of a field reference.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2407
- (<insert_1>, <insert_2>) : Precision must be > 0 and <= <insert_1>.
- Severity
- 20 : Error
- Explanation
- A precision value was given in the definition of a DECIMAL datatype which was outside of the valid range.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Correct the definition of the DECIMAL datatype so that a valid precision is specified and redeploy the message flow.
- BIP2408
- (<insert_1>, <insert_2>) : Scale must be >= 0 and <= <insert_1>.
- Severity
- 20 : Error
- Explanation
- A scale value was given in the definition of a DECIMAL datatype which was outside of the valid range.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Correct the definition of the DECIMAL datatype so that a valid scale is specified and redeploy the message flow.
- BIP2409
- (<insert_1>, <insert_2>) : An interval qualifier was expected.
- Severity
- 20 : Error
- Explanation
- INTERVAL data types must be qualified with a valid qualifier such as 'MONTH TO YEAR'. See the documentation for a full list of valid qualifiers.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2410
- (<insert_1>, <insert_2>) : A field reference was expected.
- Severity
- 20 : Error
- Explanation
- A field reference was expected here but there does not appear to be one.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2411
- (<insert_1>, <insert_2>) : The source expression did not evaluate to a ROW.
- Severity
- 20 : Error
- Explanation
- When "INSERT" is specified as the target within a ROW, its source expression must also be a ROW.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2412
- (<insert_1>, <insert_2>) : Expected one of 'ANY', 'ALL' or 'SOME'.
- Severity
- 20 : Error
- Explanation
- The token found did not match any of the expected values.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2413
- (<insert_1>, <insert_2>) : Inconsistent number of values in VALUES clause.
- Severity
- 20 : Error
- Explanation
- The number of values specified in the VALUES clause does not match the number of columns specified.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Correct the number of values specified in the VALUES clause and redeploy the message flow.
- BIP2414
- Unsupported datatype <insert_1>.
- Severity
- 20 : Error
- Explanation
- While preparing an ODBC statement a parameter with data type <insert_1> was encountered. This data type is not yet supported for ODBC operations.
- Response
- Ensure that expressions which may return values of data type <insert_1> are not used as parameters in statements or expressions that access external databases.
- BIP2415
- (<insert_1>, <insert_2>) : A correlation name must be specified.
- Severity
- 20 : Error
- Explanation
- The UPDATE and DELETE statements, and also the SELECT function when it is applied to a database, require a correlation name to be defined. This name represents a variable which holds each row involved in the operation in turn. Correlation names can be explicitly defined by an AS clause, or can be implicitly defined by a hard coded table name. It is an error to use a table name expression and not explicitly specify a correlation name.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2416
- The target type <insert_1> and the number of parameters supplied <insert_2> do not correspond to any valid CAST
- Severity
- 20 : Error
- Response
- Correct the syntax of the SQL program and re-deploy.
- BIP2417
- (<insert_1>, <insert_2>) : Invalid table reference.
- Severity
- 20 : Error
- Explanation
- A table reference consists of a correlation name (e.g. "Database") followed by one, two or three names (or name expressions) giving the data source name, the schema name and the table name. The given field reference does not meet this requirement.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2418
- (<insert_1>, <insert_2>) : Invalid schema reference.
- Severity
- 20 : Error
- Explanation
- A schema reference consists of a correlation name (e.g. "Database") followed by one or two names (or name expressions) giving the data source name and the schema name. The given field reference does not meet this requirement.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2419
- (<insert_1>, <insert_2>) : Invalid database reference.
- Severity
- 20 : Error
- Explanation
- A database reference consists of a correlation name (e.g. "Database") followed by a single name (or name expression) giving the data source name. The given field reference does not meet this requirement.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2420
- (<insert_1>, <insert_2>) : Invalid or incompatible data types for <insert_3> operator.
- Severity
- 20 : Error
- Explanation
- Either the data types of the operands of the operator were not valid for the operator, or the datatypes were incompatible.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the data types of the operands are valid and compatible with each other.
- BIP2421
- (<insert_1>, <insert_2>) : Left hand operand to <insert_3> operator must be a scalar.
- Severity
- 20 : Error
- Explanation
- The left hand operand to the operator was not a scalar valued expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the left hand operator to the <insert_3> operator is a scalar.
- BIP2422
- (<insert_1>, <insert_2>) : Right hand operand to the <insert_3> operator must be a scalar.
- Severity
- 20 : Error
- Explanation
- The right hand operand to the operator was not a scalar valued expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the right hand operand to the <insert_3> operator is a scalar.
- BIP2423
- (<insert_1>, <insert_2>) : Interval qualifier only valid with datetime subtraction.
- Severity
- 20 : Error
- Explanation
- If an interval qualifier is specified after a subtraction expression, the operands of the expression must be datetime values.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2424
- (<insert_1>, <insert_2>) : Interval qualifier must be specified with a datetime subtraction.
- Severity
- 20 : Error
- Explanation
- When subtracting two datetime values, an interval qualifier must be given.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2425
- Interval qualifier not valid for subtraction between values <insert_1> and <insert_2>.
- Severity
- 20 : Error
- Explanation
- If an interval qualifier is specified after a subtraction expression, the operands of the expression must be datetime values. The subtraction was being performed between values <insert_1> and <insert_2>.
- Response
- Ensure that the operands of the expression are datetime values.
- BIP2426
- Interval qualifier required for subtraction between values <insert_1> and <insert_2>.
- Severity
- 20 : Error
- Explanation
- When two datetime values are subtracted, an interval qualifier must be given. The subtraction was being performed between values <insert_1> and <insert_2>.
- Response
- Ensure that a valid interval qualifier is specified.
- BIP2427
- (<insert_1>, <insert_2>) : The left operand of <insert_3> operator is not a boolean expression.
- Severity
- 20 : Error
- Explanation
- The left operand of this operator must be a boolean expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2428
- (<insert_1>, <insert_2>) : The right hand operand to operator <insert_3> is not a boolean expression.
- Severity
- 20 : Error
- Explanation
- The right hand operand to this operator must be a boolean expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2429
- The left hand operand to the <insert_1> operator must evaluate to a boolean value.
- Severity
- 20 : Error
- Explanation
- The left hand operand to this operator is <insert_2>, which does not evaluate to a boolean value.
- Response
- Ensure that the left hand operand evaluates to a boolean value.
- BIP2430
- Illegal operands <insert_1> and <insert_2> for concatenation operator.
- Severity
- 20 : Error
- Explanation
- The operands for the concatenation operator were <insert_1> and <insert_2>. The concatenation operator can only be applied between two character string values, two bit string values, or two byte string values.
- Response
- Correct the syntax of the expression and redeploy the message flow.
- BIP2431
- The right hand operand to the <insert_1> operator must evaluate to a boolean value.
- Severity
- 20 : Error
- Explanation
- The right hand operand to this operator is <insert_2>, which does not evaluate to a boolean value.
- Response
- Ensure that the right hand operand evaluates to a boolean value.
- BIP2432
- (<insert_1>, <insert_2>) : The correlation name <insert_3> is not valid. Those in scope are: <insert_4>.
- Severity
- 20 : Error
- Explanation
- The first element of a field reference must be a valid correlation name, from those in scope. This message may sometimes be due to an incorrectly formed or spelled expression which is not intended to be a field reference being parsed as if it were a field reference because the parser does not recognize it.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2433
- (<insert_1>, <insert_2>) : Illegal result type for expression. Valid types are <insert_3>.
- Severity
- 20 : Error
- Explanation
- The expression must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2434
- (<insert_1>, <insert_2>) : <insert_5> field index expression does not evaluate to INTEGER value; <insert_3> evaluates to <insert_4>.
- Severity
- 20 : Error
- Explanation
- A field index must be an INTEGER value. The expression <insert_3> evaluates to a value of type <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only expressions evaluating to INTEGER values are used to designate field indexes with <insert_5>.
- BIP2435
- Array index evaluated to <insert_1>.
- Severity
- 20 : Error
- Explanation
- The array index expression must evaluate to a positive, nonzero integer value.
- Response
- Correct the logic of the program redeploy the message flow.
- BIP2436
- Invalid indexed assignment to <insert_1>.
- Severity
- 20 : Error
- Explanation
- No indexed elements from the named array exist. In order to assign a value to an element with index n, where 'n' is a positive integer, n-1 elements with the same name must already exist.
- Response
- Correct the logic of the program redeploy the message flow.
- BIP2437
- Invalid indexed assignment to element <insert_2>. Only <insert_1> elements already exist.
- Severity
- 20 : Error
- Explanation
- An attempt was made to assign a value to an element, but the index is out of range. In order to assign a value to an element with index n, the element with index n-1 must already exist.
- Response
- Correct the logic of the program redeploy the message flow.
- BIP2438
- Path must specify a name.
- Severity
- 20 : Error
- Explanation
- The path element identifies a parser and thus must have a name (but no type).
- Response
- Correct the logic of the program redeploy the message flow.
- BIP2439
- (<insert_1>, <insert_2>) : Error evaluating expression <insert_3>.
- Severity
- 20 : Error
- Explanation
- An error occurred while evaluating an expression. Subsequent messages will contain more information about the nature of the error.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the expression is correctly formed.
- BIP2440
- (<insert_1>, <insert_2>) : Invalid first operand for BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- The first operand of a BETWEEN predicate must be a scalar.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2441
- (<insert_1>, <insert_2>) : Invalid second operand for BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- The second operand of a BETWEEN predicate must be a scalar.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2442
- (<insert_1>, <insert_2>) : Invalid third operand for BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- The third operand of a BETWEEN predicate must be a scalar.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2443
- (<insert_1>, <insert_2>) : Incompatible first and second operands for BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- The first and second operands of a BETWEEN predicate must be compatible data types.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2444
- (<insert_1>, <insert_2>) : Incompatible first and third operands for BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- The data types of the first and third operands of a BETWEEN predicate must be compatible data types.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2445
- (<insert_1>, <insert_2>) : Illegal operand for unary minus.
- Severity
- 20 : Error
- Explanation
- The unary minus operator can only be applied to numeric or interval operands.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2446
- (<insert_1>, <insert_2>) : Illegal operand for unary minus applied to value <insert_3>.
- Severity
- 20 : Error
- Explanation
- The unary minus operator can only be applied to numeric or interval operands. An attempt was made to apply the unary minus operator to an inappropriate value.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the unary minus is only applied to numeric or interval operands.
- BIP2447
- (<insert_1>, <insert_2>) : Illegal operand for NOT operator.
- Severity
- 20 : Error
- Explanation
- The operand for the NOT operator must be a boolean valued expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2448
- (<insert_1>, <insert_2>) : Illegal operand for NOT operator applied to value <insert_3>.
- Severity
- 20 : Error
- Explanation
- The operand for the NOT operator must be a boolean expression. An attempt was made to apply the NOT operator to an inappropriate value.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the NOT operator is only applied to boolean expressions.
- BIP2449
- Arithmetic overflow evaluating expression <insert_3>. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- The result of this expression was outside the valid range for the data type.
- Response
- Either supply smaller values as operands or use a data type capable of holding larger values.
- BIP2450
- Divide by zero evaluating expression <insert_3>. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- A divide by zero error occurred.
- Response
- Ensure that the second operand of the division operator cannot be zero.
- BIP2451
- Incompatible types <insert_1> and <insert_2> for operator <insert_3>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to combine the values <insert_1> and <insert_2> using the operator <insert_3>.
- Response
- Ensure that the data types passed to this operator are compatible.
- BIP2452
- Overflow casting integer to interval; value <insert_1> exceeds the maximum of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The integer had the value <insert_1>, which was greater that the maximum allowed of <insert_2>.
- Response
- Ensure that the magnitude of the integer value does not exceed the maximum.
- BIP2453
- Overflow casting double to integer; value <insert_1> outside of range [<insert_2>, <insert_3>].
- Severity
- 10 : Warning
- Explanation
- The double had the value <insert_1>, which was outside of the range [<insert_2>, <insert_3>].
- Response
- Ensure that the double value does not exceed the maximum.
- BIP2454
- (<insert_1>, <insert_2>) : Conflicting table references.
- Severity
- 20 : Error
- Explanation
- In this release, all table references occurring in the same FROM clause must specify the same database and the same coordination.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2455
- Error casting character string <insert_1> to a Boolean value.
- Severity
- 20 : Error
- Explanation
- The character string has the value <insert_1>. Only the character strings 'TRUE', 'FALSE', and 'UNKNOWN' can be cast to a Boolean value.
- Response
- Ensure that the character string being cast has one of the above values.
- BIP2456
- The value <insert_1> was of an unsuitable length <insert_2> for casting from a byte array to an integer.
- Severity
- 20 : Error
- Explanation
- The operand of a casting operation was of an unsuitable length for it to be cast to the target data type. To cast a byte array to an integer the length of the array must be 8.
- Response
- Check the logic of the message flow and redeploy.
- BIP2457
- Error casting character string <insert_1> to double.
- Severity
- 20 : Error
- Explanation
- The character string must be of the form '[+/-]d+[.d+][Ed+]'. The character string had the value <insert_1>.
- Response
- Ensure that the character string being cast represents a valid number.
- BIP2458
- Error casting character string <insert_3> to a TIME. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- A character string must have the form 'TIME 'hh&colon.mm&colon.ss[.f+]', or 'hh&colon.mm&colon.ss[.f+]' to be valid for casting to a TIME value.
- Response
- Ensure that the string represents a valid time value.
- BIP2459
- Error casting character string <insert_1> to a GMT time.
- Severity
- 20 : Error
- Explanation
- The character string has the value <insert_1>. A character string must have the form 'GMTTIME 'hh&colon.mm&colon.ss[.f+]', or 'hh&colon.mm&colon.ss[.f+]' to be valid for casting to a GMT time value.
- Response
- Ensure that the character string being cast has a valid format.
- BIP2460
- Error casting character string <insert_3> to a DATE. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- A character string must have the form 'DATE 'yyyy-mm-dd', or 'yyyy-mm-dd' to be valid for casting to a date.
- Response
- Ensure that the string being cast has a valid value.
- BIP2461
- Error casting character string <insert_3> to a TIMESTAMP. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- The character string must have a the form 'TIMESTAMP 'yyyy-mm-dd hh&colon.mm&colon.ss[.f+]', or 'yyyy-mm-dd hh&colon.mm&colon.ss[.f+]' to be valid for casting to a timestamp.
- Response
- Ensure that the string represents a valid time value.
- BIP2462
- Error casting character string <insert_1> to a GMT timestamp.
- Severity
- 20 : Error
- Explanation
- The character string has the value <insert_1>. A character string must have the form 'GMTTIMESTAMP 'yyyy-mm-dd hh&colon.mm&colon.ss[.f+]', or 'yyyy-mm-dd hh&colon.mm&colon.ss[.f]' to be valid for casting to a GMT timestamp.
- Response
- Ensure that the string being cast is formatted correctly.
- BIP2463
- Error casting the character string <insert_1> to an interval.
- Severity
- 20 : Error
- Explanation
- A character string must have the format 'INTERVAL '<field values>' <qualifier>' or '<field values>' to be valid for casting to an interval. Valid field values depend on the qualifier. For example, for a DAY TO SECOND interval the format is '[<sign>]<day> <hour>:<minute>:<second>'. All fields except the first are required to have two digits. Seconds, however, can also have a fractional part.
- Response
- Ensure the string being cast is formatted correctly. Refer to the information center for more information about field values and qualifiers.
- BIP2464
- Error casting interval <insert_1> to a numeric type.
- Severity
- 20 : Error
- Explanation
- An interval must have a qualifier which specifies only one field to be valid for casting to a numeric type.
- Response
- Ensure that the interval is of the appropriate type.
- BIP2465
- Can't cast <insert_1> to the type <insert_2>.
- Severity
- 20 : Error
- Explanation
- There is no way to convert <insert_1> into the data type <insert_2>.
- Response
- Ensure that the source and target data types and values in the casting operation are compatible.
- BIP2466
- (<insert_1>, <insert_2>) : The target database <insert_3> does not have the same characteristics as the reference database <insert_4>
- Severity
- 20 : Error
- Explanation
- All databases accessed from any one node must have the same characteristics regarding the functions and data types they support. This is certainly true if they are of the same type and level (e.g. they are both DB2 v 9.1) but may not be true otherwise.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Examine the database names reported in this message. If they are not as expected, correct the logic of the flow. If they are as expected, then either re-arrange the flow to use separate nodes for the accesses or re-arrange the data into databases of the same type.
- BIP2467
- (<insert_1>, <insert_2>) : Incompatible operands for IN predicate.
- Severity
- 20 : Error
- Explanation
- The values on the right of an IN predicate must be compatible with the data type of the expression on the left.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2468
- (<insert_1>, <insert_2>) : Data type constraint violation. Actual = <insert_3> Expected = <insert_4>
- Severity
- 20 : Error
- Explanation
- A field reference containing a type constraint reported that the specified field did not contain a scalar value of the required data type.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2469
- (<insert_1>, <insert_2>) : Invalid field reference constraint.
- Severity
- 20 : Error
- Explanation
- Scalar type constraints may not be applied to list field references, references to declared scalar variables or to references to database tables. UNCOORDINATED may only be applied to references to database tables. References to database tables may not have the list indicator [].
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2470
- (<insert_1>, <insert_2>) : Illegal type for operand <insert_4> of the operator <insert_3>. Valid types are <insert_5>.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2471
- (<insert_1>, <insert_2>) : The value <insert_5> supplied as operand <insert_4> of the operator <insert_3> is of an unsuitable type. Valid types are <insert_6>.
- Severity
- 20 : Error
- Explanation
- The expression supplying the operand must evaluate to a value of a suitable type. The given expression does not so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2472
- Zero rows updated. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- The database DELETE or UPDATE operation affected zero rows. This warning has been reported as an error because you have set the node property "Treat warnings as errors".
- Response
- This error is typically handled by the message flow's error recovery procedure and no further action is required.
- BIP2473
- (<insert_1>, <insert_2>) : Invalid search condition.
- Severity
- 20 : Error
- Explanation
- A search condition must produce a boolean result.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2474
- (<insert_1>, <insert_2>) : <insert_3> is not boolean.
- Severity
- 20 : Error
- Explanation
- A search condition evaluated to <insert_3>, which is not a boolean value. Search conditions must evaluate to boolean values.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the search condition evaluates to a boolean.
- BIP2475
- (<insert_1>, <insert_2>) : Illegal argument type for EXTRACT function.
- Severity
- 20 : Error
- Explanation
- The argument to the EXTRACT function must be a datetime or interval valued expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2476
- (<insert_1>, <insert_2>) : Illegal argument type for EXTRACT function called with value <insert_3>.
- Severity
- 20 : Error
- Explanation
- The argument to the EXTRACT function must be a datetime or interval valued expression. The EXTRACT function was called with the value <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the argument supplied to the EXTRACT function is a datetime or an interval.
- BIP2477
- (<insert_1>, <insert_2>) : Cannot extract <insert_3> field from value <insert_4>.
- Severity
- 20 : Error
- Explanation
- It was not possible to extract the specified field from the value supplied.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the value supplied contains the necessary information and is correctly formed.
- BIP2478
- (<insert_1>, <insert_2>) : Path argument to <insert_3> must not specify a list.
- Severity
- 20 : Error
- Explanation
- The path argument supplied to the <insert_3> function must point to a single field only.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the path argument points to a single field.
- BIP2479
- (<insert_1>, <insert_2>) : Illegal argument value <insert_3> to ABS function.
- Severity
- 20 : Error
- Explanation
- The ABS function was called with the value <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the value passed to the ABS function is valid.
- BIP2480
- (<insert_1>, <insert_2>) : The dynamic field reference does not resolve to a reference to a message field.
- Severity
- 20 : Error
- Explanation
- The dynamic field reference supplied must resolve to a message field. References to declared variables and uninitialized references are not acceptable.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2481
- (<insert_1>, <insert_2>) : Illegal argument value <insert_4> to <insert_3> function.
- Severity
- 20 : Error
- Explanation
- The argument to <insert_3> must be a numeric type. <insert_4> is not a numeric type.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only numeric types are passed as an argument to <insert_3>.
- BIP2482
- (<insert_1>, <insert_2>) : The dynamic field reference does not resolve to a valid reference.
- Severity
- 20 : Error
- Explanation
- The dynamic field reference supplied must resolve to a declared variable or a message field. Uninitialized references are not acceptable.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2483
- (<insert_1>, <insert_2>) : Illegal arguments (values <insert_3> and <insert_4>) to MOD function; integers required.
- Severity
- 20 : Error
- Explanation
- Both arguments to the MOD function must be integral values. The function was called with the arguments <insert_3> and <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only integral values are passed to the MOD function.
- BIP2484
- (<insert_1>, <insert_2>) : Syntax error. See further messages for details of the error.
- Severity
- 20 : Error
- Explanation
- Superficially, the ESQL program is syntactically correct. However, a value (for example, a date string) does not have the correct format. See further messages for details of the error.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2485
- (<insert_1>, <insert_2>) : Illegal 1st argument (value <insert_4>) to function <insert_3>; numeric value required; value of 2nd argument was <insert_5>.
- Severity
- 20 : Error
- Explanation
- First argument to the function <insert_3> must be a numeric value. The function was called with the values <insert_4>, <insert_5>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the first argument to <insert_3> is a numeric type.
- BIP2486
- (<insert_1>, <insert_2>) : Illegal 2nd argument to function <insert_3>; values supplied were <insert_4> and <insert_5>.
- Severity
- 20 : Error
- Explanation
- Second argument to the function <insert_3> must be an integral value. The function was called with the values <insert_4>, <insert_5>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the second argument to <insert_3> is an integral type.
- BIP2487
- (<insert_1>, <insert_2>) : Duplicate schema '%3'.
- Severity
- 20 : Error
- Explanation
- A schema of this name has already been defined. Another schema with the same name cannot be created. Neither can further items be added to the existing schema.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2488
- (<insert_1>, <insert_2>) Error detected whilst executing the SQL statement <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
- Response
- See the following messages for details of the error.
- BIP2489
- (<insert_1>, <insert_2>) : The value <insert_5> is not valid as parameter <insert_4> of the function <insert_3>. Valid types are <insert_6>.
- Severity
- 20 : Error
- Explanation
- The parameter must be a value of a suitable type within the range for which the function is defined.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2490
- (<insert_1>, <insert_2>) : Illegal data type for parameter <insert_4> of statement, function or operator <insert_3>. Valid types are <insert_5>.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2491
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> of the function <insert_3>. A field reference is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2492
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> of the function <insert_3>. A non-list field reference is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2493
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> of the function <insert_3>. A list is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2494
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> of the function <insert_3>. A reference to a variable of type <insert_5> is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2495
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> or parameter <insert_5> of the function <insert_3>. The types must be comparable.
- Severity
- 20 : Error
- Explanation
- The expressions supplying the parameters must evaluate to values of types which can be compared. The given expressions cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2496
- (<insert_1>, <insert_2>) : Illegal data type for target. A non-list field reference is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the target must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2497
- (<insert_1>, <insert_2>) : Illegal data type for target. A list field reference is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the target must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2498
- (<insert_1>, <insert_2>) : An error occurred when navigating to path element <insert_3> of the field reference at the given location.
- Severity
- 20 : Error
- Explanation
- Further messages are generated that provide details of the error.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2499
- (<insert_1>, <insert_2>) : Illegal arguments to SUBSTRING function called as <insert_3>, the end was before the beginning.
- Severity
- 20 : Error
- Explanation
- Valid syntax for SUBSTRING is: SUBSTRING( source_string [ [FROM start_position] | [BEFORE beforeExpression] | [AFTER afterExpression] ] [FOR string_length]).
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2501
- (<insert_1>, <insert_2>) : The value <insert_5> supplied as parameter <insert_4> of the function <insert_3> is of an unsuitable type. Valid types are <insert_6>.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression does not so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2502
- (<insert_1>, <insert_2>) : Illegal value <insert_5> for parameter <insert_4> of the function <insert_3>. Valid values are <insert_6>.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value within a suitable range. The given expression does not do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2503
- Invalid shared variable operation.
- Severity
- 20 : Error
- Explanation
- An SQL statement has attempted an operation involving shared variables which is outside the range permitted. You cannot move (by using DETACH/ATTACH) a subtree from one shared variable to another. You cannot use functions with side effects to change shared variables when the expression invoking the function also operates on shared variables.
- Response
- Correct the logic of the ESQL program and re-deploy the message flow.
- BIP2504
- (<insert_1>, <insert_2>) : The value <insert_5> supplied as parameter <insert_4> of the function <insert_3> and the value <insert_7> supplied as parameter <insert_6> must be of the same type.
- Severity
- 20 : Error
- Explanation
- The expressions supplying the parameters must evaluate to values of the same type. The given expressions do not so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2505
- (<insert_1>, <insert_2>) : Illegal type for parameter <insert_4> of the function <insert_3>. A list is required.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression does not do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2506
- (<insert_1>, <insert_2>) : An error occurred while attempting to cast <insert_3> and <insert_4> to <insert_5>
- Severity
- 20 : Error
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2507
- (<insert_1>, <insert_2>) : An error occurred while attempting to cast <insert_3>, <insert_4> and <insert_5> to <insert_6>
- Severity
- 20 : Error
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2508
- (<insert_1>, <insert_2>) : An error occurred while attempting to cast <insert_3>, <insert_4>, <insert_5> and <insert_6> to <insert_7>
- Severity
- 20 : Error
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2509
- (<insert_1>, <insert_2>) : An error occurred while attempting to cast <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7> and <insert_8> to <insert_9>
- Severity
- 20 : Error
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2510
- (<insert_1>, <insert_2>) : The value <insert_4> supplied as the parameter of the function <insert_3> is not within the range for which the function is defined.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a suitable value. The given expression does not do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2511
- (<insert_1>, <insert_2>) : The values <insert_4> and <insert_5> supplied as parameters of the function <insert_3> are not within the range for which the function is defined.
- Severity
- 20 : Error
- Explanation
- The expressions supplying the parameters must evaluate to a suitable value. The given expressions do not do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2512
- An operand was of type <insert_1> which is not suitable for the given function.
- Severity
- 20 : Error
- Response
- Correct the syntax of the SQL program and re-deploy.
- BIP2513
- Cannot construct a <insert_2> interval from <insert_1> parameters.
- Severity
- 20 : Error
- Response
- Correct the syntax of the SQL program and re-deploy.
- BIP2514
- Cannot construct a <insert_1> interval from the values <insert_2> and <insert_3>
- Severity
- 20 : Error
- Response
- Correct the syntax of the SQL program and re-deploy.
- BIP2515
- (<insert_1>, <insert_2>) : Illegal trim character <insert_3> argument to TRIM function.
- Severity
- 20 : Error
- Explanation
- The trim character argument to the TRIM function must be a character string, a byte string or a bit string, and must be of length 1. The trim character argument was <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the trim character argument is an appropriate data type and length.
- BIP2516
- Cannot construct a <insert_1> interval from the values <insert_2>, <insert_3>, <insert_4> and <insert_5>
- Severity
- 20 : Error
- Response
- Correct the syntax of the SQL program and re-deploy.
- BIP2517
- (<insert_1>, <insert_2>) : Variable <insert_3> has already been declared in the current scope.
- Severity
- 20 : Error
- Explanation
- An attempt was made to declare the variable <insert_3>, but this variable has already been declared within the current scope. You cannot declare the same variable more than once within the same scope.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Remove the second declaration, or substitute a different variable name, and redeploy the message flow.
- BIP2518
- Invalid value <insert_1> for <insert_2> field of INTERVAL.
- Severity
- 20 : Error
- Explanation
- <insert_1> is not a valid value for the <insert_2> field of an INTERVAL value.
- Response
- Ensure that only valid values for each of the INTERVAL fields are used to construct INTERVAL values.
- BIP2519
- (<insert_1>, <insert_2>) : A non scalar parameter was passed to statement <insert_4> against datasource <insert_3>.
- Severity
- 20 : Error
- Explanation
- Only scalar parameters may be passed to stored procedures
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2520
- (<insert_1>, <insert_2>) : Nested BEGIN ATOMIC statements.
- Severity
- 20 : Error
- Explanation
- The broker has detected an attempt to execute a BEGIN ATOMIC statement within the scope of another BEGIN ATOMIC statement. This is not allowed as it may lead to deadly embraces.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2521
- (<insert_1>, <insert_2>) : Error casting the value <insert_3> to <insert_4>.
- Severity
- 20 : Error
- Explanation
- An error occurred when casting a value to a different data type. This may be because no conversions exist between the two data types or because the particular value was unsuitable.
- Response
- Subsequent messages will indicate the context of the error.
- BIP2522
- (<insert_1>, <insert_2>) : Type mismatch in CASE expression.
- Severity
- 20 : Error
- Explanation
- The WHEN clause of a simple CASE expression must be compatible with the CASE clause.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2523
- (<insert_1>, <insert_2>) : Cannot assign to a symbolic constant or input message.
- Severity
- 20 : Error
- Explanation
- Values cannot be assigned to symbolic constants or input message fields.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2524
- (<insert_1>, <insert_2>) : Cannot assign a list to a non-list, nor a non-list to a list.
- Severity
- 20 : Error
- Explanation
- A list of values cannot be assigned to a scalar variable or single message field, nor can a scalar value be assigned to a list.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2525
- Error casting character string <insert_1> to an interval with qualifier <insert_2>.
- Severity
- 20 : Error
- Explanation
- The character string had the value <insert_1> which is not a valid representation of an interval with qualifier <insert_2>. A character string must have the format 'INTERVAL '<field values>' <qualifier>' or '<value>' for it to be cast to an interval. Valid field values might depend on the qualifier.
- Response
- Ensure the string that you are casting is formatted correctly. Consult the section 'ESQL reference' in the information center for more information about field values and qualifiers.
- BIP2526
- (<insert_1>, <insert_2>) : Illegal ATOMIC block usage.
- Severity
- 20 : Error
- Explanation
- The program is attempting an operation which may result in an atomic block being entered when higher level code is already inside an atomic block. This is not allowed as it may result in deadlocks. This situation may arise through code within an atomic block calling a function or procedure which also contains an atomic block. It can also arise as a result of a the use of a PROPAGATE statement within an atomic block.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2527
- (<insert_1>, <insert_2>) : The datasource <insert_3> does not support the data type <insert_4>.
- Severity
- 20 : Error
- Explanation
- The datasource <insert_3> does not support the data type <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite your expression to avoid the use of this data type, or connect to a different datasource.
- BIP2528
- (<insert_1>, <insert_2>) : Data type <insert_3> not supported for database interaction.
- Severity
- 20 : Error
- Explanation
- The data type <insert_3> cannot be passed to a database.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Do not attempt to pass values with this data type to the database.
- BIP2529
- (<insert_1>, <insert_2>) : The datasource <insert_3> does not support CASE expressions.
- Severity
- 20 : Error
- Explanation
- CASE expressions are not supported by this data source.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite the expression to avoid use of CASE, or connect to a different data source.
- BIP2530
- (<insert_1>, <insert_2>) : The datasource <insert_3> does not support the BETWEEN predicate.
- Severity
- 20 : Error
- Explanation
- BETWEEN is not supported by this data source.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite the expression to avoid use of BETWEEN, or connect to a different data source.
- BIP2531
- (<insert_1>, <insert_2>) : The datasource <insert_3> does not support the IN predicate.
- Severity
- 20 : Error
- Explanation
- IN is not supported by this data source.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite the expression to avoid use of IN, or connect to a different data source.
- BIP2532
- (<insert_1>, <insert_2>) : The datasource <insert_3> does not support the LIKE predicate.
- Severity
- 20 : Error
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite the expression to avoid use of LIKE, or connect to a different data source.
- BIP2533
- (<insert_1>, <insert_2>) : The data type <insert_3> is not a valid data type for parameter <insert_4> of the <insert_5> function. This parameter should be of data type <insert_6>. The value passed was <insert_7>.
- Severity
- 20 : Error
- Explanation
- Parameter <insert_4> is not of the correct data type for this function ( <insert_5> ).
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the argument(s) passed to this function are of the correct data type.
- BIP2534
- (<insert_1>, <insert_2>) : The dynamic field reference does not resolve to a modifiable quantity.
- Severity
- 20 : Error
- Explanation
- The dynamic field reference supplied must resolve to a modifiable quantity (a declared variable or a field in a modifiable message) because its use implies that its value is to be changed.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2535
- (<insert_1>, <insert_2>) : Field reference does not represent a database column.
- Severity
- 20 : Error
- Explanation
- A field reference which represents a database column must consist of at least two elements, the first of which must be 'Database'.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2536
- (<insert_1>, <insert_2>) : The dynamic field reference supplied to the <insert_3> statement does not resolve to a non-list field in a modifiable message tree.
- Severity
- 20 : Error
- Explanation
- The dynamic field reference supplied to the <insert_3> statement must resolve to a non-list field in a modifiable message tree.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only non-list references to modifiable trees are passed to the <insert_3> statement.
- BIP2537
- Node <insert_4>: Executing statement <insert_3> at (<insert_1>, <insert_2>).
- Severity
- 0 : Information
- BIP2538
- Node <insert_4>: Evaluating expression <insert_3> at (<insert_1>, <insert_2>).
- Severity
- 0 : Information
- BIP2539
- Node <insert_6>: Evaluating expression <insert_5> at (<insert_1>, <insert_2>). This resolved to <insert_3>. The result was <insert_4>.
- Severity
- 0 : Information
- BIP2540
- Node <insert_5>: Finished evaluating expression <insert_4> at (<insert_1>, <insert_2>). The result was <insert_3>.
- Severity
- 0 : Information
- BIP2541
- Node <insert_6>: (<insert_1>, <insert_2>) : Comparing <insert_3> and <insert_4>; result is <insert_5>.
- Severity
- 0 : Information
- BIP2542
- Node <insert_3>: (<insert_1>, <insert_2>) : Navigating path element.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP2543
- Node <insert_4>: (<insert_1>, <insert_2>) : Failed to navigate to path element number <insert_3> because it does not exist.
- Severity
- 10 : Warning
- BIP2544
- Node <insert_6>: Executing database SQL statement <insert_3> derived from (<insert_1>, <insert_2>); expressions <insert_4>; resulting parameter values <insert_5>.
- Severity
- 0 : Information
- BIP2545
- (<insert_1>, <insert_2>) : The expression <insert_3> evaluates to a value of type <insert_4> but a value of type <insert_5> is expected.
- Severity
- 20 : Error
- Explanation
- The given expression evaluates to NULL or to a data type which is not acceptable for its usage.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2546
- (<insert_1>, <insert_2>) : <insert_5> field type expression does not evaluate to INTEGER value; <insert_3> evaluates to <insert_4>.
- Severity
- 20 : Error
- Explanation
- A field type must be an INTEGER value. The expression <insert_3> evaluates to a value of type <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only expressions evaluating to INTEGER values are used to designate field types with <insert_5>.
- BIP2547
- (<insert_1>, <insert_2>) : <insert_3> field name expression cannot evaluate to a CHARACTER value.
- Severity
- 20 : Error
- Explanation
- A field name must be a CHARACTER value. The expression supplied to <insert_3> cannot evaluate to a CHARACTER value.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2548
- (<insert_1>, <insert_2>) : A correlation name must be given.
- Severity
- 20 : Error
- Explanation
- Database tables must be assigned a correlation name in the FROM clause of a SELECT statement. This correlation name must then be used for subsequent references to that table.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2549
- (<insert_1>, <insert_2>) : Type mismatch assigning to variable; value <insert_3> inconsistent with type <insert_4>.
- Severity
- 20 : Error
- Explanation
- The source expression produced a value of <insert_3> but the target variable was declared with a type of <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that only values of the appropriate data type are assigned to declared variables.
- BIP2550
- The first parameter of a PASSTHRU or EVAL function cannot evaluate to a list.
- Severity
- 20 : Error
- Explanation
- The first parameter of a PASSTHRU or EVAL function must evaluate to something that can be represented as a character string.
- Response
- Check the first parameter of the PASSTHRU or EVAL function. Ensure that it is not an expression that will evaluate to a list of values.
- BIP2551
- (<insert_1>, <insert_2>) : The number <insert_3> was too large for an INTEGER or DECIMAL literal.
- Severity
- 20 : Error
- Explanation
- The number was <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure the number is within the scale and precision limits for the specified data type and redeploy the message flow.
- BIP2552
- (<insert_1>, <insert_2>) : The number being converted <insert_3> was too large/small to be represented as a 64 bit floating point number.
- Severity
- 20 : Error
- Explanation
- The number being converted was <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the number being converted is within the scale and precision limits for a 64 bit floating point number and redeploy the message flow.
- BIP2553
- (<insert_1>, <insert_2>) : Unexpected character <insert_3> in input.
- Severity
- 20 : Error
- Explanation
- The character was <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2554
- (<insert_1>, <insert_2>) : Unrecognized character <insert_3> in input.
- Severity
- 20 : Error
- Explanation
- The character was <insert_3>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2555
- Error casting a character string <insert_1> to an interval (qualifier <insert_2>).
- Severity
- 20 : Error
- Explanation
- The interval qualifier given on the cast specification didn't match the interval qualifier in the source character string. The character string had the value <insert_1>. The interval qualifier given in the cast specification was <insert_2>.
- Response
- See the documentation for details of which combinations of character strings and qualifiers are acceptable.
- BIP2556
- An attempt has been made to assign a scalar, row or list quantity to a target of a different basic type.
- Severity
- 20 : Error
- Explanation
- Scalar values may only be assigned to scalars, rows may only be assigned to rows and lists may only be assigned to lists.
- Response
- Check and correct the ESQL program. Pay particular attention to SELECT functions. Normally these return a list. However SELECT's containing a THE clause return a row.
- BIP2557
- (<insert_1>, <insert_2>) : Invalid function name.
- Severity
- 20 : Error
- Explanation
- Function names must be simple identifier chains and may not contain namespace identifiers or expressions of any kind.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2558
- (<insert_1>, <insert_2>) : Undefined function <insert_3>.<insert_4>.
- Severity
- 20 : Error
- Explanation
- The program is attempting to call a function which is not defined or is not in the schema path.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2559
- (<insert_1>, <insert_2>) : Illegal argument(s) <insert_4> to <insert_3> function.
- Severity
- 20 : Error
- Explanation
- The arguments to the bit manipulation functions (BITAND, BITOR, BITNOT, BITXOR) must be integers. The function was called with arguments <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2560
- (<insert_1>, <insert_2>) : A reference variable is required here.
- Severity
- 20 : Error
- Explanation
- The statement or function requires a reference variable. The name given must therefore be the name of a declared reference variable and cannot be extended (by a dot and another name).
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2561
- (<insert_1>, <insert_2>) : An attempt was made to call the function <insert_3>()' with <insert_4> parameters but this function requires <insert_5> parameters.
- Severity
- 20 : Error
- Explanation
- Most functions must be called with the correct number of arguments. Others will accept any number of arguments above a given minimum.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2562
- Node <insert_2>: Assigning a list to <insert_1>.
- Severity
- 0 : Information
- BIP2563
- Node <insert_3>: Deleting all <insert_1> instances of <insert_2>, since source list for assignment was empty.
- Severity
- 0 : Information
- BIP2564
- Node <insert_4>: Deleting instance <insert_1> of <insert_2>, since source list for assignment had <insert_3> instances.
- Severity
- 0 : Information
- BIP2565
- Node <insert_5>: Deleting instances <insert_1> through <insert_2> of <insert_3>, since source list for assignment had <insert_4> instances.
- Severity
- 0 : Information
- BIP2566
- Node <insert_3>: Assigning value <insert_1> to field / variable <insert_2>.
- Severity
- 0 : Information
- BIP2567
- Node <insert_2>: Assigning NULL to <insert_1>, thus deleting it.
- Severity
- 0 : Information
- BIP2568
- Node <insert_3>: Copying sub-tree from <insert_1> to <insert_2>.
- Severity
- 0 : Information
- BIP2569
- Node <insert_3>: (<insert_1>, <insert_2>) : WHERE clause evaluated to false or unknown. Iterating FROM clause.
- Severity
- 10 : Warning
- BIP2570
- Node <insert_3>: (<insert_1>, <insert_2>) : There were no items in the FROM clause satisfying the WHERE clause.
- Severity
- 10 : Warning
- BIP2571
- Node <insert_3>: (<insert_1>, <insert_2>) : Failed to find any more items in the FROM clause satisfying the WHERE clause.
- Severity
- 10 : Warning
- BIP2572
- Node: <insert_3>: (<insert_1>, <insert_2>) : Finding one and only SELECT result.
- Severity
- 10 : Warning
- BIP2573
- Node <insert_3>: (<insert_1>, <insert_2>) : Finding first SELECT result.
- Severity
- 10 : Warning
- BIP2574
- Node <insert_3>: (<insert_1>, <insert_2>) : Finding next SELECT result.
- Severity
- 10 : Warning
- BIP2575
- A Filter expression must evaluate to the <insert_1> data type.
- Severity
- 20 : Error
- Explanation
- The expression given in the 'filterExpression' attribute of a Filter node must evaluate to a <insert_1> type value.
- Response
- Correct the expression so that it returns a value of the correct type and redeploy the message flow.
- BIP2576
- The expression in a Filter node resulted in the value <insert_1>; boolean value expected.
- Severity
- 20 : Error
- Explanation
- The filterExpression configuring a Filter node must evaluate to a boolean value. The filterExpression resulted in the value <insert_1>.
- Response
- Correct the expression so that it always returns a value of the correct type.
- BIP2577
- (<insert_1>, <insert_2>) : <insert_3> field type expression cannot evaluate to INTEGER.
- Severity
- 20 : Error
- Explanation
- A field type must be an INTEGER value. The field type expression supplied to <insert_3> cannot evaluate to INTEGER.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2578
- (<insert_1>, <insert_2>) : Dynamic field reference <insert_3> is not detached and therefore cannot be attached to <insert_4>.
- Severity
- 20 : Error
- Explanation
- The message tree fragment pointed to by the dynamic field reference <insert_3> has not been detached. Only message tree fragments which are detached can be attached to another message tree.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that you detach the message tree fragment before attempting to reattach it elsewhere.
- BIP2579
- (<insert_1>, <insert_2>) : The function <insert_3> was not known.
- Severity
- 20 : Error
- Explanation
- <insert_3> was not known as a function.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Rewrite the SQL expression so that the condition does not occur.
- BIP2580
- (<insert_1>, <insert_2>) : No external data source specified for this node.
- Severity
- 20 : Error
- Explanation
- An attempt was made to access an external database table, but no database inputs have been specified for this Compute, Filter or Database node.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Add database inputs for each table that is accessed, and redeploy the message flow.
- BIP2581
- (<insert_1>, <insert_2>) : Field reference <insert_3> does not exist and could not be created when declaring <insert_4>.
- Severity
- 20 : Error
- Explanation
- A dynamic field reference may not point to a nonexistent target. The target field reference <insert_3> specified for the declaration of dynamic field reference <insert_4> does not exist and could not be created.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: When declaring a dynamic field reference ensure that the specified target either exists or can be created.
- BIP2582
- (<insert_1>, <insert_2>) : The argument <insert_3> passed to the function <insert_4> is not a valid UUID
- Severity
- 20 : Error
- Explanation
- The argument <insert_3> is not a valid UUID.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the argument passed to this function is valid
- BIP2583
- (<insert_1>,<insert_2>) : Expected a dynamic directional modifier but found <insert_3>.
- Severity
- 20 : Error
- Explanation
- One of FIRSTCHILD, LASTCHILD, NEXTSIBLING or PREVIOUSSIBLING was expected but <insert_3> was found.
- Response
- Correct the expression and redeploy the message flow.
- BIP2584
- Cannot add interval <insert_2> to time value <insert_1>.
- Severity
- 20 : Error
- Explanation
- The interval value is not suitable because it contains one of the fields YEAR, MONTH or DAY.
- Response
- No user action required.
- BIP2585
- Invalid interval qualifier for time subtraction, subtracting <insert_2> from <insert_1> with qualifier <insert_3>.
- Severity
- 20 : Error
- Explanation
- When giving an interval qualifier for the precision of a time subtraction, the qualifier must not contain any of the fields YEAR, MONTH or DAY.
- Response
- Correct the logic of the SQL program redeploy the message flow.
- BIP2586
- Cannot add interval <insert_2> to date value <insert_1>.
- Severity
- 20 : Error
- Explanation
- The interval value is not suitable because it contains one of the fields HOUR, MINUTE, SECOND.
- Response
- No user action required.
- BIP2587
- Invalid interval qualifier for date subtraction, subtracting <insert_2> from <insert_1> with qualifier <insert_3>.
- Severity
- 20 : Error
- Explanation
- When giving an interval qualifier for the precision of a date subtraction, the qualifier must not contain any of the fields HOUR, MINUTE or SECOND.
- Response
- Correct the logic of the SQL program redeploy the message flow.
- BIP2588
- Node <insert_4>: (<insert_1>, <insert_2>) : Evaluating string <insert_3> as an SQL statement or expression.
- Severity
- 0 : Information
- BIP2589
- Incompatible types for comparison between values <insert_1> and <insert_2>.
- Severity
- 20 : Error
- Explanation
- The values <insert_1> and <insert_2> cannot be compared, because they are of incompatible types.
- Response
- Other messages will give an indication of context of this error.
- BIP2590
- Error casting character string <insert_1> to a byte string.
- Severity
- 20 : Error
- Explanation
- An attempt was made to cast the character string <insert_1> to a byte string, but the string was of the wrong format. There must be an even number of hexadecimal digits (0-9, a-f, A-F).
- Response
- Other messages will give an indication of context of this error.
- BIP2591
- Error casting character string <insert_1> to a bit string.
- Severity
- 20 : Error
- Explanation
- An attempt was made to cast the character string <insert_1> to a bit string, but the string was of the wrong format. The string must consist only of the characters '0' and '1'.
- Response
- Other messages will give an indication of context of this error.
- BIP2592
- Error converting character string <insert_3> to decimal. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- An attempt was made to convert a character string to a decimal, but the string was of the wrong format. The string must be of the form [<sign>]<digits>[.<digits>][[<sign>]E<digits>], where <sign> can be one of '+' or '-', and <digits> are one or more decimal digits (0-9). The E can be either upper or lower case. This string can be both preceded and followed by any number of blanks, but no blanks can occur within the given format. The maximum precision is 34 digits, and the maximum exponent is 999,999,999.
- Response
- Look for other messages that give an indication of context of this error.
- BIP2593
- Error converting decimal <insert_3> to integer. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- An attempt was made to convert a decimal number to an integer but the given number could not be converted. This could be because it is too big to be represented as an integer, the number the number has one of the special values NAN or INFINITY or because the number had a fractional part and the operation was one which does not allow the rounding of fractions.
- Response
- Other messages will give an indication of context of this error.
- BIP2594
- Error converting decimal <insert_3> to float. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- An attempt was made to convert a decimal number to a float but the given number could not be converted. This could either be because it is too big to be represented as a float or because the number the number has one of the special values NAN or INFINITY.
- Response
- Other messages will give an indication of context of this error.
- BIP2595
- Error casting character string <insert_3> to an integer. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- An attempt was made to cast the character string <insert_1> to an integer, but the string was of the wrong format.
- Response
- Other messages will give an indication of context of this error.
- BIP2596
- (<insert_1>, <insert_2>) : Cannot take bitstream of partially complete output.
- Severity
- 20 : Error
- Explanation
- The BITSTREAM function can only be used with input messages.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2597
- (<insert_1>, <insert_2>) : An expression which evaluates to a scalar value is required here.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2598
- Error scaling decimal. Attempted precision <insert_3> scale <insert_4>. State = <insert_1> <insert_2> '0' '
- Severity
- 20 : Error
- Explanation
- An attempt was made to convert a decimal value to a precision or scale which are beyond the limits of the decimal data type. The maximum precision is 34 the maximum scale is 999,999,999
- Response
- Other messages will give an indication of the context of this error.
- BIP2599
- The ESQL deployed to the node <insert_1> is invalid.
- Severity
- 20 : Error
- Explanation
- The message could not be processed because the ESQL deployed to the node is invalid. Examine previous error messages for details of the problem.
- Response
- Correct the logic of the ESQL program and re-deploy the message flow.
- BIP2601
- Unable to locate the WebSphere MQ manager class required by node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The instance of the WebSphere MQ manager class could not be located when required by node <insert_1>. The current message flow has been terminated. This error is probably indicative of an internal software malfunction.
- Response
- If this occurs frequently, restart the message broker. If it continues to occur, contact your IBM support center.
- BIP2602
- Unable to create thread context in message flow node <insert_1>.
- Severity
- 20 : Error
- Explanation
- During the execution of a message flow in node <insert_1>, a new thread was created. However, a context data area could not be created for this thread. The current message flow is terminated.
- Response
- This may be indicative of a shortage of virtual memory. If other error messages seem to indicate this may be the reason, then consider reducing the memory requirements for the system, or increase the amount of physical and/or virtual memory available. If lack of storage does not seem to be the reason, and this problem occurs continually contact your IBM support center.
- BIP2603
- Unable to insert thread context into list for message flow node <insert_1>.
- Severity
- 20 : Error
- Explanation
- During the execution of a message flow in node <insert_1>, a new thread was created. However, the context data area could not be inserted into the list of contexts. The current message flow is terminated.
- Response
- This may be indicative of a shortage of virtual memory. If other error messages seem to indicate this may be the reason, then consider reducing the memory requirements for the system, or increase the amount of physical and/or virtual memory available. If lack of storage does not seem to be the reason, and this problem occurs continually contact your IBM support center.
- BIP2604
- Node failed to open WebSphere MQ queue <insert_2> owned by queue manager <insert_1>&colon. completion code <insert_3>; reason code <insert_4>.
- Severity
- 20 : Error
- Explanation
- A message flow node failed to open the indicated WebSphere MQ queue, with the resulting WebSphere MQ completion and reason codes. The message flow attempts to open the queue periodically until the queue is defined. The message flow is not fully operational until this has been done.
- Response
- Define the WebSphere MQ queue to the indicated queue manager. If the incorrect queue manager and/or queue name were specified, then correct the queue name using the Message Broker Toolkit and redeploy the message broker.
- BIP2605
- Unable to start transaction coordinated by WebSphere MQ; MQBEGIN failed; MQCC=<insert_2>, MQRC=<insert_3>, broker node <insert_4>, queue manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message flow attribute 'coordinatedTransaction' was specified as 'yes'. However, when the broker node <insert_4> reading from queue manager <insert_1> attempted to start the coordinated transaction, the MQBEGIN operation failed with the indicated WebSphere MQ reason code. The message flow continues, but the transaction will not be coordinated, and this may cause subsequent errors or unpredictable results.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2606
- Unable to get message from WebSphere MQ queue <insert_1>: MQCC=<insert_2>; MQRC=<insert_3>; node <insert_4>.
- Severity
- 20 : Error
- Explanation
- A node <insert_4> failed to get a message from WebSphere MQ queue <insert_1> using the MQGET function. The WebSphere MQ return code and reason code returned are as displayed. The node periodically retries the MQGET until it is successful.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2607
- Unable to rollback a WebSphere MQ transaction; MQBACK failed; queue manager=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>; message flow node <insert_4>.
- Severity
- 20 : Error
- Explanation
- Message flow node <insert_4> attempted to rollback a WebSphere MQ unit of work using the MQBACK function, but the rollback failed. The WebSphere MQ return code and reason code returned from MQBACK are displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2608
- Unable to inquire on WebSphere MQ queue <insert_1>: MQCC=<insert_2>; MQRC=<insert_3>; node <insert_4>.
- Severity
- 20 : Error
- Explanation
- Node <insert_4> issued an MQINQ function to inquire about the status of queue <insert_1> but the inquire failed. The WebSphere MQ completion code and reason code returned are as displayed. Recovery processing of a backed out message may not work as expected.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2609
- Unable to open WebSphere MQ queue manager <insert_3> for inquire: MQCC=<insert_1>; MQRC=<insert_2>; node <insert_4>.
- Severity
- 20 : Error
- Explanation
- An attempt to open the named connected WebSphere MQ queue manager <insert_3> failed when inquiring about its object attributes, during the processing of node <insert_4>. The WebSphere MQ completion and reason codes are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. Recovery processing of a backed out message may not work as expected.
- BIP2610
- Unable to close WebSphere MQ queue manager object: MQCC=<insert_1>; MQRC=<insert_2>; node <insert_3>.
- Severity
- 20 : Error
- Explanation
- An attempt by node <insert_3> to close the connected WebSphere MQ queue manager failed. The WebSphere MQ completion code and reason code returned are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2611
- Unable to open WebSphere MQ backout requeue queue: queue manager=<insert_1>; queue=<insert_2>; MQCC=<insert_3>; MQRC=<insert_4>; message flow node <insert_5>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_5> was unable to open or get the backout requeue queue to backout a WebSphere MQ message, with the indicated WebSphere MQ completion and reason codes. The message may not be backed out as intended.
- Response
- If there is a previous message, take any recovery action described for that error. Otherwise examine the WebSphere MQ completion and reason codes and take appropriate action.
- BIP2612
- Unable to open WebSphere MQ dead letter queue: queue manager=<insert_1>; queue=<insert_2>; MQCC=<insert_3>; MQRC=<insert_4>; message flow node <insert_5>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_5> was unable to open or get the WebSphere MQ dead letter queue to backout a WebSphere MQ message, with the indicated WebSphere MQ completion and reason codes. A previous message may provide further information. The message may not be backed out as intended.
- Response
- If there is a previous message, take any recovery action described for that error. Otherwise examine the WebSphere MQ completion and reason codes and take appropriate action.
- BIP2613
- Unable to backout a message; MQPUT to queue <insert_1> failed: MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_4> was unable to backout a message as it failed to put it to either the backout requeue queue or the WebSphere MQ dead letter queue, defined as queue <insert_1>.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2614
- Unable to commit a WebSphere MQ transaction to backout; MQCMIT failed; queueName=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 20 : Error
- Explanation
- The specified node was unable to commit a WebSphere MQ unit of work where the message needed to be backed out, because the MQCMIT function failed. The state of the message flow and any messages processed within the unit of work may be unpredictable, depending on the reason for the WebSphere MQ error.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2615
- The WebSphere MQ input node <insert_1> has backed out the message to the backout requeue or the dead letter queue.
- Severity
- 0 : Information
- Explanation
- Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
- Response
- No user action required.
- BIP2616
- Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 20 : Error
- Explanation
- The message broker was unable to commit a WebSphere MQ unit of work because the MQCMIT function failed. The state of any messages processed within the unit of work may be unpredictable, depending on the reason for the WebSphere MQ error.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2617
- Output message is empty; output node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker output node <insert_1> has received a message to write to an WebSphere output queue, but the message appears to be empty. This error may be generated when 1) there is no MQMD and no message content in the output bitstream (there really is no data) or 2) there is no MQMD and the size of the message content is less that the size of the MQMD (it appears there is no content). This situation can occur when a output message is built incorrectly using the Compute node.
- Response
- Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker.
- BIP2618
- Output message does not contain a valid MQMD; output node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker output node <insert_1> has received a message to write to an WebSphere output queue, but the message does not contain a valid MQMD. This situation can occur when a output message is built incorrectly using the Compute node.
- Response
- Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker.
- BIP2619
- Output node <insert_1> expected a distribution list but one did not exist.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker output node <insert_1> was invoked and the Destination Mode property was set to "list". However, a valid distribution list was not found.
- Response
- Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker.
- BIP2620
- Unable to write message to queue <insert_2> on queue manager <insert_1>. MQPUT failed: MQCC=<insert_3>; MQRC=<insert_4>; message flow node <insert_5>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_5> was unable to write a WebSphere MQ message as it failed to put it to the queue <insert_2> belonging to queue manager <insert_1>. The completion and reason code from the MQPUT operation are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2621
- Conversion error occurred with value <insert_1> for message flow node <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_2> was unable to convert the specified value to a multi byte character string. The current message flow is terminated.
- Response
- Check the message flow to determine the cause of the error.
- BIP2622
- Message successfully output by output node <insert_3> to queue <insert_2> on queue manager <insert_1>.
- Severity
- 0 : Information
- BIP2623
- Unable to open queue <insert_2> on WebSphere MQ queue manager <insert_1>: completion code <insert_3>; reason code <insert_4>.
- Severity
- 20 : Error
- Explanation
- A message flow node failed to open the indicated WebSphere MQ message queue. The error codes relate to the MQOPEN call.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If the open failed because the queue manager or queue did not exist, define these objects to WebSphere MQ. If the failure of the open was because incorrect object names were specified, correct the message flow configuration and attempt to redeploy the message broker.
- BIP2624
- Unable to connect to queue manager <insert_1>: MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_4> failed to connect to the WebSphere MQ queue manager <insert_1>. The return and reason codes returned by the MQCONN are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference online help to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If the open failed because the queue manager did not exist, define this object to WebSphere MQ. If the failure of the open was because an incorrect queue manager name was specified, correct the message flow configuration and attempt to redeploy the message broker.
- BIP2625
- Warning when writing message to queue <insert_2> on queue manager <insert_1>. MQPUT warning: MQCC=<insert_3>; MQRC=<insert_4>; message flow node <insert_5>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_5> received a warning when writing a WebSphere MQ message to queue <insert_2> owned by queue manager <insert_1>; however, the message was successfully queued. The return and reason code from the MQPUT are as displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2626
- Unable to open queue. Queue manager name <insert_1> is too long; node <insert_2>.
- Severity
- 20 : Error
- Explanation
- The node <insert_2> failed to open a WebSphere MQ queue as the specified queue manager name <insert_1> was longer than the maximum size allowed by WebSphere MQ.
- Response
- Correct the message flow configuration and redeploy the message broker.
- BIP2627
- Unable to open queue <insert_1>: name is too long; node <insert_2>.
- Severity
- 20 : Error
- Explanation
- The node <insert_2> failed to open a WebSphere MQ queue as the specified queue name <insert_1> was longer than the maximum size allowed by WebSphere MQ.
- Response
- Correct the message flow configuration and redeploy the message broker.
- BIP2628
- Exception condition detected on input node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The input node <insert_1> detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2629
- Broker termination request received.
- Severity
- 0 : Information
- Explanation
- A request was received to terminate the message broker.
- Response
- No user action required.
- BIP2630
- No backout queue or DLQ defined for a message to be backed out; input node <insert_2> received from queue <insert_1>
- Severity
- 0 : Information
- Explanation
- The input node <insert_2> received a message from queue <insert_1>, but was forced to attempt a backout due to the detection of an internal failure condition associated with it. The message broker has now attempted to propagate the message to the 'backoutRequeueQueueName' or the dead letter queue, but neither of these queues exist. The message is no longer processed by the message flow and continues to be backed out periodically. This situation can cause other messages to build up on the input queue until this message is removed or successfully processed.
- Response
- Examine previous messages and possibly the message flow to determine why the message is being backed out. Defining either the 'backoutRequeueQueue' or the dead letter queue will cause the message to be propagated to one of those queues.
- BIP2631
- Backed out message being propagated to failure terminal; node <insert_1>.
- Severity
- 0 : Information
- Explanation
- Node <insert_1> has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal of the node.
- Response
- Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2632
- Message received and propagated to 'out' terminal of MQ input node <insert_1>.
- Severity
- 0 : Information
- BIP2633
- Warning when starting transaction coordinated by WebSphere MQ; MQBEGIN failed: MQCC=<insert_1>; MQRC=<insert_2>; node <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The message flow attribute 'coordinatedTransaction' was specified as 'yes'. However, when the broker attempted to start the coordinated transaction in node <insert_3>, the MQBEGIN function returned a warning as indicated by the WebSphere MQ reason code. The message flow continues, but the transaction may not be being coordinated as expected, and this may cause subsequent errors or unpredictable results.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2634
- Exception condition detected: object label <insert_1>; input node <insert_2>.
- Severity
- 20 : Error
- Explanation
- An input node detected an error whilst processing a message. The message flow has been rolled back and, if the message was being processed in a unit of work, will remain on the input queue to be processed again. Following messages will indicate the cause of this exception which was generated in the STL container classes.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2635
- Exception during destination list processing; output node <insert_1>.
- Severity
- 20 : Error
- Explanation
- While processing a destination list in the output node <insert_1> an error (or errors) occurred.
- Response
- Check the preceding error messages to determine what effect this error causes, taking any action as described by those messages.
- BIP2636
- Warning when receiving a message: MQGET returned MQCC=<insert_1>, MQRC=<insert_2>; message flow node <insert_3>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_3> received a message from a queue, but a warning was generated. The return and reason code from the MQGET operation are as displayed. The message will be propagated to the failure terminal of the node.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2637
- Message propagated to failure terminal; node <insert_1>.
- Severity
- 0 : Information
- BIP2638
- The MQ output node <insert_5> attempted to write a message to queue <insert_2> connected to queue manager <insert_1>. The MQCC was <insert_3> and the MQRC was <insert_4>.
- Severity
- 0 : Information
- BIP2639
- Unable to convert backout requeue queue name to Unicode for message flow node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_1> was unable to convert the backout requeue queue name to a Unicode string. The current message flow is terminated.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2640
- Unable to convert dead letter queue name to Unicode for message flow node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_1> was unable to convert the dead letter queue name to a Unicode string. The current message flow is terminated.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2641
- Unable to disconnect from the WebSphere MQ queue manager; MQDISC failed; queue manager=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 10 : Warning
- Explanation
- The message broker was unable to disconnect from the WebSphere MQ queue manager because the MQDISC function failed. The broker operation is unlikely to be affected, since this situation will normally occur during broker shutdown.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2642
- ReplyToQ name not specified in message MQMD; output node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message flow node <insert_1> could not put the message to the ReplyToQ as its name is not specified in the MQMD of the message.
- Response
- Make sure the name of the ReplyToQ is specified in the MQMD of the message.
- BIP2643
- Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>.
- Severity
- 10 : Warning
- Explanation
- The message broker was unable to commit a WebSphere MQ unit of work because the MQCMIT function failed. The state of any messages processed within the unit of work may be unpredictable, depending on the reason for the WebSphere MQ error.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2644
- Exception condition detected on input node: <insert_1>.
- Severity
- 0 : Information
- Explanation
- Node <insert_1> has received a message, but an exception was generated whilst initializing it's internal representation. The message broker is propagating the message to the failure terminal of the node.
- Response
- If 'complete' or 'immediate' MRM, DFDL, JSON or XMLNSC message body validation is being applied to messages received by this node, it's possible the format of the body of the received message is invalid. Examine further messages for confirmation of this or to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2645
- Exception condition detected on input node <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message, but an exception was generated while initializing its internal representation. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue that is associated with this node.
- Response
- If 'complete' or 'immediate' message body validation for the MRM, DFDL, JSON or XMLNSC domain is being applied to messages that are received by this node, it's possible that the format of the body of the received message is not valid. Examine further messages for confirmation of this, or to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing that is required.
- BIP2646
- Exception condition detected on input node: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message, but an exception was generated whilst initializing it's internal representation. The failure terminal is attached but previous attempts to successfully process this message down this terminal have failed. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue. Having now reached the 'attempt limit' for processing the message down the failure terminal, the message broker is now putting the message to the requeue or dead letter backout queue associated with this node.
- Response
- If 'complete' or 'immediate' MRM, DFDL, JSON or XMLNSC message body validation is being applied to messages received by this node, it's possible the format of the body of the received message is invalid. Examine further messages to confirm this. Also, examine previous messages to determine why the exception is not being successfully processed when routed down the failure terminal. Correct these situations if possible. Perform any local error recovery processing required.
- BIP2647
- Error condition detected on input node: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message, but a warning was received from the MQGET operation. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node.
- Response
- Examine the other messages to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2648
- Message backed out to a queue; node <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
- Response
- Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2649
- Error condition detected on input node: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message, but a warning was received from the MQGET operation. The failure terminal is attached, but previous attempts to successfully process the message down this terminal have failed. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue. Having now reached the 'attempt limit' for processing the message down the failure terminal, the message broker is now putting the message to the requeue or dead letter backout queue associated with this node.
- Response
- Examine previous messages to determine why the message is not being successfully processed when routed down the failure terminal. Correct the situation if possible. Perform any local error recovery processing required.
- BIP2650
- Message backed out to a queue; node <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is attached, but previous attempts to successfully process the message down this terminal have also failed. The MQMD 'backoutCount' of the message now equals twice the 'backoutThreshold' defined for the WebSphere MQ input queue. Having now reached the 'attempt limit' for both these paths in the flow, the message broker is now putting the message to the requeue or dead letter backout queue associated with this node.
- Response
- Examine previous messages and the message flow to determine why the message is being backed out. Also, examine previous messages to determine why the error is not being successfully processed when routed down the failure terminal. Correct these situations if possible. Perform any local error recovery processing required.
- BIP2651
- Error condition detected on input node: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> received a message, but a warning was raised from the MQGET operation. MQRC=<insert_2>2
- Response
- Examine the other messages to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2652
- Message backed out to a queue; node <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow.
- Response
- Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
- BIP2653
- The WebSphere MQ Queue Manager <insert_1> does not support the MQOptimizedFlow performance options.
- Severity
- 20 : Error
- Explanation
- The deploy is rejected
- Response
- None
- BIP2654
- MQOptimizedFlow is not supported on OS/390
- Severity
- 20 : Error
- Explanation
- The Configuration Message is rejected
- Response
- The deploy is rejected
- BIP2655
- MQOptimizedFlow has detected a non-JMS input message
- Severity
- 10 : Warning
- Explanation
- An MQOptimizedFlow can only process JMS MQ messages. All input messages must be JMS compliant. If a dead letter queue (DLQ) is defined, the message will be sent to the dead letter queue. If a DLQ is not defined the flow will block
- Response
- To take advantage of this optimized pubsub node, use the JMS message model
- BIP2656
- Unable to open queue <insert_1> on WebSpehere Broker Queue Manager <insert_2> because the serialization token <insert_3>3 is already in use.
- Severity
- 0 : Information
- Explanation
- An MQInput node in another message flow has already connected to the shared queue using the same serialization token. This MQInput node will retry to connect to the queue.
- Response
- No user action required
- BIP2657
- MQGetNode <insert_6> has completed its MQGET() call. The returned MQ codes are: MQCC=<insert_4>, MQRC=<insert_5>.
- Severity
- 0 : Information
- Explanation
- MQGetNode <insert_6> has made <insert_3> attempt(s) at calling MQGET() to read queue <insert_2> of queue manager <insert_1>. The last call returned with MQ completion code <insert_4> and reason code <insert_5>.
- Response
- If the call(s) failed (returned with a non-zero return code), check the error codes and the other information provided to determine the cause of the failure and take any action necessary to resolve the problem. Possible causes include incorrect queue name, queue not readable, and message too large.
- BIP2658
- MQGetNode <insert_2> is propagating a message to the <insert_1> Terminal.
- Severity
- 0 : Information
- Explanation
- None
- Response
- None
- BIP2660
- The message received at output node <insert_5> is empty. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker output node <insert_5> has received a message for writing to a queue, but the message's bit stream is too short to be a valid message. This situation can occur when a message is built incorrectly by a Compute node (e.g. there is no MQMD).
- Response
- Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy.
- BIP2661
- The message received at output node <insert_5> does not contain a valid MQMD. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Broker output node <insert_5> has received a message to write to an WebSphere output queue, but the message does not contain a valid MQMD. This situation can occur when a output message is built incorrectly using a Compute node.
- Response
- Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy.
- BIP2662
- Invalid queue manager or queue name. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- The queue manager or queue name cannot be converted to a form acceptable to the queue manager. This may be because it contains characters not available in the queue manager's code page or because it is too long
- Response
- Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker.
- BIP2663
- Invalid reply to queue manager or queue name in output node <insert_5>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- The reply to queue manager or reply to queue name cannot be converted to a form acceptable to the queue manager. This may be because it contains characters not available in the queue manager's code page or because it is too long
- Response
- Correct the output node's configuration and redeploy the message flow.
- BIP2664
- It does not currently appear to be possible to get this message. Node <insert_5>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- BIP2665
- Output node <insert_5> expected a distribution list but one did not exist. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An MQ output node with the "Destination Mode" property set to "list" received a message but there was no valid distribution list, that is, it did not contain a "Destination" folder in turn containing an "MQ" folder.
- Response
- Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy the broker.
- BIP2666
- An error occurred in node <insert_7> when opening queue <insert_6> on queue manager <insert_5>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An error occurred when a message flow node attempted to open a queue. The reason code from the MQOPEN is displayed as the 3rd (native error) state.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2667
- An error occurred in node <insert_7> writing message to queue <insert_6> on queue manager <insert_5>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An error occurred when a message flow node attempted to write a message to a queue. The reason code from the MQPUT is displayed as the 3rd (native error) state.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2668
- A single error occurred in output node <insert_1> during destination list processing.
- Severity
- 20 : Error
- Explanation
- One error occurred while processing a destination list (i.e. whilst putting many messages).
- Response
- Check the following messages for details of the errors and the preceding messages for details of the effect these have had on message processing.
- BIP2669
- Multiple errors occurred in output node <insert_5> during destination list processing. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- More than one error occurred while processing a destination list (i.e. whilst putting many messages).
- Response
- Check the following messages for details of the errors and the preceding messages for details of the effect these have had on message processing.
- BIP2670
- Output node <insert_5> received a distribution list containing an invalid folder. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An MQ output node with the "Destination Mode" property set to "list" received a message containing a distribution list. However the "MQ" folder contained an invalid folder. The only folders allowed in this situation are "Defaults" and "DestinationData".
- Response
- Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy the broker.
- BIP2671
- Output node <insert_7> received a distribution list in which the folder <insert_5> contained the invalid field <insert_6>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An MQ output node with the "Destination Mode" property set to "list" received a message containing a distribution list. However the "Defaults" or "DestinationData" folder contained an invalid field. Only specific field names are allowed in this situation.
- Response
- Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy the broker.
- BIP2672
- Output node <insert_7> received a distribution list in which the field <insert_5> contained the invalid value <insert_6>. State = <insert_1> <insert_2> <insert_3> <insert_4>
- Severity
- 20 : Error
- Explanation
- An MQ output node with the "Destination Mode" property set to "list" received a message containing a distribution list. However the "Defaults" or "DestinationData" folder contained an field with an invalid value. Only specific values are allowed in this situation.
- Response
- Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy the broker.
- BIP2673
- Unable to rollback a WebSphere MQ transaction; MQBACK failed; queue manager=<insert_1>, MQCC=<insert_2>, MQRC=<insert_3>; message flow node. Use the WebSphere MQ return code and reason code returned to establish the cause of the error and take appropriate action. To protect the transaction this process will now terminate as the transaction state has become and may remain in doubt.
- Severity
- 20 : Error
- Explanation
- An attempt to rollback a WebSphere MQ unit of work using the MQBACK functions has failed. The WebSphere MQ return code and reason code returned from MQBACK are displayed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2674
- A broken connection to WebSphere MQ queue manager has been reported with WebSphere MQ reason code <insert_1>.
- Severity
- 20 : Error
- Explanation
- A call to a WebSphere MQ API has returned with a reason code of <insert_1>, which indicates that the current connection is no longer useable. Further messages indicate what effect this failure has on WebSphere Message Broker components.
- Response
- Check the WebSphere MQ reason code in the Application Programming Reference section of the WebSphere MQ information center to establish the cause of the error, and take the appropriate action.
- BIP2675
- The queue manager is reporting the next message in our current message group is not available.
- Severity
- 10 : Warning
- Explanation
- Queue manager <insert_1> returned a 2033 whilst reading queue <insert_2>. The message group identifier is <insert_3> and the last sequence number processed was <insert_4>. This message group is incomplete. The MQInput nodes All Messages Available option was set to <insert_5>.
- Response
- If the All Messages Available option was selected then all the messages must have been available for the message group to have started. Check to see if any messages have expired or if any other applications are retrieving messages off this queue. If the All Messages Available option was not selected then the message group could have started before all the messages were available. Check why all the group messages are not available on the input queue.
- BIP2676
- Output node <insert_1> received an empty distribution list.
- Severity
- 10 : Warning
- Explanation
- An MQ output node with the "Destination Mode" property set to "list" received a message containing an empty distribution list. If no "DestinationData" folders are created then no destinations will be written to.
- Response
- Check the message flow to determine whether the distribution list is being built correctly. If not then correct the problem and redeploy the message flow.
- BIP2701
- The user ID <insert_1> has been truncated to 12 characters.
- Severity
- 10 : Warning
- Explanation
- The user ID <insert_1> is too long to fit into the MQMD.UserIdentifier field, and was truncated to 12 characters.
- Response
- Specify a new user ID that is 12 characters or less.
- BIP2702
- The identity token type <insert_1>, issued by <insert_3>, failed authentication with security provider <insert_4>. (For a 'username' token type, the token is: <insert_2>.)
- Severity
- 10 : Warning
- Explanation
- The security provider specified failed to authenticate the provided identity token.
- Response
- Ensure that the provided identity token is valid and that the specified security provider is configured to authenticate the specified identity token. If the security provider is shown as 'Cached', the authentication result is now being returned from the broker security cache. You can use the 'mqsireloadsecurity' command to clear the broker security cache. Check your security provider logs for information about why the identity token could not be authenticated.
- BIP2703
- The identity token type <insert_1>, issued by <insert_3>, was not authorized by security provider <insert_4> to access message flow <insert_5>. (For a 'username' token type, the token is: <insert_2>.)
- Severity
- 10 : Warning
- Response
- If access is expected, ensure that the specified security provider has been configured to allow access to the specified message flow. If the security provider is shown as 'Cached', the authorization result is now being returned from the broker security cache. You can use the 'mqsireloadsecurity' command to clear the broker security cache. Check your security provider logs for information about why the identity token could not be authorized.
- BIP2704
- The identity provider <insert_1> cannot process mapping requests.
- Severity
- 10 : Warning
- Explanation
- A security profile with identity provider <insert_1> has been selected on a flow. This provider does not support mapping requests.
- Response
- Either choose a security provider that supports mapping, or disable mapping.
- BIP2705
- The identity provider <insert_1> does not exist.
- Severity
- 10 : Warning
- Explanation
- A flow's security profile specifies an identity provider that is not supported.
- Response
- Choose a different security provider.
- BIP2706
- The identity provider <insert_1> cannot process authentication requests.
- Severity
- 10 : Warning
- Explanation
- A flow's security profile specifies an identity provider that does not support authentication requests.
- Response
- Either choose a security provider that supports authentication, or disable authentication.
- BIP2707
- The identity provider <insert_1> cannot process authorization requests.
- Severity
- 10 : Warning
- Explanation
- A flow's security profile specifies an identity provider that does not support authorization requests.
- Response
- Either choose a security provider that supports authorization, or disable authorization.
- BIP2708
- An input message to flow <insert_1> does not have an identity.
- Severity
- 10 : Warning
- Explanation
- Input messages to the flow must have an identity for access.
- Response
- Modify the client calling the flow to provide an identity for the message.
- BIP2709
- The security profile <insert_1> specifies an invalid Security Token Server (STS) URL <insert_2>.
- Severity
- 20 : Error
- Explanation
- The security profile <insert_1> has specified a Security Token Server (STS) for authentication, mapping, or authorization, but the URL to the STS is not valid.
- Response
- Change the security profile using the mqsichangeproperties command or the Message Broker Explorer. Enter the URL of the STS (for example: http://sts.ibm.com:9080/wstrustservice) as the configuration parameter for each operation provided by the STS.
- BIP2710
- An HTTP or HTTPS WS-Trust request could not be made to the Security Token Server (STS), for security profile <insert_1>.
- Severity
- 20 : Error
- Explanation
- The security profile <insert_1> has specified a Security Token Server (STS) for authentication, mapping, or authorization, but the HTTP or HTTPS WS-Trust request could not be made.
- Response
- Review previous error messages to find additional information.
Check that the URL to the Security Token Server (STS) is specified correctly in the security profile, and that the STS is configured and running correctly.
- BIP2711
- An HTTP or HTTPS WS-Trust request for security profile <insert_1> was unsuccessful. The HTTP status class is <insert_2>. The body of the reply is: <insert_3>.
- Severity
- 20 : Error
- Explanation
- The security profile <insert_1> has specified a Security Token Server (STS) for authentication, mapping, or authorization, but the WS-Trust request to the STS was not successful.
- Response
- The reply might give details of the error.
Ensure that the Security Token Server is correctly deployed, configured, and available to process WS-Trust requests.
- BIP2712
- An invalid WS-Trust response status was received when a security operation was performed for security profile <insert_1>. The received response status was <insert_2>. If additional information was provided, it is shown here: <insert_3>
- Severity
- 20 : Error
- Explanation
- The security profile <insert_1> has specified a Security Token Server (STS) for authentication, mapping, or authorization. The response received from the STS did not indicate valid status.
- Response
- Ensure that the Security Token Server (STS) is correctly deployed and configured to process WS-Trust requests.
Check that the STS configuration in the security profile contains the correct server URL.
- BIP2713
- The creation of <insert_1> security provider failed.
- Severity
- 10 : Warning
- Explanation
- A security profile with a <insert_1> security provider has been selected on a flow. This provider exists, but an instance of it could not be created.
- Response
- Check that the configuration for the security provider specified in the security profile is correct.
- BIP2714
- The identity token type <insert_1>, issued by <insert_3>, cannot be used with security provider <insert_4>. (For a 'username' token type, the token is: <insert_2>.)
- Severity
- 10 : Warning
- Explanation
- The chosen security provider cannot process all security token types, and does not support tokens of type <insert_1>.
- Response
- Choose a security provider that supports the specified type of security token.
- BIP2715
- Security profile <insert_1> does not exist on the broker.
- Severity
- 10 : Warning
- Response
- Either choose a security profile that exists on the broker or create this profile on the broker, then redeploy.
- BIP2716
- A WS-Trust request was successfully made to the Security Token Server (STS) to map a token (type <insert_1>, token <insert_2>, issued by <insert_3>). However, the STS response did not contain a supported security token representing the mapped identity.
- Severity
- 10 : Warning
- Explanation
- The security provider made a WS-Trust request to the Security Token Server, supplying a token to be mapped.
The STS replied, but the reply did not contain a supported security token representing the mapped token.
The STS must map the token and issue a security token of a type supported by the broker.
- Response
- Ensure that the STS is correctly configured to process the mapping request.
- BIP2717
- A valid identity token could not be located in the body of the message on node <insert_1> using path <insert_2>.
- Severity
- 20 : Error
- Explanation
- The path expression either does not evaluate to an element in the message, or the element is of the wrong type.
- Response
- Check that the path expression returns a valid element on all incoming messages, and that a parser has been selected on the input node. (It is not possible to evaluate a path expression against a BLOB.)
- BIP2718
- A valid password could not be located in the body of the message on node <insert_1> using path <insert_2>.
- Severity
- 20 : Error
- Explanation
- The path expression either does not evaluate to an element in the message, or the element is of the wrong type.
- Response
- Check that the path expression returns a valid element on all incoming messages, and that a parser has been selected on the input node. (It is not possible to evaluate a path expression against a BLOB.)
- BIP2719
- A valid identity issuer could not be located in the body of the message on node <insert_1> using path <insert_2>.
- Severity
- 20 : Error
- Explanation
- The path expression either does not evaluate to an element in the message, or the element is of the wrong type.
- Response
- Check that the path expression returns a valid element on all incoming messages, and that a parser has been selected on the input node. (It is not possible to evaluate a path expression against a BLOB.)
- BIP2720
- A compatible identity was not found for propagation. One of the following identity types is required: (<insert_1>). Only the following identity types were found: (<insert_2>).
- Severity
- 20 : Error
- Explanation
- An output node with identity propagation enabled failed to locate a compatible identity type in the Properties folder.
- Response
- Ensure that all input nodes either have a security profile enabled, or point to an Identity in the incoming message and optionally map the identity to a type that is compatible with the output node. Alternatively, add a SecurityPEP node in the message flow to perform a mapping.
- BIP2721
- Failed to bind to the LDAP server <insert_1> with user name <insert_2>. Possible explanation: <insert_3>3
- Severity
- 20 : Error
- Response
- Ensure that the server address is correct.
Use mqsisetdbparms to check that the user name and password are valid.
If the user name is "anonymous", ensure that the LDAP server accepts anonymous binds.
- BIP2722
- The security cache has been cleared of all entries.
- Severity
- 10 : Warning
- Response
- No action is required.
- BIP2723
- The following user name tokens were removed from the security cache: <insert_1>1
- Severity
- 10 : Warning
- Response
- No action is required. Note that the tokens might not necessarily have been present in the cache prior to this operation.
- BIP2724
- A configuration exception was caught during security processing of flow <insert_1> using security profile <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The error might have been caused by either a misconfigured security profile or an error within a security provider.
- Response
- Review other error messages to find additional information.
- BIP2725
- A configuration exception was caught during security processing of flow <insert_1> using security profile <insert_2>. The error has been logged.
- Severity
- 10 : Warning
- Response
- Try again and if security processing of messages on this flow continues to fail, contact your system administrator.
- BIP2726
- The search of LDAP group <insert_1> with user name <insert_2> failed. The following explanation was returned: <insert_3>3
- Severity
- 20 : Error
- Explanation
- An attempt was made to get the members of group <insert_1>, using a bind with user name <insert_2>.
- Response
- Ensure that the user name supplied has permission to search for this group. If necessary use mqsisetdbparms to specify a different user name and password to bind to the server.
- BIP2727
- No results were retrieved when searching LDAP group <insert_1> with user name <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to get the members of group <insert_1>, using a bind with user name <insert_2>.
- Response
- Ensure that the user name supplied has permission to search for this group. If necessary use mqsisetdbparms to specify a different user name and password to bind to the server.
- BIP2728
- Failed to search LDAP for user <insert_1> with user name <insert_2> for binding. The following explanation was returned: <insert_3>3
- Severity
- 20 : Error
- Explanation
- An attempt was made to get the full Distinguished Name of <insert_1>, using a bind with user name <insert_2>.
- Response
- Ensure that the user name supplied has permission to look up the given user. If necessary use mqsisetdbparms to specify a different user name and password to bind to the server.
- BIP2729
- Conflicting information was specified in security profile <insert_1>. For <insert_6> security providers, parameter <insert_2> (set to <insert_3>) is incompatible with parameter <insert_4> (set to <insert_5>).
- Severity
- 20 : Error
- Response
- Use mqsichangeproperties to check and update the security profile.
- BIP2730
- The <insert_1> security provider for security profile <insert_2> in message flow <insert_3> could not be created.
- Severity
- 10 : Warning
- Explanation
- A security profile with a <insert_1> security provider was selected on a flow. Although this provider exists, an instance of it could not be created.
- Response
- Check that the configuration for the security provider specified in the profile is correct.
Review other error messages in the event log or syslog, and in User Trace to find additional information.
- BIP2731
- Security profile <insert_1> contains an invalid configuration. Property <insert_2> is set to <insert_3>. This property can have the following values: <insert_4>4
- Severity
- 20 : Error
- Response
- Use mqsichangeproperties to correct the value of the property.
- BIP2732
- The identity type was set to Current Token, but no identity is available in the Properties folder.
- Severity
- 20 : Error
- Explanation
- If the identity type is set to Current Token, an identity is expected in the Properties folder. The IdentityMappedType and Token is used if present, otherwise the IdentitySourceType and Token is used.
- Response
- Ensure that the Properties folder contains a valid security token type and the matching token.
- BIP2733
- A security related exception was caught during message flow processing.
- Severity
- 20 : Error
- Explanation
- A security exception was caught and is being propagated as a recoverable exception. Following messages will indicate the cause of this exception.
- Response
- Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
- BIP2734
- A SOAP Fault was returned from the <insert_1> Security Token Server (STS) when a security operation was attempted for security profile <insert_2>. The fault contained a code of <insert_3>, a reason string of <insert_4>, and detailed information of <insert_5>.
- Severity
- 20 : Error
- Explanation
- The security profile <insert_2> has specified <insert_1> for authentication, mapping, or authorization, but the WS-Trust request to the Security Token Server (STS) was not successful and a SOAP Fault was returned.
- Response
- The SOAP Fault might give details of the <insert_1> Security Token Server (STS) error.
Ensure that the STS is correctly deployed and available to process WS-Trust requests.
Check that the STS configuration is correctly configured to handle the WS-Trust request.
- BIP2735
- Identity has been passed to the <insert_1> security provider as instructed by security profile <insert_2>. The following operations are requested: <insert_3>, <insert_4>, <insert_5>.
- Severity
- 0 : Information
- Explanation
- The security profile <insert_2> has specified <insert_1> for security processing. A message has entered a node that uses this profile and the provider is being invoked.
- Response
- No action is required.
- BIP2736
- Preparing to bind to LDAP server <insert_1>, using username <insert_2> and the associated password.
- Severity
- 0 : Information
- Explanation
- The LDAP security provider is authenticating the username (<insert_2>) by performing an LDAP bind; success of this bind will guarantee the authenticity of the password.
- Response
- No action is required.
- BIP2737
- Preparing to look up distinguished name (DN) <insert_1> in group <insert_2> on LDAP server <insert_3>. Member attributes searched are <insert_4>.
- Severity
- 0 : Information
- Explanation
- The LDAP security provider is performing an authorization check on the username (<insert_1>) by checking whether it is a member of group <insert_2>.
- Response
- No action is required.
- BIP2738
- An invalid identity type of <insert_1> was specified. Possible types are: <insert_2>.
- Severity
- 20 : Error
- Explanation
- An identity type was used that was not recognized.
- Response
- Use one of the types listed and retry.
- BIP2739
- Security profile <insert_1> attempted to propagate a predefined username and password to a transport that does not support usernames. Identity types supported are: <insert_2>.
- Severity
- 20 : Error
- Explanation
- Predefined identities can be used only with username and usernameAndPassword capable transports.
- Response
- Use an identity flowed with the message instead.
- BIP2740
- Security profile <insert_1> tried to propagate a predefined username and password to a transport, but it did not provide an alias to look up.
- Severity
- 20 : Error
- Explanation
- The transportPropagationConfig property of the security profile must be filled in.
- Response
- Fill in the transportPropagationConfig property.
- BIP2741
- No security profile has been specified on a node that requires a security profile.
- Severity
- 20 : Error
- Explanation
- A node that has been configured to require an identity has been configured without a security profile; as a result, it does not have an identity available to propagate.
- Response
- See the following messages to determine the message flow and node affected, and configure the message flow or node with a security profile such as "Default_Propagation".
- BIP2742
- A recoverable exception was caught during security processing in node <insert_1>. Rethrowing the exception as a security exception.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error while processing security information for a message in node <insert_1>. A security exception has been thrown to cut short the processing of the message.
- Response
- See the following messages for details of the error.
- BIP2743
- An input message to the message flow <insert_1> does not contain a password for the Identity <insert_2>.
- Severity
- 10 : Warning
- Explanation
- Input messages to the message flow require a password, but the password field that is contained in the input message is empty.
- Response
- Modify the client that calls the message flow to provide a password for the specified Identity.
- BIP2801
- Unable to load implementation file <insert_1>, rc=<insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst loading a loadable implementation file.
- Response
- Ensure that the file exists.
- BIP2802
- Unable to locate entry point <insert_2> in implementation file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst locating an entry point in a loadable implementation file.
- Response
- Ensure that you have the correct version of the loadable implementation file. If you cannot resolve the problem contact your IBM support center.
- BIP2803
- Broker <insert_1> (UUID <insert_2>) received an internal configuration response message for execution group <insert_3> that contained no data.
- Severity
- 0 : Information
- Explanation
- The execution group failed to provide an adequate internal configuration response message.
- Response
- Use the system log messages to determine why the execution group failed to provide a complete internal configuration response message. You should check that your system is not running short of resources: for example, you may need to increase the WebSphere log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Broker Toolkit, mqsideploy command or a CMP application. Contact your IBM support center if you are unable to resolve the problem.
- BIP2804
- The broker has detected that Execution Group <insert_1>, process ID <insert_2>, has not shutdown.
- Severity
- 20 : Error
- Explanation
- An attempt was made to stop an Execution Group process by issuing an internal configuration message to the Execution Group. The Execution Group process has not yet shut down.
- Response
- Use the system Log to investigate why the Execution Group process could not shutdown. It is expected that the Execution Group will eventually shutdown normally. This message is repeated at 1 minute intervals. However, it is possible that you may need to stop the Execution Group manually. If the broker was configured as a WebSphere MQ trusted application then refer to the WebSphere MQ reference manuals to determine how to stop the Execution Group executable. Ensure that any database locks held by the Execution Group are released if the process is forced. Contact your IBM support center if you are unable to determine the reason for this problem.
- BIP2805
- Broker <insert_1> could not process an internal configuration message.
- Severity
- 20 : Error
- Explanation
- The problem was caused by a failure to parse the internal configuration message. The internal configuration message is rejected.
- Response
- Use the system log messages output prior to this message to diagnose the problem with the internal configuration message. Correct and redeploy the broker configuration message. Contact your IBM support center if you are unable to resolve the problem.
- BIP2806
- The broker was unable to publish to WebSphere MQ Queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- A publish event could not be sent because the WebSphere MQ message queue was not available.
- Response
- You should investigate why the message queue was not available by reviewing the system log messages. The current published state of the broker will be incorrect.
- BIP2807
- The broker received a negative response to a 'stopped' publish event, response is <insert_1>.
- Severity
- 20 : Error
- Explanation
- A 'stopped' publish event failed, use the response to determine the cause of the failure.
- Response
- The broker continues to run but the current published state of the broker will be incorrect until the next successful publish event. Contact your IBM support center.
- BIP2808
- The broker was unable to access its startup singleton classes.
- Severity
- 20 : Error
- Explanation
- An attempt was made to access a singleton class, this singleton class was not initialized correctly.
- Response
- The broker will not start. Obtain Service trace for the failing component and contact your IBM support center.
- BIP2809
- The broker was unable to receive a 'started' publish event response.
- Severity
- 20 : Error
- Explanation
- A response from a 'started' publish event could not be received.
- Response
- The broker continues to start-up but the current published state of the broker will be incorrect. Contact your IBM support center.
- BIP2810
- The broker received a negative response to a 'started' publish event, response is <insert_1>.
- Severity
- 20 : Error
- Explanation
- A 'started' publish event failed, use the response to determine the cause of the failure.
- Response
- The broker continues to run but the current published state of the broker will be incorrect until the next successful publish event. Contact your IBM support center.
- BIP2811
- The broker was unable to receive a 'stopped' publish event response.
- Severity
- 20 : Error
- Explanation
- A response from a 'stopped' publish event could not be received.
- Response
- The broker continues to shutdown but the current published state of the broker will be incorrect. Contact your IBM support center.
- BIP2812
- Broker <insert_1> (UUID <insert_2>) could not process an internal configuration response message for Execution Group <insert_3>.
- Severity
- 20 : Error
- Explanation
- The problem was caused by a failure to parse the internal configuration response message. The internal configuration response message is treated as an 'unknown' failure.
- Response
- Use the system log messages to diagnose the reason for the parse failure. Correct and redeploy the broker configuration message. Contact your IBM support center if you are unable to resolve the problem.
- BIP2813
- Broker <insert_1> (UUID <insert_2>) could not process an internal configuration response message for Execution Group <insert_3> to completion: missing tag <insert_4>.
- Severity
- 20 : Error
- Explanation
- The internal configuration response message returned by the Execution Group was incomplete.
- Response
- Use the system log messages to determine why the Execution Group failed to respond correctly. Redeploy the broker's configuration if you are able to resolve the problem. Contact your IBM support center if you are unable to resolve the problem.
- BIP2817
- Broker could not initialize.
- Severity
- 20 : Error
- Explanation
- A failure was detected while initializing data used by the bipbroker executable during broker startup. This may have been caused as a result of a previous broker failing to shutdown normally. Use IPCS together with the information contained in the files in the products locks directory to verify that the brokers shared semaphores are available for use.
- Response
- Collect all diagnostics produced and Contact your IBM support center.
- BIP2818
- Broker failed to create semaphore
- Severity
- 30 : Severe error
- Explanation
- An internal semaphore could not be created.
- Response
- Use the system log messages to determine why the semaphore failed to be created. Contact your IBM support center if you are unable to resolve the problem.
- BIP2819
- Broker detected invalid semaphore
- Severity
- 30 : Severe error
- Explanation
- An internal semaphore has an invalid handle value.
- Response
- Use the system log messages to determine why the semaphore has become invalid. Contact your IBM support center if you are unable to resolve the problem.
- BIP2820
- The broker has detected an uninitialized semaphore.
- Severity
- 30 : Severe error
- Explanation
- An internal semaphore has not been initialized.
- Response
- Use the system log messages to determine why the semaphore has not been initialized. Contact your IBM support center if you are unable to resolve the problem.
- BIP2821
- Broker detected initialized semaphore
- Severity
- 30 : Severe error
- Explanation
- An internal semaphore is initialized, which is an invalid state for the initialization phase.
- Response
- Use the system log messages to determine why the semaphore has apparently been initialized twice. Contact your IBM support center if you are unable to resolve the problem.
- BIP2822
- Broker problem with time-related system call
- Severity
- 30 : Severe error
- Explanation
- A system call to determine or calculate a time failed.
- Response
- Use the system log messages to determine why the system call failed. Contact your IBM support center if you are unable to resolve the problem.
- BIP2823
- A component integrity check failed.
- Severity
- 0 : Information
- Explanation
- The component startup process ran an integrity check on the component's configuration, and found errors. Previous messages should indicate the errors found.
- Response
- Examine previous messages to determine the cause of the failure. Correct the errors, and restart the component.
- BIP2824
- Broker <insert_1> has failed to connect to WebSphere MQ. The reason code is <insert_2>. No broker components will be started until the queue manager becomes available.
- Severity
- 0 : Information
- Explanation
- During Broker <insert_1> startup, an attempt to connect to the queue manager failed with a reason code of <insert_2>. This will prevent any further broker components from starting.
- Response
- Ensure that the queue manager has started successfully. Investigate and resolve the WebSphere MQ queue manager problem.
- BIP2826
- Execution Group termination wait timer reached.
- Severity
- 20 : Error
- Explanation
- An attempt was made to stop an Execution Group process by issuing an internal configuration message to the Execution Group. The Execution Group process has not yet shut down.
- Response
- Please refer to previous messages for more details of Execution Group. Use the system Log to investigate why the Execution Group process could not shutdown. This message is issued to enable customers to be aware of possible shutdown problems. However, it is possible that you may need to stop the Execution Group manually. Contact your IBM support center if you are unable to determine the reason for this problem.
- BIP2827
- Broker <insert_1> (UUID <insert_2>) received an internal configuration message that specified a 64-bit execution group; this broker is only capable of supporting 32-bit execution groups.
- Severity
- 10 : Warning
- Explanation
- The platform on which the broker is running does not support 64-bit execution group process; only 32-bit execution groups can be created on such platforms.
- Response
- A 32-bit execution group has been created. To avoid seeing this warning deploy only 32-bit execution groups to this broker, or create a broker on a 64-bit-capable platform and deploy the configuration to that broker.
- BIP2828
- Broker <insert_1> (UUID <insert_2>) received an internal configuration message that specified a 32-bit execution group; this broker is only capable of supporting 64-bit execution groups.
- Severity
- 10 : Warning
- Explanation
- The platform on which the broker is running does not support 32-bit execution group process; only 64-bit execution groups can be created on such platforms.
- Response
- A 64-bit execution group has been created. To avoid seeing this warning deploy only 64-bit execution groups to this broker, or create a broker on a 32-bit-capable platform and deploy the configuration to that broker.
- BIP2829
- Unable to initialize the Service Federation SCMP listener environment. Exception text <insert_1>1
- Severity
- 30 : Severe error
- Explanation
- The Service Federation SCMP listener detected an error whilst initializing its working environment. Examine previous error messages for details of the cause of this problem.
- Response
- Contact your IBM support center.
- BIP2830
- The Service Federation SCMP listener could not create a necessary working directory: <insert_1> (error code <insert_2>)
- Severity
- 20 : Error
- Explanation
- The Service Federation SCMP listener needs to create a working directory for the servlet engine to function correctly. This directory could not be created and the listener will exit.
- Response
- Ensure that the broker has the necessary permissions to create the required directory.
- BIP2831
- A required parameter <insert_1> for the mqsiwebuseradmin command is missing or invalid.
- Severity
- 20 : Error
- Explanation
- The requested operation involving a web user (either a create, delete, or modify) is missing the required parameter <insert_1>. Check the client program logic and try again.
- Response
- Supply or correct the named parameter and try again.
- BIP2832
- The web user account <insert_1> cannot be created because the account already exists.
- Severity
- 20 : Error
- Explanation
- An attempt was made to create a web user for which an account already exists. Web user account names are unique.
- Response
- Either delete the old account or retry the request with a different username.
- BIP2833
- The referenced web user account <insert_1> does not exist.
- Severity
- 20 : Error
- Explanation
- An operation was attempted for a web user account <insert_1>. This account is not defined within the broker registry and the operation failed.
- Response
- Correct the username if necessary and try again.
- BIP2834
- The password for the web user account <insert_1> cannot be changed because the old password did not match the one stored in the broker registry.
- Severity
- 20 : Error
- Explanation
- In order to change the password for the web user account, the request must include the previous password for that web user. The supplied password was incorrect.
- Response
- Correct the previous password and try again. If the old password has been forgotten, a broker administrator can reset the password using the 'mqsiwebuseradmin' command.
- BIP2835
- Incorrect web user version <insert_2>. The web user account <insert_1> cannot be updated.
- Severity
- 20 : Error
- Explanation
- Web user accounts are created in the broker registry in a particular format. The current broker level uses a different format to the one that created the web user. The web user <insert_1> has version <insert_2>.
- Response
- Either modify the web user using the broker version with which it was created, or delete and recreate the web user account.
- BIP2836
- No web user accounts have been defined.
- Severity
- 0 : Information
- Explanation
- Web user accounts are defined in the broker through either the mqsiwebuseradmin command or the WebSphere Message Broker administration programming interface (API). No accounts were defined on the specified broker.
- Response
- No web user accounts were defined on the specified broker.
- BIP2837
- Web user <insert_1> is defined as having a role of <insert_2>.
- Severity
- 0 : Information
- Explanation
- The web user account has been defined in the broker registry. The web user account has a role of <insert_2>, which is the system account under which actions will be authorized if administration security is enabled.
- BIP2838
- Web user role <insert_1> has a maximum length of 12 characters.
- Severity
- 20 : Error
- Explanation
- The maximum length for the role parameter is 12 characters.
- BIP2839
- The Default Web user account cannot be created, modified or deleted.
- Severity
- 20 : Error
- Explanation
- The Default Web user account named "Default" is used when administration security is disabled. It is a reserved account and cannot be removed. When security is enabled, this account is not available for use.
- BIP2850
- The requested action is not supported. (<insert_1> <insert_2>)
- Severity
- 20 : Error
- Explanation
- A CMP application asked the broker to complete an action which is not supported. The action involved an operation type <insert_1> against an object type of <insert_2>.
- Response
- Determine the method call that resulted in the failure. Consult the CMP API Reference documentation for alternative ways to complete the required task, and if necessary rewrite the CMP application to use only supported methods.
- BIP2851
- The broker object <insert_3> of type <insert_4> with uuid <insert_5> is in stopped state. The requested operation type <insert_1> against an object type of <insert_2> cannot be completed.
- Severity
- 20 : Error
- Explanation
- A CMP application sent a request to the broker to complete an action on an object. Either that object is in stopped state, or the parent object is in stopped state. While the object is in stopped state, the broker cannot complete the action.
- Response
- The broker object, and its parent object, must be running for this action to take place. If the operation is for a message flow, start the parent execution group. If the operation is for an execution group, start the execution group.
- BIP2852
- The user <insert_1> is not authorized to perform the requested operation <insert_2> against the object <insert_3> of type <insert_4>. The user <insert_1> needs to have <insert_5> permission on the object <insert_6> of type <insert_7>.
- Severity
- 20 : Error
- Explanation
- The user initiated a request to the broker to complete an action on an object. The request was rejected by the broker because the user does not have the required authorization.
- Response
- Set up authorizations for this object to grant the required authority to this user ID.
- BIP2853
- The broker was unable to check authorization for user <insert_1> (subcomponent <insert_2>). The request has been rejected owing to this error, even though the user may in fact be authorized.
- Severity
- 20 : Error
- Explanation
- During authority checks for user <insert_1>, an error occurred that cut short the checks. The user may have the correct privilieges, but this cannot be determined by the broker. Subsequent error messages may indicate the cause of the failure.
- Response
- Correct the underlying errors that prevented the broker from performing security checks, and retry the operation.
- BIP2854
- The broker was unable to create security objects for execution group <insert_1>. The create of the execution group has succeeded, but security objects will need to be created manually. Subsequent error message contain the details of the objects in need of manual creation.
- Severity
- 10 : Warning
- Explanation
- The broker attempted to create security objects as part of execution group <insert_1> creation, but was unsuccessful.
- Response
- Create the required security objects, and ensure they have the correct characteristics.
- BIP2855
- The broker was unable to delete security objects for execution group <insert_1>. The delete of the execution group has succeeded, but security objects will need to be deleted manually. Subsequent error message contain the details of the objects in need of manual deletion.
- Severity
- 10 : Warning
- Explanation
- The broker attempted to delete security objects as part of execution group <insert_1> deletion, but was unsuccessful.
- Response
- Delete the security objects.
- BIP2856
- The broker successfully created security objects for execution group <insert_1>.
- Severity
- 0 : Information
- Explanation
- The broker needs security objects for authority checks for execution group <insert_1>, and has created these objects.
- Response
- No action
- BIP2857
- The broker attempted to create a security object for execution group <insert_1>, but the object (of name <insert_2>) already exists. The pre-existing object will be used for broker authorization checks.
- Severity
- 10 : Warning
- Explanation
- The broker attempted to create a security object as part of execution group <insert_1> creation, but was unsuccessful because such an object already exists. The existing object will be used, and permissions on that object will not be changed.
- Response
- Ensure the pre-existing object has the desired permissions.
- BIP2858
- WebSphere MQ function <insert_1> failed with reason code <insert_2> . The queue name (if any) was <insert_3>.
- Severity
- 20 : Error
- Explanation
- This implementation of broker security relies on WebSphere MQ to function correctly, and a critical WebSphere MQ call has failed.
- Response
- Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
- BIP2859
- The broker successfully deleted security objects for execution group <insert_1>.
- Severity
- 0 : Information
- Explanation
- The broker no longer needs security objects for authority checks for execution group <insert_1>, and has deleted these objects.
- Response
- No action
- BIP2860
- The broker created security objects for execution group <insert_1>, but was unable to set default access permissions for group 'mqbrkrs' for object <insert_2>. The create of the execution group and associated security objects have succeeded, but object permissions may need to be set manually.
- Severity
- 10 : Warning
- Explanation
- The broker attempted to set permissions for security objects as part of execution group <insert_1> creation, but was unsuccessful.
- Response
- Ensure the created object has the desired permissions.
- BIP2861
- The broker attempted to create security objects for execution group <insert_1>, but was unable create object <insert_2>. The create of the execution group succeeded, but the security object must be created manually
- Severity
- 10 : Warning
- Explanation
- The broker attempted to create a security object as part of execution group <insert_1> creation, but was unsuccessful.
- Response
- Create the specified object, and ensure the created object has the desired permissions.
- BIP2862
- The broker attempted to delete security objects for execution group <insert_1>, but was unable delete object <insert_2>. The delete of the execution group succeeded, but the security object must be deleted manually
- Severity
- 10 : Warning
- Explanation
- The broker attempted to delete a security object as part of execution group <insert_1> deletion, but was unsuccessful.
- Response
- Delete the specified object.
- BIP2863
- The broker has detected that security objects for execution group <insert_1> are shared with at least one other execution group, and will use the existing object <insert_2> for authority checking.
- Severity
- 10 : Warning
- Explanation
- The newly-created execution group <insert_1> has a name that, when used to create security objects, is the same as at least one other execution group. The execution groups share an authentication queue for checking purposes. To prevent this behavior, ensure that all execution group names are sufficiently different that collisions in queue names do not occur.
- Response
- Ensure the existing object has the desired permissions for the new execution group.
- BIP2864
- The broker has detected that security objects for execution group <insert_1> are shared with at least one other execution group, and will not delete the existing object <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The broker attempted to delete a security object as part of execution group <insert_1> deletion, but has not done so because the object is in use by at least one other exectuion group.
- Response
- None.
- BIP2865
- Authorization check failed for user <insert_1> subcomponent <insert_2> because a required WebSphere MQ queue <insert_3> was not found.
- Severity
- 20 : Error
- Explanation
- The broker needs WebSphere MQ queues for authority checks for execution group <insert_2>, and one of these queues is not present.
- Response
- Create the required WebSphere MQ queue, and ensure it has the correct characteristics.
- BIP2866
- WebSphere Message Broker administration security is <insert_1>.
- Severity
- 0 : Information
- Explanation
- Describes whether administration security has been activated or not for the current broker. Administration security can be activated or inactivated by the mqsichangebroker command.
- Response
- No action.
- BIP2867
- WebSphere MQ was unable to set the correct security permissions on the queue <insert_1> for the group <insert_2>.
- Severity
- 20 : Error
- Explanation
- These permissions need to be set for broker security to function correctly. Please set these permissions manually.
- Response
- Use the WebSphere MQ explorer or the setmqaut command to set the Inquire (inq), Put (put), and Set (set) permissions on the <insert_1> queue for the group <insert_2>.
- BIP2870
- The request made by user <insert_1> to change the property <insert_2> to the value of <insert_3> on object <insert_4> of type <insert_5> with parent <insert_6> of type <insert_7> has the status of <insert_8>.
- Severity
- 0 : Information
- BIP2871
- The request made by user <insert_1> to <insert_2> the resource <insert_3> of type <insert_4> on parent <insert_5> of type <insert_6> has the status of <insert_7>.
- Severity
- 0 : Information
- BIP2872
- The user <insert_1> has made a request to deploy to the Broker using a deprecated method.
- Severity
- 10 : Warning
- Explanation
- A CMP application has used the BrokerProxy.deploy() method and this has been deprecated in the current broker product. In previous versions of WebSphere Message Broker this method deployed configuration changes to a broker. This had the effect of pausing the application until the request was completed by the broker, and thus provided the ability to make configuration changes synchronously. As of WebSphere Message Broker V7, property changes are applied immediately and so a separate deployment step is not required.
- Response
- Using this method is unnecessary and will cause your application to work more slowly. If the CMP application is designed to wait for updates to take affect then it should be modified to use the BrokerProxy.setSynchronous() method instead. If the CMP application does not need to wait for the updates to take affect then the Broker.deploy() method call can be removed.
- BIP2873
- The user <insert_1> has requested a deploy of the BAR file <insert_2> to execution group <insert_3> on broker <insert_4>.
- Severity
- 0 : Information
- BIP2880
- The property <insert_1> has changed from <insert_2> to <insert_3> on object <insert_4> of type <insert_5> with parent <insert_6> of type <insert_7>.
- Severity
- 0 : Information
- BIP2881
- The resource <insert_1> of type <insert_2> was created on object <insert_3> of type <insert_4> with parent <insert_5> of type <insert_6>.
- Severity
- 0 : Information
- BIP2882
- The resource <insert_1> of type <insert_2> was deleted from object <insert_3> of type <insert_4> with parent <insert_5> of type <insert_6>.
- Severity
- 0 : Information
- BIP2883
- The resource <insert_1> of type <insert_2> was modified on object <insert_3> of type <insert_4> with parent <insert_5> of type <insert_6>.
- Severity
- 0 : Information
- BIP2884
- The resource <insert_1> of type <insert_2> was redeployed to the execution group <insert_3> on broker <insert_4>.
- Severity
- 0 : Information
- BIP2885
- The broker has detected a condition on thread number <insert_1> with name <insert_2>, which requires it to shutdown and restart.
- Severity
- 20 : Error
- Explanation
- The broker has detected a condition which requires it to shut down and restart. Further messages will indicate the cause of this condition. An exception was issued on thread number <insert_1> with name <insert_2>.
- BIP2890
- The previous configuration change could not be completed. (Table(s) <insert_1>)
- Severity
- 20 : Error
- Explanation
- The previous configuration change could not be completed due to an error. The broker's configuration has returned to the state it was in before the change was requested.
- Response
- Retry the operation. If the problem persists, back up the broker's configuration by using the mqsibackupbroker command and contact your IBM support center.
- BIP2891
- A broker configuration change has failed updating <insert_1>.
- Severity
- 20 : Error
- Explanation
- The broker has not been able to complete a configuration change due to a problem updating the file. The problem may be transient, so the broker will retry 5 times at 1 min intervals before rejecting the change.
- Response
- Review previous errors for information as to why the update has failed, and correct any problems. If after correcting any problems, the broker cannot complete the configuration change then contact your IBM support center.
- BIP2892
- The broker has failed to read the configuration file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The broker has not been able to read a configuration file. The problem may be transient, so the broker will retry 5 times at 1 min intervals before rejecting the request.
- Response
- Review previous errors for information as to why the open has failed, and correct any problems. If after correcting any problems, the broker cannot open the configuration file then contact your IBM support center.
- BIP2893
- The broker has failed to rename the configuration file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The broker has not been able to rename a configuration file. The problem may be transient, so the broker will retry 5 times at 1 min intervals before rejecting the change.
- Response
- Review previous errors for information as to why the rename has failed, and correct any problems. If after correcting any problems, the broker cannot rename the configuration file then contact your IBM support center.
- BIP2894
- The broker has failed to delete the configuration file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The broker has not been able to delete a configuration file. The problem may be transient, so the broker will retry 5 times at 1 min intervals before rejecting the change.
- Response
- Review previous errors for information as to why the delete has failed, and correct any problems. If after correcting any problems, the broker cannot delete the configuration file then contact your IBM support center.
- BIP2898
- The Java Method <insert_1> could not be found as its containing class could not be found by the specified configurable service classloader <insert_2>.
- Severity
- 20 : Error
- Explanation
- The specified Java Method <insert_1> belongs to a class that could not be found by the specified configurable service classloader <insert_2>. Ensure that the fully qualified name of the method is correct and that its containing class or jar file can be found be the specified configurable service classloader.
- Response
- Examine and correct the SQL program.
- BIP2899
- The Java Method <insert_1> could not be loaded as the requested classloader configurable service <insert_2> could not be found.
- Severity
- 20 : Error
- Explanation
- The specified Java Method <insert_1> could not be loaded by the requested classloader configurable service <insert_2> as the configurable service does not exist.
- Response
- Create the specified configurable service and redeploy the flow.
- BIP2901
- The character data <insert_1> returned by the database could not be converted to Unicode.
- Severity
- 10 : Warning
- Explanation
- This situation arises because databases sometimes return garbage for their SQL states or error text. This return data typically has no significance.
- Response
- No user action required.
- BIP2902
- The text message returned from the database could not be converted to the local codepage, SQLState (<insert_1>), native error (<insert_2>).
- Severity
- 10 : Warning
- Explanation
- The text message returned from the database could not be converted to the local codepage.
- Response
- No user action required.
- BIP2903
- (<insert_1>, <insert_2>) : Invalid Exception Type (<insert_3>) used when calling the THROW statement. Valid exception types are <insert_4>.
- Severity
- 20 : Error
- Explanation
- An Invalid Exception Type (<insert_3>) was used as the first argument of the THROW statement. The valid Exception Types are <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Correct the Exception Type and redeploy the messageflow.
- BIP2904
- (<insert_1>, <insert_2>) : Mismatch found between EXTERNAL NAME and LANGUAGE clauses on the a routine definition.
- Severity
- 20 : Error
- Explanation
- A routine with a LANGUAGE clause of ESQL is not allowed to have an EXTERNAL NAME clause, but routines with a LANGUAGE JAVA or a LANGUAGE DATABASE clause require one
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2905
- (<insert_1>, <insert_2>) : The expression passed to the <insert_3> statement as parameter <insert_5> must evaluate to a <insert_4> value.
- Severity
- 20 : Error
- Explanation
- Parameter <insert_5> for the <insert_3> statement must evaluate to a <insert_4> value.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2906
- (<insert_1>, <insert_2>) : The data type <insert_3> is not a valid data type for parameter <insert_4> of the <insert_5> statement. This parameter should be of data type <insert_6>. The value passed was <insert_7>.
- Severity
- 20 : Error
- Explanation
- The <insert_4> parameter is not of the correct data type for this statement ( <insert_5> ).
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the argument(s) passed to this statement are of the correct data type.
- BIP2907
- (<insert_1>, <insert_2>) : The bit stream <insert_3> passed to the PARSE clause of the CREATE statement is not a valid bit stream.
- Severity
- 20 : Error
- Explanation
- The bit stream <insert_3> is invalid.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow. Ensure that the bit stream you use in this statement is valid.
- BIP2908
- (<insert_1>, <insert_2>) : The DOMAIN name <insert_3> passed to the DOMAIN clause of the CREATE statement is not a valid Root Element Name.
- Severity
- 20 : Error
- Explanation
- The DOMAIN name <insert_3> is an invalid Root Element Name.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the DOMAIN name used in this statement is valid. You should check for other messages issued with this one for the full context of this error.
- BIP2909
- (<insert_1>, <insert_2>) : Exception throw whilst processing the CREATE statement
- Severity
- 20 : Error
- Explanation
- The CREATE statement has been unable to be completed due to an exception being thrown whilst evaluating the PARSE clause. . Additional information available is: <insert_3>
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: You should check for other messages issued with this one for the full context of this error.
- BIP2910
- (<insert_1>, <insert_2>) : SELECT list item must be a scalar
- Severity
- 20 : Error
- Explanation
- The SELECT clause of a SELECT statement contains an item which could be a list. This cannot be used with the column functions: SUM, MAX or MIN.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2911
- (<insert_1>, <insert_2>) : Search condition for an IF statement must be a boolean expression
- Severity
- 20 : Error
- Explanation
- The condition for an IF statement must be an expression which evaluates to a boolean result: TRUE, UNKNOWN or FALSE The expression used was the wrong type.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2912
- (<insert_1>, <insert_2>) : Type mismatch on RETURN
- Severity
- 20 : Error
- Explanation
- A RETURN expression is of an unexpected type. This can occur when a statement is implicitly parsed as a RETURN statement, such as when a function is used without assigning the return value.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2913
- An attempt was made to access a database without specifying a datasource. Please specify a datasource and redeploy the message flow.
- Severity
- 20 : Error
- Explanation
- A database cannot be accessed without specifying a datasource.
- Response
- Specify the missing datasource and redeploy the message flow.
- BIP2914
- (<insert_1>, <insert_2>) : Duplicate label
- Severity
- 20 : Error
- Explanation
- A labeled statement cannot contain another labeled statement with the same label, either directly or indirectly.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>. Choose a different label for one of the statements and redeploy the message flow.
- BIP2915
- (<insert_1>, <insert_2>) : Mismatched start and end labels
- Severity
- 20 : Error
- Explanation
- This error can simply be that the start and end labels are mismatched or it can be indicative of an error in the nesting of statements.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Correct one of the labels or the nesting of statements and redeploy the message flow.
- BIP2916
- (<insert_1>, <insert_2>) : Correlation names cannot be qualified.
- Severity
- 20 : Error
- Explanation
- Correlation names (the first name in a field reference) must be a simple name identifier. They cannot be qualified by a type, an index, a list specifier ([ ]) nor may the name be calculated by an expression.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that all correlation names are unqualified.
- BIP2917
- A call to the Java method <insert_1> with parameters <insert_3> failed because a Java Exception occurred. The Java Exception information is <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to invoke the Java method <insert_1>, but the method threw an exception. Typically the exception occurs because of a coding error in the Java method or an error in the JVM (such as Out of Memory). The Java exception information was <insert_2>. The parameters passed into the method were <insert_3>.
- Response
- Examine and correct the Java method.
- BIP2918
- Node <insert_7>: Executing Java Method <insert_3> derived from (<insert_1>, <insert_2>). Parameters passed <insert_4>. Resulting parameter values <insert_5>. Return value <insert_6>.
- Severity
- 0 : Information
- BIP2919
- (<insert_1>, <insert_2>) : An error occuirred when invoking the Java method <insert_3>. The parameters passed to the method were <insert_4>.
- Severity
- 20 : Error
- Explanation
- Other messages give an indication of context of this error.
- BIP2920
- When attempting to obtain a procedure definition, the database reported that the procedure <insert_1> does not exist, or cannot be accessed.
- Severity
- 20 : Error
- Explanation
- If the procedure <insert_1> does not exist, you must create it before it can be called. Otherwise, ensure that the EXTERNAL NAME matches the name by which the procedure is known to the database, including any necessary schema or package qualifiers.
- Response
- Make sure that this procedure exists, and that you have authority to access it and have qualified the EXTERNAL NAME if necessary, then redeploy the message flow.
- BIP2921
- The procedure <insert_1> with <insert_2> parameters could not be matched with a corresponding Database stored procedure.
- Severity
- 20 : Error
- Explanation
- Stored Procedures must match the ESQL CREATE PROCEDURE definition in the following ways: 1: The ESQL parameters must all be of SCALAR type. 2: The directions of each ESQL and Database parameter (IN / OUT / INOUT) must match. 3: The number of parameters in both the ESQL and database definitions must match.
- Response
- Ensure these conditions are met and redeploy the message flow.
- BIP2922
- The database reports that the procedure <insert_1> in schema <insert_2> has <insert_3> overloaded versions. This is not supported, as it cannot be determined which of the <insert_3> definitions is required.
- Severity
- 20 : Error
- Explanation
- If the procedure <insert_1> is not already qualified with a schema name, qualification may remove this problem. Otherwise ensure that the procedure <insert_1> is the only procedure of this name within schema <insert_2>
- Response
- Correct this problem and redeploy the messageflow.
- BIP2923
- (<insert_1>, <insert_2>) : A CALL to the procedure <insert_3> failed as it could not find a database definition for this procedure. Please check that this procedure exists in the database and that it's definition matches the ESQL definition.
- Severity
- 20 : Error
- Explanation
- If the procedure <insert_3> does not exist it will need to be created before it can be called. Otherwise ensure that the EXTERNAL NAME <insert_4> matches the name by which it is known to the Database, including any necessary schema/package qualifiers.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Make sure that this procedure exists and you have authority to access it and have qualified the EXTERNAL NAME if necessary, then redeploy the message flow.
- BIP2924
- (<insert_1>, <insert_2>) : A CALL to the procedure <insert_3> failed as a database definition for this procedure could not be found in the schema <insert_4>.
- Severity
- 20 : Error
- Explanation
- If the procedure <insert_3> does not exist it will need to be created before it can be called. Otherwise ensure that the schema <insert_4> matches the schema name by which this procedure is known to the Database.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Please check that this procedure exists in the schema <insert_4> and that it's definition matches the ESQL definition. Otherwise you will need to qualify the EXTERNAL NAME of this procedure on the CREATE PROCEDURE statement with the correct Database schema.
- BIP2925
- (<insert_1>, <insert_2>) : A byte array literal must have an even number of digits.
- Severity
- 20 : Error
- Explanation
- This is most likely to have been caused by attempting to use a X' literal with an odd number of digits (0-9, A-F, a-f) between the quotes.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Ensure that the literal has an even number of digits.
- BIP2926
- (<insert_1>, <insert_2>) : A CALL to procedure <insert_3> failed as multiple procedure definitions match this procedure in the schema <insert_4>. Change the database procedure name to make it unique as overloaded procedures in the same schema are not supported.
- Severity
- 20 : Error
- Explanation
- The procedure definition must be unique within the schema <insert_4>.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow: Please check with the database that this procedure exists once only in the supplied schema.
- BIP2927
- The Java method <insert_1> was found but it has a 'throws' clause
- Severity
- 20 : Error
- Explanation
- The Java method <insert_1> must not have a 'throws' clause
- Response
- Examine and correct the SQL program to ensure that no referenced Java methods have 'throws' clauses.
- BIP2928
- The Java method <insert_1> was found but its return type does not match the ESQL return type
- Severity
- 20 : Error
- Explanation
- The Java method <insert_1> has a return type that does not match its ESQL return type. Correct the ESQL return type or change the Java return type
- Response
- Examine and correct the SQL program.
- BIP2929
- (<insert_1>, <insert_2>) : Mismatch found between LANGUAGE DATABASE and RETURNS clauses
- Severity
- 20 : Error
- Explanation
- A LANGUAGE DATABASE routine is not allowed to have a RETURNS clause.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2930
- A function or procedure was called but the value supplied for the <insert_1> parameter was of type <insert_2> but the function/procedure expects value of type <insert_3>
- Severity
- 20 : Error
- Explanation
- Functions and procedures require an exact matching between the data type of values supplied as parameters and the data type in its definition.
- Response
- Examine and correct the SQL program
- BIP2931
- A function or procedure was called, but the value supplied for the <insert_1> parameter was not a reference. The function or procedure expects a reference.
- Severity
- 20 : Error
- Explanation
- Functions and procedures do not allow data types other than references (for example, expressions) to be used for IN or INOUT parameters that are defined to be references.
- Response
- Examine and correct the ESQL program.
- BIP2932
- A function or procedure was called but the value supplied for the <insert_1> parameter was not a reference but the definition of the function/procedure requires a reference.
- Severity
- 20 : Error
- Explanation
- Functions and procedures require references to be supplied for OUT and INOUT scalar parameters so that the resulting value can be assigned to its target.
- Response
- Examine and correct the SQL program
- BIP2933
- A function or procedure was called but the value supplied for the <insert_1> parameter was not a reference to a reference variable but the definition of the function/procedure requires a reference to a reference variable.
- Severity
- 20 : Error
- Explanation
- Functions and procedures require references to reference variables to be supplied for OUT and INOUT reference parameters so that the resulting value can be assigned to its target.
- Response
- Examine and correct the SQL program
- BIP2934
- Error detected whilst executing the function or procedure <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker detected an error whilst executing the function or procedure <insert_1>. An exception has been thrown to cut short the processing of the message.
- Response
- See the following messages for details of the error.
- BIP2935
- (<insert_1>, <insert_2>) : An expression which evaluates to a scalar variable or a field is required here.
- Severity
- 20 : Error
- Explanation
- The expression supplying the parameter must evaluate to a value of a suitable type. The given expression cannot possibly do so.
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2936
- A RETURN statement attempted to return a value of type <insert_1> but the containing routine is defined to return a value of type <insert_2>.
- Severity
- 20 : Error
- Explanation
- An exact match between the datatype of the value returned by a return statement and the datatype specified on the routine declaration is required.
- Response
- Examine and correct the SQL program
- BIP2937
- An attempt was made to define the function or procedure <insert_1> but a function or procedure with this name already exists.
- Severity
- 20 : Error
- Explanation
- An attempt was made to define the function or procedure <insert_1> but a function or procedure with this name already exists. Function and procedure names are case insensitive, occupy the same name space and must be unique regardless of the number or type of their parameters
- Response
- Examine and correct the SQL program
- BIP2938
- An attempt was made to execute the non existent function or procedure <insert_1>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to execute the function or procedure <insert_1> but no such function or procedure has been defined. All functions and procedures must be defined in the node that uses them.
- Response
- Examine and correct the SQL program
- BIP2939
- (<insert_1>, <insert_2>) : Unsuitable function or procedure <insert_3>.<insert_4>.
- Severity
- 20 : Error
- Explanation
- The program is attempting to call a function which is defined but either returns a value when none is required or does not return a value when one is required
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2940
- (<insert_1>, <insert_2>) : Wrong number of parameters. <insert_5> supplied but <insert_6> required for function/procedure <insert_3>.<insert_4>.
- Severity
- 20 : Error
- Explanation
- The program is attempting to call a function which is defined but does not have the same number of parameters as are present in the call
- Response
- Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.
- BIP2941
- The Datatype <insert_1> is not supported when invoking the Java method <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to pass data of datatype <insert_1> to or from a Java method either as a parameter or as a return value. This type is not supported when invoking a Java method.
- Response
- Examine and correct the SQL program
- BIP2942
- The EXTERNAL NAME <insert_1> is not a valid name for a qualified Java method.
- Severity
- 20 : Error
- Explanation
- An attempt was made to invoke a Java method using an invalid qualified Java method name. The name used was <insert_1>.
- Response
- Examine and correct the SQL program
- BIP2943
- The Java Method <insert_1> could not be found as its containing class could not be found in the deployed bar file or in the 'workpath/shared-classes/' directory.
- Severity
- 20 : Error
- Explanation
- The specified Java Method <insert_1> belongs to a class that could not be found in the deployed bar file or the 'workpath/shared-classes/' directory. Ensure that the fully qualified name of the method is correct and that its containing class or jar file is in the deployed bar file or in the 'workpath/shared-classes/' directory.
- Response
- Examine and correct the SQL program.
- BIP2944
- The Java method <insert_1> does not have a valid return type.
- Severity
- 20 : Error
- Explanation
- The specified Java Method <insert_1> does not have a return type that is in the list of supported Java return types.
- Response
- Examine and correct the SQL program.
- BIP2945
- The Java method <insert_1> has an invalid parameter type that is not on the list of supported Java parameter types or is of the wrong direction.
- Severity
- 20 : Error
- Explanation
- One or more of the parameters to the specified Java Method <insert_1> is not of the list of supported Java parameter types or is of the wrong direction. Ensure that all parameters to the Java method are on the list of supported parameter datatypes and directions.
- Response
- Examine and correct the SQL program.
- BIP2946
- The Java method <insert_1> could not be found
- Severity
- 20 : Error
- Explanation
- The Java method <insert_1> with the specified signature could not be found in the specified class. Ensure the method exists in the specified class and that it exactly matches its ESQL signature.
- Response
- Examine and correct the SQL program.
- BIP2947
- The Java method <insert_1> was found but it is not declared to be public
- Severity
- 20 : Error
- Explanation
- The Java method <insert_1> must be declared to be public
- Response
- Examine and correct the SQL program.
- BIP2948
- The Java method <insert_1> was found, but is not declared to be static.
- Severity
- 20 : Error
- Explanation
- The Java method <insert_1> must be declared to be static.
- Response
- Examine and correct the SQL program.
- BIP2949
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2950
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2951
- Event generated by user code. Additional information : <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- The event was generated by an SQL LOG or THROW statement. This is the normal behavior of these statements.
- Response
- Since this is a user generated event, the user action is determined by the message flow and the type of event.
- BIP2952
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2953
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2954
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2955
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2956
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2957
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2958
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2959
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2960
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2961
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2962
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2963
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2964
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2965
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2966
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2967
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2968
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2969
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2970
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2971
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2972
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2973
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2974
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2975
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2976
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2977
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2978
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2979
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2980
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2981
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2982
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2983
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2984
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2985
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2986
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2987
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2988
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2989
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2990
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2991
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2992
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2993
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2994
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2995
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2996
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2997
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2998
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.
- BIP2999
- A user generated ESQL exception has been thrown. The additional information provided with this exception is: <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9> <insert_10>
- Severity
- 0 : Information
- Explanation
- This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the THROW statement.
- Response
- Since this is a user generated exception, the user action is determined by the message flow and the type of exception thrown.