BIP6000-6999: Runtime components - IBM MQ parsers

BIP6001
Cannot find MQSI_PARAMETERS_FILE environment variable.
Severity
20 : Error
Explanation
In order to parse messages using the
eon. parser, the MQSI_PARAMETERS_FILE environment variable must give the location of the parameters file giving the connection information for the database containing the
eon. format definitions.
Response
Set the MQSI_PARAMETERS_FILE environment variable to provide the location of the parameters file. To enable the environment variable definition to take effect on an AIX or Solaris system, restart the integration node in the new environment. On an NT system, reboot the machine.

BIP6002
Cannot open
eon. parameters file <insert_1>.
Severity
20 : Error
Explanation
In order to parse messages using the
eon. parser, the MQSI_PARAMETERS_FILE environment variable must give the location of the parameters file giving the connection information for the database containing the
eon. format definitions.
Response
Correct the value of the MQSI_PARAMETERS_FILE environment variable to contain the full path to the
eon. parameters file. On an NT system it will be necessary to reboot the machine in order for the change to have any effect

BIP6003
Error <insert_1> : <insert_2> connecting to
eon. format database with session <insert_3>.
Severity
20 : Error
Explanation
A database session could not be created using the specified session name, <insert_3>. The specific error was <insert_1> : <insert_2>.
Response
Check that the NN_CONFIG_FILE_PATH environment variable is set, and that the directory to which it points contains an nnsyreg.dat file appropriately configured for the above named session. It is necessary to stop and restart the integration node to ensure that any changes that are made to fix this problem are seen by the integration node.

BIP6004
Unsupported
eon. control message received.
Severity
20 : Error
Explanation
A message was received which specified one of the unsupported options OPT_SHUTDOWN or OPT_RELOAD_RULESET in the option buffer of the MQRFH header.
Response
The integration node can be shut down using the normal IBM Integration Bus mechanisms. In order to reload a ruleset a configuration message must be sent to the normal integration node configuration queue, this can be performed using the mqsireload command. See the IBM Integration Bus online documentation for more details on both of these operations.

BIP6005

eon. parser failed to process message: input format <insert_1>; error code <insert_2>; error text <insert_3>.
Severity
20 : Error
Explanation
When processing the message using input format <insert_1>,
eon. reported an error.
The
eon. error code was <insert_2>.
The
eon. error text was <insert_3>.
Response
See the
eon. manuals for further information.

BIP6007
Error connecting to
eon. format database using session name <insert_1>.
Severity
20 : Error
Explanation
A database session could not be created using the specified session name, <insert_1>. There was no further information regarding the cause of the connection failure.
Response
Check that the NN_CONFIG_FILE_PATH environment variable is set, and that the directory to which it points contains an nnsyreg.dat file appropriately configured for the above named session. It is necessary to stop and restart the integration node to ensure that any changes that are made to fix this problem are seen by the integration node.

BIP6008
Error parsing
eon. parameters file <insert_1> at column <insert_3> on line <insert_2>.
Severity
20 : Error
Explanation
The configuration file giving the database connection information for the
eon. rules and format database was of an invalid format. The error occurred at column <insert_3> on line <insert_2>.
Response
Ensure that the file name given has the expected value. If not, change the value of the MQSI_PARAMETERS_FILE environment variable to the correct value, and reboot the machine. If the correct file is being read, check the IBM Integration Bus documentation for the correct format for the file, correct the error and resend the message that prompted the failure. Changes to the file will be picked the next time it is necessary to connect to the
eon. database.

BIP6009
Illegal modification of a
eon. message.
Severity
20 : Error
Explanation
Generating messages which have a 'NNSY' body using a Compute node is not supported.
If the message did not originate from a Compute node, this message indicates an internal error.
Response
Rewrite the message flow so that it does not attempt to generate
eon. messages from a Compute node.

BIP6021
The RFH option buffer length was <insert_1>, however no name/value data was present.
Severity
20 : Error
Explanation
The buffer length was <insert_1>, however no name/value pairs were found in the option buffer.
Response
Consult the support team responsible for the application generating the RFH messages.

BIP6022
Name <insert_1> has no associated value.
Severity
20 : Error
Explanation
A name was found in the name/value option buffer with no associated value.
Response
Check the application that generated the message.

BIP6041
Bitstream cannot be aligned to a four byte boundary in codepage <insert_1>.
Severity
20 : Error
Explanation
The bitstream for this parser should be aligned on a four byte boundary. However after conversion to the requested codepage it was not possible to do so.
Response
Either change the codepage to an SBCS codepage or change the content of the message.

BIP6042
End of message reached unexpectedly at offset <insert_1>.
Severity
20 : Error
Explanation
The end of the message was encountered before the message was syntactically complete.
Response
Correct the application (or compute expression) that generated the message.

BIP6043
Invalid folder size of <insert_1> detected within a WebSphere MQ MQRFH2 header.
Severity
20 : Error
Explanation
The folder size defined in an MQRFH2 header must be a multiple of four bytes, and must not be negative. The message being processed does not conform to this rule.
Response
Correct the application or the compute expression that generated the message.

BIP6044
Folder size of <insert_1> exceeds the size of the message.
Severity
20 : Error
Explanation
The folder size as given in the message would extend beyond the end of the message bitstream.
Response
Correct the application (or compute expression) that generated the message.

BIP6045
Value at offset <insert_1> must start with single or double quote: data just before error is <insert_2>; data just after error is <insert_3>.
Severity
20 : Error
Explanation
Attribute Values in the option buffer must start with a single or a double quote. The value at the message offset indicated did not.
Response
Correct the application (or compute expression) that generated the message.

BIP6046
Mismatched start and end tags at offset <insert_1>: data just before the error is <insert_2>; data just after the error is <insert_3>.
Severity
20 : Error
Explanation
The MQRFH2 parser encountered an end tag that did not match the currently open start tag in the name-value data area. The offset is from the beginning of the name-value length field which precedes the name-value data field that contains the error.
Response
Correct the application or the compute expression that generated the message.

BIP6047
Syntax error in attribute specification at offset <insert_1>: data just before the error is <insert_2>; data just after the error is <insert_3>.
Severity
20 : Error
Explanation
The MQRFH2 parser expected an '=' following the attribute name at the offset indicated.
Response
Correct the application or the compute expression that generated the message.

BIP6048
Error occurred at offset <insert_1> in the MQRFH2 name-value data area.
Severity
20 : Error
Explanation
An error occurred in the name-value data area. This message gives the location of the error in the option buffer. The offset is from the beginning of the name-value length field which precedes the name-value data field that contains the error.
Response
Correct the application or the compute expression that generated the message.

BIP6049
A folder was incompletely nested at offset <insert_1>.
Severity
20 : Error
Explanation
When processing the MQRFH2 header, a folder was encountered that was not correctly nested. Possible causes include missing or multiple end tags.
Response
Correct the application or the compute expression that generated the message.

BIP6050
A folder had an incorrect name specification at offset <insert_1>.
Severity
10 : Warning
Explanation
There is a syntax error in the folder at offset <insert_1>. A tag name was terminated with an invalid character.
Response
Correct the application (or compute expression) that generated the message.

BIP6060
Node <insert_4> used parser type <insert_1> to process a portion of the incoming message of length <insert_3> bytes beginning at offset <insert_2>.
Severity
0 : Information

BIP6061
Node <insert_5> used parser type <insert_1> to process a portion of the incoming message of length <insert_3> bytes beginning at offset <insert_2>. The parser type was selected based on value <insert_4> from the previous parser.
Severity
0 : Information

BIP6062
Invalid message body/header sequence <insert_2>/<insert_1> encountered by node <insert_3>.
Severity
10 : Warning
Explanation
The integration node has encountered a message body of type <insert_2> followed by a message header of type <insert_1>. It is not valid to have message headers following message bodies.
Response
Identify the source of the invalid message.

BIP6063
Node <insert_3> used parser type <insert_1> to process the input stream, beginning at offset <insert_2>.
Severity
0 : Information

BIP6064
Node <insert_4> used parser type <insert_1> to process the input stream, beginning at offset <insert_2>. The parser type was selected based on value <insert_3> from the previous parser.
Severity
0 : Information

BIP6065
A stream source was asked to provide all of its data.
Severity
10 : Warning
Explanation
The input transport is capable of providing input data through a stream. This allows portions of the input data to be read as required, so using less memory than transports that retrieve all of the data.
Although the input transport can read the data through a stream, the data is being passed to a component in the integration node that requires all of the data be read in.
If the input data is large, there might be increased memory usage within this integration server.
Response
To help reduce memory usage, modify the message flow so that data provided by a stream is not passed to components in the integration node that cannot process streams. In particular:
Avoid passing the data to parsers other than XMLNSC, JSON, MRM TDS and MRM CWF.
Avoid using ESQL functions, such as ASBITSTREAM and BITSTREAM, that request all of the data.
Avoid passing data to user-defined nodes and parsers.
Avoid passing the data to transports that do not support streams.

BIP6066
The <insert_1> parser could not parse the bitstream into a sequence of records. This type of parser does not support the Parsed Record Sequence option for the Record Detection parameter.
Severity
20 : Error
Explanation
In a FileInput node, the Record Detection parameter was set to Parsed Record Sequence on the Records and Elements tab so that the node propagates each matching structure as a separate message.
The message domain selected on the Inbound Message Parsing tab does not support this option. This option is only supported with the XMLNSC, JSON, MRM TDS and MRM CWF parsers.
Response
To avoid this problem, do one of the following:
Modify the Record Detection parameter on the Records and Elements tab so that the parser selected on the Inbound Message Parsing tab can be used.
Modify the Message domain parameter on the Inbound Message Parsing tab so that the XMLNSC, JSON, MRM TDS or MRM CWF parser is used.

BIP6067
The <insert_1> parser could not parse the bitstream into a sequence of records because no bytes were parsed for the current record.
Severity
20 : Error
Explanation
In a FileInput node, the Record Detection parameter was set to Parsed Record Sequence on the Records and Elements tab so that the node propagates each matching structure as a separate message.
For this processing to be successful, at least one byte must be parsed per record.
Response
Modify the bitstream, message model, or both so that at least one byte can be parsed per record.

BIP6068
A request was made to serialize a bitstream from element <insert_1> using parser <insert_2>. The result was zero bytes long.
Severity
10 : Warning
Explanation
The node or ESQL ASBITSTREAM function requested that an element serialize its bitstream and this resulted in no bytes being written.
Response
If the output bitstream should not have been zero bytes long, ensure that the correct element was specified.
If the parser name is blank or set to a root parser, associate an owning parser with the element:
If created in ESQL, the DOMAIN clause of the CREATE statement can be used.
If created using the user-defined extension API use a method that allows a parser to be specified.

