BIP4000-4999: Runtime components - Built-in nodes

BIP4001
Syntax error in SQL statements in node <insert_0>.
Severity
20 : Error
Explanation
The configuration failed due to errors in the SQL statement text. See the following messages for details of the error
Response
The following error messages will give specific details of the location and nature of the error. Check and correct the syntax of the SQL statements and redeploy.

BIP4002
Transaction state is not consistent with the value of 'transaction' attribute in node <insert_0>.
Severity
20 : Error
Explanation
The node <insert_0> would cause a commit of the database transaction on DSN <insert_1>. However, an active transaction already exists on that database, which would be committed prematurely if this node did a commit. This situation can arise if a previous node which caused a database update on the same DSN had the transaction property of 'automatic' specified. The message flow logic is regarded as inconsistent in such a situation.
Response
Examine the logic of the message flow, correct it and redeploy.

BIP4003
Incorrect return type <insert_0> in node <insert_2>. The value returned was <insert_1>.
Severity
20 : Error
Explanation
Return statements in filter nodes (and filter expressions) must return a value of type BOOLEAN
Response
Examine the logic of the given node's SQL statements, correct them and redeploy.

BIP4004
Message propagated to 'true' terminal of filter node <insert_0>.
Severity
0 : Information

BIP4005
Message propagated to 'false' terminal of filter node <insert_0>.
Severity
0 : Information

BIP4006
Message propagated to 'unknown' terminal of filter node <insert_0>.
Severity
0 : Information

BIP4007
Message propagated to 'out' terminal of node <insert_0>.
Severity
0 : Information

BIP4008
Message propagated to <insert_0> terminal of node <insert_1>.
Severity
0 : Information

BIP4009
Invalid terminal identifier <insert_0>.
Severity
20 : Error
Explanation
THE TERMINAL clause of a PROPAGATE statement did not identify a valid terminal
Response
Examine the logic of the given node's SQL statements, correct them and redeploy.

BIP4010
Message propagated to label node <insert_0> by node <insert_1>.
Severity
20 : Error

BIP4011
Invalid terminal identifier <insert_0>.
Severity
20 : Error
Explanation
The LABEL clause of a PROPAGATE statement did not identify a valid label node
Response
Examine the logic of the given node's SQL statements, correct them and redeploy.

BIP4012
(<insert_0>, <insert_1>) : Unexpectedly encountered end of trace pattern.
Severity
20 : Error
Explanation
The trace pattern configuring a trace node contained mismatched braces (<insert_', '>) at the line and column indicated. The preceding message will indicate the identity of the node and the message flow in which it was defined.
Response
Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then redeploy the message flow: Correct the trace pattern and redeploy the message flow.

BIP4013
(<insert_0>, <insert_1>) : An expression must be given between braces in a trace pattern.
Severity
20 : Error
Explanation
The text between braces (<insert_', '>) in a trace pattern configuring a trace node must consist of a valid SQL expression defining the value to be traced. The preceding message will give the identity of the trace node and the message flow in which it was defined.
Response
Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then redeploy the message flow: Correct the trace pattern and redeploy the message flow.

BIP4014
<insert_1> : Invalid value <insert_0> for the 'treatWarningsAsErrors' attribute of a database node; 'yes' or 'no' required.
Severity
20 : Error
Explanation
The 'treatWarningsAsErrors' attribute can have the values 'no' or 'yes'. An attempt was made to set the attribute to the value <insert_0>.
Response
Correct the value of the attribute to either 'no' or 'yes'.

BIP4020
NeonRules node <insert_1> received an invalid message with the following parts: <insert_0>.
Severity
20 : Error
Explanation
Messages received must consist of a Properties folder, an MQMD, an MQRFH or MQRFH2 (optional), and a 'NEON' body. The message consisted of the following parts : <insert_0>.
Response
Correct either the application or message flow which is originating the message being processed by the NeonRules node so that it conforms to the rules described above. Alternatively augment the message flow processing nodes prior to the NeonRules node to transform the incoming message into the desired form.

BIP4021
<insert_4>: Rules evaluation failed. Message details: application group <insert_0>; message type <insert_1>; rules error # <insert_2>; rules error message <insert_3>.
Severity
20 : Error
Explanation
Details of the message and the error raised whilst processing the message by the NNSY rules processor are:- Application group: <insert_0>
Message type: <insert_1>
Rules Error #: <insert_2>
Rules Error Message: <insert_3>.
If the Rules Error Message refers to a problem parsing the input message, this may be due to a problem with the database connection rather than a problem with the message itself. Check that the file pointed to by MQSI_PARAMETERS_FILE contains the correct parameters to allow the NeonRules node to connect to the database containing your NNSY Rules and Formats.
Response
Further details of the error message and corrective actions can be found in the NNSY manuals.

BIP4022
Node <insert_2>: Rules evaluation succeeded: application group <insert_0>; message type <insert_1>.
Severity
0 : Information
Explanation
Application group: <insert_0>, Message type: <insert_1>.
Response
No user action required.

BIP4023
<insert_4>: Unknown action detected. Message details: application group <insert_0>; message type <insert_1>; action name <insert_2>; subscription ID <insert_3>.
Severity
20 : Error
Explanation
The action resulting from processing a message through the NeonRules node is not supported. Full details of the message and the resulting action are Application group: <insert_0>
Message type: <insert_1>
Action Name: <insert_2>
Subscription ID: <insert_3>
Response

Correct the NNSY rules to ensure that the resultant actions are supported by WebSphere Message Brokers.

BIP4024
Node <insert_2>: The rules evaluation yielded a subscription. Message details: application group <insert_0>; message type <insert_1>.
Severity
0 : Information
Explanation
Application group: <insert_0>, Message type: <insert_1>.
Response
No user action required.

BIP4025
Node <insert_2>: No subscriptions found. Message details: application group <insert_0>; message type <insert_1>.
Severity
0 : Information
Explanation
Application group: <insert_0>, Message type: <insert_1>.
Response
No user action required.

BIP4026
An unknown error occurred processing the rules.
Severity
20 : Error
Explanation
An unexpected error has occurred whilst processing a message by the NeonRules node.
Response
This is an internal error. Contact your IBM support center.

BIP4027
Node <insert_2>: Performing a reformat operation. Message details: input message type <insert_0>; output message type <insert_1>.
Severity
0 : Information
Explanation
Input Message Type: <insert_0>, Output Message Type: <insert_1>.
Response
No user action required.

BIP4028
Failed to reformat message. Message details: input message type <insert_0>; output message type <insert_1>; formatter error number <insert_2>; formatter error message <insert_3>.
Severity
20 : Error
Explanation
Details of the message and the error raised whilst formatting the message by the NNSY formatter are:- Input message type: <insert_0>
Output message type: <insert_1>
Formatter Error number: <insert_2>
Formatter Error Message: <insert_3>
Response

Further details of the error message and corrective actions can be found in the NNSY manuals.

BIP4029
Node <insert_2>: Reformat completed successfully. Message details: input message type <insert_0>; output message type <insert_1>.
Severity
0 : Information
Explanation
Input Message Type: <insert_0>, Output Message Type: <insert_1>.
Response
No user action required.

BIP4030
Target queue not set for putqueue action.
Severity
20 : Error
Explanation
The NNSY rules processor has evaluated a message with a putqueue action, but has not specified a target queue to which the resultant message should be sent.
Response
Correct the NNSY rules to ensure that the action is correctly specified.

BIP4031
Output type not set for reformat.
Severity
20 : Error
Explanation
The NNSY rules processor has evaluated a message with a reformat action, but has not specified an output type for the message.
Response
Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give details of the correct specification of the actions.

BIP4032
Input type not set for reformat.
Severity
20 : Error
Explanation
The NNSY rules processor has evaluated a message with a reformat action, but has not specified an input type for the message.
Response
Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give details of the correct specification of the actions.

BIP4033
Cannot propagate RF header, there is no RF header on the input message.
Severity
20 : Error
Explanation
The NNSY rules processor has evaluated a message with a propagate action indicating that the rules and formatter header should be included. However the incoming message did not include this header.
Response
Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give details of the correct specification of the actions.

BIP4036
Node <insert_7>: Performing a putqueue action. Options: OPT_TARGET_QUEUE <insert_0>; OPT_APP_GRP <insert_1>; OPT_MSG_TYPE <insert_2>; MQS_FORMAT <insert_3>; MQS_EXPIRY <insert_4>; MQS_PERSIST <insert_5>; MQS_PROPAGATE <insert_6>.
Severity
0 : Information
Explanation
The putqueue options are listed above.
Response
No user action required.

BIP4037
Node <insert_7>: Performing a propagate action. Options: OPT_APP_GRP <insert_1>; OPT_MSG_TYPE <insert_2>; MQS_FORMAT <insert_3>; MQS_EXPIRY <insert_4>; MQS_PERSIST <insert_5>; MQS_PROPAGATE <insert_6>.
Severity
0 : Information
Explanation
The propagate options are listed above.
Response
No user action required.

BIP4038
<insert_0>: The 'targetFormat' attribute cannot be empty.
Severity
20 : Error
Explanation
The targetFormat attribute must specify a valid NNSY output format as the target of the format operation. It cannot be the empty string.
Response
Use the Message Brokers Toolkit to set the value of the targetFormat attribute to the correct value and redeploy the message flow.

BIP4039
The NeonFormatter node <insert_1> received an invalid message, body type <insert_0>.
Severity
20 : Error
Explanation
The messages received by the NeonFormatter node must have a 'NEON' body. The body type of the message received was <insert_0>.
Response
Check that the application or message flow generating the messages destined for the current message flow are producing the messages with a Rules and Formatter Header (MQRFH) identifying that the body of the message is of type 'NEON'. If no Rules and Formatter Header is present, the MQInput node for the message flow can specify that the body is of default type 'NEON'.

BIP4040
The Execution Group <insert_0> has processed a configuration message successfully.
Severity
0 : Information
Explanation
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
Response
No user action required.

BIP4041
Execution group <insert_0> received an invalid configuration message. See the following messages for details of the error.
Severity
20 : Error
Explanation
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Response
Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.

BIP4042
Invalid action <insert_0> in configuration message.
Severity
20 : Error
Explanation
The message broker received a configuration message containing the invalid action <insert_0>. This error can only result from configuration messages having an invalid structure.
Response
Ensure that no applications are writing to the broker's configuration queues.

BIP4043
Invalid action <insert_0> on resource <insert_1> in configuration message.
Severity
20 : Error
Explanation
The message broker received a configuration message which attempted the action <insert_0> on the resource <insert_1> but this action is not valid for this type of resource.
Response
Check that all necessary user-defined extensions are installed.

BIP4044
Invalid configuration message.
Severity
20 : Error
Explanation
The message broker received an invalid configuration message and has not been able to restore its original configuration. It will now restart.
Response
If the problem is not cleared by the restart, check that the database being used to store the broker's persistent state is operating correctly then stop and restart the broker.

