BIP5000-5999: Runtime components - Parsers
- BIP5001
- Internal error. Invalid buffer offsets for output: start offset <insert_0>; end offset <insert_1>; end of buffer <insert_2>.
- Severity
- 20 : Error
- Explanation
- The offsets for an XML element are invalid. Start offset = <insert_0>, End offset = <insert_1>.
- Response
- Record the full details provided with this message and contact your IBM Support Center.
- BIP5002
- Error creating AsgardParser.
- Severity
- 20 : Error
- Explanation
- A failure was encountered while attempting to create a parser object.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5003
- Internal Error. Invalid buffer parameters: offset <insert_0>; size <insert_1>.
- Severity
- 20 : Error
- Explanation
- An invalid buffer was passed to the XML parser. Offset = <insert_0> . Size = <insert_1>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5004
- An XML parsing error <insert_4> occurred on line <insert_2> column <insert_3> when parsing element <insert_5>.
Internal error codes : <insert_0>, <insert_1>.
- Severity
- 20 : Error
- Explanation
- This error was reported by the generic XML parser. It is usually the result of a badly-formed XML message.
- Response
- Check that the input XML message is a well-formed XML message that adheres to the XML specification. Note that the line number and column number quoted give the position where the parser discovered the problem. The actual error might be earlier in the message.
Other possible causes could be:
1. A character not supported by XML in the instance message data.
XML only supports a subset of control characters so ensure that no unsupported characters, such as X'00', appear in the document.
2. The Coded Character Set ID defined in the message header does not reflect the contents of the instance message.
If the XML document has an XML prologue, the WebSphere MQ CodedCharSetId should be consistent with the XML Encoding field.
3. A reserved XML character appears in the instance message data.
Characters that could otherwise be recognised as XML mark-up such as < or & should be replaced with the comparable XML entities such as < or &.
- BIP5005
- There are <insert_0> top level elements <insert_1> in the document.
- Severity
- 20 : Error
- Explanation
- There should be only one top level element in an XML message.
- Response
- Check that the message is well formed and adheres to the XML specification in that it has only one top level element.
- BIP5006
- Duplicate XML or DOCTYPE declaration of element <insert_0>.
- Severity
- 20 : Error
- Explanation
- The element <insert_0> has been defined more than once as type xmlXmlDecl or xmlDocTypeDecl. Only one element may be defined as one of these types.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification, and that the modifications being made to the message in the messageflow are also consistent with the XML specification.
- BIP5007
- A top level item <insert_0> has an invalid type <insert_1>. Note that the item might be unamed if it is not an element, for example if it is the root of the message.
- Severity
- 20 : Error
- Explanation
- A top level item was found which did not have type xmlElement, xmlXmlDecl, xmlDocTypeDecl, xmlParserRoot, xmlBitStream, xmlComment, xmlProcessingInstruction or xmlWhiteSpace.
- Response
- Check that the message is well formed and adheres to the XML specification, and that modifications made to the message in the message flow are also consistent with the XML specification.
- BIP5008
- Invalid element name <insert_0>.
- Severity
- 20 : Error
- Explanation
- An invalid element name found. An XML element name must begin with a letter, an underscore character, '_', or a colon,':' . An XML element name may additionally contain digits and the punctuation characters ( '.', '-', '_' and ':'). Invalid element name: <insert_0>.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification, and that the modifications being made to the message in the message flow are also consistent with the XML specification.
- BIP5009
- XML Parsing Errors have occurred.
- Severity
- 20 : Error
- Explanation
- Errors have occurred during parsing of XML.
- Response
- Review further error messages for an indication to the cause of the errors.
- BIP5010
- XML Writing Errors have occurred.
- Severity
- 20 : Error
- Explanation
- Errors have occurred during writing of XML.
- Response
- Review further error messages for an indication to the cause of the errors.
- BIP5011
- XML Namespace not allowed for an element unless in the XMLNS domain.
- Severity
- 20 : Error
- Explanation
- While writing the XML message the element <insert_0> was found with Namespace <insert_1>. Namespaces are only allowed in the XMLNS domain.
- Response
- If you wish to process namespaces change the domain to be XMLNS. If you do not wish to process namespaces modify your ESQL so that it does not contain namespace references.
- BIP5012
- XML Namespace not allowed for an attribute unless in the XMLNS domain.
- Severity
- 20 : Error
- Explanation
- While writing the XML message the attribute <insert_0> was found with Namespace <insert_1>. Namespaces are only allowed in the XMLNS domain.
- Response
- If you wish to process namespaces change the domain to be XMLNS. If you do not wish to process namespaces modify your ESQL so that it does not contain namespace references.
- BIP5013
- In the XMLNS domain XMLNS attributes must be specified in the ESQL using the NamespaceDecl correlation name.
- Severity
- 20 : Error
- Explanation
- The XMLNS attribute <insert_0> was specified as an Attribute not as a NamespaceDecl element.
- Response
- Modify the ESQL to specify the correlation name NamespaceDecl for the element.
- BIP5014
- Element must have a namespace specified if there is a default namespace in scope.
- Severity
- 20 : Error
- Explanation
- Whilst writing the XMLNS message, element <insert_0> was found to be in scope of a default namespace, but this element does not have a namespace defined.
- Response
- This error can occur if the NamespaceDecl correlation name has been used to create a default namespace for a parent element, and a child element has been created that does not have a namespace. If you have defined a default namespace in your output message tree, then all elements that are in scope of this default namespace must be defined to be in a namespace. Modify the output message tree so that element <insert_0> is defined to be in a namespace. If element <insert_0> belongs to the default namespace, then this element needs to be created in the default namespace.
- BIP5015
- Namespace declaration must have a valid value.
- Severity
- 20 : Error
- Explanation
- Whilst writing the XMLNS message, a namespace declaration ( an xmlns attribute ) was found in the tree as a child of element <insert_1>::<insert_0>, but it does not have a valid value.
- Response
- This error can occur when the tree is incorrectly built. Check your ESQL or mapping to ensure that a valid value is being assigned to the xmlns attribute. If necessary, use a trace node or the message flow debugger to inspect the tree immediately before it is written.
- BIP5016
- The item <insert_0> of type <insert_1> is not one of the expected types for a top level element at this point in the XML document.
- Severity
- 20 : Error
- Explanation
- A top level element was found which did not have type xmlComment or xmlProcessingInstruction.
- Response
- Check that the message is well formed and adheres to the XML specification, and that the modifications made to the message in the message flow are also consistent with the XML specification.
- BIP5017
- The type of the root element <insert_0> is not one of the expected types for a top level element at this point in the XML document.
- Severity
- 20 : Error
- Explanation
- A root element was found which did not have type xmlElement, xmlParserRoot or xmlBitStream.
- Response
- Check that the message is well formed and adheres to the XML specification, and that modifications made to the message in the message flow are also consistent with the XML specification.
- BIP5102
- Data overflow. The field <insert_0> in message <insert_1> with a value of <insert_2> has caused an overflow.
- Severity
- 20 : Error
- Explanation
- While mapping data between its logical and physical representations, a data overflow occurred. The value being set in the logical representation is larger than the maximum value possible for the chosen logical type.
- Response
- Modify the message model or custom wire format mapping, redeploy to the parser and send the message through again.
- BIP5103
- The message identifier is not available to the parser.
- Severity
- 20 : Error
- Explanation
- The message identifier, for this message, is not being passed to the parser correctly.
- Response
- Correct the mapping, redeploy to the parser and send the message through again.
- BIP5105
- Memory allocation failed.
- Severity
- 20 : Error
- Explanation
- A failure was encountered while attempting to allocate memory.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5107
- Unknown internal time representation.
- Severity
- 20 : Error
- Explanation
- While mapping a time field to a physical type an invalid physical type was encountered.
- Response
- Modify the message model or custom wire format mapping, redeploy to the parser and send the message through again.
- BIP5113
- Error retrieving Message definition from dictionary.
- Severity
- 20 : Error
- Explanation
- The message identifier encountered was not found in the runtime dictionary.
- Response
- Check that you are using an appropriate dictionary for the message being sent and resubmit the message.
- BIP5115
- Element <insert_0> is not a member of the message.
- Severity
- 20 : Error
- Explanation
- While handling a message, the element <insert_0> was not defined as a direct member of the current message as defined in the runtime dictionary.
- Response
- Check that you are using an appropriate dictionary for the message being sent and resubmit the message.
- BIP5116
- Unexpected XML Element encountered: message set <insert_0>; message <insert_1>; tag encountered <insert_2>.
- Severity
- 20 : Error
- Explanation
- While handling an XML message a field or structure identifier was encountered which was not defined as a direct member of the current message as defined in the runtime dictionary. Current details are: Message Set = <insert_0>, Message = <insert_1>, Tag encountered = <insert_2>.
- Response
- Check that you are using an appropriate dictionary for the message being sent and resubmit the message.
- BIP5117
- XML parsing error (<insert_4>) encountered on line <insert_2> column <insert_3>. The XML parser was attempting to parse element (<insert_6>) in message (<insert_5>). The internal error code was (<insert_0>), (<insert_1>).
- Severity
- 20 : Error
- Explanation
- The above error was reported by the XML parser.
- Response
- This message is usually caused by a badly-formed XML message. Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. Note that the line number and column number quoted above give the position where the parser discovered the problem. The actual error may be earlier in the message.
- BIP5118
- XML input / output exception reported.
- Severity
- 20 : Error
- Explanation
- The above error was reported by the XML parser.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification.
- BIP5119
- XML Exception reported.
- Severity
- 20 : Error
- Explanation
- The error was reported by the BIPXML4C parser.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification.
- BIP5120
- XML parser reported by the BIPXML4C parser: error text <insert_0>.
- Severity
- 20 : Error
- Explanation
- The error was reported by the BIPXML4C parser Error text <insert_0>.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification.
- BIP5121
- Invalid buffer offsets on element: start offset <insert_0>; end offset <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred when attempting to write an XML message. An element has a start element offset of <insert_0> and an end offset of <insert_1>.
- Response
- Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification.
- BIP5122
- Unidentified field identifier <insert_0> in data stream.
- Severity
- 20 : Error
- Explanation
- While handling a PDF message, a field identifier, <insert_0> was encountered which was not found in the runtime dictionary.
- Response
- Check that you have deployed and are using the appropriate dictionary for the message being sent and resubmit the message.
- BIP5123
- Invalid buffer parameters: index <insert_0>; size <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal processing error has occurred. An invalid buffer was passed to the MRM parser. Properties of the buffer are : Index = <insert_0>; Size = <insert_1>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5124
- Internal Error: A call to DumpCWFMsgInfo failed with error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal processing error has occurred while writing out Custom Wire Format debug information. Error code <insert_0>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5125
- An error occurred during extraction of a message from the record-oriented bit stream.
- Severity
- 20 : Error
- Explanation
- The error was encountered while the bit stream was being read.
- Response
- Ensure that the message being passed is modeled correctly, and that the appropriate runtime dictionary and custom wire format information have been deployed successfully.
- BIP5126
- Error freeing temporary resources.
- Severity
- 20 : Error
- Explanation
- The error was encountered while freeing temporary resource used during the handling of a record oriented bitstream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5127
- Internal error while processing custom wire format data for <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error was encountered while extracting information from the deployed Custom Wire Format resource.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5128
- Error initializing MRM message <insert_1> with dictionary identifier <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message <insert_1> could not be initialized using the dictionary <insert_0>.
- Response
- Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message.
- BIP5129
- Error retrieving Message Translation Interface table entry from message handle: message <insert_1>; dictionary <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occurred while trying to get a table entry using the message <insert_1> and the dictionary <insert_0>.
- Response
- Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message.
- BIP5130
- Parser error retrieving dictionary handle: current message set id <insert_0>; current message id <insert_1>.
- Severity
- 20 : Error
- Explanation
- Error retrieving dictionary handle from message handle. Current message set id = <insert_0>, current message id = <insert_1>.
- Response
- Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message.
- BIP5131
- Message set identifier is not valid.
- Severity
- 20 : Error
- Explanation
- When parsing an MRM message the broker requires a valid message set identifier.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5132
- Custom Wire Format identifier is not valid.
- Severity
- 20 : Error
- Explanation
- When parsing an MRM, Custom Wire Format message the broker requires a valid message set identifier and a valid Custom Wire Format identifier.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5133
- An internal MRM parser error occurred.
- Severity
- 20 : Error
- Explanation
- Resource manager handle is not valid. When parsing an MRM message the broker requires a valid Message Translation Interface Resource manager handle which should have already been initialized.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5134
- Message identifier is not valid.
- Severity
- 20 : Error
- Explanation
- When parsing an MRM message the broker requires a valid message identifier.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5135
- Error writing custom wire format message.
- Severity
- 20 : Error
- Explanation
- An error occurred while writing to the message buffer.
- Response
- Please refer back to any previous error messages to determine why the error might have occurred.
- BIP5136
- Invalid Wire Format Identifier <insert_0>.
- Severity
- 20 : Error
- Explanation
- When processing an MRM message the broker requires a valid wire format identifier.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5140
- Error deploying Custom Wire Format descriptor: message set id <insert_0>; format descriptor id <insert_1>; format module <insert_2>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to deploy a custom wire format descriptor. Message set id = <insert_0>, Custom wire format descriptor id = <insert_1>, Custom wire format module = <insert_2>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5145
- Error setting up runtime dictionary resource using message set identifier <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to deploy message set. Use the Message Brokers Toolkit to match the message set Identifier : <insert_0>, to a message set name.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5146
- Error setting up custom wire format resource: message set id <insert_0>; format descriptor id <insert_1>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to deploy a custom wire format description record. Message set id = <insert_0>, Custom wire format descriptor Id = <insert_1>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5147
- Error setting up relationship of custom wire format to plug-in: message set id <insert_0>; format descriptor id <insert_1>; format module <insert_2>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to deploy a custom wire format descriptor. The resource manager relationship between message set and custom wire format file could not be set up. Message set id = <insert_0>, Custom wire format descriptor Id = <insert_1>, Custom wire format module = <insert_2>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5148
- Unexpected detail type <insert_0> received from broker.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to deploy a detail from the broker. The detail type: <insert_0> is unknown to the current MRM parser.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5149
- Error deleting runtime dictionary resource: message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to remove a deployed resource from the broker for message set <insert_0>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5151
- Error parsing PDF bit stream: message set id <insert_0>; message id <insert_1>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to parser an MRM native bit stream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5152
- Message definition does not contain element: message set identifier <insert_0>; message identifier <insert_1>; element found <insert_2>.
- Severity
- 20 : Error
- Explanation
- An element was encountered while parsing a message which does not belong, at the top level, in that message, according to the current message set.
- Response
- Check that you have packaged the message correctly and the correct message type is being used. Set the correct message properties and then resubmit the message.
- BIP5153
- Retrieving Message Definition from dictionary: message <insert_1>; message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- When handling an MRM message the broker requires valid message set and message identifiers. The broker was unable to retrieve a definition for a message.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5154
- Structure <insert_0> does not contain element <insert_1>.
- Severity
- 20 : Error
- Explanation
- The current message content implies that structure <insert_0> contains element <insert_1>. The message set definition does not support this.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5155
- An error occurred while retrieving definition of structure <insert_0> from run-time dictionary.
- Severity
- 20 : Error
- Explanation
- The message set definition does not have a definition for structure <insert_0>.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5156
- Definition for element <insert_0> not found in dictionary.
- Severity
- 20 : Error
- Explanation
- The deployed message set does not have a definition for element <insert_0>.
- Response
- Check that you have packaged the message set and the correct message properties correctly then resubmit the message.
- BIP5157
- Error allocating buffer for list of Deployed formats.
- Severity
- 20 : Error
- Explanation
- A failure was encountered while attempting to allocate memory.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5158
- Error retrieving list of deployed formats.
- Severity
- 20 : Error
- Explanation
- Error retrieving list of deployed formats.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5159
- Error deleting Custom Wire Format resource: message set id <insert_0>; wire format <insert_1>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to remove a deployed resource from the broker. Error removing customer wire format: <insert_1>. Message set Id = <insert_0>.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5160
- Error retrieving custom wire format for dictionary: message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error was detected when trying to retrieve a list of deployed custom wire formats from the broker for message set <insert_0>.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5161
- Error allocating buffer for list of deployed custom wire formats.
- Severity
- 20 : Error
- Explanation
- A failure was encountered while attempting to allocate memory.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5162
- Internal Error initializing the Message Translation Interface with the Resource Manager.
- Severity
- 20 : Error
- Explanation
- An internal processing error has occurred.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5163
- Invalid data source for broker database.
- Severity
- 20 : Error
- Explanation
- An internal error has occurred when trying to connect to a data source through the resource manager.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5164
- An error occurred when a type was applied to a value.
Element: <insert_0>
Expected type: <insert_1>
Actual type: <insert_2>
Actual value: <insert_3>
- Severity
- 20 : Error
- Explanation
- An error occurred when trying to match the value of the element with the type of the element.
- Response
- Check that the field is in the correct format for the data type expected.
- BIP5167
- A Custom Wire Format error occurred during the parsing or writing of message <insert_2>.
- Severity
- 20 : Error
- Explanation
- See the following messages for further details. Contact your IBM support center if you cannot resolve the error.
- BIP5168
- A Custom Wire Format writing error occurred involving an incorrect data conversion. Element <insert_2> is either too long, or is out of range for the physical data type of <insert_3>.
- Severity
- 20 : Error
- Explanation
- While the logical tree was being written to the bit stream, a data conversion error occurred.
- Response
- Change the definition of the element so that it can store the data safely. Alternatively change the message that is being written so that the value is in the correct range for the element.
- BIP5169
- A bitstream parsed by the CWF parser/writer is too long for the specified MRM Message Type. Message Set: <insert_0>, Message Type: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The data received for parsing by the CWF parser/writer, which is supposed to represent a message of type <insert_1> from Message Set <insert_0>, is too long to be of that Message Type.
- Response
- Check that the message data is valid for the specified Message Set and Message Type. If the problem persists, record all the details provided with this message and contact your IBM support center.
- BIP5170
- A Custom Wire Format parsing error occurred. The value <insert_3> of boolean element <insert_2> in the bit stream did not match the logical definition.
- Severity
- 20 : Error
- Explanation
- The value in the bit stream (<insert_3>) for element <insert_2> did not match either the 'Boolean True' or the 'Boolean False' values defined in the message set.
- Response
- Check that the 'Boolean True' and 'Boolean False' values on the CWF physical format properties of the message set are correct.
Check that the message has been constructed correctly.
Check that the message set and message type were correctly specified for the input message.
See previous errors for further details.
- BIP5171
- An error occurred while a Custom Wire Format message was being parsed:
Current message: <insert_2>
Current element: <insert_3>
Path from message root: <insert_4>
Offset from start of message: <insert_5>
- Severity
- 20 : Error
- Explanation
- See the following errors for more details.
- BIP5172
- An error occurred while a Custom Wire Format message was being read from the bit stream.
- Severity
- 20 : Error
- Explanation
- See following messages for further details.
- BIP5173
- There has been an attempt to write invalid data to the bit stream:
Current element: <insert_0>
Data type: <insert_1>
Data value: <insert_2>
- Severity
- 20 : Error
- Explanation
- Check why the data in the message is not valid for the data type of the element. Change the MRM definition of the element, or alter the data value being written. See the following messages for more details.
- BIP5174
- Custom Wire Format error. Insufficient memory: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Unable to allocate any more space. Insufficient memory available.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5175
- Custom Wire Format. Error opening file: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while opening a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5176
- Custom Wire Format. Error reading file: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5177
- Custom Wire Format. NLS conversion error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- During translation of a string between Unicode and bitstream representations an error occurred.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5178
- Custom Wire Format. Tree read error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading the tree from the Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5179
- Internal Error writing elements in custom wire format: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- An internal error has occurred whilst processing elements in the message set above.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5180
- A Custom Wire Format error has occurred. An unknown message type has been identified for message set <insert_2>
- Severity
- 20 : Error
- Explanation
- The Custom Wire Format parser or writer has received an unknown message type identifier in the message properties.
The specified message set (<insert_2>) does not contain a message type with this identifier.
Previous errors will supply the message set name and the message type identifier.
Check that the supplied message identifier is correct.
Check that the supplied message set identifier is correct.
Check that the message set contains a message type with the specified identifier.
- BIP5181
- A Custom Wire Format error has occurred. The message bit stream is smaller than expected.
Current element: <insert_2>
- Severity
- 20 : Error
- Explanation
- The bit stream is smaller than expected for a Custom Wire Format message of this message type.
Check that the input message is correctly structured, and has not been corrupted.
Check the MRM definition of this message type.
See the following messages for more details.
- BIP5182
- Custom Wire Format error. Write buffer overflow: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- A result would not fit in the supplied buffer.
- Response
- Increase the memory capacity of your system or try to free up some system memory by closing other applications.
- BIP5183
- Custom Wire Format error. Invalid buffer passed to parser or writer:
Function name <insert_1>
- Severity
- 20 : Error
- Explanation
- A null buffer has been encountered.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5184
- Custom Wire Format. Repeat logic error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The number of repeats assigned to an element is invalid.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5185
- Custom Wire Format. Resource error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error in Custom Wire Format. The resource manager successfully loaded the resource but the details are invalid.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5186
- Custom Wire Format. Error reading date: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a logical date from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5187
- Custom Wire Format. Error reading time: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a logical time from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5188
- Custom Wire Format. Error reading date and time: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a logical datetime from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5189
- Custom Wire Format. Error writing date: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while writing a logical date from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5190
- Custom Wire Format. Error writing time: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while writing a logical time from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5191
- Custom Wire Format. Error writing DateTime: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while writing a logical datetime from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5192
- Custom Wire Format error. Invalid date format: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a date format string from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5193
- Custom Wire Format error. Invalid time format: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a time format string from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5194
- Custom Wire Format error. Invalid DateTime format string time: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while reading a datetime format string from a Custom Wire Format file.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5195
- Custom Wire Format error. Invalid element length: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An invalid element length was encountered for a custom wire format element.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5196
- Custom Wire Format error. Invalid External Decimal: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- Custom Wire Format Invalid External Decimal.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5197
- Custom Wire Format error. Invalid Packed Decimal: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- Custom Wire Format Invalid Packed Decimal.
- Response
- Check that the packed decimal has been constructed correctly.
- BIP5198
- Custom Wire Format error. Field length overflow: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- A field length overflow has occurred.
- Response
- The Custom Wire Format field is not large enough to hold what is in the element. Review the message and check the lengths where necessary.
- BIP5199
- Data overflow or underflow in field <insert_0> of message <insert_1>. The message has a maximum or minimum length of <insert_2> in the dictionary. The actual length is <insert_3>.
- Severity
- 20 : Error
- Explanation
- The field <insert_0> in message <insert_1> has a maximum or minimum length defined in the dictionary of <insert_2>. The actual value of the field has a length of <insert_3>.
- Response
- Modify the message set or message flow and redeploy to the broker or modify the input message and resubmit to the broker.
- BIP5201
- Message Translation Interface error. Invalid Field Type: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned by MTIAddField and MTIAddFieldInstance if the field type parameter is invalid.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5202
- Message Translation Interface error. Invalid message handle: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message handle parameter passed into the Message Translation Interface API function that requires a message handle is not a valid handle for the message.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5203
- Message Translation Interface error. Invalid mode: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The 'mode' parameter is not set to one of the specified values.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5204
- Message Translation Interface error. Invalid Mode For Process order: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The 'mode' is not set to one of the specified values for the process order that has been specified.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5205
- Message Translation Interface error. Invalid Node Class: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The 'Node Class' parameter in a function call is not a valid value for that function.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5206
- Message Translation Interface error. Invalid Process Order: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The 'Process Order' parameter passed into the Message Translation Interface function is not a valid value.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5207
- Message Translation Interface error. Invalid Relative Position: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The 'Relative Position' parameter passed into the Message Translation Interface function is not valid.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5208
- Message Translation Interface error. Invalid Return Code: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5209
- Message Translation Interface error. Invalid Syntax Version: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The version number of the message is not correct.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5210
- Message Translation Interface error. Invalid relative position for element: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Message Translation Interface tried to add a new message element as a sub element to another message element that is not a predefined or self defining structure.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5211
- Message Translation Interface error. Invalid operation for element: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The type of a message element is not valid for the sort of operation that you are trying to perform on it.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5212
- Message Translation Interface error. Invalid message: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal error has occurred in the Message Translation Interface. The message handle parameter that was passed into a function is not a valid handle to a message.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5213
- Message Translation Interface error. Invalid structure: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error in the Message Translation Interface for an invalid structure.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5214
- Message Translation Interface error. Invalid message operation: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An operation carried out on a predefined message element is illegal.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5215
- Message Translation Interface error. Invalid identifier: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5216
- Message Translation Interface error. Invalid version number: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5217
- Message Translation Interface error. Invalid dump format: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned from MTIDumpMessage when the dump format parameter is invalid.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5218
- Message Translation Interface error. Invalid message name: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned by the function MTIGetMessageIdent when the message name parameter does not specify a valid message.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5219
- Message Translation Interface error. Invalid tag name: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>.
- Severity
- 20 : Error
- Explanation
- This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag.
- Response
- Check that the XML message contains the correct tags for the message type defined in the message set given above.
- BIP5220
- Message Translation Interface error. Invalid message mode: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_4>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned by the function MTIGetMessageIdent when the message mode parameter does not specify a valid mode.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5221
- Message Translation Interface error. Invalid parameter: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned from MTIGetPreDefinedTransactionDefinition when an invalid parameter is passed to this function.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5222
- Message Translation Interface error. Invalid instance array: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned by MTIAddAtom and MTIGetAtom when the instanceArray parameter is NULL, or when the length of the instanceArray (instanceArrayLen) is incorrect.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5223
- Message Translation Interface error. Invalid context tag: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned by MTIAddAtom and MTIGetAtom when an invalid context tag is passed to the context_tag parameter.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5224
- Message Translation Interface error. Invalid transaction id: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned by MTIAddAtom and MTIGetAtom when the message header of the goldMsgHandle parameter contains an invalid requestType.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5225
- Message Translation Interface. PDF write error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a Message Translation Interface PDF Write operation fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5226
- Message Translation Interface. PDF read error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a Message Translation Interface PDF Read operation fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5227
- Message Translation Interface error. PDF invalid length: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a Message Translation Interface PDF has an invalid length.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5228
- Message Translation Interface error. PDF invalid operation: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when an invalid operation is performed on a Message Translation Interface PDF.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5229
- Message Translation Interface error. PDF overflow: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a Message Translation Interface PDF operation causes an overflow.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5230
- Message Translation Interface error. PDF not initialized: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a Message Translation Interface PDF is not initialized.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5231
- Message Translation Interface. PDF initializing error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error initializing a Message Translation Interface PDF.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5232
- Message Translation Interface. PDF termination error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when there is an error terminating a Message Translation Interface PDF.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5233
- Message Translation Interface. PDF read header error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when there is an error reading a Message Translation Interface PDF Header.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5234
- Message Translation Interface. PDF write header error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when there is an error writing a Message Translation Interface PDF Header.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5235
- Message Translation Interface error. PDF invalid CP: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when there is an invalid CP operation on a Message Translation Interface PDF.
- Response
- Check that you have a valid broker installation. If the problem persists contact your IBM support center.
- BIP5236
- Message Translation Interface error. NLS file malformed: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Message Translation Interface returns this error if the NLS codepage file is found to contain data not conforming to the NLS file specification.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5237
- Message Translation Interface error. Invalid NLS string: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned when the Message Translation Interface encounters invalid data in an NLS string.
- Response
- Check that you have a valid broker installation. If the problem persists contact, your IBM support center.
- BIP5238
- Message Translation Interface error. Message header missing: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Message Translation Interface returned an error indicating that the message has no header attached.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5239
- Message Translation Interface error. No transaction value: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- A message does not have a transaction value.
- Response
- Check the message and redeploy.
- BIP5240
- Message Translation Interface warning: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. The Message Translation Interface function encountered a compatibility problem.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5241
- Message Translation Interface error. Missing mandatory element: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Message Translation Interface has returned an error indicating that the mandatory element is missing from a message.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5242
- Message Translation Interface error. Insufficient memory: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. This error is returned by any Message Translation Interface function that tries to allocate memory and fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5243
- Message Translation Interface error. Buffer full: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. This error indicates that a memory buffer, used while putting a message to bitstream, has filled completely.
- Response
- Check that you have a valid broker installation. If the problem persists contact your IBM support center.
- BIP5244
- Message Translation Interface error. Batch buffer full: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5245
- Message Translation Interface error. Empty message: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5246
- Message Translation Interface error. Field Def mismatch: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5247
- An index error has occurred in the Message Translation Interface:
Message set: <insert_2>
Message: <insert_3>
Parent element: <insert_4>
Current element: <insert_5>
Function name: <insert_1>
Error code: <insert_0>
- Severity
- 20 : Error
- Explanation
- An internal error has occurred. This error is returned when a function that uses an index as a reference to an instance of an element or structure has been given an index value that is invalid.
- Response
- Check that you have a valid broker installation. If the problem persists contact your IBM support center.
- BIP5248
- Message Translation Interface. Initialization error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. The Message Translation Interface failed to initialize correctly.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5249
- Message Translation Interface. Message parsing error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. The Message Translation Interface function encountered a problem with the structure of a message stored in a bitstream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5250
- Message Translation Interface error. Null pointer: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. This error code is returned by various Message Translation Interface functions when they are expecting one of their parameters not to be NULL.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5251
- Message Translation Interface error. Structure Def mismatch: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5252
- Message Translation Interface. System error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned if internal data structures used by the Message Translation Interface appear to have become corrupted by some system cause, as opposed to a software cause.
- Response
- Check that you have a valid broker installation. If the problem persists contact, your IBM support center.
- BIP5253
- Message Translation Interface. Trace error: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned when there is an error opening a trace file or stream.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5254
- Message Translation Interface. Element is field: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Message Translation Interface code.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5255
- Message Translation Interface error. Duplicate Peer IDs: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned when the MTIPutMessageToBitstream and MTIGetMessageFromBitstream functions find that two 'peer' message elements have the same TAG.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5256
- A bitstream error has occurred in the Message Translation Interface:
Message set: <insert_2>
Message: <insert_3>
Parent element: <insert_4>
Current element: <insert_5>
Function name: <insert_1>
Error code: <insert_0>
- Severity
- 20 : Error
- Explanation
- A file-handling error has occurred when opening, closing, or manipulating a bit stream.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5257
- Message Translation Interface error. Data out of bounds: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error occurs when encoding a predefined structure containing a character field with data that is too large for the character field.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5258
- Message Translation Interface not initialized: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error occurs when a Message Translation Interface function is called before the Message Translation Interface function MTIInitialize has been successfully called.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5259
- Message Translation Interface error. Options warning: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Message Translation Interface Options warning message.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5260
- Message Translation Interface error. Definition not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The definition of a predefined element/attribute, complex type/group or message was not found in the Standard Message Dictionary.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5261
- Message Translation Interface error. Element not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- A search for a message element did not find the element.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5262
- Message Translation Interface error. CStruct not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned when a CStruct can not be found in the Standard Message Dictionary.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5263
- Message Translation Interface error. Status information not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Message Translation Interface Status Information could not be found.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5264
- Message Translation Interface error. NLS file not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Returned by Message Translation Interface when NLS codepage file or DLL cannot be found or loaded.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5265
- Message Translation Interface error. NLS incompatible version: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Returned by Message Translation Interface when a NLS file is incompatible for use with the Message Translation Interface ( SBCS Message Translation Interface with MBCS codepage,) or a calling program isn't using the correct version of the Message Translation Interface.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5266
- Resource Manager error. Config File missing: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An Internal Error occurred. The configuration file is missing for the Resource Manager.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5267
- Resource Manager. Config File error: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. Configuration file is malformed for the Resource Manager.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5268
- Resource Manager error. Mapping File missing: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. The mapping file is missing for the Resource Manager.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5269
- Resource Manager error. Corrupt Mapping File: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred in the Resource Manager as the mapping file is corrupted.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5270
- Resource Manager error. Buffer too small: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Buffer parameter is too small.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5271
- Resource Manager. File error: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- A general file I/O error occurred in the Resource Manager.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5272
- Resource Manager error. Duplicate resource: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Resource Manager attempted to add a resource into the mapping file when it already exists.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5273
- Resource Manager error. Resource not found: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Resource Manager requested a resource that was not found in the mapping file.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5274
- Resource Manager error. Dependency exists: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Resource Manager tried to delete a resource on which a dependency exists.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5275
- Resource Manager error. Resource in use: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The resource is not present in the mapping file, but is still in use by the Resource Manager.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5276
- Resource Manager error. Plug-in module not found: message set <insert_2>; format identifier <insert_3>; function name <insert_2>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Plug-in module cannot be found / loaded.
- Response
- Check that you have a valid broker installation. If the problem persists contact your IBM support center.
- BIP5277
- Resource Manager error. Plug-in entry point not found: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Plug-in module does not contain a mandatory entry point.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5278
- Resource Manager not initialized: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Resource Manager has not been initialized.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5279
- Resource Manager error. Invalid DataSource: message set <insert_2>; format identifier <insert_3>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Resource Manager cannot find an ODBC DataSource or a Flat File.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5280
- Message Translation Interface error. Unknown Error.
- Severity
- 20 : Error
- Explanation
- An Unhandled Internal Error has occurred in the Message Translation Interface.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5281
- An error occurred during conversion from text to binary, caused by an invalid buffer:
Message set: <insert_0>
Resource type: <insert_1>
Resource name: <insert_2>
- Severity
- 20 : Error
- Explanation
- An invalid buffer has been passed for conversion from text to binary data during the deployment process.
- Response
- Check that you are using a valid message set and message flow. Ensure that you have a valid broker installation and redeploy to the broker. If the problem persists, contact your IBM support center.
- BIP5282
- Invalid children elements of structure element found.
- Severity
- 20 : Error
- Explanation
- A child element was found under a structure which is not a valid child for this structure.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5283
- Invalid repeating field within complex element <insert_0>.
- Severity
- 20 : Error
- Explanation
- A repeating element was detected within a complex element, <insert_0>. The repeating element was either not defined as repeating or was incorrectly encoded in the physical message. For example there may be another element between the instances of the repeating elements.
- Response
- Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
- BIP5284
- Message Translation Interface error. Invalid element handle: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error code is returned if the value in an element handle parameter passed into one of the Message Translation Interface functions is not a known handle or does not refer to a message element.
- Response
- Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
- BIP5285
- Message Translation Interface parsing errors have occurred.
Message set name: <insert_0>
Message format: <insert_2>
Message type path: <insert_3>
- Severity
- 20 : Error
- Explanation
- Review other error messages to find the cause of the errors.
- BIP5286
- Message Translation Interface writing errors have occurred.
Message set name: <insert_0>
Message format: <insert_2>
Message type path: <insert_3>
- Severity
- 20 : Error
- Explanation
- Review other error messages to find the cause of the errors.
- BIP5287
- Message Translation Interface error. Offset greater than message length: message set <insert_0>; message <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message received is invalid because the offset of an element in the message is greater than Message length.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5288
- An MRM parsing error has occurred. The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this type.
Number of bytes parsed: <insert_0>
Actual length of message: <insert_1>
- Severity
- 20 : Error
- Explanation
- When parsing the instance message according to the message model, the parser reached the end of the message definition before it reached the end of the bit stream. Either the message bit stream has been incorrectly constructed, or the message model is incorrect.
- Response
- Ensure that the message bit stream is correctly formed.
Ensure that the message properties (name, physical format, message set) are correct.
Ensure that the message model for this message type is correct. In particular, check that the element lengths and number of repeats are correct. You should find the message set and message type quoted in other error messages.
If this is a TDS message, enable user trace (debug level) and parse the message. In the trace file check the messages issued by the TDS parser to find the problem.
- BIP5289
- Message Translation Interface error. Message Set ID too large for buffer: message set <insert_2> (size <insert_1>); buffer size <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Message Set ID <insert_2> exceeds the length of the internal buffer used to store the Id. Current buffer size is <insert_0>. The Message Set Id size is <insert_1>
- Response
- Check that you have a valid Message Set identifier and that the length does not exceed the current buffer size allowed to store it.
- BIP5290
- Invalid value for physical data type in Custom Wire Format: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Examined the physical type of an element. The value of the field to be written out is negative and the physical datatype for the output is unsigned.
- Response
- Check that you have a valid physical type associated with this field in the Custom Wire Format characteristics or that the logic of the message flow is correct.
- BIP5291
- The field <insert_0> in message <insert_1> has a repeat count defined in the dictionary of <insert_2>. The actual number of repeats is <insert_3>.
- Severity
- 20 : Error
- Explanation
- Examined the repeat count of an element. The number of field repeats to be written out does not match the value defined in the dictionary.
- Response
- Check that you have the correct number of repeats for this field in the Custom Wire Format characteristics or that the number of the repeats for this element in the message flow is correct.
- BIP5292
- Custom Wire Format error: Expected element not found: message set <insert_2>; message <insert_3>; parent element <insert_4>; current element <insert_5>; function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- While mapping a physical data type to a logical type an expected element was not found.
- Response
- Check that the current element given above is in the incoming message.
- BIP5293
- The Dictionary is not compatible with this Parser.
- Severity
- 20 : Error
- Explanation
- The dictionary for this message set is not compatible with this version of the parser.
- Response
- The message set makes use of functionality not supported by the broker to which it was deployed. Please refer to the details provided when adding the message set to your broker archive file and/or consider upgrading your broker.
- BIP5294
- The MRM bitstream worker associated with message format <insert_3> of message set <insert_2> is not valid.
- Severity
- 20 : Error
- Explanation
- The required bitstream worker (MRM parser) for message set/message format pair (<insert_2>, <insert_3>) is not valid. Although the bit stream worker library has been successfully loaded, it is not valid for the requested message format. It is possible that your installation is incomplete or has been corrupted.
- Response
- The bitstream workers are loaded when the message broker starts an execution group (DataFlowEngine instance).
Check the application event viewer (or system log) for error messages when the broker is started or when a message set is deployed to the broker.
Check that the appropriate bitstream worker library file (dll or shared object) exists in the correct directory and that any library paths are valid. On a Windows platform these library files should be located in the <Install Dir>&bsl;bin directory. On all other platforms the files should be located in the <Install Dir>/lib directory.
The following list identifies the relationship between an MRM parser and the required library files:
Custom Wire Format (CWF) : 'bipcwfworker.wrk' or 'bipcwfworker64.wrk'
Tagged/Delimited Format (TDS) : 'biptdsworker.wrk' or 'biptdsworker64.wrk'
MRM XML Format : 'bipxmlworker.wrk' or 'bipxmlworker64.wrk'
If the problem cannot be resolved it is recommended that you reinstall the product.
- BIP5295
- Resource Manager: Environment variable missing or invalid.
- Severity
- 20 : Error
- Explanation
- A required environment variable is missing or has an invalid value.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5296
- Resource Manager: File name generation failed.
- Severity
- 20 : Error
- Explanation
- A system error occurred during generation of a new file name for a resource.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5297
- Resource Manager: Directory creation failed.
- Severity
- 20 : Error
- Explanation
- A system error occurred during creation of a resource directory.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5298
- Resource Manager: An XML parsing error occurred.
- Severity
- 20 : Error
- Explanation
- An XML parsing error occurred, most likely during the processing of deploy data used for the registration of multiple related resources. This probably means that the deploy data is invalid.
- Response
- This error message is thrown in the Resource Manager's rmDeploy() method. Attempt to deploy a simple messageset initially to see if there is a problem with the users configuration. Verify that all components are compatible ( versioning).
- BIP5299
- Resource Manager: Deploy file cannot be found.
- Severity
- 20 : Error
- Explanation
- The file containing deploy data, used for registering multiple related resources, could not be found. The specified deploy file does not exist.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5301
- Resource Manager: An error occurred during map info initialization.
- Severity
- 20 : Error
- Explanation
- A mapping information object cannot be initialized properly from the database. The cause of the error can be failure to allocate memory.
- Response
- Examine memory usage and free up the required resources.
- BIP5302
- Resource Manager: An error occurred during cache info initialization.
- Severity
- 20 : Error
- Explanation
- This error is currently not used.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5303
- Resource Manager: Bitstream worker manager initialization error.
- Severity
- 20 : Error
- Explanation
- A Bitstream Worker Manager could not be created. This is caused by memory allocation failure.
- Response
- Examine memory usage and increase memory available to the broker.
- BIP5304
- A runtime dictionary resource for message set <insert_2> cannot be found.
The list of known message sets is: <insert_3>
- Severity
- 20 : Error
- Explanation
- A runtime dictionary resource for a message set was requested by the broker, but the resource could not be found as it is not registered to this execution group. This means that the message set was not deployed, or was not deployed properly, to the execution group.
- Response
- Check that the dictionary identifier (e.g. DLPLT0807A001) or dictionary name (shown in the Message Brokers Toolkit for the message set) is the same as that specified in the message instance or input node of the message flow. Verify that the correct message set is associated with the execution group, and redeploy.
- BIP5305
- Resource manager: Dictionary initialization error for message set <insert_2>
- Severity
- 20 : Error
- Explanation
- The creation of an object to hold standard dictionary information or physical format descriptor information failed: message set ID: <insert_2>. The cause is probably memory allocation failure.
- Response
- Examine memory usage and increase the memory available to the broker. Stop and restart the broker, then redeploy this message set. If the problem persists, contact your IBM support center.
- BIP5306
- Resource manager: Bitstream worker initialization error, for format <insert_2>.
- Severity
- 20 : Error
- Explanation
- The creation of a bitstream worker object failed: format name: <insert_2>. The resource manager was unable to find the requested worker in the cache, and subsequently was unable to load it into the cache. This might be caused by a memory allocation failure. It could also be caused by a corrupt worker file (dll or shared object file with the extension .wrk), or the requested file might not be available.
- Response
- Examine memory usage and increase memory available to the broker. Check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory. .wrk files reside in the <install dir>&bsl;bin directory on Windows, and in <install dir>/lib on other platforms.
The following list identifies the relationship between an MRM parser and the required library files :
Custom Wire Format (CWF) : 'bipcwfworker.wrk' or 'bipcwfworker64.wrk'
Tagged/Delimited Format (TDS) : 'biptdsworker.wrk' or 'biptdsworker64.wrk'
MRM XML Format : 'bipxmlworker.wrk' or 'bipxmlworker64.wrk'
If the problem cannot be resolved it is recommended that you reinstall the product.
- BIP5307
- Resource Manager: Unexpected null pointer.
- Severity
- 20 : Error
- Explanation
- This is an internal program error that occurs when an unexpected null pointer is passed to a function.
- Response
- Record the full details provided with this message and contact your IBM support center. Trace files will help identify where the error is occurring.
- BIP5308
- Resource Manager: No workers installed.
- Severity
- 20 : Error
- Explanation
- This error is currently not used.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5309
- Resource Manager: Invalid bitstream worker: message set id <insert_0>, wire format descriptor id <insert_1>.
- Severity
- 20 : Error
- Explanation
- The bitstream worker library specified for message set id/wire format descriptor pair (<insert_0>, <insert_1>) is not a valid bitstream worker library. The file that was loaded failed to provide the Resource manager with required information regarding its factory class, the number of formats and the formats it supports and their level.
- Response
- Check that all the worker files (indicated by the extension *.wrk e.g. bipxmlworker.wrk) located in the worker load directory are in fact workers and that the files have not been corrupted. E.g. On Windows workers are loaded from the <MQSI dir>&bsl;bin directory. Other platforms use the <MQSI dir>/lib directory. Check for other error messages that may indicate which file is causing the problem.
- BIP5310
- Resource Manager: Memory allocation error.
- Severity
- 20 : Error
- Explanation
- Memory allocation failed.
- Response
- Free up some memory in the system before continuing.
- BIP5311
- Resource Manager: Null format name for wire format descriptor <insert_1>.
- Severity
- 20 : Error
- Explanation
- This is an internal program error that occurs when the format name associated with a wire format descriptor resource is null. Wire format descriptor: <insert_1>.
- Response
- Trace files may indicate the source of the error. Record the full details provided with this message and contact your IBM support center.
- BIP5312
- Resource Manager: Caching error.
- Severity
- 20 : Error
- Explanation
- This is an internal program error that occurs if a cache entry is invalid.
- Response
- Record the full details provided with this message and contact your IBM support center. Trace files may be required to help identify the sequence of calls.
- BIP5313
- Message format <insert_3> is not defined for message set <insert_2>.
- Severity
- 20 : Error
- Explanation
- The message broker has received a message for processing within the MRM domain.
However, this message could not be processed because the message format specified via the physical format identifier <insert_3> has not been defined for message set <insert_2>.
Note that the message format is used to describe the physical representation of the message and can be specified by way of either the properties on an input node, or dynamically within an RFH2 message header.
- Response
- If the physical format identifier was intended to identify a message format, you should perform one or more of the following actions:
1) Check that the message format has been specified correctly on the MQ input node or within the RFH2 header.
2) Check that the correct message set has been specified on the MQ input node or within the RFH2 header
3) Add the appropriate physical format information to your message set and redeploy your message set.
4) Ensure that your message set has been correctly deployed.
- BIP5314
- Resource manager: Descriptor initialization error for message set ID: <insert_2>.
- Severity
- 20 : Error
- Explanation
- The creation of an object to hold physical format descriptor information failed: message set ID: <insert_2>. The cause is probably a memory allocation failure.
- Response
- Examine the memory usage and increase the memory available to the broker. Stop and restart the broker, then redeploy this message set. If the problem persists, contact your IBM support center.
- BIP5315
- Resource Manager: No transaction started.
- Severity
- 20 : Error
- Explanation
- This is an internal program error which occurs if an attempt is made to end or cancel a transaction even though no transaction has been started.
- Response
- Try to restart the broker service and retry the operation. If this fails stop the broker and the database services and restart both. Examine both system logs and database logs for errors.
- BIP5316
- A library error occurred during loading of the MRM bitstream worker <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message broker has attempted to load the <insert_1> bitstream worker. However, this attempt was unsuccessful.
The bitstream worker libraries are used by the MRM domain to process messages with a particular physical representation. The following list identifies the relationship between an MRM parser and the required library files:
Custom Wire Format (CWF) : 'bipcwfworker.wrk' or 'bipcwfworker64.wrk'
Tagged/Delimited Format (TDS) : 'biptdsworker.wrk' or 'biptdsworker64.wrk'
MRM XML Format : 'bipxmlworker.wrk' or 'bipxmlworker64.wrk'
Attempts to process messages with the physical format identified above will not be successful until this problem is resolved.
- Response
- The bitstream workers are loaded when the message broker starts an execution group (DataFlowEngine instance).
Check that the <insert_1> bitstream worker library (dll or shared object) exists in the correct directory. On a Windows platform the library files should be located in the <Install Dir>&bsl;bin directory. On all other platforms the files should be located in the <Install Dir>/lib directory.
Check the application event viewer (or system log) for error messages when the broker is started or when a message set is deployed to the broker.
Also check that the user ID under which the broker is executing has sufficient privileges to load the file.
- BIP5317
- Resource Manager: Bitstream worker API error.
- Severity
- 20 : Error
- Explanation
- This is an internal error produced by a call to one of the functions of the bitstream worker API.
- Response
- Check that the bitstream worker file has not been corrupted. Check System logs for errors.
- BIP5318
- Resource manager has detected a message dictionary ID mismatch for message set ID: <insert_2>, physical format descriptor ID: <insert_3>.
- Severity
- 20 : Error
- Explanation
- There has been an attempt to register a resource with a message set ID that does not match the message set ID specified within the resource.
Message set ID: <insert_2>
Physical format descriptor ID: <insert_3>.
- Response
- Stop the broker and delete any pending messages from the system queues on the broker's queue manager in WebSphere MQ Explorer. Retry the operation and examine the system logs for any errors. Check to see if any other errors are being generated. Finally, record the full details provided with this message and contact your IBM support center.
- BIP5319
- Resource Manager: Already Initialized.
- Severity
- 20 : Error
- Explanation
- This is an internal program error which occurs when an attempt is made at initializing the Resource Manager more than once. The initialization occurs in the rmInitialise() method in the MtiImbParser factory class constructor.
- Response
- Trace files for the Execution group should be collected. Record the full details provided with this message and contact your IBM support center.
- BIP5320
- Resource Manager: Incorrect count.
- Severity
- 20 : Error
- Explanation
- Internal program error - a Resource Manager function has been called with an incorrect parameter value.
- Response
- Stop and restart the broker and redeploy the resource. Retry the operation. If it still fails record the full details provided with this message and contact your IBM support center.
- BIP5321
- Resource Manager: Database Error. Either the database or WBIMB are wrongly configured, or there is an internal program error.
- Severity
- 20 : Error
- Explanation
- A database error has occurred.
- Response
- Verify that userids and passwords used are valid (attempt to connect via an SQL prompt).
Stop and restart the database. Retry the operation.
Examine the database logs and if possible turn on database tracing.
If possible, use an ODBC tracing tool.
Make sure that the database and WBIMB are properly installed.
If the problem persists, record the full details provided with this message and contact your IBM support center.
- BIP5322
- Dictionary Info Error.
- Severity
- 20 : Error
- Explanation
- Unable to set the Dictionary Info object in the setDictionaryInfo() call.
- Response
- Review further error messages for an indication to the cause of the errors.
- BIP5323
- Dictionary Iterator Error has occurred.
- Severity
- 20 : Error
- Explanation
- Unable to set context from the tag supplied in the setContextFromTag() call.
- Response
- Verify that the message type belongs to the Dictionary that was loaded. Review further error messages for an indication to the cause of the errors.
- BIP5324
- Error occurred during FI parser Event.
- Severity
- 20 : Error
- Explanation
- Unable to allocate a worker info object. This is probably because of memory problems in the system.
- Response
- Examine the systems memory usage and allocate additional memory. Retry the operation. If the problem persists contact support.
- BIP5325
- A message dictionary error has occurred. Dictionary <insert_2> has not been initialized in function <insert_1>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> was called before the dictionary <insert_2> was initialized. This is an internal error.
- Response
- Redeploy the dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5326
- A message dictionary error has occurred. An invalid member ID was passed to function <insert_1> when it was processing element <insert_3> of dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> has received an invalid member ID when it was processing the element <insert_3> in the dictionary <insert_2>. This can be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5327
- A message dictionary error has occurred. A negative index was passed to function <insert_1> for dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> was passed a negative index for the dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5328
- A message dictionary error has occurred. An invalid index was passed to function <insert_1> when it was processing dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> was passed an invalid index when it was processing the dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5329
- A message dictionary error has occurred. While processing dictionary <insert_2>, function <insert_1> was passed an out-of-range index.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: While processing the dictionary <insert_2> the function <insert_1> was passed an index that was greater than the recorded number of rows for an internal structure. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5330
- A message dictionary error has occurred. Tag <insert_3> was not found when function <insert_1> was processing dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- MtiImbParser:Standard dictionary error: A definition was not found. The function <insert_1> was unable to find the tag <insert_3> in the dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. If the message type is included in the input message verify that it is a member of the message set specified. Verify that the message instance corresponds to the dictionary specified. Review further error messages for an indication of what caused the errors.
- BIP5331
- A message dictionary error has occurred. An invalid tag name <insert_3> was found for dictionary <insert_2> in function <insert_1>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: Function <insert_1> did not find the tag, alias, or type <insert_3> in the dictionary <insert_2>. Tags must not be zero length, and tags, types, and aliases must not exceed 255 characters in length. This might be an internal error, or might indicate a problem with the dictionary.
- Response
- Verify that items such as message type (possibly embedded in the message itself) do not exceed 255 characters. Examine other tags that might exceed this value and reduce to the required length. Review further error messages for an indication of what caused the errors. Redeploy the message dictionary.
- BIP5332
- While the message was being mapped to the logical model an error occurred in function <insert_0>, for dictionary <insert_1>; element <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary iterator error: The function <insert_0> reported an error when processing the dictionary <insert_1>; the element was <insert_2>.
- Response
- Redeploy the message set containing this dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5333
- A message dictionary error has occurred. A row count error occurred in function <insert_1> for dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> reported a row count error when processing the dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary, and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5334
- A message dictionary error has occurred. A null property format error occurred in function <insert_1> while it was processing dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> reported a null property format error when it was processing the message dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5335
- A message dictionary error has occurred. A null property name error occurred in function <insert_1> while it was processing dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> reported a null property name error while it was processing the message dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5336
- A message dictionary error has occurred. A parse error occurred in function <insert_1> while it was processing dictionary <insert_2>.
- Severity
- 20 : Error
- Explanation
- Standard dictionary error: The function <insert_1> reported a parse error while it was processing the dictionary <insert_2>. This might be an internal error, or there might be a problem with the dictionary.
- Response
- Redeploy the message dictionary and verify that no errors were reported. Ensure that the dictionary that is deployed is the dictionary specified in the input message (or input node on the message flow). Review further error messages for an indication of what caused the errors.
- BIP5337
- An error was found during the parsing process. Message identifier <insert_0> differs from expected identifier <insert_1>.
- Severity
- 20 : Error
- Explanation
- The message identifier found in the bit stream (<insert_0>) differs from the expected message identifier (<insert_1>).
- Response
- The body of the input message contains a message identifier (for example, the outermost tag of an XML message). The message identifier has also been specified in a header (for example, RFH2) or in the properties of an input node. The two identifiers do not match. Fix the problem and resend the message.
- BIP5338
- A Dictionary Iterator Error has occurred during writing.
- Severity
- 20 : Error
- Explanation
- DI Handler Error: Unable to spawn a new MtiImbDictionaryIterator object. This can occur if no Dictionary was specified or if there was insufficient memory to allocate a new Dictionary iterator object.
- Response
- Examine memory usage on the system and free up the required resources if necessary. Examine the message flow, if the input node does not require/specify a dictionary and it is not contained in the message instance ( e.g self defining XML) but the output format requires member ids e.g CWF. Change the message flow, or specify the Dictionary in the instance if this is the case. Review further error messages for an indication to the cause of the errors.
- BIP5339
- There is a mismatch between the message tree and the logical definition. This occurred when element <insert_2> in message set <insert_1> was being written.
- Severity
- 20 : Error
- Explanation
- While the message was being written, the message tree did not match the logical structure of the message. The problem was encountered while element <insert_2> in message set <insert_1> was being written.
- Response
- This problem is usually caused by a badly-structured input message. It can also be caused by a badly-structured output message tree. Check that the structure of the input message matches the logical structure of the message definition. Check that elements defined as simple elements do not have child elements. If necessary, check that elements occur in the correct sequence, and with the correct number of repeats. If you have modified the message set or message type property in your message flow, check that these are correct.
- BIP5340
- A Dictionary Iterator Error has occurred during writing.
- Severity
- 20 : Error
- Explanation
- DI Handler Error: Unable to Retrieve member id. The getMemberId() method will throw this error if it receives a NULL dictionary iterator pointer. In this case it is an internal error. It can also be caused if the member id returned by the dictionary iterator is < 1.
- Response
- Verify that the dictionary was deployed without error. Attempt to redeploy the Dictionary. Review further error messages for an indication to the cause of the errors. Obtain function level traces and contact support.
- BIP5341
- An IMB syntax node Type Error has occurred during writing.
- Severity
- 20 : Error
- Explanation
- MtiImbSyntax Error: Unknown or Invalid Type found in IMB Tree. A call to getData() on a MtiImbSyntaxElement has found a type associated with an ImbValue which it cannot handle. This is an internal error.
- Response
- Gather trace logs and contact support detailing what operations were performed. Examine any ESQL to see what type of manipulation occurred on elements. Review further error messages for an indication to the cause of the errors.
- BIP5342
- An IMB syntax node Category Error has occurred during writing.
- Severity
- 20 : Error
- Explanation
- MTIIMBSyntax Error: An Unknown or Invalid Category was associated with a node in the IMB Tree. This is an internal error.
- Response
- Contact support, providing trace files and details of the operations performed. The structure of the input message will be important. Review further error messages for an indication to the cause of the errors.
- BIP5343
- No physical format descriptor was found when a message in message set <insert_0> was being processed.
- Severity
- 20 : Error
- Explanation
- The physical format name determines the parser or writer which will be used to process a message. The message did not specify a physical format in its message properties, and the message set (<insert_0>) did not provide a default. This means that the message cannot be parsed or written.
- Response
- Ensure that a physical format is supplied. You can specify the physical format name in the 'format' field of the RFH2 header, in the input node properties, or in the 'Default Wire Format' property of the message set.
Supply a physical format name in the properties of the message, or input node of the flow. Alternatively set a 'Default Wire Format' for the message set and redeploy. Check that the message set was deployed successfully.
- BIP5344
- Custom Wire Format output: There is a mismatch between the logical definition and the message tree.
Message: <insert_0>
Element: <insert_1>
- Severity
- 20 : Error
- Explanation
- The CWF writer has been given a message tree that does not match the logical message definition.
The elements may have been added to the message tree in the wrong order - elements in the tree must be in the same order as the message definition.
There may be elements missing from the message tree. All elements are compulsory when writing a CWF message. Each element must be present in the tree, unless a default value is defined for that element.
The message type or message set may be incorrect.
- Response
- If the output message was assembled in a Compute node, check that the elements were added to the message in the order specified in the logical message definition.
Check that the output message contains all the elements in the logical message definition (perhaps you need to copy the entire input message to the output tree before modifying it).
Check that the output message has the correct message set and message type properties.
Check that the output message does not contain self-defining elements (elements not included in the message definition).
Check that any missing elements have default values defined.
Collect debug-level user trace, which contains information on how the message tree is being matched with the message definition.
- BIP5345
- CWF Worker: The tree contains an illegal choice element.
Message name: <insert_0>
Element name: <insert_1>
- Severity
- 20 : Error
- Explanation
- The CWF worker cannot handle certain types of elements (those for which the length depends on the actual value of the message) within a 'choice' element. This error indicates that the CWF Worker has encountered such elements and cannot proceed with parsing or writing.
- Response
- Redesign the message in question so that its 'choice' elements do not contain length/repeat references or the illegal physical types (null, null terminated string, length encoded string 1 and length encoded string 2) or use a different wire format.
- BIP5346
- CWF Worker: The following internal error occurred: <insert_0>
Data: <insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>
- Severity
- 20 : Error
- Explanation
- An internal error occurred in the CWF Worker.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5347
- MtiImbParser2: RM has thrown an unknown exception.
- Severity
- 20 : Error
- Explanation
- Returned by the RM when an unknown exception is thrown. This is an internal error.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible.
- BIP5348
- MtiImbParser: Failed to load all the required resources.
- Severity
- 20 : Error
- Explanation
- The MtiImbParser failed in the function loadParserResources() which loads all the resources before a parse can commence.
- Response
- Check previous errors to indicate which resource failed to load. Ensure the resource is available to the parser. If the problem can be replicated record details of the error and contact support.
- BIP5349
- No Physical Format layer with Wire Format Identifier <insert_0> in message set.
Each Physical Format layer in a message set is identified by a Wire Format Identifier (WFI).
The <insert_0> parser or writer could not find any Physical Format with the specified WFI in this message set.
- Severity
- 20 : Error
- Explanation
- Wire Format Identifiers identify the physical format information for an MRM Message Set. They are created and stored in a database when the Message Set is deployed. A WFI for Wire Format <insert_0> could not be found in the database, which means that the Message Set identifier specified for the message does not match any physical format layer in the message set.
See previous messages for details of the Message Set and Wire Format Identifier
- Response
- Check that the Message Set Identifier specified for the message is correct. Check that the message set contains a physical format layer with a WFI of <insert_0>. Check that the message set deployed successfully.
- BIP5350
- There was a Custom Wire Format error when writing the message <insert_2>.
The error occurred during or after the writing of element <insert_3>.
- Severity
- 20 : Error
- Explanation
- Check that the message has been built correctly and conforms to the MRM model.
Review other error messages for more details.
- BIP5351
- An unexpected message definition has been found in the message bitstream. Message type <insert_2> was not found in message type path <insert_1>, for message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to parse an embedded message of message type <insert_2>, as part of a multipart message using a message type path. However, the message type <insert_2> could not be located in the message type path specified, <insert_1>. Additional information: Message set <insert_0>.
- Response
- Ensure that the correct message set has been loaded for the message being parsed. Check the message set property 'Message Type Prefix', and the message type path specified on the message being processed. Ensure that the message conforms to the specified structure. If the problem still occurs, record the full details provided with this message and contact your IBM support center.
- BIP5352
- While a multipart message was being processed, an embedded message was received that was out of the specified order. The specified message type path <insert_1> does not match the actual message type path of the logical tree <insert_2>. The message set is <insert_0>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to add a parsed message in the wrong position according to the message type path. The message type path in the tree, <insert_2>, was compared with the specified message type path <insert_1>. Additional information: Message set <insert_0>.
- Response
- Ensure that the correct message set has been loaded for the message being parsed. Check the message set property 'Message Type Prefix', and the message type path specified on the message being processed. Ensure that the message conforms to the specified structure. If the problem still occurs, record the full details provided with this message and contact your IBM support center.
- BIP5353
- A mismatch between the message type prefix <insert_1> and the message type path <insert_2> has occurred, for a message in message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message type prefix, <insert_1>, specified for message set <insert_0>, was incompatible with the specified message type path, <insert_2>.
- Response
- This error is most commonly caused by specifying the message type path as an absolute path (prefixed with '/'), while also having a different message type prefix specified for the message set.
Ensure that the correct message set has been deployed for the message being parsed.
If the message set property 'Message Type Prefix' is specified, and the message is using an absolute message type path, ensure that they match.
Make sure the message conforms to the structure specified by the message type path.
If the problem still occurs, record the full details provided with this message and contact your IBM support center.
- BIP5354
- MTI internal error: diagnostic information <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal software error has occurred in the Message Translation Interface Parser. The diagnostic information associated with this message is: <insert_0>.
- Response
- Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
- BIP5355
- Choice not resolved and output properties are not compatible: Message Set <insert_0>, Message Format <insert_1>, Message Type Path <insert_2>, Parent Element <insert_3>.
- Severity
- 20 : Error
- Explanation
- An unresolved choice was present in the message tree when the output properties are not compatible. For a choice to be written to the output without being resolved, the Message Set, Message Format, Message Type Path, CCSID and Encoding of the message being written must all be the same as that in the parsed message.
- Response
- Ensure that all the properties are compatible or that all choices are resolved.
- BIP5356
- An error has occurred while a multipart message was being written. Element <insert_1> cannot have an embedded message <insert_0>, for message set <insert_2>.
- Severity
- 20 : Error
- Explanation
- An error occurred when an attempt was being made to match an embedded message with the logical model. The embedded message <insert_0> is not allowed as a child of <insert_1>. The message set was <insert_2>.
- Response
- Ensure that the model allows a message in the position that <insert_0> was found. This error can also be caused by having more than one message as a child of an element with type composition message. Make sure such elements only have a single message as a child.
- BIP5357
- The message type path <insert_2> is incompatible with message type prefix <insert_1>, in message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- The error may have occurred because there is a message type prefix specified in message set <insert_0> but the message type path is relative (does not start with the '/' character) instead of absolute.
- Response
- Check that the message type prefix combined with the message type path resolves to a valid complete message type path. Make sure that there is correct use of a leading '/' character for absolute paths.
- BIP5358
- Multiple levels of unresolved embedded messages are not supported.
- Severity
- 20 : Error
- Explanation
- There is currently no support for embedded messages with unresolved identity embedded in another message with an unresolved identity.
- Response
- An unresolved embedded message is a message that is contained in another message and whose identity is established by ESQL statements only. The current implementation supports only one level of unresolved embedded messages.
- BIP5359
- Input Message is only partially parsed.
- Severity
- 20 : Error
- Explanation
- The input message is only partially processed. This may be due to the presence of one or more unresolved embedded messages that have not been explicitly referred to in the ESQL contained in a compute node. This may cause a failure when some workers attempt to write the message.
- Response
- An unresolved embedded message is a message that is contained in another message and whose identity is established by ESQL statements only. Please ensure that all unresolved embedded messages in the input message are referred to explicitly, i.e. named, in the ESQL code.
- BIP5360
- The writing of NULL binary data is not supported in the Custom Wire Format physical format.
Message set: <insert_0>
Message type: <insert_1>
Element ID: <insert_2>
- Severity
- 20 : Error
- Explanation
- When message <insert_1> was being written, binary element <insert_2> had a NULL value. The CWF physical format does not support special representation of NULL values for binary items.
- Response
- Update the message flow to ensure that element <insert_2> does not have a NULL value, or alter the message definition.
- BIP5361
- Message validation error. The value <insert_1> for element <insert_0> in the message is not valid.
The value is less than the minimum inclusive value <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message is less than the minimum inclusive value specified for the element.
- Response
- Modify the message set or message flow and redeploy to the broker, or modify the input message and resubmit to the broker.
See the following messages for more details.
- BIP5362
- Message validation error. The value <insert_1> for element <insert_0> in the message is not valid.
The value is greater than the maximum inclusive value <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message is greater than the maximum inclusive value specified for the element.
- Response
- Modify the message set or message flow and redeploy to the broker, or modify the input message and resubmit to the broker.
See the following messages for more details.
- BIP5363
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> is shorter than the minimum length <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message is shorter than the minimum length specified for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5364
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> is longer than the maximum length <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message is longer than the maximum length specified for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5365
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> does not conform to the DateTime type as denoted by template <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message does not conform to the DateTime simple type specified for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5366
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> contains more than <insert_2> fractional digits.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message contains more fractional digits than specified by the scale value for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5367
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> is not in the list of allowed values.
- Severity
- 20 : Error
- Explanation
- The value for the element in the message is not one of the enumeration values specified for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5368
- Message Validation failure. Invalid value for element <insert_0>.
The value is a null value but null values are not permitted for this element.
- Severity
- 20 : Error
- Explanation
- The value for this element in the message is null but null values are not permitted for this element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5369
- Message Validation failure. Invalid value for element <insert_0>.
The value <insert_1> does not match the pattern <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value for the element does not match the pattern specified for the element.
- Response
- Modify the message set or messageflow and redeploy to the broker or modify the input message and resubmit to the broker.
See following the messages for more details.
- BIP5370
- Message Validation failure. Invalid pattern for element <insert_0>.
The pattern <insert_1> is not valid.
- Severity
- 20 : Error
- Explanation
- The pattern specified as a value constraint for the element is not valid.
- Response
- Modify the message set and redeploy to the broker.
See following the messages for more details.
- BIP5371
- There was a message validation error. Element or attribute <insert_0> failed to validate. The path to the element is <insert_1>. The element is defined as a child of a complex type or group that has a content validation setting of 'Closed' and composition <insert_2>.
- Severity
- 20 : Error
- Explanation
- Possible causes could be:
1. The child has not been defined as a member of its parent complex type or group.
2. The child has been created out of order in the logical tree, for the ordered compositions ('Ordered Set' or 'Sequence').
3. The child is a duplicate, which is not allowed for a composition of 'Ordered Set' or 'Unordered Set'.
- Response
- As appropriate:
Modify the message set and redeploy it to the broker.
Modify the message flow and redeploy it to the broker.
Modify the input message and resubmit it to the broker.
- BIP5372
- There was a message validation error. Element or attribute <insert_0> is not defined as a member of the message set <insert_1>. The path to the element is <insert_2>. The element is defined as a child of a complex type or group that has a content validation setting of 'Open Defined' and composition <insert_3>.
- Severity
- 20 : Error
- Explanation
- As appropriate:
Modify the message set and redeploy it to the broker. Specifically, make sure that the element is defined in the message set.
Modify the message flow and redeploy it to the broker. If the element is created in the message flow, make sure that it has the correct name and namespace.
Modify the input message and resubmit it to the broker.
- BIP5373
- Message validation error. A default value for element <insert_0> cannot be found in the dictionary.
- Severity
- 20 : Error
- Explanation
- Add a default value to the element definition in the message set and redeploy to the broker.
Alternatively, alter the message flow to ensure that the element always has a value, so a default value is not needed.
- BIP5374
- Message validation error. An element does not meet the minOccurs constraint.
element: <insert_0>
instances: <insert_1>
minOccurs: <insert_2>
parent: <insert_3>
parent index: <insert_4>
- Severity
- 20 : Error
- Explanation
- Element <insert_0> has <insert_1> instances in the logical tree, but has been defined with a minOccurs constraint of <insert_2> within its parent type/element <insert_3> of index <insert_4>.
- Response
- Trace the message tree, and compare it to the message definition used for validation.
Alter the message set, decreasing the minOccurs constraint or setting a default value for this element, then redeploy to the broker.
Alternatively increase the number of instances of the element in the message itself.
- BIP5375
- Message validation error. An element has exceeded its maxOccurs constraint.
element: <insert_0>
instances: <insert_1>
maxOccurs: <insert_2>
- Severity
- 20 : Error
- Explanation
- Element <insert_0> has <insert_1> instances in the logical tree, but has been defined with a maxOccurs constraint of <insert_2>.
- Response
- Trace the message tree, and compare it to the message definition used for validation.
Alter the message set, increasing the maxOccurs constraint, and redeploy to the broker.
Alternatively decrease the number of instances of the element in the message itself.
- BIP5376
- Message Validation failure. A Timing validation error has occurred.
- Severity
- 20 : Error
- Explanation
- An unresolved Choice or Message has being encountered while trying to completely parse the bitstream.
- Response
- Adjust the validateTiming option on the relevant node to 'immediate' and redeploy to the broker.
- BIP5377
- Message validation error. An unresolved choice within parent <insert_0> could not be resolved using defaults.
- Severity
- 20 : Error
- Explanation
- A parent element, <insert_0>, of composition 'Choice' or 'Sequence' that contains an embedded group of composition 'Choice', could not be resolved. All resolutions of the choice were deemed to be mandatory.
- Response
- Resolve the choice in the message flow. For example, refer to a specific member of the choice in a Compute node, a Java Compute node, or a Mapping node.
- BIP5378
- There was a message validation error. An element, considered complete, does not meet the Min Occurs constraint, or an element is out of sequence in the logical tree. Element <insert_0> has <insert_1> instances on the logical tree after parsing to the current element <insert_3>, but has been defined or qualified with a Min Occurs constraint of <insert_2>.
Current element: <insert_3>
Previous element: <insert_4>
Next element: <insert_5>
Parent type/element: <insert_6>
- Severity
- 20 : Error
- Explanation
- As appropriate:
Adjust the Min Occurs constraint downwards and redeploy the message set to the broker.
Increase the instances of the element in the message and resubmit it to the broker.
Make sure that the elements in the message are in the correct order and resubmit it to the broker.
- BIP5379
- Invalid option 'FolderBitStream'
- Severity
- 20 : Error
- Explanation
- An ESQL operation included the use of 'FolderBitStream'. The MRM Domain does not support this option.
- Response
- Check your ESQL, and ensure that you do not use the option 'FolderBitStream' when working with messages in the MRM Domain.
- BIP5380
- Internal error while matching element <insert_0> with value <insert_1> against pattern <insert_2>.
- Severity
- 20 : Error
- Explanation
- An error was encountered while validating the element against a pattern.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5381
- Resource Manager: An ambiguous dictionary was specified for message set <insert_2>, in function <insert_1>.
- Severity
- 20 : Error
- Explanation
- The runtime dictionary resource for message set <insert_2> has been requested by the broker in the function <insert_1>, however the resource cannot be obtained as the message set name is ambiguous. This means that multiple resources with this message set name have been deployed and thus the message set name specification cannot be reliably resolved.
- Response
- The broker was requested to load a dictionary using an ambiguous message set name. The most likely reason for this error is that there are multiple levels of a message set deployed with the same message set name. In this situation, the message set must be identified using the message set identifier (rather than the name). Alternatively, ensure that there are not multiple levels of the message set deployed to the broker.
- BIP5382
- Resource Manager: A duplicate message set name <insert_2> was specified.
- Severity
- 20 : Error
- Explanation
- A message set deployment request for message set <insert_2> has been received by the message broker. However, the broker already has a message set registered with the same 'Message Set Name' but a different 'Identifier'. This would result in an ambiguous resource being registered and thus the request has been rejected.
- Response
- The broker was requested to register a runtime message set resource (dictionary) using an ambiguous 'Message Set Name'. The most likely reason for this error is that there is already a message set deployed with this name, but with a different identifier. You should either remove the existing message set deployment or change the name of the message set currently being deployed.
- BIP5383
- Message validation failure. The value for field <insert_0> is not valid.
The decimal value <insert_1> contains more than <insert_2> total digits.
- Severity
- 20 : Error
- Explanation
- The value for the field in the data message contains more digits than was specified by the total digits value for the field.
- Response
- Modify the message set or message flow and redeploy to the broker, or modify the input message and resubmit to the broker.
See the following messages for more details.
- BIP5384
- The Message Type Path <insert_0> does not reference an embedded message.
- Severity
- 20 : Error
- Explanation
- When using the ASBITSTREAM or CREATE ... FIELD ... PARSE functions in FolderBitStream mode, the root of the bitstream or tree must be an embedded message. Thus, the Message Type Path must reference a message defined within the message model.
- Response
- Modify the message path passed as a parameter to the ASBITSTREAM or CREATE ... FIELD .. PARSE function so that it references a message within the message set.
- BIP5386
- Message validation error. The xsi:type attribute value for element <insert_2> in message set <insert_3> is invalid.
Type <insert_1> cannot be overridden with type <insert_0>.
- Severity
- 20 : Error
- Explanation
- Element <insert_2> has an xsi:type attribute with value <insert_0>, but type <insert_0> is not derived from the declared type <insert_1> of element <insert_2>.
- Response
- Modify the message so that the xsi:type attribute identifies a valid type, or modify message set <insert_3> so that global type <insert_0> is derived from type <insert_1>.
- BIP5387
- Message validation error. The xsi:type attribute value for element <insert_2> in message set <insert_3> is invalid.
Type <insert_1> cannot be overridden with type <insert_0>.
- Severity
- 20 : Error
- Explanation
- Element <insert_2> has an xsi:type attribute with value <insert_0>, but type <insert_0> conflicts with the 'block' attribute on type <insert_1>.
- Response
- Modify the message so that the value of the xsi:type attribute is valid.
Modify message set <insert_3> so that type <insert_0> is a valid substitution for type <insert_1>.
- BIP5388
- Message validation error. The xsi:type attribute value is invalid.
Element type <insert_1> cannot be overridden with type <insert_0>, for message set <insert_2>.
- Severity
- 20 : Error
- Explanation
- Element <insert_1> has an xsi:type attribute with value <insert_0>, but type <insert_0> conflicts with the 'block' attribute on element <insert_1>.
- Response
- Modify the message so that the value of the xsi:type attribute is valid.
Modify message set <insert_2> so that type <insert_0> is a valid substitution for the type of element <insert_1>.
- BIP5389
- Message validation failure. The element has an invalid type.
The type of element <insert_1> is <insert_0>, which is an abstract type in message set <insert_2>
- Severity
- 20 : Error
- Explanation
- Element <insert_1> is based on complex type <insert_0>, which is an abstract type. Abstract types must be overridden using xsi:type.
- Response
- Modify the message, adding an xsi:type attribute to element <insert_1>, or modify message set <insert_2> so that type <insert_0> is not abstract.
- BIP5390
- An element of type xsd:list has been deemed complete with the number of ItemType instances less than its minLength constraint.
list element: <insert_0>
length: <insert_1>
minLength: <insert_2>
- Severity
- 20 : Error
- Explanation
- Element <insert_0> has <insert_1> ItemType instances in the logical tree, but has been defined with a minLength constraint of <insert_2>.
- Response
- Alter the message set, decreasing the minLength constraint and redeploy to the broker, or increase the number of ItemType instances in the message.
- BIP5391
- An element of type xsd:list has been deemed complete with the number of ItemType instances greater than its maxLength constraint.
list element: <insert_0>
length: <insert_1>
maxLength: <insert_2>
- Severity
- 20 : Error
- Explanation
- Element <insert_0> has <insert_1> ItemType instances on the logical tree, but has been defined with a maxLength constraint of <insert_2>.
- Response
- Alter the message set, increasing the maxLength constraint and redeploy to the broker, or decrease the number of ItemType instances in the message.
- BIP5392
- Message validation error. The wildcard element maxOccurs constraint has been exceeded.
Element <insert_0> exceeds the maxOccurs constraint of <insert_1>.
- Severity
- 20 : Error
- Explanation
- Element <insert_0> has been matched with a wildcard element but exceeds the maxOccurs constraint <insert_1> for this wildcard element. Only one element can be matched with each occurrence of a wildcard element.
- Response
- Alter the message set, increasing the maxOccurs constraint of the wildcard element, and redeploy to the broker. Alternatively remove the instance of the element in the incoming message (when parsing) or from the logical tree (when writing).
- BIP5393
- One or more Message Validation failures have occurred.
- Severity
- 20 : Error
- Explanation
- Message Validation failure. A Validation Failure Action of Exception List has been selected and one or more Message Validation failures have occurred during a parse or write operation.
- Response
- Review the following list of Message Validation failures for an indication to the cause of the failures.
- BIP5394
- Resource Manager: A duplicate message set alias was specified on message set <insert_2>.
- Severity
- 20 : Error
- Explanation
- A message set deployment request for message set <insert_2> has been received by the message broker. However, the broker already has a message set registered with the same 'Message Set Alias' but a different 'Identifier'. This would result in an ambiguous resource being registered and thus the request has been rejected.
- Response
- The broker was requested to register a runtime message set resource (dictionary) using an ambiguous 'Message Set Alias'. The most likely reason for this error is that there is already a message set deployed with this 'Message Set Alias' (but a different identifier). You should either remove the existing message set deployment or modify the 'Message Set Alias' of the message set currently being deployed.
- BIP5395
- An xsi:type attribute value on element <insert_2> is invalid.
<insert_0> is not a valid MemberType of union type <insert_1>.
- Severity
- 20 : Error
- Explanation
- Element <insert_2> is based on a union type <insert_1> and has an xsi:type attribute with value <insert_0>. This should explicitly resolve the union <insert_1> to one of its modeled memberTypes. The xsi:type attribute value <insert_0> does not correspond to a valid memberType of union <insert_1>.
- Response
- Modify the message so that the xsi:type attribute identifies a valid memberType of union <insert_1>, or check the message model, ensuring that union type <insert_1> contains the correct list of simple types.
- BIP5396
- An unresolved union error occurred for element or attribute <insert_0>.
The data type <insert_2> is not a valid data type for union type <insert_1>.
- Severity
- 20 : Error
- Explanation
- The element or attribute <insert_0> is based on union type <insert_1>. The data type <insert_2> does not correspond to any of the valid data types of union <insert_1>.
- Response
- Check that the message contains a valid value for element or attribute <insert_0>.
Check that union type <insert_1> contains the correct list of simple types.
Consider using an xsi:type attribute to resolve the union explicitly.
Consider changing the type of the element in the tree to correspond with one of the union datatypes.
- BIP5397
- A Timing error has occurred while trying to parse a message into a shared tree
- Severity
- 20 : Error
- Explanation
- An unresolved Choice or Message has being encountered while trying to completely parse the bitstream.
- Response
- Modify the ESQL so that the tree is not shared and redeploy to the broker.
- BIP5398
- Resource Manager: An invalid DateTime format or value was specified in message set <insert_2>.
- Severity
- 20 : Error
- Explanation
- A request to register the runtime dictionary resource for message set <insert_2> has been received by the broker. However, this message set contains an invalid DateTime format or specifies a DateTime which is not valid for the given format. Therefore, the request has been rejected.
- Response
- The broker has received a deployment request containing an invalid DateTime format, an invalid value, or both, for the message set <insert_2>.
Ensure that all DateTime formats are specified correctly in this message set and that all DateTime values are valid for their associated format string.
After doing this, retry the deployment operation.
- BIP5399
- A message identification mismatch occurred in a multipart message.
Expected embedded message: <insert_2>
Actual embedded message: <insert_1>
Message set: <insert_0>
- Severity
- 20 : Error
- Explanation
- The broker has identified an embedded message in the bit stream of the multipart message <insert_1>, defined within message set <insert_0>. However, this contradicts the expected embedded message type <insert_2>, which has been identified by way of a previously parsed element or attribute that has the 'InterpretValueAs' property set to 'MessageIdentity'.
- Response
- The broker has encountered a self describing embedded message (typically by way of an XML tag name) in the bit stream. However, this message does not correspond with the expected value as identified by a previously parsed 'Message Identity' field.
Ensure that:
1) The 'InterpretValueAs = MessageIdentity' property is correctly specified on an appropriate element/attribute in the message model.
2) The embedded message tag name <insert_1> in the input bit stream is as expected.
- BIP5401
- XML Worker: An internal error occurred. Diagnostic information: <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred during the operation of the XML Worker.
- Response
- Please contact your IBM support center.
- BIP5402
- Unable to write out unparsed element.
- Severity
- 20 : Error
- Explanation
- The XML worker cannot write element because it is an unparsed buffer.
- Response
- Please ensure that all elements in the bitstream can be completely parsed.
- BIP5403
- Error writing out self defining element with no name.
- Severity
- 20 : Error
- Explanation
- A self defining element with no name was encountered by the XML Worker. The XML worker needs a name to render the element in XML.
- Response
- Ensure that all self defining elements have a name defined.
- BIP5404
- XML data conversion error.
An error occurred while characters were being converted to logical type <insert_2> for element <insert_1> in message <insert_0>.
- Severity
- 20 : Error
- Explanation
- Please ensure that the element specified contains valid data for the logical type specified (<insert_2>).
- BIP5406
- XML parsing error: Unexpected data was found before the start of the message content.
Unexpected data: <insert_0>
Root tag name: <insert_1>
- Severity
- 20 : Error
- Explanation
- Ensure that the incoming message does not contain data between the root tag name (<insert_1>) and the message tag.
- BIP5407
- XML parsing error: Element <insert_0>, with a namespace <insert_1>, was found when namespaces are not enabled for the message set.
- Severity
- 20 : Error
- Explanation
- The element with XML name <insert_0> is in namespace <insert_1>. However namespaces have not been enabled for the message set.
- Response
- If you intend to use namespaces ensure that namespaces have been enabled for the message set.
If you do not intend to use namespaces ensure that no element or attribute is in a namespace.
- BIP5408
- XML parsing error: Attribute <insert_0>, with a namespace <insert_1>, was found when namespaces are not enabled for the message set.
- Severity
- 20 : Error
- Explanation
- The attribute with XML name <insert_0> is in namespace <insert_1>. However namespaces have not been enabled for the message set.
- Response
- If you intend to use namespaces ensure that namespaces have been enabled for the message set.
If you do not intend to use namespaces ensure that no element or attribute is in a namespace.
- BIP5409
- XML Worker: Wire Format 'XML' specified.
- Severity
- 20 : Error
- Explanation
- Default MRM XML settings are being used because wire format identifier 'XML' was specified and not found.
- Response
- This can be due to an incorrect setting of the wire format identifier in a message.
- BIP5410
- XML parsing error: An unresolved union error occurred for element or attribute <insert_0>, of type <insert_1>.
- Severity
- 20 : Error
- Explanation
- The element or attribute <insert_0> is based on union type <insert_1>. The value of <insert_0> could not be cast to any member of the union.
- Response
- Check that the message contains a valid value for element or attribute <insert_0>.
Check that union type <insert_1> contains the correct list of simple types.
Consider using an xsi:type attribute to resolve the union explicitly.
- BIP5411
- XML parsing error: A list of lists is not allowed.
Element or attribute: <insert_0>
List type: <insert_1>
Item type: <insert_2>
- Severity
- 20 : Error
- Explanation
- Element or attribute <insert_0> is based on list type <insert_1>, which has an itemType based on list type <insert_2>. A list cannot be derived at any level from another list type.
- Response
- Check that list type <insert_1> contains the correct simple type for its itemType.
Check that if list type <insert_1> has an itemType of 'union', the union specified does not have a memberType of 'list' at any level.
- BIP5421
- Tagged/Delimited String Format (TDS) parsing error
Current message : <insert_0>
Path to current element : <insert_1>
Offset from start of message : <insert_2>
- Severity
- 30 : Severe error
- Explanation
- See following errors for more details.
- BIP5422
- No Length associated with fixed length data
- Severity
- 20 : Error
- Explanation
- The TDS parser could not extract data from the bitstream for Fixed Length element <insert_0> as no Length or LengthRef was defined in the dictionary.
- Response
- Define a Length or LengthRef property for Element <insert_0>.
- BIP5423
- Incorrect Logical Type for the first child of a complex type or group with TDS Data Element Separation of Fixed Length AL3.
- Severity
- 20 : Error
- Explanation
- The first child of a Fixed Length AL3 complex type or group should be an INTEGER defining the complete length of the structure.
- Response
- Change the logical type of the first child of each Fixed Length AL3 complex type or group in the message definition to INTEGER.
- BIP5424
- No Message Id received in TDS Parser Initialization
- Severity
- 30 : Severe error
- Explanation
- The TDS worker is not receiving a proper Message Id parameter during initialization.
- Response
- Ensure that the message identifier used in your message matches the message as defined in the Message Brokers Toolkit.
- BIP5425
- The bitstream of a TDS message is longer than expected.
- Severity
- 20 : Error
- Explanation
- The TDS parser could not complete parsing because the bitstream contains more data than expected. This could be caused by either an incorrect message definition or by an incorrect message.
- Response
- Make sure that the incoming message is a correct TDS message.
- BIP5426
- The bitstream of a TDS message contains less data than expected.
- Severity
- 20 : Error
- Explanation
- The TDS parser could not complete parsing because the bitstream contains less data than expected. This could be caused by either an incorrect value for the Length property in the message definition, or by an inconsistent value inside a LengthRef field.
- Response
- Make sure that the incoming message is a consistent message under the TDS message definition.
- BIP5427
- The TDS parser could find no embedded message with the required TDS message key <insert_0>.
- Severity
- 20 : Error
- Explanation
- An element that has the 'Interpret Element Value' property set to 'Message Key' has previously been parsed successfully.
However, an attempt to locate an embedded message with the appropriate TDS message key <insert_0> has failed.
- Response
- Ensure that a message with the TDS message key <insert_0> has been correctly defined in the message model, and has been deployed successfully to the broker.
Ensure that the 'Interpret Element Value = Message Key' property has been specified on the correct element.
Ensure that the input message contains a valid and correctly located message key.
- BIP5428
- The bitstream does not contain the required Message Key, Message Identity or Message Path for a nested message.
- Severity
- 20 : Error
- Explanation
- The TDS parser could not find the Message Key or Message Identity for a nested message in the bitstream. It also could not identify the nested message using a Message Path.
- Response
- Make sure that the incoming upper level message is a consistent message under the TDS message definition or define a Message Path to identify the nested message.
- BIP5429
- The TDS parser could not parse an expected boolean value because the bitstream contains an incorrect encoding of a TDS boolean value. The expected boolean representations are:
True: <insert_0>
False: <insert_1>
Null: <insert_2>
The byte offset is <insert_3>.
- Severity
- 20 : Error
- Explanation
- Make sure that the incoming message is consistent with the defined TDS model.
- BIP5430
- No tag length while extracting Fixed Length Tag in TDS message.
- Severity
- 20 : Error
- Explanation
- The TDS message definition does not provide a required Tag Length property for an element, either at project level or at complex type/group level.
- Response
- Make sure that in the TDS message definition, all required Tag Length properties are set.
- BIP5431
- Parser not Initialized.
- Severity
- 30 : Severe error
- Explanation
- The Parser has not been initialized. This is an internal error.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5432
- Bad TDS dictionary Index, or invalid TDS dictionary.
- Severity
- 30 : Severe error
- Explanation
- The TDS message definition which has been deployed is incorrect. This is an internal error
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5434
- TDS Parser or Writer internal error
- Severity
- 30 : Severe error
- Explanation
- An unexpected internal error occurred during parsing or writing of a TDS message
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5435
- Memory allocation error
- Severity
- 30 : Severe error
- Explanation
- The system ran out of memory during parsing or writing a TDS message.
- Response
- Examine memory usage and increase memory available to the broker.
- BIP5436
- Data Length Error
Element name: <insert_0>
Element type: <insert_1>
Expected data length: <insert_2>
Actual data length: <insert_3>
Data: <insert_4>
- Severity
- 30 : Severe error
- Explanation
- While a TDS message was being written, it was found that the data length was inconsistent with the element definition.
- Response
- If the element is of binary data type, make sure that the length is the same as the expected length, as defined in the message definition.
If the element is of string data type, make sure the length is not greater than the expected length.
- BIP5437
- The group indicator was missing in the bit stream.
Type or group: <insert_0>
Group indicator expected: <insert_1>
At offset: <insert_2>
- Severity
- 20 : Error
- Explanation
- The MRM TDS parser could not parse the data in the bit stream for complex type or group <insert_0>. A group indicator <insert_1> was not present in the bit stream at offset <insert_2>.
- Response
- The message model definition does not match the bit stream.
Check that your model definition is correct and if so, update your bit stream data accordingly.
Collect debug-level user trace for more information on how the model is being matched.
- BIP5438
- The group terminator was missing in the bit stream.
- Severity
- 20 : Error
- Explanation
- The TDS parser could not parse the data in the bit stream for Fixed Length complex type or group <insert_0>. No group terminator <insert_1> was present in the bit stream at offset <insert_2>.
- Response
- The message model definition does not match the bit stream.
Check that your model definition is correct and if so, update your bitstream data accordingly.
Collect debug-level user trace for more information on how the model is being matched.
- BIP5439
- No Element defined for Tag <insert_0>.
- Severity
- 20 : Error
- Explanation
- The TDS parser has detected the Tag <insert_0> in the input message bitstream for which there is no element defined. An element of Fixed Length is required within the current structure (<insert_1>).
- Response
- Check the value parsed for previous elements in the bitstream, as an error in their length may have resulted in the misinterpretation of the tag.
- BIP5440
- TDS data conversion error.
- Severity
- 20 : Error
- Explanation
- Error converting characters at position <insert_0> to logical type <insert_3> in message <insert_1>, current element <insert_2>.
- Response
- Please ensure that the element specified contains valid data for the logical type specified (<insert_3>).
- BIP5441
- The TDS Parser has encountered a Tag value of length 0 within the bitstream.
- Severity
- 20 : Error
- Explanation
- The TDS parser is expecting a Tag value delimited by the Tag Data Separator (<insert_0>) at position <insert_1> in the bitstream. The Tag value is not present (length 0).
- Response
- The message model definition does not match the bitstream. Check that your model definition is correct and if so, update your bitstream data accordingly.
- BIP5442
- Error interpreting the value of element.
- Severity
- 20 : Error
- Explanation
- The value (<insert_0>) at offset (<insert_1>) for element (<insert_2>) is not a valid "EDIFACT Service String". The "EDIFACT Service String" should be of length 6.
- Response
- The message model definition does not match the bitstream. Check that your model definition is correct and if so, update your bitstream data accordingly.
- BIP5443
- Error interpreting the value of element.
- Severity
- 20 : Error
- Explanation
- The value (<insert_0>) at offset (<insert_1>) for element (<insert_2>) is not a valid "X12 Service String". The "X12 Service String" should be of length 103.
- Response
- The message model definition does not match the bitstream. Check that your model definition is correct and if so, update your bitstream data accordingly.
- BIP5444
- Error interpreting the value of element.
- Severity
- 20 : Error
- Explanation
- The value (<insert_0>) at offset (<insert_1>) for element (<insert_2>) is not a valid "EDIFACT Syntax Level Identifier". The "EDIFACT Syntax Level Identifier" should be of length 4.
- Response
- The message model definition does not match the bitstream. Check that your model definition is correct and if so, update your bitstream data accordingly.
- BIP5445
- Tagged/Delimited String Format (TDS) parsing error.
- Severity
- 20 : Error
- Explanation
- The TDS parser has encountered an error. See following messages for more details.
- BIP5446
- The data length associated with element <insert_0> was invalid.
Length <insert_1> calculated from offset <insert_2> is invalid.
- Severity
- 20 : Error
- Explanation
- The MRM TDS parser could not extract data from the bit stream for element <insert_0>, because an invalid length (<insert_1>) was calculated at offset (<insert_2>).
During the parsing of a complex type or group with Data Element Separation of 'Tagged Encoded Length', this error occurred because the value resulting from the data length in the bit stream, combined with the value of the 'Extra Chars In Encoded Length' property, resulted in a negative number.
During the parsing of a complex type or group with Data Element Separation of 'Fixed Length', this error occurred because the value of the element referenced by the 'Length Value Of' is a negative number.
- Response
- Check the value parsed for previous elements in the bit stream, as an error in their length might have resulted in the misinterpretation of the input message bit stream, resulting in the wrong value being used as a length value.
- BIP5447
- Tagged/Delimited String Format (TDS) writing error while writing message <insert_0>
- Severity
- 30 : Severe error
- Explanation
- See following errors for more details.
- BIP5448
- Invalid Data Length associated with Element <insert_0>.
- Severity
- 20 : Error
- Explanation
- The element (<insert_0>) does not contain a fixed length. TDS does not support Length References within a complex type or group with Data Element Separation 'Fixed Length' and composition 'Choice'.
- Response
- Remove the Length reference value and replace it with a length value.
- BIP5449
- Data Element Separation method is invalid.
- Severity
- 20 : Error
- Explanation
- TDS Data Element Separation of 'Undefined' is only valid for composition 'Message'.
- Response
- Correct the Data Element Separation value.
- BIP5450
- Data pattern <insert_2> associated with element <insert_0> of logical type <insert_1> is invalid.
- Severity
- 20 : Error
- Explanation
- Check that your model definition is correct. In particular ensure that any hexadecimal values in the pattern are supported. Consider changing the data pattern for element <insert_0>.
- BIP5451
- An error has occurred at offset <insert_3> while the bit stream was being parsed. Data for element <insert_0> of logical type <insert_1> is longer than expected.
- Severity
- 20 : Error
- Explanation
- The MRM TDS parser could not complete parsing because the bit stream contains more data than expected for element <insert_0>.
The data length for element <insert_0> is defined in the model as <insert_2>. The number of data bytes extracted from the bit stream for element <insert_0> is <insert_4>. This could be caused by either an incorrect message definition or by an incorrect message.
- Response
- Check that your model definition is correct, and if so make sure that the incoming message is correct with respect to the message definition.
- BIP5452
- Mandatory Element <insert_0> has no value or default value set.
- Severity
- 20 : Error
- Explanation
- Mandatory element (<insert_0>) has not been set and has no default value. A mandatory fixed length element must have a value set or a default value specified.
- Response
- Set a value or specify a default value for this element.
- BIP5453
- Incoming message is self defining.
- Severity
- 20 : Error
- Explanation
- The message requiring writing is self-defining. TDS cannot write self-defining messages.
- Response
- Check the message defining and flow.
- BIP5454
- Choice Element has more than one option defined.
- Severity
- 20 : Error
- Explanation
- An element with a complex type that has composition 'Choice' can only have one option defined in the message.
- Response
- Correct the defined message to accept the outgoing bitstream.
- BIP5455
- Occurrence <insert_0> of ACORD AL3 element <insert_1> at offset <insert_2> is invalid in the bit stream. The full path to the element is <insert_3>.
- Severity
- 20 : Error
- Explanation
- An earlier occurrence of repeating element <insert_1> has been marked as not present.
In an ACORD AL3 message, when an occurrence of a repeating element has been marked as not present then no subsequent occurrences of that repeating element can be present.
A '?' in the leftmost position of an element's data is used to signify that the element is not present.
- Response
- Check that your model definition is correct and that the 'max occurs' value for element <insert_3> is correct. If the model is correct, make sure that the incoming message is a valid ACORD AL3 TDS message.
- BIP5456
- The TDS physical format does not support list types. Element <insert_0> is based on a list type.
- Severity
- 20 : Error
- Explanation
- Update the message model for element <insert_0> to remove the list type. Consider using a repeating field based on a non-list type.
- BIP5457
- The message type contains more than one message.
- Severity
- 20 : Error
- Explanation
- Only one message is allowed inside a type of composition message.
- Response
- Check your model, and add repeats to the message type if required.
- BIP5458
- The TDS physical format does not support an unbounded number of occurrences for element <insert_0>, because it is contained in a fixed length choice.
- Severity
- 20 : Error
- Explanation
- A choice contains element <insert_0>, which is defined with a 'max occurs' of -1 (unbounded). This option is not supported within a fixed length environment for a choice, because it must be possible to calculate the length of each member of the choice.
- Response
- Modify the message model to ensure that no elements contained in a fixed length choice repeat an unbounded number of times. Check the repeats of element <insert_0>.
- BIP5459
- The TDS physical format does not support union types. Element <insert_0> attempts to use a union type.
- Severity
- 20 : Error
- Explanation
- Alter the message model to remove the union type, then redeploy.
- BIP5461
- An MRM CWF physical format output error has occurred. A null value cannot be output for element <insert_0>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to output element <insert_0>, which has a null value, but the definition of this element does not allow null values to be used.
- Response
- Check the message set null representation properties for this element. For example, ensure that the 'nillable' logical property is correctly set.
If using a Null Encoding of 'NullLiteralFill' ensure that the physical type is not 'Null Terminated' or 'Length Encoded String'.
If using ESQL, check your code for statements like 'VALUE = NULL' See previous messages for details of the message set and message.
- BIP5462
- An MRM Custom Wire Format physical format parsing error has occurred.
The error occurred during the parsing of an element or group that repeats to the end of the bit stream.
Current message: <insert_1>
Current element or group: <insert_2>
Path from message root: <insert_3>
Element or group occurrence: <insert_4>
- Severity
- 20 : Error
- Explanation
- Instances of the final element or group in a CWF message will be parsed until the end of the bit stream when the maxOccurs of the final element or group is '-1'.
Check that the message model is correct. Also examine the instance message being processed, to make sure it conforms to the model.
See following errors for more details.
- BIP5463
- An MRM Custom Wire Format physical format output error has occurred.
The error occurred during the output of an element that is missing from the message tree.
The policy for the output of missing elements for the current message set is: 'Use Null Value'.
However, no null value has been specified for this element.
Current message: <insert_1>
Current element: <insert_2>
- Severity
- 20 : Error
- Explanation
- One of the following actions may resolve the problem:
Check that the correct 'Policy for Missing Elements' has been specified for your message set.
Ensure that an appropriate null value has been specified for the element's 'Encoding Null Value' property.
Change the message flow so that this element is present in the message tree before outputting the message.
- BIP5464
- An MRM Custom Wire Format physical format field reference error has occurred.
The error occurred during the parsing or output of an element or attribute (field). This field has either a length reference or repeat reference defined. However, the value of the target of this field reference could not be determined.
Current message: <insert_1>
Current field: <insert_2>
Target of field reference: <insert_3>
- Severity
- 20 : Error
- Explanation
- One of the following actions may resolve the problem:
Check that the length reference or repeat reference information has been correctly defined in the message model.
On parsing, ensure that the target of the field reference has been correctly parsed and is present in the input bit stream.
On output, ensure that the target of the field reference is present in the message tree.
- BIP5465
- An MRM Custom Wire Format physical format field reference error has occurred.
The error occurred during the parsing or output of an element or attribute (field). This field has either a length reference or repeat reference defined. However, the value of the target of this field reference is invalid. The value of the target of the field reference must be a non-negative number.
Current message: <insert_1>
Current field: <insert_2>
Target of field Reference: <insert_3>
Value of target of field reference: <insert_4>
- Severity
- 20 : Error
- Explanation
- One of the following actions may resolve the problem:
Check that the length reference or repeat reference information has been correctly defined in the message model.
On parsing, ensure that the target of the field reference has been correctly parsed and that its value is not negative.
On output, ensure that the target of the field reference is present in the message tree and that its value is not negative.
- BIP5471
- PDF Worker error. General Error.
- Severity
- 20 : Error
- Explanation
- An Error has occurred while performing a general operation on the PDF bitstream.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5472
- PDF Worker error. Parser not initialized.
- Severity
- 20 : Error
- Explanation
- An attempt was made to parse a bitstream without out first initializing the PDF Parser.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5473
- PDF Worker error. Writer not initialized.
- Severity
- 20 : Error
- Explanation
- An attempt was made to write a bitstream without out first initializing the PDF Writer.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5474
- PDF Worker error. FI Handler not assigned.
- Severity
- 20 : Error
- Explanation
- An attempt was made to parse a bitstream without out assigning an FI handler to the worker.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5475
- PDF Worker error. FI Message tree not assigned.
- Severity
- 20 : Error
- Explanation
- An attempt was made to write a bitstream without out assigning an FI Message tree to the worker.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5476
- PDF Worker error: PDF Bitstream has not been initialized: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a PDF Bitstream is not initialized within the PDF worker.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5477
- PDF Worker error: PDF invalid operation: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when an invalid operation is performed within the PDF worker.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5478
- Message Translation Interface error. Null pointer: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal Error. An unexpected NULL pointer has been encountered within the PDF Worker.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5479
- PDF Worker error: PDF read error: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a PDF worker Read operation fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5480
- PDF Worker error: PDF write error: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when a PDF worker Write operation fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5481
- PDF Worker error: Parsing Errors have occurred: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Errors have occurred during parsing.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5482
- PDF Worker error: A problem has occurred when using ICU: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred when trying to create/use an ICU converter.
- Response
- Check environment setup. Record the full details provided with this message and contact your IBM support center.
- BIP5483
- PDF Worker error. Insufficient memory: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- Internal error. This error is returned by any PDF Worker function that tries to allocate memory and fails.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5484
- A PDF worker error has occurred, in the form of a PDF overflow: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This error is returned when the PDF worker tries to perform an operation beyond the end of the bit stream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5485
- PDF Worker error. PDF definition not found: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is returned when expected items are not found in the bitstream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5486
- PDF Worker error. Invalid PDF Bitstream: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- The PDF Worker was asked to parse an invalid or blank bitstream.
- Response
- Record the full details provided with this message and contact your IBM support center.
- BIP5487
- PDF Worker error. Unknown Error: function name <insert_1>; error code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An Unexpected Internal Error has occurred in the PDF Worker.
- Response
- Record the full details of the activity that was in progress and contact your IBM support center.
- BIP5491
- An xsi:type attribute value on element <insert_0> could not be resolved in message set <insert_1>. Type <insert_2> will be used.
The xsi:type attribute on element <insert_0> did not resolve to a global type definition in message set <insert_1>.
Element <insert_0> will revert to its defined type <insert_2>.
- Severity
- 10 : Warning
- Explanation
- Check that <insert_1> is the expected message set. If the message set is correct perform one of the following actions:
Modify the message so that the xsi:type attribute identifies a valid type
Add the global type definition to message set <insert_1>.
- BIP5492
- Message validation error: A wildcard element does not meet its minOccurs constraint. It has <insert_0> instances on the logical tree, but has been defined with a minOccurs constraint of <insert_1>.
- Severity
- 20 : Error
- Explanation
- Alter the message model, decreasing the wildcard element minOccurs constraint, then redeploy the message set.
Alternatively increase the instances of the wildcard element in the bit stream (when parsing) or in the logical tree (when writing).
Only one element can be matched with each occurrence of a wildcard element.
- BIP5493
- Message, element or attribute <insert_0> is self-defining within parent <insert_1>.
The message, element or attribute <insert_0> did not match with any corresponding
artifact in the message model hence it is considered to be self-defining.
- Severity
- 10 : Warning
- Explanation
- If it is not intended that this message, element or attribute be self-defining,
check that the message set is referenced in the message properties, or
modify the message model to correspond to the instance message, or
modify the instance message to correspond to the message model.
- BIP5494
- The logical tree is now being matched to the message model.
- Severity
- 0 : Information
- BIP5501
- Assertion failed: <insert_0> File: <insert_1>. Line <insert_2>.
- Severity
- 20 : Error
- Explanation
- A debug assertion failed.
- Response
- Please contact your IBM support center.
- BIP5502
- A Common Parser Interface internal error occurred: Diagnostic information: <insert_0>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred while reading from or writing to the bitstream.
- Response
- If the problem persists, please contact your IBM support center.
- BIP5503
- Read of a text element failed. Message is too short.
Message data : <insert_0>
Text element offset : <insert_1>
Expected length of element : <insert_2>
- Severity
- 20 : Error
- Explanation
- The reading of a text element of a message failed because the message was too short to contain the expected length of text.
Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
- BIP5504
- Read of text element failed. Null terminator not found.
Message data : <insert_0>
Search for null terminator started at offset <insert_1>.
- Severity
- 20 : Error
- Explanation
- The reading of a text element of a message failed because the expected null terminator was not found.
Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
- BIP5505
- A data conversion failed because the data was invalid.
Type of data being read: <insert_0>
Data: <insert_1>
- Severity
- 20 : Error
- Explanation
- Data conversion when reading or writing a message failed because the input data was invalid for the output data type.
- Response
- Review other error messages for details of the message set and message type.
Check that the message model is correct and that the processed message is of the expected format and type. Specifically, the following actions might help to resolve the problem:
1. Check that the bit stream is correctly aligned with the model. For example, check the lengths of input elements against the model.
2. Check that the input message has the correct Encoding and Coded Character Set ID applied to the message body.
3. Check that the input message has an appropriate WebSphere MQ format applied to the message body.
4. If the error occured for a numeric field then check that the input data is compatible with the physical format settings defined in the model.
5. If the input message is incompatible with the MRM model definitions then check the message at source.
- BIP5506
- Data conversion failed: input data out of bounds.
Type of data being read : <insert_0>
Target data type : <insert_1>
Data : <insert_2>
- Severity
- 20 : Error
- Explanation
- A data conversion during reading or writing of a message failed because the input data was out of bounds for the output data type.
Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
- BIP5507
- Data conversion failed: input data too long.
Input type : <insert_0>
Output type : <insert_1>
Maximum expected length : <insert_2>
Data value : <insert_3>
- Severity
- 20 : Error
- Explanation
- A data conversion during reading or writing of a message failed because the input data was too long for the output data type.
Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
- BIP5508
- The timezone specified for the message set is invalid.
Specified timezone : <insert_0>
- Severity
- 20 : Error
- Explanation
- Check that the timezone value specified for the message set is correct.
If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5509
- The parsing of a DateTime string failed.
Format string used : <insert_0>
Message data : <insert_1>
Start offset of DateTime element : <insert_2>
- Severity
- 20 : Error
- Explanation
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that format specified for the DateTime element is correct.
Check that the processed message is of the expected format and type.
If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5510
- Conversion of DateTime seconds or milliseconds failed.
Error code : <insert_0>
Milliseconds : <insert_1>
Epoch : <insert_2>
- Severity
- 20 : Error
- Explanation
- The converter failed to convert seconds or milliseconds received as a DateTime element in a message into a DateTime value.
Check that the message model is correct. Review previous messages for details of the message set and message type.
Check the validity of the epoch specified for the DateTime element.
Check that the processed message is of the expected format and type.
If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5511
- The conversion of a binary dateTime element to a valid dateTime value failed, with internal error code <insert_0>.
Format string: <insert_3>
Data: <insert_1>
Offset from start of element: <insert_2>
- Severity
- 20 : Error
- Explanation
- The parser failed to read a binary dateTime element from the bit stream and convert it to a dateTime value.
Internal error code <insert_0> was returned.
- Response
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
Check that the specified format string is correct.
Check that the processed message has the expected physical format and message type identifier.
- BIP5512
- The formatting of a DateTime string failed.
DateTime value : <insert_1>
Format string : <insert_2>
Format string offset : <insert_3>
- Severity
- 20 : Error
- Explanation
- The formatting of a string DateTime element to be written to a message failed.
The internal error code was <insert_0>
- Response
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
Check that the message flow is setting this element to a valid value.
Check that the format specified for the element is valid.
If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5513
- Conversion to DateTime seconds or milliseconds failed.
DateTime value : <insert_1>
- Severity
- 20 : Error
- Explanation
- The converter failed to convert a DateTime value into seconds or milliseconds for the output message.
Internal error code : <insert_0>
- Response
- Check that the message model is correct. Review previous messages for details of the message set, message type and element.
Check that the processed message is of the expected format and type.
Check that the message flow has set this element to a valid value.
- BIP5514
- Write of a binary DateTime value failed.
DateTime value : <insert_1>
Format string : <insert_2>
Format string offset : <insert_3>
- Severity
- 20 : Error
- Explanation
- The converter failed to convert a DateTime value into binary format for the output message.
Internal error code : <insert_0>
- Response
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
Check that the message flow is setting this element to a valid value.
Check that the format string specified for the element is valid.
- BIP5515
- The century window (<insert_0>) specified for the message set is invalid.
- Severity
- 20 : Error
- Explanation
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
Check that the century window value specified for the message set is correct.
- BIP5516
- The epoch specified for a DateTime element is invalid. Epoch value : <insert_0>
- Severity
- 20 : Error
- Explanation
- The epoch is used with DateTime when the DateTime value has a physical type of Seconds or Milliseconds, and signifies
the moment from which the seconds or milliseconds are counted. The epoch should be specified in the 'DateTime Format' field
of the CWF tab in the Message Brokers Toolkit, as a DateTime string with the format 'yyyy-MM-dd'T'HH:mm ZZZ'.
The default value for the epoch is '1970-01-01T00:00 +00:00'.
- Response
- Check that the message model is correct. Review previous messages for details of the message set and message type.
Check that the processed message is of the expected format and type.
Check that the epoch value specified for the element is correct.
- BIP5518
- Dictionary load error.
- Severity
- 20 : Error
- Explanation
- An unknown error occurred while reading in the dictionary.
- Response
- Please contact your IBM support center.
- BIP5519
- An attempt has been made to deploy a Message Set containing a complex type or group the currently unsupported type composition 'Message'. Message set identifier: <insert_0>, type identifier: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The 'Multipart Messages' feature of the message model is as yet not supported by the parsers and writers. For the moment, therefore, the 'Message' type composition should not be used when defining message sets.
- Response
- Change the message set so that it does not define any complex types or groups with the type composition 'Message'.
- BIP5520
- The specified padding character is invalid for the current coded character set id.
Padding character : <insert_0>
Coded character set id (CCSID) : <insert_1>
- Severity
- 20 : Error
- Explanation
- The data converter has received a request to pad or trim an element using a padding character that is invalid for the current CCSID specified for the message.
Review previous messages for details of the message set, message type and element.
Change the padding character for the element or specify a coded character set id for the message that is compatible with the specified padding character.
- BIP5521
- The padding of an element failed.
Padding character: <insert_0>
Padding character size (bytes): <insert_2>
Padding needed (bytes): <insert_1>
Coded Character Set ID (CCSID): <insert_3>
- Severity
- 20 : Error
- Explanation
- Either the padding character specified in hexadecimal for a message element is invalid for the codepage used to write the message, or the element cannot be padded because the padding character length is not compatible with the current length of the element (for example, padding needs to be put into an odd number of bytes but the padding character is two bytes wide).
- Response
- Review previous messages for details of the message set, message type, and element.
Change the padding character for this element or specify a coded character set ID for the message that is compatible with the specified padding character.
- BIP5522
- Common Parser Interface: Internal error accessing PWFData object. Diagnostic information: <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occurred while accessing the data of an element.
- Response
- This is an internal error. Please contact your IBM support center.
- BIP5523
- Common parser interface: The string <insert_1> cannot be converted to the logical type <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occurred during the conversion of a value represented as a string into its internal logical representation. This indicates a problem with the values in the message set rather than the values in the user's message.
- Response
- It is possible that the string from the element entered as part of the message set was incompatible with the logical type. Check that all values for the element and the Encoding Null Value property for physical formats in the message set are valid for the particular element.
Note: DateTime values must match the ISO 8601 format rather than the format specified for the particular field.
- BIP5527
- The epoch specified for a date-time element is invalid. Error code: <insert_0>, epoch string: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The epoch is used with date-time when the date-time value has a physical type of seconds or milliseconds, and signifies the moment from which the seconds or milliseconds are counted. The epoch should be specified in the 'Format String' field of the date-time properties CWF tab in the Message Brokers Toolkit as a date-time string with the format 'yyyy-MM-dd'T'HH:mm ZZZ'. The default value for the epoch is '1970-01-01T00:00 +00:00'.
- Response
- Check the epoch value specified for the element. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5528
- The epoch specified for a date-time element is invalid. Error code: <insert_0>, epoch string: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The epoch is used with date-time when the date-time value has a physical type of seconds or milliseconds, and signifies the moment from which the seconds or milliseconds are counted. The epoch should be specified in the 'Format String' field of the date-time properties CWF tab in the Message Brokers Toolkit as a date-time string with the format 'yyyy-MM-dd'T'HH:mm ZZZ'. The default value for the epoch is '1970-01-01T00:00 +00:00'.
- Response
- Check the epoch value specified for the element. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5529
- The time zone specified, <insert_0>, is not supported.
- Severity
- 20 : Error
- Explanation
- Time zone <insert_0> is not supported. See the product documentation for DateTime formats for information on supported time zone formats.
- Response
- Check the message that is being processed, and ensure that only supported time zones are used in data that will be parsed as a DateTime value.
If the unsupported time zone is not present in the message, check that a time zone is set correctly on each message set physical format and redeploy the message set.
- BIP5530
- Unable to access internal calendar. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is an internal error. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5531
- Unable to add to calendar field <insert_1> by amount <insert_2>. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check the calendar field values in the message.
- BIP5532
- Unable to set calendar field. Field:<insert_1>, value:<insert_2>. Century window: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the datetime in the message.
- BIP5533
- Unable to set the calendar to date <insert_1>. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the given date value.
- BIP5534
- Unable to set time in milliseconds. Time:<insert_1>. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the Datetime value specified for the project.
- BIP5535
- Unable to set timezone <insert_1>. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the timezone
- BIP5536
- Unable to retrieve a calendar field. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is an internal error. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5537
- Unable to access internal datetime. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is an internal error. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5538
- Unable to get details of internal datetime. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- This is an internal error. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5539
- Unable to format datetime <insert_0> using format string <insert_1>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the format string <insert_1> specified for the element.
- BIP5540
- Unable to parse value <insert_0> using format string <insert_1>. Strict Datetime Checking = <insert_2>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the string being passed to the datetime parser.
- BIP5541
- Unable to set the century window. Century window in milliseconds is <insert_1>, Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the century window value specified for the project. If the problem persists please record all the details provided with this error message and contact your IBM support center.
- BIP5542
- Unable to convert this datetime to a pattern. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the entered datetime.
- BIP5543
- Unable to set the datetime pattern to <insert_1>. Error code: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the datetime pattern specified for the project.
- BIP5544
- Unable to convert passed datetime string to an allowable I or T format.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the datetime specified in the message.
- BIP5545
- DateTime entered is invalid, as leniency is not set.
- Severity
- 20 : Error
- Explanation
- Check and possibly correct the entered datetime. Remember the calendar is not lenient.
- BIP5546
- Duration value <insert_0> has an invalid combination of date/time fields.
- Severity
- 20 : Error
- Explanation
- The broker cannot process elements of type 'duration' if they contain years/months as well as days/hours/minutes/seconds.
This is a deliberate limitation of the ESQL specification.
If possible, ensure that such elements do not appear in your input messages.
Alternatively, change the type of the element to 'string'.
- BIP5547
- Duration value <insert_0> contains a field which is outside the range of a signed 32-bit integer.
- Severity
- 20 : Error
- Explanation
- The individual fields of an element of type 'duration' must lie in the range 0..2147483647.
The input message contained an element which did not meet these criteria.
- BIP5548
- Duration value <insert_0> has too much precision in the 'seconds' field.
- Severity
- 20 : Error
- Explanation
- The broker cannot process durations with a precision finer than one microsecond.
The input message contained a duration value with too much precision.
- BIP5549
- Duration value <insert_0> contains too many days.
- Severity
- 20 : Error
- Explanation
- The broker cannot process durations containing more than 100 million days.
Consider using a year/month duration instead.
- BIP5550
- Numeric value <insert_0> cannot trim to length 0.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value cannot trim to length 0.
Ensure the value does not trim to length 0.
- BIP5551
- Numeric value <insert_0> can only contain the specified decimal point.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value can only contain the specified decimal point.
The specified numeric contains a decimal point of '.' which has not been specified.
Redefine the decimal point to the appropriate value.
- BIP5552
- Numeric value <insert_0> must contain an integer part.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value must contain an integer part.
Ensure the numeric value contains an integer part, or consider not using strict numeric checking.
- BIP5553
- Numeric value <insert_0> in 'Explicit Decimal Point' format must include a decimal point.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value in 'Explicit Decimal Point' format must include a decimal point.
- Response
- Consider using a different numeric precision.
- BIP5554
- Numeric value <insert_0> in 'All Significant Digits' format must not end in a decimal point.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, only numeric values in 'Explicit Decimal Point' format can end in a decimal point.
This numeric value is not in 'Explicit Decimal Point' format and so must have a digit after the decimal point.
- Response
- Consider using a different numeric precision.
- BIP5555
- Numeric value <insert_0> can only be in exponential notation if the format is 'Exponential Notation'.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value cannot be in exponential notation unless the format is specified as 'Exponential Notation'.
- Response
- Consider using a different numeric precision.
- BIP5556
- Numeric value <insert_0> in format 'Exponential notation' must be given in exponential notation.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a value specified as format 'Exponential notation' must be given in exponential notation.
Consider using a different numeric precision.
- BIP5557
- Numeric value <insert_0> does not contain <insert_1> decimal places, as specified.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value must have the precision specified.
Consider using a different numeric precision.
- BIP5558
- Numeric value <insert_0> has VDP set, but contains a decimal point.
- Severity
- 20 : Error
- Explanation
- Under strict numeric checking, a numeric value with VDP set must not contain a decimal point.
Consider using a different numeric precision.
- BIP5559
- The dateTime value currently being written cannot be represented in seconds since an epoch date of <insert_0>.
- Severity
- 20 : Error
- Explanation
- The value is further from the given epoch date than the dateTime value can represent.
- Response
- Consider making any of the following changes:
Change your epoch date <insert_0>, by editing the physical property 'DateTime Format' for this element.
Reduce your value to within the allowed range.
Choose another dateTime representation.
- BIP5561
- The millisecond value currently being parsed cannot be represented as a dateTime value since an epoch date of <insert_0>.
- Severity
- 20 : Error
- Explanation
- The millisecond value <insert_1> is too far from the epoch <insert_0> for this dateTime representation.
- Response
- Consider making any of the following changes:
Change your epoch date <insert_0>, by editing the physical property 'DateTime Format' for this element.
Reduce your millisecond value <insert_1>.
Choose another dateTime representation.
- BIP5562
- Message set <insert_0> was deployed from Version 2.1. It must be redeployed from Version 6.
- Severity
- 20 : Error
- Explanation
- If your broker database contains message sets deployed from WebSphere MQSeries Integrator Version 2.1 then you must redeploy the message sets from the Version 6 toolkit before you start your Version 6 broker. This restriction will be removed in a future FixPak. Details of migration strategies may be found in help topic "Migrating and Upgrading".
- Response
- Redeploy the message set.
- BIP5563
- Unable to parse/write datetime <insert_0> since the DateTime Format string is not set.
- Severity
- 20 : Error
- Explanation
- Check that the DateTime Format string specified for the element is not blank.
Enter a valid format string or restore the message set default format string.
- BIP5564
- Item <insert_0> from the logical tree has matched with the message model as <insert_1>.
- Severity
- 0 : Information
- BIP5565
- Item <insert_0> from the logical tree has not matched with the message model.
- Severity
- 10 : Warning
- BIP5566
- The Custom Wire Format Length Count property for an element of type 'External Decimal' has a value less than 1.
Element name: <insert_0>
Length Count: <insert_1>
- Severity
- 20 : Error
- Explanation
- Either correct the model by setting the length of the 'External Decimal' element to a value greater than 0, or remove the element from the input data.
- BIP5601
- An error occurred while the HL7 field separator was being interpreted for element <insert_1>. The value <insert_0> is not valid.
- Severity
- 20 : Error
- Explanation
- Element <insert_1> has the TDS physical property "Interpret Element Value" set to "HL7 Field Separator". The value <insert_0> of element <insert_1> is not a valid "HL7 Field Separator" because its length is incorrect. The "HL7 Field Separator" is the first character in the Encoding Characters field, and should be of length 1.
- Response
- Check that the property "Interpret Element Value" is set correctly, and has been applied to the correct element in your message model.
- BIP5602
- An error occurred while the HL7 service string was being interpreted for element <insert_1>. The value <insert_0> is not valid.
- Severity
- 20 : Error
- Explanation
- Element <insert_1> has "Interpret Element Value" set to "HL7 Service String". The value <insert_0> of element <insert_1> is not a valid "HL7 Service String" because its length is incorrect. The "HL7 Field Separator" is the first character in the Encoding Characters field, and should be of length 1. The "HL7 Service String" represents the remaining characters in the Encoding Characters field, and should be of length 2, 3, or 4.
- Response
- Check that the property "Interpret Element Value" is set correctly, and has been applied to the correct element in your message model.
- BIP5603
- An error occurred while the TDS escape character was being specified. <insert_0> is greater than one character in length.
- Severity
- 20 : Error
- Explanation
- The escape character specified, <insert_0>, is too long. The TDS message set property 'Escape Character' must be exactly one character.
- Response
- Correct the value of the escape character in the message set, then redeploy the message set.
- BIP5604
- Required markup was missing following a complex child or group <insert_0>.
- Severity
- 20 : Error
- Explanation
- No markup was found following the complex child or group <insert_0>. The parent of this child or group has a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited'.
All complex children within a type or group with a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited' must be followed by some markup. This markup could be a 'Repeating Element Delimiter', a 'Delimiter', a 'Group Terminator', or some markup from a higher level in the message model.
- Response
- If the message model is valid correct the incoming message bit stream and parse again. If the incoming message bit stream is correct modify the message model to conform to the message bit stream. Then redeploy the message model to the broker and parse the message bit stream again.
- BIP5605
- An open or open-defined element <insert_0> has occurred inside a type or group of data element separation <insert_1>.
This data element separation type cannot contain open or open-defined elements.
The data has been discarded, and the message will be written without it.
- Severity
- 10 : Warning
- Explanation
- Confirm that the element matches that in the model, and that it is correctly described in the flow.
Collect debug-level user trace for more information on how the model is being matched.
- BIP5606
- The element or group <insert_0> has a length of zero and repeats an unbounded number of times within parent <insert_1> at offset <insert_2> in the bitstream.
- Severity
- 20 : Error
- Explanation
- The TDS Parser is unable to parse an element or group that has a length of zero and repeats an unbounded number of times because it cannot determine the actual number of repeats of the element or group in the message.
- Response
- If <insert_0> is a simple element and it is intended that it repeats an unbounded number of times and the length of the element is defined within the message model, update the model for element <insert_0> so that it has its length property set to be >= 0. Alternatively if the length of element <insert_0> is determined by a reference to another element in the message, update the value of this element in the bitstream so that it has a value >= 0. If <insert_0> is a complex element or a group and it is intended that it repeats an unbounded number of times check that at least one of its children has a length >= 0. If it is not intended that element or group <insert_0> repeats an unbounded number of times update the message model so that the Max Occurs property has a value >= 0.
- BIP5607
- The end of the bit stream has been reached at byte <insert_0>.
- Severity
- 0 : Information
- BIP5608
- <insert_0> has been matched as a group terminator for <insert_1> at byte <insert_2>.
- Severity
- 0 : Information
- BIP5609
- <insert_0> has been matched as a delimiter for <insert_1> at byte <insert_2>.
- Severity
- 0 : Information
- BIP5610
- <insert_0> has been matched as a repeating element delimiter for <insert_1> at byte <insert_2>.
- Severity
- 0 : Information
- BIP5611
- <insert_0> has been matched as a tag data separator for <insert_1> at byte <insert_2>.
- Severity
- 0 : Information
- BIP5612
- <insert_1>, ending at byte <insert_0>, was matched as the tag for <insert_2>.
- Severity
- 0 : Information
- BIP5613
- <insert_1> was matched as the group indicator for <insert_2> at byte <insert_0>.
- Severity
- 0 : Information
- BIP5614
- <insert_1>, ending at byte <insert_0>, was matched as the tag of a self-defining element.
- Severity
- 0 : Information
- BIP5615
- <insert_1>, ending at byte <insert_0>, was matched as the tag of open defined element <insert_2>.
- Severity
- 0 : Information
- BIP5616
- <insert_0> bytes from byte <insert_1> were matched using data pattern <insert_2> for <insert_3>.
- Severity
- 0 : Information
- BIP5617
- Checking for an alternative meaning for markup found at byte <insert_0>.
- Severity
- 0 : Information
- BIP5618
- The element or group <insert_0> has the repeat reference target <insert_1>, which has the invalid value <insert_2>.
- Severity
- 20 : Error
- Explanation
- The target of the repeat reference of the element or group has an invalid value. The value of the repeat reference target must be a non-negative integer.
- Response
- One of the following actions may resolve the problem:
Check that the repeat reference information has been correctly specified in the message model.
On parsing, ensure that the target of the repeat reference has been correctly parsed and that its value is not negative.
On output, ensure that the target of the repeat reference is present in the message tree and that its value is not negative.
- BIP5619
- The value of the repeat reference target <insert_1> of element or group <insert_0> cannot be determined.
- Severity
- 20 : Error
- Explanation
- One of the following actions may resolve the problem:
Check that the repeat reference information has been correctly specified in the message model.
On parsing, ensure that the target of the repeat reference has been correctly parsed and is present in the input bitstream.
On output, ensure that the target of the repeat reference is present in the message tree.
- BIP5620
- The unresolved repeat reference <insert_0> of element <insert_1> occurs within the unresolved choice <insert_2>.
- Severity
- 10 : Warning
- Explanation
- When an unresolved choice is encountered the maxmimum length of the choice is calculated based on all possible resolutions of the choice. If an element with a repeat reference that has not been resolved is encountered, the length cannot be calculated correctly. A choice is unresolved if it has a Data Element Separation of Fixed Length, Fixed Length AL3, All Elements Delimited, or Variable Length Element Delimited.
- Response
- A possible action is to modify the message model so that no element with a repeat reference occurs within an unresolved choice.
- BIP5621
- The number of repeats <insert_0> of element or group <insert_1> in the input message does not match the value <insert_2> of the repeat reference target <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The message has been parsed successfully. However the element or group has specified a repeat reference whose value does not match the number of repeats of the element or group in the input message.
- Response
- Check that the input message is valid. If not valid the possible actions are:
Modify the value of the repeat reference to match the actual number of repeats.
Modify the number of repeats to match the value of the repeat reference.
- BIP5622
- The number of repeats <insert_0> of element or group <insert_1> in the message tree does not match the value <insert_2> of the repeat reference target <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The tree has been written successfully. However the element or group has specified a repeat reference whose value does not match the number of repeats of the element or group in the message tree.
- Response
- Check that the message tree is valid. If not valid the possible actions are:
Modify the value of the repeat reference in the message tree to match the actual number of repeats of the element or group.
Modify the number of repeats of the element or group in the tree to match the value of the repeat reference.
- BIP5623
- The element or group <insert_0> is defined by its Data Pattern property as having a hexadecimal value, but the input message does not use a single-byte code page.
The Data Pattern property value is: <insert_2>
The code page used is: <insert_1>
- Severity
- 20 : Error
- Explanation
- Hexadecimal values (identified by &bsl;xNN) within a Data Pattern property are only supported when parsing messages that are encoded in single-byte code pages.
- Response
- As appropriate:
Change the Data Pattern property for the element or group within the message model so that it does not specify hexadecimal values. Redeploy the message set to the broker.
Modify the data of the input message to be encoded in a single-byte code page. Resubmit the message to the broker.
- BIP5624
- The regular expression parser used by the broker has encountered an problem.
Byte offset: <insert_0>
Message name: <insert_1>
Data Pattern: <insert_2>
- Severity
- 20 : Error
- Explanation
- The problem is probably due to a pattern that not recognised by the parser, or one that it does not know how to parse.
- Response
- Check the data pattern that you have specified for the element in the message model and ensure that it is a valid regular expression.
- BIP5625
- A quote character (<insert_0>) is missing.
- Severity
- 20 : Error
- Explanation
- When parsing a field with an opening quote character, the end of the message was reached before finding the closing quote character.
The problem might have occurred because you included a quote character within the field.
- Response
- Ensure the message being processed conforms to the message definition.
As appropriate, add a closing quote character to the field being parsed, or remove the opening quote character.
If you want to include a quote character within a quoted field, include it twice, consecutively, in the bit stream.
- BIP5626
- The value set for the 'quote character' property (<insert_0>) is invalid.
- Severity
- 20 : Error
- Explanation
- The 'quote character' property must specify a single character.
- Response
- Change the TDS physical format property 'quote character' for this message set.
- BIP5627
- The quote character (<insert_0>) at byte offset <insert_1> is invalid.
- Severity
- 20 : Error
- Explanation
- A quote character is not allowed at this position in the message.
If quoting is to be used, a quote character must occur at the start and end of a variable length field.
- Response
- Ensure the message being processed conforms to the message definition.
Check the TDS physical format property 'quote character' is specified correctly.
If you want to include a quote character within a quoted field, include it twice, consecutively, in the bit stream.
- BIP5651
- No valid Content-Type header was found in the MIME header block by line <insert_0>.
- Severity
- 20 : Error
- Explanation
- A valid Content-Type header is required in the top-level MIME header block and in any MIME header blocks for nested multipart parts.
- Response
- For information on MIME Content-Type, refer to the information center.
- BIP5652
- An invalid header line was encountered in the following MIME header block: <insert_0>
- Severity
- 20 : Error
- Explanation
- MIME header lines consist of a colon-delimited name-value pair.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5653
- A MIME part delimiter was encountered, but is not valid at line <insert_0>.
- Severity
- 20 : Error
- Explanation
- MIME multipart boundary delimiters start with a hyphen pair followed by a locally unique boundary string.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5654
- An unexpected end of data occurred at line <insert_0>.
- Severity
- 20 : Error
- Explanation
- The data might have been truncated, or a MIME boundary delimiter or header block separator might be missing.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5655
- A MIME end-delimiter was encountered, but is not valid here: <insert_0>
- Severity
- 20 : Error
- Explanation
- MIME multipart boundary delimiters start with a hyphen pair followed by a boundary string and a further hyphen pair.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5656
- Unexpected parse failure at or near: <insert_0>
- Severity
- 20 : Error
- Explanation
- Unexpected parse failure.
- Response
- This is an internal error. Contact your IBM support center.
- BIP5657
- An unexpected value-only element was found in logical tree: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Value-only elements can only appear as the first child, last child, or both, of Parts where they represent MIME preamble and epilogue data respectively.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5658
- An invalid MIME media type <insert_0> was encountered in a Content-Type header.
- Severity
- 20 : Error
- Explanation
- The MIME parser does not accept all MIME media types.
- Response
- For information on accepted MIME media types, refer to the information center.
- BIP5659
- The MIME parser was unable to convert data from base64 at or near line <insert_0>.
- Severity
- 20 : Error
- Explanation
- The parser encountered some data that was identified as being base64 encoded by its Content-Transfer-Encoding header. The data is not a valid base64 sequence.
- Response
- For information on the MIME message format, refer to the information center.
- BIP5661
- A problem was encountered in the MIME logical tree near node <insert_0>.
- Severity
- 20 : Error
- Explanation
- The logical tree does not conform to the structure expected for MIME.
- Response
- For information on the MIME logical tree, refer to the information center.
- BIP5662
- Invalid node encountered in the MIME logical tree: <insert_0>.
- Severity
- 20 : Error
- Explanation
- A Parts node was encountered in the context of a non-multipart Content-Type.
- Response
- For information on the MIME logical tree, refer to the information center.
- BIP5663
- A problem was encountered in the MIME logical tree at node: <insert_0>.
- Severity
- 20 : Error
- Explanation
- A Parts node was encountered in the context of a multipart Content-Type which does not include a valid boundary parameter definition.
- Response
- For information on the MIME logical tree, refer to the information center.
- BIP5664
- A problem was encountered in the MIME logical tree at node: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The last child of a Data node must be owned by the BLOB domain.
- Response
- For information on the MIME logical tree, refer to the information center.
- BIP5665
- The MIME parser discarded some data from the bitstream at or near line <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The MIME parser found and discarded prolog or epilog data.
- Response
- For information on the MIME logical tree, refer to the information center.
- BIP5666
- The following encoding value will be interpreted as 0 by the MIME parser: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The encoding value supplied is invalid.
- Response
- Check that the encoding value was set correctly. If the value appears to be valid please contact your IBM support center.
- BIP5667
- The value specified for the boundary parameter is invalid at or near <insert_0>.
- Severity
- 20 : Error
- Explanation
- A valid boundary parameter is required in the Content-Type header for multipart MIME.
- Response
- Check that the Content-Type value is correct and that the boundary value does not include trailing whitespace. For information on MIME Content-Type and boundary, refer to the information center.
- BIP5902
- An error occurred in parser <insert_0> whilst parsing the field named <insert_1> on behalf of node <insert_3>. The data being parsed was <insert_2>.
- Severity
- 10 : Warning
- Explanation
- This message gives the name of the field in the parser that was being parsed at the time the error occurred.
- Response
- You should check for other messages issued with this one for the full context of the error.
- BIP5903
- Invalid configuration message: type <insert_0> invalid for parser factory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to create a message format detail of type <insert_0> but this is not a valid type for parser factory <insert_1>.
- Response
- No user action required.
- BIP5904
- Invalid configuration message: type <insert_0> invalid for parser factory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to change a message format detail of type <insert_0> but this not a valid type for parser factory <insert_1>.
- Response
- No user action required.
- BIP5905
- Invalid configuration message: type <insert_0> invalid for parser factory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to delete a message format detail of type <insert_0> but this not a valid type for parser factory <insert_1>.
- Response
- No user action required.
- BIP5906
- Invalid configuration message: type <insert_0> invalid for parser factory <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The message broker received a configuration message containing an instruction to report a message format detail of type <insert_0> but this not a valid type for parser factory <insert_1>.
- Response
- No user action required.
- BIP5907
- Invalid target.
- Severity
- 20 : Error
- Explanation
- The target element must be a name element and may not have a value. In addition, the element must not be marked as 'special'. The supplied element has name <insert_0>, type <insert_1>, and value <insert_2>.
- Response
- Ensure that the field reference used to identify the target element correctly addresses a name element.
- BIP5912
- Error in parser <insert_0> whilst writing the field named <insert_1> to the bitstream.
- Severity
- 10 : Warning
- Explanation
- This message gives the name of the field in the parser that was being written at the time the error occurred. The parser was trying to write <insert_2> into this field.
- Response
- You should check for other messages issued with this one for the full context of the error.