BIP6069
The integration node is not capable of handling a message of data type <insert_1>.
Severity
10 : Warning
Explanation
The integration node received a message that requires the handling of data of type <insert_1>, but the integration node does not have the capability to handle data of this type.
Response
Check both the message being sent to the integration node and the configuration data for the node. References to the unsupported data type must be removed if the message is to be processed by the integration node.

BIP6070
The integration node cannot handle a message of data type <insert_1> because the current fix pack function level of <insert_2> does not support this parser. Use 'mqsichangebroker integrationNodename -f all' to enable this functionality.
Severity
10 : Warning
Explanation
The integration node received a message that requires the handling of data of type <insert_1>. The integration node cannot handle messages of this type because new functionality has not been enabled for this integration node. Use 'mqsichangebroker integrationNodename -f all' to enable this (and all other) functionality.
Response
Either change the flow to avoid using the unavailable parser, or enable new functionality using the mqsichangebroker command.

BIP6081
The bit stream contains an unrecognized entity at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
An ampersand (&) was found in the bit stream, but it does not introduce a valid, recognized entity for substitution.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6082
Invalid target element. Type = <insert_1>, Name = <insert_2>, value = <insert_3>.
Severity
20 : Error
Explanation
The target element of a folder bit-stream operation must be a name element and may not have a value. The supplied target did not meet this requirement.
Response
Ensure that the field reference used to identify the target element correctly addresses a name element.

BIP6083
Invalid character in element name at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
The set of characters that can be used for element names is restricted.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6084
End of message reached unexpectedly at offset <insert_1>. The preceding text is <insert_2>.
Severity
20 : Error
Explanation
The end of the message was encountered before the message was syntactically complete.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6085
Syntax error in attribute specification at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
An '=' is required between an attribute name and its value.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6086
Invalid character at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
Attribute values must be enclosed in single or double quotes.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6087
Mismatched start and end tags at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
An end tag name that does not match the matching start tag name was encountered.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6088
Syntax error at offset <insert_1>. The preceding text is <insert_2> and the following text is <insert_3>.
Severity
20 : Error
Explanation
End tags must end with the sequence '/>'. '/' was encountered, but is not followed by '>'.
Response
Examine the bit stream and determine why an invalid bit stream was supplied.

BIP6089
An error occurred whilst parsing in a bit-stream of type <insert_1>.
Severity
20 : Error
Explanation
See the following messages for details of the error.
Response
Examine the bit-stream and determine why an invalid bit-stream was supplied.

BIP6090
Generic expression: Column <insert_1> in row <insert_2> within the namespace map, owned by node <insert_3>, is missing a value.
Severity
20 : Error
Explanation
The namespace map cannot be processed. This is an internal error.
Response
Contact your IBM support center.

BIP6091
Generic expression: The value of column <insert_1> in row <insert_2> within namespace map, owned by node <insert_3>, was expected to be a character string.
Severity
20 : Error
Explanation
The namespace map cannot be processed. This is an internal error.
Response
Contact your IBM support center.

BIP6092
In the namespace map owned by node <insert_2> the prefix <insert_1> is associated with more than one namespace URI.
Severity
20 : Error
Explanation
This is an internal error. The namespace map should not contain more than one entry for a namespace prefix.
Response
Open the namespace map for the node in the flow editor and delete any duplicate entries. Contact your IBM support center if you are unable to determine the cause of the problem.

BIP6093
Generic expression: XPath expressions do not require message objects assigned as variable values.
Severity
20 : Error
Explanation
An attempt was made to assign a message to a variable name, in node <insert_1>.
Response
None.

BIP6094
Generic expression: ImbXPathValue cannot be created. The value is not a known ImbValue type.
Severity
20 : Error
Explanation
None.
Response
None.

BIP6095
Generic expression: ImbXPathValue cannot be created. The value has an incorrect ImbValue state.
Severity
20 : Error
Explanation
None.
Response
None.

BIP6096
Generic expression: ESQL expressions do not require XPath value objects assigned as variable values.
Severity
20 : Error
Explanation
An attempt was made to assign an XPath value to a variable name, in node <insert_1>.
Response
None.

BIP6097
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire either the input root message, its owning message group, or the context.
Severity
20 : Error
Explanation
None
Response
None.

BIP6098
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire the input local environment message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6099
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire the input exception list message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6101
An error has occurred in the <insert_1> parser when reading a message.
Severity
20 : Error
Explanation
The parser has encountered an error whilst trying to read a part of the message or message header.
Response
Check the application that generated the message to ensure that the message is well formed. If the problem persists, you should report it to the support organization responsible for the parser that detected the error. If this is an IBM supplied parser, you should contact your IBM support center.

BIP6102
An error has occurred in parser <insert_1> when generating the message.
Severity
20 : Error
Explanation
An error has occurred in the parser when it was attempting to create a bitstream representation of the message. Either the element tree is incorrect for this parser type or the parser is in error.
Response
Correct the application or compute expression that generated the element tree.

BIP6103
Parser <insert_1> has encountered an error.
Severity
20 : Error
Explanation
The parser has encountered an error. More details are given by further error messages. This message is issued to enable the application to identify the failing parser.
Response
Analyze the information contained in the following messages and act accordingly.

BIP6104
Lack of system resources, integration node failed to allocate memory.
Severity
20 : Error
Explanation
An attempt to allocated memory was denied by the operating system. You should allocate more paging space before the integration node is restarted.
Response
This is a fatal error and the integration node needs to be restarted.

BIP6105
The remaining bitstream is too small to contain an <insert_1> structure.
Severity
20 : Error
Explanation
The bitstream, as presented to the <insert_2> parser, is too small to contain a structure of type <insert_1>. The message appears to have been truncated.
Response
Check with the support group responsible for the parser in question.

BIP6106
Length of parser field name <insert_1> was <insert_2>. It should be <insert_3>.
Severity
20 : Error
Explanation
The length of the value does not match the required length for the field.
Response
Correct the application (or compute expression) that generated the message.

BIP6107
The value of field name <insert_1> must be a boolean, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of the element must be boolean for field name <insert_1>.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6108
The value of field name <insert_1> must be a byte string, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of element for this field must be a byte string.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6109
The value of field name <insert_1> must be a character string, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of this element must be a character string for this field.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6110
The value of field name <insert_1> must be a date, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of element for this field must be a date.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6111
The value of field name <insert_1> must be a time stamp, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of element for this field must be a time stamp.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6112
The value of field name <insert_1> must be a time, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of element for this field must be a time.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6113
The value of field name <insert_1> must an integer, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of this element must be an integer for this field.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6114
The value of field name <insert_1> must be an interval, its value was <insert_2>.
Severity
20 : Error
Explanation
The type of this element must be an interval for this field.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6115
Unconvertible field value for <insert_1>.
Severity
20 : Error
Explanation
The element for a field could not be converted to the required type.
Response
Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

BIP6116
Integration node internal program error.
Severity
20 : Error
Explanation
An attempt was made to parse a message but no parse buffer was supplied. This is an internal error in the parser.
Response
Contact your IBM support center.

BIP6117
Internal parser error.
Severity
20 : Error
Explanation
An internal parser error has been detected.
Response
You should report this problem to the support organization responsible for the parser that detected the error. If this is an IBM supplied parser, you should contact your IBM support center.

BIP6118
The remaining bitstream is too small to contain the indicated structure.
Severity
20 : Error
Explanation
The bitstream, as presented to the <insert_2> parser, is too small to contain the <insert_1> structure. The length of this structure as given in the structure header is <insert_3>. The message appears to have been truncated.
Response
Check with the support group responsible for the parser in question.

BIP6119
The bitstream for <insert_1> contained an unrecognized entity.
Severity
20 : Error
Explanation
An ampersand was found in the bitstream but did not introduce a valid, recognized entity for substitution.
Response
Check with the support group responsible for the parser in question.

BIP6121
Command and Response not valid for Type field of a parameter.
Severity
20 : Error
Explanation
You have specified either Command or Response in the Type field of a Parameter. These two values are only valid for the Type field of the Command not the type field of a parameter.
Response
You should contact the support group responsible for maintaining the application that generated the error, or the support group responsible for your Compute node SQL expression depending on the source of the erroneous message.

BIP6122
Parameter type of <insert_1> for PCF headers is not handled by the PCF parser.
Severity
20 : Error
Explanation
The parameter type specified is not valid when used in the command header.
Response
The message flow processing the message must be modified to avoid referencing or setting the contents of the WebSphere MQ PCF header containing the unsupported parameter type.

BIP6123
Can not load MQ libraries from Installation Path (<insert_1>) due to error (<insert_2>). Removing the MQ symbolic links within /usr/lib via the MQ command dltmqlnk may resolve the problem.
Severity
20 : Error
Explanation
Can not load MQ libraries from Installation Path (<insert_1>) due to error (<insert_2>).
Response
Removing the MQ symbolic links within /usr/lib via the MQ command dltmqlnk may resolve the problem.

BIP6124
Can not load MQ libraries from Installation Path (<insert_1>) due to error (<insert_2>).
Severity
20 : Error
Explanation
Can not load MQ libraries from Installation Path (<insert_1>) due to error (<insert_2>).
Response
Ensure that the MQ libraries install path points to a valid set of MQ libraries.

BIP6220
Parser class <insert_1> already exists.
Severity
0 : Information
Explanation
A user-defined parser factory has attempted to define a parser class, but a parser class of that name already exists. The request is rejected.
Response
Ensure that the parser class names do not clash.

BIP6221
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire the environment message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6222
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire either the output root message, its owning message group and context, or the environment message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6223
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire either the output local environment, its owning message group and context, or the environment message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6224
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire either the output exception list message, its owning message group and context, or the environment message.
Severity
20 : Error
Explanation
None
Response
None.

BIP6225
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It was not possible to acquire either the environment message, its owning message group, or its context.
Severity
20 : Error
Explanation
None
Response
None.

BIP6226
Generic expression: The ESQL expression, in node <insert_1>, cannot be evaluated. It required navigation to an output tree that was not supplied to us.
Severity
20 : Error
Explanation
None
Response
None.

BIP6227
Generic expression: The MessageAssembly type could not be recognized. An incorrect variable name <insert_1> was provided for an assigned MessageAssembly.
Severity
20 : Error
Explanation
None
Response
None.