BIP4045
Configuration changed successfully.
Severity
0 : Information
Explanation
The message broker received a configuration message and updated its configuration accordingly. This change concerned its publish-subscribe capability.
Response
No user action required.

BIP4046
Invalid configuration message. See the following messages for details of the error.
Severity
20 : Error
Explanation
The publish/subscribe function of the broker has received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of the broker topology or topics which the Configuration Manager was unable to detect. It can also result from the broker having become out of step with the configuration repository or from other applications sending extraneous messages to the configuration queues of the broker (SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Response
Check the relevant topology and topic definitions, perform a complete redeploy of the configuration and ensure that no applications are writing to the configuration queues.

BIP4047
Invalid body type <insert_0> in configuration message.
Severity
20 : Error
Explanation
The message broker received a configuration message containing the invalid body type <insert_0>. This error can only result from configuration messages having an invalid structure.
Response
Ensure that no applications are writing to the broker's configuration queue.

BIP4048
The execution group has received a request to stop.
Severity
0 : Information
Explanation
The execution group has received a request to stop and will terminate its process as soon as possible.
Response
No user action required.

BIP4050
Duplicate labelName attribute <insert_0> in label node.
Severity
20 : Error
Explanation
Two label nodes within a message flow have been found to have the same labelName attribute <insert_0>.
Response
The message flow must be changed so that each label node has a unique labelName attribute.

BIP4051
Label node with Label Name attribute <insert_0> could not be found.
Severity
20 : Error
Explanation
A Label node with Label Name attribute of <insert_0> could not be found by a RouteToLabel node.
Response
The destination list of the message contains a destination label that does not exist. Check the validity of the SQL in the Compute node that created the destination list.

BIP4052
Unable to create the User Defined Attribute <insert_0> with a type of <insert_1> and a value of <insert_2>. Recoverable Exception information <insert_3>.
Severity
20 : Error
Explanation
The User Defined Attribute <insert_0> could not be created. The type <insert_1> or the value <insert_2> might be invalid. Refer to the Exception information <insert_3> for further information.
Response
A deploy message sent to this broker contains an invalid User Defined Attribute. Correct the User Defined Attribute and redeploy.

BIP4053
Attempt to create an existing User Defined Attribute <insert_0>.
Severity
20 : Error
Explanation
The User Defined Attribute <insert_0> already exists
Response
A deploy message sent to this broker contains a message to create an existing User Defined Attribute.

BIP4054
User Defined Attribute <insert_0> does not exist.
Severity
20 : Error
Explanation
The User Defined Attribute <insert_0> can not be reported or changed as it does not exist
Response
Correct the request for this User Defined Attribute.

BIP4055
(<insert_0>, <insert_1>) : User defined attribute must specify an initial value expression.
Severity
20 : Error
Explanation
User defined attributes must either be given an initial value on the DECLARE statement or be given a value at deploy time.
Response
Set the value of the User Defined Attribute at deploy time.

BIP4056
Unsupported data type <insert_0>.
Severity
20 : Error
Explanation
Internal error during type conversion.
Response
See previous messages for more details.

BIP4060
Data <insert_0> from trace node <insert_1>.
Severity
0 : Information
Explanation
The trace node <insert_1> has output the specified trace data.
Response
This is an information message provided by the message flow designer. The user response will be determined by the local environment.

BIP4061
Invalid trace file path specification for trace node <insert_0>.
Severity
10 : Warning
Explanation
The trace node <insert_0> has its destination specified to be a file but the given file path is empty. The message flow processing will continue, but trace output will not be written.
Response
Correct the message flow definition and redeploy it to the broker.

BIP4062
Node (class=<insert_0> name=<insert_1>) did not specify a closing brace in pattern attribute.
Severity
20 : Error
Explanation
A Trace node in a message flow included an expression within a 'pattern' attribute. However, the expression was not terminated with a closing brace character.
Response
Correct the message flow configuration and redeploy the broker.

BIP4063
Node (class=<insert_0>, name=<insert_1>) contained an error in the trace pattern.
Severity
20 : Error
Explanation
The pattern attribute in the specified trace node was not specified correctly.
Response
Correct the message flow configuration and redeploy the broker.

BIP4064
Operating system error <insert_1> opening trace file <insert_0> for trace node <insert_2>.
Severity
10 : Warning
Explanation
The trace node <insert_2> attempted to open the trace file <insert_0> but the operating system reported the error <insert_1>. Message flow processing will continue, but trace output will not be written. The node will continually attempt to open the file until it succeeds.
Response
If the name or location of the file was not specified correctly, then correct the message flow configuration and redeploy the broker. If the file could not be opened due to an environment or system error, take appropriate action to correct this situation.

BIP4065
Operating system error <insert_1> attempting to write to trace file <insert_0> for trace node <insert_2>.
Severity
10 : Warning
Explanation
The trace node <insert_2> attempted write to open the trace file <insert_0> but the operating system reported the error <insert_1>. Message flow processing will continue, but trace output will not be written. The node will continually attempt to open the file until it succeeds.
Response
If the file could not be opened due to an environment or system error, take appropriate action to correct this situation.

BIP4066
Unable to output trace data for trace node <insert_0>.
Severity
10 : Warning
Explanation
The trace node <insert_0> was unable to output trace data during its execution. The following messages will indicate the reason(s) for this.
Response
Refer to the following messages and take appropriate action.

BIP4067
Message propagated to output terminal for trace node <insert_0>.
Severity
0 : Information
Explanation
The trace node <insert_0> has received a message and is propagating it to any nodes connected to its output terminal.
Response
No user action required.

BIP4080
Message propagated to try terminal from try-catch node <insert_0>.
Severity
0 : Information
Explanation
The try-catch node <insert_0> has received a message and is propagating it to any nodes connected to its try terminal.
Response
No user action required.

BIP4081
Message propagated to catch terminal from try-catch node <insert_0>.
Severity
0 : Information
Explanation
The try-catch node <insert_0> has caught an exception which occurred in a node connected to its try terminal. The message has been augmented with an exception list and is propagating it to any nodes connected to its catch terminal for further processing. See the following messages for details of the exception list.
Response
No user action required.

BIP4101
Exception thrown by throw node <insert_0>.
Severity
0 : Information
Explanation
The throw node <insert_0> has received a message and will throw an exception as this is its normal behavior.
Response
No user action required.

BIP4120
Configuration message contained an invalid SQL expression; compute node <insert_0> in message flow <insert_1>.
Severity
20 : Error
Explanation
The compute node <insert_0> in message flow <insert_1> reported an error processing its compute expression.
Response
See the following messages for details of the error.

BIP4121
Syntax error in SQL statements in compute node <insert_2>.
Severity
20 : Error
Explanation
The configuration of compute node <insert_2> failed due to errors in the SQL expression. See the following messages for details of the error. The statement text was <insert_1>.
Response
The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for compute node SQL statements in the WebSphere Message Brokers publications. Correct the statements configuring the node and redeploy the configuration.

BIP4123
Incorrect return type <insert_0> in compute node <insert_2>. The value returned was <insert_1>.
Severity
20 : Error
Explanation
Return statements in compute nodes must return a value of type 'bool'
Response
Examine the logic of the given node's SQL statements, correct them and redeploy.

BIP4124
Message propagated to 'out' terminal of compute node <insert_0>.
Severity
0 : Information

BIP4140
Exception condition detected by user-defined node <insert_0>.
Severity
0 : Information
Explanation
The user-defined node <insert_0> detected an error during processing. The behavior of the message flow will depend upon how the user-defined node has reacted to the generation of the exception. A well behaved user-defined node is expected to re-throw the exception for it to be caught and handled by the message flow as normal.
Response
Check any error messages which follow to determine why the exception was generated, and take action as described by those messages.

BIP4141
Exception condition detected in user-defined node or parser <insert_6>. Arguments: type <insert_0>; file <insert_1>; line <insert_2>; function <insert_3>; messageNumber <insert_4>; traceText <insert_5>.
Severity
20 : Error
Explanation
The user-defined node or parser <insert_6> has attempted to throw an exception by calling the cciThrowException() utility function, but the exception type specified in the 'type' argument was invalid. This is a problem within the user-defined extension software itself.
Response
Correct the problem in the user-defined extension software or contact the supplier of the user-defined extension to report the problem.

BIP4142
Evaluating cniElementSet<insert_0>. Changing value from <insert_1> to <insert_2>.
Severity
0 : Information
Explanation
Element <insert_0> has been changed to <insert_2>.
Response
No user action required.

BIP4143
Invalid terminal name.
Severity
20 : Error
Explanation
An attempt was made to create a terminal with no name.
Response
Ensure the terminal has a valid name.

BIP4144
Entered function <insert_0>(<insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>).
Severity
0 : Information
Explanation
Entered the specified function with the specified parameters.
Response
No user action required.

BIP4145
Exiting function <insert_0> with result: <insert_1>(<insert_2>).
Severity
0 : Information
Explanation
About to exit the specified the function with the specified result.
Response
No user action required.

BIP4146
Evaluating cpiSetElement<insert_0>. Changing value from <insert_1> to <insert_2>.
Severity
0 : Information
Explanation
Element <insert_0> has been changed to <insert_2>.
Response
No user action required.

BIP4147
User-defined extension input parameter failed debug validation check.
Severity
20 : Error
Explanation
Input parameter <insert_1> passed into function <insert_0> is not a valid object.
Response
Correct user-defined extension implementation accordingly.

BIP4148
User-defined extension damaged broker's object.
Severity
20 : Error
Explanation
Function <insert_0> has damaged broker's object passed as parameter <insert_1>.
Response
Correct user-defined extension implementation accordingly.

BIP4149
User-defined extension input parameter failed debug validation check.
Severity
20 : Error
Explanation
Input parameter <insert_1> passed into function <insert_0> is a NULL pointer.
Response
Correct user-defined extension implementation accordingly.

BIP4150
User-defined extension input parameter failed debug validation check.
Severity
20 : Error
Explanation
Input parameter <insert_1> passed into function <insert_0> does not have a valid value.
Response
Correct user-defined extension implementation accordingly.

BIP4151
An unexpected value was returned from User-defined extension implementation function <insert_0>.
Severity
20 : Error
Explanation
The implementation function returned <insert_1> but the expected values are <insert_2>.
Response
Correct user-defined extension implementation accordingly.

BIP4152
User-defined extension Implementation function <insert_0> returned CCI_BUFFER_TOO_SMALL on 2nd attempt.
Severity
20 : Error
Explanation
The implementation function <insert_0> has set the returnCode output parameter to CCI_BUFFER_TOO_SMALL and returned <insert_1> as the required size of the buffer in characters. The function was then invoked with a buffer of this size and again set returnCode to CCI_BUFFER_TOO_SMALL.
Response
Correct user-defined extension implementation accordingly.

BIP4153
The user-defined property (UDP) <insert_0> has an invalid data type <insert_1>.
Severity
20 : Error
Explanation
The datatype <insert_1> is not supported as a UDP. This can be due to using versions of runtime components that are incompatible with your Message Brokers Toolkit.
Response
Make sure that you are using versions of runtime components that are compatible with your Message Brokers Toolkit.

BIP4154
The user-defined property (UDP) <insert_0> of datatype <insert_1> has an incorrect structure. Reason: <insert_2>
Severity
20 : Error
Explanation
An internal problem has occurred trying to construct the datatype <insert_1>. This can be due to using versions of runtime components that are incompatible with your Message Brokers Toolkit.
Response
Make sure that you are using versions of runtime components that are compatible with your Message Brokers Toolkit.

BIP4155
A dynamic terminal called <insert_1> (of type <insert_0>) could not be created because there is already a terminal with that name.
Severity
20 : Error
Explanation
The message flow definition deployed to the broker either defines a new terminal with the same name as one that already exists, or it defines the same terminal twice. This can be due to using versions of runtime components that are incompatible with your Message Brokers Toolkit.
Response
Make sure that you are using versions of runtime components that are compatible with your Message Brokers Toolkit.

BIP4156
A dynamic terminal of type <insert_0> (called <insert_1>) could not be created because this type of dynamic terminal is not allowed.
Severity
20 : Error
Explanation
You can only create a dynamic terminal of type 'output' or 'input'.
Response
This is an internal error. Contact your IBM support center.

BIP4157
The user-defined node <insert_0> could not be deployed. Details: <insert_1>
Severity
20 : Error
Explanation
The node could not be deployed because an error in the node's 'onInitialize' method prevented the node from initializing.
Response
Review the details given above. Report the error to the node's writer if you cannot correct the error yourself.

BIP4160
Message propagated to match terminal by check node <insert_0>.
Severity
0 : Information
Explanation
The check node <insert_0> has matched a received message against the criteria and is propagating it to any nodes connected to its match terminal.
Response
No user action required.

BIP4161
Message propagated to failure terminal by check node <insert_6>. Values received: domain <insert_0>; set <insert_1>; type <insert_2>. Values expected: domain <insert_3>; set <insert_4>; type <insert_5>.
Severity
20 : Error
Explanation
The check node <insert_6> has detected that a received message did not match the specified criteria and that there is a message flow processing node attached to its failure terminal and thus the message is being propagated to any nodes connected to that terminal.

BIP4162
Nonmatching message rejected by check node <insert_6>. Values received: domain <insert_0>; set <insert_1>; type <insert_2>. Values expected: domain <insert_3>; set <insert_4>; type <insert_5>.
Severity
20 : Error
Explanation
The check node <insert_6> has detected that the input message did not match the specified criteria and that there is NOT a message flow processing node attached to its failure terminal. An exception is therefore being generated.
Response
Identify why invalid messages are either being sent into the broker or being generated, correcting the problem if necessary. If the check node attributes are not being specified correctly, correct them and redeploy the message broker.

BIP4163
Message propagated to the first terminal of the FlowOrder node <insert_0>.
Severity
0 : Information
Explanation
The FlowOrder node has received a message and has propagated it to the output terminal called first. Once the processing of the message down the first terminal has finished, the message will be propagated to the second terminal.
Response
No user action required.

BIP4164
Message propagated to the second terminal of the FlowOrder node <insert_0>.
Severity
0 : Information
Explanation
The FlowOrder node has finished processing a message down the first terminal and has propagated it to the second terminal.
Response
No user action required.

BIP4180
Message propagated to output terminal by database node <insert_0>.
Severity
0 : Information
Explanation
The database node <insert_0> has received a message and is propagating it to any nodes connected to its output terminal.
Response
No user action required.

BIP4181
Syntax error in SQL statements in database node <insert_2>.
Severity
20 : Error
Explanation
The configuration of database node <insert_2> failed due to errors in the SQL statement text. See the following messages for details of the error. The statement text was <insert_1>.
Response
The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for database node SQL statements in the WebSphere Message Brokers publications. Correct the statements and redeploy the configuration.

BIP4183
Incorrect return type <insert_0> in database node <insert_2>. The value returned was <insert_1>.
Severity
20 : Error
Explanation
Return statements in database nodes must return a value of type 'bool'
Response
Examine the logic of the given node's SQL statements, correct them and redeploy.

BIP4184
Message propagated to 'out' terminal of database node <insert_0>.
Severity
0 : Information

BIP4201
Message propagated to out terminal from node <insert_0>.
Severity
0 : Information
Explanation
A reset content descriptor node has received a message and is propagating it to any nodes connected to its out terminal.
Response
No user action required.

BIP4202
The WebSphere MQ Everyplace queue manager failed to start.
Severity
30 : Severe error
Explanation
The WebSphere MQ Everyplace queue manager failed to start.
Response
Ensure that the queue manager has been created and that the registry entry is correct.

BIP4203
The internal WebSphere MQ Everyplace transformer component failed to initialize.
Severity
30 : Severe error
Explanation
The internal WebSphere MQ Everyplace transformer component failed to initialize.
Response
Ensure that a valid transformer is being used within WebSphere MQ Everyplace.

BIP4204
WebSphere MQ Everyplace configuration error.
Severity
30 : Severe error
Explanation
WebSphere MQ Everyplace configuration error.
Response
If using a WebSphere MQ Everyplace ini file, please ensure that it is valid.

BIP4205
A WebSphere MQ Everyplace error occurred. The exact nature of the problem could not be determined.
Severity
30 : Severe error
Explanation
A WebSphere MQ Everyplace error occurred. The exact nature of the problem could not be determined.
Response
Please refer to trace messages before this error occurred.

BIP4206
The mqimqe.jar file could not be loaded.
Severity
30 : Severe error
Explanation
The mqimqe.jar could not be read at runtime.
Response
Ensure that the file exists within the application.

BIP4207
A WebSphere MQ Everyplace method could not be accessed.
Severity
20 : Error
Explanation
A WebSphere MQ Everyplace method within the mqimqe.jar file could not be accessed.
Response
Ensure that the mqimqe.jar file is not damaged.

BIP4208
WebSphere MQ Everyplace database error. Cannot write to inbound table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to write to the WebSphere MQ Everyplace inbound table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4209
Error attempting to write to WebSphere MQ Everyplace outbound database table.
Severity
30 : Severe error
Explanation
An error was encountered whilst attempting to write to the WebSphere MQ Everyplace outbound database table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4210
WebSphere MQ Everyplace database error. Cannot write to outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to write to the WebSphere MQ Everyplace destination table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4211
WebSphere MQ Everyplace database error. Cannot read from inbound table.
Severity
20 : Error
Explanation
An error occurred whilst attempting to read from the WebSphere MQ Everyplace inbound table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4212
WebSphere MQ Everyplace database error. Cannot read from outbound message table.
Severity
20 : Error
Explanation
An error occurred whilst attempting to read from the WebSphere MQ Everyplace outbound message table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4213
WebSphere MQ Everyplace database error. Cannot read a record from outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to read a record from the WebSphere MQ Everyplace destination table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4214
WebSphere MQ Everyplace database error. Cannot delete record from inbound table.
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete the WebSphere MQ Everyplace inbound message table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4215
WebSphere MQ Everyplace database error. Cannot delete record from outbound table.
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete a record from the WebSphere MQ Everyplace outbound message table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4216
WebSphere MQ Everyplace database error. Cannot delete record from outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete a WebSphere MQ Everyplace outbound destination message record.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4217
WebSphere MQ Everyplace database error. Cannot put non-publish/subscribe WebSphere MQ Everyplace message to table.
Severity
30 : Severe error
Explanation
Cannot put non-publish/subscribe WebSphere MQ Everyplace message to inbound WebSphere MQ Everyplace table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4218
Cannot read non-publish/subscribe WebSphere MQ Everyplace message from table.
Severity
30 : Severe error
Explanation
Cannot read a non-publish/subscribe WebSphere MQ Everyplace message from table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4219
WebSphere MQ Everyplace database error. Cannot delete non-publish/subscribe WebSphere MQ Everyplace message from the database table.
Severity
30 : Severe error
Explanation
Cannot delete a non-publish/subscribe WebSphere MQ Everyplace message from table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4220
Message propagated to out terminal from node <insert_0>.
Severity
0 : Information
Explanation
A label node has received a message and is propagating it to any nodes connected to its out terminal.
Response
No user action required.

BIP4221
Some (but not all) of the WebSphere MQ Everyplace tables are missing.
Severity
20 : Error
Explanation
Some (but not all) of the WebSphere MQ Everyplace tables are missing.
Response
Recreate the broker.

BIP4222
The mqisdp.jar file could not be loaded.
Severity
30 : Severe error
Explanation
The mqisdp.jar could not be read at runtime.
Response
Ensure that the file exists within the application.

BIP4223
A SCADA method could not be accessed.
Severity
30 : Severe error
Explanation
A SCADA method within the mqisdp.jar file could not be accessed.
Response
Ensure that the mqisdp.jar file is not damaged.

BIP4224
SCADA database error. Cannot write to inbound table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to write to the SCADA inbound table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4225
Error attempting to write to SCADA outbound database table.
Severity
30 : Severe error
Explanation
An error was encountered whilst attempting to write to the SCADA outbound database table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4226
SCADA database error. Cannot write to outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to write to the SCADA destination table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4227
SCADA database error. Cannot read from inbound table.
Severity
20 : Error
Explanation
An error occurred whilst attempting to read from the SCADA inbound table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4228
SCADA database error. Cannot read from outbound message table.
Severity
20 : Error
Explanation
An error occurred whilst attempting to read from the SCADA outbound message table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4229
SCADA database error. Cannot read from outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred whilst attempting to write to the SCADA destination table.
Response
Ensure that the database tables exist and that the application has appropriate access.

BIP4230
SCADA database error. Cannot delete record from inbound table.
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete the SCADA inbound message table.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4231
SCADA database error. Cannot delete record from outbound table
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete a record from the SCADA inbound message table
Response
Ensure that the database tables exist and that the application has appropriate access to the database

BIP4232
SCADA database error. Cannot delete record from outbound destination table.
Severity
30 : Severe error
Explanation
An error occurred when attempting to delete a SCADA outbound destination message record.
Response
Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4233
Could not resolve destination node using specified port number.
Severity
10 : Warning
Explanation
Could not resolve destination node using specified port number. A subscription has been made by a node that no longer exists.
Response
Unsubscribe from all subscriptions for the node no longer being used.

BIP4234
Failed to get a message from the queue.
Severity
10 : Warning
Explanation
Failed to get a message from the queue.
Response
No user action required.

BIP4235
Failed to put a message onto the queue.
Severity
30 : Severe error
Explanation
Failed to put a message onto the queue.
Response
Queue may be full. No user action required.

BIP4236
Node <insert_0> failed to bind to port <insert_1>
Severity
30 : Severe error
Explanation
The port number specified for the node is already being used in another message flow, or is unavailable for some other reason.
Response
Change the port number to one not being used by another message flow or by another quite separate application. If one message flow is replacing another using the same port number, use a full rather than a delta deploy. This ensures that the old flow is removed from service at the broker before the new flow is introduced.

BIP4237
SCADA Initialization failed.
Severity
10 : Warning
Explanation
An internal error stopped the SCADA server from starting.
Response
Redeploy the message flow.

BIP4238
MQIsdp manager not available.
Severity
30 : Severe error
Explanation
Initialization problem with the SCADA node.
Response
Redeploy the message flow.

BIP4239
Some of the SCADA database tables are missing.
Severity
30 : Severe error
Explanation
The SCADA Input node was unable to find all of the database tables required for correct operation
Response
Recreate the broker.

BIP4240
RouteToLabel node <insert_1> unable to locate Label node <insert_0>.
Severity
20 : Error
Explanation
A RouteToLabel node has received a message containing a label but there is no Label node with this label.
Response
This problem may result from the logic of the message flow as specified by the user not calculating a valid Label node name for all valid input messages, from the input message being of an unexpected nature or from the deployed configuration not being as intended. Check the logic of the message flow to ensure that in all cases the calculated Label node names will be correct and then check that the input message is not of an unexpected nature. Finally 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.

BIP4241
Message propagated to target Label node by RouteToLabel node <insert_0>.
Severity
0 : Information
Explanation
A RouteToLabel node has received a message and is propagating it to the appropriate Label node.
Response
No user action required.

BIP4242
Failure putting message to <insert_3> queue manager <insert_0>, queue <insert_1>, from node type <insert_2>
Severity
20 : Error
Explanation
WebSphere Message Brokers failed in an attempt to put a message.
Response
Examine the message flow nodes, and make any corrections that may be necessary. For example, an MQeOutput node may include an incorrect Destination Mode, Queue Manager Name or Queue Name property.

BIP4243
Unexpected message number <insert_0> received from <insert_1> for node type <insert_2>
Severity
20 : Error
Explanation
An internal error occurred in communication within WebSphere Message Brokers.
Response
Your installation of WebSphere Message Brokers requires service. Pass details of this message to your administrator.

BIP4244
WebSphere MQ Everyplace redirection error
Severity
20 : Error
Explanation
An attempt to redirect output from WebSphere MQ Everyplace for the trace file failed.
Response
Check that the file details for the WebSphere MQ Everyplace trace file are correct and that the file can be written to.

BIP4245
WebSphere MQ Everyplace configuration template error
Severity
20 : Error
Explanation
An error occurred either creating or expanding a configuration template for WebSphere MQ Everyplace.
Response
Refer to the WebSphere MQ Everyplace trace file for further information.

BIP4246
WebSphere Everyplace JNI initialization failure
Severity
30 : Severe error
Explanation
A node is unable to communicate with WebSphere Everyplace using the JNI.
Response
Check that the Java code in the CLASSPATH used by WebSphere Message Brokers is not damaged.

BIP4247
Unable to get message from SCADA
Severity
20 : Error
Explanation
The buffer allocated internally for a message from SCADA is too small.
Response
Report this error to your IBM Support Center.

BIP4248
Unable to confirm WebSphere MQ Everyplace message with Unique ID <insert_0>
Severity
10 : Warning
Explanation
The WebSphere MQ Everyplace message with the given Unique ID could not be confirmed. This may be because no message with the ID was previously received, or because the message previously received can no longer be referenced by the broker. The Unique ID comprises the 2 WebSphere MQ Everyplace properties MQe.Msg_OriginQMgr and MQe.Msg_Time, concatenated with an intervening period.
Response
Check WebSphere MQ Everyplace client programs for the correct use of confirmPutMessage. Check that there have been no broker database errors that may have caused messages to be lost during database recovery.

BIP4249
Scada Thread pool is busy.
Severity
20 : Error
Explanation
The Scada thread pool is overloaded or has stopped working.
Response
If there is no co-responding BIP4250 message then the Scada thread pool may have stopped working or is overloaded.

BIP4250
Scada Thread pool has recovered.
Severity
10 : Warning
Explanation
The Scada thread pool has recovered from an overloaded period.
Response
This indicates that the Scada thread pool has recovered after an overloaded condition.

BIP4260
A memory allocation error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in allocating the thread local storage index.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4261
A thread creation error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in creating a thread responsible for transmitting the breakpoint information.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4262
An initialization error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in creating the node factory provided by the interface cniCreateNodeFactory.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4263
An operational error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in defining a node class within the node factory.
Response
Check if the XML definition of the node ImbDebugNode is valid and retry the operation. If this problem persists, contact your IBM support center.

BIP4264
A threading problem occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in blocking incoming threads, the Message Brokers Toolkit debugger might not work properly.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4265
A mutual exclusion error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in releasing a mutex object.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4266
Unable to get an attribute from a node.
Severity
20 : Error
Explanation
The attribute 'FlowUuid' could not be received from the node ImbDebugNode.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4267
Unable to get an attribute from a node.
Severity
20 : Error
Explanation
The attribute 'DebugNodeID' could not be received from the node ImbDebugNode.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4268
A mutual exclusion error occurred.
Severity
20 : Error
Explanation
An access violation occurred while waiting for a mutex object in the node ImbDebugNode.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4269
A propagation error occurred.
Severity
10 : Warning
Explanation
The node ImbDebugNode was unsuccessful to propagate a message.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4270
A propagation error occurred.
Severity
20 : Error
Explanation
An Output terminal is not connected.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4271
An element error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode received an unknown value type for an element.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4272
An element error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in extracting an element value.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4273
An element error occurred.
Severity
10 : Warning
Explanation
The node ImbDebugNode was unsuccessful in extracting an element name.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4274
An element error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in extracting an element type.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4275
An element error occurred.
Severity
10 : Warning
Explanation
The node ImbDebugNode was unsuccessful in setting an element value.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4276
A terminal creation error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in creating an Input terminal.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4277
A terminal creation error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in creating an Output terminal.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4278
A create node error occurred.
Severity
20 : Error
Explanation
The node name is not supported for the node ImbDebugNode.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4279
A communication setting error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in getting the controller IP address.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4280
A reception error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in receiving information from the Message Brokers Toolkit.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4281
A socket error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in creating a socket.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4282
A socket error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in setting the socket options.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4283
A connection error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in connecting to a Message Brokers Toolkit socket.
Response
Restart your broker, restart your Message Brokers Toolkit and retry the operation. If this problem persists, contact your IBM support center.

BIP4284
A sending error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in sending information to the Message Brokers Toolkit.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4285
A socket error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in binding a socket.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4286
A socket error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in listening to a client connection.
Response
Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

BIP4287
A memory allocation error occurred.
Severity
20 : Error
Explanation
The node ImbDebugNode was unsuccessful in allocating memory.
Response
Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4302
WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.
Severity
20 : Error
Explanation
WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.
Response
Add the required name/value pair and redeploy the message flow.

BIP4303
The trace file for WebSphere MQ Everyplace could not be created
Severity
20 : Error
Explanation
The trace file specified for WebSphere MQ Everyplace trace could not be created.
Response
Ensure that your disk is not full and that this file is not write protected.

BIP4342
WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.
Severity
20 : Error
Explanation
WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.
Response
Add the required name/value pair and redeploy the message flow.

BIP4343
The trace file for WebSphere MQ Everyplace could not be created
Severity
20 : Error
Explanation
The trace file specified for WebSphere MQ Everyplace could not be created.
Response
Ensure that your disk is not full and that this file is not write protected.

BIP4350
An error has occurred in the debugger.
Severity
30 : Severe error
Explanation
An internal error has occurred in the debugger.
Response
Contact your local IBM support center.

BIP4351
An error has occurred in the debugger's Remote Agent Controller
Severity
20 : Error
Explanation
The Remote Agent Controller is a separate process used to debug the broker.
Response
Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.

BIP4352
An error occurred when trying to communicate with the debugger
Severity
30 : Severe error
Explanation
Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.

BIP4353
An error occurred in the JNI layer during flow debugging
Severity
20 : Error
Explanation
Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.

BIP4354
An error occurred when invoking the debugger
Severity
30 : Severe error
Explanation
Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.

BIP4360
Java node information: <insert_0>.
Severity
0 : Information
Explanation
Information message generated by Java node.
Response
No user action required.

BIP4361
Java node warning: <insert_0>.
Severity
10 : Warning
Explanation
Warning message generated by user Java node.
Response
Contact the node provider for further details.

BIP4362
Java node error: <insert_0>.
Severity
20 : Error
Explanation
Error message generated by user Java node.
Response
Contact the node provider for further details.

BIP4363
The Java API framework could not locate the <insert_0>: <insert_1>.
Severity
30 : Severe error
Explanation
An internal JNI error has occurred during property introspection.
Response
This is an internal error. Contact your IBM support center.

BIP4364
The Java API framework could not create an instance of <insert_0>.
Severity
30 : Severe error
Explanation
An internal JNI error has occurred during object instantiation.
Response
This is an internal error. Contact your IBM support center.

BIP4365
The Java API framework could not create an array of <insert_0>, size[<insert_1>].
Severity
30 : Severe error
Explanation
An internal JNI error has occurred during the creation of an array.
Response
This is an internal error. Contact your IBM support center.

BIP4366
Unable to create Java node <insert_0> of type <insert_1>.
Severity
20 : Error
Explanation
An exception has occurred during the creation of the Java node: <insert_2>
Response
Contact the node provider for further details.

BIP4367
The method <insert_0> in Java node <insert_1> has thrown the following exception: <insert_2>.
Severity
20 : Error
Explanation
The method <insert_0> of the Java node has thrown an exception. Examine previous error messages for details of the cause of the problem.
Response
This error is generated by the Java node API. It can occur in a Java Compute node or a Java user-defined node. If the node is a user-defined node, contact the node provider for further details.

BIP4368
The method <insert_0> has thrown the following exception: <insert_1>.
Severity
30 : Severe error
Explanation
The Java API framework has caught an unhandled Java exception.
Response
Contact the node provider for further details.

BIP4369
A memory allocation error has occurred.
Severity
20 : Error
Explanation
The Java API framework was unsuccessful in allocating memory.
Response
Restart you broker and retry the operation. If the problem persists, contact your IBM support center.

BIP4370
Failure in CNI layer, return code is <insert_0>.
Severity
20 : Error
Explanation
An internal error has occurred in the CNI layer of the user-defined node interface.
Response
This is an internal error. Contact your IBM support center.

BIP4371
Failure to locate Java class <insert_0>
Severity
30 : Severe error
Explanation
The Java class <insert_0> could not be found by the Java API framework.
Response
This is an internal error. Contact your IBM support center.

BIP4372
Failure to locate Java method or field <insert_0> in class <insert_1>.
Severity
30 : Severe error
Explanation
The Java method or field <insert_0> in class <insert_1> could not be found by the Java API framework.
Response
This is an internal error. Contact your IBM support center.

BIP4373
Element value type <insert_0> is not valid.
Severity
30 : Severe error
Explanation
The object supplied to MbElement.setValue(...) is not a supported type.
Response
Contact the node provider for further details.

BIP4374
An unexpected exception has occurred in the Java API framework.
Severity
30 : Severe error
Explanation
An internal processing error has occurred.
Response
This is an internal error. Contact your IBM support center.

BIP4375
The transaction type <insert_0> is not recognized.
Severity
20 : Error
Explanation
The transaction type supplied to the constructor of the SQL statement has not been recognized.
Response
Contact the node provider for further details.

BIP4376
Unable to locate resource bundle <insert_0>.
Severity
30 : Severe error
Explanation
The Java resource bundle could not be found by the Java API framework.
Response
Make sure the Java resource bundle is in the CLASSPATH and restart the broker.

BIP4377
The user node <insert_0> does not have a default constructor.
Severity
30 : Severe error
Explanation
The Java API framework was unable to find a default constructor for the user node.
Response
Contact the node provider for further details.

BIP4378
The <insert_0> object has been cleared
Severity
30 : Severe error
Explanation
The node implementation has attempted to reference an object which has previously been cleared.
Response
Contact the node provider for further details.

BIP4379
An STL exception has been thrown by <insert_0>.
Severity
30 : Severe error
Explanation
An unexpected STL exception has been thrown.
Response
This is an internal error. Contact your IBM support center.

BIP4380
The terminal <insert_0> already exists.
Severity
20 : Error
Explanation
An attempt has been made to create a terminal with a name that has already been used.
Response
Make sure that the terminal name is unique.

BIP4381
Element type <insert_0> is not valid.
Severity
20 : Error
Explanation
An attempt has been made to create an element with an invalid type.
Response
Contact the node provider for further details.

BIP4382
XPath parse error at column <insert_1> in expression <insert_0>.
Severity
20 : Error
Explanation
The XPath parser encountered a syntax error in the expression.
Response
Refer to the XPath 1.0 W3C recommendation for syntax rules.

BIP4383
XPath: Both arguments of the union operator must evaluate to nodesets
Severity
10 : Warning
Explanation
One or both of the arguments to the union (|) operator evaluated to a non-nodeset type.
Response
Refer to the XPath 1.0 W3C recommendation for usage details.

BIP4384
XPath: Function <insert_0> is not in the XPath 1.0 specification or is not a broker extension function.
Severity
10 : Warning
Explanation
The XPath processor encountered an unsupported function call in the expression.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4385
XPath: Function has been passed too many arguments.
Severity
10 : Warning
Explanation
The XPath processor has encountered an unexpected comma (,) operator suggesting that a function has been passed too many arguments.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4386
XPath: Expression before relative location path does not evaluate to a nodeset.
Severity
10 : Warning
Explanation
The expression preceding the relative location path (starting with /) must evaluate to a nodeset.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4387
XPath: Predicates can only be applied to a nodeset.
Severity
10 : Warning
Explanation
The expression preceding a predicate must evaluate to a nodeset type.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4388
XPath: The variable <insert_0> is not bound to a value.
Severity
10 : Warning
Explanation
The XPath processor encountered an unbound variable reference in the expression.
Response
Bind a value to the variable reference before evaluating the expression.

BIP4389
XPath: An internal state error was encountered by the XPath evaluator (opcode <insert_0>).
Severity
20 : Error
Explanation
An internal state error was encountered by the XPath evaluator.
Response
Contact your IBM service representative.

BIP4390
XPath: The function <insert_0> has been passed the wrong number of arguments.
Severity
10 : Warning
Explanation
The function has been passed the wrong number of arguments.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4391
XPath: The argument of function <insert_0> does not evaluate to a nodeset.
Severity
10 : Warning
Explanation
The function argument must evaluate to a nodeset type.
Response
Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4392
XPath: The function 'id' is not supported by the broker.
Severity
10 : Warning
Explanation
The function 'id' is not supported by the broker.
Response
Avoid use of the XPath function 'id'.

BIP4393
XPath: The broker extension function <insert_0> requires one argument.
Severity
10 : Warning
Explanation
The broker extension function requires one argument.
Response
Check the appropriate function call in the XPath expression.

BIP4394
Java exception: <insert_0>; thrown from class name: <insert_1>, method name: <insert_2>, file: <insert_3>, line: <insert_4>; trace text: <insert_5>; resource bundle: <insert_6>; key: <insert_7>; inserts(optional): <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>, <insert_14>, <insert_15>, <insert_16>, <insert_17>
Severity
20 : Error
Explanation
The message contains that data associated with a Java exception.
Response
No user action required.

BIP4395
Java exception: <insert_0>; thrown from class name: <insert_1>, method name: <insert_2>, file: <insert_3>, line: <insert_4>
Severity
20 : Error
Explanation
The message contains that data associated with a Java exception.
Response
No user action required.

BIP4396
<insert_0> is not a valid PAR. A PAR file must contain a classes directory.
Severity
10 : Warning
Explanation
<insert_0> doesn't contain a classes directory that is required by the PAR file format.
Response
Consult the product documentation and repackage the user-defined node into a valid PAR file.

BIP4397
Loading class <insert_0> from path <insert_1> in <insert_2>.
Severity
0 : Information
Explanation
Broker JVM class loading information.
Response
No user action required.

BIP4398
Loading class <insert_0> from path <insert_1> in JAR <insert_2> packaged in PAR <insert_3>.
Severity
0 : Information
Explanation
Broker JVM class loading information.
Response
No user action required.

BIP4401
Message propagated to out terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateControl node has received a message and is propagating it to any nodes connected to its out terminal
Response
No user action required

BIP4402
Message propagated to control terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateControl node has received a message and is propagating a control message to any nodes connected to its control terminal
Response
No user action required

BIP4403
The control terminal is not connected.
Severity
20 : Error
Explanation
The control terminal on the AggregateControl node is not connected to any other nodes.
Response
Check the message flow and ensure that the control terminal on the AggregateControl node is ultimately connected to the control terminal on the corresponding AggregateReply node. This is to ensure control messages from the AggregateControl node reach the AggregateReply node.

BIP4404
Existing aggregation data found in LocalEnvironment
Severity
20 : Error
Explanation
The LocalEnvironment.ComIbmAggregateControlNode area reserved for AggregateControl node data already contains information. This message may already have passed through an AggregateControl node.
Response
Check that the message flow does not contain two AggregateControl nodes which are connected in series.

BIP4405
Aggregation data in LocalEnvironment is invalid
Severity
20 : Error
Explanation
The LocalEnvironment.ComIbmAggregateControlNode area reserved for passing information from an AggregateControl node to an AggregateRequest node does not contain valid data.
Response
Check that the message has passed through an AggregateControl node before arriving at the AggregateRequest node. Check that this LocalEnvironment data has not been lost. Nodes such as the Compute node should copy the LocalEnvironment before changing it, and should propagate it using a propagation option including LocalEnvironment.

BIP4406
Missing or invalid destination data in LocalEnvironment.WrittenDestination
Severity
20 : Error
Explanation
Part of the destination data required by the AggregateRequest node and contained in LocalEnvironment.WrittenDestination is missing or not valid. This data is usually inserted by an output node.
Response
Check that the message has previously passed through a node designed to support aggregation. The MQOutput node and MQeOutput node are two examples. Check that this LocalEnvironment data has not been lost. Nodes such as the Compute node should copy the LocalEnvironment before changing it, and should propagate it using a propagation option including LocalEnvironment.

BIP4407
Message propagated to out terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateRequest node has received a message and is propagating it to any nodes connected to its out terminal
Response
No user action required

BIP4408
Could not allocate a thread for timeout processing in AggregateReply node.
Severity
30 : Severe error
Explanation
The AggregateReply node requires a thread to perform timeout processing. This demand has been refused. Normal function cannot continue without this thread.
Response
The operating system may have run low on threads. Try to make more threads available. Try reducing the number of threads used by a message flow by decreasing the value of the 'Additional Instances' attribute from the 'Assignments' panel.

BIP4409
Control message arrived from different broker (UUID <insert_0>).
Severity
20 : Error
Explanation
The control message received through the control terminal originated from an AggregateControl node on another broker. The sending broker's UUID is included in the message.
Response
Ensure that the AggregateControl node that the control message originated from, and the AggregateReply node which received it, are on the same broker.

BIP4410
The AggregateReply node has a different aggregate name (<insert_0>) to the corresponding AggregateControl node (<insert_1>)).
Severity
20 : Error
Explanation
The control message originated from an AggregateControl node with a different aggregate name.
Response
Ensure that the AggregateControl node that the control message originated from, and the AggregateReply node which received it, have the same value for the 'aggregate name' attribute.

