BIP4000-4999: Runtime components - Built-in message flow nodes
- BIP4001
- Syntax error in SQL statements in node <insert_1>.
- 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_1>.
- Severity
- 20 : Error
- Explanation
- The node <insert_1> would cause a commit of the database transaction on DSN <insert_2>. 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_1> in node <insert_3>. The value returned was <insert_2>.
- 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_1>.
- Severity
- 0 : Information
- BIP4005
- Message propagated to 'false' terminal of filter node <insert_1>.
- Severity
- 0 : Information
- BIP4006
- Message propagated to 'unknown' terminal of filter node <insert_1>.
- Severity
- 0 : Information
- BIP4007
- Message propagated to 'out' terminal of node <insert_1>.
- Severity
- 0 : Information
- BIP4008
- Message propagated to <insert_1> terminal of node <insert_2>.
- Severity
- 0 : Information
- BIP4009
- Invalid terminal identifier <insert_1>.
- 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 ESQL statements, correct them, and redeploy the message flow.
- BIP4010
- Message propagated to label node <insert_1> by node <insert_2>.
- Severity
- 20 : Error
- BIP4011
- Invalid terminal identifier <insert_1>.
- 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_1>, <insert_2>) : 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_1>, around line and column <insert_2>, then redeploy the message flow: Correct the trace pattern and redeploy the message flow.
- BIP4013
- (<insert_1>, <insert_2>) : 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_1>, around line and column <insert_2>, then redeploy the message flow: Correct the trace pattern and redeploy the message flow.
- BIP4014
- <insert_2> : Invalid value <insert_1> 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_1>.
- Response
- Correct the value of the attribute to either 'no' or 'yes'.
- BIP4015
- Message propagated to the 'out' terminal of node <insert_2> with the following message trees: <insert_1>.
- Severity
- 0 : Information
- BIP4016
- Message propagated to terminal <insert_1> of node <insert_3> with the following message trees: <insert_2>.
- Severity
- 0 : Information
- BIP4017
- Message propagated to label node <insert_1> by node <insert_3> with the following message trees: <insert_2>.
- Severity
- 20 : Error
- BIP4018
- When a SELECT is used in an IN predicate, there must only be one column returned. However, a column called <insert_3> was found when a column called <insert_4> was expected. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- In an IN predicate, there must only be one column returned if a SELECT is used.
- Response
- Look for other messages that give an indication of the context of this error.
- BIP4019
- Error decoding (converting) the base64 character string <insert_3> to a BLOB. State = <insert_1> <insert_2> '0' '.
- Severity
- 20 : Error
- Explanation
- An attempt was made to decode (convert) a base64 encoded string into a BLOB. Possible reasons for this are that it is the wrong length (not a multiple of 4) or that it contains characters that are invalid in a base64 encoded string. The point in the string at which the error was detected was <insert_4> (-1 means invalid length). The data decoded upto this point (if any) was <insert_5>. The full length of the source string was <insert_6>, and <insert_7> whitespace characters were found and ignored before the error point was reached.
- Response
- Look for other messages that give an indication of the context of this error.
- BIP4020
- NeonRules node <insert_2> received an invalid message with the following parts: <insert_1>.
- 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_1>.
- 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_5>&colon. Rules evaluation failed. Message details&colon. application group <insert_1>; message type <insert_2>; rules error # <insert_3>; rules error message <insert_4>.
- Severity
- 20 : Error
- Explanation
- Details of the message and the error raised whilst processing the message by the
eon. rules processor are&colon.-
- Response
- Further details of the error message and corrective actions can be found in the
eon. manuals.
- BIP4022
- Node <insert_3>: Rules evaluation succeeded: application group <insert_1>; message type <insert_2>.
- Severity
- 0 : Information
- Explanation
- Application group: <insert_1>, Message type: <insert_2>.
- Response
- No user action required.
- BIP4023
- <insert_5>: Unknown action detected. Message details: application group <insert_1>; message type <insert_2>; action name <insert_3>; subscription ID <insert_4>.
- 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
- Response
- Correct the
eon. rules to ensure that the resultant actions are supported by IBM Integration Bus.
- BIP4024
- Node <insert_3>: The rules evaluation yielded a subscription. Message details: application group <insert_1>; message type <insert_2>.
- Severity
- 0 : Information
- Explanation
- Application group: <insert_1>, Message type: <insert_2>.
- Response
- No user action required.
- BIP4025
- Node <insert_3>: No subscriptions found. Message details: application group <insert_1>; message type <insert_2>.
- Severity
- 0 : Information
- Explanation
- Application group: <insert_1>, Message type: <insert_2>.
- 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_3>: Performing a reformat operation. Message details: input message type <insert_1>; output message type <insert_2>.
- Severity
- 0 : Information
- Explanation
- Input Message Type: <insert_1>, Output Message Type: <insert_2>.
- Response
- No user action required.
- BIP4028
- Failed to reformat message. Message details: input message type <insert_1>; output message type <insert_2>; formatter error number <insert_3>; formatter error message <insert_4>.
- Severity
- 20 : Error
- Explanation
- Details of the message and the error raised whilst formatting the message by the
eon. formatter are:-
- Response
- Further details of the error message and corrective actions can be found in the
eon. manuals.
- BIP4029
- Node <insert_3>: Reformat completed successfully. Message details: input message type <insert_1>; output message type <insert_2>.
- Severity
- 0 : Information
- Explanation
- Input Message Type: <insert_1>, Output Message Type: <insert_2>.
- Response
- No user action required.
- BIP4030
- Target queue not set for putqueue action.
- Severity
- 20 : Error
- Explanation
- The
eon. 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
eon. rules to ensure that the action is correctly specified.
- BIP4031
- Output type not set for reformat.
- Severity
- 20 : Error
- Explanation
- The
eon. rules processor has evaluated a message with a reformat action, but has not specified an output type for the message.
- Response
- Correct the
eon. rules to ensure that the action is correctly specified. The
eon. publications give details of the correct specification of the actions.
- BIP4032
- Input type not set for reformat.
- Severity
- 20 : Error
- Explanation
- The
eon. rules processor has evaluated a message with a reformat action, but has not specified an input type for the message.
- Response
- Correct the
eon. rules to ensure that the action is correctly specified. The
eon. 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
eon. 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
eon. rules to ensure that the action is correctly specified. The
eon. publications give details of the correct specification of the actions.
- BIP4036
- Node <insert_8>: Performing a putqueue action. Options: OPT_TARGET_QUEUE <insert_1>; OPT_APP_GRP <insert_2>; OPT_MSG_TYPE <insert_3>; MQS_FORMAT <insert_4>; MQS_EXPIRY <insert_5>; MQS_PERSIST <insert_6>; MQS_PROPAGATE <insert_7>.
- Severity
- 0 : Information
- Explanation
- The putqueue options are listed above.
- Response
- No user action required.
- BIP4037
- Node <insert_8>: Performing a propagate action. Options: OPT_APP_GRP <insert_2>; OPT_MSG_TYPE <insert_3>; MQS_FORMAT <insert_4>; MQS_EXPIRY <insert_5>; MQS_PERSIST <insert_6>; MQS_PROPAGATE <insert_7>.
- Severity
- 0 : Information
- Explanation
- The propagate options are listed above.
- Response
- No user action required.
- BIP4038
- <insert_1>: The 'targetFormat' attribute cannot be empty.
- Severity
- 20 : Error
- Explanation
- The targetFormat attribute must specify a valid
eon. output format as the target of the format operation. It cannot be the empty string.
- Response
- Use the Integration Toolkit to set the value of the targetFormat attribute to the correct value and redeploy the message flow.
- BIP4039
- The NeonFormatter node <insert_2> received an invalid message, body type <insert_1>.
- 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_1>.
- 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 integration server <insert_1> 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
- Integration server <insert_1> received an administration request that encountered an exception.
- Severity
- 20 : Error
- Explanation
- While attempting to process an administration request, an exception was encountered. No updates have been made to the configuration of the integration server.
- Response
- Review related error messages to determine why the administration request failed.
- BIP4042
- Invalid action <insert_1> in configuration message.
- Severity
- 20 : Error
- Explanation
- The integration node received a configuration message containing the invalid action <insert_1>. This error can only result from configuration messages having an invalid structure.
- Response
- Ensure that no applications are writing to the integration node's configuration queues.
- BIP4043
- Invalid action <insert_1> on resource <insert_2> in configuration message.
- Severity
- 20 : Error
- Explanation
- The integration node received a configuration message which attempted the action <insert_1> on the resource <insert_2> 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 integration node 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 integration node's persistent state is operating correctly then stop and restart the integration node.
- BIP4045
- Configuration changed successfully.
- Severity
- 0 : Information
- Explanation
- The integration node received a configuration message and updated its configuration accordingly. This change concerned its publish-subscribe capability.
- Response
- No user action required.
- BIP4047
- Invalid body type <insert_1> in configuration message.
- Severity
- 20 : Error
- Explanation
- The integration node received a configuration message containing the invalid body type <insert_1>. This error can only result from configuration messages having an invalid structure.
- Response
- Ensure that no applications are writing to the integration node's configuration queue.
- BIP4048
- The integration server has received a request to stop.
- Severity
- 0 : Information
- Explanation
- The integration server 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_1> in label node.
- Severity
- 20 : Error
- Explanation
- Two label nodes within a message flow have been found to have the same labelName attribute <insert_1>.
- 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_1> could not be found.
- Severity
- 20 : Error
- Explanation
- A Label node with Label Name attribute of <insert_1> 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_1> with a type of <insert_2> and a value of <insert_3>. Recoverable Exception information <insert_4>.
- Severity
- 20 : Error
- Explanation
- The User Defined Attribute <insert_1> could not be created. The type <insert_2> or the value <insert_3> might be invalid. Refer to the Exception information <insert_4> for further information.
- Response
- A deploy message sent to this integration node contains an invalid User Defined Attribute. Correct the User Defined Attribute and redeploy.
- BIP4053
- Attempt to create an existing User Defined Attribute <insert_1>.
- Severity
- 20 : Error
- Explanation
- The User Defined Attribute <insert_1> already exists
- Response
- A deploy message sent to this integration node contains a message to create an existing User Defined Attribute.
- BIP4054
- User Defined Attribute <insert_1> does not exist.
- Severity
- 20 : Error
- Explanation
- The User Defined Attribute <insert_1> can not be reported or changed as it does not exist
- Response
- Correct the request for this User Defined Attribute.
- BIP4055
- (<insert_1>, <insert_2>) : 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_1>.
- Severity
- 20 : Error
- Explanation
- Internal error during type conversion.
- Response
- See previous messages for more details.
- BIP4057
- The value of user-defined property <insert_4> defined on message flow <insert_3> (integration server <insert_2> of integration node <insert_1>) has been changed from <insert_5> to <insert_6>.
- Severity
- 0 : Information
- Explanation
- A configuration request was received by the integration node to change the value of the user-defined property.
- Response
- None.
- BIP4060
- Data <insert_1> from trace node <insert_2>.
- Severity
- 0 : Information
- Explanation
- The trace node <insert_2> 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_1>.
- Severity
- 10 : Warning
- Explanation
- The trace node <insert_1> 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 integration node.
- BIP4062
- Node (class=<insert_1> name=<insert_2>) 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 integration node.
- BIP4063
- Node (class=<insert_1>, name=<insert_2>) 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 integration node.
- BIP4064
- Operating system error <insert_2> opening trace file <insert_1> for trace node <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The trace node <insert_3> attempted to open the trace file <insert_1> but the operating system reported the error <insert_2>. 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 integration node. 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_2> attempting to write to trace file <insert_1> for trace node <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The trace node <insert_3> attempted write to open the trace file <insert_1> but the operating system reported the error <insert_2>. 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_1>.
- Severity
- 10 : Warning
- Explanation
- The trace node <insert_1> 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_1>.
- Severity
- 0 : Information
- Explanation
- The trace node <insert_1> has received a message and is propagating it to any nodes connected to its output terminal.
- Response
- No user action required.
- BIP4068
- Cannot change complex attribute of UUID <insert_1>; valid UUIDs are in (<insert_2>)
- Severity
- 20 : Error
- Explanation
- Only certain complex attributes with UUIDs in (<insert_2>) can be modified through the mqsichangeflowmonitoring command. To change other complex attributes, redeploy the flow.
- Response
- Correct the spelling if the UUID is misspelled, or redeploy the flow with an updated attribute.
- BIP4069
- The event source with address <insert_1> for node <insert_2> is not valid.
- Severity
- 20 : Error
- Explanation
- The node exists, but the event source was not found.
- Response
- Use one of the following methods to check that the event exists in the node:
Use the message flow editor.
Use the 'mqsireportflowmonitoring' command, with the '-n' option. Only event sources that are in the returned list can be enabled or disabled.
- BIP4070
- MbTable row for complex attribute <insert_1> is badly-formed; element <insert_2> is not valid
- Severity
- 20 : Error
- Explanation
- The element <insert_2> is not valid for complex attributes of UUID <insert_1>.
- Response
- Either correct the name or remove the element.
- BIP4071
- An error was encountered while loading monitoring profile <insert_1> for use by message flow <insert_2>
- Severity
- 20 : Error
- Explanation
- The message flow could not parse the monitoring profile.
The XML in the monitoring profile is not well-formed, or it does not conform to the monitoring profile schema.
- Response
- Correct the XML in the monitoring profile and update the configurable service.
- BIP4072
- A query expression which should have produced a boolean result has been evaluated, but it did not produce a boolean result. The returned value <insert_1> was treated as <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The expression should return a boolean value. This expression did not return a boolean value, but it was interpreted as a boolean by the message flow and the value shown was used.
- Response
- Check that you have specified the expression correctly.
Consider changing the expression so that it always returns a boolean value.
- BIP4073
- A query expression which should have produced a boolean result has been evaluated, but it did not produce a boolean result. The result was interpreted as 'false'.
- Severity
- 10 : Warning
- Explanation
- The expression should return a boolean value. This expression did not return a boolean value. It was not possible to convert the value to a boolean, so it was interpreted as 'false'.
- Response
- Check that you have specified the query expression correctly.
Change the query expression so that it always returns a Boolean value.
- BIP4074
- The event filter on the event emitted by event source <insert_1> in flow <insert_2> has been evaluated and returned <insert_3>. The query text was <insert_4>.
- Severity
- 0 : Information
- Explanation
- The event filter, which controls whether an event is emitted, has been evaluated for event source <insert_1> in flow <insert_2>.
The result of the evaluation was <insert_3>.
The query text evaluated was <insert_4>.
- Response
- No action is required. This message is for information.
- BIP4075
- A message was issued during the evaluation of the event filter expression on the event emitted by event source <insert_1> in flow <insert_2>. See the previous message for details.
- Severity
- 10 : Warning
- Explanation
- The event filter, which controls whether an event is emitted, has been evaluated for event source <insert_1> in flow <insert_2>.
A message was issued while this expression was being evaluated. See the previous message for details.
- Response
- See the previous message and take any corrective action that may be necessary.
- BIP4076
- Message flow <insert_2> successfully loaded monitoring profile <insert_1>.
- Severity
- 0 : Information
- Explanation
- The message flow successfully loaded a monitoring profile.
- Response
- No user action is required.
- BIP4077
- Integration node event published on topic <insert_1> using the <insert_2> transport.
- Severity
- 0 : Information
- Explanation
- An integration node event has been published on the given topic and transport.
- Response
- No user action required.
- BIP4078
- An error occurred publishing integration node event on topic <insert_1> using the <insert_2> transport.
- Severity
- 20 : Error
- Explanation
- The integration node was unable to publish an event on the topic due to an unexpected error. The cause of this failure is specified in the message or message that follow.
- Response
- Ensure that the configuration of the transport used to publish the event is correct, and that the transport is available.
- BIP4079
- An error occurred loading the policy document for the <insert_1> event group and <insert_2> transport from location <insert_3>.
- Severity
- 20 : Error
- Explanation
- The integration node was unable to load the policy document configured for event publication for event group <insert_1> and transport <insert_2> from the location specified in the URL <insert_3>. The cause of this failure is specified in the message or message that follow.
- Response
- Ensure that the policy URL which is configured for the event group and transport is correct and refers to a valid endpoint for the transport.
- BIP4080
- Message propagated to try terminal from try-catch node <insert_1>.
- Severity
- 0 : Information
- Explanation
- The try-catch node <insert_1> 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_1>.
- Severity
- 0 : Information
- Explanation
- The try-catch node <insert_1> 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.
- BIP4089
- An error occurred registering a web socket subscription for topic <insert_1>.
- Severity
- 20 : Error
- Explanation
- The integration node was unable register a web socket subscription for topic <insert_1> because the topic root is invalid. The topic root must start with the product topic root, followed by the integration node name and event type identifier. For example IBM/IntegrationBus/IB10NODE/Status
- Response
- Correct the topic. Topics can include wildcards, but wildcards must be specified in the topic after the product topic root, integration node name, and event type identifier. A single wildcard subscription to more than one integration node or event type is not supported.
- BIP4101
- Exception thrown by throw node <insert_1>.
- Severity
- 0 : Information
- Explanation
- The throw node <insert_1> 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_1> in message flow <insert_2>.
- Severity
- 20 : Error
- Explanation
- The compute node <insert_1> in message flow <insert_2> 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_3>.
- Severity
- 20 : Error
- Explanation
- The configuration of compute node <insert_3> failed due to errors in the SQL expression. See the following messages for details of the error. The statement text was <insert_2>.
- 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 IBM Integration Bus publications. Correct the statements configuring the node and redeploy the configuration.
- BIP4123
- Incorrect return type <insert_1> in compute node <insert_3>. The value returned was <insert_2>.
- 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_1>.
- Severity
- 0 : Information
- BIP4125
- Failed to load ESQL file <insert_1>.
- Severity
- 20 : Error
- Explanation
- See previous messages for the cause of the failure.
- Response
- If the problem persists, remove the ESQL file that failed to load and then redeploy all artifacts.
- BIP4126
- Failed to delete ESQL file <insert_1> because it no longer exists.
- Severity
- 10 : Warning
- Explanation
- The file was not deleted because it no longer exists.
- Response
- No action is required. The named ESQL file was already deleted, and attempting to delete the file again has caused no additional problems.
- BIP4127
- Failed to find ESQL module <insert_1>.
- Severity
- 20 : Error
- Explanation
- The module that is required for the ESQL node cannot be found.
- Response
- Make sure that the required ESQL module is deployed.
- BIP4128
- Failed to deploy ESQL <insert_1> called <insert_2> contained in <insert_3> because it is already deployed in file <insert_4>.
- Severity
- 20 : Error
- Explanation
- The ESQL component has already been deployed in a different ESQL file.
- Response
- Ensure that each ESQL module, routine or declare statement is declared in only one ESQL file.
- BIP4129
- The ESQL file <insert_1> in shared library <insert_2> cannot be deployed because it is in the default integration node schema.
- Severity
- 20 : Error
- Explanation
- ESQL files in shared libraries cannot be in the default integration node schema.
- Response
- Modify the shared library <insert_1> so that none of its ESQL files are in the default integration node schema. All the ESQL files must contain a BROKER SCHEMA statement that specifies a valid integration node schema.
- BIP4130
- One or more ESQL files in shared library <insert_1> are in the default integration node schema.
- Severity
- 20 : Error
- Explanation
- ESQL files in shared libraries cannot be in the default integration node schema.
- Response
- Modify the shared library <insert_1> so that none of its ESQL files are in the default integration node schema. All the ESQL files must contain a BROKER SCHEMA statement that specifies a valid integration node schema.
- BIP4131
- The application <insert_1> is trying to use ESQL files from shared library <insert_2>. However, shared library <insert_2> has ESQL files in the integration node schema <insert_3>, which is already defined by ESQL files in application <insert_1>.
- Severity
- 20 : Error
- Explanation
- When an application is referencing shared libraries, all the ESQL files for an integration node schema must be in a single container.
ESQL files for an integration node schema must not be in both an application and a shared library that is referenced by that application.
Additionally, ESQL files for an integration node schema must not be in two or more shared libraries that are referenced by a single application.
- Response
- Move all the ESQL files in the integration node schema <insert_3> into the application <insert_1>.
Alternatively, move all the ESQL files in the integration node schema <insert_3> into one of the shared libraries that are referenced by application <insert_1>.
- BIP4132
- The application <insert_1> is trying to use ESQL files from shared library <insert_2>. However, shared library <insert_2> has ESQL files in the integration node schema <insert_3>, which is already defined by ESQL files in shared library <insert_4>.
- Severity
- 20 : Error
- Explanation
- When an application is referencing shared libraries, all the ESQL files for an integration node schema must be in a single container.
ESQL files for an integration node schema must not be in both an application and a shared library that is referenced by that application.
Additionally, ESQL files for an integration node schema must not be in two or more shared libraries that are referenced by a single application.
- Response
- Move all the ESQL files in the integration node schema <insert_3> into the application <insert_1>.
Alternatively, move all the ESQL files in the integration node schema <insert_3> into one of the shared libraries that are referenced by application <insert_1>.
- BIP4133
- The shared library <insert_1> is trying to use ESQL files from shared library <insert_2>. However, shared library <insert_2> has ESQL files in the integration node schema <insert_3>, which is already defined by ESQL files in shared library <insert_4>.
- Severity
- 20 : Error
- Explanation
- When a a shared library is referencing other shared libraries, all the ESQL files for an integration node schema must be in a single container.
ESQL files for an integration node schema must not be in both an application or shared library and a shared library that is referenced by that application or shared library.
Additionally, ESQL files for an integration node schema must not be in two or more shared libraries that are referenced by a single application or shared library.
- Response
- Move all the ESQL files in the integration node schema <insert_3> into the shared library <insert_1>.
Alternatively, move all the ESQL files in the integration node schema <insert_3> into one of the shared libraries that are referenced by shared library <insert_1>.
- BIP4140
- Exception condition detected by user-defined node <insert_1>.
- Severity
- 0 : Information
- Explanation
- The user-defined node <insert_1> 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_7>. Arguments: type <insert_1>; file <insert_2>; line <insert_3>; function <insert_4>; messageNumber <insert_5>; traceText <insert_6>.
- Severity
- 20 : Error
- Explanation
- The user-defined node or parser <insert_7> 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_1>. Changing value from <insert_2> to <insert_3>.
- Severity
- 0 : Information
- Explanation
- Element <insert_1> has been changed to <insert_3>.
- 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_1>(<insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>).
- Severity
- 0 : Information
- Explanation
- Entered the specified function with the specified parameters.
- Response
- No user action required.
- BIP4145
- Exiting function <insert_1> with result: <insert_2>(<insert_3>).
- Severity
- 0 : Information
- Explanation
- About to exit the specified the function with the specified result.
- Response
- No user action required.
- BIP4146
- Evaluating cpiSetElement<insert_1>. Changing value from <insert_2> to <insert_3>.
- Severity
- 0 : Information
- Explanation
- Element <insert_1> has been changed to <insert_3>.
- Response
- No user action required.
- BIP4147
- User-defined extension input parameter failed debug validation check.
- Severity
- 20 : Error
- Explanation
- Input parameter <insert_2> passed into function <insert_1> is not a valid object.
- Response
- Correct user-defined extension implementation accordingly.
- BIP4148
- User-defined extension damaged integration node's object.
- Severity
- 20 : Error
- Explanation
- Function <insert_1> has damaged integration node's object passed as parameter <insert_2>.
- Response
- Correct user-defined extension implementation accordingly.
- BIP4149
- User-defined extension input parameter failed debug validation check.
- Severity
- 20 : Error
- Explanation
- Input parameter <insert_2> passed into function <insert_1> 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_2> passed into function <insert_1> 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_1>.
- Severity
- 20 : Error
- Explanation
- The implementation function returned <insert_2> but the expected values are <insert_3>.
- Response
- Correct user-defined extension implementation accordingly.
- BIP4152
- User-defined extension Implementation function <insert_1> returned CCI_BUFFER_TOO_SMALL on 2nd attempt.
- Severity
- 20 : Error
- Explanation
- The implementation function <insert_1> has set the returnCode output parameter to CCI_BUFFER_TOO_SMALL and returned <insert_2> 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_1> has an invalid data type <insert_2>.
- Severity
- 20 : Error
- Explanation
- The datatype <insert_2> is not supported as a UDP. This can be due to using versions of runtime components that are incompatible with your Integration Toolkit.
- Response
- Make sure that you are using versions of runtime components that are compatible with your Integration Toolkit.
- BIP4154
- The user-defined property (UDP) <insert_1> of datatype <insert_2> has an incorrect structure. Reason: <insert_3>3
- Severity
- 20 : Error
- Explanation
- An internal problem has occurred trying to construct the datatype <insert_2>. This can be due to using versions of runtime components that are incompatible with your Integration Toolkit.
- Response
- Make sure that you are using versions of runtime components that are compatible with your Integration Toolkit.
- BIP4155
- A dynamic terminal called <insert_2> (of type <insert_1>) could not be created because there is already a terminal with that name.
- Severity
- 20 : Error
- Explanation
- The message flow definition deployed to the integration node 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 integration node's Toolkit.
- Response
- Make sure that you are using versions of runtime components that are compatible with your integration node's Toolkit.
- BIP4156
- A dynamic terminal of type <insert_1> (called <insert_2>) 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_1> could not be deployed. Details: <insert_2>2
- 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
- A message was propagated to the Match terminal by Validate node or Check node <insert_1>.
- Severity
- 0 : Information
- Explanation
- The Validate node or Check node <insert_1> has matched a received message against the criteria and is propagating it to any nodes that are connected to its Match terminal.
- Response
- No user action is required.
- BIP4161
- A message was propagated to the failure terminal by Validate node or Check node <insert_7>. Expected values: domain <insert_4>; set <insert_5>; type <insert_6>. Actual values received: domain <insert_1>; set <insert_2>; type <insert_3>.
- Severity
- 20 : Error
- Explanation
- The Validate node or Check node <insert_7> detected that a message was received that did not meet the specified criteria, and that a message flow processing node is attached to its failure terminal. As a result, the message is being propagated to any nodes that are connected to that terminal.
- BIP4162
- A non-matching message has been rejected by Validate node or Check node <insert_7>. Expected values: domain <insert_4>; set <insert_5>; type <insert_6>. Actual values received: domain <insert_1>; set <insert_2>; type <insert_3>.
- Severity
- 20 : Error
- Explanation
- The Validate node or Check node <insert_7> detected that the input message did not meet the specified criteria, and that a message flow processing node is not attached to its failure terminal. An exception has been generated.
- Response
- Identify the reason why invalid messages are being generated or sent into the integration node, and correct the problem. Ensure that you have specified the properties of the Validate node or Check node correctly, and redeploy the message flow.
- BIP4163
- Message propagated to the first terminal of the FlowOrder node <insert_1>.
- 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_1>.
- 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_1>.
- Severity
- 0 : Information
- Explanation
- The database node <insert_1> 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_3>.
- Severity
- 20 : Error
- Explanation
- The configuration of database node <insert_3> failed due to errors in the SQL statement text. See the following messages for details of the error. The statement text was <insert_2>.
- 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 IBM Integration Bus publications. Correct the statements and redeploy the configuration.
- BIP4183
- Incorrect return type <insert_1> in database node <insert_3>. The value returned was <insert_2>.
- 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_1>.
- Severity
- 0 : Information
- BIP4185
- Failed to delete file <insert_1> because node <insert_2> is using ESQL module <insert_3> contained with in it.
- Severity
- 20 : Error
- Explanation
- You cannot delete a file if it contains one or more ESQL modules that are in use.
- Response
- To delete the file, first ensure that no message flows are using any ESQL module that is contained within the file, then try to delete the file again.
- BIP4186
- Failed to call ESQL routine <insert_1> because the incorrect number of parameters was supplied. <insert_2> parameters were supplied but <insert_3> parameters were expected.
- Severity
- 20 : Error
- Explanation
- The incorrect number of parameters was supplied for a call to an ESQL routine.
- Response
- Ensure that the correct number of parameters are supplied to call the ESQL routine.
- BIP4187
- Failed to call ESQL routine <insert_1> because parameter number <insert_2> (the first parameter is number 1) is not of the correct type.
- Severity
- 20 : Error
- Explanation
- All parameters that are supplied in the ESQL function call must be of the correct type.
- Response
- Ensure that the paramaters are of the correct type to call the ESQL routine.
- BIP4188
- Failed to call ESQL routine <insert_1> because it has not been deployed.
- Severity
- 20 : Error
- Explanation
- The specified ESQL routine does not exist within the application or integration server that the message flow is running in.
- Response
- Ensure that the correct ESQL routine is deployed.
- BIP4189
- An attempt was made to delete file <insert_1> which contains ESQL module <insert_2> that is required by node <insert_3> in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- An ESQL module cannot be deleted if it is required by a node that is currently deployed.
- Response
- Ensure that the ESQL module is not required by any nodes that are currently deployed.
- BIP4190
- ESQL routine <insert_1> has been resolved to two schemas found in the PATH statement: <insert_2> and <insert_3>.
- Severity
- 20 : Error
- Explanation
- When using the schema PATH clause to resolve your ESQL routines, ensure that only one ESQL routine can be resolved.
- Response
- Ensure that the ESQL routine name is not contained in more than one schema that is referenced in the path clause. If the ESQL routine name is contained in more than one schema that is referenced in the path clause, you must fully qualify the ESQL routine name to specify the schema name of the ESQL routine that you want to call.
- BIP4191
- The ESQL module named <insert_1> is of type <insert_2> but an ESQL module of type <insert_3> is required.
- Severity
- 20 : Error
- Explanation
- Each type of ESQL node requires a particular type of ESQL module to function correctly.
- Response
- Ensure that the required ESQL module is of the correct type.
- BIP4192
- ESQL file <insert_1> is not a valid UTF-8 file.
- Severity
- 20 : Error
- Explanation
- ESQL files must be in code page 1208 to be deployed as separate artifacts. See other exceptions for details of what is invalid.
- Response
- Ensure that the ESQL file is in UTF-8.
- BIP4201
- Message propagated to out terminal from node <insert_1>.
- 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_1>.
- 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 integration node.
- 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_1> failed to bind to port <insert_2>2
- 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 integration node 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 integration node.
- BIP4240
- RouteToLabel node <insert_2> unable to locate Label node <insert_1>.
- Severity
- 20 : Error
- Explanation
- A RouteToLabel node received a message that contains a label, but no Label node has this label.
- Response
- Possible causes of this error are as follows: (a) The input message is not as expected. (b) The logic of the message flow, which does not calculate a valid Label node name for all valid input messages. (c) Errors in deployment. Check that the input message is as expected. Then check the logic of the message flow, to ensure that in all cases the calculated Label node names are correct. Finally ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker, using the complete configuration option. If the problem persists, contact your IBM Support Center.
- BIP4241
- Message propagated to target Label node by RouteToLabel node <insert_1>.
- 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_4> queue manager <insert_1>, queue <insert_2>, from node type <insert_3>3
- Severity
- 20 : Error
- Explanation
- IBM Integration Bus 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_1> received from <insert_2> for node type <insert_3>3
- Severity
- 20 : Error
- Explanation
- An internal error occurred in communication within IBM Integration Bus.
- Response
- Your installation of IBM Integration Bus 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
- IBM Everyplace JNI initialization failure
- Severity
- 30 : Severe error
- Explanation
- A node is unable to communicate with IBM Everyplace using the JNI.
- Response
- Check that the Java code in the CLASSPATH used by IBM Integration Bus 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_1>1
- 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 integration node. 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 integration node 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.
- BIP4251
- The SCADAInput node <insert_1> is no longer supported in IBM Integration Bus.
- Severity
- 20 : Error
- Explanation
- A SCADAInput node has been deployed to the integration node. The node will not work because SCADA function is no longer supported.
- Response
- Remove all SCADA nodes from this message flow, then redeploy the message flow.
- BIP4252
- The SCADAOutput node <insert_1> is no longer supported in IBM Integration Bus.
- Severity
- 20 : Error
- Explanation
- A message has been propagated to a SCADAOutput node. The node will not work because SCADA function is no longer supported.
- Response
- Remove all SCADA nodes from this message flow, then redeploy the message flow.
- BIP4253
- The MQeInput node <insert_1> is no longer supported in IBM Integration Bus.
- Severity
- 20 : Error
- Explanation
- An MQeInput node has been deployed to the integration node. The node will not work because MQe function is no longer supported.
- Response
- Remove all MQe nodes from this message flow, replace them with the appropriate MQ nodes, and redeploy the message flow.
See the IBM Integration Bus information center for the current release of the product for further information.
- BIP4254
- The MQeOutput node <insert_1> is no longer supported in IBM Integration Bus.
- Severity
- 20 : Error
- Explanation
- A message has been propagated to an MQeOutput node. The node will not work because MQe function is no longer supported.
- Response
- Remove all MQe nodes from this message flow, replace them with the appropriate MQ nodes, and redeploy the message flow.
See the IBM Integration Bus information center for the current release of the product for further information.
- BIP4256
- The RouteToLabel node <insert_2> was unable to locate a 'labelName' element in the local environment.
- Severity
- 20 : Error
- Explanation
- The specified RouteToLabel node has received a message, but no 'labelName' element exists in the local environment of the message. The RouteToLabel node cannot continue without at least one valid 'labelName' element.
- Response
- Ensure that the local environment in the message contains at least one 'labelName' element. The RouteToLabel node looks for a valid 'labelName' element in the path: 'LocalEnvironment.Destination.RouterList.DestinationData.labelName'.
If you have created the 'labelName' element in the OutputLocalEnvironment of an ESQL Compute node, ensure that the ESQL Compute node has a compute mode setting that includes 'LocalEnvironment'.
- 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 integration node 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 integration node 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 integration node 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 Integration Toolkit debugger might not work properly.
- Response
- Restart your integration node 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 integration node 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 integration node 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 integration node 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 integration node 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 integration node, 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 Integration Toolkit.
- Response
- Restart your integration node, 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 integration node, 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 integration node, 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 an Integration Toolkit socket.
- Response
- Restart your integration node, restart your Integration 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 Integration Toolkit.
- Response
- Restart your integration node, 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 integration node, 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 integration node, 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 integration node 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.
- BIP4305
- An error occurred during the configuration of decision services in the directory <insert_1> (application <insert_2>, library <insert_3>).
- Severity
- 20 : Error
- Explanation
- The deployment or deletion of a decision service caused an error.
- Response
- Review further error messages for an indication to the cause of the errors.
- BIP4306
- The decision service <insert_1> cannot be created because schema <insert_2> is missing.
- Severity
- 20 : Error
- Explanation
- When a decision service is created in the Integration Toolkit, the parameters are based on schema types. The schema files that define these schema types need to be available to the decision service. Schema file <insert_2> is missing.
- Response
- Include the missing schema in the scope of the decision service. For example, if the decision service is contained in an application, ensure that the schema is available in the application or in an associated library.
- BIP4307
- The decision service <insert_1> cannot be created because an exception occurred.
The exception is <insert_2>.
The exception stack trace is <insert_3>.
- Severity
- 20 : Error
- Explanation
- When a decision service is deployed it is compiled into rulesets. An exception occurred during this compilation.
- Response
- Review previous errors and ensure that all dependencies have been included for the decision service.
- BIP4308
- The Decision Service node supports the XMLNSC and DFDL domains only; however, the inbound message has a domain of <insert_1>
- Severity
- 20 : Error
- Explanation
- The Decision Service node uses the content of the inbound message during the execution of the decision service. XMLNSC and DFDL are the only supported domains; however, the message that arrived at the input terminal has a domain of <insert_1>.
- Response
- Use one of the transformation nodes to change the message domain from <insert_1> to the XMLNSC or DFDL domain.
- BIP4309
- The DecisionService node <insert_1> in message flow <insert_2> cannot find the required file <insert_5> that is used by decision service <insert_6>.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) is configured to use decision service <insert_6>. The decision service <insert_6> has an associated compiled <insert_5> file. This compiled file cannot be located.
- Response
- Redeploy the decision service.
- BIP4310
- The DecisionService node <insert_1> in message flow <insert_2> detected an exception when it used decision service <insert_5>.
The exception is <insert_6>.
The exception stack trace is <insert_7>.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) is configured to use decision service <insert_5>. Processing the input parameter data against this decision service caused the exception.
- Response
- Check that the decision service definitions are consistent. Check that the input parameter data is correct. Check that the parameter XPath expressions are correct.
- BIP4311
- An MQTT Publish using <insert_1> detected an exception when it was attempting to publish to topic <insert_2> using server connection <insert_3>, Client id <insert_4>, Security identity username <insert_7> and Security identity <insert_8>.
The exception is <insert_5>.
The exception stack trace is <insert_6>.
- Severity
- 20 : Error
- Explanation
- An MQTT Publish using <insert_1> detected an exception when it tried to connect to the MQTT server.
- Response
- Check that the MQTT server is active, you are using a unique Client ID and the correct Security identity and that the Security identity is configured with the correct credentials for the server connection.
- BIP4319
- An exception occurred during the creation of ruleset <insert_1> with namespace <insert_2>.
The exception is <insert_3>.
The exception stack trace is <insert_4>.
- Severity
- 20 : Error
- Explanation
- When a Decision service is deployed the rulesets are created in the integration node decision service repository. During the creation of ruleset <insert_1> with namespace <insert_2> an exception occurred.
- Response
- Refer to the exception message to understand why the ruleset cannot be created.
- BIP4320
- An exception occurred during the deletion of ruleset <insert_1> with namespace <insert_2>.
The exception is <insert_3>.
The exception stack trace is <insert_4>.
- Severity
- 20 : Error
- Explanation
- When a Decision service is deleted the rulesets are removed from the integration node decision service repository. During the deletion of ruleset <insert_1> with namespace <insert_2> an exception occurred.
- Response
- Refer to the exception message to understand why the ruleset cannot be deleted.
- BIP4321
- The DecisionService node '&'1 in message flow <insert_2> cannot locate the data for parameter <insert_5> using the XPath expression <insert_6>.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) has parameter <insert_5>. The data for this parameter cannot be located using the XPath expression <insert_6>. The domain of the input message is <insert_7> with a root element name of <insert_8>.
- Response
- Check that the XPath expression is correct for this parameter. Check that the domain of the input message matches the XPath expression. Check that the root element matches the XPath expression. Check that the field identified by the XPath expression can be serialized as an XML document.
- BIP4322
- The DecisionService node <insert_1> in message flow <insert_2> cannot find the location identified for parameter <insert_5> using the XPath expression <insert_6>.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) has parameter <insert_5>. The location identified by the XPath expression <insert_6> cannot be found. The domain of the input message is <insert_7> with a root element name of <insert_8>.
- Response
- Check that the XPath expression is correct for this parameter. Check that the domain of the message matches the XPath expression. Check that the root element matches the XPath expression.
- BIP4323
- The DecisionService node <insert_1> in message flow <insert_2> could not locate the ruleset <insert_5> that is defined by the decision service <insert_7>.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) is configured to use the integration node decision service repository. The ruleset <insert_5> with namespace <insert_6> cannot be located in the integration node decision service repository.
- Response
- If the ruleset is deployed to a remote decision service repository, select the option "Use DecisionServiceRepository configurable service". You must configure the default DecisionServiceRepository configurable service with the path of an ra.xml file that defines the repository connection. If you are using a decision service deployed to the integration server, do not select the option "Use DecisionServiceRepository configurable service". Check that the decision service <insert_7> is deployed to the integration server.
- BIP4324
- The DecisionService node <insert_1> in message flow <insert_2> cannot locate the ruleset <insert_5> in the remote repository that is defined by the DecisionServiceRepository configurable service.
- Severity
- 20 : Error
- Explanation
- The DecisionService node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) is configured to use a DecisionServiceRepository configurable service. The ruleset <insert_5> with namespace <insert_6> cannot be located in the remote decision service repository as defined by the configurable service.
- Response
- Check that the DecisionServiceRepository configurable service properties are correct. Check that the JDBCProviders configurable service properties are correct. Check that the ruleset <insert_5> with namespace <insert_6> is deployed to the remote repository. If you are using a decision service deployed to the integration server, do not select the option "Use DecisionServiceRepository configurable service". Check that the decision service is deployed to the integration server.
- BIP4325
- A DecisionService node detected an exception when it used the DecisionServiceRepository configurable service.
The exception is <insert_1>.
The exception stack trace is <insert_2>.
- Severity
- 20 : Error
- Explanation
- A DecisionService node is configured to use the DecisionServiceRepository configurable service. The information provided by the ra.xml file caused the exception.
- Response
- Check that the DecisionServiceRepository configurable service properties are correct. Check that the JDBCProviders configurable service properties are correct. Check that the remote repository defined by the JDBCProviders configurable service is available.
- BIP4326
- Decision service output <insert_1>.
- Severity
- 0 : Information
- BIP4327
- IBM Integration Bus decision services are now enabled.
- Severity
- 0 : Information
- BIP4328
- IBM Integration Bus decision services are now disabled.
- Severity
- 0 : Information
- BIP4329
- You attempted to deploy an integration node archive (BAR) file to integration server <insert_2> on integration node <insert_1>, but a flow within the BAR file contains a node of type <insert_4> that requires extension <insert_3> to be enabled in the integration node. The BAR file cannot be deployed.
- Severity
- 20 : Error
- Explanation
- The BAR file cannot be deployed because it contains a flow that is not valid for the target integration node. The DecisionService node allows IBM Integration Bus to call business rules that run on a component of IBM Decision Server that is provided with IBM Integration Bus. The IBM Integration Bus license entitles you to use this component only through the DecisionService node and only for development and functional test.
- Response
- To use the IBM Decision Server component beyond development and functional test, you must purchase a separate license entitlement for either IBM Decision Server or IBM Decision Server Rules Edition for IBM Integration Bus. To confirm that you are entitled to use the IBM Decision Server component, issue the command: mqsimode -x DecisionServices Alternatively, rework your message flow to use nodes that are valid in the current mode.
- 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 integration node.
- 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
- Response
- 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
- Response
- 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
- Response
- Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.
- BIP4359
- XPath query <insert_1> has an undefined namespace prefix <insert_2>
- Severity
- 20 : Error
- Explanation
- All namespace prefixes in an XPath expression must be mapped to a namespace URI. The prefix quoted in the error message is not mapped.
- Response
- If you created the XPath expression using the XPath Expression Builder in the Toolkit:
- Open the XPath Expression Builder.
- Expand the 'Namespace Settings' section.
- Add the prefix and its URI to the list.
- Redeploy the message flow.
If you supplied the XPath expression in a monitoring profile through a configurable service:
- Add a 'prefixMapping' element to the monitoring profile.
- Update the configurable service that contains the monitoring profile.
- BIP4360
- Java node information: <insert_1>.
- Severity
- 0 : Information
- Explanation
- Information message generated by Java node.
- Response
- No user action required.
- BIP4361
- Java node warning: <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Warning message generated by user Java node.
- Response
- Contact the node provider for further details.
- BIP4362
- Java node error: <insert_1>.
- 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_1>: <insert_2>.
- 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_1>.
- 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_1>, size[<insert_2>].
- 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_1> of type <insert_2>.
- Severity
- 20 : Error
- Explanation
- An exception has occurred during the creation of the Java node: <insert_3>3
- Response
- Contact the node provider for further details.
- BIP4367
- The method <insert_1> in Java node <insert_2> has thrown the following exception: <insert_3>.
- Severity
- 20 : Error
- Explanation
- The method <insert_1> 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_1> has thrown the following exception: <insert_2>.
- 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 integration node and retry the operation. If the problem persists, contact your IBM support center.
- BIP4370
- Failure in CNI layer, return code is <insert_1>.
- 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_1>1
- Severity
- 30 : Severe error
- Explanation
- The Java class <insert_1> 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_1> in class <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The Java method or field <insert_1> in class <insert_2> 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_1> 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_1> 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_1>.
- 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 integration node.
- BIP4377
- The user node <insert_1> 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_1> 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_1>.
- 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_1> 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_1> 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_2> in expression <insert_1>.
- 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_1> is not in the XPath 1.0 specification or is not an integration node 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_1> 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_1>).
- 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_1> 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_1> 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 integration node.
- Severity
- 10 : Warning
- Explanation
- The function 'id' is not supported by the integration node.
- Response
- Avoid use of the XPath function 'id'.
- BIP4393
- XPath: The integration node extension function <insert_1> requires one argument.
- Severity
- 10 : Warning
- Explanation
- The integration node extension function requires one argument.
- Response
- Check the appropriate function call in the XPath expression.
- BIP4394
- Java exception: <insert_1>; thrown from class name: <insert_2>, method name: <insert_3>, file: <insert_4>, line: <insert_5>; trace text: <insert_6>; resource bundle: <insert_7>; key: <insert_8>; inserts(optional): <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>, <insert_14>, <insert_15>, <insert_16>, <insert_17>, <insert_18>
- Severity
- 20 : Error
- Explanation
- The message contains that data associated with a Java exception.
- Response
- No user action required.
- BIP4395
- Java exception: <insert_1>; thrown from class name: <insert_2>, method name: <insert_3>, file: <insert_4>, line: <insert_5>
- 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
- Integration node 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
- Integration node JVM class loading information.
- Response
- No user action required.
- BIP4399
- An unexpected error has occurred in the Java API framework. You have attempted to create another instance of the node.
- Severity
- 30 : Severe error
- Explanation
- Within the Java API framework, any node can have only one instance of itself. The most likely cause of the error is a Java statement that attempts to create a second instance of a JavaCompute Node, although the error could also occur in Java code that you have written for other Java plug-in nodes.
- Response
- Rework your Java code and remove any attempt to create a second instance of the node. If your code does not contain an attempt to create a node, or if the problem persists, contact your IBM Support Center.
- BIP4401
- Message propagated to out terminal from node <insert_1>
- 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_1>
- 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_1>
- 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 integration node (UUID <insert_1>).
- Severity
- 20 : Error
- Explanation
- The control message received through the control terminal originated from an AggregateControl node on another integration node. The sending integration node'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 integration node.
- BIP4410
- The AggregateReply node has a different aggregate name (<insert_1>) to the corresponding AggregateControl node (<insert_2>).
- Severity
- 20 : Error
- Explanation
- The control message originated from an AggregateControl node with a different aggregate name.
- Response
- Ensure that the AggregateControl node from which the control message originated, 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_1>
- 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
- 10 : Warning
- 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_1>
- 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_1>
- 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_1>.
- 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_1>.
- BIP4418
- Invalid control message received by AggregateReply node <insert_2>. Missing Information : <insert_1>
- 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_1>
- 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_2>. Missing Information : <insert_1>
- 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_1>
- 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_1> 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_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_1>.
- Response
- Check that the underlying aggregation WebSphere MQ queue is functioning correctly.
- BIP4423
- Unable to store control message in AggregateReply node. Queue=<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_1>.
- Response
- Check that the underlying aggregation WebSphere MQ queue is functioning correctly.
- BIP4424
- Unable to retrieve control message in AggregateReply node. Queue=<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_1>.
- Response
- Check that the underlying aggregation WebSphere MQ queue is functioning correctly.
- BIP4425
- Unable to retrieve request message in AggregateReply node. Queue=<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_1>.
- Response
- Check that the underlying aggregation WebSphere MQ queue is functioning correctly.
- BIP4426
- Unable to store request message in AggregateControl node. Queue=<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_1>.
- Response
- Check that the underlying aggregation WebSphere MQ queue is functioning correctly.
- BIP4427
- Unable to store control message in AggregateControl node. Queue=<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_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_1>.
- 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>, Correlid=<insert_1>.
- Severity
- 10 : Warning
- Explanation
- The AggregateReply node has matched an incoming reply message to an outgoing request message but has failed to find a matching control message. This state should never be reached and is typically caused by WebSphere MQ problems. 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 error might be due to another process or person removing control messages from <insert_3>.
- BIP4430
- Aggregation control message has a bad format. Queue=<insert_1>, Correlid=<insert_2>.
- 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_1> and it has Correlid <insert_2>.
- 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_1>.
- Severity
- 20 : Error
- Explanation
- The AggregationReply node has tried to store a reply message but has failed. Failed to put a message to queue <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_1>, Reply Protocol = <insert_2>. Reply Group Id = <insert_3>.
- Response
- No user action required.
- BIP4433
- Failed to retrieve a reply message. Queue=<insert_1>.
- Severity
- 20 : Error
- Explanation
- The AggregationReply node has tried to retrieve a reply message but has failed. Failed to get a message from queue <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_1>.
- 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.
- BIP4436
- Unable to backout a timeout message to <insert_1> after processing <insert_2> times. Error text: <insert_3>.
- Severity
- 20 : Error
- Explanation
- An AggregateReply node detected that a timeout message had been processed <insert_2>2 times. The backout threshold is set on the Aggregation queues, so backout processing was attempted.
- Response
- The AggregateReply node attempts to put this message back on the dead-letter queue. If the dead-letter queue is not defined, the timeout message is discarded, but user data on the reply queue will not be affected.
- BIP4437
- Unable to put a timeout message to the dead-letter queue <insert_1> after processing <insert_2> times. Error text: <insert_3>.
- Severity
- 20 : Error
- Explanation
- An AggregateReply node detected that a timeout message had been processed <insert_2>2 times. The backout threshold is set on the Aggregation queues, so backout processing was attempted. Either the backout requeue queue is not defined, or there was a previous error while attempting to put the message back on the dead-letter queue. During an attempt to put the message on the dead-letter queue <insert_1>, the following error was experienced: <insert_3>.
- Response
- The AggregateReply node discards this timeout message, but user data on the reply queue will not be affected.
- BIP4438
- Timeout message backed out to <insert_1> after processing <insert_2> times.
- Severity
- 20 : Error
- Explanation
- An Aggregate Reply node detected that a timeout message had been processed <insert_2> times. The backout threshold is set on the Aggregation queues so backout processing was attempted. The message was succesfully backed out to <insert_1> but user data on the reply queue will not be affected.
- Response
- You should resolve the cause of the original processing failure, and place the message on the SYSTEM.BROKER.AGGR.TIMEOUT queue again for reprocessing. If this message is not the result of a downstream exception, or if you are unable to resolve the cause of the backed out messages, you should contact your IBM Support Center.
- BIP4440
- An XSLT transformation was requested. The XSLT node has invoked the eXMLT engine to perform a transformation of XML data. The supplied stylesheet name is <insert_2>. The input data is <insert_1>.
- Severity
- 0 : Information
- Response
- No user action is required.
- BIP4441
- The XSLT transformation is complete. The eXMLT engine has completed the transformation. Output data is <insert_1>.
- Severity
- 0 : Information
- Response
- No user action is required.
- BIP4442
- An XSLT error <insert_2> was reported by XSLT node <insert_1>.
- Severity
- 20 : Error
- Response
- Inspect the error text to determine an appropriate action.
- BIP4443
- The stylesheet name could not be resolved in XSLT node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The sytlesheet name has not been specified in the node property "Stylesheet name", in the local environment, or in the XML document.
- Response
- Ensure that the stylesheet name is available.
- BIP4444
- The XSLT warning <insert_2> was reported by XSLT node <insert_1>.
- Severity
- 10 : Warning
- Response
- Inspect the warning message to determine the appropriate action.
- BIP4445
- The XSLT information message <insert_2> was reported by XSLT node <insert_1>.
- Severity
- 0 : Information
- Response
- No user action is required.
- BIP4446
- The XSLT node <insert_1> requested a transformation of XML data, but the identified stylesheet <insert_2> 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
- The XSLT node <insert_1> encountered a problem during the transformation. The error message is <insert_2>.
- Severity
- 20 : Error
- Explanation
- The transformation could not be completed.
- Response
- Check the error message to identify the cause and correct the error.
- BIP4448
- Output CharSet specification <insert_1> from Local Environment (priority <insert_2>) was found.
- Severity
- 0 : Information
- Explanation
- The XSLT node tried to read the Output CharSet specification from Local Environment and received <insert_1>. The specified priority for selecting Local Environment Output CharSet is <insert_2>.
- Response
- No user action is required.
- BIP4449
- Output CharSet specification <insert_1> from Node Attribute (priority <insert_2>) was found.
- Severity
- 0 : Information
- Explanation
- The XSLT node tried to read Output CharSet specification from Node Attribute and received <insert_1>. The specified priority for selecting Node Attribute Output CharSet is <insert_2>.
- Response
- No user action is required.
- BIP4450
- No Output CharSet specification was found. Default Output CharSet <insert_1> will be used.
- Severity
- 0 : Information
- Explanation
- The XSLT node could not find any Output CharSet specification. Therefore the default Output CharSet <insert_1> will be used.
- Response
- No user action is required.
- BIP4451
- Style sheet Name specification <insert_1> from LocalEnvironment (priority <insert_2>) was found.
- Severity
- 0 : Information
- Explanation
- The XSLTransform node tried to read the style sheet Name specification from LocalEnvironment, and received <insert_1>. The specified priority for selecting LocalEnvironment style sheet Name is <insert_2>.
- Response
- No user action is required.
- BIP4452
- Style sheet Name specification <insert_1> from Node Attribute (priority <insert_2>) was found.
- Severity
- 0 : Information
- Explanation
- The XSLTransform node tried to read the style sheet Name specification from Node Attribute, and received <insert_1>. The specified priority for selecting Node Attribute style sheet Name is <insert_2>.
- Response
- No user action is required.
- BIP4453
- Node <insert_2> could not use non-string data from the LocalEnvironment for overriding property <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Only string values are valid for the property.
- Response
- Make sure a valid string value is specified.
- BIP4454
- XSLT node <insert_1> completed a transformation successfully. However, it produced a result that cannot be serialized to a valid XML string. The failure message is <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The problem may have occurred because the output does not conform to the XML standard or the output encoding is not supported.
- Response
- Inspect the failure message to determine appropriate action.
- BIP4455
- No recipient address was specified.
- Severity
- 20 : Error
- Explanation
- The EmailOutput node cannot create and send an e-mail as no recipient address (To, Cc, or Bcc) has been specified.
- Response
- At least one recipient address is required to send an e-mail. Recipient addresses can be specified as node properties, or in the EmailOutputHeader. Review the message flow to ensure that at least one address is specified in one of these locations.
- BIP4456
- When parsing the recipient address <insert_1>, the following error occurred: <insert_2>.
- Severity
- 20 : Error
- Explanation
- The EmailOutput node cannot create and send an e-mail as an error was found while parsing a recipient address.
- Response
- Recipient addresses can be specified as node properties or in the EmailOutputHeader. Review the message flow to ensure that recipient addresses are correctly specified in these locations.
- BIP4457
- A parsing exception occurred for Content-Type <insert_1>.
- Severity
- 20 : Error
- Explanation
- The EmailOutput node cannot create and send an e-mail as an error was found while parsing the Content-Type.
- Response
- A Content-Type can be selected as a node property or specified in the LocalEnvironment. Review the message flow to ensure that the Content-Type is correctly specified in the LocalEnvironment.
- BIP4458
- There was an error when the EmailOutput tried to create an e-mail and send it to the SMTP server. The description of the error is: <insert_1>.
- Severity
- 20 : Error
- Response
- Review the content of the error and correct it, if possible. Contact your IBM support center if you are unable to resolve the problem.
- BIP4459
- The EmailOutput node received a Java exception when it tried to create an e-mail and send it to the SMTP server. The stack trace from the exception is <insert_1>.
- Severity
- 20 : Error
- Response
- Review the stack trace and correct any errors. Contact your IBM support center if you are unable to resolve the problem.
- BIP4460
- Message propagated to out terminal from node <insert_1>.
- 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.
- BIP4461
- No name was specified for the SMTP server.
- Severity
- 20 : Error
- Explanation
- The EmailOutput node cannot create and send an e-mail as no SMTP server name was specified.
- Response
- An SMTP server name is required to send an e-mail. The SMTP server name can be specified as a node property, in the LocalEnvironment, or as an integration node external resource. Review the message flow to ensure that an SMTP server name is specified in one of these locations.
- BIP4462
- Message propagated to out terminal from node <insert_1>
- Severity
- 0 : Information
- Explanation
- A SecurityPEP 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_1>. The Java stack trace is: <insert_2>
- Severity
- 20 : Error
- Explanation
- The Java JAR file deployment to the integration node failed.
- Response
- This is an internal error. Contact your IBM support center.
- BIP4501
- Failed to delete Java code resource <insert_1>.
- 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 integration node runtime. Stop the integration node 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 integration node in an inconsistent state.
- Response
- Ensure there is sufficient disk space available on the machine running the integration node runtime. Stop the integration node, delete all files in <insert_1>, restart the integration node and perform a full redeploy.
- BIP4503
- Failed to deploy Java code resource <insert_1>. An IOException was thrown during deployment. The Java stack trace is: <insert_2>
- Severity
- 20 : Error
- Explanation
- The Java JAR file deployment to the integration node failed.
- Response
- Ensure there is sufficient disk space available on the machine running the integration node runtime.
- BIP4504
- Failed to deploy Java code resource <insert_1>. A ClassNotFoundException was thrown during deployment. The Java stack trace is: <insert_2>
- Severity
- 20 : Error
- Explanation
- The Java JAR file deployment to the integration node failed.
- Response
- Ensure all dependencies of the Java code have been deployed to the runtime.
- BIP4505
- Failed to deploy Java code resource <insert_1>. The Java class deployed to the Java Compute Node must be public and extend MbJavaComputeNode. The Java stack trace is: <insert_2>
- Severity
- 20 : Error
- Explanation
- The Java JAR file deployment to the integration node failed.
- Response
- The Java Compute Node class implementation must be public and extend MbJavaComputeNode
- BIP4506
- The attempted deletion of Java resource <insert_1> caused a ClassNotFoundException. Since this resource is still required by the integration node it has been restored.
- Severity
- 20 : Error
- Explanation
- The attempted deletion of the Java resource <insert_1> caused a ClassNotFoundException. The integration node 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_1>. Exception <insert_2> was thrown when serializing a Java exception. The Java stack trace is <insert_3>.
- Severity
- 20 : Error
- Explanation
- Because the serialization has failed, this exception is not available in preceding nodes in the flow.
- Response
- If the exception being serialized is a user class, ensure that it can be serialized.
- BIP4509
- Unable to de-serialize a Java exception. The following exception <insert_1> was thrown when de-serializing a Java exception. The Java stack trace is <insert_2>.
- Severity
- 20 : Error
- Explanation
- Because the de-serialization failed, this exception is not available.
- Response
- Ensure that the node catching the exception has access to the exception class.
- BIP4510
- Java compute class <insert_1> not found.
- Severity
- 20 : Error
- Explanation
- The class <insert_1> associated with Java compute node <insert_2> could not be found by the integration node.
- Response
- Ensure that the class <insert_1> has been deployed and is available to the integration node.
- BIP4511
- <insert_1> was thrown while loading Java compute class <insert_2>.
- Severity
- 20 : Error
- Explanation
- A NoClassDefFoundError was thrown while loading Java compute node class <insert_2>. This means that a class used by <insert_2> could not be found.
- Response
- Ensure that all the dependencies of <insert_2> have been deployed to the integration node.
- BIP4512
- <insert_2> was thrown while loading Java user-defined node class <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The stack trace of the exception is <insert_3>.
- Response
- Use the exception information to resolve the problem and restart the integration node. If the stack trace reports a java.lang.NoClassDefFoundError this normally means that the dependencies can not be loaded, or if packaged as a PAR file ensure the user has access to the system temporary directory and adequate space is available.
- BIP4513
- The JavaClassLoader configurable service <insert_1> property includedDeployedJars contains an invalid value <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The includedDeployedJars property can only contain entries which end in .jar or which have the value "automatic". Entries should be separated by a ';' character.
- Response
- Modify the configurable service to contain the correct value.
- BIP4514
- The classloader defined by the JavaClassLoader configurable service <insert_1> has attempted to load jar file <insert_2> which is already in use by <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Only one JavaClassLoader configurable service can be configured to load any particular jar.
- Response
- Make sure the configurable services are configured correctly so only one service will load any given jar file.
- BIP4515
- A shared URL classloader attempted to load a jar file from the directory <insert_1>, but the directory does not exist.
- Severity
- 20 : Error
- Explanation
- The shared URL classloader attempts to load all jar files in a given directory, but the directory does not exist. This will not directly cause any failures, but it might cause a class not found exception if a node was relying on a jar file which should be in that directory.
- Response
- Make sure the directory exists and contains any required jar files.
- BIP4516
- Failed to find all the required WebSphere MQ java classes. Class <insert_1> not found in CLASSPATH <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- Not all the WebSphere MQ jars are installed on this machine. IBM Integration Bus requires that WebSphere MQ for Java is installed to work correctly.
- Response
- Make sure that all the correct WebSphere MQ components are installed and that the CLASSPATH correctly contains the WebSphere MQ jar files.
- BIP4517
- An exception was issued when an instance of Java class <insert_1> was being created for JavaCompute node <insert_2>. The stack trace of the exception is: <insert_3>.
- Severity
- 20 : Error
- Explanation
- An exception was issued when an instance of a Java class was being created for a JavaCompute node.
- Response
- Examine the exception. Ensure that all dependencies of the specified Java class are deployed to the integration server.
- BIP4601
- The Timeout Control Node <insert_2> failed to navigate to the message location specified. The location specified was: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Ensure that the Location <insert_1> is valid for the message tree where it is used.
- Response
- Correct the specified message location.
- BIP4602
- The Timeout Control Node <insert_2> received a timeout request that did not contain a valid timeout action value.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_2> 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_1>.
- Response
- Supply an Action element, with one of the valid values of SET or CANCEL.
- BIP4603
- The Timeout Control Node <insert_1> received a timeout request that did not contain a timeout action.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_1> 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 TimeoutControl node <insert_1> received a timeout request that contained an empty timeout identifier.
- Severity
- 20 : Error
- Explanation
- The node correctly navigated to the specified timeout request location in the request message, and this location contains an identifier element, but the element is empty.
- Response
- Supply a non-empty identifier element.
- BIP4605
- The Timeout Control Node <insert_1> received a timeout request that did not contain a timeout identifier.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_1> 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_2> received a timeout request that did not contain a valid timeout start date value.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_2> 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_1>.
- Response
- Ensure the supplied timeout StartDate is not in the past. TODAY is a valid value.
- BIP4607
- The Timeout Control Node <insert_2> received a timeout request that did not contain a valid timeout start time value.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_2> 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_1>.
- Response
- Ensure the supplied timeout StartTime is not in the past. NOW is a valid value.
- BIP4608
- The Timeout Control Node <insert_2> received a timeout request that did not contain a valid timeout count value.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_2> 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_1>.
- Response
- Ensure the supplied timeout Count is either -1 (for unlimited) or greater than zero.
- BIP4609
- The Timeout Control Node <insert_2> received a timeout request that did not contain a valid timeout interval value.
- Severity
- 20 : Error
- Explanation
- The Timeout Control Node <insert_2> 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_1>.
- Response
- Ensure the supplied timeout Interval is not less than zero.
- BIP4610
- The Timeout Control Node <insert_2> 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_2> 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_1>.
- 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 TimeoutControl node <insert_2> failed to cancel an existing timeout request on queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The node could not cancel a current timeout request because the WebSphere MQ operation failed.
- Response
- Check the cause of the WebSphere MQ failure.
- BIP4612
- The TimeoutControl node <insert_2> failed to store an incoming timeout request on queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The node could not store a timeout request because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4613
- The Timeout Control Node <insert_2> 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_1>.
- 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 TimeoutControl node <insert_2> failed to access its internal store on queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The node could not access its internal store because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4615
- The TimeoutNotification node <insert_2> failed to delete a non-persistent timeout request from queue <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The node could not delete a timeout request because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4616
- The TimeoutNotification node <insert_2> failed to delete an overridden timeout request on queue <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The node could not delete a timeout request because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4617
- The TimeoutNotification node <insert_2> failed to access its internal store on queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The node could not access its internal store because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4618
- The TimeoutNotification node <insert_2> failed to get a message from its internal store on queue <insert_1>.
- Severity
- 20 : Error
- Explanation
- The node could not retrieve a timeout message because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4619
- The TimeoutNotification node <insert_1> received a bad timeout request.
- Severity
- 20 : Error
- Explanation
- The node received a corrupt timeout request message. This error can occur if the message stored by the corresponding TimeoutControl node cannot be de-serialized. It can also occur if messages that are not generated by a TimeoutControl node have been put on the message store.
- Response
- Correct the incoming data.
- BIP4620
- The TimeoutNotification node <insert_3> failed to update a message in its internal store. The WebSphere MQ return codes for the operation are completion code <insert_1>, reason code <insert_2>.
- Severity
- 20 : Error
- Explanation
- The node could not update a timeout message because the WebSphere MQ operation failed.
- Response
- Correct the cause of the WebSphere MQ failure.
- BIP4621
- Exception condition detected on input node: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> 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_1>.
- Severity
- 20 : Error
- Explanation
- The input node <insert_1> 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 by input node <insert_1>.
- Severity
- 20 : Error
- Explanation
- An input node detected an error while processing a message. The message flow has been rolled back. Following messages will indicate the cause of this exception which was generated in another part of the message flow.
- Response
- Check the error messages that follow to determine why the exception was generated, and take the action that is described by those messages.
- BIP4624
- Exception condition detected on input node: <insert_1>.
- Severity
- 0 : Information
- Explanation
- Node <insert_1> has detected a failure during message processing. The integration node 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_1>
- 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_1>
- 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_2>
- Severity
- 0 : Information
- Explanation
- A TimeoutControl node has set a timeout with identifier <insert_1>
- Response
- No user action required
- BIP4628
- Timeout request cancelled by node <insert_2>
- Severity
- 0 : Information
- Explanation
- A TimeoutControl node has cancelled a timeout with identifier <insert_1>
- Response
- No user action required
- BIP4629
- Timeout request being processed by node <insert_2>
- Severity
- 0 : Information
- Explanation
- A TimeoutNotification node is processing a timeout with identifier <insert_1>
- Response
- No user action required
- BIP4630
- An MQGET operation was unsuccessful. Completion Code <insert_1>; Reason Code <insert_2>.
- 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_3> failed to navigate to the <insert_2> specified. The location specified was: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Ensure that the Location <insert_1> 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_2> was unable to obtain MsgId/CorrelId for message matching from input MQMD location: <insert_1>.
- 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 occurred 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_3> received an configuration message containing an invalid attribute value <insert_2> specified. The location specified was: <insert_1>.
- Severity
- 20 : Error
- Explanation
- Ensure that the Location <insert_1> 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_3> failed to navigate to the default location <insert_1> for <insert_2>.
- Severity
- 0 : Information
- Explanation
- Location <insert_1> is the default value for <insert_2> and it was not found. It is assumed that this <insert_2> 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_2> node property is not needed; Otherwise, make sure the location is available or correct the location specification.
- BIP4636
- Unable to back out a timeout message to <insert_1> after processing <insert_2> times. Error text: <insert_3> mqcc: <insert_4> mqrc: <insert_5>5
- Severity
- 20 : Error
- Explanation
- A TimeoutNotification node detected that a timeout message had been processed <insert_2>2 times. The backout threshold is set on the timeout queues, so backout processing was attempted. During an attempt to back out the message to <insert_1>, the following error occurred : <insert_3> mqcc: <insert_4> mqrc: <insert_5>5
- Response
- The TimeoutNotification node attempts to put this message back on the dead-letter queue. If the dead-letter queue is not defined, the timeout message is discarded, but user data on the reply queue will not be affected.
- BIP4637
- Unable to put a timeout message to the dead-letter queue <insert_1> after processing <insert_2> times. Error text: <insert_3> mqcc: <insert_4> mqrc: <insert_5>5
- Severity
- 20 : Error
- Explanation
- A TimeoutNotification node detected that a timeout message had been processed <insert_2>2 times. The backout threshold is set on the timeout queues, so backout processing was attempted. Either the backout requeue queue is not defined, or there was a previous error while attempting to put the message back on the dead-letter queue. During an attempt to put the message on the dead-letter queue <insert_1>, the following error occurred: <insert_3> mqcc: <insert_4> mqrc: <insert_5>5
- Response
- The TimeoutNotification node discards this timeout message, but user data on the reply queue will not be affected.
- BIP4638
- Timeout message backed out to <insert_1> after processing <insert_2> times.
- Severity
- 20 : Error
- Explanation
- A TimeoutNotification node detected that a timeout message had been processed <insert_2> times. The backout threshold is set on the timeout queues so backout processing was attempted. The message was succesfully backed out to <insert_1> but user data on the reply queue will not be affected.
- Response
- Resolve the cause of the original processing failure, and place the message on the SYSTEM.BROKER.TIMEOUT.QUEUE queue again for reprocessing. If this message is not the result of a downstream exception, or if you are unable to resolve the cause of the backed out messages, contact your IBM Support Center.
- BIP4640
- IIB JMSClient. <insert_1> There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = <insert_2>. Location of the bindings = <insert_3>. ConnectionFactory Name = <insert_4>. JMS destination = <insert_5>. The exception text is : <insert_7>.
- Severity
- 20 : Error
- Explanation
- The node cannot obtain a JNDI Administered Object, because some of the values specified 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 Configurable Service attributes associated with this JMS Provider and restart the integration server
or
Change the node attributes and redeploy the message flow.
- BIP4641
- JMSClient <insert_1>: incorrect URL specified for Initial Context Factory.
- Severity
- 20 : Error
- Explanation
- JNDI could not find the Initial Context Factory for the JMS provider at the URL specified.
- Response
- Check that the JNDI-administered objects are at the URL path specified. If the administered objects are stored by LDAP, verify that you have provided the correct security credentials (user ID and password) on the mqsichangeproperties command.
- BIP4642
- IIB JMSClient.<insert_1> There was JMS Exception while creating <insert_2> Destination. If available the JMS provider return code is <insert_4>.
- 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
- IIB JMSClient.<insert_1>. Error Receiving JMS Message. If Available the text from the JMS Exception is <insert_2>.
- 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
- IIB JMSClient.<insert_1> Unable to create a JMS Message for output. If available the text from the JMS Exception is <insert_2>.
- 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
- JMSClient.<insert_1> A JMS exception occurred when the node tried to create a JMS Session.
- Severity
- 0 : Information
- Explanation
- The node could not establish a JMS Session on the JMS Connection.
- Response
- Verify that the JMS provider is available, and that sufficient resources have been allocated.
- BIP4646
- JMSClient. <insert_1> The format of a JMS message received by the node is not valid and could not be processed.
- Severity
- 0 : Information
- Explanation
- The node received a JMS message that 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 might be at the destination configured in the failure path of the deployed flow, or the backout destination if specified in the node, or it might have been rolled back to the provider.
- BIP4647
- JMSClient. <insert_1> A JMS exception occurred when the node tried to create a JMS message consumer. If available the JMS exception text is : <insert_2>
- Severity
- 20 : Error
- Explanation
- The node could not 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 persists, contact the vendor of the JMS provider.
- BIP4648
- JMSClient.<insert_1> The connection with the JMS provider could not start, or has closed for Initial Context factory <insert_2>. The node will try to re-establish the connection.
- Severity
- 20 : Error
- Explanation
- The JMS Connection with the JMS provider 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
- The node tries to reconnect to the JMS provider, unless the message flow is shutting down. Check that the provider is available.
- BIP4649
- A connection with the JMS provider has been made on behalf of node <insert_1> using initial context factory <insert_2>, JNDI bindings location <insert_4> and connection factory name <insert_5>. This connection is using the JMS transaction mode <insert_3>.
- Severity
- 0 : Information
- Explanation
- The JMS Connection with the JMS provider has started for this node.
- Response
- No user action required.
- BIP4650
- IIB JMSClient.<insert_1> Invalid setting for node attribute "Transaction Coordinated" with a non XA-Compliant JMS provider. Initial Context Factory: <insert_2> URL: <insert_3>.
- Severity
- 20 : Error
- Explanation
- The JMS Provider is not enabled for XA-Compliant transaction coordination .
- Response
- Modify the node attribute and re-deploy, or enable XA-Complaint transaction coordination by setting the JMSProviders configurable service attribute 'jmsProviderXASupport' to 'true'.
- BIP4651
- JMSClient. <insert_1> A JMS exception occurred when the node tried to send a JMS message. If available the JMS exception text is : <insert_2>
- Severity
- 20 : Error
- Explanation
- The node could not 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 persists, contact the vendor of the JMS provider.
- BIP4652
- JMSClient. <insert_1> A JMS exception occurred when the node tried to acknowledge a JMS message. If available the JMS Exception text is : <insert_2>
- Severity
- 20 : Error
- Explanation
- The node could not 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, contact the vendor of the JMS provider.
- BIP4653
- JMSClient. <insert_1> An error occurred when the node tried to dispatch another instance of the message flow.
- Severity
- 0 : Information
- Explanation
- The node could not dispatch another processing thread for an additional instance of the message flow.
- Response
- Check the number of instances configured for this message flow. If the problem persists, contact your IBM representative.
- BIP4654
- IIB JMSClient. <insert_1> An error was returned downstream from the Input node. If available the text of the exception is <insert_2>.
- 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
- JMSClient.<insert_1> The node could not extract JMS header data from a JMS input message.
- Severity
- 20 : Error
- Explanation
- The node could not extract header data from the JMS message because it was corrupted or badly formed.
- Response
- Investigate the cause of the badly-formed JMS message.
- BIP4656
- JMSClient.<insert_1> The node could not extract JMS properties data from a JMS input message.
- Severity
- 20 : Error
- Explanation
- The node could not extract property data from the JMS message because it was corrupted or badly formed.
- Response
- Investigate the cause of the badly-formed JMS message.
- BIP4657
- JMSClient. <insert_1> The node could not extract the data payload from a JMS input message.
- Severity
- 20 : Error
- Explanation
- The node could not extract the payload data from the JMS message. This was because it was either in an unexpected IIB 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
- IIB JMSClient.<insert_1> 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 IIB 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
- IIB JMSClient. <insert_1> 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 IIB 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
- IIB JMSClient.<insert_1> 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
- IIB JMSClient.<insert_1> 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
- IIB JMSClient. <insert_1> 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
- The JMSType set in the header has been rejected by the JMS Provider, either because it is an unrecognized JMSType or because it is not appropriate for the class of Message being used. Correct the value of the JMSType header or use a different class of Message.
- BIP4663
- IIB JMSClient.<insert_1> 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
- IIB JMSClient.<insert_1> 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
- JMSClient.<insert_1>.The node could not update MRM-related property values in the MbMessage.
- Severity
- 20 : Error
- Explanation
- The node could not set values for message set, type, or format in the MbMessage.
- Response
- If possible, turn on service trace and investigate the format of the data in the JMSType field in the header data of the JMS message.
- BIP4666
- JMSClient.<insert_1> The JMS message received by the node was of an unexpected type <insert_2> for message domain <insert_3>.
- Severity
- 20 : Error
- Explanation
- The node could not process the JMS Message because it was an unexpected type for the message domain specified in the node attributes.
- Response
- Investigate
- BIP4667
- JMSClient.<insert_1> An exception occurred during shutdown of the message flow. If available the text from the exception is <insert_2>.
- Severity
- 20 : Error
- Explanation
- An unexpected error occurred during shutdown of the message flow.
- Response
- Investigate the cause of the error. If the problem persists, contact your IBM representative.
- BIP4668
- IIB JMSClient.<insert_1> There was an error while attempting to create a JMS message producer.If available the text of the exception is <insert_2>.
- 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
- JMSClient.<insert_1>. A backout destination was not configured for a JMS node.
- Severity
- 10 : Warning
- Explanation
- The node was unable to process a JMS message because of errors and cannot send it to a backout destination because none was configured.
- Response
- Investigate the cause of the message failure. Consider setting Backout Destination and Backout Threshold properties for the node.
- BIP4670
- IIB 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
- IIB 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
- IIB 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_1> 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
- IIB JMSClient.<insert_1> Error finding local transaction in table for the Provider with Initial Context Factory <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.
- BIP4674
- IIB JMSClient.<insert_1> Error committing a transaction for the Provider with Initial Context Factory <insert_2>. The Requesting ID was <insert_3>.
- 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
- IIB JMSClient.<insert_1> Error rolling back transaction for the Provider with Initial Context Factory <insert_2>. The Requesting ID was <insert_3>.
- 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
- IIB JMSClient <insert_1>. Error closing JMS session for the Provider with Initial Context Factory <insert_2>. The Requesting ID is <insert_3>.
- 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
- IIB JMSClient. <insert_1> The type of JMS Message received by the node is invalid for the message domain <insert_2>.
- 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.
- BIP4678
- An e-mail error occurred during processing of a message. The e-mail error message is <insert_1>.
- Severity
- 20 : Error
- Explanation
- This error was detected by the EmailOutput node. The following message describes the diagnostic information that is provided by the e-mail system <insert_1>.
- Response
- Look at the diagnostic information that is provided with the e-mail system. Further diagnostic information might be written to user trace.
- BIP4679
- An error has occurred in the message flow in JMSInput node <insert_1>, which is using the CLIENT_ACKNOWLEDGMENT mode. This mode might cause <insert_2> duplicate messages to be redelivered to the input node.
- Severity
- 0 : Information
- Explanation
- This error was detected by the JMSInput node. The node is configured to use JMS CLIENT_ACKNOWLEDGEMENT mode, and an error has occurred during the acknowledgment of a batch of JMS messages. These messages have been processed by the message flow, but the JMS provider might redeliver them. This situation can also occur if the JMS connection being used by the node is broken and re-established. In both cases, duplicate messages might be received by the JMSInput node after the failure has occurred.
- Response
- If the JMS provider supports the optional JMS redelivery count, you can set the JMSInput node Backout Threshold and Backout Destination properties to manage duplicate messages. If you prefer, you can define your own method to process duplicate messages.
- BIP4680
- Unsupported message domain <insert_1> encountered in mapping node <insert_2>.
- 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
- BIP4681
- An error occurred finding the transaction identifier for the JDBC data source <insert_1>.
- Severity
- 20 : Error
- Explanation
- The underlying JDBC connection with the data source driver is no longer available.
- Response
- Check the connectivity and availability of the database management system.
- BIP4682
- An error occurred committing a transaction for the JDBC data source <insert_1>.
- Severity
- 20 : Error
- Explanation
- The underlying JDBC connection with the DataSource driver is no longer available.
- Response
- Check the connectivity and availability of the database management system.
- BIP4684
- An error occurred rolling back a transaction for the JDBC data source <insert_1>.
- Severity
- 20 : Error
- Explanation
- The underlying JDBC connection with the DataSource driver is no longer available.
- Response
- Check the connectivity and availability of the database management system.
- BIP4685
- An error occurred closing a JMS session 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.
- BIP4686
- An error occurred finding a local transaction for the JMS 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.
- BIP4687
- An error occurred committing a transaction 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.
- BIP4688
- An error occurred rolling back a transaction 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.
- BIP4689
- An error occurred closing a JMS connection 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.
- BIP4690
- The Initial Context Factory class name <insert_1> was not valid, or the class is not available to the integration node, or a wrong location has been specified for the JNDI bindings <insert_2>.
- Severity
- 20 : Error
- Explanation
- The node is unable to find the Initial Context Factory class specified either because the name is not valid, or the JNDI bindings location has been incorrectly specified.
- Response
- Check that the class name for the Initial Context Factory is correct. Ensure that the class name has been correctly specified in the integration node configurable service properties. Check that the correct name and path have been specified for the JNDI bindings.
- BIP4691
- The JMS connection factory name <insert_1> that was specified in the node properties was not valid, or the name cannot be found in the JNDI bindings <insert_2>.
- Severity
- 20 : Error
- Explanation
- The name of JMS connection factory is not valid, or does not exist in the JNDI bindings.
- Response
- Check the name for errors and ensure that it exists in the JNDI bindings.
- BIP4692
- The backout JMS destination for the JMSInput node was missing or not valid, or the name cannot be found in the JNDI bindings <insert_1>.
- Severity
- 20 : Error
- Explanation
- The name of the JMS destination for backout of messages is missing or not valid.
- Response
- Specify a valid JMS destination for backout of messages that have been redelivered to the input destination, where the number of redeliveries exceeds the threshold specified in the node properties.
- BIP4693
- The JMS destination <insert_1> that was specified for the JMS node was not valid, or the name cannot be found in the JNDI bindings <insert_2>.
- Severity
- 20 : Error
- Explanation
- The name of the JMS destination is not valid or was not found in the JNDI bindings, or the underlying JMS provider resource has not been configured correctly.
- Response
- Check that the name of the JMS destination has been configured in the JNDI bindings. Check that the underlying JMS provider resource has been correctly configured.
- BIP4694
- The message received at output node <insert_3> contains an MQMD at index <insert_1> which is the wrong position; the MQMD should be at index <insert_2>.
- Severity
- 20 : Error
- Explanation
- The IBM Integration Bus output node <insert_3> has received a message to write to WebSphere MQ, but the message contains an MQMD in the wrong position in the message. This situation can occur when an output message is built incorrectly using a Compute node.
- Response
- Check the message flow to determine whether the message is being built correctly. You can use a Trace node to see how the message has been built. Correct the problem and redeploy.
- BIP4695
- A connection with the JMS provider has been made on behalf of node <insert_1> in CLIENT_ACKNOWLEDGMENT mode using initial context Factory <insert_2>, JNDI bindings location <insert_4> and connection factory name <insert_5>. This connection is using the JMS transaction mode <insert_3>.
- Severity
- 0 : Information
- Explanation
- The JMS Connection with the JMS provider has started for this node using CLIENT_ACKNOWLEDGEMENT mode.
- Response
- No user action required.
- BIP4696
- The JMSInput Node <insert_1> could not backout a message.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has been unable to backout a message. The node was unable to obtain a MessageProducer for the backout destination <insert_2>. The JMS Client did not return any error information.
- Response
- Examine the logs for your JMS Provider to determine why a MessageProducer could not be created. Correct this situation if possible.
- BIP4697
- The JMSInput Node <insert_1> could not process a non-transactional message. A backout destination has either not been defined or sending the message to the backout destination has failed. Since the message can not be rolled back the message has been discarded.
- Severity
- 20 : Error
- Explanation
- Node <insert_1> has been unable to process a transactional message. Either no backout destination has been defined, or an attempt to backout the message has failed. Since non-transactional messages can not be rolled back, the integration node has discarded this message.
- Response
- Define a backout destination for this node. Examine previous messages and the message flow to determine why the message is can not be processed. Correct this situation if possible.
- BIP4698
- The JMSInput Node <insert_1> has backed out the message to the backout destination <insert_2>.
- Severity
- 0 : Information
- Explanation
- Message backout processing has been invoked, and the message has been backed out to the backout destination.
- Response
- No user action required.
- BIP4700
- The Collector node <insert_1> failed to process a message passed to terminal <insert_2> caused by a logical error in the event handler class <insert_3>.
- Severity
- 30 : Severe error
- Response
- Contact your IBM support center.
- BIP4701
- The Collector node <insert_1> attempted to register an invalid event handler on terminal <insert_2>. The handler class was <insert_3>.
- Severity
- 30 : Severe error
- Response
- Contact your IBM support center.
- BIP4702
- The Collector node <insert_1> received a message collection on terminal <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- Only single-body messages can be sent to this node.
- Response
- Redesign the message flow so that message collections are not presented to the input terminal of a Collector node.
- BIP4703
- The Collector node <insert_1> failed to process a message passed to terminal <insert_2>. This is caused by an exception <insert_4> thrown by event handler class <insert_3>.
- Severity
- 30 : Severe error
- Response
- Contact your IBM support center.
- BIP4704
- The IBM Integration Bus event store failed to process a storage request because the WebSphere MQ queue <insert_1> reached its maximum depth. The WebSphere MQ reason code is <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The failure might be because:
A client that is passing messages to one of the input terminals is inactive.
The configuration properties of the node are not appropriate for the pattern of incoming messages.
The Collection expiry property is too large or not set.
- Response
- Ensure that the properties for this node are set to values that are appropriate to the rate and balance of messages that are appearing at each terminal. Ensure that the Collection expiry property is set to an appropriate value. Generally, increasing the maximum queue depth will delay rather than fix this problem.
- BIP4705
- The IBM Integration Bus event store failed to process a storage request when it attempted to store the event on queue <insert_1>.
- Severity
- 30 : Severe error
- Response
- Check that the underlying WebSphere MQ queue is functioning correctly.
- BIP4706
- The event storage system failed to serialize the event handler state. The object serializer threw exception <insert_1>.
- Severity
- 30 : Severe error
- Response
- Contact your IBM service center.
- BIP4707
- The Collector node <insert_1> cannot receive event messages.
- Severity
- 30 : Severe error
- Explanation
- The Collector node <insert_1> does not have any active input terminals. It must have one or more input terminals wired to receive event messages.
- Response
- In the Integration Toolkit, right-click on the Collector node and select 'Add Input Terminal'. Give the terminal a name, configure its properties, and wire it to an input source.
- BIP4708
- The Collector node <insert_1> has received a message on its Control terminal.
- Severity
- 30 : Severe error
- BIP4709
- Message collection (id = <insert_1>) is complete.
- Severity
- 0 : Information
- BIP4710
- Incomplete message collection (id = <insert_1>) propagated to the 'Expire' terminal.
- Severity
- 30 : Severe error
- BIP4711
- Message collection (id = <insert_1>) propagated to the 'Out' terminal.
- Severity
- 30 : Severe error
- BIP4712
- Message <insert_1> of <insert_2> from input terminal <insert_3> accepted into message collection (Correlation string = <insert_4>).
- Severity
- 0 : Information
- BIP4713
- Timeout waiting for next message on terminal <insert_1>. Number of messages collected on this terminal = <insert_2>. Correlation string = <insert_3>.
- Severity
- 30 : Severe error
- BIP4714
- New message collection created (id = <insert_1>).
- Severity
- 0 : Information
- BIP4715
- The timeout value for terminal <insert_1> is greater than or equal to the collection expiry value.
- Severity
- 20 : Error
- Explanation
- The timeout property for terminal <insert_1> has a value of <insert_2>, which is greater than or equal to the value of the collection expiry property (<insert_3>). This means that collection expiry will always occur before the terminal has timed out.
- Response
- Reduce or remove the terminal timeout or extend the collection expiry.
- BIP4720
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The XPath expression is not valid.
- Response
- Check the syntax of the XPath expression.
- BIP4721
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The element to which the XPath expression refers could not be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the Xpath expression is correct, and refers to a valid element.
- BIP4722
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>
- Severity
- 20 : Error
- Explanation
- For the element to which the XPath refers, no value could be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the XPath expression is correct and that a valid value is associated with the given element.
- BIP4723
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>; data type <insert_5> was expected
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression cannot be converted to <insert_5>, and MQ property <insert_2> expects a <insert_5> data type.
- Response
- Check that the value associated with the element given by the XPath expression is correct, and is of the correct data type.
- BIP4724
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is not a valid <insert_2> value.
- Response
- Check the value returned by the XPath expression.The value must equal -1, or be greater than 1.
- BIP4725
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is not a valid <insert_2> value.
- Response
- Check the value returned by the XPath expression. The value must be greater than, or equal to, 0.
- BIP4726
- Incorrect XPath expression <insert_1> for the MQ property <insert_2> in the MQHeader node <insert_3> present in message flow <insert_4>; maximum length allowed is <insert_5>
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is too long.
- Response
- Check the value returned by the XPath expression and ensure that the length is within the prescribed length.
- BIP4727
- Trace is entering header node <insert_1> that is present in message flow <insert_2>.
- Severity
- 0 : Information
- BIP4728
- The header node operations have successfully completed; exiting the header node <insert_1> that is present in message flow <insert_2>.
- Severity
- 0 : Information
- BIP4729
- Incorrect XPath expression <insert_1> for the HTTP property <insert_2> in the HTTPHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The XPath expression is not valid.
- Response
- Check the syntax of the XPath expression.
- BIP4730
- Incorrect XPath expression <insert_1> for the HTTP property <insert_2> in the HTTPHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The element to which the XPath expression refers could not be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the Xpath expression is correct, and refers to a valid element.
- BIP4731
- Incorrect XPath expression <insert_1> for the HTTP property <insert_2> in the HTTPHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- For the element to which the XPath refers, no value could be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the XPath expression is correct and that a valid value is associated with the given element.
- BIP4732
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is not valid for property <insert_2>.
- Response
- Check the value that is returned by the XPath expression, and correct the expression to return a value of 1 or 2.
- BIP4733
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The XPath expression is not valid.
- Response
- Check the syntax of the XPath expression.
- BIP4734
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The element to which the XPath expression refers could not be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the Xpath expression is correct, and refers to a valid element.
- BIP4735
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> present in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- For the element to which the XPath refers, no value could be found in the message, Environment, or LocalEnvironment.
- Response
- Check that the XPath expression is correct and that a valid value is associated with the given element.
- BIP4736
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> present in message flow <insert_4>; data type <insert_5> was expected
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression cannot be converted to <insert_5>, and JMS property <insert_2> expects a <insert_5> data type.
- Response
- Check that the value associated with the element given by the XPath expression is correct, and is of the correct data type.
- BIP4737
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is not a valid value for property <insert_2>.
- Response
- Check the value that is returned by the XPath expression. The value must be greater than 0.
- BIP4738
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> in message flow <insert_4>.
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is not valid for property <insert_2>.
- Response
- Check the value that is returned by the XPath expression, and correct the expression to return a value in the range 0 to 9.
- BIP4739
- Incorrect XPath expression <insert_1> for the JMS property <insert_2> in the JMSHeader node <insert_3> present in message flow <insert_4>; maximum length allowed is <insert_5>
- Severity
- 20 : Error
- Explanation
- The value returned by the XPath expression is too long.
- Response
- Check the value returned by the XPath expression and ensure that the length is within the prescribed length.
- BIP4741
- The JMS node <insert_1> was unable to load the vendor proprietary API class <insert_2> using the IBM API wrapper class <insert_3>.
- Severity
- 20 : Error
- Explanation
- The IBM vendor proprietary handler class was not able to load the API class that implements vendor specific handling for the JMS provider
- Response
- Check that the location for the JMS provider jar files is correctly configured in the IBM Integration Bus JMSProvider Configurable Services
- BIP4742
- The JMS node <insert_1> was unable to find the expected API method <insert_2> in class <insert_3> using the IBM API wrapper class <insert_4>.
- Severity
- 20 : Error
- Explanation
- The IBM vendor proprietary handler class was not able to find the API method in the class that implements vendor specific handling for the JMS provider
- Response
- Please refer to the vendor documentation to verify that the version of the vendor product supports the method call.
- BIP4743
- Unable to obtain a transaction resource for JMS provider <insert_1> The vendor error message was <insert_2>.
- Severity
- 20 : Error
- Explanation
- The IBM component that interfaces with the JMS provider's proprietary API was not able to obtain a transaction resource from that API class. The vendor exception message describes the problem.
- Response
- Check that the JMS server is active, and that there are no network problems. Refer to the JMS Provider vendor documentation to determine the cause of the exception.
- BIP4751
- IMSRequest node <insert_1> in message flow <insert_2> is about to send a record starting with the bytes <insert_3> to the IMS Connect system on Hostname <insert_4> listening on Port <insert_5> using Data store <insert_6> with GroupName <insert_7>, Username <insert_8> and Password <insert_9>.
- Severity
- 0 : Information
- BIP4752
- A record of size <insert_1> has been received from IMS Connect on Hostname <insert_2> on Port <insert_3> using Data store <insert_4> in IMSRequest node <insert_5> in message flow <insert_6>.
- Severity
- 0 : Information
- BIP4753
- The CICSRequest node <insert_1> in message flow <insert_2> is about to call CICS program <insert_3>, at URL <insert_4>, with a client applid of <insert_5>, a client qualifier of <insert_6>, a connection timeout of <insert_7>, a request timeout of <insert_8>, a COMMAREA of length <insert_9> that starts with the bytes <insert_10>, and a security identity of <insert_11>.
- Severity
- 0 : Information
- BIP4754
- CICSRequest node <insert_1> in message flow <insert_2> has recieved a COMMAREA of length <insert_5> from CICS program <insert_3> at URL <insert_4>. The COMMAREA starts with the bytes <insert_6>.
- Severity
- 0 : Information
- BIP4755
- The IMSRequest node <insert_1> in message flow <insert_2> is propagating username <insert_3> from the message to the IMS system that is running the transaction.
- Severity
- 0 : Information
- Explanation
- The security profile for the <insert_1> IMSRequest node is set to propagate the identity in the message to the IMS system. The identity in the message is determined to be <insert_3> and has been taken from the IdentityMapped- or IdentitySource- elements in the Properties folder.
- Response
- None
- BIP4756
- The CICSRequest node <insert_1> in message flow <insert_2> is about to call a Channel-based CICS program <insert_3>, at URL <insert_4>, with a client applid of <insert_5>, a client qualifier of <insert_6>, a connection timeout of <insert_7>, a request timeout of <insert_8>, and a security identity of <insert_9>.
- Severity
- 0 : Information
- BIP4761
- The message flow attempted to use <insert_1> configurable service <insert_2>, which has not been defined in the integration node.
- Severity
- 20 : Error
- Explanation
- Configurable services need to be set on the integration node. Use the mqsireportproperties command to check that a <insert_1> configurable service called <insert_2> exists.
- Response
- Use the mqsicreateconfigurableservice command to create the required configurable service.
- BIP4762
- Invalid value <insert_1> for <insert_2> configurable service <insert_3> property <insert_4>.
- Severity
- 20 : Error
- Explanation
- The property must have a value greater than or equal to zero.
- Response
- Check that the value is set to an integer greater than or equal to zero.
- BIP4763
- Invalid value <insert_1> for <insert_2> configurable service <insert_3> property <insert_4>.
- Severity
- 20 : Error
- Explanation
- The property must have a valid boolean value of true or false.
- Response
- Check that the value is set to a valid boolean value.
- BIP4764
- Security identity <insert_1> was not found in the integration node.
- Severity
- 20 : Error
- Explanation
- If a security identity is used to define a user name and password for an IMS connection, it must be defined in the integration node by using the mqsisetdbparms command. When setting the security identity, make sure it is prefixed by <insert_2>. Do not include the prefix when setting the security identity on the node or in configurable services.
- Response
- Check that the security identity has been defined on the integration node.
- BIP4765
- Timed out whilte trying to run a transaction in IMS. Execution timeout: <insert_1> milliseconds, Hostname: <insert_2>, Port number: <insert_3>, Data store name <insert_4>.
- Severity
- 20 : Error
- Explanation
- The IMS transaction did not complete within the timeout value given.
- Response
- Check that the transaction being run is processing correctly and is associated with a program that is running.
- BIP4766
- Timed out while trying to run a transaction in IMS. Socket timeout: <insert_1> milliseconds, Hostname: <insert_2>, Port number: <insert_3>, Data store name <insert_4>.
- Severity
- 20 : Error
- Explanation
- The IMS transaction did not complete within the timeout value given.
- Response
- Check that the transaction being run is processing correctly and is associated with a program that is running.
- BIP4767
- Invalid configurable service of type <insert_1> called <insert_2>.
- Severity
- 20 : Error
- Explanation
- The integration node failed to load the configurable service <insert_2>. See previous errors to find out why the configurable service failed to load.
- Response
- Check that the configurable service has been configured correctly.
- BIP4768
- Invalid socket timeout value: <insert_1> seconds.
- Severity
- 20 : Error
- Explanation
- An invalid socket timeout was specified. The socket timeout must be the number of seconds in the range 0-2147483 where a value of 0 is treated as an infinite timeout.
- Response
- Specify a valid socket timeout value in the range 0-2147483.
- BIP4769
- The following IMS adapter error has occurred: <insert_1>.
- Severity
- 20 : Error
- Explanation
- An IMS adapter error has occurred during processing in an IMS node.
- Response
- Review the error message given above to resolve the cause of the error.
- BIP4770
- Invalid execution timeout value: <insert_1> seconds.
- Severity
- 20 : Error
- Explanation
- An invalid execution timeout was specified. The execution timeout must be the number of seconds in the range 1 to 2147483.
- Response
- Specify a valid execution timeout value in the range 1 to 2147483.
- BIP4771
- An error occurred while calling a CICS program using the CICS Transaction Gateway (CTG). The CTG error message is <insert_1>.
- Severity
- 20 : Error
- Explanation
- This error was detected by the CICSRequest node. The CTG error message is <insert_1>.
- Response
- Look at the diagnostic information that is provided by the CTG in following messages.
- BIP4772
- Invalid connection timeout value <insert_1> seconds in CICSConnection configurable service <insert_2>.
- Severity
- 20 : Error
- Explanation
- An invalid connection timeout was specified. The connection timeout must be the number of seconds in the range 0 - 2147483. Where a value of 30 means that you must use the value that is specified on the node. A value of 0 is treated as an infinite connection timeout.
- Response
- Specify a valid socket timeout value in the range 0 - 2147483.
- BIP4773
- Invalid request timeout value <insert_1> seconds in CICSConnection configurable service <insert_2>.
- Severity
- 20 : Error
- Explanation
- An invalid request timeout was specified. The request timeout must be the number of seconds in the range 0 - 2147483. Where a value of 120 means that you must use the value that is specified on the node. A value of 0 is treated as an infinite request timeout.
- Response
- Specify a valid request timeout value in the range 0 - 2147483.
- BIP4774
- Invalid connection timeout value <insert_1> seconds.
- Severity
- 20 : Error
- Explanation
- An invalid connection timeout was specified. The connection timeout must be the number of seconds in the range 0 - 2147483. Where a value of 0 is treated as an infinite timeout. The value will be overridden by the connectionTimeoutSecs property in a CICSConnection configurable service.
- Response
- Specify a valid socket timeout value in the range 0 - 2147483.
- BIP4775
- Invalid request timeout value: <insert_1> seconds.
- Severity
- 20 : Error
- Explanation
- An invalid request timeout was specified. The request timeout must be the number of seconds in the range 0 - 2147483. Where a value of 0 is treated as an infinite timeout. The value will be overridden by the requestTimeoutSecs property in a CICSConnection configurable service.
- Response
- Specify a valid request timeout value in the range 0 - 2147483.
- BIP4776
- CICSRequest node <insert_1> in message flow <insert_2> has received abend code <insert_3> from CICS program <insert_4> on CICS server <insert_5>. The input message is propagated to the Error terminal if it has been connected.
- Severity
- 20 : Error
- Explanation
- The CICSRequest node <insert_1> in message flow <insert_2> has tried to execute CICS program <insert_4> on CICS server <insert_5>. The program has failed with abend code <insert_3>.
- Response
- Resolve the cause of the abend with your CICS adminstrator or developer, and amend the node properties or message flow if required.
- BIP4777
- Invalid CICS client applid: <insert_1> in CICSConnection configurable service <insert_2>. If specified, the CICS client applid must be a maximum of eight alphanumeric characters only.
- Severity
- 20 : Error
- Explanation
- An invalid CICS client applid was specified. The clientApplid property is optional. If this property is specified, the value must be a maximum of eight alphanumeric characters only.
- Response
- Specify a valid CICS client applid if one is required.
- BIP4778
- Invalid CICS client qualifier: <insert_1> in CICSConnection configurable service <insert_2>. If specified, the CICS client qualifier must be a maximum of eight alphanumeric characters only.
- Severity
- 20 : Error
- Explanation
- An invalid CICS client qualifier was specified. The clientQualifier property is optional. If this property is specified, the value must be a maximum of eight alphanumeric characters only.
- Response
- Specify a valid CICS client qualifier if one is required.
- BIP4779
- The length of the COMMAREA received from CICS program <insert_1> in node <insert_2> in message flow <insert_3> is not expected. The COMMAREA received is <insert_4> bytes and <insert_5> bytes were expected.
- Severity
- 10 : Warning
- Explanation
- The expected COMMAREA length for CICS program <insert_1> in node <insert_2> in message flow <insert_3> is <insert_5> bytes. However, <insert_4> bytes were received from the CICS program.
- Response
- If this result is unexpected, investigate why it has occurred.
- BIP4780
- Invalid value <insert_1> for the IMSConnect configurable service UseSSL property. Valid values are True or False.
- Severity
- 20 : Error
- Explanation
- An invalid value was specified for the IMSConnect configurable service property UseSSL. This property enables or disables SSL support for IMS. Valid values are True or False.
- Response
- Specify a valid value of True or False for the UseSSL property.
- BIP4781
- Invalid value <insert_1> for IMSConnect configurable service property SSLEncryptionType. Valid values are ENULL, Weak, or Strong.
- Severity
- 20 : Error
- Explanation
- An invalid value was specified for the IMSConnect configurable service property SSLEncryptionType. This property configures the strength of the SSL encryption that is used when connecting to IMS. Valid values are ENULL, Weak, or Strong.
- Response
- Specify a valid value of ENULL, Weak, or Strong for the property SSLEncryptionType.
- BIP4782
- Security identity <insert_1> was not found in the integration node.
- Severity
- 20 : Error
- Explanation
- If a security identity is used to define a user name and password for a CICS connection, it must be defined in the integration node by using the mqsisetdbparms command. When setting the security identity by using the mqsisetdbparms command, make sure it is prefixed by <insert_2>. Do not include the prefix when setting the security identity on the node or in configurable services.
- Response
- Check that the security identity has been defined on the integration node.
- BIP4783
- The message identity in the Properties folder was not of type "username" or "usernameAndPassword" and cannot be supported by the CICSRequest node.
- Severity
- 20 : Error
- Explanation
- The CICSRequest node can propagate the message identity to CICS, but only if the type of that identity is either "username" or "usernameAndPassword". The node will check to see if there is a mapped identity first and if not, the message identity will fall back to the source identity.
- Response
- Change the message flow to provide a message with a message identity of type "username" or "usernameAndPassword" by changing the input node for the message flow, or by using a SecurityPEP node to modify the type.
- BIP4784
- CICSConnection configurable services <insert_1> and <insert_2> both define the same connection details to CICS. The configured CICSConnection property values are cicsServer <insert_3>, gatewayURL <insert_6>, clientApplid <insert_4>, and clientQualifier <insert_5>.
- Severity
- 10 : Warning
- Explanation
- Configurable services <insert_1> and <insert_2> are both configured to use the same connection details to CICS, which might lead to conflicts between the other properties that are defined in the configurable services.
- Response
- Define one CICSConnection configurable service for each connection to CICS only.
- BIP4785
- A CICSRequest node has been configured to connect to <insert_1> over the Secure Sockets Layer (SSL) protocol, but no SSL keystore file has been configured for the integration node or integration server.
- Severity
- 10 : Warning
- Explanation
- A CICSRequest node is configured to use SSL, but requires an integration node or integration server keystore file. This keystore file must contain trust certificates and any identity certificates. For more information about setting an integration node or integration server keystore file, see "Securing the connection to CICS by using SSL" in the IBM Integration Bus documentation.
- Response
- For more information about setting an integration node or integration server keystore file, "Securing the connection to CICS by using SSL" in the IBM Integration Bus documentation.
- BIP4786
- A connection error has occurred for a Secure Sockets Layer (SSL) protocol connection to CICS at location <insert_1>, which is using keystore <insert_2> and truststore <insert_3>.
- Severity
- 10 : Warning
- Explanation
- A connection error has occurred for an SSL connection to CICS. The cause might be because the CICS region is not available, or because the SSL configuration is not correct. The CICSRequest node does not support a separate SSL truststore, which means that any signer certificates required for CICS connectivity must be placed in the keystore file instead of in a separate truststore file. For more information, see "Securing the connection to CICS by using SSL" in the IBM Integration Bus documentation.
- Response
- Ensure that the keystore file that is defined to the integration node contains the signer certificates, and if client-authentication is enabled in the TCPIPSERVICE, the integration node keystore file contains a personal certificate that is trusted by CICS. Also ensure that the CICS region is available, TCP/IP is enabled, and the TCPIPSERVICE that is defined in CICS is correctly configured for SSL.
- BIP4787
- The name of a message <insert_1> in the message collection cannot be used as a CICS container name because it exceeds the 16 char name length limit.
- Severity
- 10 : Warning
- Explanation
- The CICS node is configured to use a CICS Channel structure in order to communicate with CICS. The integration node models a channel as a Message Collection structure where each message becomes a container in the channel. As CICS Channels expect each Container to have a 16 character name, this in turn places a requirement on the input message collection.
- Response
- Ensure that the name of the message within the collection is unique and not more than 16 characters.
- BIP4788
- A message name <insert_1> in the message collection cannot be used as a CICS container because it is not unique. Containers must be unique within a CICS channel.
- Severity
- 10 : Warning
- Explanation
- The CICS node is configured to use a CICS Channel structure in order to communicate with CICS. The integration node models a channel as a Message Collection structure where each message becomes a container in the channel. As CICS Channels expect each Container to have a unique name, this in turn places a requirement on the input message collection.
- Response
- Ensure that the name of the message within the collection is unique and not more than 16 characters.
- BIP4789
- The Channel name for the CICS request was not provided in the LocalEnvironment for a single message CICS Channel request.
- Severity
- 10 : Warning
- Explanation
- The CICSRequest node can create a channel request either from a message collection, or from a single message. In this case, the CICSRequest node has determined that the input message is not a message collection, and is treating the input as a single message. In order for the CICSRequest node to serialize this message as a container in a channel, it needs to know the Channel name and the Container name. Both of these fields have a 16 character limit. The channel name can be specified in the LocalEnvironment by setting $LocalEnvironment/Destination/CICS/RequestChannel/ChannelName.
- Response
- Ensure that the LocalEnvironment contains the name of the channel. This name must not exceed the 16 character maximum length.
- BIP4790
- The Container name for the CICS request was not provided in the LocalEnvironment for a single message CICS Channel request.
- Severity
- 10 : Warning
- Explanation
- The CICSRequest node can create a channel request either from a message collection or from a single message. In this case, the CICSRequest node has determined that the input message is not a message collection, and is treating the input as a single message. In order for the CICSRequest node to serialize this message as a container in a channel, it needs to know the Channel name and the Container name. Both of these fields have a 16 character limit. The container name can be specified in the LocalEnvironment by setting $LocalEnvironment/Destination/CICS/RequestChannel/SingleMessageContainerName.
- Response
- Ensure that the LocalEnvironment contains the name of the channel. This name must not exceed the 16 character maximum length.
- BIP4791
- The CollectionName attribute in the message collection has a value <insert_1> that cannot be used as a CICS channel name because it exceeds the 16 char name length limit.
- Severity
- 10 : Warning
- Explanation
- The CICS node is configured to use a CICS Channel structure in order to communicate with CICS. The integration node models a channel as a Message Collection structure. CICS expects a Channel name to have a 16 character name, this in turn places a requirement on the input message collection.
- Response
- Ensure that the CollectionName attribute of the message collection is not more than 16 characters.
- BIP4792
- Invalid ConnectionIdleTimeoutSec value: <insert_1> seconds.
- Severity
- 20 : Error
- Explanation
- An invalid ConnectionIdleTimeoutSec was specified. The ConnectionIdleTimeoutSec must be the number of seconds in the range 0 to 2147483.
- Response
- Specify a valid ConnectionIdleTimeoutSec value in the range 0 to 2147483.
- BIP4801
- The PHP file <insert_1> referenced by the PHPCompute node <insert_2> does not exist or is not readable.
- Severity
- 30 : Severe error
- Response
- Ensure that the PHP file has been deployed in the integration node archive (bar) file or that it exists on the computer containing the integration node runtime environment.
- BIP4802
- PHP class <insert_1> not found.
- Severity
- 30 : Severe error
- Response
- Ensure that the PHP script contains a class with the same name as the script, without the .php extension.
- BIP4803
- The PHP class <insert_1> does not contain an 'evaluate' method.
- Severity
- 30 : Severe error
- Explanation
- An evaluate method must be defined to process messages.
- Response
- Define a method 'evaluate($output_assembly, $input_assembly) <insert_ ... > to process messages.
- BIP4804
- The PHP file <insert_1> does not contain a '<?php ... ?>' tag.
- Severity
- 30 : Severe error
- Explanation
- PHP code must exist within a <?php ... ?> processing instruction (code island). Either the processing instructions are not present, or the PHP script is not in the UTF8 codepage.
- BIP4805
- The following syntax error occurred in PHP file <insert_1> at line <insert_2>: <insert_3>
- Severity
- 30 : Severe error
- Response
- Correct the error in the PHP script and redeploy.
- BIP4806
- The following PHP runtime error occurred while processing PHP file <insert_1> at line <insert_2>: <insert_3>
- Severity
- 30 : Severe error
- BIP4807
- Read-only message exception while processing PHP file <insert_1>, line <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- An attempt was made to modify a read-only input message in the PHP script. Before you can modify an input message, you must make a copy of it. You can do this either by specifying one of the supported transformation annotations on the evaluate() method, or by instantiating a new MbsMessage object in the PHP code.
- Response
- Modify the PHP script and redeploy.
- BIP4808
- The PHPCompute node <insert_1> has attempted to propagate to an undefined output terminal <insert_2>.
- Severity
- 30 : Severe error
- Response
- Either correct the terminal name or create a dynamic terminal with that name on the node.
- BIP4809
- The PHPCompute node <insert_1> has attempted to propagate to an undefined Label node <insert_2>.
- Severity
- 30 : Severe error
- Response
- Either correct the Label name or create a Label node with that name in the message flow.
- BIP4810
- PHPCompute node <insert_1> invoking PHP script <insert_2>.
- Severity
- 0 : Information
- Explanation
- The PHPCompute node <insert_1> is about to invoke the PHP script <insert_2>.
- BIP4811
- The PHP script <insert_1> has an evaluate method with the annotation <insert_2> defined.
- Severity
- 0 : Information
- Explanation
- The PHPCompute node has detected the annotation <insert_2> on the user's evaluate method.
- BIP4812
- Invoking the evaluate method on the PHP class <insert_1>.
- Severity
- 0 : Information
- Explanation
- The PHPCompute node is invoking the user's evaluate method for the class <insert_1>.
- BIP4813
- Propagating message assembly to output terminal <insert_2>.
- Severity
- 0 : Information
- Explanation
- The PHPCompute node <insert_1> is about to propagate the message assembly to output terminal <insert_2>.
- BIP4814
- Index out of range. The PHPCompute node <insert_1> has attempted to write to a repeating element named <insert_2> with index <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- When you explicitly index the target element, the index must refer to an existing element. If you want to create a new element as the target, use the empty index operator '[]'.
- Response
- Modify the PHP code to fix the problem.
- BIP4815
- The PHPCompute node <insert_1> has attempted to call the addElement() method with an invalid value (<insert_2>) for the element position (parameter 4) at line <insert_4> in the PHP script <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- This parameter must be one of 'MB_LAST_CHILD', 'MB_FIRST_CHILD', 'MB_NEXT_SIBLING', or 'MB_PREVIOUS_SIBLING'.
- Response
- Modify the PHP code to fix the problem.
- BIP4816
- An error occurred in the PHPCompute node during processing of a message. The error message is <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- This error was detected by the PHPCompute node. The following message describes the diagnostic information that is provided by the PHPCompute node <insert_1>.
- Response
- Inspect the diagnostic information that is provided in the error message and the associated error messages.
- BIP4817
- Array index out of range. The PHPCompute node <insert_1> has attempted to write to index <insert_3> of an array at path <insert_2>, but this index does not exist.
- Severity
- 30 : Severe error
- Explanation
- When you explicitly specify an array index, the array index must refer to an existing array element. To create a new array element as the target, use the empty index operator '[]'.
- Response
- Modify the PHP code to fix the problem.
- BIP4818
- A message flow was configured to have its transactions coordinated, but the transaction manager is not correctly configured.
- Severity
- 20 : Error
- Explanation
- The transaction manager is not correctly configured to enable coordinated transactions. See the previous error message for the cause of the failure. If WebSphere MQ is the transaction manager to coordinate the transactions, then WebSphere MQ must be installed on the same computer as the integration node. A queue manager must be defined on the integration node.
- Response
- Ensure the transaction manger is configured correctly and its prerequisites are installed.
- BIP4821
- A duplicate message with sequence number <insert_2> has been received by the ReSequence node (<insert_1>) in sequence group <insert_3>.
- Severity
- 20 : Error
- Explanation
- The ReSequence node has received a duplicate message with sequence number <insert_2> in the sequence group <insert_3>. The message has been rejected from the sequence group.
- Response
- Ensure that each message in a sequence group has a unique monotonically increasing sequence number.
- BIP4822
- The sequence group <insert_2> is complete.
- Severity
- 0 : Information
- Explanation
- The ReSequence node (<insert_1>) has received the final message in the sequence group <insert_2> with sequence number <insert_3>. This sequence group is now closed.
- Response
- No user action is required.
- BIP4823
- The missing message timer has expired while waiting for the next message in the sequence.
- Severity
- 10 : Warning
- Explanation
- The ReSequence node (<insert_1>) will no longer wait for the message with sequence number <insert_2> to arrive in sequence group <insert_3>. Subsequent messages in this group will be propagated to the Expire terminal. If this message eventually arrives, it will be propagated to the Missing terminal.
- Response
- No user action is required.
- BIP4824
- Missing message arrived after the timeout period.
- Severity
- 10 : Warning
- Explanation
- The ReSequence node (<insert_1>) has received the message with sequence number <insert_2> in sequence group <insert_3> after the missing message expiry period. The message will be propagated out of sequence to the Missing terminal.
- Response
- No user action is required.
- BIP4825
- The start of sequence automatic period for Resequence node <insert_1> has expired. The lowest sequence number is <insert_2>, which will be used as the start of sequence number for group <insert_3>.
- Severity
- 0 : Information
- Explanation
- None
- Response
- No user action is required.
- BIP4826
- Automatic End of sequence period has expired.
- Severity
- 0 : Information
- Explanation
- The Resequence node (<insert_1>) has completed its timed period for automatically determining the last message in the sequence group <insert_2>.
- Response
- No user action is required.
- BIP4827
- The ReSequence node (<insert_1>) has failed to find a sequence number in a message associated with group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The ReSequence node (<insert_2>) has received a message, but the XPath expression could not find a matching element in the message tree. The message has been rejected from the sequence group <insert_1>.
- Response
- Ensure that each message in a sequence group has a unique monotonically increasing sequence number in the location specified by the XPath expression.
- BIP4828
- The ReSequence node (<insert_1>) has encountered a non-integer sequence number (<insert_2>) in sequence group <insert_3>.
- Severity
- 20 : Error
- Explanation
- The ReSequence node (<insert_1>) has received a message, but the XPath expression has evaluated to an element that does not contain a valid integer. The message has been rejected from the sequence group <insert_3>. The invalid element value is <insert_2>.
- Response
- Ensure that all messages within a sequence group have a unique monotonically increasing sequence number in the location specified by the XPath expression.
- BIP4829
- The Resequence node (<insert_1>) has encountered a range of missing messages (<insert_2> - <insert_3>), which is too large to add to the local environment.
- Severity
- 10 : Warning
- Explanation
- The range of missing messages is too large to add to the local environment of an expired message. A truncated list of the first <insert_4> will be added to the local environment and the rest will be ignored.
- Response
- Ensure that the resequence properties on the node are valid and that the range of missing messages cannot be too large.
- BIP4833
- The Sequence node <insert_1> encountered an invalid (non-integer) start sequence number (<insert_2>) in the default local environment path, for sequence group <insert_3>.
- Severity
- 20 : Error
- Explanation
- The Sequence node <insert_1> has received a message, but the start sequence number set in the local environment does not contain a valid integer value. The message has been rejected from the sequence group <insert_3>. The invalid element value is <insert_2>.
- Response
- Ensure that the start sequence number set in the local environment is an integer.
- BIP4834
- The Sequence node <insert_1> failed to store the sequence number in the location specified by the 'Path to store sequence number' property, for sequence group <insert_2>.
- Severity
- 20 : Error
- Explanation
- The Sequence node <insert_1> has received a message, but the XPath location <insert_3> specified in the 'Path to store sequence number' property cannot be created for the sequence group <insert_2>. The Sequence node <insert_1> is unable to store the sequence number in the specified XPath location.
- Response
- Ensure that the XPath expression specifying the location in the message is correct.
- BIP4835
- Sequence node <insert_1> has ended the sequence for sequence group <insert_2> because the end of sequence timeout has been reached.
- Severity
- 0 : Information
- Explanation
- The Sequence node (<insert_1>) has completed its timed period for automatically determining the last message in the sequence group (<insert_2>).
- Response
- None
- BIP4836
- The Sequence node <insert_1> failed to resolve XPath Location <insert_2> specified in the 'Path to sequence group identifier' property.
- Severity
- 20 : Error
- Explanation
- The Sequence node <insert_1> has received a message, but the path to the sequence group identifier that is specified as the XPath location <insert_2> returns a null value.
- Response
- Ensure that the XPath to the sequence group identifier is correct.
- BIP4837
- The Sequence node <insert_1> finished processing the message and assigned sequence number <insert_3> to it. The message belongs to sequence group <insert_2>.
- Severity
- 20 : Error
- Explanation
- None
- Response
- No user action required.
- BIP4838
- A message was issued during the evaluation of the end of sequence predicate expression for Sequence node <insert_1>. See the previous message for details.
- Severity
- 10 : Warning
- Explanation
- The end of sequence predicate has been evaluated for a Sequence node (<insert_1>). During the evaluation of this expression a message has been issued. See the previous message for details.
- Response
- No user action is required.
- BIP4839
- Sequence node <insert_1> has ended the sequence for sequence group <insert_2> because the end of sequence number <insert_3> has been reached.
- Severity
- 0 : Information
- Explanation
- The sequence group has reached the end of sequence number defined on the node.
- Response
- No user action is required.
- BIP4840
- Sequence node <insert_1> has ended the sequence for sequence group <insert_2> because the end of sequence predicate was true.
- Severity
- 0 : Information
- Explanation
- The Sequence node has ended the sequence for the sequence group because the end of sequence predicate was calculated to be equal to true.
- Response
- No user action is required.
- BIP4841
- The <insert_1> Configurable service <insert_2> has an invalid queue prefix <insert_3>.
- Severity
- 20 : Error
- Explanation
- The queue prefix <insert_3> is not valid. It must be a valid WebSphere MQ queue name, it must contain no more than 8 characters, and it must not begin or end in a period (.).
- Response
- Modify the queue name prefix to satisfy these requirements.
- BIP4842
- Failed to create queue <insert_1> that is required by the component type <insert_2> named <insert_3>.
- Severity
- 20 : Error
- Explanation
- The queue <insert_1> does not exist, and an attempt to create the queue was made before the component tried to use it.
- Response
- Check the WebSphere MQ error log for a reason why the queue could not be created. Create the required queue manually before deploying or starting this component type.
- BIP4843
- The timeoutSeconds parameter, within the Aggregation configurable service <insert_1>, has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the timeoutSeconds parameter is not a valid number that can be used by the Timeout parameter of the AggregateControl node. It must be a positive decimal number representing the required timeout in seconds that contains at most one decimal place. Values such as 0.1, 0.9, 1, 1.0, 7.8, 7888, and 100000.6 are valid, but values such as 0.10, 0.11, 1.000007, 78., and 66666.20 are invalid. A value of zero indicates there is no timeout and the timeout mechanism is disabled.
- Response
- Ensure that the configurable service timeoutSeconds parameter is set to a valid value containing at most one decimal place.
- BIP4844
- The collectionExpirySeconds parameter of the Collection configurable service called <insert_1> has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the collectionExpirySeconds parameter is not a valid integer that can be used by the "Collection expiry" property on the Collector node. The value must be a positive integer specifying the required expiry time in seconds. A value of zero means that there is no expiry and the expiry mechanism is disabled.
- Response
- Ensure that the configurable service parameter is set to a valid value.
- BIP4845
- The Timer configurable service <insert_1> parameter timeoutIntervalSeconds has an invalid value <insert_2> .
- Severity
- 20 : Error
- Explanation
- The timeoutIntervalSeconds value is not a valid integer that can be used as the timeout interval parameter on the TimeoutNotification node. The value must be a positive integer greater than zero, which is the required timeout interval value used by the node in automatic mode. The node generates messages at this rate. The value is ignored if the node is not running in automatic mode.
- Response
- Check that the configurable service parameter is set to a valid value.
- BIP4846
- The missingMessageTimeoutSeconds parameter of the Resequence configurable service called <insert_1> has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the missingMessageTimeoutSeconds parameter is not a valid integer that can be used by the "Missing message timeout" property on the Resequence node. The value must be a positive integer, specifying the required expiry time in seconds. A value of zero means that there is no missing message timeout and the expiry mechanism is disabled.
- Response
- Ensure that the configurable service parameter is set to a valid value.
- BIP4847
- The startSequenceSeconds parameter of the Resequence configurable service called <insert_1> has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the startSequenceSeconds parameter is not a valid integer that can be used by the "Start of sequence definition" property of the Resequence node. The value must be a positive integer greater than zero, specifying the required time (in seconds) to wait before calculating the start number. The value is used only if the "Start of sequence definition" property is set to "Automatic".
- Response
- Ensure that the configurable service parameter is set to a valid value.
- BIP4848
- The endSequenceSeconds parameter of the Resequence configurable service called <insert_1> has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the endSequenceSeconds parameter is not a valid integer that can be used by the "End of sequence definition" parameter on the Resequence node. It must be a positive integer greater than zero, specifying the required time (in seconds) to wait before ending a sequence group. The value is used only if the "End of sequence definition" property on the Resequence node is set to "Automatic".
- Response
- Ensure that the configurable service parameter is set to a valid value.
- BIP4849
- Node <insert_1> has tried to use the <insert_2> configurable service <insert_3> but it does not exist.
- Severity
- 20 : Error
- Explanation
- The configurable service does not exist.
- Response
- Ensure that the configurable service exists and that the integration node has been restarted.
- BIP4850
- AggregateControl node <insert_1> has failed to use a timeout value specified in the incoming message. The path used was <insert_2> and the value calculated was <insert_3>.
- Severity
- 20 : Error
- Explanation
- Ensure that the path specified in the incoming message is valid and that the resolved value is a valid positive integer. A value of zero is allowed and signifies that the timeout process is disabled.
- Response
- Ensure that the incoming message contains the correct data and that the specified path is correct.
- BIP4851
- Resequence node <insert_1> has received a message in sequence group <insert_2> with sequence number <insert_3>, which evaluates the start of sequence predicate to 'True'. However, messages with earlier sequence numbers have already been stored (the lowest is <insert_4>).
- Severity
- 20 : Error
- Explanation
- The message that evaluates the start of sequence predicate to 'True' must be the first message in the sequence.
- Response
- Ensure that the message contains the first sequence number in the sequence group.
- BIP4852
- A message was issued during the evaluation of the end of sequence predicate expression for Resequence node <insert_1>. See the previous message for details.
- Severity
- 10 : Warning
- Explanation
- The end of sequence predicate has been evaluated for Resequence node <insert_1>. During the evaluation of this expression a message was issued. See the previous message for details.
- Response
- No user action is required.
- BIP4853
- Resequence node <insert_1> has received a message with sequence number <insert_3> in sequence group <insert_2>. It is the last message in the group.
- Severity
- 0 : Information
- Explanation
- The sequence group has reached the end sequence number defined on the node. The group will be closed when all preceding messages have arrived.
- Response
- No user action is required.
- BIP4854
- Resequence node <insert_1> has received a message in sequence group <insert_2> that evaluates the end of sequence predicate to 'True' and sets the end sequence number for the group to <insert_3>.
- Severity
- 0 : Information
- Explanation
- The end sequence number has been set for the sequence group based on the current message. The sequence group will be closed when all preceding messages have arrived.
- Response
- No user action is required.
- BIP4855
- Resequence node <insert_1> has received a message in sequence group <insert_2> that evaluates the start of sequence predicate to 'True' and sets the start sequence number to <insert_3> for the sequence group.
- Severity
- 0 : Information
- Explanation
- None
- Response
- No user action is required.
- BIP4856
- Resequence node <insert_1> has received a message in sequence group <insert_2> with sequence number <insert_3>, which evaluates the end of sequence predicate to 'True'. However, messages with later sequence numbers have already been stored.
- Severity
- 20 : Error
- Explanation
- The message that evaluates the end of sequence predicate to 'True' must be the last message in the sequence.
- Response
- Ensure that the message contains the last sequence number in the sequence group.
- BIP4857
- Resequence node <insert_1> has received a message in sequence group <insert_2> with sequence number <insert_3>, which is less than the start sequence number (<insert_4>).
- Severity
- 20 : Error
- Explanation
- The Resequence node has received a message that is not one of the allowed sequence numbers in the sequence group.
- Response
- Ensure that the start sequence number has been calculated correctly.
- BIP4858
- Resequence node <insert_1> has received a message in sequence group <insert_2> with sequence number <insert_3>, which is greater than the end sequence number (<insert_4>).
- Severity
- 20 : Error
- Explanation
- The Resequence node has received a message that is not one of the allowed sequence numbers in the sequence group.
- Response
- Ensure that the end sequence number has been calculated correctly.
- BIP4859
- Sequence node <insert_1> has a start sequence number (<insert_2>) that is greater than the end sequence number (<insert_3>).
- Severity
- 20 : Error
- Explanation
- The Sequence node <insert_1> has received a message, but the start sequence number specified (<insert_2>) is greater than the end sequence number (<insert_3>).
- Response
- Ensure that the start sequence number is correct.
- BIP4861
- The IBM Integration Bus sequence store failed to process a storage request because the WebSphere MQ queue <insert_1> reached its maximum depth. The WebSphere MQ reason code is <insert_2>.
- Severity
- 20 : Error
- Explanation
- The queue might have become full for one of the following reasons:
A large number of sequence groups are being created and not closed.
The maximum allowed queue depth is not large enough for the required number of sequence groups.
- Response
- Ensure that sequence groups are closed when they are no longer needed. Typically, increasing the maximum queue depth delays rather than solves this problem.
- BIP4862
- The IBM Integration Bus sequence event store failed to process a storage request when it attempted to store the event on WebSphere MQ queue <insert_1>.
- Severity
- 20 : Error
- Response
- Review the previous exception to establish the cause of the error.
- BIP4863
- Failed to delete the state for a sequence group from WebSphere MQ queue <insert_1>. The WebSphere MQ reason code is <insert_2>. The message has a group ID of <insert_3>.
- Severity
- 20 : Error
- Response
- Review the reason code to establish the cause of the error.
- BIP4864
- Failed to access the WebSphere MQ queue <insert_1> to check for sequence group information. The WebSphere MQ reason code is <insert_2>.
- Severity
- 20 : Error
- Response
- Review the reason code to establish the cause of the error.
- BIP4865
- The sequence state stored on the WebSphere MQ queue <insert_1> for sequence group <insert_2> with group ID <insert_3> is in an invalid format. Only messages in <insert_4> format should be on the queue.
- Severity
- 20 : Error
- Response
- Ensure that no applications other than IBM Integration Bus are putting or modifying data on these queues.
- BIP4866
- The timeoutThreads property of the Aggregation configurable service <insert_1> has an invalid value of <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value of the timeoutThreads property is not a valid integer that can be used by the AggregateReply node. It must be a positive integer representing the required number of timeout processing threads. An empty value represents the default single timeout thread.
- Response
- Ensure that the timeoutThreads property on the Aggregation configurable service is set to a valid value.
- BIP4867
- The timeoutThreads property of the Aggregation configurable service <insert_1> is set to <insert_2>, but no queue prefix was specified.
- Severity
- 20 : Error
- Explanation
- When more than one timeout processing thread is used the queuePrefix property must be set to a unique value.
- Response
- Ensure that the queuePrefix property on the Aggregation configurable service is set to a valid value.
- BIP4868
- The timeoutThreads property of the Aggregation configurable service <insert_1> is set to <insert_2>, but the queue prefix <insert_4> is also used by configurable service <insert_3>.
- Severity
- 20 : Error
- Explanation
- When multiple timeout threads are being used the queuePrefix specified on the Aggregation configurable service must be unique.
- Response
- Ensure that the queuePrefix property on the Aggregation configurable service parameter is set to a unique value.
- BIP4869
- The timeoutSeconds property, within the Aggregation configurable service <insert_1>, is set to <insert_2>. As this value is below one second the timeoutThreads, currently set to <insert_3>, is below the required minimum value of 2.
- Severity
- 20 : Error
- Explanation
- When using an Aggregation timeout value below one second the configurable service must also have a timeoutThreads value set to 2 or greater.
- Response
- Ensure that the timeoutThreads value is set to 2 or greater on the Aggregation configurable service.
- BIP4870
- The retryMechanism parameter of the Resequence node called <insert_1> is not compatible with the endOfSequence parameter.
- Severity
- 20 : Error
- Explanation
- The value of the retryMechanism parameter is not compatible with the value of the endOfSequence parameter. When the retryMechanism parameter is 'failure', the endOfSequence parameter must be 'automatic'.
- Response
- Ensure that the retryMechanism parameter and the endOfSequence parameter are set to compatible values.
- BIP4881
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> cannot connect to the naming service located at <insert_4>.
- Severity
- 20 : Error
- Explanation
- The CORBA nodes need to communicate with a naming service to access object references. If the node cannot communicate with the naming service, the node cannot function.
- Response
- Check that the Naming service property of the node is configured correctly. If the configuration is correct, check that the naming service is running and that a firewall is not preventing the integration node from communicating with the naming service. If the Naming service property refers to a configurable service, ensure that the configurable service exists and that the integration node has been restarted since the configurable service was created. To verify that the problem is resolved, restart the message flow.
- BIP4883
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> cannot connect to the naming service located at <insert_4>.
- Severity
- 10 : Warning
- Explanation
- The CORBA nodes must communicate with a naming service to access object references. When the CORBA node is deployed, the node tries to communicate with the naming service. If it fails to communicate with the naming service, the node tries again when it receives a message. If the node cannot communicate with the naming service when a message arrives, an error is thrown.
- Response
- Check that the Naming service property of the node is configured correctly. If the configuration is correct, check that the naming service is running and that a firewall is not preventing the integration node from communicating with the naming service. If the Naming service property refers to a configurable service, ensure that the configurable service exists and that the integration node has been restarted since the configurable service was created. If you are planning to start your naming service at a later time, you can ignore this warning.
- BIP4884
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has connected to the naming service located at <insert_4> but cannot retrieve the object reference <insert_5>.
- Severity
- 20 : Error
- Explanation
- The object reference cannot be found in the naming service.
- Response
- Check that the Object reference name property of the node is configured correctly, and the server has put the object reference in the naming service. To verify that the problem is resolved, restart the message flow.
- BIP4885
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has connected to the naming service located at <insert_4> but cannot get the object reference <insert_5>.
- Severity
- 10 : Warning
- Explanation
- When a CORBARequest node is deployed, the node tries to get the object reference. If the node cannot get the object reference, the node tries again when it receives a message.
- Response
- Check that the Object reference name property of the node is correct. If you plan to put the object reference in the naming service later, you can ignore this warning.
- BIP4886
- A CORBA node is configured with IDL file <insert_1>, but the IDL file is not deployed.
- Severity
- 20 : Error
- Explanation
- A CORBA node cannot load the IDL file with which it is configured.
- Response
- Deploy the IDL file to the integration node.
- BIP4887
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> is configured with IDL file <insert_4> and interface name <insert_5> but the interface cannot be found in the IDL file.
- Severity
- 20 : Error
- Explanation
- The interface cannot be found in the IDL file.
- Response
- Make sure that the IDL file and Interface name properties of the node are correct, then redeploy the message flow.
- BIP4888
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> is configured with naming service <insert_4> in an incorrect format.
- Severity
- 20 : Error
- Explanation
- The naming service must be in the format <host>:<port> where port is optional; for example: 127.0.0.1:1050 or 127.0.0.1 The default value of the port is 1050.
- Response
- Ensure that the Naming service property of the node is correct, then redeploy the message flow.
- BIP4889
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to make an invocation when using object reference <insert_4>.
- Severity
- 10 : Warning
- Explanation
- The object reference that has been taken from the naming service has failed to be used by an invocation. The integration node will try to get a new copy from the naming service but if it fails again, an error will be issued.
- Response
- If the server has invalidated the object reference and put a new object reference in the naming service, the node gets the new object reference. If you are not expecting a replacement object reference, check the status of the CORBA server that you are trying to call.
- BIP4890
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> is configured with IDL file <insert_4> and it contains the unsupported type <insert_5>.
- Severity
- 20 : Error
- Explanation
- The CORBA nodes support a subset of IDL only. The node is configured to use an IDL file that contains an unsupported type.
- Response
- You must use an IDL file that uses the supported types only.
- BIP4891
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has attempted to call operation <insert_5> but did not receive a valid body. A body with the name <insert_4> is expected.
- Severity
- 20 : Error
- Explanation
- The CORBARequest node gets the input parameters from the incoming tree but the node cannot find them.
- Response
- Correct the message flow or ensure that the incoming message has the correct structure.
- BIP4892
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has called operation <insert_5> from interface <insert_4> on object reference <insert_6>.
- Severity
- 0 : Information
- Explanation
- The CORBARequest node has made a call to CORBA.
- Response
- None.
- BIP4893
- IDL file <insert_1> has been deployed to integration server <insert_2>.
- Severity
- 0 : Information
- Explanation
- An IDL file has been deployed.
- Response
- None.
- BIP4894
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has called operation <insert_5> from interface <insert_4> on object reference <insert_6> and the CORBA exception <insert_7> has been thrown. The exception is propagated to the Error terminal.
- Severity
- 0 : Information
- Explanation
- Invocation of a CORBA operation has resulted in a CORBA exception, which might be a CORBA system exception or a user-defined exception.
- Response
- If the Error terminal is connected, no action is required. If the Error terminal is not connected, consider whether to handle the CORBA exceptions.
- BIP4895
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> is configured with IDL file <insert_4> and interface name <insert_5> and operation name <insert_6> but the operation cannot be found in the interface.
- Severity
- 20 : Error
- Explanation
- The interface cannot find the operation that is specified in the CORBARequest node properties.
- Response
- Ensure that the IDL file, Interface name, and Operation name properties of the node are correct. When you have verified these properties, redeploy the message flow.
- BIP4896
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has attempted to call operation <insert_4> but did not find a value for parameter <insert_5> in the tree.
- Severity
- 20 : Error
- Explanation
- To call a CORBA operation, you must put all the in and inout parameters in the tree. Parameter <insert_4> is missing from the tree.
- Response
- Correct the message flow or ensure that the incoming message has the correct structure.
- BIP4897
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has attempted to call operation <insert_4> but the value for parameter <insert_5> is not the correct type <insert_6>.
- Severity
- 20 : Error
- Explanation
- To call a CORBA operation, you must put all the in and inout parameters in the tree. The parameter types must be compatible.
- Response
- Correct the message flow or ensure that the incoming message has the correct structure.
- BIP4898
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has received a CORBA exception <insert_4>. If the Error terminal is not connected, no further processing occurs.
- Severity
- 10 : Warning
- Explanation
- CORBA exceptions are propagated to the Error terminal of the CORBARequest node. If the terminal is not connected, no further processing occurs.
- Response
- If you do not want to process exceptions, no further action is required. To handle exceptions, connect the Error terminal, and redeploy the message flow.
- BIP4899
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> is about to call operation <insert_5> from interface <insert_4> on object reference <insert_6>.
- Severity
- 0 : Information
- Explanation
- A CORBARequest node is about to make a call to CORBA.
- Response
- None.
- BIP4901
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has attempted to invoke operation <insert_5> but did not receive a valid body. The body <insert_5> was found but the operation body <insert_6> was not found.
- Severity
- 20 : Error
- Explanation
- The CORBARequest node gets the input parameters from the incoming tree but the node has not been able to find them.
- Response
- Correct the message flow or ensure that the incoming message has the correct structure.
- BIP4902
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to make an invocation using object reference <insert_4>.
- Severity
- 20 : Error
- Explanation
- The object reference that has been taken from the naming service has failed to be used by an invocation.
- Response
- Ensure the server has put a valid object reference in the naming service.
- BIP4903
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to call operation <insert_4>. Parameter <insert_5> contains a sequence that has a bound of <insert_6> but the incoming message contains <insert_7> items.
- Severity
- 20 : Error
- Explanation
- IDL sequences can be bounded; for example, sequence<long, 10>. The incoming message contains too many items for the sequence.
- Response
- Correct the message flow so that it does not create too many items for the sequence, then redeploy the flow.
- BIP4904
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to call operation <insert_4>. This operation contains the enum <insert_5> but the incoming message contains invalid value <insert_6>. The valid values are <insert_7>.
- Severity
- 20 : Error
- Explanation
- An IDL enum contains a set of valid values. The incoming message contains an invalid value for the enum.
- Response
- Correct the message flow so that the incoming message contains a valid value for the enum.
- BIP4905
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to call operation <insert_4> because the metadata is not valid. This error can happen if the IDL file <insert_5> is out of sync with the IDL file on the CORBA server.
- Severity
- 20 : Error
- Explanation
- The CORBARequest node has not been able to build a dynamic request to send to the CORBA server because the metadata is not valid.
- Response
- Ensure that the IDL that is referenced from the CORBA node matches the file on the CORBA server, and that you are using only supported types and constructs.
- BIP4906
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has called operation <insert_4> and the CORBA server has raised the unknown user-defined exception <insert_5>.
- Severity
- 20 : Error
- Explanation
- CORBA operations can raise user-defined exceptions. The CORBA server has raised an exception that is not inside the IDL file that is associated with the CORBARequest node.
- Response
- Ensure that the IDL that is referenced from the CORBA node matches the file on the CORBA server; in particular, check that the operation in question does not raise additional exceptions.
- BIP4907
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> attempted to call operation <insert_4> from interface <insert_5> in IDL file <insert_6> but operation <insert_7> is unsupported.
- Severity
- 20 : Error
- Explanation
- The operation is not supported. Check the information center to see which parts of CORBA are supported by IBM Integration Bus.
- Response
- Check the CORBA support topic in the information center to see which parts of CORBA are supported by IBM Integration Bus.
- BIP4908
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to find IDL construct <insert_4>. This construct must be in the IDL file.
- Severity
- 20 : Error
- Explanation
- The CORBA node has been unable to find a construct in its IDL file that is required to call an operation.
- Response
- Check that the IDL file is valid and that it contains only supported constructs.
- BIP4909
- CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3> has failed to call operation <insert_4>. Parameter <insert_5> contains the structure <insert_6> and structure member <insert_7> is missing from the incoming message.
- Severity
- 20 : Error
- Explanation
- When passing a structure in as an in or inout parameter, you must include all its members in the incoming message.
- Response
- Ensure that the incoming message contains all the structure members. If necessary, change the message flow, then redeploy it.
- BIP4910
- An error has occurred while parsing IDL file <insert_1>. A construct <insert_2> with the name <insert_3> was being parsed. The expected token is <insert_4> but the token in the file is <insert_5>.
- Severity
- 20 : Error
- Explanation
- CORBA nodes need valid IDL files that contain only constructs that IBM Integration Bus supports.
- Response
- Ensure that the IDL file is valid and that it contains only constructs that are supported by IBM Integration Bus.
- BIP4911
- An error has occurred while parsing IDL file <insert_1>. The error is <insert_2>.
- Severity
- 20 : Error
- Explanation
- CORBA nodes need valid IDL files that contain only constructs that IBM Integration Bus supports. If the integration node receives an error while parsing a supported construct, error message BIP4910 is issued.
- Response
- Ensure that the IDL file is valid and that it contains only constructs that are supported by IBM Integration Bus.
- BIP4912
- The Operation name property has been configured incorrectly for CORBARequest node <insert_1>.
- Severity
- 20 : Error
- Explanation
- The Operation name property for the node <insert_1> has been set to a null value or an empty string and is therefore not valid.
- Response
- The operation name can be configured by using a property on the node or in the local environment. If the name is set in both places, the local environment takes precedence over the node property.
- BIP4913
- The Operation name property for CORBARequest node <insert_1> in message flow <insert_2> has been overridden by the value <insert_3> in the local environment.
- Severity
- 0 : Information
- Explanation
- The Operation name property for a CORBARequest node can be overridden in the local environment.
- Response
- None.
- BIP4914
- The CORBARequest node <insert_1> in message flow <insert_2> has been configured with the configurable service <insert_3> and the Naming service property has been set to <insert_4>
- Severity
- 0 : Information
- Explanation
- CORBARequest nodes can be configured with a configurable service. The configurable service has been used to set a new value for the Naming service property.
- Response
- None.
- BIP4915
- The CORBARequest node <insert_1> in message flow <insert_2> has been configured with the configurable service <insert_3> and the Object reference name property has been set to <insert_4>
- Severity
- 0 : Information
- Explanation
- CORBARequest nodes can be configured with a configurable service. The configurable service has been used to set a new value for the object reference property.
- Response
- None.
- BIP4916
- The CORBARequest node <insert_1> in message flow <insert_2> has attempted to call the unsupported operation <insert_3>.
- Severity
- 0 : Information
- Explanation
- IBM Integration Bus supports a subset of CORBA. You have tried to call an operation that contains an unsupported type or a one-way operation.
- Response
- Modify your message flow to call only supported operations.
- BIP4917
- The IDL file <insert_1> contains the unsupported token <insert_2>.
- Severity
- 0 : Information
- Explanation
- IBM Integration Bus supports a subset of CORBA. You have tried to deploy an IDL file that contains an unsupported token.
- Response
- Remove any unsupported tokens from the IDL file. Check that the IDL file is still valid, then redeploy it.
- BIP4918
- The CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has been configured with operation <insert_4> from interface <insert_5> in IDL file <insert_6> but operation <insert_7> is not supported.
- Severity
- 10 : Warning
- Explanation
- The operation is not supported. Check the information center to see which parts of CORBA are supported by IBM Integration Bus.
- Response
- Check the CORBA support topic in the information center to see which parts of CORBA are supported by IBM Integration Bus. If you plan to use a local environment override to call a different operation, no action is required. Otherwise, modify and redeploy your message flow.
- BIP4919
- The CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has been configured with interface <insert_4> in IDL file <insert_5> but the operation is not supported.
- Severity
- 20 : Error
- Explanation
- The interface is not supported because it is abstract or uses inheritance. Check the information center to see which parts of CORBA are supported by IBM Integration Bus.
- Response
- Check the CORBA support topic in the information center to see which parts of CORBA are supported by IBM Integration Bus.
- BIP4920
- CORBARequest node <insert_1> in message flow <insert_2> in integration server <insert_3> has been configured with interface <insert_4> and has got the object reference <insert_5> but its repository ID is not the expected ID <insert_6>.
- Severity
- 10 : Warning
- Explanation
- Each CORBA interface has a repository ID, which is based on its scope in the IDL file. The object reference that has been resolved from the naming service repository ID is not the expected value.
- Response
- If your IDL file contains pragmas that change the repository ID, prefix, and ID, they are unsupported and ignored by IBM Integration Bus. This behavior might result in an error on the server or when making the request. If your IDL file contains no pragmas, check that you have configured the naming service and object reference properties correctly and that the object reference implements the interface that you have configured on the node.
- BIP4921
- An error occurred during processing of the IDL file for CORBA node <insert_1> in message flow <insert_2> in integration server <insert_3>.
- Severity
- 20 : Error
- Response
- Use associated error messages to identify the reason for the failure.
- BIP4922
- The IDL file <insert_1> does not contain a supported token.
- Severity
- 20 : Error
- Explanation
- A CORBA node could not parse the IDL file because none of the expected tokens were found.
- Response
- Ensure that the IDL file has not been corrupted.
- BIP4971
- EmailInput node <insert_1> is about to propagate an email and the following header is missing <insert_2>.
- Severity
- 10 : Warning
- Explanation
- An Email input node has propagated an Email with a missing header.
- Response
- This could mean that there are invalid Emails on the server. If this is a problem then contact your Email server administrator. If you are expecting this header to be missing then take no action.
- BIP4972
- An error occurred while the EmailInput node <insert_1> tried to process an email from the email server. The description of the error is: <insert_2>.
- Severity
- 20 : Error
- Explanation
- The EmailInput node <insert_1> has not been able to process an email.
- Response
- Review the content of the error and correct it. Contact your IBM Support Center if you require assistance in resolving the problem.
- BIP4973
- EmailInput node <insert_1> in message flow <insert_2> has received an email with content type <insert_3> and internal type <insert_4>, which the EmailInput node is not able to process.
- Severity
- 20 : Error
- Explanation
- An EmailInput node has received an email of an internal type that cannot be processed. Contact your IBM Support Center for further assistance.
- Response
- None
- BIP4974
- EmailInput node <insert_1> in message flow <insert_2> is using configurable service <insert_3>, and the EmailInput node property <insert_4> has been overridden with a configurable service property value of <insert_5>.
- Severity
- 0 : Information
- Explanation
- An EmailInput node can be configured to use the EmailServer configurable service. An EmailInput node property has been overridden by a value on the configurable service.
- Response
- None
- BIP4975
- Either the EmailInput node <insert_1> in message flow <insert_2> has been configured with Security identity property value <insert_3>, or the EmailServer configurable service has been configured with securityIdentity property value <insert_3>, which has not been defined by using the mqsisetdbparms command.
- Severity
- 20 : Error
- Explanation
- An EmailInput node or EmailServer configurable service has been configured with a security identity that contains a user ID and password for the email server but the security identity that has been defined does not exist.
- Response
- Either create the security identity by using the mqsisetdbparms command or correct the value of the security identity property that has been configured on the EmailInput node or the EmailServer configurable service.
When you use the mqsisetdbparms command to set user ID and password security credentials for an email server, ensure that you have specified email::<secId>. Where secId is the value of the Security identity property on the EmailInput node or in the -n securityIdentity property of the associated EmailServer configurable service. For example: mqsisetdbparms IBNODE -n email::<mySecurityIdentityObjectName> -u myUserID -p myPassword
- BIP4976
- EmailInput node <insert_1> in message flow <insert_2> is unable to communicate with email server <insert_3>. The error message is <insert_4>.
- Severity
- 20 : Error
- Explanation
- The EmailInput node cannot communicate with the email server.
- Response
- Ensure that the email server is running and is accessible from the system that IBM Integration Bus is running on. Also ensure that the Email Server property is correctly configured on the EmailInput node, or that the serverName property is correctly configured on the EmailServer configurable service.
- BIP4977
- EmailInput node <insert_1> in message flow <insert_2> has been configured with the configurable service <insert_3> but the configurable service does not exist.
- Severity
- 20 : Error
- Explanation
- You can optionally configure an EmailInput node with a EmailServer configurable service that the EmailInput node or message flow refers to at run time for connection information, instead of defining the connection properties on the node or the message flow. An EmailInput node has been configured with a configurable service that does not exist.
- Response
- Either modify the Email Server property on the EmailInput node to a configurable service that exists, or create the configurable service and redeploy your message flow.
- BIP4978
- Transfer command does not exist in the local environment.
- Severity
- 20 : Error
- Explanation
- In the local environment, no element exists with the name of the transfer command that has been called. This command cannot be run.
- Response
- Change the local environment to include a child element with the same name as the transfer command that you want to run. For example, to set the MKDIR command for pre transfer commands: set InputLocalEnvironment.Destination.File.Remote.Precommand[1].MKDIR = 'T4';
- BIP4979
- Either the EmailInput node <insert_1> in message flow <insert_2> has been configured with invalid email server URL <insert_3>, or the EmailServer configurable service has been configured with invalid email server URL <insert_3>.
- Severity
- 20 : Error
- Explanation
- The email server URL must be in the format <insert_protocol>://<insert_hostname>:<insert_port>. Where protocol can be pop3 or imap, where hostname can be the Internet Protocol version 4 (IPv4) TCP/IP address or DNS-resolvable host name of the email host, and where port is the port number that the email server is listening on for connections over Post Office Protocol 3 (POP3) or Internet Message Access Protocol (IMAP).
- Response
- Either modify the Email Server property on the EmailInput node to be a valid value, or modify the serverName property on the EmailServer configurable service, and redeploy the message flow.
- BIP4980
- Resource property <insert_1> cannot be changed to the value <insert_2> because the property is read only.
- Severity
- 20 : Error
- Explanation
- The property cannot be changed by modifying the resource directly. The property is read only and is set by the integration server.
- Response
- No action is required.
- BIP4981
- The model queue <insert_1>, which is required by the FTEInput and FTEOutput nodes, does not exist.
- Severity
- 20 : Error
- Explanation
- The nodes use the integration node system model queue <insert_1> to create queues needed for communication with the WebSphere MQ File Transfer Edition agent. The model queue is created when the integration node is created, or when an integration node is migrated from a previous release. If the integration node was created on version 7.0.0.0 of the product, the integration node tries to create the model queue when the agent is first used. This message means that the integration node could not create the queue. The SYSTEM.BROKER.MODEL.QUEUE will be used, but transfers sent from the agent will not persist if the agent is restarted.
- Response
- Create the model queue manually: "DEF qmodel(SYSTEM.BROKER.FTE.MODEL) DESCR('FTE MODEL QUEUE ') DEFPSIST(YES) DEFTYPE(PERMDYN) DEFSOPT(SHARED) MAXDEPTH(10000) MSGDLVSQ(FIFO) HARDENBO SHARE " or recreate the integration node.
- BIP4982
- Unable to create an agent name <insert_1>, which contains invalid characters.
- Severity
- 20 : Error
- Explanation
- The agent name is derived from a combination of the integration node name and the integration server name. WebSphere MQ File Transfer Edition can be correctly configured only if the agent name contains only the following characters: Uppercase A-Z, Lowercase a-z, Numerics 0-9, Period (.), Forward slash (/), Underscore (_), Percent sign (%).
- Response
- Either rename the integration server, or configure the agent to run in a different integration server that has a name that contains only allowed characters.
- BIP4983
- The FTE agent name is too long, and has been truncated from <insert_1> to <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The FTE agent name is derived from a combination of the integration node and integration server name. If the integration node name exceeds 12 characters, or the integration server exceeds 15 characters, they are truncated to form the agent name. This might result in two integration servers running an agent with the same name. If this happens, behavior is undefined. Both agents start successfully, and try to register with the coordination queue manager, but only one is correctly registered.
- Response
- Change the name of the integration server containing the agent to be within the required size limit.
- BIP4984
- No file could be found to process. Directory name: <insert_1>; file pattern: <insert_2>.
- Severity
- 20 : Error
- Explanation
- No file could be found to be read.
- Response
- Make sure the required file exists in the given directory.
- BIP4985
- Cannot process file <insert_1> in directory <insert_2> because of error <insert_3>.
- Severity
- 20 : Error
- Explanation
- The FileRead node found a file to process, but could not access it for the reason given.
- Response
- Make sure the file can be accessed.
- BIP4986
- Cannot process file <insert_1> in directory <insert_2> because it is already being processed by a <insert_3> node.
- Severity
- 20 : Error
- Explanation
- A FileRead node can not process files that a <insert_3> node is processing.
- Response
- Make sure that the FileRead node does not access to the same files as a <insert_3> node.
- BIP4987
- Starting to process file <insert_1> in directory <insert_2>.
- Severity
- 0 : Information
- Explanation
- A FileRead node has found a file to process.
- Response
- None.
- BIP4988
- The directory <insert_1> is not a valid directory name.
- Severity
- 0 : Information
- Explanation
- A FileRead node cannot access the directory because the directory name is invalid. The most likely cause is that the name contains invalid characters.
- Response
- Make sure that the directory name is valid for the system it is being used on.
- BIP4989
- <insert_2> files matching file pattern <insert_1> found in directory <insert_3>.
- Severity
- 20 : Error
- Explanation
- Multiple files in the specified directory match the file pattern. The FileRead node cannot determine which file to process.
- Response
- Make sure that the directory contains only one matching file.
- BIP4990
- The directory <insert_1> does not exist.
- Severity
- 20 : Error
- Explanation
- A FileRead node can not access the directory. Likely causes are that the directory does not exist, or the integration node does not have permission to access it.
- Response
- Make sure that the directory exists and that the integration node can access it.
- BIP4991
- File node <insert_1> in message flow <insert_2> can not access directory <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The file node failed to find the directory <insert_3>. Either the directory does not exist, or the integration node does not have permission to access it. The node will continue checking at every poll interval.
- Response
- Ensure that the input directory exists, and that its permissions are correctly set.
- BIP4992
- Cannot move file <insert_1> to directory <insert_2> because it already exists in that directory.
- Severity
- 20 : Error
- Explanation
- The file cannot be overwritten.
- Response
- Remove the file from the directory and retry.
- BIP4993
- Unsupported <insert_1> command ' <insert_2> for a pre or post command. Supported commands are <insert_3>.
- Severity
- 20 : Error
- Explanation
- The specified command is not supported for a <insert_1> pre or post command.
- Response
- Change the pre or post command to one of the following, supported commands: <insert_3>.
- BIP4994
- Error executing <insert_1> command <insert_2> on remote server. Error details: <insert_3>.
- Severity
- 20 : Error
- Explanation
- An error occurred trying to run a <insert_1> command.
- Response
- Review the cause of the <insert_1> error. To ignore errors from a pre transfer or post transfer command, set the IgnoreError flag in the local environment to true (For example: set InputLocalEnvironment.Destination.File.Remote.Postcommand[1].IgnoreErrors = 'true';).
- BIP4995
- Incorrect parameter type for transfer command <insert_1>. Value given is <insert_3> for Field <insert_2> but a integer value is required.
- Severity
- 20 : Error
- Explanation
- The command given requires an integer value for it's <insert_2> field.
- Response
- Change the given field to have the correct type.
- BIP4996
- Transfer command <insert_1> includes a child element called <insert_2>.
- Severity
- 20 : Error
- Explanation
- The specified requires no child elements.
- Response
- Change the specified command to include no child elements. For example, the MKDIR command can be created using set InputLocalEnvironment.Destination.File.Remote.Precommand[1].MKDIR = 'T4' but MKDIR must include no child elements.
- BIP4997
- Transfer command <insert_1> has not been given a value.
- Severity
- 20 : Error
- Explanation
- The specified command must be given a value.
- Response
- Change the specified command to have a valid value. For example, the MKDIR command can be created using set InputLocalEnvironment.Destination.File.Remote.Precommand[1].MKDIR = 'T4' where T4 is the value of the command.
- BIP4998
- Transfer command <insert_1> is missing the child element <insert_2>.
- Severity
- 20 : Error
- Explanation
- The specified command must include the specified child element, and the specified child element must be set to the correct value.
- Response
- Change the specified command to include a valid child element. For example, the Rename command must include a From child element, and a To child element.
- BIP4999
- Transfer command <insert_1> includes the child element <insert_2>. This child element is not valid.
- Severity
- 20 : Error
- Explanation
- The specified command must include only the valid child elements.
- Response
- Change the specified command to include only valid child elements. For example, the Rename command must include only a From child element and a To child element.