BIP6228
Generic expression: It was not possible to parse the XPath expression, in node <insert_1>. An incorrect XPath expression was supplied. An XPath location step was expected.
Severity
20 : Error
Explanation
None
Response
None.

BIP6229
Generic expression: It was not possible to parse an ESQL expression, in node <insert_1>. An incorrect ESQL expression was supplied. An ESQL path element was expected.
Severity
20 : Error
Explanation
None
Response
None.

BIP6230
Generic expression: It was not possible to parse an expression, in node <insert_1>. An incorrect expression was supplied: <insert_2>.
Severity
20 : Error
Explanation
None
Response
None.

BIP6231
An error occurred in node: <insert_1>1 Exception details: <insert_2>2
Severity
20 : Error
Explanation
An error message was generated by the node.
Response
Contact your IBM support center if you are unable to determine the cause of the problem.

BIP6232
An error occurred in node: <insert_1>1 There was a problem loading database driver class: <insert_2>2 Exception details: <insert_3>3
Severity
20 : Error
Explanation
The node was unable to load the specified JDBC driver class.
Response
Contact your IBM Integration Bus administrator.

BIP6233
An error occurred in node: <insert_1>1 There was a problem establishing a connection to the given database URL: <insert_2>2 Exception details: <insert_3>3
Severity
20 : Error
Explanation
The node was unable to establish a connection to the given database URL.
Response
Contact your IBM Integration Bus administrator.

BIP6234
Error in node: <insert_1>1 There was a problem setting an auto-commit mode to a given state for connection. Exception details: <insert_2>2
Severity
20 : Error
Explanation
The node was unable to switch off database transactional support for an acquired JDBC database connection. This node performs only read-only interactions with a given data source.
Response
Contact your IBM Integration Bus administrator.

BIP6235
Error in node: <insert_1>1 There was a problem releasing a JDBC connection. Exception details: <insert_2>2
Severity
20 : Error
Explanation
The node was unable to release an acquired JDBC database connection.
Response
Contact your IBM Integration Bus administrator.

BIP6236
Error in node: <insert_1>1 There was a problem creating a prepared statement: <insert_2>2 Exception details: <insert_3>3
Severity
20 : Error
Explanation
The node was unable to create a prepared statement on an acquired JDBC connection.
Response
Contact your IBM Integration Bus administrator.

BIP6237
Error in node: <insert_1>1 A problem was encountered during management of acquired JDBC connections. Exception details: <insert_2>2
Severity
20 : Error
Explanation
The node was unable to retrieve JDBC connection details.
Response
Contact your IBM Integration Bus administrator.

BIP6238
Error in node: <insert_1>. Prepared statement: <insert_2>. A problem was encountered during processing of a result set returned from a database query. An unsupported value type <insert_3> was returned for column <insert_4>.
Severity
20 : Error
Explanation
The node was unable to convert and store the result returned for column <insert_4>.
Response
Contact your IBM Integration Bus administrator.

BIP6239
Error in node: <insert_1>. A problem was encountered while closing a prepared statement owned by an idle JDBC connection. Prepared statement: <insert_2>. Exception details: <insert_3>.
Severity
20 : Error
Explanation
The node was unable to immediately release database and JDBC resources owned by a statement object.
Response
Contact your IBM Integration Bus administrator.

BIP6240
Error in node: <insert_1>. A problem was encountered while storing column values that were returned in a result set from a JDBC database query. Prepared statement: <insert_2>. Exception details: <insert_3>3
Severity
20 : Error
Explanation
None
Response
Contact your IBM Integration Bus administrator.

BIP6241
Error in node: <insert_1>. A problem was encountered during execution of prepared statement: <insert_2>. Exception details: <insert_3>.
Severity
20 : Error
Explanation
Either a database access error has occurred, or the SQL statement did not return a result set.
Response
Contact your IBM Integration Bus administrator.

BIP6242
Error in node: <insert_1>. A problem was encountered during execution of a prepared statement that includes parameter inserts: <insert_2>. Exception details: <insert_3>.
Severity
20 : Error
Explanation
Either a problem was encountered while setting values for the JDBC SQL query parameter inserts in the above statement, or during query execution a database access error occurred, or the SQL statement did not return a result set.
Response
Contact your IBM Integration Bus administrator.

BIP6243
Error in node: <insert_1>. A problem was encountered when closing a result set returned from a query using a prepared statement: <insert_2>. Exception details: <insert_3>3
Severity
20 : Error
Explanation
The node was unable to immediately release database and JDBC resources owned by a ResultSet object.
Response
Contact your IBM Integration Bus administrator.

BIP6244
Error in node: <insert_1>. A problem was encountered inserting parameter values into prepared statement: <insert_2>.
Severity
20 : Error
Explanation
The node was unable to insert a value for parameter <insert_3> into the prepared statement. The parameter value acquired from an integration node tree element is an unsupported object type <insert_4>.
Response
Contact your IBM Integration Bus administrator.

BIP6245
Error in node: <insert_1>. A problem was encountered inserting parameter values into prepared statement: <insert_2>.
Severity
20 : Error
Explanation
The node was unable to insert a value for parameter <insert_3> into the prepared statement. It is not possible to use a parameter value acquired from an integration node tree element that does not have a valid value state. The value state of the element is <insert_4>.
Response
Contact your IBM Integration Bus administrator.

BIP6246
Error in node: <insert_1>. A problem was encountered inserting parameter values into prepared statement: <insert_2>.
Severity
20 : Error
Explanation
The node was unable to insert a value for parameter <insert_3> into the prepared statement. It is not possible to use a parameter value acquired from an integration node tree element that is of an unknown type. The element type is <insert_4>.
Response
Contact your IBM Integration Bus administrator.

BIP6247
Error in node: <insert_1>. A problem was encountered evaluating general expression <insert_2>, which was given for the <insert_3> element value in the query element table for this node.
Severity
20 : Error
Explanation
The node evaluated the provided expression against the incoming message tree, but the result of the expression has returned an empty list containing no integration node tree elements.
Response
Examine the provided expression to confirm that it is correct.

BIP6248
Error in node: <insert_1>. A problem was encountered evaluating general expression <insert_2>, which was given for the <insert_3> element value in the query element table for this node.
Severity
20 : Error
Explanation
The node evaluated the provided expression against the incoming message tree, but the result of the expression has returned null. A single element, double, boolean or string value was expected to be returned.
Response
Examine the provided expression to confirm that it is correct.

BIP6249
Error in node: <insert_1>. A problem was encountered evaluating read-write path expression <insert_2>, which was given for the <insert_3> data element expression in the data element table for this node.
Severity
20 : Error
Explanation
The node evaluated the provided expression against the outgoing message tree, but the result of the expression has returned an element list where the first element is null. A single element value was expected to be returned.
Response
Examine the provided expression to confirm that it is correct.

BIP6250
Error in node: <insert_1>. A problem was encountered evaluating the result set from prepared statement: <insert_2>, which was given for the <insert_3> data element expression in the data element table for this node.
Severity
20 : Error
Explanation
The node evaluated the result set for column <insert_3>, for data element table row entry <insert_4>. A value was expected, but none was found for this column in the set.
Response
Examine the provided prepared statement to confirm that it is correct.

BIP6251
Error in node: <insert_1>. A problem was encountered evaluating read-write path expression <insert_2>, which was given for the <insert_3> data element expression in the data element table for this node.
Severity
20 : Error
Explanation
The node evaluated the provided expression against the outgoing message tree, but the result of the expression has returned either null or an empty element list, or has not returned an element list object.
Response
Examine the provided expression to confirm that it is correct.

BIP6252
Error in node: <insert_1>. A problem was encountered evaluating general expression <insert_2>, which was given for the <insert_3> element value in the query element table for this node.
Severity
20 : Error
Explanation
The node evaluated the provided expression against the incoming message tree, but the result of the expression has returned an element list where the first element is null. A single element value was expected to be returned.
Response
Examine the provided expression to confirm that it is correct.

BIP6253
Error in node: <insert_1>. Could not locate JDBC Provider entry <insert_2> in the integration node registry, which was given for the data source name property for this node.
Severity
20 : Error
Explanation
The node can not establish a connection with a database if the provided JDBC data source definition is not present as an entry in the registry associated with the integration node.
Response
Examine the data source name provided on the node and ensure the value given matches an existing JDBC Provider registry entry for the integration node concerned.

BIP6254
Evaluating the contents of a result set returned from a database query in node: <insert_4>.
Severity
0 : Information
Explanation
Extracting an SQL data type <insert_1> for qualified database column name <insert_3> returned for row number <insert_2> in the result set.
Response
No user action required.

BIP6255
Evaluating the contents of a result set returned from a database query in node: <insert_1>.
Severity
0 : Information
Explanation
Extracting a value of <insert_3> for qualified database column name <insert_2>.
Response
No user action required.

BIP6256
When evaluating the contents of a result set returned from a database query in node: <insert_1>, the SQL select statement failed to produce a match.
Severity
10 : Warning
Explanation
A problem was encountered processing the results set returned for a database query performed by this node. There are no rows present in the result set.
Response
The SQL select statement issued by this node has produced an empty result set, indicating that the test conditions forming the query were not satisfied. As a consequence this node will pass its original message unchanged down the 'keyNotFound' output terminal for the node. This condition may have been expected, in which case no further action is required. Alternatively, you can further refine the SQL query configured for this node, in order to improve the chances of the test conditions within the WHERE clause being satisfied.

BIP6257
Executing a prepared SQL query against a database connected to by node: <insert_1>.
Severity
0 : Information
Explanation
The SQL query statement is <insert_2>.
Response
No user action required.

BIP6258
Executing a prepared SQL query with parameters against a database connected to by node: <insert_1>.
Severity
0 : Information
Explanation
The parameterized SQL query statement is <insert_2>.
Response
No user action required.

BIP6259
Setting the value of a designated parameter within a prepared parameterized SQL query used by node: <insert_6>.
Severity
0 : Information
Explanation
Setting a value of type <insert_1> for a parameter at position <insert_2> with a value of <insert_3>. This parameter has a target SQL type of <insert_4> and a target scale value of <insert_5>.
Response
No user action required.

BIP6260
Setting the value of a designated parameter within node: <insert_1>.
Severity
0 : Information
Explanation
Setting value of <insert_2> into parameter.
Response
No user action required.