BIP4411
Message propagated to out terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateReply node has received a message and is propagating it to any nodes connected to its out terminal
Response
No user action required

BIP4412
Corresponding request record not found for the reply message.
Severity
0 : Information
Explanation
An AggregateReply node has received a message at its 'in' terminal. No corresponding record of a request message being sent could be found. See subsequent messages to determine how this situation has been handled.
Response
It is possible that extraneous messages are arriving at the AggregateReply node 'in' terminal. Check your flow to ensure that the only messages arriving here are replies to request messages previously sent out and passed through an AggregateRequest node. It is possible that this message is a valid reply but part of an aggregation which previously timed out. It is possible that this is a reply to a message which has not yet been recorded by an AggregateRequest node. This can happen if request messages are sent outside of transactional control. Adjust your transaction settings to ensure that messages are sent under transactional control.

BIP4413
Storing unknown message persistently for subsequent processing.
Severity
0 : Information
Explanation
The message has been stored persistently by the AggregateReply node. If it is subsequently discovered to be a valid reply in an aggregation then it will be processed as such at that time. If a number of seconds passes as specified by the 'unknown timeout' attribute, then the message will be propagated to the 'unknown' terminal.
Response
No user action required.

BIP4414
Message propagated to unknown terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateReply node has propagated a message to the 'unknown' terminal.
Response
No user action required

