BIP6000-6999: Runtime components - WebSphere MQ and New Era parsers

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

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

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

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

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

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

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

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

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

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

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

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

BIP6043
Invalid folder size of <insert_0> detected within a WebSphere MQ RFH2 header.
Severity
20 : Error
Explanation
WebSphere MQ RFH2 headers require that the folder size must be a multiple of four bytes and must not be negative. The message being processed did not conform to this rule.
Response
Correct the application (or compute expression) that generated the message.

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

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

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

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

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

BIP6049
A folder was nested incompletely at offset <insert_0>.
Severity
20 : Error
Explanation
When processing the RFH2 header a folder was encountered that was not correctly nested. Possible causes may be either missing end tags or multiple end tags.
Response
Correct the application (or compute expression) that generated the message.

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

BIP6060
Parser type <insert_0> created on behalf of node <insert_3> to handle portion of incoming message of length <insert_2> bytes beginning at offset <insert_1>.
Severity
0 : Information

BIP6061
Parser type <insert_0> created on behalf of node <insert_4> to handle portion of incoming message of length <insert_2> bytes beginning at offset <insert_1>. Parser type selected based on value <insert_3> from previous parser.
Severity
0 : Information

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

BIP6081
The bitstream contained an unrecognized entity at offset <insert_0>. The preceeding text was <insert_1>and the following <insert_2>.
Severity
20 : Error
Explanation
An ampersand was found in the bitstream but did not introduce a valid, recognized entity for substitution.
Response
Examine the bit-stream and determine why an invalid bit-stream was supplied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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