BIP6261
Loading the JDBC driver class for node: <insert_1>.
Severity
0 : Information
Explanation
The JDBC driver class named <insert_2> was loaded, with major number version <insert_3> and minor number version <insert_4>. The driver is a genuine JDBC Compliant driver: <insert_5>.
Response
No user action required.

BIP6262
Using a JDBC connection URL to connect to the JDBC driver class for node: <insert_1>.
Severity
0 : Information
Explanation
The JDBC connection URL is <insert_2>.
Response
No user action required.

BIP6263
Error in node: <insert_1>. A problem was encountered obtaining a JDBC connection for this node.
Severity
20 : Error
Explanation
The node has made attempts to make a database connection to the given URL <insert_3>. The loaded JDBC driver class <insert_2> is the wrong kind of driver to connect to the given URL.
Response
Examine the data source name provided on the node and ensure that the given value matches an existing JDBC Provider registry entry for the integration node concerned. Examine the details associated with the JDBC Provider entry in the registry, to ensure they are correct. Examine your environment to ensure that only one driver is being loaded and that it is the correct driver for the connection URL given in the JDBC Provider entry. Contact your IBM support center if you are unable to determine the cause of the problem.

BIP6264
Setting the value of a designated parameter within a prepared parameterized SQL query used by node: <insert_4>.
Severity
0 : Information
Explanation
Setting value of type <insert_1> for parameter at position <insert_2> with a value of <insert_3>.
Response
No user action required.

BIP6265
A problem was encountered when committing a transaction with the JDBC Datasource <insert_1>.
Severity
20 : Error
Explanation
The node was unable to commit a database transaction with DataSource <insert_1>, which represents a JDBC provider. This problem can be caused by network problems, or errors on the database server. The transaction might be left in an "in-doubt" state, which you might have to resolve manually.
Response
Check the database logs to determine the reason for the problem, and refer to the documentation supplied by the database provider. Contact your IBM support center if you are unable to determine the cause of the problem.

BIP6266
A problem was encountered when rolling back a transaction with the JDBC Datasource <insert_1>.
Severity
20 : Error
Explanation
The node was unable to roll back a database transaction with DataSource <insert_1>, which represents a JDBC provider. This problem can be caused by network problems, or errors on the database server. The transaction might be left in an "in-doubt" state, which you might have to resolve manually.
Response
Check the database logs to determine the reason for the problem, and refer to the documentation supplied by the database provider. Contact your IBM support center if you are unable to determine the cause of the problem.

BIP6267
There has been a problem establishing a connection to the JDBC provider <insert_2> in node <insert_1>. Exception details: <insert_3>3
Severity
20 : Error
Explanation
The node has been unable to establish a connection to the JDBC Provider.
Response
Contact your IBM Integration Bus administrator.

BIP6268
A connection error has occurred for JDBC provider <insert_1>. The integration node will attempt to reconnect to the JDBC provider. Exception details: <insert_2>2
Severity
20 : Error
Explanation
The JDBC connection to the JDBC provider has ended for the reasons given by the exception details.
Response
Contact your IBM Integration Bus administrator.

BIP6269
A request for a JDBC connection from pool <insert_1> has timed out after waiting for <insert_2> milliseconds.
Severity
20 : Error
Explanation
A request has been made for a JDBC connection from pool <insert_1>, but the request could not be satisfied within the timeout period.
Response
Examine the JDBC connection pooling resource statistics.
Consider increasing the size of the JDBC connection pool.

BIP6270
The node <insert_1> has evaluated the filter expression <insert_2> at row position <insert_3> and the result was <insert_4>.
Severity
0 : Information
Explanation
The node has evaluated a filter expression against the input message.
Response
No response required.

BIP6271
The node <insert_1> has propagated a message to the <insert_2> terminal, at row position <insert_3> because a filter expression matched.
Severity
0 : Information
Explanation
The node has propagated a message to an output terminal because a filter expression matched.
Response
No response required.

BIP6272
The node <insert_1> has propagated a message to the default terminal because no filter expressions matched.
Severity
0 : Information
Explanation
The node has propagated a message to the default terminal.
Response
No response required.

BIP6273
The node <insert_1> has added the following namespace declaration: <insert_2> = <insert_3>.
Severity
0 : Information
Explanation
The node has declared a namespace definition.
Response
No response required.

BIP6274
The node <insert_1> has added a filter expression <insert_2> to its filter table at row position <insert_3>.
Severity
0 : Information
Explanation
The node has added a filter expression to its table.
Response
No response required.

BIP6275
The method <insert_1> has been called on JDBC proxy object <insert_2>, but the JDBC connection relating to that object has ended.
Severity
20 : Error
Explanation
A JDBC connection has been released back to the pool of connections, but a method has been called on an object relating to that connection.
Response
All objects relating to the connection must be discarded when the connection is released back to the pool of connections.

BIP6276
Node <insert_1> is unable to create a connection with the datasource represented by JDBCProviders configurable service name <insert_2>, because it does not match the XAOpenString name for an XA resource manager that participates in a globally coordinated transaction.
Severity
20 : Error
Explanation
The node has been configured for global coordination, but it is unable to start a transaction with a datasource. The JDBCProviders configurable service name specified in the getJDBCType4Connection() call does not match an XA resource manager defined to the integration node's queue manager.
Response
Examine the configurable service name provided in the getJDBCType4Connection() API call. Ensure that it matches the XAOpenstrings value configured in an XA resource manager entry for the integration node queue manager. If the XA resource manager entry is missing, define it to the integration node's queue manager. On a Windows platform, this is a queue manager property, while on a UNIX or Linux platform, it is a stanza in the queue manager's qm.ini file.

BIP6277
Node <insert_1> is unable to create a connection with the datasource represented by JDBCProviders configurable service name <insert_2>, because of incompatible configuration settings:
Severity
20 : Error
Explanation
The message flow has been configured for globally coordinated transactions, but the configurable service expects to use non XA connections.
Response
You have two options: 1.Modify the configurable service used by the getJDBCType4Connection() API call to set the property "jdbcProviderSupportsXA" to "true" 2.Uncheck the message flow property "Coordinated Transaction" in the deployable Bar File.

BIP6301
REST API <insert_1> failed to deploy because either the <insert_2> attribute was not specified in the REST API descriptor file or the value of the attribute was empty.
Severity
20 : Error
Explanation
The descriptor file for REST API <insert_1> requires the attribute <insert_2>.
Response
Ensure that the REST API contains a valid descriptor file.

BIP6302
REST API <insert_1> does not contain a definition for operation <insert_2>.
Severity
20 : Error
Explanation
The request for operation <insert_2> failed because this operation has not been defined in REST API <insert_1>.
Response
Ensure that the path and HTTP method are correct.

BIP6303
REST API <insert_1> failed to deploy because the REST API definition file <insert_2> does not exist or cannot be found.
Severity
20 : Error
Explanation
The specified REST API requires a valid definition file, but the definition file that is referenced in the descriptor file cannot be found.
Response
Ensure that the specified definition file was deployed with the specified REST API.

BIP6304
REST API <insert_1> failed to deploy because the REST API definition type <insert_2> is invalid or unsupported.
Severity
20 : Error
Explanation
Valid definition types are: 'swagger_20'
Response
Ensure that the REST API descriptor file contains a valid definition type.

BIP6305
REST API <insert_1> failed to deploy because the REST API definition contains the operation name <insert_2> more than once.
Severity
20 : Error
Explanation
Each REST operation that is defined in the specified REST API must have a unique operation name.
Response
Ensure that all operation names are unique in the REST API.

BIP6306
The requested operation <insert_1> has not been implemented in REST API <insert_2>.
Severity
20 : Error
Explanation
Although operation <insert_1> has been defined in REST API <insert_2>, the associated implementing subflow could not be found.
Response
Ensure that this operation has been implemented, then re-deploy the REST API.

BIP6307
REST API <insert_1> failed to deploy because the implementing message flow <insert_2> could not be found.
Severity
20 : Error
Explanation
The specified REST API requires an implementing message flow, but the implementing message flow that is referenced in the descriptor file cannot be found.
Response
Ensure that the specified implementing message flow was deployed with the specified REST API.

BIP6308
REST API <insert_1> failed to deploy because the implementing message flow contains two <insert_2> nodes: <insert_3> and <insert_4>
Severity
20 : Error
Explanation
The implementing message flow has an unexpected additional node. The implementing message flow must not contain additional nodes.
Response
Remove the additional node from the implementing message flow and redeploy the REST API.

BIP6309
REST API <insert_1> failed to deploy because the implementing message flow contains an unexpected node <insert_2>.
Severity
20 : Error
Explanation
The implementing message flow has an unexpected additional node. The implementing message flow must not contain additional nodes.
Response
Remove the additional nodes from the implementing message flow and redeploy the REST API.

BIP6310
REST API <insert_1> failed to deploy because the implementing message flow does not contain the following required node: <insert_2>
Severity
20 : Error
Explanation
The implementing message flow requires the following node: <insert_2>
Response
Regenerate the implementing message flow and redeploy the application.

BIP6311
REST API <insert_1> does not support method <insert_2> for URL <insert_3>.
Severity
20 : Error
Explanation
The HTTP request to URL <insert_3> with HTTP method <insert_2> failed as this method is not registered for this URL. REST API <insert_1>.
Response
Ensure that the URL and HTTP method are correct.

BIP6312
The component: <insert_1> is not valid.
Severity
30 : Severe error
Explanation
The component specified in the URL is not valid.
Response
Ensure that the URL and HTTP method are correct.

BIP6313
The resource manager: <insert_1> is not valid.
Severity
30 : Severe error
Explanation
The resource manager specified in the URL is not valid.
Response
Ensure that the URL and HTTP method are correct.

BIP6314
The property: <insert_1> is not valid.
Severity
30 : Severe error
Explanation
The property specified in the URL is not valid.
Response
Ensure that the URL and HTTP method are correct.

BIP6315
REST API <insert_1> cannot be deployed to the integration server. The integration server is configured to use the HTTP listener for the integration node.
Severity
20 : Error
Explanation
REST APIs can only be deployed to integration servers that are configured to use the HTTP listener for the integration server.
Response
Configure the integration server to use the HTTP listener for the integration server. Set the integration server property 'httpNodesUseEmbeddedListener' to 'true' by using the mqsichangeproperties command. Alternatively, set the property by using the administration web user interface.