BIP4415
The record of the request that initiated this reply contains unexpected data.
Severity
20 : Error
Explanation
An AggregateReply node received unexpected information when dealing with the record of the request that was stored to correlate against this reply.
Response
Contact your IBM support center.

BIP4416
Message propagated to timeout terminal from node <insert_0>
Severity
0 : Information
Explanation
An AggregateReply node has propagated a message to the 'timeout' terminal.
Response
No user action required

BIP4417
Message could not be stored persistently. Missing Information : <insert_0>.
Severity
20 : Error
Explanation
An AggregateReply node attempted to store a message persistently. In order to do so, it needs to discover information from the message. Part of that information could not be found.
Response
Ensure that the message has a valid Properties folder and a payload (e.g. XML). Ensure the message has the following information : <insert_0>.

BIP4418
Invalid control message received by AggregateReply node <insert_1>. Missing Information : <insert_0>
Severity
20 : Error
Explanation
An AggregateReply node received a control message at its control terminal. The message was not in the format that was expected. The following information was expected but not found: <insert_0>
Response
Ensure that the message received at the control terminal of the AggregateReply node was generated by the control terminal of an AggregateControl node. If the message needed to be modified for delivery purposes (for example, adding an MQMD), ensure that the XML payload was not affected by this modification.

BIP4419
Invalid reply message received by AggregateReply node <insert_1>. Missing Information : <insert_0>
Severity
20 : Error
Explanation
An AggregateReply node received a message at its in terminal. The message was not in the format that was expected. The following information was expected but not found: <insert_0>
Response
Ensure that the message received at the control terminal of the AggregateReply node has a 'Properties' folder.