BIP6316
REST API <insert_1> cannot be deployed to the integration server. The REST API contains a definition of a resource with path <insert_2>. The path <insert_2> does not represent a valid path.
Severity
20 : Error
Explanation
REST APIs only support resources with valid paths. A valid path must represent a valid RFC6570 level 1 URI template. Path parameters in the path must start with a <insert_3> character and end with a <insert_4> character, with the parameter name between them.
Response
Modify the API definitions for the specified REST API so that all of the defined resources have valid paths.

BIP6318
REST API <insert_1> cannot be deployed to the integration server. Either the API definitions for the REST API could not be parsed from the file <insert_2> or the API definitions are not supported.
Severity
20 : Error
Explanation
An error occurred while the API definitions for the specified REST API were being parsed.
Response
To determine why the API definitions could not be parsed, examine the additional error messages.

BIP6319
The HTTPInput node <insert_1> in message flow <insert_2> (application <insert_3>, library <insert_4>) could not be deployed because it has an invalid URL specifier of <insert_5>. The URL specifier is invalid as it clashes with the URL specifier <insert_6> of the HTTPInput node <insert_7> in message flow <insert_8> (application <insert_9>, library <insert_10>).
Severity
20 : Error
Explanation
If the HTTPInput nodes have the same URL specifiers and both of the nodes are deployed, it would cause a clash.
Response
Modify the URL specifier of one of the HTTPInput nodes so that a clash does not occur.

BIP6324
The RESTAsyncRequest node <insert_1> with the unique identifier <insert_2> cannot find its corresponding RESTAsyncResponse node.
Severity
20 : Error
Explanation
The specified RESTAsyncRequest node cannot perform any work until its corresponding RESTAsyncResponse node has been deployed. The corresponding RESTAsyncResponse node must have the specified unique identifier.
Response
Deploy the corresponding RESTAsyncResponse node with the specified unique identifier.

BIP6325
The RESTAsyncResponse node <insert_1> with the unique identifier <insert_2> cannot find its corresponding RESTAsyncRequest node. The RESTAsyncResponse node has currently checked <insert_3> times for the corresponding RESTAsyncRequest node, and will continue checking. It cannot receive any response messages until it can find the corresponding RESTAsyncRequest node.
Severity
20 : Error
Explanation
The specified RESTAsyncResponse node cannot perform any work until its corresponding RESTAsyncRequest node has been deployed. The corresponding RESTAsyncRequest node must have the specified unique identifier.
Response
Deploy the corresponding RESTAsyncRequest node with the specified unique identifier.

BIP6326
REST response node <insert_1> received a response for the operation <insert_2>. The operation was unsuccessful. HTTP status code: <insert_3>, response headers: <insert_4> bytes, response body: <insert_5> bytes.
Severity
20 : Error
Explanation
The REST response node has received a response for the specified operation in the REST API. The operation was unsuccessful.
Response
No action is required.

BIP6327
REST response node <insert_1> received a response for an operation. The operation was unsuccessful. HTTP status code: <insert_2>, response headers: <insert_3> bytes, response body: <insert_4> bytes.
Severity
20 : Error
Explanation
The REST response node has received a response for the specified operation in the REST API. The operation was unsuccessful.
Response
No action is required.

BIP6328
REST response node <insert_1> received a response for the operation <insert_2>. The operation was successful. HTTP status code: <insert_3>, response headers: <insert_4> bytes, response body: <insert_5> bytes.
Severity
0 : Information
Explanation
The REST response node has received a response for the specified operation in the REST API. The operation was successful.
Response
No action is required.

BIP6329
REST response node <insert_1> received a response for an operation. The operation was successful. HTTP status code: <insert_2>, response headers: <insert_3> bytes, response body: <insert_4> bytes.
Severity
0 : Information
Explanation
The REST response node has received a response for the specified operation in the REST API. The operation was successful.
Response
No action is required.

BIP6330
REST response node <insert_1> is receiving a response for the operation <insert_2>.
Severity
0 : Information
Explanation
The REST response node is receiving a response for the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6331
REST response node <insert_1> is receiving a response for an operation.
Severity
0 : Information
Explanation
The REST response node is receiving a response for the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6332
REST response node <insert_1> failed to receive a response for the operation <insert_2>.
Severity
20 : Error
Explanation
The REST response node failed to receive a response for the specified operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6333
REST response node <insert_1> failed to receive a response for an operation.
Severity
20 : Error
Explanation
The REST response node failed to receive a response for an operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6334
REST request node <insert_1> failed to submit a request for the operation <insert_2>.
Severity
20 : Error
Explanation
The REST request node failed to submit a request for the specified operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6335
REST request node <insert_1> failed to submit a request for an operation.
Severity
20 : Error
Explanation
The REST request node failed to submit a request for an operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6336
REST request node <insert_1> is submitting a request for the operation <insert_2>. HTTP method: <insert_3>, URL: <insert_4>, request headers: <insert_5> bytes, request body: <insert_6> bytes.
Severity
0 : Information
Explanation
The REST request node is submitting a request for the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6337
REST request node <insert_1> is submitting a request for an operation. HTTP method: <insert_2>, URL: <insert_3>, request headers: <insert_4> bytes, request body: <insert_5> bytes.
Severity
0 : Information
Explanation
The REST request node is submitting a request for the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6338
REST request node <insert_1> submitted a request for the operation <insert_2>.
Severity
0 : Information
Explanation
The REST request node has submitted a request for the specified operation in the REST API. The response for the request will be handled in a separate thread by a REST response node.
Response
No action is required.

BIP6339
REST request node <insert_1> submitted a request for an operation.
Severity
0 : Information
Explanation
The REST request node has submitted a request for the specified operation in the REST API. The response for the request will be handled in a separate thread by a REST response node.
Response
No action is required.

BIP6340
REST request node <insert_1> has been configured with an operation that specifies no security requirements. The REST request node will not attempt to add security information to the REST request.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies no security requirements. The REST request node will not attempt to add security information to the REST request.
Response
If the REST request requires security information, then those security requirements must be defined in the REST API definitions file.

BIP6341
REST request node <insert_1> cannot satisfy API key security requirement <insert_2> because the security identity <insert_3> specified in the LocalEnvironment does not contain a valid API key.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity, specified in the LocalEnvironment, does not contain a valid API key.
Response
Use the mqsisetdbparms command to store a valid API key against the specified security identity for the REST request node to use.

BIP6342
REST request node <insert_1> can satisfy API key security requirement <insert_2> using the API key in the security identity <insert_3> specified in the LocalEnvironment.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the specified security identity, specified in the LocalEnvironment, does contain a valid API key.
Response
No action is required.

BIP6343
REST request node <insert_1> can satisfy API key security requirement <insert_2> using the API key <insert_3> provided in the LocalEnvironment.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the LocalEnvironment does contain a valid API key.
Response
No action is required.

BIP6344
REST request node <insert_1> cannot satisfy HTTP basic authentication security requirement <insert_2> because the security identity <insert_3> specified in the LocalEnvironment does not contain a valid username and password.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity, specified in the LocalEnvironment, does not contain a valid username and password.
Response
Use the mqsisetdbparms command to store a valid username and password against the specified security identity for the REST request node to use.

BIP6345
REST request node <insert_1> can satisfy HTTP basic authentication security requirement <insert_2> using the username and password in the security identity <insert_3> specified in the LocalEnvironment.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the specified security identity, specified in the LocalEnvironment, does contain a valid username and password.
Response
No action is required.

BIP6346
REST request node <insert_1> cannot satisfy security requirement <insert_2> because the security identity <insert_3> specified in the LocalEnvironment does not exist or cannot be accessed.
Severity
20 : Error
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity, specified in the LocalEnvironment, does not exist or cannot be accessed.
Response
Use the mqsisetdbparms command to store valid security credentials against the specified security identity for the REST request node to use.

BIP6347
REST request node <insert_1> can satisfy HTTP basic authentication security requirement <insert_2> using the username <insert_3> and password provided in the LocalEnvironment.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the LocalEnvironment does contain a valid username and password.
Response
No action is required.

BIP6348
REST request node <insert_1> is using the LocalEnvironment override <insert_2> with value <insert_3> to override the node property <insert_4> with value <insert_5>.
Severity
0 : Information
Explanation
The LocalEnvironment specifies an override for the specified node property. The value in the LocalEnvironment will be used instead of the value configured on the node.
Response
No action is required.

BIP6349
REST request node <insert_1> cannot use the LocalEnvironment override <insert_2> with value <insert_3> to override the node property <insert_4> with value <insert_5>.
Severity
20 : Error
Explanation
The LocalEnvironment specifies an override for the specified node property. The value in the LocalEnvironment is invalid and cannot be used.
Response
To determine why the LocalEnvironment override could not be used, examine the additional error messages.

BIP6350
REST request node <insert_1> cannot invoke operation <insert_2>. The XPath expression <insert_3> specified for the parameter <insert_4> returned an empty value.
Severity
20 : Error
Explanation
The specified XPath expression returned an empty value for the specified parameter. Empty values cannot be used for path parameters. Valid values must be specified for path parameters, which cannot be empty or null.
Response
Ensure that a valid value, which cannot be empty or null, is provided for the specified path parameter.

BIP6351
REST request node <insert_1> failed to deploy because either the <insert_2> attribute was not specified in the REST request node attributes or the value of the attribute was empty.
Severity
20 : Error
Explanation
The REST request node <insert_1> requires the attribute <insert_2>.
Response
Ensure that the REST request node specifies all required attributes.

BIP6352
REST request node <insert_1> failed to deploy because a definition for operation <insert_2> could not be found in the REST API definition file <insert_3>.
Severity
20 : Error
Explanation
The specified REST request node specifies the name of an operation, but that operation cannot be found in the specified REST API definition file.
Response
Ensure that the operation name on the REST request node is correct.

BIP6353
REST request node <insert_1> failed to deploy because the REST API definition file <insert_2> does not exist or cannot be found.
Severity
20 : Error
Explanation
The specified REST request node requires a valid definition file, but the definition file that is referenced in the REST request node attributes cannot be found.
Response
Ensure that the specified definition file was deployed with the specified REST request node.

BIP6354
REST request node <insert_1> failed to deploy because the REST API definition type <insert_2> is invalid or unsupported.
Severity
20 : Error
Explanation
Valid definition types are: 'swagger_20'
Response
Ensure that the REST request node specifies a valid definition type.

BIP6355
REST request node <insert_1> failed to deploy because the REST API definition file <insert_3> contains the operation name <insert_2> more than once.
Severity
20 : Error
Explanation
Each REST operation that is defined in the specified REST API definition file must have a unique operation name.
Response
Ensure that all operation names are unique in the REST API definition file.