BIP4420
Request message identifier is not unique
Severity
20 : Error
Explanation
The AggregateRequest node <insert_0> attempted to record the delivery of a request message, but the message's unique identifier has already been used.
Response
Ensure that a new unique identifier is generated for the request message you are passing to the AggregateRequest node. This can be achieved by using the 'Request' tab when configuring the MQOutput node or the MQeOutput node. Check that the same message is not being propagated to more than one AggregateRequest node.

BIP4421
Empty message received by the AggregateReply node.
Severity
20 : Error
Explanation
An AggregateReply node is unable to process an empty message.
Response
Check the flow that has propagated the message to this node.

BIP4422
Unable to store request message in AggregateReply node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateReply node failed to store a message recording an aggregation request. This message is used by the node to record the details of the reply it expects back from a particular request. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4423
Unable to store control message in AggregateReply node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateReply node failed to store a control message. This message is used by the node to control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4424
Unable to retrieve control message in AggregateReply node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateReply node failed to retrieve a control message. This message is used by the node to control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to get a message from queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4425
Unable to retrieve request message in AggregateReply node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateReply node failed to retrieve a request message. This message is used to store state about a request. Failed to get a message from queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4426
Unable to store request message in AggregateControl node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateControl node failed to store a request message. This message is used by the node to control a particular aggregation. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4427
Unable to store control message in AggregateControl node. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The AggregateControl node failed to store a control message. This message is used by the node to control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4428
Missing aggregate request information in Environment. The missing information was in aggregate folder : <insert_0>.
Severity
20 : Error
Explanation
An AggregateControl node attempted to process the information about individual aggregate requests. In order to do so, it needs specific information to be stored by AggregateRequest nodes. Part of that information could not be found.
Response
Ensure that the message flow is correctly designed for aggregation. In particular, verify that Output nodes come before AggregateRequest nodes and that the Environment of the message tree is not changed by the flow after the AggregateControl node.