BIP6356
REST request node <insert_1> cannot be deployed to the integration server. Either the REST API definitions for the REST request node could not be parsed from the file <insert_2> or the REST API definitions are not supported.
Severity
20 : Error
Explanation
An error occurred while the REST API definitions for the specified REST request node were being parsed.
Response
To determine why the REST API definitions could not be parsed, examine the additional error messages.

BIP6357
REST request node <insert_1> cannot be deployed because it contains an entry in the parameters table for the parameter <insert_2>, which is not defined for the operation <insert_3> in the REST API definition file <insert_4>.
Severity
20 : Error
Explanation
The specified REST request node contains an entry in the parameters table for a parameter that is not defined.
Response
Remove the entry for the specified parameter from the parameters table.

BIP6358
REST request node <insert_1> cannot be deployed because it contains an entry in the parameters table for the parameter <insert_2>, which contains an invalid XPath expression <insert_3>.
Severity
20 : Error
Explanation
The specified REST request node contains an entry in the parameters table for a parameter that has an invalid XPath expression.
Response
Modify the XPath expression for the specified parameter from the parameters table.

BIP6359
REST request node <insert_1> cannot be deployed because the <insert_2> attribute has the value <insert_3>, which is not a valid URL.
Severity
20 : Error
Explanation
The specified REST request node contains an invalid value for the specified attribute. The specified attribute requires a value that is a valid URL.
Response
Modify the specified attribute so that the value is a valid URL.

BIP6360
REST request node <insert_1> cannot invoke operation <insert_2>. The parameter <insert_3> is marked as required, but a value has not been specified for that parameter.
Severity
20 : Error
Explanation
The specified parameter is marked as required. A value must be provided for all parameters that are marked as required.
Response
Ensure that a value is provided for the specified parameter. Values can be provided for parameters by specifying an XPath expression on the REST request node properties, or by setting the values in the LocalEnvironment.

BIP6361
REST request node <insert_1> cannot invoke operation <insert_2>. The XPath expression <insert_3> specified for the parameter <insert_4> returned <insert_5> values.
Severity
20 : Error
Explanation
The specified XPath expression returned multiple values for the specified parameter. Only a single value can be specified for each parameter.
Response
Ensure that the specified XPath expression returns a single value. Modify the XPath expression or the input message assembly so that only a single value is returned by the XPath expression. Alternatively, remove the XPath expression and pass a single value for the parameter in the LocalEnvironment.

BIP6362
REST request node <insert_1> cannot invoke operation <insert_2>. The LocalEnvironment contains multiple values for the parameter <insert_3>.
Severity
20 : Error
Explanation
The LocalEnvironment contains multiple values for the specified parameter. Only a single value can be specified for each parameter.
Response
Ensure that the LocalEnvironment contains at most one value for a parameter.

BIP6363
REST request node <insert_1> extracted the value <insert_2> from the LocalEnvironment for the parameter <insert_3>.
Severity
0 : Information
Explanation
The specified value for the specified parameter was extracted from the LocalEnvironment tree. The specified value will be used when invoking the operation in the REST API.
Response
No action is required.

BIP6364
REST request node <insert_1> extracted the value <insert_2> using the XPath expression <insert_3> for the parameter <insert_4>.
Severity
0 : Information
Explanation
The specified value for the specified parameter was extracted using the specified XPath expression. The specified value will be used when invoking the operation in the REST API.
Response
No action is required.

BIP6365
REST request node <insert_1> is setting the value of the 'Content-Type' header to <insert_2>. The value was automatically determined from the message domain of the input message. The message domain of the input message is <insert_3>.
Severity
0 : Information
Explanation
No 'Content-Type' header was provided in the input message. The REST request node is setting the specified value for the 'Content-Type' header.
Response
No action is required.

BIP6366
REST request node <insert_1> is setting the value of the 'Content-Type' header to <insert_2>. The value was determined from the 'contentType' property of the REST request node, or an override in the LocalEnvironment. The message domain of the input message is <insert_3>.
Severity
0 : Information
Explanation
No 'Content-Type' header was provided in the input message. The REST request node is setting the specified value for the 'Content-Type' header.
Response
No action is required.

BIP6367
REST request node <insert_1> has generated a request body by serializing the input message. The request body is <insert_2> bytes long. The CCSID used was <insert_3>, and the encoding used was <insert_4>.
Severity
0 : Information
Explanation
The REST request node has generated a request body by serializing the input message. The request body will be used when invoking the operation in the REST API.
Response
No action is required.

BIP6368
REST request node <insert_1> has compressed the request body by using the compression algorithm <insert_2>. The uncompressed request body was <insert_3> bytes long. The compressed request body is <insert_4> bytes long.
Severity
0 : Information
Explanation
The REST request node has compressed the request body by using the specified compression algorithm. The compressed request body will be used when invoking the operation in the REST API.
Response
No action is required.

BIP6369
REST request node <insert_1> is invoking the operation <insert_2>. HTTP method: <insert_3>, URL: <insert_4>, request headers: <insert_5> bytes, request body: <insert_6> bytes.
Severity
0 : Information
Explanation
The REST request node is invoking the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6370
REST request node <insert_1> is invoking an operation. HTTP method: <insert_2>, URL: <insert_3>, request headers: <insert_4> bytes, request body: <insert_5> bytes.
Severity
0 : Information
Explanation
The REST request node is invoking the specified operation in the REST API. See subsequent messages for success or failure messages relating to this request.
Response
No action is required.

BIP6371
REST request node <insert_1> invoked the operation <insert_2>. The operation was successful. HTTP status code: <insert_3>, response headers: <insert_4> bytes, response body: <insert_5> bytes, total request time: <insert_6> ms.
Severity
0 : Information
Explanation
The REST request node has invoked the specified operation in the REST API. The operation was successful.
Response
No action is required.

BIP6372
REST request node <insert_1> invoked an operation. The operation was successful. HTTP status code: <insert_2>, response headers: <insert_3> bytes, response body: <insert_4> bytes, total request time: <insert_5> ms.
Severity
0 : Information
Explanation
The REST request node has invoked the specified operation in the REST API. The operation was successful.
Response
No action is required.

BIP6373
REST request node <insert_1> invoked the operation <insert_2>. The operation was unsuccessful. HTTP status code: <insert_3>, response headers: <insert_4> bytes, response body: <insert_5> bytes, total request time: <insert_6> ms.
Severity
20 : Error
Explanation
The REST request node has invoked the specified operation in the REST API. The operation was unsuccessful.
Response
No action is required.

BIP6374
REST request node <insert_1> invoked an operation. The operation was unsuccessful. HTTP status code: <insert_2>, response headers: <insert_3> bytes, response body: <insert_4> bytes, total request time: <insert_5> ms.
Severity
20 : Error
Explanation
The REST request node has invoked the specified operation in the REST API. The operation was unsuccessful.
Response
No action is required.

BIP6375
REST request node <insert_1> failed to invoke the operation <insert_2>.
Severity
20 : Error
Explanation
The REST request node failed to invoke the specified operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6376
REST request node <insert_1> failed to invoke an operation.
Severity
20 : Error
Explanation
The REST request node failed to invoke an operation in the REST API.
Response
To determine why the operation could not be invoked, examine the additional error messages.

BIP6377
REST request node <insert_1> is setting the value of the 'Accept' header to <insert_2>. The value was determined from the 'accept' property of the REST request node, or an override in the LocalEnvironment.
Severity
0 : Information
Explanation
No 'Accept' header was provided in the input message. The REST request node is setting the specified value for the 'Accept' header.
Response
No action is required.

BIP6378
REST request node <insert_1> is using the message domain <insert_2> to parse the response body. The message domain <insert_2> was selected as the 'Content-Type' header in the response is <insert_3>.
Severity
0 : Information
Explanation
The REST request node has automatic Content-Type handling enabled, and has automatically selected a message domain to use to parse the response body.
Response
No action is required.

BIP6379
REST request node <insert_1> is using the message domain <insert_2> to parse the response body. The message domain <insert_2> was selected as there is no 'Content-Type' header in the response.
Severity
0 : Information
Explanation
The REST request node has automatic Content-Type handling enabled, and has automatically selected a message domain to use to parse the response body.
Response
No action is required.

BIP6380
REST request node <insert_1> is processing security requirement set <insert_2> of <insert_3>.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node is processing these sets to determine if the node needs to add security information to the REST request.
Response
No action is required.

BIP6381
REST request node <insert_1> has successfully satisfied all of the security requirements in the security requirement set <insert_2> of <insert_3>.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node has satisfied all of the security requirements in one of these sets by adding security information to the REST request.
Response
No action is required.

BIP6382
REST request node <insert_1> is processing security requirement <insert_2>.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node is processing these sets to determine if the node needs to add security information to the REST request.
Response
No action is required.

BIP6383
REST request node <insert_1> cannot process the security requirement <insert_2> because the security requirement <insert_2> is not defined in the REST API definition file <insert_3>.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot process the specified security requirement because it does not exist in the specified REST API definition file.
Response
The REST API definition file may be incorrect. An operation that is defined in the REST API definition file references a security requirement that is not defined in that REST API definition file.

BIP6384
REST request node <insert_1> cannot process the security requirement <insert_2> because the security requirement <insert_2> of type <insert_3> is not supported by this node.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot process the specified security requirement because it is not supported by this node. file.
Response
The REST request node cannot supply the security information for this security requirement type. If this security information is required in order to invoke the current operation, then you must specify the security information yourself by adding it into the input message.

BIP6385
REST request node <insert_1> could not satisfy all of the security requirements in the security requirement set <insert_2> of <insert_3>.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. However, the REST request node could not satisfy all of the security requirements in one of these sets by adding security information to the REST request.
Response
The REST request node cannot supply the security information for all of the security requirements in this security requirement set. If this security information is required in order to invoke the current operation, then you must specify the security information yourself by adding it into the input message.

BIP6386
REST request node <insert_1> could not satisfy all of the security requirements in any of the security requirement sets.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. However, the REST request node could not satisfy all of the security requirements in any of these sets by adding security information to the REST request.
Response
The REST request node cannot supply the security information for all of the security requirements in any of the security requirement sets. If this security information is required in order to invoke the current operation, then you must specify the security information yourself by adding it into the input message.

BIP6387
REST request node <insert_1> cannot satisfy security requirement <insert_2> because a security identity has not been specified on the node or in the LocalEnvironment tree.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because a security identity has not been specified.
Response
Specify a security identity on the REST request node, or in the LocalEnvironment tree.

BIP6388
REST request node <insert_1> cannot satisfy HTTP basic authentication security requirement <insert_2> because the security identity <insert_3> does not contain a valid username and password.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity does not contain a valid username and password.
Response
Use the mqsisetdbparms command to store a valid username and password against the specified security identity for the REST request node to use.

BIP6389
REST request node <insert_1> cannot satisfy API key security requirement <insert_2> because the security identity <insert_3> does not contain a valid API key.
Severity
10 : Warning
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity does not contain a valid API key.
Response
Use the mqsisetdbparms command to store a valid API key against the specified security identity for the REST request node to use.

BIP6390
REST request node <insert_1> can satisfy HTTP basic authentication security requirement <insert_2> using the username and password in the security identity <insert_3>.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the specified security identity does contain a valid username and password.
Response
No action is required.

BIP6391
REST request node <insert_1> can satisfy API key security requirement <insert_2> using the API key in the security identity <insert_3>.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the specified security identity does contain a valid API key.
Response
No action is required.

BIP6392
REST request node <insert_1> can satisfy HTTP basic authentication security requirement <insert_2> using an existing 'Authorization' header in the input message.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the input message contains an existing 'Authorization' header.
Response
No action is required.

BIP6393
REST request node <insert_1> can satisfy API key security requirement <insert_2> using an existing <insert_3> header or query parameter in the input message.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node can satisfy the specified security requirement because the input message contains an existing query or header parameter.
Response
No action is required.

BIP6394
REST request node <insert_1> has applied HTTP basic authentication security requirement <insert_2> by adding an 'Authorization' header to the HTTP request.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node has applied the specified security requirement by adding an 'Authorization' header to the HTTP request.
Response
No action is required.

BIP6395
REST request node <insert_1> has applied API key security requirement <insert_2> by adding an <insert_3> header or query parameter to the HTTP request.
Severity
0 : Information
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node has applied the specified security requirement by adding a header or query parameter to the HTTP request.
Response
No action is required.

BIP6396
REST request node <insert_1> cannot satisfy security requirement <insert_2> because the security identity <insert_3> does not exist or cannot be accessed.
Severity
20 : Error
Explanation
The REST request node has been configured with an operation that specifies one or more sets of security requirements. The REST request node cannot satisfy the specified security requirement because the specified security identity does not exist or cannot be accessed.
Response
Use the mqsisetdbparms command to store valid security credentials against the specified security identity for the REST request node to use.

BIP6397
An attempt was made to deploy a RESTAsyncRequest node that was paired with an HTTPAsyncResponse or a SOAPAsyncResponse node. The unique identifier was <insert_1>.
Severity
30 : Severe error
Explanation
It is an error to deploy a RESTAsyncRequest node that is paired with an HTTPAsyncResponse or a SOAPAsyncResponse node as it must be paired with a RESTAsyncResponse node.
Response
Correct this error and redeploy the flow.

BIP6398
An attempt was made to deploy a RESTAsyncResponse node that was paired with an HTTPAsyncRequest or a SOAPAsyncRequest node. The unique identifier was <insert_1>.
Severity
30 : Severe error
Explanation
It is an error to deploy a RESTAsyncResponse node that is paired with an HTTPAsyncRequest or a SOAPAsyncRequest node as it must be paired with a RESTAsyncRequest node.
Response
Correct this error and redeploy the flow.

BIP6399
REST request node <insert_1> cannot invoke operation <insert_2>. The LocalEnvironment contains an empty value for the path parameter <insert_3>.
Severity
20 : Error
Explanation
The LocalEnvironment tree contains an empty value for the specified path parameter. Empty values cannot be used for path parameters. Valid values must be specified for path parameters, which cannot be empty or null.
Response
Ensure that a valid value, which cannot be empty or null, is provided for the specified path parameter.

BIP6401
The connection agent for the remote callable flow has not been configured. The message flow in application <insert_1> with endpoint name <insert_2> cannot be called.
Severity
30 : Severe error
Explanation
To call a remote flow, you must configure an agent. No agent has been configured; therefore, the current request has not been sent to a remote server.
Response
Configure a IBM Integration Bus agent.

BIP6402
The connection agent for the remote callable flow cannot be configured on this platform. A message flow in application <insert_1> with endpoint name <insert_2> cannot be called.
Severity
30 : Severe error
Explanation
To call a remote flow, you must configure an agent. However, you cannot configure an agent on this platform.
Response
None.

BIP6403
Remote callable flow switch has not successfully started in <insert_3> seconds, preventing invocation of a flow in application <insert_1> with endpoint <insert_2>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support requires a switch to be configured in order to allow remote flow invocation. The configured switch has not successfully started, and so the current request has not been sent to a remote server.
Response
Examine error logs to determine why the IBM Integration Bus switch has not started. Resolve any network issues or configuration problems, and retry the request.

BIP6404
An exception occurred while attempting to call a flow in application <insert_1> with endpoint name <insert_2> on a remote server. The message might not have been sent correctly.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has encountered an exception while calling a remote flow. Subsequent exceptions might provide more information.
Response
Examine error logs to determine why the IBM Integration Bus agent has not sent the message successfully. Resolve any network issues or configuration problems, and retry the request.

BIP6405
An exception occurred while attempting to call a flow in application <insert_1> with endpoint name <insert_2> on a remote server. The message might not have been sent correctly.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has encountered an exception while calling a remote flow. No local flow matched the specified application and endpoint name. Subsequent exceptions might provide more information.
Response
Examine error logs to determine why the IBM Integration Bus agent has not sent the message successfully. Resolve any network issues or configuration problems, and retry the request.

BIP6406
No callable flow with application <insert_1> and endpoint name <insert_2> is available, and no remote callable flow agent has been configured. The flow cannot be called.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support requires an agent to be configured in order to allow remote flow invocation. No local flow matched the specified application and endpoint name, no agent has been configured, and so the current request has not been sent to local or remote flows.
Response
Configure a IBM Integration Bus agent, or deploy a flow locally that matches the specified application and endpoint names.

BIP6407
No callable flow in application <insert_1> with endpoint name <insert_2> is available. The flow cannot be called.
Severity
30 : Severe error
Explanation
To call a flow, a local callable flow must be available in the specified application and with the specified endpoint name. A callable flow is not available with the specified application and endpoint names; therefore, the current request has not been sent.
Response
Deploy a flow locally that matches the specified application and endpoint names.

BIP6408
Callable flow in application <insert_1> with endpoint name <insert_2> did not respond within the <insert_3> second timeout specified on the Callable Flow Invoke node.
Severity
30 : Severe error
Explanation
A response was not received in the required time period.
Response
Check the error messages that follow to determine why the error occurred. Also check the error logs in the remote servers that contain the specified callable flow.

BIP6409
The connection agent for the remote callable flow has not started successfully in <insert_3> seconds. A message flow has not been registered in application <insert_1> with endpoint name <insert_2>.
Severity
30 : Severe error
Explanation
To register a remote flow, you much configure a connection agent. The configured agent has not started successfully; therefore, the current request has not been sent to a remote server.
Response
Examine error logs to determine why the IBM Integration Bus agent has not started. Resolve any network issues or configuration problems, and restart the flow.

BIP6410
Callable flow in application <insert_1> with endpoint name <insert_2> is already registered.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support allows only one endpoint to be registered for any given application.
Response
Change the application or endpoint name so that the combination is unique, then retry the operation.

BIP6411
No callable flow in application <insert_1> and with endpoint name <insert_2> is available. This flow cannot be called.
Severity
30 : Severe error
Explanation
To call a flow, a local callable flow must be available in the specified application and with the specified endpoint name. A callable flow has not become available with the specified application and endpoint names within the specified timeout interval of <insert_3> seconds. Therefore, the current request has not been sent.
Response
Deploy a flow locally that matches the specified application and endpoint names.

BIP6412
An error has occurred while calling a flow: <insert_1>, with return code <insert_2> and error number <insert_3> for callable flow name <insert_4>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error. The message might not have been sent correctly.
Response
Examine error logs to determine why the IBM Integration Bus callable flow support has encountered an error. Resolve any network issues or configuration problems, and retry the request.

BIP6413
Callable flow in application <insert_1> with endpoint name <insert_2> did not become available within <insert_3> seconds.
Severity
30 : Severe error
Explanation
A message could not be sent in the required time period.
Response
Check the error messages that follow to determine why the error occurred. Also check the error logs in the remote servers that contain the specified callable flow.

BIP6414
Callable flow input node <insert_3> encountered an error while attempting to register in application <insert_1> with endpoint name <insert_2>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the input node during registration.
Response
See subsequent error messages for more information.

BIP6415
Callable flow input node <insert_3> encountered an error while attempting to deregister in application <insert_1> with endpoint name <insert_2>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the input node during deregistration.
Response
See subsequent error messages for more information.

BIP6416
Callable Flow input node <insert_3> was unable to clear queued incoming messages before deregistering in application <insert_1> with endpoint name <insert_2>. Some messages might time out, or not be processed.
Severity
30 : Severe error
Explanation
The Callable Flow input node attempts to process all pending messages before stopping but was unable to do so, and some messages have been left on the in-memory queue. These messages might be processed later, if the input node is being redployed or reconfigured, or the messages might not be processed if the input node is being stopped or undeployed.
Response
None.

BIP6417
Callable Flow input node <insert_1> encountered an error while validating an inbound message.
Severity
30 : Severe error
Explanation
An internal error occurred during message validation.
Response
See previous error messages to determine the cause of the error.

BIP6418
Message does not contain valid callable flow context information
Severity
30 : Severe error
Explanation
Callable flow context information is required for reply processing to be successful. The needed information was not found in the incoming message, and no callable flow reply can be produced.
Response
Provide the required callable flow context information.

BIP6419
The provided configuration file for the property <insert_1> is not valid JSON and cannot be used to configure the integration server component <insert_2>.
Severity
20 : Error
Explanation
The specified integration server component requires a configuration file in the JSON format.
Response
If you have used the mqsichangeproperties command to provide the configuration file for the specified integration server component, then ensure that the '-p' flag has been used to provide the file contents rather than the path to the file. For example:
mqsichangeproperties nodeName -e serverName -o ComIbmIIBSwitchManager -n agentXConfigFile -p /tmp/agentx.json