BIP4429
Failed to find a matching control message for a reply message. Queue=<insert_2>, Reason Code=<insert_0>, Correlid=<insert_1>.
Severity
10 : Warning
Explanation
The Aggregation Reply node has matched an incoming reply message to an out going request message but has failed to find a matching control message. This state should never be reached and is probably caused by WebSphere MQ problems. The WebSphere MQ return code was <insert_0> when attempting to get a message with correlid <insert_1> from queue <insert_2>. The reply message has been processed as an unknown message.
Response
Review the current state of the system and try to understand why the control message might be missing. This could be due to another process or person removing contol messages from <insert_2>.

BIP4430
Aggregation control message has a bad format. Queue=<insert_0>, Correlid=<insert_1>.
Severity
20 : Error
Explanation
The Aggregation Reply node has tried to process a control message but it has a corrupt format. The control message is on WebSphere MQ queue <insert_0> and it has Correlid <insert_1>.
Response
If the error persists then remove the control message form the WebSphere MQ queue. By removing the control message all details of the aggregation will be lost.

BIP4431
Failed to store a reply message. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The Aggregation Reply node has tried to store a reply message but has failed. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4432
Storing a aggregation reply message persistently for subsequent processing.
Severity
0 : Information
Explanation
The message has been stored persistently by the AggregateReply node. It will be stored until all replies for the aggregation have returned. Message details: Reply Id = <insert_0>, Reply Protocol = <insert_1>. Reply Group Id = <insert_2>.
Response
No user action required.

BIP4433
Failed to retrieve a reply message. Queue=<insert_0>, Reason Code=<insert_1>.
Severity
20 : Error
Explanation
The Aggregation Reply node has tried to retrieve a reply message but has failed. Failed to get a message from queue <insert_0> because of WebSphere MQ reason code <insert_1>
Response
Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4435
The Aggregation Reply node has received a reply message which has a blank reply ID: <insert_0>.
Severity
20 : Error
Explanation
This is not allowed because the reply ID is needed so that a reply message can be matched to the original request message. If you are using WebSphere MQ to send and receive aggregation requests, the reply ID must be stored in the correlation identifier (CorrelId) field of the message descriptor (MQMD) and it must be set to the value of the message ID in the request message's MQMD.
Response
Make sure that all reply messages have their reply IDs correctly set to match the ID of the request message.

BIP4440
XMLT Transformation requested. The XMLT node has invoked the eXMLT engine to perform a transformation of XML data. The supplied stylesheet name is <insert_1>. The input data is <insert_0>.
Severity
0 : Information
Explanation
The XMLT node has invoked the eXMLT engine to perform a transformation of XML data.
Response
No user action required.

BIP4441
XMLT transformation complete. The eXMLT engine has completed the transformation. Output data is <insert_0>.
Severity
0 : Information
Explanation
The eXMLT engine has completed the transformation. Output data is <insert_0>.
Response
No user action required.

BIP4442
XMLT error <insert_1> reported by XMLT node <insert_0>.
Severity
20 : Error
Explanation
The XMLT node <insert_0> has reported the following error <insert_1>.
Response
Inspect the error text to determine appropriate action

BIP4443
Stylesheet name not found. XMLT node <insert_0> requested a transformation of XML data but the transformation could not be completed because the stylesheet name could not be determined using the given selection priorities. Node attribute priority: <insert_1>. LocalEnvironment priority: <insert_2>. Embedded XML Priority: <insert_3>.
Severity
20 : Error
Explanation
An XMLT node requested a transformation of XML data but the transformation could not be completed because the stylesheet name could not be determined using the given selection priorities. Node attribute priority: <insert_1>. LocalEnvironment priority: <insert_2>. Embedded XML Priority: <insert_3>.
Response
Ensure that the stylesheet name is available.

BIP4444
XMLT warning <insert_1> reported by XMLT node <insert_0>.
Severity
10 : Warning
Explanation
The XMLT node <insert_0> has reported the following warning <insert_1>.
Response
Inspect the warning message to determine appropriate action.

BIP4445
XMLT information message <insert_1> reported by XMLT Node <insert_0>.
Severity
0 : Information
Explanation
The XMLT node <insert_0> has reported the following information message <insert_1>.
Response
No user action required.

BIP4446
XMLT node <insert_0> requested a transformation of XML data but the identified stylesheet, <insert_1>, does not exist.
Severity
20 : Error
Explanation
The transformation could not be completed because the stylesheet could not be found.
Response
Ensure that the identified style sheet is available.

BIP4447
XMLT node <insert_0> encountered a problem during the transformation. The error message is <insert_1>.
Severity
20 : Error
Explanation
The transformation could not be completed.
Response
Check the error message to identify the cause and correct the error.

BIP4448
Found Output CharSet specification <insert_0> from Local Environment (priority <insert_1>).
Severity
0 : Information
Explanation
The XMLT node tried to read Output CharSet specification from Local Environment and got <insert_0>. The specified priority for selecting Local Environment Output CharSet is <insert_1>.
Response
No user action required.

BIP4449
Found Output CharSet specification <insert_0> from Node Attribute (priority <insert_1>).
Severity
0 : Information
Explanation
The XMLT node tried to read Output CharSet specification from Node Attribute and got <insert_0>. The specified priority for selecting Node Attribute Output CharSet is <insert_1>.
Response
No user action required.

BIP4450
No Output CharSet specification was found. Using default Output CharSet <insert_0>.
Severity
0 : Information
Explanation
The XMLT node could not find any Output CharSet specification. The default Output CharSet <insert_0> is therefore to be used.
Response
No user action required.

BIP4451
Found Stylesheet Name specification <insert_0> from Local Environment (priority <insert_1>).
Severity
0 : Information
Explanation
The XMLT node tried to read Stylesheet Name specification from Local Environment and got <insert_0>. The specified priority for selecting Local Environment Stylesheet Name is <insert_1>.
Response
No user action required.

BIP4452
Found Stylesheet Name specification <insert_0> from Node Attribute (priority <insert_1>).
Severity
0 : Information
Explanation
The XMLT node tried to read Stylesheet Name specification from Node Attribute and got <insert_0>. The specified priority for selecting Node Attribute Stylesheet Name is <insert_1>.
Response
No user action required.

BIP4460
Message propagated to out terminal from node <insert_0>.
Severity
0 : Information
Explanation
A pass through node has received a message and is propagating it to any nodes connected to its out terminal.
Response
No user action required.

BIP4500
Failed to deploy Java code resource <insert_0>. The Java stack trace is: <insert_1>
Severity
20 : Error
Explanation
The Java JAR file deployment to the broker failed.
Response
This is an internal error. Contact your IBM support center.

BIP4501
Failed to delete Java code resource <insert_0>.
Severity
20 : Error
Explanation
The Java JAR file failed to be deleted. This file may be locked by the operating system.
Response
Ensure there is sufficient disk space available on the machine running the broker runtime. Stop the broker and delete this file manually.

BIP4502
An unexpected error occurred during the deployment of a Java resource.
Severity
20 : Error
Explanation
An error occurred during the deployment of a Java resource. This may have left the broker in an inconsistent state.
Response
Ensure there is sufficient disk space available on the machine running the broker runtime. Stop the broker, delete all files in <insert_0>, restart the broker and perform a full redeploy.

BIP4503
Failed to deploy Java code resource <insert_0>. An IOException was thrown during deployment. The Java stack trace is: <insert_1>
Severity
20 : Error
Explanation
The Java JAR file deployment to the broker failed.
Response
Ensure there is sufficient disk space available on the machine running the broker runtime.

BIP4504
Failed to deploy Java code resource <insert_0>. A ClassNotFoundException was thrown during deployment. The Java stack trace is: <insert_1>
Severity
20 : Error
Explanation
The Java JAR file deployment to the broker failed.
Response
Ensure all dependencies of the Java code have been deployed to the runtime.

BIP4505
Failed to deploy Java code resource <insert_0>. The Java class deployed to the Java Compute Node must be public and extend MbJavaComputeNode. The Java stack trace is: <insert_1>
Severity
20 : Error
Explanation
The Java JAR file deployment to the broker failed.
Response
The Java Compute Node class implementation must be public and extend MbJavaComputeNode

BIP4506
The attempted deletion of Java resource <insert_0> caused a ClassNotFoundException. Since this resource is still required by the broker it has been restored.
Severity
20 : Error
Explanation
The attempted deletion of the Java resource <insert_0> caused a ClassNotFoundException. The broker still requires the Java resource so it has not be deleted.
Response
No user action required.