BIP6420
The connection agent for the remote callable flow has been configured, but the link with the Switch server was not established after <insert_3> seconds. The message flow in application <insert_1> with endpoint name <insert_2> cannot be called.
Severity
20 : Error
Explanation
To call a remote flow, you must configure an agent, and that agent must establish a link with the Switch server. The agent has not established a link with the Switch server; therefore, the current request has not been sent to a remote server.
Response
Check the status of the configured agent. The agent will log its current status to the syslog on UNIX platforms, or the event viewer on Windows.

BIP6421
Callable flow invoke node <insert_3> encountered an error while attempting to register for application <insert_1> and endpoint name <insert_2>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the invoke node during registration.
Response
See subsequent error messages for more information.

BIP6422
Callable flow invoke node <insert_4> encountered an error while attempting to deregister for application <insert_1> and endpoint name <insert_2> with unique identifier <insert_3>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the invoke node during deregistration.
Response
See subsequent error messages for more information.

BIP6423
Callable flow asynchronous response node <insert_2> encountered an error while attempting to register with unique identifier <insert_1>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the asynchronous response node during registration.
Response
See subsequent error messages for more information.

BIP6424
Callable flow asynchronous response node <insert_2> encountered an error while attempting to deregister with unique identifier <insert_1>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the asynchronous response node during deregistration.
Response
See subsequent error messages for more information.

BIP6425
A Callable Flow asynchronous invoke node with the identifier <insert_1> cannot find its corresponding Callable Flow asynchronous response node (deploy in progress <insert_2>)
Severity
20 : Error
Explanation
It is an error to deploy a Callable Flow asynchronous invoke node without its corresponding Callable Flow asynchronous response node.
Response
Deploy the corresponding Callable Flow asynchronous response node.

BIP6426
Callable Flow asynchronous response node <insert_2> was unable to clear queued incoming messages before deregistering for unique identifier <insert_1>. Some messages might not be processed.
Severity
30 : Severe error
Explanation
The Callable Flow asynchronous response node attempts to process all pending messages before stopping but was unable to do so, and some messages have been left on the in-memory queue. These messages might be processed later, if the asynchronous response node is being redployed or reconfigured, or the messages might not be processed if the asynchronous response node is being stopped or undeployed.
Response
None.

BIP6427
Callable Flow asynchronous response node <insert_2> with unique identifier <insert_1> encountered an error while validating an inbound message.
Severity
30 : Severe error
Explanation
An internal error occurred during message validation.
Response
See previous error messages to determine the cause of the error.

BIP6428
An attempt was made to deploy two Callable Flow asynchronous invoke nodes with the same unique identifier <insert_1> to the same integration server.
Severity
30 : Severe error
Explanation
It is an error to deploy two Callable Flow asynchronous invoke nodes with the same unique identifier to the same integration server.
Response
Correct this error and redeploy the flow.

BIP6429
An attempt was made to deploy two Callable Flow asynchronous response nodes with the same unique identifier <insert_1> to the same integration server.
Severity
30 : Severe error
Explanation
It is an error to deploy two Callable Flow asynchronous response nodes with the same unique identifier to the same integration server.
Response
Correct this error and redeploy the flow.

BIP6430
Callable flow asynchronous invoke node <insert_4> encountered an error while attempting to register for application <insert_1> and endpoint name <insert_2> with unique identifier <insert_3>.
Severity
30 : Severe error
Explanation
The IBM Integration Bus callable flow support has returned an error to the asynchronous invoke node during registration.
Response
See subsequent error messages for more information.

BIP6450
The connection agent for remote callable flows has established a connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent has successfully connected to the Switch server.
Response
No response required.

BIP6451
The connection agent for remote callable flows has terminated the connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent has terminated the connection to the Switch server as a result of user action. The integration server is shutting down, or the connection agent has been reconfigured.
Response
No response required.

BIP6452
The connection agent for remote callable flows has failed to connect to the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent cannot establish a connection to the Switch server.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible by the connection agent.

BIP6453
The connection agent for remote callable flows has encountered a network error when communicating with the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible by the connection agent.

BIP6454
The connection agent for remote callable flows has encountered a network error when communicating with the Switch server with URL <insert_1>.
Severity
20 : Error
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible by the connection agent.

BIP6455
The Switch server has started listening for HTTPS administration requests on port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has successfully started listening for HTTPS administration requests.
Response
No response required.

BIP6456
The Switch server has stopped listening for HTTPS administration requests on port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has stopped listening for HTTPS administration requests as a result of user action. The integration server is shutting down, or the Switch server has been reconfigured.
Response
No response required.

BIP6457
The Switch server has failed to start listening for HTTPS administration requests on port <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A Switch server has been configured on this integration server. The Switch server cannot start listening for HTTPS administration requests.
Response
Investigate the cause of the error. The specified port may be unavailable or might be in use by another process on this system.

BIP6458
The Switch server has started listening for agent requests on the front side port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has successfully started listening for agent requests on the front side port.
Response
No response required.

BIP6459
The Switch server has stopped listening for agent requests on the front side port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has stopped listening for agent requests on the front side port as a result of user action. The integration server is shutting down, or the Switch server has been reconfigured.
Response
No response required.

BIP6460
The Switch server has failed to start listening for agent requests on the front side port <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A Switch server has been configured on this integration server. The Switch server cannot start listening for agent requests on the front side port.
Response
Investigate the cause of the error. The specified port may be unavailable or might be in use by another process on this system.

BIP6461
The Switch server has started listening for agent requests on the back side port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has successfully started listening for agent requests on the back side port.
Response
No response required.

BIP6462
The Switch server has stopped listening for agent requests on the back side port <insert_1>.
Severity
0 : Information
Explanation
A Switch server has been configured on this integration server. The Switch server has stopped listening for agent requests on the back side port as a result of user action. The integration server is shutting down, or the Switch server has been reconfigured.
Response
No response required.

BIP6463
The Switch server has failed to start listening for agent requests on the back side port <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A Switch server has been configured on this integration server. The Switch server cannot start listening for agent requests on the back side port.
Response
Investigate the cause of the error. The specified port may be unavailable or might be in use by another process on this system.

BIP6464
The secure connectivity agent for cloud systems has established a connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent has successfully connected to the Switch server.
Response
No response required.

BIP6465
The secure connectivity agent for cloud systems has terminated the connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent has terminated the connection to the Switch server as a result of user action. The integration server is shutting down, or the secure connectivity agent has been reconfigured.
Response
No response required.

BIP6466
The secure connectivity agent for cloud systems has failed to connect to the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent cannot establish a connection to the Switch server.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible by the secure connectivity agent.

BIP6467
The secure connectivity agent for cloud systems has encountered a network error when communicating with the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible by the secure connectivity agent.

BIP6468
The secure connectivity agent for cloud systems has encountered a network error when communicating with the Switch server with URL <insert_1>.
Severity
20 : Error
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible to the secure connectivity agent.

BIP6469
The secure connectivity agent for on-premises systems has established a connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent has connected successfully to the Switch server.
Response
No response required.

BIP6470
The secure connectivity agent for on-premises systems has terminated the connection to the Switch server with URL <insert_1>.
Severity
0 : Information
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent has terminated the connection to the Switch server as a result of user action. The integration server is shutting down, or the secure connectivity agent has been reconfigured.
Response
No response required.

BIP6471
The secure connectivity agent for on-premises systems has failed to connect to the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent cannot establish a connection to the Switch server.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible to the secure connectivity agent.

BIP6472
The secure connectivity agent for on-premises systems has encountered a network error when communicating with the Switch server with URL <insert_1>. The error message is: <insert_2>.
Severity
20 : Error
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible to the secure connectivity agent.

BIP6473
The secure connectivity agent for on-premises systems has encountered a network error when communicating with the Switch server with URL <insert_1>.
Severity
20 : Error
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent has encountered a network error while communicating with the Switch server and must disconnect.
Response
Investigate the cause of the error. The Switch server might be unavailable or might not be accessible to the secure connectivity agent.

BIP6474
The connection agent for remote callable flows cannot start because it has been configured with an invalid configuration file. The configuration file is for an agent of type <insert_1>.
Severity
20 : Error
Explanation
A connection agent for remote callable flows has been configured on this integration server. The connection agent has been configured with an invalid configuration file and it cannot start.
Response
Reconfigure the connection agent with the correct configuration file.

BIP6475
The secure connectivity agent for cloud systems cannot start because it has been configured with an invalid configuration file. The configuration file is for an agent of type <insert_1>.
Severity
20 : Error
Explanation
A secure connectivity agent for cloud systems has been configured on this integration server. The secure connectivity agent has been configured with an invalid configuration file and it cannot start.
Response
Reconfigure the secure connectivity agent with the correct configuration file.

BIP6476
The secure connectivity agent for on-premises systems cannot start because it has been configured with an invalid configuration file. The configuration file is for an agent of type <insert_1>.
Severity
20 : Error
Explanation
A secure connectivity agent for on-premises systems has been configured on this integration server. The secure connectivity agent has been configured with an invalid configuration file and it cannot start.
Response
Reconfigure the secure connectivity agent with the correct configuration file.

BIP6500
The integration server could not complete Bluemix startup and usage reporting setup.
Severity
20 : Error
Explanation
The integration server encountered an issue with the Bluemix reporting service configuration.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP6501
The integration server failed to perform Bluemix startup and usage reporting. Diagnostic information: <insert_1>.
Severity
20 : Error
Explanation
The reported error occurred when the integration server attempted Bluemix startup and usage reporting.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP6502
The integration server failed to post a Bluemix startup and usage reporting event to <insert_1>. Diagnostic information: <insert_2>.
Severity
10 : Warning
Explanation
The reported error occurred when the integration server attempted Bluemix startup and usage reporting.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP6503
The integration server posted a Bluemix startup and usage reporting event to <insert_1> and received an unexpected response code <insert_2>.
Severity
10 : Warning
Explanation
The reported unexpected response code occurred when the integration node attempted to post a Bluemix startup and usage reporting event.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP6504
The integration server could not complete Bluemix log reporting setup. Setup has failed, with the following details: <insert_1>.
Severity
20 : Error
Explanation
The integration server encountered an issue with the Bluemix logging service configuration.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP6505
The integration server failed to deliver Bluemix log reporting data to <insert_1>. Error details: <insert_2>.
Severity
10 : Warning
Explanation
An error occurred when the integration node attempted to send data to the configured Bluemix logging service. This data will not be resent. See the following messages for possible additional details of the error.
Response
Review the configuration by using the 'mqsireportbluemixreporting' command, correct it by using the 'mqsichangebluemixreporting' command, and then restart the integration server.