BIP4507
A cleared message was propagated.
Severity
20 : Error
Explanation
A node tried to propagate a message that has already been cleared using clearMessage(). Clearing a message releases all resources associated with it, so it can no longer be used.
Response
Modify node code to ensure that no cleared messages are propagated.

BIP4508
Unable to serialize Java exception <insert_0>.
Severity
20 : Error
Explanation
The following exception <insert_1> was thrown when serializing a Java exception. The Java stack trace is: <insert_2> As the serialization failed this exception will not be available in up stream nodes.
Response
If the exception being serialized is a user class, ensure that it is serializable.

BIP4509
Unable to deserialize a Java exception.
Severity
20 : Error
Explanation
The following exception <insert_0> was thrown when deserialize a Java exception. The Java stack trace is: <insert_1> As the deserialization failed this exception will not be available.
Response
Ensure that the node catching the exception has access to the exception class.

BIP4510
Java compute class <insert_0> not found.
Severity
20 : Error
Explanation
The class <insert_0> associated with Java compute node <insert_1> could not be found by the broker.
Response
Ensure that the class <insert_0> has been deployed and is available to the broker.

BIP4511
<insert_0> was thrown while loading Java compute class <insert_1>.
Severity
20 : Error
Explanation
A NoClassDefFoundError was thrown while loading Java compute node class <insert_1>. This means that a class used by <insert_1> could not be found.
Response
Ensure that all the dependencies of <insert_1> have been deployed to the broker.

BIP4512
<insert_1> was thrown while loading Java user-defined node class <insert_0>.
Severity
30 : Severe error
Explanation
The stack trace of the exception is <insert_2>.
Response
Use the exception information to resolve the problem and restart the broker.

BIP4601
The Timeout Control Node <insert_1> failed to navigate to the message location specified. The location specified was: <insert_0>.
Severity
20 : Error
Explanation
Ensure that the Location <insert_0> is valid for the message tree where it is used.
Response
Correct the specified message location.

BIP4602
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout action value.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout action. The request message was correctly navigated to the specified timeout request location, and this location contained an Action element, but the element did not have a valid value. The value contained was <insert_0>.
Response
Supply an Action element, with one of the valid values of SET or CANCEL.

BIP4603
The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout action.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout action. The request message was correctly navigated to the specified timeout request location, but this location did not contain an Action element.
Response
Supply an Action element, with one of the valid values of SET or CANCEL.

BIP4604
The Timeout Control Node <insert_0> received a timeout request that contained an empty timeout identifier.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_0> received a timeout request that contained an empty timeout identifier. The request message was correctly navigated to the specified timeout request location, and this location contained an Identifer element, but the element was empty.
Response
Supply a non-empty Identifier element.

BIP4605
The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout identifier.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout identifier. The request message was correctly navigated to the specified timeout request location, but this location did not contain an Identifier element.
Response
Supply a non-empty Identifier element.

BIP4606
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout start date value.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout start date. The request message was correctly navigated to the specified timeout request location, and this location contained a StartDate element, but the element did not have a valid value. The value contained was <insert_0>.
Response
Ensure the supplied timeout StartDate is not in the past. TODAY is a valid value.

BIP4607
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout start time value.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout start time. The request message was correctly navigated to the specified timeout request location, and this location contained a StartTime element, but the element did not have a valid value. The value contained was <insert_0>.
Response
Ensure the supplied timeout StartTime is not in the past. NOW is a valid value.

BIP4608
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout count value.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout count. The request message was correctly navigated to the specified timeout request location, and this location contained a Count element, but the element did not have a valid value. The value contained was <insert_0>.
Response
Ensure the supplied timeout Count is either -1 (for unlimited) or greater than zero.

BIP4609
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout interval value.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout interval. The request message was correctly navigated to the specified timeout request location, and this location contained an Interval Count element, but the element did not have a valid value. The value contained was <insert_0>.
Response
Ensure the supplied timeout Interval is not less than zero.

BIP4610
The Timeout Control Node <insert_1> received a timeout request that contained an identifier which clashes with an existing timeout request for this node.
Severity
20 : Error
Explanation
The Timeout Control Node <insert_1> received a timeout request that contained an identifier which is already in use for a previous timeout request to this node. The supplied identifier is <insert_0>.
Response
Supply a unique timeout Identifier element. Note also that this error can be avoided by setting AllowOverwrite in future timeout requests to TRUE.

BIP4611
The Timeout Control Node <insert_2> failed to cancel an existing timeout request.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4612
The Timeout Control Node <insert_2> failed to store an incoming timeout request.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4613
The Timeout Control Node <insert_1> received a CANCEL request for an unmatched Identifier.
Severity
20 : Error
Explanation
The supplied timeout CANCEL request contained an Identifier which was unmatched for this node. The Identifier was <insert_0>.
Response
This error occurs when the CANCEL cannot be matched to an existing timeout for this node. The Identifier in the CANCEL request may be incorrect, or the referenced timeout may have expired.

BIP4614
The Timeout Control Node <insert_2> failed to access its internal store.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4615
The Timeout Notification Node <insert_2> failed to delete a non-persistent timeout request.
Severity
10 : Warning
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4616
The Timeout Notification Node <insert_2> failed to delete an overridden timeout request.
Severity
10 : Warning
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4617
The Timeout Notification Node <insert_2> failed to access its internal store.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4618
The Timeout Notification Node <insert_2> failed to get a message from its internal store.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4619
The Timeout Notification Node <insert_0> received a bad timeout request.
Severity
20 : Error
Explanation
The node received a corrupt timeout request message.
Response
This error can occur if the message stored by the corresponding Timeout Control node cannot be un-serialised. It can also occur if non-timeout control node messages have been put on the message store. Correct the incoming data.

BIP4620
The Timeout Notification Node <insert_2> failed to update a message in its internal store.
Severity
20 : Error
Explanation
The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.
Response
correct the reason for the MQ failure.

BIP4621
Exception condition detected on input node: <insert_0>.
Severity
20 : Error
Explanation
Node <insert_0> has detected a failure during message processing. The failure terminal is not attached, so the message flow has been rolled back.
Response
Examine further messages to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.

BIP4622
Exception condition detected on input node <insert_0>.
Severity
20 : Error
Explanation
The input node <insert_0> detected an error whilst processing a message. 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.

BIP4623
Exception condition detected: object label <insert_0>; input node <insert_1>.
Severity
20 : Error
Explanation
An input node detected an error whilst processing a message. The message flow has been rolled back. 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.

BIP4624
Exception condition detected on input node: <insert_0>.
Severity
0 : Information
Explanation
Node <insert_0> has detected a failure during message processing. The message broker is propagating the message to the failure terminal.
Response
Examine further messages to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.

BIP4625
Message propagated to out terminal from node <insert_0>
Severity
0 : Information
Explanation
A TimeoutControl node has received a message and is propagating it to any nodes connected to its out terminal
Response
No user action required

BIP4626
Message propagated to out terminal from node <insert_0>
Severity
0 : Information
Explanation
A TimeoutNotification node is propagating a message to any nodes connected to its out terminal
Response
No user action required

BIP4627
Timeout request set by node <insert_1>
Severity
0 : Information
Explanation
A TimeoutControl node has set a timeout with identifier <insert_0>
Response
No user action required

BIP4628
Timeout request cancelled by node <insert_1>
Severity
0 : Information
Explanation
A TimeoutControl node has cancelled a timeout with identifier <insert_0>
Response
No user action required

BIP4629
Timeout request being processed by node <insert_1>
Severity
0 : Information
Explanation
A TimeoutNotification node is processing a timeout with identifier <insert_0>
Response
No user action required

BIP4630
An MQGET operation was unsuccessful. Completion Code <insert_0>; Reason Code <insert_1>.
Severity
20 : Error
Explanation
An error occurred during a WebSphere MQ MQGET call.
Response
Examine the error codes to determine the cause of the failure.

BIP4631
The MQ Get node <insert_2> failed to navigate to the <insert_1> specified. The location specified was: <insert_0>.
Severity
20 : Error
Explanation
Ensure that the Location <insert_0> is valid for the message tree where it is used.
Response
Check the following exception output, if any, for more details about the problem and correct the specified message location.

BIP4632
MQ Get node <insert_1> was unable to obtain MsgId/CorrelId for message matching from input MQMD location: <insert_0>.
Severity
20 : Error
Explanation
When 'Get by Message ID'/'Get by Correlation ID' node properties are selected, a valid MQMD must be provided in the input message to MQ Get node at the location specified by the 'Input MQMD Location' node attribute.
Response
Examine the 'Get by Message ID'/'Get by Correlation ID' and 'Input MQMD Location' node attributes to ensure that they are correctly specified and the input message to the node has the right structure. Check the following exception output, if any, for more details about the problem.

BIP4633
An error occured whilst performing an MQGet node operation.
Severity
20 : Error
Explanation
N/A.
Response
See the following messages for information pertaining to this error.

BIP4634
The MQ Get node <insert_2> received an configuration message containing an invalid attribute value <insert_1> specified. The location specified was: <insert_0>.
Severity
20 : Error
Explanation
Ensure that the Location <insert_0> is valid for the message tree where it is used.
Response
Check the following exception output, if any, for more details about the problem and correct the specified message location.

BIP4635
The MQ Get node <insert_2> failed to navigate to the default location <insert_0> for <insert_1>.
Severity
0 : Information
Explanation
Location <insert_0> is the default value for <insert_1> and it was not found. It is assumed that this <insert_1> node property is not needed in this case and, therefore, the issue is ignored.
Response
Ignore this message (and the previous user trace message regarding this navigation, if there is one) if this <insert_1> node property is not needed; Otherwise, make sure the location is available or correct the location specification.

BIP4640
WBIMB JMSClient. <insert_0> There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = <insert_1>. Location of the bindings = <insert_2>. ConnectionFactory Name = <insert_3>. JMS destination = <insert_4>. The exception text is : <insert_5>.
Severity
20 : Error
Explanation
The node could not obtain a JNDI Administered Object because some of the values specified in the node attributes are incorrect
Response
Check the JNDI Administered configuration for the JMS provider used by the node. Either modify the JNDI Administered objects and rebuild the bindings, or change the node attributes and re-deploy the message flow.

BIP4641
WBIMB JMSClient.<insert_0> Invalid URL <insert_0> specified for Initial Context Factory <insert_1>.
Severity
20 : Error
Explanation
The Initial Context Factory for the JMS provider could not be found by JNDI at the URL specified.
Response
Check the JNDI Administered objects are located at the URL path specified. If the administered objects are stored using LDAP verify that the correct security credentials (userid and password) have been provided using the mqsichangeproperties command. credentials have been

BIP4642
WBIMB JMSClient.<insert_0> There was JMS Exception while creating <insert_1> Destination. If available the JMS provider return code is <insert_3>.
Severity
20 : Error
Explanation
The Destination supplied in the node attributes ( or JMSReplyTo for a reply message ) could not be created.
Response
Verify that the string supplied for the JMS destination is valid for the JMS Provider, and check that the destination exists.

BIP4643
WBIMB JMSClient.<insert_0>. Error Receiving JMS Message. If Available the text from the JMS Exception is <insert_1>.
Severity
20 : Error
Explanation
The node could not receive a JMS Message because of a JMS Exception on the JMS consumer and session.
Response
Investigate the cause of the JMS exception.

BIP4644
WBIMB JMSClient.<insert_0> Unable to create a JMS Message for output. If available the text from the JMS Exception is <insert_1>.
Severity
0 : Information
Explanation
The node was unable to create a JMS Message because of a JMS Exception.
Response
Investigate the cause of the JMS Exception.

BIP4645
WBIMB JMSClient.<insert_0> The was JMS Exception while creating a JMS Session
Severity
0 : Information
Explanation
The node was unable to establish a JMS Session on the JMS Connection.
Response
Verify that the JMS provider is available, and that sufficient resources have been allocated. destination exists.

BIP4646
WBIMB JMSClient. <insert_0> The format of a JMS Message received by the node is invalid and could not be processed.
Severity
0 : Information
Explanation
The JMS message received by the node is unreadable. The message will be delivered to the failure terminal of the node or rolled back if a fail path is not configured.
Response
Investigate the JMS Message for syntax errors. The message may be found at the destination configured in the failure path of the deployed flow, or the backout destination if sepecified in the node, or it may have been rolled back to the provider.

BIP4647
WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to create a JMS message consumer. If available the JMS Exception text is : <insert_1>
Severity
20 : Error
Explanation
The node was unable to create a JMS message consumer on the JMS session. The JMS provider returned an exception.
Response
Investigate the cause of the JMS Exception. If the problem persist then contact the vendor of the JMS provider.

BIP4648
WBIMB JMSClient.<insert_0> The Connection with the JMS provider was unable to start, or has closed for Initial Conext factory <insert_1> . The node will attempt to re-establish the connection.
Severity
20 : Error
Explanation
The JMS Connection with the JMS provide from this node has stopped. This could be due to the message flow stopping or the connection could have ended abnormally because of a problem with the JMS provider.
Response
If the message flow is not shutting down then the node will attempt to re-connect to the JMS provider. Check that the provider is available.

BIP4649
WBIMB JMSClient.<insert_0> A Connection with the JMS provider has started for Initial Context Factory <insert_1>.
Severity
0 : Information
Explanation
The JMS Connection with the JMS provider has started for this node.
Response
No user action required.

BIP4650
WBIMB JMSClient.<insert_0> Invalid setting for node attribute "Transaction Coordinated" with a non XA-Compliant JMS provider. Initial Context Factory: <insert_1> URL: <insert_2>.
Severity
20 : Error
Explanation
The JMS Provider is not enabled for XA-Compliant transaction coordination .
Response
Modify the node attribute and re-deploy.

BIP4651
WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to send a JMS message . If avaiable the JMS Exception text is : <insert_1>
Severity
20 : Error
Explanation
The node was unable to send a JMS message on the JMS session. The JMS provider returned an exception.
Response
Investigate the cause of the JMS Exception. If the problem persist then contact the vendor of the JMS provider.

BIP4652
WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to acknowledge a JMS message . If avaiable the JMS Exception text is : <insert_1>
Severity
20 : Error
Explanation
The node was unable to acknowledge a JMS message on the JMS session. The JMS provider returned an exception.
Response
Investigate the cause of the JMS Exception. If the problem persists then contact the vendor of the JMS provider.

BIP4653
WBIMB JMSClient. <insert_0> There was an error while attempting to dispatch another instance of the message flow.
Severity
0 : Information
Explanation
The node was unable to dispatch another processing thread for an additional instance of the message flow.
Response
Check the number of instances cnfigured for this message flow. If the problem persists then contact IBM.

BIP4654
WBIMB JMSClient. <insert_0> An error was returned downstream from the Input node. If available the text of the exception is <insert_1>.
Severity
0 : Information
Explanation
The message flow experienced processing errors downstream of the input node, which may have returned an exception.
Response
Investigate the cause of the processing exception.If the problem persists then contact IBM.

BIP4655
WBIMB JMSClient.<insert_0> There was a problem extacting JMS header data from a JMS input message.
Severity
20 : Error
Explanation
The node was unable to obtain header data from the received JMS Message because it was corrupted or badly formed.
Response
Investigate the cause of the badly formed JMS Message.

BIP4656
WBIMB JMSClient.<insert_0> There was a problem extacting JMS properties data from a JMS input message.
Severity
20 : Error
Explanation
The node was unable to obtain property data from the received JMS Message because it was corrupted or badly formed.
Response
Investigate the cause of the badly formed JMS Message.

BIP4657
WBIMB JMSClient. <insert_0> There was a problem extacting the data payload from a JMS input message.
Severity
20 : Error
Explanation
The node was unable to obtain the payload data from the JMS message received. This was because it was either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.
Response
Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4658
WBIMB JMSClient.<insert_0> There was a problem putting JMS header related data to the MbMessage.
Severity
20 : Error
Explanation
The node was unable to write JMS message header data to the MbMessage. This was because it was either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.
Response
Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4659
WBIMB JMSClient. <insert_0> There was a problem putting JMS payload data to the MbMessage.
Severity
20 : Error
Explanation
The node was unable to write JMS message payload data to the MbMessage. This was because it was either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.
Response
Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4660
WBIMB JMSClient.<insert_0> There was a problem extracting JMS header related data from the MbMessage.
Severity
20 : Error
Explanation
The node was unable to extract JMS header related data from the MbMessage because it was badly formed.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4661
WBIMB JMSClient.<insert_0> There was a problem extracting the body data from the MbMessage.
Severity
20 : Error
Explanation
The node was unable to extract data from the MbMessage because it was badly formed.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4662
WBIMB JMSClient. <insert_0> There was a problem setting JMS related header data to the JMS output message.
Severity
20 : Error
Explanation
The node was unable to set header related data to the JMS output message because it was either badly formed or in an unexpected type.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4663
WBIMB JMSClient.<insert_0> There was a problem setting JMS property data to the JMS output message.
Severity
20 : Error
Explanation
The node was unable to set JMS property data to the JMS output message because it was either badly formed or in an unexpected type.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4664
WBIMB JMSClient.<insert_0> There was a problem adding payload data to the JMS output message.
Severity
20 : Error
Explanation
The node was unable to set payload data to the JMS output message because it was either badly formed or in an unexpected type.
Response
If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4665
WBIMB JMSClient.<insert_0>.There was a problem updating MRM related properties values in the MbMessage.
Severity
20 : Error
Explanation
The node was unable to set values for message Set, type or format in the MbMessage. an unexpected type.
Response
If possible, turn on service trace and investigate the format of the data in the JMSType field in the hedaer data of the JMS message.

BIP4666
WBIMB JMSClient.<insert_0> The JMS message recieved by the node was of an unxpected type <insert_1> for message domain <insert_2>.
Severity
20 : Error
Explanation
The node was unable to process the JMS Message because it was an unexpected type for the message domain specified in the node attributes.
Response
Investigate

BIP4667
WBIMB JMSClient.<insert_0> There was an exception during shutdown of the message flow. If available the text from the exception is <insert_1>.
Severity
20 : Error
Explanation
An unxpected error occurred during shutdown of the message flow.
Response
Investigate the cause of the error. If the problem persists then contact IBM.

BIP4668
WBIMB JMSClient.<insert_0> There was an error while attempting to create a JMS message producer.If available the text of the exception is <insert_1>.
Severity
20 : Error
Explanation
The node was unable to create a JMS Message producer because of a JMS exception with the JMS provider.
Response
Investigate the cause of the JMS exception. If the error persists then contact the vendor of the JMS provider.

BIP4669
WBIMB JMSClient.<insert_0> A JMS message was redelivered to the node and a backout destination has not been configured .
Severity
20 : Error
Explanation
The node was unable to process a JMS Message because of errors and could not send it to a backout destination because none was configured.
Response
Investigate the cause of the message failure. Also consider setting a backout destination and threshold for the node

BIP4670
WBIMB The node was unable to read the MQMD from the message.
Severity
20 : Error
Explanation
The node was unable to transform an MQ Message because the MQMD header could not be found or there are errors with the message structure
Response
Check that a correctly formed MQMD header is present in the message.

BIP4671
WBIMB The node was unable to find the body of the message.
Severity
20 : Error
Explanation
The node was unable to transform a message because the body could not be found or there are errors with the message structure
Response
Check that the message body is present in the message, and correctly formed.

BIP4672
WBIMB The node was unable to find a mandatory section of a JMS message.
Severity
20 : Error
Explanation
The node was unable to transform a JMS message because the <insert_0> section could not be found or there are errors with the message structure
Response
Check that the JMS message section has been correctly formed and is present in the message.

BIP4673
WBIMB JMSClient.<insert_0> Error finding local transaction in table for the Provider with Initial Context Factory <insert_1>.
Severity
20 : Error
Explanation
The underlying JMS Connection with the JMS provider has probably failed.
Response
Check the connectivity and availability of the JMS provider.

BIP4674
WBIMB JMSClient.<insert_0> Error committing a transaction for the Provider with Initial Context Factory <insert_1>. The Requesting ID was <insert_2>.
Severity
20 : Error
Explanation
The underlying JMS Connection with the JMS provider has probably failed.
Response
Check the connectivity and availability of the JMS provider.

BIP4675
WBIMB JMSClient.<insert_0> Error rolling back transaction for the Provider with Initial Context Factory <insert_1>. The Requesting ID was <insert_2>.
Severity
20 : Error
Explanation
The underlying JMS Connection with the JMS provider has probably failed.
Response
Check the connectivity and availability of the JMS provider.

BIP4676
WBIMB JMSClient.<insert_0> Error closing JMS Sesssion for the Provider with Initial Context Factory <insert_1>. The Requesting ID was <insert_2>.
Severity
20 : Error
Explanation
The underlying JMS Connection with the JMS provider has probably failed.
Response
Check the connectivity and availability of the JMS provider.

BIP4677
WBIMB JMSClient. <insert_0> The type of JMS Message received by the node is invalid for the message domain <insert_1>.
Severity
20 : Error
Explanation
The JMS Message received by the node is not a valid type for the message domain. The message will be delivered to the failure terminal of the node or rolled back if a fail path is not configured.
Response
Either reconfigure the JMSInput node to change the expected message domain , or modify the value of the JMSType header in the JMS Message. The message may be found at the destination configured in the failure the provider.

BIP4680
Unsupported message domain <insert_0> encountered in mapping node <insert_1>.
Severity
20 : Error
Explanation
This error indicates that ESQL code generated for a mapping node has encountered a message domain that it does not support.
Response
Ensure that the Body subtree of the logical message tree is owned by a message domain that is supported by the Mapping node. The supported domains are ... MRM XML XMLNS XMLNSC JMSMap JMSStream