Diagnostic messages

We bSph ere Message Broker

Diagnostic m essages

Ve r s i o n 6 Release 0



We bSph ere Message Broker

Diagnostic m essages

Ve r s i o n 6 Release 0



Note

Before using this information and the product it supports, read the information in the Notices appendix.

This edition applies to version 6, release 0, modification 0, fix pack 4 of IBM

®

WebSphere Message Broker, with

Message Brokers Toolkit version 6, release 0, modification 2, and to all subsequent releases and modifications until

otherwise indicated in new editions.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

About this information . . . . . . . .v

Who this book is for . . . . . . . . . . . .v

How to use this book . . . . . . . . . . .v

BIP0001 to BIP1007 (Message Broker

Toolkit) . . . . . . . . . . . . . . .1

BIP1000 to BIP1999 (Configuration

Manager) . . . . . . . . . . . . . .31

BIP2000 to BIP2999 (Broker) . . . . .77

BIP3000 to BIP3999 (Built-in nodes) 185

BIP4000 to BIP4999 (Built-in nodes) 217

BIP5000 to BIP5999 (Parsers) . . . . 267

BIP6000 to BIP6999 (WebSphere MQ

and New Era parsers) . . . . . . . . 345

BIP7000 to BIP7999 (Publish

Subscribe) . . . . . . . . . . . . 353

BIP8000 to BIP8999 (Commands) . . . 383

BIP9000 to BIP9999 (z/OS and

Cloudscape) . . . . . . . . . . . . 459

Appendix. Notices . . . . . . . . . 479

Trademarks . . . . . . . . . . . . . . 481

iv Diagnostic messages

About this information

This PDF describes the user messages returned by the WebSphere

®

Message Broker

products listed below, with explanations and suggested actions. It is designed for

use as a quick reference. This PDF applies to the following products:

v WebSphere Message Broker V6.0

v WebSphere Event Broker V6.0

Always

refer to the WebSphere Message Broker online information center to access

the most current information. The information center is periodically updated on

the document update site. The PDFs that you can download from that Web site

might not contain the most current information.

Do not provide feedback on this PDF. Refer to the online information to ensure

that you have access to the most current information, and use the Feedback link

that appears at the end of each topic to report any errors or suggestions for

improvement. Using the Feedback link provides precise information about the

location of your comment.

The content of these topics is created for viewing online; you might find that the

formatting and presentation of some messages are not optimized for the printed

page. Text highlighting might also have a different appearance.

Who this book is for

The information is intended for system operators, system programmers, and

anyone who needs to understand and take action in response to WebSphere

Message Broker user messages.

How to use this book

User messages are numbered BIP0001 through BIP9999, and they are listed in this

book in numeric order. However, not all numbers have been used so the list is not

continuous.

Reading a message

The format of a WebSphere MQ Broker user message is:

v The message identifier, which comprises these parts:

1. The characters ‘BIP’ which identify the message as being from WebSphere

Message Brokers.

2. A four-digit decimal code.

v

The text of the message

Most

messages contain an explanation of why the message was issued, and a

Response section, which tells the user what to do. Read the whole message before

taking any action.

vi Diagnostic messages

BIP0001 to BIP1007 (Message Broker Toolkit)

BIP0095 SCRIBBLE subscriber has stopped

receiving messages.

BIP0110 An Internal Error has occurred.

Severity: 20 : Error

Explanation: An Unknown Internal Error has

occurred.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0111 An error has occurred while saving

<insert_0>.

Severity: 20 : Error

Explanation: Either the file has been edited with a

Text Editor, or another application has corrupted the

file.

BIP0112 An internal error occurred while

deleting the resource.

Severity: 20 : Error

Explanation: The file could be read only, or is locked

by another process.

BIP0113 An internal error occurred while

applying your changes.

Severity: 20 : Error

Explanation: Either a value that was entered was

incorrect or an unknown internal error was found.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0114 Incorrect Parameters were supplied.

Severity: 20 : Error

Explanation: Incorrect parameters were supplied.

n This is an internal error.

The method was: <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0115 An error occurred while trying to open

the editor.

Severity: 20 : Error

Explanation: An error occured opening file <insert_0>.

Either the file is corrupted or has been modified by

another application.

BIP0116 Error creating Message Definition File.

Severity: 20 : Error

Explanation: An error occured while creating

<insert_0>.

Unable to write to the local file system: <insert_0>

Response: Refresh the workspace.

BIP0117 There was an error loading plugin

<insert_0>.

Severity: 20 : Error

Explanation: Something went wrong while loading

plugin <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0118 Error creating Message Set Resource.

Severity: 20 : Error

Explanation: An error occured while creating

<insert_0>.

Unable to write to the local file system: <insert_0>

Response: Refresh the workspace.

BIP0119 Error validating resource <insert_0>.

Severity: 20 : Error

Explanation: An error occured while building resource

<insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0120 Error loading XML Schema file

<insert_0>.

Severity: 20 : Error

Explanation: An error occured wrong while loading

the XML Schema file <insert_0> Refresh the workspace.

BIP0121 Error generating WSDL File.

Severity: 20 : Error

Explanation: An error occured while generating

WSDL file <insert_0>.

Unable to write to the local file system: <insert_0>

Response: Refresh the workspace.

BIP0122 Error updating Message Set Cache file

for Message Set <insert_0>.

Severity: 20 : Error

Explanation: An error occured while updating the

Message Set Cache file for Message Set <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0123 Error saving Message Set Cache file

<insert_0>.

Severity: 20 : Error

Explanation: An error occured while saving the

Message Set Cache file <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0124 An error occurred while retrieving

properties for <insert_0>.

Severity: 20 : Error

Explanation: An unexpected error occured while

retrieving properties for <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0125 Error creating Message Set Project.

Severity: 20 : Error

Explanation: An error occured while creating Message

Set Project <insert_0>.

Response: Unable to write to the local file system:

<insert_0>

nRefresh the workspace.

BIP0126 Error creating Message Category File.

Severity: 20 : Error

Explanation: An error occured while creating

<insert_0>.

Response: Unable to write to the local file system:

<insert_0>

nRefresh the workspace.

BIP0127 Error loading Message Set Cache file for

Message Set <insert_0>.

Severity: 20 : Error

Explanation: An error occured while loading the

Message Set Cache file.

Response: Perform a full build and if the problem

persists turn on tracing to capture details of the error.

Retry the operation and contact your IBM support

center.

BIP0128 Error renaming wire format <insert_0> in

message set <insert_1>.

Severity: 20 : Error

Explanation: An internal error occured while

renmaing wire format <insert_0>.

Unable to write to the local file system.

nReplace existing message set version with local history

version and retry the operation and if the problem

persists contact your IBM support center.

BIP0129 An Internal Message Set Compile Error

has occurred.

Severity: 20 : Error

Explanation: An Unexpected Exception <insert_0>, the

message was <insert_1>. Check the user log for details

of the error. Retry the operation and contact your IBM

support center.

BIP0130 Command completed.

Severity: 0 : Information

Explanation: Refer to report file for details of what

was imported.

BIP0131 Command did not complete.

Severity: 20 : Error

Explanation: See earlier error messages for details of

the problem.

BIP0132 Incorrect arguments supplied to

mqsimigratemsgsets.

Severity: 20 : Error

Explanation: You must supply -d <directoryName>.

BIP0133 Error accessing directory <insert_0>.

Severity: 20 : Error

Explanation: Please ensure the specified directory

exists and that you have read access.

2 Diagnostic messages

BIP0134 Empty directory <insert_0>.

Severity: 10 : Warning

Explanation: No files with extension ″mrp″ were

found in the specified directory.

BIP0135 Error creating report file.

Severity: 20 : Error

Explanation: A problem was encountered creating the

<insert_0> file. If the -log option was specified please

ensure the filepath is correct. Otherwise if this problem

persists please contact your IBM Support Center.

BIP0136 A project already exists for message set

<insert_0>, ignoring message set.

Severity: 10 : Warning

Explanation: If you intend to replace this project,

either delete it and retry the operation, or rerun the

command with the -rm option.

BIP0137 An unexpected exception has occurred.

Severity: 20 : Error

Explanation: An exception was caught in method

<insert_0>, details are: <insert_1>. If this problem

persists, turn on tracing to capture details of the error.

Retry the operation and contact your IBM Support

Center.

BIP0138 Migrate message sets from a 2.1 export

file format.

Severity: 0 : Information

Explanation: Syntax: mqsimigratemsgsets

-data <workspace> Workspace location

-d <dirpath> Directory path (full or relative) containing

.mrp export files

-rm Replace message set projects if they already exist

(optional)

-v Produce verbose report (optional)

-g Create all elements and types as global (optional)

-part Partition a .mrp file into many message definition

files (optional)

-log <filepath> Report file (optional)

-pl Elements with prefixed identifiers always created as

local elements (optional)

BIP0139 A problem was encountered migrating

export file <insert_0>.

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. Refer to the report file for details of

the problem.

BIP0140 Incorrect arguments supplied to

mqsimigratemsgsets.

Severity: 20 : Error

Explanation: If you specify -log you must supply the

name of a report file.

BIP0141 Parsing of export file terminated, SAX

parsing error <insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0142 Validation failure: Missing value

reference in Element <insert_0>

MRValueMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0143 Validation failure: Unresolved

MRValueRef in Element <insert_0>

MRValueMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0144 Validation failure: Unresolved

MRValidValueRef in Element <insert_0>

MRValueMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0145 Validation failure: Missing object

reference in Compound Type <insert_0>

MRTypeMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

BIP0001 to BIP1007 (Message Broker Toolkit) 3

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0146 Validation failure: Unresolved

MRElementRef in Compound Type

<insert_0> MRTypeMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0147 Validation failure: Unresolved

MRMessageRef in Compound Type

<insert_0> MRTypeMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0148 Validation failure: Unresolved

MRCompoundRef in Compound Type

<insert_0> MRTypeMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0149 Validation failure: Missing object

reference in Category <insert_0>

MRCategoryMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0150 Validation failure: Unresolved

MRTransactionRef in Category

<insert_0> MRCategoryMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0151 Validation failure: Unresolved

MRMessageRef in Category <insert_0>

MRCategoryMember

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0152 Validation failure: Missing type

reference in Element <insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0153 Validation failure: Unresolved

MRCompoundRef in Element <insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0154 Validation failure: Missing

MRCompoundRef reference in Message

<insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0155 Validation failure: Unresolved

MRCompoundRef in Message <insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0156 Validation failure: Missing

MRSimpleRef in Element Value

<insert_0>

Severity: 20 : Error

4 Diagnostic messages

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0157 Validation failure: Unresolved

MRLengthRef in Element <insert_0>

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is that

the export file has been manually edited. Export the

message set again and retry the operation. If this error

still occurs contact your IBM Support Center.

BIP0158 Unreferenced Element Length <insert_0>

not imported

Severity: 10 : Warning

Explanation: <Not used>

BIP0159 Unreferenced Element Valid Value

<insert_0> not imported

Severity: 10 : Warning

Explanation: <Not used>

BIP0160 Unreferenced Element Value <insert_0>

not imported

Severity: 10 : Warning

Explanation: <Not used>

BIP0161 Compound Type <insert_0> has a base

type, please refer to help for details of

how this is migrated

Severity: 10 : Warning

Explanation: <Not used>

BIP0162 Member message <insert_0> min/max

occurs set to 1

Severity: 10 : Warning

Explanation: <Not used>

BIP0163 Ignoring invalid value <insert_0> for

property <insert_1>, object <insert_2>

Severity: 10 : Warning

Explanation: <Not used>

BIP0164 Ignoring unknown or dropped property

<insert_0>, object <insert_1>

Severity: 10 : Warning

Explanation: <Not used>

BIP0165 Value Constraint role <insert_0> not

migrated for Element <insert_1> of type

<insert_2>

Severity: 10 : Warning

Explanation: <Spare>

BIP0166 Ignoring Element qualification in

Message <insert_0>

Severity: 10 : Warning

Explanation: <Not used>

BIP0167 Element Qualifiers encountered, not

migrated

Severity: 10 : Warning

Explanation: <Not used>

BIP0168 Ignoring unresolved default wire format

<insert_0>

Severity: 10 : Warning

Explanation: <Not used>

BIP0169 Message Set state of frozen not

supported, ignoring

Severity: 10 : Warning

Explanation: <Not used>

BIP0170 Message Set state of finalized not

supported, ignoring

Severity: 10 : Warning

Explanation: <Not used>

BIP0171 Message Set level > 1 not supported,

Message Set name is distinguished

instead

Severity: 10 : Warning

Explanation: <Not used>

BIP0172 Message Set basing not supported,

dependency information not migrated

Severity: 10 : Warning

Explanation: <Not used>

BIP0001 to BIP1007 (Message Broker Toolkit) 5

BIP0173 C Language Binding not supported,

binding not migrated

Severity: 10 : Warning

Explanation: <Not used>

BIP0174 COBOL Language Binding not

supported, binding not migrated

Severity: 10 : Warning

Explanation: <Not used>

BIP0175 The Date Template for Element

<insert_0> does not match a Schema

simple type, using xsd:datetime or

xsd:time instead

Severity: 10 : Warning

Explanation: <Not used>

BIP0176 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Namespace <insert_0> is used in this

dictionary. Namespaces are not supported by brokers

earlier than Version 5. The path to the object which

uses the

amespace is <insert_1>.

BIP0177 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: This message set has namespace support

enabled. Namespaces are not supported by brokers

earlier than Version 5.

BIP0178 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> uses Daylight

Savings Time (DST). DST is not supported by brokers

earlier than Version 5.

BIP0179 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Custom Wire Format <insert_0> uses

Trailing Skip Count. Trailing Skip Count is not

supported by brokers earlier than Version 5. The path

to the object is <insert_1>.

BIP0180 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: XML Wire Format <insert_0> uses

NullXMLSchema to handle null values.

NullXMLSchema is not supported by brokers earlier

than Version 5.

BIP0181 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: XML Wire Format <insert_0> uses

Namespace <insert_1>. Namespaces are not supported

by brokers earlier than Version 5. The path to the object

which uses the

amespace is <insert_2>.

BIP0182 Message Set compile error.

Severity: 20 : Error

Explanation: A exception was thrown while compiling

the Message Set. The cause of the error was an

exception of type <insert_0>, with message <insert_1>.

The stack trace at the time of the error was:

<insert_2>

nRetry the operation and contact your IBM support

center.

BIP0183 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> uses Strict

Datetime Checking. This option is not supported by

brokers earlier than Version 5.

BIP0184 Invalid Rendering option detected for

Element <insert_0> in wire format

<insert_1>

Severity: 20 : Error

Explanation: Elements or element references of

complex types can only be rendered as XMLElement or

XMLElementAttrID.

Response: Modify the rendering options and

regenerate the schema.

BIP0185 Invalid Rendering option detected for

Element reference <insert_0> in wire

format <insert_1>

Severity: 20 : Error

Explanation: Elements or element references of

complex types can only be rendered as XMLEleemnt or

XMLElementAttrID.

6 Diagnostic messages

Response: Modify the rendering options and

regenerate the schema.

BIP0186 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> has Suppress

Absent Element Delimiters set to a value other than

″End Of Type″. This option is not supported by brokers

earlier than Version 5. The path to the object is

<insert_1>.

BIP0187 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> has Suppress

Absent Element Delimiters set to a value other than

EndOfType at the message set level. This option is not

supported by brokers earlier than Version 5.

BIP0188 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: Datetime Value <insert_0> is used in this

dictionary. Datetimes with time zones set are not

supported by brokers earlier than Version 5. The path

to the object which uses the Datetime value is

<insert_1>.

BIP0189 This dictionary requires a Version 5 (or

later) broker.

Severity: 10 : Warning

Explanation: This dictionary contains a facet or value

constraint with an integer which is outside the 32-bit

range.″. Brokers earlier than Version 5 do not support

64-bit integer values in facets or value constraints. The

name of the object which uses the 64-bit value is

<insert_0>.

BIP0190 Ignoring SWIFT, EDIFACT or X12

″Delimiter″ message set property value

<insert_0>, it had no effect

Severity: 10 : Warning

Explanation: <Not used>

BIP0191 Replacing dropped composition ″simple

unordered set″ with ″all″, Compound

Type <insert_0>

Severity: 10 : Warning

Explanation: <Not used>

BIP0192 Replacing dropped composition ″simple

unordered set″ with ″unorderedSet″,

Compound Type <insert_0>

Severity: 10 : Warning

Explanation: <Not used>

BIP0193 Replacing dropped composition ″empty″

with an empty ″sequence″, Compound

Type <insert_0>

Severity: 10 : Warning

Explanation: <Not used>

BIP0194 This is a large message set, you should

consider using the -part option to create

multiple message definition files

Severity: 10 : Warning

Explanation: <Not used>

BIP0195 Element <insert_0> is referenced more

than once and so is global. This is a

misuse of prefixed identifiers and could

result in duplicate elements being

created.

Severity: 10 : Warning

Explanation: <Not used>

BIP0196 Could not create physical format

<insert_0>.

Severity: 20 : Error

Explanation: The export file for this message set can

not be processed. The most likely reason for this is a

duplicate physical format identifier. If so this will be

indicated by preceding informational messages in the

report. Correct the message set, export the message set

again and retry the operation. If this error still occurs

contact your IBM Support Center.

BIP0197 This dictionary requires a Version 5 Fix

Pack 2 (or later) broker.

Severity: 10 : Warning

Explanation: Custom Wire Format <insert_0> uses 8

byte integers. This option is not supported by brokers

earlier than Version 5 Fix Pack 2. The path to the object

is <insert_1>.

BIP0198 This dictionary requires a Version 5 Fix

Pack 2 (or later) broker.

Severity: 10 : Warning

Explanation: Custom Wire Format <insert_0> uses

Packed Decimals with lengths greater than 6 bytes. This

BIP0001 to BIP1007 (Message Broker Toolkit) 7

option is not supported by brokers earlier than Version

5 Fix Pack 2. The path to the object is <insert_1>.

BIP0199 This dictionary requires a Version 5 Fix

Pack 2 (or later) broker.

Severity: 10 : Warning

Explanation: Custom Wire Format <insert_0> uses

External Decimals with lengths greater than 11 bytes.

This option is not supported by brokers earlier than

Version 5 Fix Pack 2. The path to the object is

<insert_1>.

BIP0200 This dictionary requires a Version 5 Fix

Pack 2 (or later) broker.

Severity: 10 : Warning

Explanation: Element or attribute <insert_0> uses

schema simple type ″xsd:duration″. This type is not

supported by brokers earlier than Version 5 Fix Pack 2.

The path to the object is <insert_1>.

BIP0201 This dictionary requires a Version 5 Fix

Pack 3 (or later) broker.

Severity: 10 : Warning

Explanation: Custom Wire Format <insert_0> uses

External Decimals with Sign EBCDIC Custom

representation. This option is not supported by brokers

earlier than Version 5 Fix Pack 3. The path to the object

is <insert_1>.

BIP0202 This dictionary requires a Version 5 Fix

Pack 3 (or later) broker.

Severity: 10 : Warning

Explanation: TDS Format <insert_0> uses ″Strict

Numeric Checking″. This option is not supported by

brokers earlier than Version 5 Fix Pack 3.

BIP0203 This dictionary requires a Version 5 Fix

Pack 4 (or later) broker.

Severity: 10 : Warning

Explanation: TDS Format <insert_0> uses ″Observe

Element Length″. This option is not supported by

brokers earlier than Version 5 Fix Pack 4 The path to

the object is <insert_1>.

BIP0204 This dictionary requires a Version 5 Fix

Pack 4 (or later) broker.

Severity: 10 : Warning

Explanation: TDS Format <insert_0> uses TLOG

Message Standard. This option is not supported by

brokers earlier than Version 5 Fix Pack 4.

BIP0205 This dictionary requires a Version 5 Fix

Pack 4 (or later) broker.

Severity: 10 : Warning

Explanation: CWF Format <insert_0> uses ″Output

Policy For Missing Elements″ set to a value other than

″Use Default Value″. This option is not supported by

brokers earlier than Version 5 Fix Pack 4.

BIP0206 This dictionary requires a Version 5 Fix

Pack 4 (or later) broker.

Severity: 10 : Warning

Explanation: CWF Format <insert_0> uses elements

with the ″Encoding Null″ property set to

″NullLiteralFill″. This option is not supported by

brokers earlier than Version 5 Fix Pack 4. The path to

the object is <insert_1>

BIP0207 This dictionary requires a Version 5 Fix

Pack 5 (or later) broker.

Severity: 10 : Warning

Explanation: TDS Format <insert_0> uses HL7

Messaging Standard. This option is not supported by

brokers earlier than Version 5 Fix Pack 5.

BIP0208 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: CWF Format <insert_0> uses

elements/groups with an unbounded number of

repeats. This option is not supported by brokers earlier

than Version 6. The path to the object is <insert_1>

BIP0209 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Message <insert_0> has a Message Alias

specified. This option is not supported by brokers

earlier than Version 6.

BIP0210 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: You must supply -d

<sourceFilesDirectory>.

BIP0211 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: No source directory specified after -d.

8 Diagnostic messages

BIP0212 Error accessing source files directory

<insert_0>.

Severity: 20 : Error

Explanation: Please ensure the specified directory

exists and that you have read access.

BIP0213 Empty directory <insert_0>.

Severity: 10 : Warning

Explanation: No C/COBOL/DTD/XSD files found in

the specified directory.

BIP0214 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: You must supply -p

<messageSetProjectName>.

BIP0215 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: No message set project name specified

after -p.

BIP0216 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: -log specified but no report file name

supplied.

BIP0217 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: -opt specified but no options file

supplied.

BIP0218 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: Invalid options file pathname <insert_0>.

BIP0219 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: -base specified but no base message set

name supplied.

BIP0220 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: Invalid base message set name

<insert_0>.

BIP0221 Import C/COBOL/DTD/XSD files to

generate message definitions.

Severity: 0 : Information

Explanation: Syntax: mqsicreatemsgdefs

-data <workspace> Workspace location

-p <messageSetProjectName>, will be created if it does

not exist

-base <baseMessageSetProjectName\

baseMessageSetName>

(optional)

-d <sourceFilesDirectory> (absolute/relative) containing

C/COBOL/DTD/XSD files

-rmp Replace message set project if it already exists

(optional)

-rmd Replace message definitions if they already exist

(optional)

-ns Namespace aware if creating new message set

(optional)

-msg Create messages from complex global elements

(optional)

-v Produce verbose report (optional)

-opt <importPropertiesFilePath> (absolute/relative)

(optional)

-log <reportFileName> (optional)

BIP0222 Message definition with the same name

already exists, ignoring source file

<insert_0>.

Severity: 10 : Warning

Explanation: If you intend to replace this message

definition, either delete it and retry the operation, or

rerun the command with the -rmd option.

BIP0223 The message set has no Custom Wire

Format layer defined. Only the logical

information will appear in the model.

Severity: 10 : Warning

Explanation: <Not used>

BIP0224 The message set has no XML Wire

Format layer defined. Only the logical

information will appear in the model.

Severity: 10 : Warning

Explanation: <Not used>

BIP0001 to BIP1007 (Message Broker Toolkit) 9

BIP0225 Command completed.

n Refer to file <insert_0> for details of

what was imported.

Severity: 0 : Information

Explanation: <Not used>

BIP0226 Command did not complete.

Severity: 20 : Error

Explanation: See earlier error messages for details of

the problem.

BIP0227 Error loading import options file

<insert_0>.

Severity: 20 : Error

Explanation: Please make sure the specified options

file a valid XML file.

BIP0228 Error loading import options file

<insert_0>.

Severity: 20 : Error

Explanation: Missing or invalid option for <insert_0>:

<insert_1>.

BIP0229 Empty message set project <insert_0>.

Severity: 20 : Error

Explanation: Please make sure the specified message

set project has a message set in it.

BIP0230 Message set project <insert_0> already

exists.

Severity: 20 : Error

Explanation: Please make sure the message set project

specified for -p does not exist when -base

<baseMsetProjbaseMsetName> is specified, or use the

-rmp option to

eplace the existing project.

BIP0231 A problem was encountered importing

file <insert_0>.

Severity: 20 : Error

Explanation: No message definition can be generated

for this source file. Refer to the report file for details of

the problem.

BIP0232 Error occurred while creating message

defintiion.

Severity: 20 : Error

Explanation: An internal error has occured while

importing <insert_0>. If this problem persists, turn on

tracing to capture details of the error. Retry the

operation and contact your IBM Support Center.

BIP0233 Error occurred while creating message

set <insert_0>.

Severity: 20 : Error

Explanation: An exception was caught in method

<insert_0>, details are: <insert_1>. If this problem

persists, turn on tracing to capture details of the error.

Retry the operation and contact your IBM Support

Center.

BIP0234 Error occurred while importing file

<insert_0>.

Severity: 20 : Error

Explanation: The source file contains errors, details

are: <insert_1> Please correct the error and try

importing the file again.

BIP0235 The message set has no namespace

support. The imported XML Schema

will be modified to remove namespaces.

Severity: 10 : Warning

Explanation: <Not used>

BIP0236 Error occured while creating message

definition.

Severity: 20 : Error

Explanation: <insert_0> cannot be imported since it

contains unsupported features.

<insert_1>

BIP0237 Error loading import options file

<insert_0>.

Severity: 20 : Error

Explanation: Missing uri and/or prefix attributes in

URI_PREFIX_PAIRS.

BIP0238 Error occured while importing file

<insert_0>.

Severity: 20 : Error

Explanation: The file cannot be renamed to form a

valid message artifact file name.

BIP0239 Byte alignment for elements referenced

in the complex type <insert_0> may not

be correct.

Severity: 10 : Warning

Explanation: Byte alignment should be fixed by

10 Diagnostic messages

editing the file through the message definition editor.

Probable cause: Element in the COBOL copy book has

OCCURS DEPENDING ON clause.REA239 = <Not

used>

BIP0240 An unexpected exception has occurred

while importing a COBOL file

<insert_0>.

Severity: 20 : Error

Explanation: Check the COBOL copybook is valid by

ensuring it compiles on the system from which it was

obtained. Correct any errors and try importing the file

again. If this problem persists, contact your IBM

Support Center.

BIP0241 An unexpected exception has occurred

while importing a C file <insert_0>.

Severity: 20 : Error

Explanation: Check the C file is valid by ensuring it

compiles on the system from which it was obtained.

Correct any errors and try importing the file again. If

this problem persists, contact your IBM Support Center.

BIP0242 The source C file name is invalid:

<insert_0>.

Severity: 20 : Error

Explanation: Rename the C file so that it does not

contain any of the following characters <insert_’, ’%’,

’’’, ’#’, ’>. Correct any errors and try importing the file

again.

BIP0243 The source COBOL file name is invalid:

<insert_0>.

Severity: 20 : Error

Explanation: Rename the COBOL file so that it does

not contain any of the following characters <insert_’,

’%’, ’’’, ’#’, ’>. Correct any errors and try importing the

file again.

BIP0250 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: An element/attribute has the ″Interpret

Value As″ property set to a value other than ″None″.

This option is not supported by brokers earlier than

Version 6. The path to the object is <insert_0>

BIP0251 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> sets XML

version to <insert_1>. Only XML version 1.0 is

supported by brokers earlier than Version 6.

BIP0252 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> sets Suppress

XML Encoding to false. Generation of the XML

declaration ″encoding″ attribute is not supported by

brokers earlier than Version 6.

BIP0253 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical format <insert_0> has XML

″Output policy for xsi:type attributes″ set to a value

other than ″When Present″. This option is not

supported by brokers earlier than Version 6.

BIP0254 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Physical Format <insert_0> has the ″Use

Input UTC Format on Output″ property set to true.

This option is not supported by brokers earlier than

Version 6.

BIP0255 This dictionary requires a Version 6 (or

later) broker.

Severity: 10 : Warning

Explanation: Message <insert_0> has XML ″Output

policy for xsi:type attributes″ set to a value other than

″When Present″. This option is not supported by

brokers earlier than Version 6.

BIP0256 Error details are

<insert_0>

Severity: 20 : Error

Explanation: <Not used>

BIP0257 Within a message set, a message name

<insert_0> and a message alias must be

unique.

Severity: 20 : Error

Explanation: A message alias or message name cannot

have the same value as any other message name or

message alias within the message set.

BIP0001 to BIP1007 (Message Broker Toolkit) 11

BIP0258 Incorrect arguments supplied to

mqsicreatemsgdefs.

Severity: 20 : Error

Explanation: You must supply -data

<workspaceDirectory>.

BIP0259 Incorrect arguments supplied to

mqsimigratemsgsets.

Severity: 20 : Error

Explanation: You must supply -data

<workspaceDirectory>.

BIP0310 Error occurred while generating XML

schema.

Severity: 20 : Error

Explanation: An internal error occured while creating

<insert_0>. If this problem persists, turn on tracing to

capture details of the error. Retry the operation and

contact your IBM Support Center.

BIP0311 Error occurred while generating XML

schema.

Severity: 20 : Error

Explanation: An internal error occured while trying to

locate attribute <insert_0> in namespace <insert_1>. If

this problem persists, turn on tracing to capture details

of the error. Retry the operation and contact your IBM

Support Center.

BIP0312 Error occurred while generating XML

schema.

Severity: 20 : Error

Explanation: An internal error occured while trying to

locate element <insert_0> in namespace <insert_1>. If

this problem persists, turn on tracing to capture details

of the error. Retry the operation and contact your IBM

Support Center.

BIP0313 Error loading MXSD file <insert_0>.

Severity: 20 : Error

Explanation: An error occured wrong while loading

the MXSD file <insert_0> Refresh the workspace.

BIP0320 Error occurred while generating HTML

documentation.

Severity: 20 : Error

Explanation: An internal error occured while

documentation. If this problem persists, turn on tracing

to capture details of the error. Retry the operation and

contact your IBM Support Center.

BIP0330 Error creating WSDL definitions.

Severity: 20 : Error

Explanation: An internal error occured while

generating WSDL definitions for message set

<insert_0>. If this problem persists, turn on tracing to

capture details of the error. Retry the operation and

contact your IBM Support Center.

BIP0331 Error importing WSDL File.

Severity: 20 : Error

Explanation: An error occured while creating

<insert_0> for the following reason: <insert_1>

Response: See report log for more details.

BIP0610 Import a WSDL file to generate a

message definition.

Severity: 0 : Information

Explanation: Syntax: mqsicreatemsgdefsfromwsdl

-data <workspace> Workspace location

-p <messageSetProjectName>, will be created if it does

not exist

-base <baseMessageSetProjectName\

baseMessageSetName>

(optional)

-d <sourceFilesDirectory> (absolute/relative) containing

WSDL files

-f <wsdlFile> (absolute/relative to -d) The wsdl file to

import

-binding <bindingName> (optional if wsdl contains

only one binding)

-rmp Replace message set project if it already exists

(optional)

-rmd Replace message definitions if they already exist

(optional)

-v Produce verbose report (optional)

-log <reportFileName> (optional)

-vfa <wsi-validation-action>, where the action is one of

″ignore″, ″warn″, or ″fail″ (optional)

BIP0611 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: You must supply -d

<sourceFilesDirectory>.

BIP0612 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: No source directory specified after -d.

12 Diagnostic messages

BIP0613 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: You must supply -p

<messageSetProjectName>.

BIP0614 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: No message set project name specified

after -p.

BIP0615 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: You must supply -f <wsdlFile>.

BIP0616 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: No wsdl file specified after -f.

BIP0617 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: -log specified but no report file name

supplied.

BIP0618 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: -base specified but no base message set

name supplied.

BIP0619 Invalid arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: The provided WSDL <insert_0> contains

no bindings. The WSDL to import must contain at least

one binding.

BIP0620 Invalid arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: -binding was not specified however the

wsdl being imported has multiple bindings. Specify the

binding to import and re-run the tool.

BIP0621 Invalid arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: The binding name <insert_0> does not

exist in the WSDL definition

BIP0622 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: Invalid base message set name

<insert_0>.

BIP0623 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: -binding specified but no binding name

supplied.

BIP0624 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: -vfa specified but no WSI validation

action supplied.

BIP0625 Incorrect arguments supplied to

mqsicreatemsgdefsfromwsdl.

Severity: 20 : Error

Explanation: You must supply -data

<workspaceDirectory>.

BIP0800 An unexpected exception occurred:

<insert_0>

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0801 An unexpected exception occurred:

<insert_0>

Severity: 20 : Error

Explanation: A <insert_0> exception occurred but

provided no additional information.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0001 to BIP1007 (Message Broker Toolkit) 13

BIP0810 An error occurred while saving file

<insert_0>.

Severity: 20 : Error

Explanation: An exception occurred and the file is not

saved.

Response: Resolve the reason of error and try again.

BIP0811 The file <insert_0> refers some

inaccessible resources.

Severity:

20 : Error

Explanation: Unloadable resources and mappings

associated with them will be removed from this file at

next save.REA811 =

Some of the referenced resources cannot be loaded.

Response: Refer to task list for more information.

BIP0812 The file <insert_0> cannot be loaded.

Severity: 20 : Error

Explanation: Some error occurred while loading this

file.

Response: Refer to task list for more information.

BIP0813 The resource <insert_0> cannot be

created.

Severity: 20 : Error

Explanation: Unable to write to the local file system:

<insert_0>

Response: Refresh the workspace.

BIP0814 The resource <insert_0> cannot be

created.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>.

Response: Resolve the reason of error and try again.

BIP0815 The container at <insert_0> cannot be

accessed.

Severity: 20 : Error

Explanation: Either the resource does not exist or it is

a closed project.

Response: If the resource is a closed project, open it.

Otherwise, refresh your workspace and try again.

BIP0816 The resource <insert_0> could not be

<insert_1>.

Severity: 20 : Error

Explanation: The workspace is out of synch with the

local file system.

Response: Refresh your workspace and try again.

BIP0817 The resource <insert_0> could not be

<insert_1>.

Severity: 20 : Error

Explanation: Unable to read the resource from the

local file system. Another application might be

preventing this resource from being accessed.

Response: Close other applications that are accessing

the resource and try again.

BIP0818 The resource <insert_0> could not be

<insert_1>.

Severity: 20 : Error

Explanation: Unable to write the resource to the

destination in the local file system. This resource may

already exist in the file system.

Response: Refresh your workspace and try again.

BIP0819 The resource <insert_0> could not be

<insert_1>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0820 Unable to delete resources.

Severity: 20 : Error

Explanation: The workspace is out of synch with the

file system.

Response: Refresh your workspace and try again.

BIP0821 Unable to delete resources.

Severity: 20 : Error

Explanation: Unable to access one of the selected

resources. Another application might be preventing this

resource from being accessed.

Response: Close other applications that are accessing

the resources being deleted and try again.

14 Diagnostic messages

BIP0822 Unable to delete resources.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0823 An error occurred while saving file

<insert_0>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0824 The resource <insert_0> could not be

loaded.

Severity: 20 : Error

Explanation: The resource no longer exists on the file

system.

Response: Refresh your workspace and then recreate

the resource or re-add it from the repository.

BIP0825 The resource <insert_0> could not be

loaded.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0826 The resource <insert_0> could not be

loaded.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Recreate the resource or replace it with a

saved version from the

epository.

BIP0827 The palette could not be generated.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Retry the operation and contact your IBM

support center.

BIP0828 The class <insert_0> could not be

loaded.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Close and then reopen the workbench and

try again.

BIP0829 Unable to load the selected wizard.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Ensure the wizard’s plugin is installed

correctly, restart the workbench and try again.

BIP0830 Unable to locate the selected marker.

Severity: 20 : Error

Explanation: Marker <insert_0> does not exist.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0831 The resource <insert_0> could not be

accessed.

Severity: 20 : Error

Explanation: The workspace is out of synch with the

local file system.

Response: Refresh your workspace and try again.

BIP0832 The resource <insert_0> could not be

accessed.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0833 The resource <insert_0> could not be

accessed.

Severity: 20 : Error

Explanation: Unable to access the resource on the

local file system. Another application might be

preventing this resource from being accessed.

Response: Close other applications that are accessing

the resource and try again.

BIP0001 to BIP1007 (Message Broker Toolkit) 15

BIP0834 The resource <insert_0> could not be

closed.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: Resolve the reason of error and try again.

BIP0835 Unable to alter schema paths.

Severity: 20 : Error

Explanation: The current ESQL source code cannot be

parsed correctly.

Response: Resolve the syntax error and try again.

BIP0836 The action could not be performed on

the resources.

Severity: 20 : Error

Explanation: Exceptions occurred and provided the

following information.

Response: Resolve the reason of error and try again.

BIP0837 Migrate message flows from a 2.1 export

file format.

Severity: 0 : Information

Explanation: Syntax: mqsimigratemsgflows

-data <workspace> Workspace location

-p <projectName> The name of the project to use or

create

-d <dirpath> Directory path (full or relative) containing

the flow export files

-rm Replace message flow projects if they already exist

(optional)

-log <filepath> Report file (optional)

BIP0838 Unable to start message flows

migration.

Severity: 20 : Error

Explanation: No parameters were supplied to the

mqsimigratemsgflows command.

Correct and reissue the command.

BIP0839 Incorrect arguments supplied to

mqsimigratemsgflows.

Severity: 20 : Error

Explanation: You must supply -p <projectName>.

BIP0840 Incorrect arguments supplied to

mqsimigratemsgflows.

Severity: 20 : Error

Explanation: You must supply -d <dirPath>.

BIP0841 The resource <insert_0> could not be

added to broker archive file <insert_1>.

Severity: 20 : Error

Explanation: Compile errors occurred in the following

resource: <insert_0>

Rebuild your project and try again.

BIP0842 The message flow application <insert_0>

could not be added to broker archive

file <insert_1>.

Severity: 20 : Error

Explanation: Internal exceptions occurred in the

<insert_0> plugin

Resolve the reason of error and try again.

BIP0843 Unable to use exported flows directory

<insert_0>.

Severity: 20 : Error

Explanation: The specified directory does not exist.

Specify an existing exported message flows directory.

BIP0844 Unable to use exported flows directory

<insert_0>.

Severity: 20 : Error

Explanation: The specified directory is in fact a file.

Specify an existing exported message flows directory.

BIP0845 Unable to use exported flows directory

<insert_0>.

Severity: 20 : Error

Explanation: The specified directory is not readable.

Ensure the directory has sufficient read permissions.

BIP0846 Unable to find exported flows in

directory <insert_0>.

Severity: 20 : Error

Explanation: The specified directory does not contain

any file.

Specify an existing exported message flows directory.

16 Diagnostic messages

BIP0847 Unable to create the migration report

file.

Severity: 20 : Error

Explanation: The mqsimigratemsgflows command

was unable to create the report file

in the current working directory.

Verify you can create any text file in the current

working directory.

BIP0848 Unable to parse message flow export

file <insert_0>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message:

<insert_1>.

The export file must be a well formed XML file.

BIP0849 Unable to migrate message flow export

file <insert_0>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message:

<insert_1>.

BIP0850 Unable to migrate message flow export

file <insert_0>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message:

<insert_1>.

Ensure the file has read permission and no other

application is accessing it.

BIP0851 Unable to create project <insert_0>.

Severity: 20 : Error

Explanation: The specified project does not exist and

cannot be created.

Specify an existing project or a project with a valid

name.

BIP0852 Unable to use existing project

<insert_0>.

Severity: 20 : Error

Explanation: The specified project is not a message

flow project.

Specify an existing message flow project

or a non-existing project with a valid name.

BIP0853 The resource <insert_0> could not be

added to broker archive file <insert_1>.

Severity: 20 : Error

Explanation: Internal errors occurred while compiling

the following resource: <insert_0>

Resolve the reason of error and try again.

BIP0854 An unexpected exception occurred:

<insert_0>.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred while

processing the following resource: <insert_1>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0855 Unable to migrate message flow export

file <insert_0>.

Severity: 20 : Error

Explanation: The message flow export file is empty.

Ensure the file is not damaged and has appropriate

read permissions.

BIP0856 Unable to migrate message flow export

file <insert_0>.

Severity: 20 : Error

Explanation: The message flow export file is not

readable.

Ensure the file has appropriate read permissions.

BIP0857 Selected Execution Group(s) associated

to broker <insert_0> cannot be deleted.

Severity: 20 : Error

Explanation: A Broker must contain at least one

Execution Group.

Unselect one or more execution groups or create

another execution group and retry the operation.

BIP0858 Unable to create message flow

<insert_0> in workspace.

Severity: 20 : Error

Explanation: The migrate command could not write

the new message flow.

The following error message was issued by the

workspace:

<insert_0>.

Verify you are able to create files in the project.

BIP0001 to BIP1007 (Message Broker Toolkit) 17

BIP0859 The message flow name <insert_0> is

invalid.

Severity: 10 : Warning

Explanation: The migrate command cannot use the

flow name as the file name.

The flow name has been changed to <insert_0>.

You may later rename the flow from the Message

Brokers Toolkit.

BIP0860 Numeric conversion from string

<insert_0> to type double failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

BIP0861 Numeric conversion from string

<insert_0> to type long failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

BIP0862 Numeric conversion from string

<insert_0> to type float failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

BIP0863 Numeric conversion from string

<insert_0> to type integer failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

BIP0864 The plugin [<insert_0>] failed to

complete its configuration tasks.

Severity: 20 : Error

Explanation: A unexpected runtime exception

[<insert_0>] occurred whilst performing task

[<insert_1>].

Response: <insert_2>

Resolve the reason of error and try again.

Be aware your runtime may now be in an incomplete

state.

BIP0865 The plugin [<insert_0>] failed to

complete a configuration task.

Severity: 20 : Error

Explanation: An attempt to perform task [<insert_0>],

resulted in an error.

Response: <insert_1>

<insert_2>

Resolve the reason of error and try again.

Be aware your runtime may now be in an incomplete

state.

BIP0866 The plugin [<insert_0>] failed to

complete its configuration tasks.

Severity: 10 : Warning

Explanation: The wizards configuration processing

was halted by the user.

Processing was halted after the successful completion

of task [<insert_0>]

Response: <insert_1>

Be aware your runtime may now be in an incomplete

state.

BIP0867 A dependent subflow or primitive is

missing.

Severity: 10 : Warning

Explanation: The migration command cannot evaluate

if a missing flow is a subflow

with terminals or a user defined node. The migration

made the assumption

that it was a subflow.

If the subflow was indeed a user defined node, change

the extension to .msgnode,

open the message node in the editor, make some

changes and save. The message node

will be regenerated correctly.

A flow may not be able to resolve this subflow, if it has

been renamed.

In that case, re-export the flows and subflows in the

same export file.

Message flow name being migrated: <insert_0>

Missing flow name: <insert_1>

Missing flow uuid: <insert_2>

BIP0868 Unable to correctly migrate a promoted

property.

Severity: 20 : Error

Explanation: The migration command cannot locate

the node hosting an overridden property.

A placeholder property was substituted to preserve the

flow integrity.

Message flow name being migrated: <insert_0>

Promoted property name: <insert_1>

Overridden property name: <insert_2>

After migration, from the Message Brokers Toolkit,

18 Diagnostic messages

promote the property again.

ESQL code reuse has been enhanced significantly and is

no longer promotable.

Refer to the ESQL programming guide for further

information.

BIP0869 Conversion from string <insert_0> to

Time failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

The format for an ESQL Time property is:

hh:mm:ss.ffffff

BIP0870 Conversion from string <insert_0> to

Timestamp failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

The format for an ESQL Timestamp property is:

yyyy-mm-dd hh:mm:ss.ffffff

BIP0871 Conversion from string <insert_0> to

Date failed.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

Use Message Brokers Toolkit to open the flow and

assign a valid value.

The format for an ESQL Date property is: yyyy-mm-dd

BIP0872 Unable to assign a property value.

Severity: 20 : Error

Explanation: Cannot assign a value for the property

<insert_0> from the flow <insert_1>.

The given value is not in the list of the enumeration

type.

Property value from the migrated flow: <insert_2>

Property type enumerated choices: <insert_3>

After migration, from the Message Brokers Toolkit,

assign a value to the property.

BIP0873 An unexpected error occurred while

trying to open an editor.

Severity: 20 : Error

Explanation: An internal error occurred which

reported the following message: <insert_0>.

Response: Turn on tracing to capture details of the

error. Retry the operation and contact your IBM

support center.

BIP0874 A failure response has been received

from Configuration Manager on

<insert_0>.

Severity: 20 : Error

Explanation: A failure response has been received

which provided the message(s) detailed below.

Response: Editor/Viewer has been refreshed with

Configuration Manager content.

BIP0875 An unknown type response has been

received from Configuration Manager

on <insert_0>.

Severity: 20 : Error

Explanation: An unknown type response has been

received which provided the message(s) detailed below.

Response: Editor/Viewer has been refreshed with

Configuration Manager content.

BIP0876 Changes you initiated may conflict with

Configuration Manager actual content.

Severity: 10 : Warning

Explanation: Configuration Manager sent a change

notification while you are editing its content.

Response: To avoid any potential conflict, close editor

without saving.

BIP0877 Initiated changes cannot be processed

for now.

Severity: 10 : Warning

Explanation: Configuration Manager did not send yet

all expected responses to previous actions.

Response: Click OK to stop waiting for these

responses and to refresh editor content.

You will then be able to initiate changes.

Click Cancel to go on waiting for Configuration

Manager responses to be processed.

BIP0878 Paste operation cannot performed as the

copied object has been deleted.

Severity: 20 : Error

Explanation: A previously copied domain object

cannot be pasted as it does no longer exist

on the Configuration Manager.

Response: Copy a new object before retrying the paste

operation.

BIP0001 to BIP1007 (Message Broker Toolkit) 19

BIP0879 Unable to write an ESQL Module

Severity: 20 : Error

Explanation: The migrate command could not write

an ESQL Module.

Error message from the Message Brokers Toolkit

workspace:

<insert_0>

Message flow name being migrated: <insert_1>

Message flow ESQL filename: <insert_2>

Message flow node hosting the ESQL module:

<insert_3>

ESQL Module content: <insert_4>

BIP0880 Unable to create a connection between

two nodes.

Severity: 20 : Error

Explanation: The migration command cannot connect

the node <insert_0>

to the node <insert_1>.

Message flow name being migrated: <insert_2>

After migration, from the Message Brokers Toolkit, edit

the flow and connect the two nodes.

BIP0881 Unable to restore a connection bend

point.

Severity: 0 : Information

Explanation: The migration command cannot restore a

bend point on a connection between

two nodes.

Message flow name being migrated: <insert_0>

After migration, from the Message Brokers Toolkit, edit

the flow and reroute the connection.

BIP0882 Unable to locate the source node of a

connection.

Severity: 20 : Error

Explanation: The migration command cannot locate

the node initiating a connection.

Message flow name being migrated: <insert_0>

Message processing source node UUID: <insert_1>

After migration, from the Message Brokers Toolkit, edit

the flow,

locate the source node and reconnect it.

BIP0883 Unable to locate the target node of a

connection.

Severity: 20 : Error

Explanation: The migration command cannot locate

the node ending a connection.

Message flow name being migrated: <insert_0>

Message processing target node UUID: <insert_1>

After migration, from the Message Brokers Toolkit, edit

the flow,

locate the source node and reconnect it.

BIP0884 A RETURN statement has been detected

in the Filter ESQL expression.

Severity: 0 : Information

Explanation: The migrate command has not added a

RETURN statement as one was detected.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

After migration, from the Message Brokers Toolkit,

verify that a RETURN statement exists.

BIP0885 A RETURN statement has not been

detected in the Filter ESQL expression.

Severity: 0 : Information

Explanation: The migrate command has added a

RETURN statement as one was not detected.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

After migration, from the Message Brokers Toolkit,

verify the RETURN statement is correct.

BIP0886 An unexpected exception occurred:

<insert_0>

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>.

Response: The migration command may have

terminated prematurely.

If so, remove the export file being migrated, and

resume migration.

Consult the report.txt file for migration progress.

BIP0887 The <insert_0> is not properly set in

enqueue file <insert_1>.

Severity: 20 : Error

Explanation: Check the enqueue file <insert_0> for

errors and try again.

BIP0888 The resource <insert_0> could not be

added to broker archive file <insert_1>.

Severity: 20 : Error

Explanation: <insert_1>.

BIP0889 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Message Brokers Toolkit is experiencing

problems communicating with the Configuration

Manager on <insert_0>.

20 Diagnostic messages

Response: Ensure that the Configuration Manager is

available.

If so, do the following:

1) Select the Window > Preferences menu.

2) Select the Broker Administration > Configuration

Manager Proxy preferences.

3) Increase the Maximum retry attempts, Initial and/or

Increase time between attempts values.

4) Apply the changes.

5) Retry the operation.

BIP0890 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Message Brokers Toolkit is experiencing

problems communicating with the Configuration

Manager on <insert_0>.

Response: Resolve the reason of error and try again.

BIP0891 An empty file cannot be added to a

message flow as a subflow.

Severity: 20 : Error

Explanation: Empty files are not valid as message

subflows.

Response: Add content to the subflow and try the

operation again.

BIP0892 A successful response has been received

from Configuration Manager on

<insert_0>.

Severity: 0 : Information

Explanation: A successful response has been received

which provided the message(s) detailed below.

BIP0893 Cannot communicate with queue

manager <insert_0>.

Severity: 20 : Error

Explanation: An unexpected exception occurred while

attempting to communicate with the queue manager.

Response: Check the name/status of the queue

manager and try again.

BIP0894 Topology cannot be saved because some

brokers are missing Queue Manager

Name definition.

Severity: 20 : Error

Explanation: Mandatory ″Queue Manager Name″

property is not filled for following brokers:

<insert_0>

Modify this property for each listed broker and try the

operation again.

BIP0895 Cannot dequeue message from queue

<insert_0> using queue manager

<insert_1>.

Severity: 20 : Error

Explanation: Check the enqueue file <insert_0> for

errors and try again.

BIP0896 Cannot enqueue message into queue

<insert_0> using queue manager

<insert_1>.

Severity: 20 : Error

Explanation: Check the enqueue file <insert_0> for

errors and try again.

BIP0897 Cannot delete Configuration Manager’s

subscription.

Severity: 10 : Warning

Explanation: Subscriptions starting with $SYS or

$ISYS are used internally

by the Configuration Manager and cannot be deleted.

BIP0898 Cannot add subflow <insert_0>

Severity: 20 : Error

Explanation: The reference to file <insert_0> is

ambiguous.

A file with the same name may exist in the same

schema in a referenced project.

Response: Rename one of the files and try the

operation again.

BIP0899 Cannot add subflow <insert_0>

Severity: 20 : Error

Explanation: The file <insert_0> cannot be found.

The file may exist in a project that is not referenced.

Response: Add the project containing the subflow as a

referenced project and try the operation again.

BIP0900 An exception occurred when trying to

update Configuration Manager on

<insert_0>.

Severity: 20 : Error

Explanation: An exception has been received which

provided additional information detailed below.

Response: Editor/Viewer has been refreshed with

Configuration Manager content.

BIP0001 to BIP1007 (Message Broker Toolkit) 21

BIP0901 <insert_0> Editor cannot be opened.

Severity: 20 : Error

Explanation: The Configuration Manager has sent an

ACL restriction on <insert_0>

Verify the ACL and retry the operation.

BIP0902 ESQL breakpoint marker in file

<insert_0> cannot be updated.

Severity: 20 : Error

Explanation: The breakpoint location or breakpoint

attributes cannot be set.

Errors could be happened in <insert_0>.

BIP0903 A Compute node has been substituted

for an Extract node.

Severity: 0 : Information

Explanation: The Extract node is now developed

using the mapping editor.

It no longer hosts hand coded ESQL statements.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

BIP0904 A Database node has been substituted

for a Warehouse node.

Severity: 0 : Information

Explanation: The Warehouse node is now developed

using the mapping editor.

It no longer hosts hand coded ESQL statements.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

BIP0905 Not enough memory to display image

with given scale factor.

Severity: 20 : Error

Explanation: Selected image <insert_0>

cannot be displayed with a <insert_1> scale factor.

Response: Select another image or decrease scale

factor and retry the operation.

BIP0906 Cannot load a platform dependency.

Severity: 20 : Error

Explanation: A suitable extension for point <insert_0>

cannot be loaded.

BIP0907 The file provided cannot be used.

Severity: 20 : Error

Explanation: The file <insert_0> is not writable.

Modify Read-only attribute or choose another file.

BIP0908 An attempt was made to create a new

file but a failure return code was

returned

Severity: 20 : Error

Explanation: The file <insert_0> could not be created.

The user should amend the filename and try again.

BIP0909 An attempt was made to create a new

file but an exception was thrown.

Severity: 20 : Error

Explanation: The file <insert_0> could not be created

(after <insert_1>).

BIP0910 The file provided cannot be opened.

Severity: 20 : Error

Explanation: The file <insert_0> doesn’t exist.

nChoose another file and try again.

BIP0911 Would you like to override an existing

file?

Severity: 10 : Warning

Explanation: The file <insert_0> already exists.

nDo you want to replace it?

BIP0912 The file provided cannot be parsed.

Severity: 20 : Error

Explanation: The file <insert_0> is not a valid topics

export file.

nChoose a valid topics file and try again.

BIP0913 Configuration Manager is not at the

required software product level.

Severity: 20 : Error

Explanation: The version of the Configuration

Manager is not compatible with current version of

Message Brokers Toolkit.

Reply to the sent request indicates that Configuration

Manager is not at a sufficient level.

Try to connect to a same product level Configuration

Manager and retry the operation.

BIP0914 Message Brokers Toolkit is unable to

communicate with the Configuration

Manager.

Severity: 20 : Error

Explanation: Network connection may be dropped

and / or WebSphere MQ queue manager <insert_0> is

not running and / or listener on port <insert_1> is not

started.

22 Diagnostic messages

Response: First, check the Queue Manager is available

by doing the following:

1) Ensure network connection is enabled.

2) Start WebSphere MQ queue manager <insert_0> if

necessary.

3) Ensure listener on port <insert_1> is running.

Then, do the following:

4) Disconnect from the Domain if already connected.

5) Connect to the Domain.

6) Retry the operation.

BIP0915 Message Brokers Toolkit is unable to

communicate with the Configuration

Manager.

Severity: 20 : Error

Explanation: WebSphere MQ queue manager

<insert_0> cannot be reached.

Response: Ensure first the Queue Manager is

available.

If so, then do the following:

1) Disconnect from the Domain if already connected.

2) Connect to the Domain.

3) Retry the operation.

BIP0916 Unable to dequeue message.

Severity: 20 : Error

Explanation: Cannot get message from queue

<insert_0> under queue manager <insert_1>.

Response: Check names of the queue and the queue

manager and try again.

BIP0917 No messages found to dequeue.

Severity: 20 : Error

Explanation: No messages were found on queue

<insert_0> under queue manager <insert_1>.

Response: Check the names and status of the queue

and the queue manager and try again.

BIP0918 The resource <insert_0> could not be

refactored.

Severity: 20 : Error

Explanation: An error occurred while trying to read

the file from disk.

Response: The file may be internally inconsistent.

Modify the file in its editor and save it to correct the

error.

BIP0919 An exception occurred while sending a

message to Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: Text Messenger is experiencing problems

sending a message.

nRestart the application.

BIP0920 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Text Messengers connection on Queue

Manager <insert_0> has been broken or is not available.

nEnsure your Queue Manager is available and your

listener is running.

BIP0921 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Text Messenger is experiencing problems

communicating with the Configuration Manager on

<insert_0>.

nEnsure you have run the create queue wizard for the

Getting Started Samples.

BIP0922 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Text Messenger is experiencing problems

sending a message.

BIP0923 An exception occurred while

subscribing messages on Queue

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Surf subscriber is experiencing problems

sending subscriptions.

nRestart the application.

BIP0924 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Surf Subscribers connection on Queue

Manager <insert_0> has been broken or is not available.

nEnsure your Queue Manager is available and your

listener is running.

BIP0001 to BIP1007 (Message Broker Toolkit) 23

BIP0925 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Surf Subscriber is experiencing problems

communicating with the Configuration Manager on

<insert_0>.

nEnsure you have run the create queue wizard for the

Getting Started Samples.

BIP0926 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Surf Subscriber is experiencing problems

subscribing topics.

BIP0927 An exception occurred while publishing

messages on Queue Manager on

<insert_0>.

Severity: 20 : Error

Explanation: Publisher is experiencing problems

publishing messages.

nRestart the application.

BIP0928 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Publishers connection on Queue

Manager <insert_0> has been broken or is not available.

nEnsure your Queue Manager is available and your

listener is running.

BIP0929 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Publisher is experiencing problems

communicating with the Configuration Manager on

<insert_0>.

nEnsure you have run the create queue wizard for the

Getting Started Samples.

BIP0930 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Publisher is experiencing problems

publishing messages.

BIP0931 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Pagers connection on Queue Manager

<insert_0> has been broken or is not available.

nEnsure your Queue Manager is available and your

listener is running.

BIP0932 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Pager is experiencing problems

communicating with the Configuration Manager on

<insert_0>.

nEnsure you have run the create queue wizard for the

Getting Started Samples.

BIP0933 An exception occurred while

communicating with the Configuration

Manager on <insert_0>.

Severity: 20 : Error

Explanation: Pager is experiencing problems receiving

messages.

BIP0934 An exception occurred while getting

messages from Queue Manager

<insert_0>.

Severity: 20 : Error

Explanation: Pager is experiencing problems getting

messages.

nRestart the application.

BIP0935 Several domain connection files exist for

the domain.

Severity: 20 : Error

Explanation: Domain connection editor cannot be

opened because several domain connection files exist

for the domain <insert_0>.

Response: Select the domain connection file you want

to edit and open it.

BIP0936 Topology Configuration cannot be

deployed for now.

Severity: 10 : Warning

Explanation: Topology Configuration on <insert_0>

cannot be deployed because a previous Broker

Configuration is deployed.

24 Diagnostic messages

Response: Retry later the deploy operation on Broker

Topology.

BIP0937 Problem on connecting to broker.

Severity: 20 : Error

BIP0938 There was a problem trying to create a

subscriber.

Severity: 20 : Error

BIP0939 There was a problem trying to start the

subscriber listening on the subscribe

queue.

Severity: 20 : Error

BIP0940 There was a problem trying to stop the

subscriber.

Severity: 20 : Error

BIP0941 The message received was incorrectly

formed.

Severity: 20 : Error

BIP0942 The connection to the QueueManager

was closed.

Severity: 20 : Error

BIP0943 Error creating the connection to

WebSphere MQ.

Severity: 20 : Error

BIP0944 Failed to create Coordinate publisher.

Severity: 20 : Error

BIP0945 Failed to create Clear screen publisher.

Severity: 20 : Error

BIP0946 Exception when closing connection to

broker.

Severity: 20 : Error

BIP0947 Error on publishing clear message.

Severity: 20 : Error

BIP0948 Error on publishing coordinate message.

Severity: 20 : Error

BIP0949 WebSphere MQ error getting message

from Queue.

Severity: 20 : Error

BIP0950 SCRIBBLE has a WebSphere MQ

connection message.

Severity: 0 : Information

BIP0951 SCRIBBLE has got a subscribe message.

Severity: 0 : Information

BIP0952 SCRIBBLE subscriber has started

receiving messages.

Severity: 0 : Information

BIP0954 Cannot create image with specified file

name.

Severity: 20 : Error

Explanation: An image cannot be created from

specified image file <insert_0>.

The file may not exist or has not a valid JPG or GIF

format.

Response: Verify that file exists and is valid, then

retry the operation.

BIP0955 Compile a broker archive file from

source.

Severity: 0 : Information

Explanation: Syntax: mqsicreatebar -data workspace -b

barName [-version id] [-esql21]

t[-p projectName [...]] -o filePath1 [filePath2 [...]]

Command Options:

’-data workspace’ workspace location (Mandatory)

’-b barName’ bar file name to create or replace

’-version id’ appends ’_’ and id to compiled names in

the archive (optional)

’-esql21’ compile ESQL for brokers version 2.1

(optional)

’-p projectName’ specify projects containing files to link

(optional, multiple

tprojects can be specified)

’-o filePath1’ workspace relative path (including the

project) of deployable

tfiles to add to the broker archive. Multiple deployable

files can be compiled

tin a single mqsicreatebar command.

BIP0001 to BIP1007 (Message Broker Toolkit) 25

BIP0956 Unable to start mqsicreatebar.

Severity: 20 : Error

Explanation: No parameters were supplied to the

mqsicreatebar command.

BIP0957 Incorrect arguments supplied to

mqsicreatebar.

Severity: 20 : Error

Explanation: You must supply the ″-b <barName>″

parameter.

BIP0958 Nothing to do in mqsicreatebar.

Severity: 20 : Error

Explanation: You must supply the workspace-relative

path of the msgflow or messagset.mset

to compile using the -o parameter.

BIP0959 Incorrect arguments supplied to

mqsicreatebar.

Severity: 20 : Error

Explanation: Project name is not valid.

BIP0960 Incorrect ″-p″ or ″-o″ argument supplied

to mqsicreatebar.

Severity: 20 : Error

Explanation: Project directory <insert_0> does not

exist.

BIP0961 Error opening workspace in

mqsicreatebar.

Severity: 20 : Error

Explanation: Project could not be created for directory

<insert_0>.″

The reason given was:

<insert_1>

BIP0962 Error opening workspace in

mqsicreatebar.

Severity: 20 : Error

Explanation: Project <insert_0> could not be opened.

The reason given was:

<insert_1>

BIP0963 Error saving file in mqsicreatebar.

Severity: 20 : Error

Explanation: The file <insert_0> could not be saved to

disk.

The reason given was:

<insert_1>

BIP0964 Incorrect ″-o or -p″ argument supplied to

mqsicreatebar.

Severity: 20 : Error

Explanation: File <insert_0> does not exist.

BIP0965 Error compiling files in mqsicreatebar.

Severity: 20 : Error

Explanation: The message is:

<insert_0>

BIP0967 No more handles available to display

image.

Severity: 20 : Error

Explanation: The Operating System cannot allocate

new graphical objects

because it has reached its maximum number of

handles.

Close then reopen the workbench and try again.

BIP0968 A Database node has been substituted

for a DataInsert node.

Severity: 0 : Information

Explanation: The DataInsert node is now developed

using the mapping editor.

It no longer hosts hand coded ESQL statements.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

BIP0969 A Database node has been substituted

for a DataUpdate node.

Severity: 0 : Information

Explanation: The DataUpdate node is now developed

using the mapping editor.

It no longer hosts hand coded ESQL statements.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

BIP0970 A Database node has been substituted

for a DataDelete node.

Severity: 0 : Information

Explanation: The DataDelete node is now developed

using the mapping editor.

It no longer hosts hand coded ESQL statements.

Message flow name being migrated: <insert_0>

Message processing node name: <insert_1>

26 Diagnostic messages

BIP0971 Cannot open ESQL module <insert_0>

Severity: 20 : Error

Explanation: The reference to module <insert_0> is

ambiguous.

A module with the same name may exist in the same

schema in a referenced project.

Response: Rename one of the modules and try the

operation again.

BIP0972 Incorrect arguments supplied to

mqsimigratemsgflows.

Severity: 20 : Error

Explanation: If you specify -log you must supply the

name of a report file.

BIP0973 Unable to delete existing project

<insert_0>.

Severity: 20 : Error

Explanation: The specified project could not be

deleted.

Specify a non-existing project with a valid name.

BIP0974 Invalid ’esql’ protocol URL parsed

Severity: 20 : Error

Explanation: The invalid ’esql’ protocol URL is

<insert_0>.

BIP0975 A resource could not be found.

Severity: 20 : Error

Explanation: A <insert_0> exception occurred which

reported the following message: <insert_1>

Response: The ESQL or Mapping file path length may

exceed 256 characters which may not be supported by

the file system.

To overcome this situation, keep install path, project

names, broker schema names, and message flow names

reasonably short.

BIP0976 Property name collision has been

detected.

Severity: 20 : Error

Explanation: A property with the name <insert_0>

appears more than once in the flow <insert_1>.

The flow has not been corrected by the migration tool.

You must later correct the flow manually.

BIP0977 The WebSphere MQ classes for Java

could not be found.

Severity: 20 : Error

Explanation: The WebSphere MQ classes for Java

must be installed to use the enqueue editor to send

messages.

Response: If this package is installed check and see if

the following environment variable is set:

Windows: PATH=<install directory>\lib

Linux: LD_LIBRARY_PATH=/opt/mqm/java/lib

BIP0978 The WebSphere MQ classes for Java

could not be found.

Severity: 20 : Error

Explanation: The WebSphere MQ classes for Java

must be installed to get messages using the dequeue

dialog.

Response: If this package is installed check and see if

the following environment variable is set:

Windows: PATH=<install directory>\lib

Linux: LD_LIBRARY_PATH=/opt/mqm/java/lib

BIP0979 Read a broker archive file.

Severity: 0 : Information

Explanation: Syntax: mqsireadbar -b <full path to bar

file>

BIP0980 Unable to read broker archive file.

Severity: 20 : Error

Explanation: File <insert_0> does not exist.

BIP0981 Incorrect arguments supplied to

mqsireadbar.

Severity: 20 : Error

Explanation: You must supply the ″-b <full path to

bar file>″ parameter.

BIP0982 Unable to start mqsireadbar.

Severity: 20 : Error

Explanation: No parameters were supplied to the

mqsireadbar command.

BIP0983 Unable to read broker archive file.

Severity: 20 : Error

Explanation: The message is:

<insert_0>

BIP0001 to BIP1007 (Message Broker Toolkit) 27

BIP0985 Error storing incrementally compiled

ESQL.

Severity: 20 : Error

Explanation: The ESQL content associated with

<insert_0> could not

be saved.

BIP0986 Command completed successfully.

Severity: 0 : Information

BIP0987 A failure response has been received

from Configuration Manager on

<insert_0>.

Severity: 20 : Error

Explanation: A failure response has been received

which provided the message(s) detailed below.

BIP0988 Error occurred while completing

mqsicreatebar command.

Severity: 10 : Warning

BIP0989 Incorrect ″-o″ argument supplied to

mqsicreatebar.

Severity: 20 : Error

Explanation: File <insert_0> cannot be added because

it does not contain a valid file extension.

BIP0990 Incorrect arguments supplied to

mqsimigratemsgflows.

Severity: 20 : Error

Explanation: You must supply -data <workspace>.

BIP0991 A failure response has been received

from Configuration Manager on

<insert_0>.

Severity: 20 : Error

Explanation: A failure response has been received

which provided the message(s) detailed below.

Response: Resolve the reason of error and try again.

BIP0992 Cannot add drag and drop resource

<insert_0>

Severity: 20 : Error

Explanation: The file <insert_0> cannot be found.

The file may exist in a project that is not referenced.

Response: Add the project containing the resource as

a referenced project and try the operation again.

BIP0993 Cannot add drag and drop resource

<insert_0>

Severity: 20 : Error

Explanation: The reference to file <insert_0> is

ambiguous.

A file with the same name may exist in the same

schema in a referenced project.

Response: Rename one of the files and try the

operation again.

BIP0994 Cannot update flow node <insert_0>

Severity: 20 : Error

Explanation: The file <insert_0> cannot be found.

The file may exist in a project that is not referenced.

Response: Add the project containing the resource as

a referenced project and try the operation again.

BIP1000 Apply override values in broker archive

file.

Severity: 0 : Information

Explanation: Syntax: mqsiapplybaroverride -b <full

path to bar file> -p <full path to override properties

file>

BIP1001 Unable to start mqsiapplybaroverride.

Severity: 20 : Error

Explanation: No parameters were supplied to the

mqsiapplybaroverride command.

BIP1002 Incorrect arguments supplied to

mqsiapplybaroverride command.

Severity: 20 : Error

Explanation: You must supply the ″-b <full path to

bar file>″ parameter.

BIP1003 Incorrect arguments supplied to

mqsiapplybaroverride command.

Severity: 20 : Error

Explanation: You must supply the ″-p <full path to

override properties file>″ parameter.

BIP1004 Unable to read broker archive file.

Severity: 20 : Error

Explanation: File <insert_0> does not exist.

28 Diagnostic messages

BIP1005 Unable to read properties file.

Severity: 20 : Error

Explanation: File <insert_0> does not exist.

BIP1006 Error applying override values in

mqsiapplybaroverride.

Severity: 20 : Error

Explanation: The message is:

<insert_0>

BIP1007 Error saving file in

mqsiapplybaroverride.

Severity: 20 : Error

Explanation: The file <insert_0> could not be saved to

disk.

The reason given was:

<insert_1>

BIP0001 to BIP1007 (Message Broker Toolkit) 29

30 Diagnostic messages

BIP1000 to BIP1999 (Configuration Manager)

BIP1001 Message associated with number <insert_0> was not found: data supplied <insert_1>.

Severity: 30 : Severe error

Explanation: A message number was used for which no associated message text could be found.

Response: This is an internal error. Contact your IBM support center.

BIP1002 Unexpected exception in ConfigurationManager class <insert_1> method; exception text: <insert_0>,

<insert_2>.

Severity: 30 : Severe error

Explanation: An exception was caught by the ConfigurationManager class <insert_1> method while the

Configuration Manager was being started or stopped. The exception text is: <insert_0>, <insert_2>.

Response: Retry the operation. If the exception still occurs, contact your IBM support center.

BIP1003 The Configuration Manager is available for use.

Severity: 0 : Information

Explanation: The Configuration Manager has started successfully.

Response: No user action required.

BIP1004 The Configuration Manager is not available for use.

Severity: 30 : Severe error

Explanation: A problem has been encountered while trying to start the Configuration Manager. The problem is not

expected to be transient.

Response: Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the

Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start

the Configuration Manager again. If the problem persists contact your IBM support center.

BIP1005 The Configuration Manager is no longer available for use.

Severity: 20 : Error

Explanation: The Configuration Manager has encountered a situation where it is unable to continue processing.

However, the situation is expected to be transient and the Configuration Manager will automatically attempt to

restart after a short delay.

Response: Look at previous error messages for the Configuration Manager in the event log. Determine and correct

the cause of the problem if necessary.

BIP1006 The Configuration Manager is no longer available for use.

Severity: 30 : Severe error

Explanation: The Configuration Manager has encountered a situation where it is unable to continue. The problem is

not expected to be transient.

Response: Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the

Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start

the Configuration Manager again.

BIP1007 The Configuration Manager is not available for use.

Severity: 20 : Error

Explanation: A problem has been encountered while trying to start the Configuration Manager. However the

problem is expected to be transient and the Configuration Manager will automatically attempt to restart after a short

delay.

Response: Look at previous error messages for the Configuration Manager in the event log. Determine and correct

the cause of the problem if necessary. If the problem persists contact your IBM support center.

BIP1008 Unable to locate file <insert_0>.

Severity: 30 : Severe error

Explanation: A file required by the Configuration Manager could not be found. This may be the result of an

inconsistent installation of the Configuration Manager.

Response: Ensure that the file exists in the WebSphere Message Brokers directory. Check that the file permissions

are such that the file is readable. Retry the operation. If this is still not successful, contact your IBM support center.

BIP1009 Trace level not restored due to invalid trace level <insert_0> in repository.

Severity: 10 : Warning

Explanation: An invalid trace level <insert_0> was found in the configuration repository while attempting to restore

the trace level to a previously saved level. The Configuration Manager will continue but trace will not be active.

Response: If you need to run with Configuration Manager trace active, use the mqsichangetrace command utility to

set the desired trace level. If this problem persists contact your IBM support center.

BIP1010 Trace level not preserved due to invalid trace level <insert_0>.

Severity: 10 : Warning

Explanation: An invalid trace level <insert_0> was encountered while attempting to save the trace level in the

configuration repository. The Configuration Manager will continue, but the trace level has not been saved so a

subsequent restart may not trace at the correct level.

Response: This is an internal error. Contact your IBM support center.

BIP1011 Trace level <insert_0> successfully restored.

Severity: 0 : Information

Explanation: A trace level of <insert_0> has been restored from the configuration repository. The Configuration

Manager is now running with trace active at level <insert_0>.

Response: No user action required.

BIP1012 Unexpected exception creating or deleting Configuration Manager in ConfigurationData class

<insert_0> method; exception text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the ConfigurationData class <insert_0> method while the Configuration

Manager was being created or deleted. The exception text is: <insert_1>.

Response: Retry the operation. If the exception still occurs, contact your IBM support center.

BIP1013 Unexpected exception in Configuration Manager PersistentTrace class <insert_1> method; exception

text: <insert_0>, <insert_2>.

Severity: 30 : Severe error

Explanation: While restoring or preserving the trace level in the configuration repository, an exception was caught

32 Diagnostic messages

by the PersistentTrace class <insert_1> method. The exception text is: <insert_0>, <insert_2>.

Response: This is an internal error. Contact your IBM support center.

BIP1015 External exception.

Severity: 20 : Error

Explanation: The Configuration Manager attempted to use the services of an external component, but the

component failed with the following error: <insert_0>

Response: Contact your IBM support center.

BIP1016 Failed to initiate deploy.

Severity: 30 : Severe error

Explanation: The requested deploy operation failed to initiate.

Response: Check there are no existing deploy requests still outstanding then reissue the command.

BIP1017 A backup archive called <insert_0> was created successfully.

Severity: 0 : Information

BIP1018 Unexpected exception in utility <insert_0>; method <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the <insert_0> utility in method <insert_1>. The exception text is:

<insert_2>. The current operation will end.

Response: For XML parser errors check the XML is well-formed and the correct encoding is specified.

Retry the operation if possible. If the exception still occurs, contact your IBM support center.

BIP1019 Message flow <insert_0> could not be found.

Severity: 20 : Error

Explanation: The utility was asked to start or stop a named message flow <insert_0>, but this is not deployed to

execution group <insert_1> on broker <insert_2>.

Response: Check that the (case-sensitive) message flow name has been entered correctly. Use the Broker

Administration perspective of the Message Brokers Toolkit or the Config Manager Proxy to ensure that the message

flow has been deployed successfully.

BIP1020 Message flow <insert_0> could not be started.

Severity: 20 : Error

Explanation: The utility was asked to start message flow <insert_0> running in execution group <insert_1> on

broker <insert_2>, but the action did not complete successfully.

Response: Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user

has the authority defined in the Configuration Manager to control message flows on that execution group. If you

suspect that the run state is not being reported correctly, try redeploying the topology using the ’complete’ option. If

the problem persists, contact your IBM support representative.

BIP1021 Message flow <insert_0> could not be stopped.

Severity: 20 : Error

Explanation: The utility was asked to stop message flow <insert_0> running in execution group <insert_1> on broker

<insert_2>, but the action did not complete successfully.

Response: Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user

BIP1000 to BIP1999 (Configuration Manager) 33

has the authority defined in the Configuration Manager to control message flows on that execution group. If you

suspect that the run state is not being reported correctly, try redeploying the topology using the ’complete’ option. If

the problem persists, contact your IBM support representative.

BIP1022 At least one message flow could not be started.

Severity: 20 : Error

Explanation: The following message flows were not reported as running by the time a timeout occurred: <insert_0>.

The following message flows were reported as running: <insert_1>.

Response: Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user

has the authority defined in the Configuration Manager to control message flows on that execution group and broker.

If you suspect that the run state is not being reported correctly, try redeploying the topology using the ’complete’

option. If the problem persists, contact your IBM support representative.

BIP1023 At least one message flow could not be stopped.

Severity: 20 : Error

Explanation: The following message flows were not reported as stopped by the time a timeout occurred: <insert_1>.

The following message flows were reported as having stopped successfully: <insert_0>.

Response: Ensure that the broker <insert_2> and the Configuration Manager are running and that the current user

has the authority defined in the Configuration Manager to control message flows on that execution group and broker.

If you suspect that the run state is not being reported correctly, try redeploying the topology using the ’complete’

option. If the problem persists, contact your IBM support representative.

BIP1024 Starts message flows.

Syntax:

mqsistartmsgflow (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-e

executionGroupName [-m flowName]] [-w timeoutValue] [-v traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-n cfgParameterFileName’ File containing Configuration Manager connection parameters (.configmgr)

’-i ipAddress’ IP address or host name of the Configuration Manager

’-p port’ port number of the Configuration Manager

’-q qMgr’ queue manager of the Configuration Manager

’-b brokerName’ name of the broker on which to start message flows

’-e executionGroupName’ name of the execution group on which to start message flows. If this is not specified, all

message flows on the broker will be started.

’-m flowName’ name of the message flow to start. If this is not specified, all message flows on the execution group

will be started.

’-w timeoutValue’ time to wait (in seconds) for message flows to start (Default=60)

’-v traceFileName’ send verbose internal trace to the specified file.

BIP1025 Stops message flows.

Syntax:

mqsistopmsgflow (-n cfgFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-e egName [-m

flowName]] [-w timeout] [-v traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-n cfgFileName’ Configuration Manager connection file (.configmgr)

’-i ipAddress’ IP address or host name of the Configuration Manager

’-p port’ port number of the Configuration Manager

’-q qMgr’ queue manager of the Configuration Manager

’-b brokerName’ name of the broker on which to stop message flows

’-e egName’ name of the execution group on which to stop message flows. If this is not specified, all message flows

on the broker will be stopped.

34 Diagnostic messages

’-m flowName’ name of the message flow to stop. If this is not specified, all message flows on the execution group or

broker will be stopped.

’-w timeout’ time to wait (in seconds) for message flows to stop (default=60)

’-v traceFileName’ send verbose internal trace to the specified file

BIP1026 Deploying configuration information to broker <insert_0>...

Severity: 0 : Information

BIP1027 Submitting request to the Configuration Manager to start <insert_0>...

Severity: 0 : Information

BIP1028 Submitting request to the Configuration Manager to stop <insert_0>...

Severity: 0 : Information

BIP1029 Waiting up to <insert_1> second(s) for broker <insert_0> to update its configuration...

Severity: 0 : Information

BIP1030 Message flow <insert_0> is reported as started.

Severity: 0 : Information

BIP1031 Message flow <insert_0> is reported as stopped.

Severity: 0 : Information

BIP1032 Deploys pub/sub topology, topics or BAR file configuration data to the specified broker(s).

Syntax:

mqsideploy.bat (-connection cfgParameterFileName | (-i ipAddress -p port -q qMgr)) ((-b

brokerName [([-e executionGroupName ((-bar BARFileName [-complete]) | -rm deployedObjects)]) |

-cancel]) | (-topology [-complete]) | (-topics [-complete]) | -cancel) [-w timeoutValue] [-v

traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-connection cfgParameterFileName’ Configuration Manager connection parameters (.configmgr)

’-i ipAddress’ ip address of Configuration Manager.

’-p port’ port number of Configuration Manager.

’-q queueManager’ queue manager of Configuration Manager.

’-b brokerName’ name of broker to deploy to.

’-e executionGroupName’ name of execution group to deploy to.

’-bar BARFileName’ deploy the specified Broker Archive file.

’-rm deployedObjects’ colon separated list of deployed objects to remove from the execution group.

’-cancel’ tells the Configuration Manager to stop waiting for broker responses to currently outstanding deploy

requests, across the domain or on the specified broker. Use this flag with caution; any subsequent responses to

cancelled deploys will be ignored by the Configuration Manager, meaning that the status reported by the

Configuration Manager may be incorrect.

’-topology’ deploy pub/sub neighbor configuration to all brokers.

’-topics’ deploy topics hierarchy to all brokers.

’-complete’ clear existing data before deployment (vs. deploy incremental changes).

’-w timeoutValue’ value in seconds to wait for responses.

’-v traceFileName’ send verbose internal trace to the specified file.

BIP1000 to BIP1999 (Configuration Manager) 35

BIP1033 Invalid parameters.

Severity: 20 : Error

Explanation: The specified flags are invalid or cannot be used together: <insert_0>.

Response: Reissue the command specifying valid options and flags.

BIP1034 Properties file could not be read

Severity: 20 : Error

Explanation: A Configuration Manager Proxy application was asked to read connection parameters from the

properties file <insert_0> but this could not be found or was found to be invalid.

Response: Reissue the command specifying a valid path and file name. If such a file is not available, Use the

Message Brokers Toolkit to generate one, or supply the Configuration Manager connection parameters individually.

BIP1035 Property missing from properties file.

Severity: 30 : Severe error

Explanation: Property <insert_0> was not found in the properties file <insert_1>.

Response: Reissue the command making sure a valid <insert_1> properties file is in the current directory.

BIP1036 Configuration Manager port is not a number.

Severity: 30 : Severe error

Explanation: The Configuration Manager port value (<insert_0>) is not valid port number. This must be an integer

value.

Response: Retry the command specifying a valid port number in the configuration or properties file.

BIP1037 Broker not found.

Severity: 30 : Severe error

Explanation: Broker <insert_0> was not found in the Configuration Manager repository.

Response: Reissue the command specifying an existing broker.

BIP1038 Execution group not found.

Severity: 30 : Severe error

Explanation: Either the execution group <insert_0> was not found in the Configuration Manager repository for

broker <insert_1>, or you do not have the required permissions to view it.

Response: Reissue the command specifying a valid execution group to which you have access.

BIP1039 Deploying BAR file <insert_2> to broker <insert_0> (execution group <insert_1>) ...

Severity: 0 : Information

BIP1040 Waiting <insert_0> second(s) for reply to deploy request for deploy Id <insert_1> ...

Severity: 0 : Information

BIP1041 Configuration Manager connection parameters could not be found

Severity: 20 : Error

Explanation: A Configuration Manager Proxy application could not connect to a Configuration Manager because no

connection parameters were provided. Furthermore, no default connection parameters could be determined.

36 Diagnostic messages

Response: Reissue the command, specifying a valid set of Configuration Manager connection parameters.

BIP1042 Timeout waiting for reply to deploy request (deploy id <insert_0>).

Severity: 0 : Information

BIP1043 No previous deploy request files found to resolve (file extension <insert_0>).

Severity: 0 : Information

BIP1044 Connecting to the Configuration Manager’s queue manager...

Severity: 0 : Information

BIP1045 Connecting to the Configuration Manager...

Severity: 0 : Information

BIP1046 Unable to connect with the Configuration Manager (<insert_0>).

Severity: 20 : Error

Explanation: The utility encountered a problem while attempting to connect to the Configuration Manager’s queue

manager to put a message to its request queue.

Response: Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the

Configuration Manager’s queue manager is running and that the current user is able to put messages to its

SYSTEM.BROKER.CONFIG.QUEUE. If this error text includes an MQ reason code, look up the meaning behind the

error in the Application Programming Reference guide and proceed as appropriate.

BIP1047 The operation could not be completed by the Configuration Manager.

Severity: 20 : Error

Explanation: The utility did not receive an expected message from the Configuration Manager within a reasonable

amount of time. The cause is described as: <insert_0>

Response: Ensure that the Configuration Manager is running and that the correct connection parameters have been

supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.

BIP1055 Deploying pub/sub neighbors (topology) configuration...

Severity: 0 : Information

BIP1056 Cancelling all outstanding deploy requests ...

Severity: 0 : Information

BIP1057 Deploying topics hierarchy...

Severity: 0 : Information

BIP1058 The Configuration Manager supplied the following message(s):

Severity: 0 : Information

BIP1059 Please use the Event Log Viewer to view the output of previous deploys.

Severity: 0 : Information

Explanation: The -r flag has been removed from the mqsideploy utility.

Response: Consult the Configuration Manager’s event log in order to view the results of previous deployment. This

BIP1000 to BIP1999 (Configuration Manager) 37

can be done using the Event Log Viewer of the Message Brokers Toolkit or programmatically using the LogProxy

class in the Config Manager Proxy. Increasing the value of the timeout period (-w) on the deployment will allow the

utility to wait for a longer period of time for broker responses.

BIP1062 Removing the following objects from execution group <insert_1>:

<insert_0>

Severity: 0 : Information

BIP1063 Objects with the following name(s) could not be found on <insert_1>:

<insert_0>

Severity: 10 : Warning

BIP1064 Removing message set <insert_0> from execution group <insert_1> ...

Severity: 0 : Information

BIP1065 The CLASSPATH is incorrectly configured

Severity: 30 : Severe error

Explanation: The utility was unable to start because a required set of Java classes could not be loaded from the

CLASSPATH (<insert_0>).

Response: Add <insert_1> (from the installed product’s classes directory) to the CLASSPATH environment variable

and reissue the command.

BIP1070 The file <insert_0> cannot be found or is not a valid Configuration Manager archive.

Severity: 30 : Severe error

Explanation: Reissue the command specifying a valid path and file name for the archive.

BIP1071 The specified archive <insert_0> already exists.

Severity: 30 : Severe error

Explanation: Reissue the command specifying a different archive name for the backup.

BIP1072 The internal repository for Configuration Manager <insert_0> cannot be accessed.

Severity: 30 : Severe error

Explanation: Make sure the Configuration Manager is not running then reissue the command.

BIP1073 Creates a backup archive of the specified Configuration Manager’s repository.

Syntax:

mqsibackupconfigmgr configMgrName -d archiveDirectory [-a archiveName] [-w workPath]

Severity: 0 : Information

Explanation: Command Options:

’configMgrName’ name of Configuration Manager to backup.

’-d archiveDirectory’ name of the directory the backup archive will be written to.

’-a archiveName’ name of the archive

’-w workPath’ work path for the Configuration Manager repository

38 Diagnostic messages

BIP1074 Source and target directories are the same!

Severity: 30 : Severe error

Explanation: The Configuration data repository directory <insert_0> is the same as the backup directory.

Response: Reissue the command specifying a different backup directory.

BIP1075 Creating backup archive for Configuration Manager <insert_0> in directory <insert_1> ...

Severity: 0 : Information

BIP1076 Failed to backup the Configuration Manager <insert_0>

Severity: 30 : Severe error

Explanation: At least one file in the Configuration Manager’s repository could not be backed up.

Response: Check user access to the backup or restore directory and reissue the command. If this problem persists

contact your IBM support center.

BIP1077 Failed to find a valid Configuration data respository for <insert_0>

Severity: 30 : Severe error

Explanation: The Configuration data repository for Configuration Manager <insert_0> is either missing or invalid.

Response: Reissue the command specifying a valid Configuration Manager.

BIP1078 Restores a configuration data backup archive for the specified Configuration Manager.

Syntax:

mqsirestoreconfigmgr configMgrName -d archiveDirectory -a archiveName [-w workPath]

Severity: 0 : Information

Explanation: Command Options:

’configMgrName’ name of the Configuration Manager that will have its repository overwritten

’-d archiveDirectory’ name of the directory the archive will be read from

’-a archiveName’ name of the archive to restore

’-w workPath’ work path for the Configuration Manager repository

BIP1079 Replacing repository for <insert_0> with archive <insert_1>...

Severity: 0 : Information

BIP1080 The Configuration Manager is not running.

Severity: 0 : Information

Explanation: The <insert_0> command attempted to contact the Configuration Manager, but failed because the

Configuration Manager is not currently running.

Response: Ensure that the Configuration Manager has been started using the mqsistart command.

BIP1081 The Configuration Manager encountered an unexpected error.

Severity: 0 : Information

Explanation: An unexpected exception was returned whilst communicating with the Configuration Manager.

Response: Check the previous entries in the error log to determine the cause of the problem.

BIP1000 to BIP1999 (Configuration Manager) 39

BIP1082 The mqsideploy utility is deploying a BAR file using a v5.x Configuration Manager. If the BAR file

contains JAR files or XSL Stylesheets, they will not be deployed. Also, if any files in the BAR file

contain embedded keywords, this information will not be extracted.

Severity: 0 : Information

Explanation: If you wish to deploy JAR files or XSL Stylesheets, or if you wish to reveal embedded version

information, reissue the command specifying the location of a higher version Configuration Manager.

BIP1083 The Configuration Manager <insert_0> received a CMP request from user <insert_1> (Proxy session

ID=<insert_2>, type=<insert_3>).

Severity: 0 : Information

Explanation: No user action is required.

BIP1084 The Configuration Manager <insert_0> responded to the CMP request from user <insert_1> (Proxy

session ID=<insert_2>, <insert_3> request elements successful).

Severity: 0 : Information

Explanation: No user action is required.

BIP1085 The Configuration Manager <insert_0> published changes to <insert_1> with UUID <insert_2> to

CMP with session ID <insert_3>.

Severity: 0 : Information

Explanation: No user action is required.

BIP1086 The Configuration Manager <insert_0> sent a deploy message to broker <insert_1> (<insert_2>).

Severity: 0 : Information

Explanation: No user action is required.

BIP1087 The Configuration Manager <insert_0> received a deploy response from broker <insert_1>

(<insert_2>).

Severity: 0 : Information

Explanation: No user action is required.

BIP1088 The Configuration Manager <insert_0> received a publication from broker <insert_1> (<insert_2>).

Severity: 0 : Information

Explanation: No user action is required.

BIP1089 Ignoring the following name(s) as they are ambiguous on <insert_1>:

<insert_0>

Severity: 10 : Warning

BIP1090 Cancelling outstanding deploys on broker <insert_0>...

Severity: 0 : Information

BIP1092 Broker <insert_0> successfully processed the deployment request.

Severity: 0 : Information

40 Diagnostic messages

BIP1093 Broker <insert_0> reported the following error(s):

Severity: 20 : Error

BIP1094 Deployment to broker <insert_0> was not required because its configuration was already up-to-date.

Severity: 0 : Information

BIP1095 The Configuration Manager has not yet responded to the deployment request.

Severity: 10 : Warning

Explanation: The Configuration Manager did not respond to the deployment request within a reasonable amount of

time. The request is queued for processing and will be completed when the Configuration Manager is able to do so.

Response: Ensure that the Configuration Manager is running. It is not usually necessary to repeat the deployment

action once the Configuration manager is started. Increasing the value of the timeout period (-w) will allow the

utility to wait for a longer period of time for Configuration Manager responses.

BIP1096 No broker responses have been received yet.

Severity: 10 : Warning

Explanation: The Configuration Manager initiated the deployment but no broker responses were received within a

reasonable amount of time. The request is queued for processing at the broker(s) and will be completed when it is

possible to do so.

Response: Ensure that the affected set of brokers is running. It is not usually necessary to repeat the deployment

action once the set of brokers is started. Increasing the value of the timeout period (-w) will allow the utility to wait

for a longer period of time for broker responses.

BIP1097 Some, but not all broker responses have been received yet.

Severity: 10 : Warning

Explanation: The Configuration Manager initiated the deployment but at least one broker did not respond to the

request within a reasonable amount of time. The request is queued for processing at the affected broker(s) and will

be completed when it is possible to do so. At this time, no brokers have rejected the deployment.

Response: Following this message is the set of broker responses received by the Configuration Manager. Ensure that

the affected set of brokers is running. It is not usually necessary to repeat the deployment action once the set of

brokers is started. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of

time for broker responses.

BIP1098 At least one failure response has been received.

Severity: 20 : Error

Explanation: The deployment request was sent to the Configuration Manager but at least one component rejected

the deployment.

Response: Following this message is the set of responses for each component. Review the errors to discover the

cause of the problem.

BIP1099 Deployment completed successfully.

Severity: 0 : Information

Explanation: All brokers affected by the deployment request have successfully processed the message and have

updated their configurations accordingly.

BIP1000 to BIP1999 (Configuration Manager) 41

BIP1100 Broker <insert_0> had not responded before the timeout occurred.

Severity: 20 : Error

BIP1101 Unknown WebSphere MQ queue manager name <insert_0>.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager during Configuration Manager startup, the

name supplied is not that of a queue manager known to WebSphere MQ.

Response: The most likely situation is that the queue manager specified on the mqsicreateconfigmgr command -q

option has been deleted. You must delete the Configuration Manager using the mqsideleteconfigmgr command, then

recreate it using mqsicreateconfigmgr, ensuring that the -q option is specified correctly. To preserve your

configuration data in the configuration repository and message repository, do not specify the -n and -m flags on the

mqsideleteconfigmgr command. Note also that WebSphere MQ queue manager names are case-sensitive. For more

information on this error see the WebSphere MQ Application Programming Reference manual, code 2058.

BIP1102 The WebSphere MQ queue manager <insert_0> is not currently available.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager during Configuration Manager startup, queue

manager <insert_0> is not up and running. This is expected to be a transient situation and the Configuration

Manager will restart after a short interval.

Response: Start the WebSphere MQ queue manager and its associated listener. For more information on this error

see the WebSphere MQ Application Programming Reference manual, codes 2059, 2161, and 2162.

BIP1103 WebSphere MQ queue manager <insert_0> no longer available.

Severity: 30 : Severe error

Explanation: The Configuration Manager’s connections to WebSphere MQ queue manager <insert_0>, and its

associated listener, have been lost. This is expected to be a transient situation and the Configuration Manager will

stop then restart after a short interval.

Response: Restart the WebSphere MQ queue manager. For more information on this error see the WebSphere MQ

Application Programming Reference manual, codes 2009, 2161, and 2162.

BIP1104 An authorization error occurred when the Configuration Manager accessed WebSphere MQ object

<insert_0>.

Severity: 30 : Severe error

Explanation: WebSphere MQ has raised an authorization exception while connecting to the WebSphere MQ queue

manager, or opening one of the WebSphere MQ queues used by the Configuration Manager. The name of the

WebSphere MQ object in question is <insert_0>.

Response: Check that the user name passed as the ServiceUserId argument to the mqsicreateconfigmgr utility

program is authorized to connect to WebSphere MQ and access the necessary queues. See the WebSphere MQ

Message Brokers online documentation, section ’Setting Up Security’ for guidance. You may also find help in the

WebSphere MQ Application Programming Reference manual, codes 2035 and 2063.

BIP1105 Unknown WebSphere MQ queue name <insert_0> .

Severity: 30 : Severe error

Explanation: When opening the WebSphere MQ queues used by the Configuration Manager, the name supplied is

not that of a queue known to WebSphere MQ queue manager.

Response: Check that the WebSphere MQ queue manager you specified has a definition for queue <insert_0>. Check

that you are using the correct queue manager, as the mqsicreateconfigmgr command creates the required WebSphere

MQ queues automatically. Note that WebSphere MQ queue names are case-sensitive. For more information on this

error see the WebSphere MQ Application Programming Reference manual, code 2085.

42 Diagnostic messages

BIP1106 WebSphere MQ error detected, reason code <insert_0>.

Severity: 30 : Severe error

Explanation: An error has occurred while making a WebSphere MQ call from the Configuration Manager. The

WebSphere MQ reason code is <insert_0>. The Configuration Manager will continue processing if it is possible to do

so.

Response: For more information on this error see the WebSphere MQ Messages manual or WebSphere MQ Online

Help, code <insert_0>.

BIP1107 Unexpected exception in Configuration Manager MQProcessor class <insert_1> method; exception

text: <insert_0>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager MQProcessor class <insert_1> method. The

exception text is: <insert_0>. The Configuration Manager will continue processing if it is safe to do so.

Response: Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to

capture details of the exception, and contact your IBM support center.

BIP1109 WebSphere MQ error writing to dead letter queue, reason code <insert_0>.

Severity: 30 : Severe error

Explanation: An error occurred while the Configuration Manager was putting a message on the dead letter queue.

The WebSphere MQ reason code is <insert_0>. A previous message will indicate the reason why the message was put

to the dead letter queue in the first place.

Response: For more information on this error see the WebSphere MQ Application Programming Reference manual,

code <insert_0>.

BIP1110 Unrecognized WebSphere MQ message received by the Configuration Manager on input queue

<insert_1>; reason code <insert_0>.

Severity: 10 : Warning

Explanation: A message was received by the Configuration Manager on input queue <insert_1>, but the message

could not be processed. The WebSphere MQ ReasonCode is <insert_0>. The message has been written to the

WebSphere MQ dead letter queue.

Response: Look at the message on the dead-letter queue to establish which application sent the message and what

is wrong with it. For more information on this error see the WebSphere MQ Application Programming Reference

manual, code <insert_0>.

BIP1111 java.lang.OutOfMemoryError in Configuration Manager MQProcessor class <insert_0> method.

Severity: 20 : Error

Explanation: A java.lang.OutOfMemoryError was caught by the Configuration Manager MQProcessor class

<insert_0> method. This means the Java Virtual Machine has exhausted its available memory heap.

Response: Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java

Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the

WebSphere Message Brokers online documentation for guidance. Then restart the Configuration Manager and retry

the operation. Repeat if necessary until the error no longer occurs.

BIP1112 Unexpected exception in Configuration Manager RegistrationHandler class <insert_1> method;

exception text: <insert_0>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager RegistrationHandler class <insert_1> method.

The exception text is: <insert_0>. The Configuration Manager will continue processing if it is safe to do so.

BIP1000 to BIP1999 (Configuration Manager) 43

Response: Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to

capture details of the exception, and contact your IBM support center.

BIP1113 The utility could not open file <insert_0> for writing trace output.

Severity: 10 : Warning

Explanation: An attempt was made to open the file <insert_0> so that internal utility trace could be written there,

but this was not successful.

Response: If the file already exists, ensure that it is not locked or in use by another application, and that the current

user can write to it. If the file does not exist, ensure that the current user has the authority to write to the specified

directory. Try specifying a different filename. If the problem persists, please contact your IBM support center.

BIP1121 Creates an execution group.

Syntax:

mqsicreateexecutiongroup (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b

brokerName -e executionGroupName [-l] [-w timeoutValue] [-v traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-n cfgParameterFileName’ Configuration Manager connection parameters (.configmgr)

’-i ipAddress’ IP address or host name of the Configuration Manager

’-p port’ port number of the Configuration Manager

’-q qMgr’ queue manager of the Configuration Manager

’-b brokerName’ name of the broker on which to create the execution group

’-e executionGroupName’ name of the new execution group

’-l’ creates a 64-bit execution-group.

’-w timeoutValue’ time to wait (in seconds) for the execution group to be created (default=60)

’-v traceFileName’ send verbose internal trace to the specified file.

BIP1122 Deletes an execution group.

Syntax:

mqsideleteexecutiongroup (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b

brokerName -e executionGroupName [-w timeoutValue] [-v traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-n cfgParameterFileName’ Configuration Manager connection parameters (.configmgr)

’-i ipAddress’ IP address or host name of the Configuration Manager

’-p port’ port number of the Configuration Manager

’-q qMgr’ queue manager of the Configuration Manager

’-b brokerName’ name of the broker on which the execution group resides

’-e executionGroupName’ name of the execution group to delete

’-w timeoutValue’ time to wait (in seconds) for the execution group to be deleted (default=60)

’-v traceFileName’ send verbose internal trace to the specified file.

BIP1123 The execution group already exists.

Severity: 20 : Error

Explanation: The utility was asked to create execution group <insert_1> on broker <insert_0>, but it already exists.

Response: Check that the names of the execution group and broker are correct and reissue the command.

BIP1124 Creating execution group <insert_1> on broker <insert_0>...

Severity: 0 : Information

44 Diagnostic messages

BIP1125 The execution group could not be created.

Severity: 20 : Error

Explanation: The utility was asked to create execution group <insert_1> on broker <insert_0>, but it was not

completed successfully by the Configuration Manager. The Configuration Manager reported the following error(s):

<insert_2>

Response: Determine the cause of the problem by reviewing the error messages. If the problem persists, contact

your IBM support representative.

BIP1126 The execution group was created successfully.

Severity: 0 : Information

Explanation: The Configuration Manager will ask the broker to initialize the execution group when a resource is

deployed to it.

BIP1127 This command will implicitly remove all resource(s) deployed to the execution group: <insert_0>

Severity: 0 : Information

BIP1128 Deleting the execution group <insert_0> from the Configuration Manager’s repository...

Severity: 0 : Information

BIP1129 The execution group could not be deleted.

Severity: 20 : Error

Explanation: The utility was asked to delete execution group <insert_1> on broker <insert_0>, but it was not

completed successfully by the Configuration Manager. The Configuration Manager reported the following error(s):

<insert_2>

Response: Determine the cause of the problem by reviewing the error messages. If the problem persists, contact

your IBM support representative.

BIP1130 Deleting the execution group from the Configuration Manager’s repository and from broker

<insert_0>...

Severity: 0 : Information

BIP1131 The execution group was deleted successfully from the Configuration Manager’s repository. It was

not necessary to deploy these changes to broker <insert_0>.

Severity: 0 : Information

Explanation: The new configuration was not deployed because the execution group had never been initialized on

the broker.

BIP1132 Access denied

Severity: 20 : Error

Explanation: You do not have the appropriate level of authority defined in the Configuration Manager’s access

control table in order to complete the specified operation. (<insert_0>)

Response: Consult your domain administrator.

BIP1000 to BIP1999 (Configuration Manager) 45

BIP1151 Unprocessable request received by the Configuration Manager; server type <insert_1> invalid for

resource type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager, but the URI identifies a target server type

(<insert_1>) which is not valid for resource type <insert_0>.

Response: If the request did not originate from the Message Brokers Toolkit, correct the application issuing the

request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on

Configuration Manager tracing to capture details of the request, and contact your IBM support center.

BIP1152 Internal error in the Configuration Manager; resource type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager but an internal inconsistency has been detected

within the Configuration manager code. The target resource type is <insert_0>.

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the

operation and contact your IBM support center.

BIP1153 Unprocessable request received by the Configuration Manager; URI is <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager, but the URI contains two items of metadata

following the first ’?’. A maximum of one item of metadata may be specified on a URI, and so a URI may only

contain zero or one ’?’ characters. The URI in question is <insert_0>.

Response: If the request did not originate from the Message Brokers Toolkit, correct the application issuing the

request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on

Configuration Manager tracing to capture details of the request, and contact your IBM support center.

BIP1154 Unprocessable request received by the Configuration Manager; <insert_1> operation not permitted

for resource type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager, but a <insert_1> operation is never permitted

for target resource type <insert_0>.

Response: If the request did not originate from the Message Brokers Toolkit, correct the application issuing the

request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on

Configuration Manager tracing to capture details of the request, and contact your IBM support center.

BIP1155 Internal error in the Configuration Manager; resource type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager but the URI identifies a target resource type

<insert_0> for which no corresponding RoleManager object type can be found.

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the

operation and contact your IBM support center.

BIP1156 Internal error within the Configuration Manager; server type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager but the URI identifies a target server type

(<insert_0>) for which no corresponding RoleManager server type can be found.

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the error. Retry the

operation and contact your IBM support center.

46 Diagnostic messages

BIP1157 The properties for the target resource cannot be located.

Severity: 30 : Severe error

Explanation: The resource has been located in the repository, but no associated properties XML can be found. This

means no label and icon information is available for the resource.

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the exception. Retry

the operation and contact your IBM support center.

BIP1158 Unprocessable request received by the Configuration Manager; resource type <insert_0>.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager but the URI identifies target resource type

<insert_0> for which the Configuration Manager is not configured.

Response: If the request did not originate from the Message Brokers Toolkit, correct the application issuing the

request. Otherwise retry the operation from the Message Brokers Toolkit. If the exception still occurs, turn on

Configuration Manager tracing to capture details of the request, and contact your IBM support center.

BIP1159 Broker <insert_0> has a blank queue manager name.

Severity: 20 : Error

Explanation: An attempt was made to create or modify a broker with no associated WebSphere MQ queue manager

name. This is a mandatory property. The broker name is <insert_0>.

Response: Provide a queue manager name for the broker and retry the operation. If the problem persists, contact

your IBM support center.

BIP1160 Duplicate name <insert_1> for <insert_0> within configuration repository.

Severity: 20 : Error

Explanation: An error occurred when attempting to save <insert_0> <insert_1> to the configuration repository

because another <insert_0> already exists with the same name.

Response: Rename the <insert_0> and retry the operation.

BIP1161 Unable to locate WebSphere MQ Java classes.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager at Configuration Manager startup, the

WebSphere MQ Java classes could not be located.

Response: Ensure that the required level of WebSphere MQ Java classes are installed and have been correctly added

to the CLASSPATH. Different versions of WebSphere MQ Java classes require different entries in the CLASSPATH (in

particular version 5.21 of MA88 requires connector.jar to be identified in the CLASSPATH). You should consult the

documentation provided with your version of WebSphere MQ Java classes for information on what is required in the

CLASSPATH for that version. You may need a restart of your machine in order that any alterations to the

CLASSPATH are picked up by the Service Control Manager which is used in starting the Configuration Manager.

Ensure that the userid under which the Configuration Manager is running has the correct authorities (on some

platforms this means adding your user id to the mqm and Administrators groups). Ensure that WebSphere MQ

classes for Java libraries (for example on Windows mqjbnd04.dll) are available via the PATH. Ensure that WebSphere

MQ classes for Java jar files (for example com.ibm.mq.jar) are available via the CLASSPATH.

BIP1162 Unprocessable registration request received by the Configuration Manager.

Severity: 30 : Severe error

Explanation: A request was received by the Configuration Manager to register for updates to the resource <insert_0>

, but an exception was thrown while processing this request (<insert_1>).

Response: Restart the connection to the Configuration Manager and retry the operation. If the exception still occurs,

BIP1000 to BIP1999 (Configuration Manager) 47

turn on Configuration Manager tracing to capture details of the request and contact your IBM support center.

BIP1163 Unprocessable request received by the Configuration Manager.

Severity: 30 : Severe error

Explanation: A serialized request was received by the Configuration Manager, but the message was not in a

recognized object format. The request was serialized as a <insert_0>.

Response: Correct the application that issued the request so that it serializes using the correct object type and

format. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request and

contact your IBM support center.

BIP1164 Unprocessable request received by the Configuration Manager.

Severity: 30 : Severe error

Explanation: A serialized request was received by the Configuration Manager, but the message was malformed. The

following exception was thrown: <insert_0>.

Response: Correct the application that issued the request so that it serializes using the correct format. If the

exception still occurs, turn on Configuration Manager tracing to capture details of the request and contact your IBM

support center.

BIP1165 Unexpected exception creating or deleting security ACL Information in ConfigurationACLGroup

class <insert_0> method; exception text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the ConfigurationACLGroup class <insert_0> method while the ACL

security information was being created or deleted. The exception text is: <insert_1>.

Response: Retry the operation. If the exception still occurs, contact your IBM support center.

BIP1170 Failed to restore the repository for the Configuration Manager <insert_0>.

Severity: 30 : Severe error

Explanation: At least one file in the Configuration Manager’s repository could not be restored. The restore operation

was rolled back and the Configuration Manager is in the state it was in before the restore command was issued.

Response: Check that the Configuration Manager is not running, and that the file specified is a valid Configuration

Manager archive. Check that the current user has authority to read the archive and write to the directory described

by the work path. If this problem persists contact your IBM support center.

BIP1171 Verifying the restored repository...

Severity: 0 : Information

BIP1172 The database is invalid (<insert_0>)

Severity: 30 : Severe error

BIP1173 The Configuration Manager could not initialize because a required service is not available.

Severity: 30 : Severe error

Explanation: The Configuration Manager was unable to initialize because either the machine does not have a local

IP address or an MD5 cryptography service is not available.

Response: Ensure that the machine has a local IP address and that cryptography services are enabled, then retry the

operation. If the exception still occurs, contact your IBM support center.

48 Diagnostic messages

BIP1201 Unknown or unsupported database of type <insert_0>.

Severity: 30 : Severe error

Explanation: While attempting to determine the type of database being used for the configuration repository, the

database type <insert_0> was returned. This is an unknown or unsupported database.

Response: This is an internal error. Contact your IBM support center.

BIP1202 Unexpected exception in the Configuration Manager DBManager class <insert_1> method; exception

text: <insert_0>, <insert_2>.

Severity: 30 : Severe error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager DBManager class <insert_1> method. The database operation did not complete successfully.

The exception text is: <insert_0>, <insert_2>.

Response: The exception text may indicate that a Java class could not be found; check that the system CLASSPATH

variable contains the correct classes. If the problem persists please contact your IBM support center.

BIP1203 Unknown database column type <insert_0>.

Severity: 30 : Severe error

Explanation: While attempting to construct the database tables for the configuration repository, a column type of

<insert_0> was found. This is an unknown column type. The database tables have not been constructed successfully.

Response: This is an internal error. Contact your IBM support center.

BIP1204 Unable to locate required <insert_0> <insert_1> in directory <insert_2>.

Severity: 30 : Severe error

Explanation: While attempting to prime the database tables for the configuration repository, a file or directory was

either not found or could not be read. This may be the result of an inconsistent installation. The database tables have

not been primed successfully.

Response: Ensure that the file or directory exists in the WebSphere Message Brokers <insert_2> directory. Check that

the permissions are such that the file or directory is readable. Retry the mqsicreateconfigmgr command. If this is still

not successful, contact your IBM support center.

BIP1205 Unexpected exception accessing configuration repository; exception text: <insert_1>.

Severity: 20 : Error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager. The database operation did not complete successfully. If this message was issued by the

Configuration Manager, then it will continue if it is safe to do so. The exception text is: <insert_1>.

Response: If this problem persists contact your IBM support center.

BIP1206 Database not running; exception text: <insert_0>.

Severity: 20 : Error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager. This was because the database is not up and running. The database operation did not

complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to

do so. The exception text is: <insert_0>.

Response: If this problem persists contact your IBM support center.

BIP1000 to BIP1999 (Configuration Manager) 49

BIP1207 Database <insert_0> not found; exception text: <insert_1>.

Severity: 20 : Error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager. This was because the database name <insert_0> is not recognized and the database cannot be

found. The database operation did not complete successfully. The exception text is: <insert_1>.

Response: If this problem persists contact your IBM support center.

BIP1208 Database product name cannot be found: object <insert_0> is null.

Severity: 30 : Severe error

Explanation: A problem was encountered while attempting to get information from the configuration repository

database manager. The <insert_0> object is null.

Response: This is an internal error. Contact your IBM support center.

BIP1209 The userid and/or password are not authorized for connection to the configuration repository

<insert_0>.

Severity: 20 : Error

Explanation: When starting or creating or deleting the Configuration Manager, the configuration repository database

<insert_0> could not be opened because the userid and/or password is not authorized.

Response: This error is most probably a result of either incorrect userid and password being provided for the -u

and -p options on the mqsicreateconfigmgr command, or the userid not having been assigned access rights to the

configuration repository database by the database management system. First check that the access rights have been

correctly configured. Then, if necessary, delete your Configuration Manager (using the mqsideleteconfigmgr

command) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command) with the

correct options. To preserve your configuration data in the configuration repository and message repository, do not

specify the -n and -m flags on the mqsideleteconfigmgr command.

BIP1210 Missing or blank configuration repository JDBC driver name.

Severity: 30 : Severe error

Explanation: The configuration repository JDBC driver name supplied to the Configuration Manager is either blank

or is missing. This is a mandatory property of the Configuration Manager.

Response: This is an internal error. Contact your IBM support center.

BIP1211 Missing or blank configuration repository JDBC connection name.

Severity: 30 : Severe error

Explanation: The configuration repository JDBC connection name supplied to the Configuration Manager is either

blank or is missing. This is a mandatory property of the Configuration Manager.

Response: This is an internal error. Contact your IBM support center.

BIP1213 User <insert_0> is not allowed to unlock resource locked by user <insert_1>.

Severity: 30 : Severe error

Explanation: An attempt has been made to unlock a resource in the configuration repository, but the principal

supplied with the unlock request (<insert_0>) does not match the principal associated with the locked resource

(<insert_1>).

Response: The resource was locked by a different user. You cannot unlock a resource for which you do not own the

lock.

50 Diagnostic messages

BIP1214 Cannot unlock resource with lock token <insert_0> as the resource is not locked.

Severity: 30 : Severe error

Explanation: An attempt has been made to unlock a resource in the configuration repository, but the lock token

supplied with the unlock request (<insert_0>) does not exist in the configuration repository, implying that the

resource is not locked.

Response: The resource has already been unlocked. You can not unlock a resource for which no lock exists.

BIP1215 Invalid configuration repository table name <insert_0> detected by Configuration Manager

DBManager class <insert_1> method.

Severity: 30 : Severe error

Explanation: The Configuration Manager DBManager class <insert_1> method has detected an unknown table name

<insert_0> when processing a request against the configuration repository.

Response: This is an internal error. Contact your IBM support center.

BIP1216 Can not update resource <insert_0> which is not locked.

Severity: 30 : Severe error

Explanation: An attempt has been made to update an existing resource <insert_0> in the configuration repository

but the resource has not been locked.

Response: You must first lock a resource before you update it.

BIP1217 Referenced <insert_1> not found, (UUID <insert_0>).

Severity: 20 : Error

Explanation: A referenced <insert_1> has not been found in the configuration repository.

Response: It is possible the parent of the <insert_1> written to the repository but the <insert_1> itself has not.

Alternatively, the referenced <insert_1> may have been deleted. If this problem persists contact your IBM support

center.

BIP1221 Found invalid Configuration Manager Database for migration!

Severity: 20 : Error

Explanation: The Configuration Manager Database specified for migration did not contain a complete set of valid

tables. A new empty internal respository has been created instead.

Response: It is possible the wrong database has been specified for migration. If this is the case, please delete and

recreate the Configuration Manager specifying the correct database. If no migration is needed no further action is

required.

BIP1222 Using internal Configuration respository

Severity: 10 : Warning

Explanation: The Configuration Manager is connecting to its internal repository.

Response: No action.

BIP1223 Attempting to open and migrate DB2 database <insert_0>...

Severity: 0 : Information

BIP1000 to BIP1999 (Configuration Manager) 51

BIP1224 Migrating from DB2 Database: <insert_0>

Severity: 0 : Information

Explanation: Migrating from DB2 Database <insert_0> to the Configuration internal repository.

Response: No action.

BIP1225 Database migration failed

Severity: 30 : Severe error

Explanation: Migration from DB2 Database <insert_0> to the Configuration internal repository failed.

Response: See previous messages for details. Contact your IBM support center if the problem persists.

BIP1226 Configuration data already migrated

Severity: 10 : Warning

Explanation: The Configuration Manager internal repository indicates data migration has already taken place.

Response: No action.

BIP1227 Failed to find internal respository!

Severity: 30 : Severe error

Explanation: The Configuration Manager failed to find its internal repository. A new, empty one has been created.

This is a non-destructive action.

Response: Stop the Configuration Manager and restore the repository from a previous backup. Contact your IBM

support center if the problem persists.

BIP1228 The Configuration Manager repository has been successfully created.

Severity: 0 : Information

BIP1229 Failed to migrate table: <insert_1>

Severity: 30 : Severe error

Explanation: The Configuration Manager failed to read UUID <insert_0> from table <insert_1> while migrating

configuration data.

Response: This is an internal error. Contact your IBM support center if the problem persists.

BIP1230 The Configuration Manager’s repository is not available for use.

Severity: 30 : Severe error

Explanation: The Configuration Manager was not able to gain exclusive access to its internal repository. Either

another process already has exclusive access to the repository (for example, if another instance of the Configuration

Manager is running), or the user ID under which the Configuration Manager was started does not have the required

authority to access the repository.

Response: Ensure that the Configuration Manager is not already running, and that no other process is running that

may have acquired exclusive access to the repository. Also, ensure that the Configuration Manager’s user ID has the

required authority to access the database; the user at least needs to be a member of the mqm and mqbrkrs groups,

and on Windows the user also needs to be in the Administrators group.

52 Diagnostic messages

BIP1301 Invalid call to Configuration Manager PrincipalsManager class <insert_0> method.

Severity: 30 : Severe error

Explanation: An invalid method call was made to the Configuration Manager PrincipalsManager class <insert_0>

method.

Response: This is an internal error. Contact your IBM support center.

BIP1302 Unexpected exception in Configuration Manager PrincipalsManager class makeTXDoc method;

exception text: UnsupportedEncodingException, character set <insert_0>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager PrincipalsManager class makeTXDoc method

when constructing an XML document. The exception text is: UnsupportedEncodingException, character set

<insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1303 Unexpected exception in Configuration Manager PrincipalsManager class <insert_0> method;

exception text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager PrincipalsManager class <insert_0> method.

The exception text is: <insert_1>.

Response: Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details

of the exception, and contact your IBM support center.

BIP1304 Error accessing User Name Server from Configuration Manager PrincipalsManager class <insert_0>

method; exception text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager PrincipalsManager class <insert_0> method

whilst getting information from the User Name Server UGRegistry client. The exception text is: <insert_1>.

Response: Check preceding log entries for related errors and retry the operation. If the exception still occurs, restart

the Configuration Manager, then retry the operation again. If the exception still occurs, turn on Configuration

Manager tracing to capture details of the exception, and contact your IBM support center.

BIP1305 Invalid call to Configuration Manager PrincipalsManager class <insert_0> method; Section parameter

value <insert_1> encountered.

Severity: 30 : Severe error

Explanation: An attempt was made by the Configuration Manager to call the PrincipalsManager class <insert_0>

method using value <insert_1> for the Section parameter. Only a value of SHARED is supported.

Response: This is an internal error. Contact your IBM support center.

BIP1306 Invalid call to Configuration Manager PrincipalsManager class <insert_0> method; Container

parameter value <insert_1> encountered.

Severity: 30 : Severe error

Explanation: An attempt was made by the Configuration Manager to call the PrincipalsManager class <insert_0>

method using value <insert_1> for the Container parameter. Only values of USER, GROUP and PUBLICGROUP are

supported.

Response: This is an internal error. Contact your IBM support center.

BIP1000 to BIP1999 (Configuration Manager) 53

BIP1350 The current operation has timed out.

Severity: 20 : Error

Explanation: One or more requests have been sent to the Configuration Manager to process the current operation,

but no reply has been received for the last request sent.

Response: Either your request has queued up behind a long-running request by another user, or the Configuration

Manager has stopped. Check that it is up and running then retry the operation. Because the link to the Configuration

Manager is via WebSphere MQ, it is important to note that the original operation may have fully completed, or have

partly completed, even though no reply was received in the allotted time. The results of the retried operation should

indicate this, and will determine subsequent actions.

BIP1351 WebSphere MQ queue manager <insert_0> unknown on host system <insert_1>.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager, the name supplied is not that of a queue

manager known to WebSphere MQ on host system <insert_1>. The Message Brokers Toolkit is unable to communicate

with the Configuration Manager.

Response: Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box

has been correctly specified, and that a WebSphere MQ queue manager with the required name exists on the

specified host system. Note that WebSphere MQ queue manager names are case-sensitive. For more information on

this error see the WebSphere MQ Application Programming Reference manual, code 2058.

BIP1352 WebSphere MQ queue manager <insert_0> on host system <insert_1> not available.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager, queue manager <insert_0> is not up and

running and listening for input on host system <insert_1>. The Message Brokers Toolkit is unable to communicate

with the Configuration Manager.

Response: Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box

has been correctly specified. Start the WebSphere MQ queue manager if it is not running. Ensure that the WebSphere

MQ listener is running and listening on the correct port, that only one listener is listening on that port. Ensure that

WebSphere MQ server connection channel SYSTEM.BKR.CONFIG is defined to the queue manager. For more

information on this error see the WebSphere MQ Application Programming Reference manual, codes 2059, 2161, 2162,

and 2009.

BIP1353 WebSphere MQ queue manager <insert_0> no longer available.

Severity: 30 : Severe error

Explanation: The Message Brokers Toolkit’s connection to WebSphere MQ queue manager <insert_0> has been lost.

The Message Brokers Toolkit is unable to communicate with the Configuration Manager.

Response: Restart the WebSphere MQ queue manager and the WebSphere MQ listener. If necessary also restart the

Configuration Manager. For more information on this error see the WebSphere MQ Application Programming

Reference manual, codes 2009, 2161 and 2162.

BIP1355 Unknown WebSphere MQ queue name <insert_0> .

Severity: 30 : Severe error

Explanation: When opening the WebSphere MQ queues used by the Message Brokers Toolkit, the name supplied is

not that of a queue known to the WebSphere MQ queue manager. The Message Brokers Toolkit is unable to

communicate with the Configuration Manager.

Response: Check that the queue manager name entered in the Message Brokers Toolkit File->Connection dialog box

has been correctly specified. Also check that it is associated with the Configuration Manager, and that it has a

definition for queue <insert_0>. Note that WebSphere MQ queue and queue manager names are case-sensitive. For

more information on this error see the WebSphere MQ Application Programming Reference manual, code 2085.

54 Diagnostic messages

BIP1356 WebSphere MQ error detected, reason code <insert_0>.

Severity: 30 : Severe error

Explanation: An error has occurred while making a WebSphere MQ call from the Message Brokers Toolkit. The

WebSphere MQ reason code is <insert_0>.

Response: For more information on this error see the WebSphere MQ Application Programming Reference manual,

code <insert_0>.

BIP1357 Unrecognized reply received from the Configuration Manager.

Severity: 20 : Error

Explanation: A request has been sent to the Configuration Manager to process the current operation, but the reply

received back is not one recognized by the Message Brokers Toolkit.

Response: The most likely cause is that another WebSphere MQ application is erroneously processing messages on

SYSTEM.BROKER.CONFIG.QUEUE. Check that the Configuration Manager is up and running and is the only

WebSphere MQ application processing messages on the queue. If no other application can be identified and the

problem persists, contact your IBM support center.

BIP1358 Unexpected exception in Message Brokers Toolkit <insert_1> class <insert_2> method; exception text:

<insert_0>, <insert_3>.

Severity: 30 : Severe error

Explanation: An exception was caught by the <insert_1> class <insert_2> method when the Message Brokers Toolkit

was communicating with the Configuration Manager. The exception text is: <insert_0>, <insert_3>.

Response: Retry the operation. If the exception still occurs, restart the Message Brokers Toolkit, then retry the

operation again. If the exception still occurs, turn on Message Brokers Toolkit tracing to capture details of the

exception, and contact your IBM support center.

BIP1359 The connection to WebSphere MQ queue manager <insert_0> has been lost.

Severity: 30 : Severe error

Explanation: When communicating with WebSphere MQ, queue manager <insert_0> is no longer up and running

and listening for input. The Message Brokers Toolkit is unable to communicate with the Configuration Manager.

Response: Restart the WebSphere MQ queue manager if it is not running. Ensure that the WebSphere MQ listener is

running and listening on the correct port, that only one listener is listening on that port. For more information on this

error see the WebSphere MQ Application Programming Reference manual, codes 2161, 2162, and 2009.

BIP1360 Configuration Manager is not at the required software level.

Severity: 20 : Error

Explanation: A request was sent to the Configuration Manager to process the current operation, but the reply

received back indicates that the Configuration Manager is not at a sufficient level to recognize requests of that

command level.

Response: The Message Brokers Toolkit or Config Manager Proxy application has been upgraded to the latest

product level, but a similar upgrade has not been made to the Configuration Manager. This is an incompatible

combination of software; either upgrade the Configuration Manager to the same level as the Message Brokers Toolkit

and Config Manager Proxy, or connect to a different Configuration Manager.

BIP1361 Unable to locate WebSphere MQ Java classes.

Severity: 30 : Severe error

Explanation: When connecting to the WebSphere MQ queue manager at Configuration Manager startup, the

WebSphere MQ Java classes could not be located. All Message Brokers Toolkit and Config Manager Proxy

applications will be unable to communicate with the Configuration Manager.

BIP1000 to BIP1999 (Configuration Manager) 55

Response: Ensure that the required level of WebSphere MQ Java classes are installed and have been correctly added

to the classpath. You must also ensure that the userid under which you are running has permission to access the

directory where the WebSphere MQ Java classes are installed (on some platforms this may mean adding your user id

to the Administrators group).

BIP1362 Unable to locate WebSphere security exit class.

Severity: 30 : Severe error

Explanation: When a Message Brokers Toolkit or Config Manager Proxy application attempted to connect to the

WebSphere queue manager, the WebSphere security exit class <insert_0> could not be located. The application is

unable to communicate with the Configuration Manager with the desired level of security.

Response: Ensure that the WebSphere security exit class <insert_0> exists in the specified location, and that the

current user has authority to load it.

BIP1363 A problem was encountered while configuring WebSphere MQ security exit class <insert_1>;

exception text: <insert_0>.

Severity: 30 : Severe error

Explanation: The Message Brokers Toolkit or Config Manager Proxy application could not configure user-supplied

class <insert_1> for use as a WebSphere MQ security exit. The exception text is: <insert_0>. The Message Brokers

Toolkit is unable to communicate with the Configuration Manager with the desired level of security.

Response: Check that the CLASSPATH system environment variable contains the jar files for any classes that are

used by the security exit. Ensure that the security exit implements the WebSphere MQ MQSecurityExit interface and

is correctly coded. For a complete description of how to implement a WebSphere MQ security exit for the WebSphere

MQ Java Client please refer to WebSphere MQ documentation.

BIP1401 Invalid call to Configuration Manager MRMManager class <insert_0> method.

Severity: 30 : Severe error

Explanation: An invalid method call was made to the Configuration Manager MRMManager class <insert_0>

method.

Response: This is an internal error. Contact your IBM support center.

BIP1402 Unexpected exception in Configuration Manager MRMManager class <insert_1> method; exception

text: <insert_0>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager MRMManager class <insert_1> method. The

exception text is: <insert_0>.

Response: Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details

of the exception, and contact your IBM support center.

BIP1403 Missing or blank message repository database name.

Severity: 30 : Severe error

Explanation: The message repository database name supplied to the Configuration Manager is either blank or

missing. This is a mandatory property of the Configuration Manager. The most likely cause of this is manual editing

of the registry entries created by the mqsicreateconfigmgr command.

Response: Delete the Configuration Manager using the mqsideleteconfigmgr command, without specifying the -n or

-m options. Then recreate the Configuration Manager using the mqsicreateconfigmgr command, specifying the correct

database name on the -m option. See the WebSphere Message Brokers online documentation for guidance. If the

problem persists, contact your IBM support center.

56 Diagnostic messages

BIP1404 Update or create message repository resource <insert_1> of type <insert_0> in server <insert_2> failed:

empty hashtable.

Severity: 30 : Severe error

Explanation: An empty hashtable was supplied when updating or creating resource <insert_1> of type <insert_0> in

server <insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1405 Update or create message repository resource <insert_1> of type <insert_0> in server <insert_2> failed:

no XML document.

Severity: 30 : Severe error

Explanation: No XML document was supplied when updating or creating resource <insert_1> of type <insert_0> in

server <insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1406 Unable to lock message repository resource <insert_1> of type <insert_0> in server <insert_2>: no

ActiveLock object.

Severity: 30 : Severe error

Explanation: No ActiveLock object was supplied when writing resource <insert_1> of type <insert_0> in server

<insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1407 Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: empty hashtable.

Severity: 30 : Severe error

Explanation: An empty hashtable was supplied when updating or creating the properties for resource <insert_1> of

type <insert_0> in server <insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1408 Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: no XML document.

Severity: 30 : Severe error

Explanation: No XML document was supplied when updating or creating the properties for resource <insert_1> of

type <insert_0> in server <insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1409 Unable to unlock resource <insert_1> of type <insert_0> in server <insert_2>: no ActiveLock object.

Severity: 30 : Severe error

Explanation: No ActiveLock object was supplied when writing resource <insert_1> of type <insert_0> in server

<insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1410 Update or create resource <insert_1> of type <insert_0> in server <insert_2> failed: no ActiveLock

object.

Severity: 30 : Severe error

Explanation: No ActiveLock object was supplied when updating or creating resource <insert_1> of type <insert_0>

in server <insert_2> within the message repository.

Response: This is an internal error. Contact your IBM support center.

BIP1000 to BIP1999 (Configuration Manager) 57

BIP1411 Unable to save NNSY resource to the configuration database.

Severity: 30 : Severe error

Explanation: Changes to NNSY resources cannot be performed using the Message Brokers Toolkit.

Response: The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates

to a NNSY resource, you will need to use the NNSY Formatter GUI instead.

BIP1412 Unable to save the properties for the NNSY resource to the configuration database.

Severity: 30 : Severe error

Explanation: Changes to NNSY resources cannot be performed using the Message Brokers Toolkit.

Response: The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates

to a NNSY resource, you will need to use the NNSY Formatter GUI instead.

BIP1413 Unable to lock a NNSY resource.

Severity: 30 : Severe error

Explanation: Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not

possible to put a lock on a NNSY resource.

Response: The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates

to a NNSY resource, you will need to use the NNSY Formatter GUI instead.

BIP1414 Unable to unlock a NNSY resource.

Severity: 30 : Severe error

Explanation: Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not

possible to release a lock on a NNSY resource.

Response: The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates

to a NNSY resource, you will need to use the NNSY Formatter GUI instead.

BIP1415 Unable to delete a NNSY resource.

Severity: 30 : Severe error

Explanation: Changes to NNSY resources cannot be performed using the Message Brokers Toolkit, and so it is not

possible to delete a NNSY resource.

Response: The Message Brokers Toolkit provides a read-only view of NNSY resources. In order to perform updates

to a NNSY resource, you will need to use the NNSY Formatter GUI instead.

BIP1449 Configuration Manager cannot locate one or more Java classes; exception text: <insert_0>.

Severity: 30 : Severe error

Explanation: There was an error establishing the correct Java environment for accessing the message repository.

Response: This normally indicates an inconsistent installation of the Configuration Manager. Check that

Configuration Manager has been installed correctly and that no jar files have been deleted. If the problem persists

contact your IBM support center.

BIP1450 Error loading library imbMRMInterface; error text: <insert_0>.

Severity: 30 : Severe error

Explanation: The Configuration Manager was unsuccessful when loading the imbMRMInterface library. Any error

text follows: <insert_0>.

Response: This normally indicates an inconsistent installation of the Configuration Manager. Check that the

Configuration Manager has been installed correctly and that PATH includes the directory containing the

58 Diagnostic messages

Configuration Manager libraries and executables. If the problem persists contact your IBM support center.

BIP1461 Invalid call to Configuration Manager CacheManager class <insert_0> method.

Severity: 30 : Severe error

Explanation: An invalid method call was made to the Configuration Manager CacheManager class <insert_0>

method.

Response: This is an internal error. Contact your IBM support center.

BIP1462 Unexpected exception in Configuration Manager CacheManager class <insert_1> method; exception

text: <insert_0>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager CacheManager class <insert_1> method. The

exception text is: <insert_0>.

Response: Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details

of the exception, and contact your IBM support center.

BIP1502 Unexpected exception in Configuration Manager BrokerManager class <insert_0> method; exception

text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager BrokerManager class <insert_0> method. The

exception text is: <insert_1>. The current operation will terminate.

Response: Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to

capture details of the exception and contact your IBM support center.

BIP1503 Unable to find required execution group document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for execution group <insert_0> could not be found

in the configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing deploy document is of type <insert_1>.

Response: The execution group document <insert_0> is not available. This is an internal error. Contact your IBM

support center.

BIP1504 Unknown deploy type or action type <insert_0>.

Severity: 30 : Severe error

Explanation: The Configuration Manager BrokerManager class received a request to perform the action <insert_0>.

This action is not recognized.

Response: This is an internal error. Contact your IBM support center.

BIP1505 Subscription can not be deleted.

Severity: 20 : Error

Explanation: An attempt was made to delete a subscription, but the subscription in question was created by a

WebSphere Message Brokers component for its own internal use. Such subscriptions can not be deleted.

Response: Retry the operation on a different subscription.

BIP1000 to BIP1999 (Configuration Manager) 59

BIP1506 Queue manager <insert_2> cannot be associated with broker <insert_0>; it may still be in use by

another broker <insert_1> which is pending deletion.

Severity: 20 : Error

Explanation: Broker <insert_1> has been removed from the domain of active brokers, although it may still be using

its queue manager. It is not possible to associate another broker with the queue manager until the Configuration

Manager can confirm that the first broker has tidied up its resources.

Response: After successfully removing a broker from the domain, you must initiate a deploy of the topology in

order to instruct the broker component to stop and tidy up its resources. This can be done using the Message Brokers

Toolkit, mqsideploy utility or the Configuration Manager Proxy API. Once the deploy is successful, you must delete

the broker component using the mqsideletebroker command. Only then can you associate a new broker with the

queue manager.

If the runtime broker component has already been deleted and is therefore unable to cleanly tidy up its resources,

you must purge any remaining references to the broker and its queue manager from the Configuration Manager’s

repository. To do this, either (a) make the queue manager or its SYSTEM.BROKER.ADMIN.QUEUE inaccessible to the

Configuration Manager and initiate a topology deploy, or (b) use the Configuration Manager Proxy API

TopologyProxy.removeDeletedBroker().

BIP1507 Cannot find root element <insert_0> in XML document.

Severity: 30 : Severe error

Explanation: The Configuration Manager could not find a root element named <insert_0> in the XML document it

was attempting to parse.

Response: This is an internal error. Contact your IBM support center.

BIP1508 Unexpected root element <insert_0> in XML document: root element <insert_1> expected.

Severity: 30 : Severe error

Explanation: The Configuration Manager found an unexpected root element named <insert_0> while parsing an

XML document looking for root element <insert_1>.

Response: This is an internal error. Contact your IBM support center.

BIP1509 The deployment action was not required.

Severity: 0 : Information

Explanation: The Configuration Manager was asked to initiate a deployment operation, but this was not performed

because the deployed configuration has not changed.

Response: No user action required.

BIP1510 Deployment failed; a deployment is already in progress to broker <insert_0>

Severity: 20 : Error

Explanation: The Configuration Manager was asked to deploy to broker <insert_0>, but this could not be attempted

because it has not yet received a response to a previous deployment request submitted to that broker. To ensure that

the deployed configuration is consistent with the reported configuration, the more recent deployment request has

been discarded.

Note that if you are attempting to deploy the publish/subscribe topology or topic hierarchy, no brokers in the

domain will have received the new deployment message. There can be no outstanding deploys in the domain before

deployment of such a configuration can occur.

Response: Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor or

Configuration Manager Proxy may be used to check that all responses to the outstanding deploy have been received

and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers

exist and are running, all WebSphere MQ queue managers are running, and that all channels between queue

managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have

not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then cancel the

60 Diagnostic messages

deploy operation; either (a) right-click the broker in the Message Brokers Toolkit and select the ’Cancel Deployment’

option, or (b) use mqsideploy with the -c option, or (c) use the BrokerProxy.cancelDeployment() method in a

Configuration Manager Proxy application. Note that cancelling the deployment operation does not stop the

deployment message from being processed by the broker; it simply forces the Configuration Manager to remove any

outstanding deployment locks that may be associated with the broker. If a broker subsequently processes a

deployment message that has been cancelled using this technique, the deployed configuration may become

inconsistent with the reported configuration.

BIP1511 Queue manager <insert_2> cannot be associated with broker <insert_0>; it is already associated with

broker <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to associate broker <insert_0> with WebSphere MQ queue manager <insert_2>,

but broker <insert_1> already has this association. A WebSphere MQ queue manager can only have one broker

associated with it.

Response: Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker

<insert_1> then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration

from the real broker. It is only after all types of configuration data (message flows, message sets, topology, topics)

have been successfully deleted from the real broker that the broker document is finally deleted from the

configuration repository. Until that time the queue manager can not be associated with another broker. Once this has

been done, you must also physically delete and recreate the real broker using the mqsideletebroker and

mqsicreatebroker commands.

BIP1512 No Topology document found.

Severity: 30 : Severe error

Explanation: When attempting to deploy configuration data, the Topology document could not be found in the

configuration repository.

Response: This is an internal error. Contact your IBM support center.

BIP1513 Unprocessable response received by Configuration Manager on input queue <insert_0>.

Severity: 10 : Warning

Explanation: A message was received by the Configuration Manager on input queue <insert_0>, but the message

was not a response to an outstanding broker request. This message has erroneously appeared on queue <insert_0>.

Response: The message has been written to the WebSphere MQ dead letter queue. Look at the message on the dead

letter queue to establish which application sent the message. If the message was a reply from a broker to which a

deploy was subsequently cancelled, then it can be safely ignored. Otherwise correct the application.

BIP1514 Unprocessable publication received by Configuration Manager on input queue <insert_0>.

Severity: 10 : Warning

Explanation: A publication was received by the Configuration Manager on input queue <insert_0>, but the

publication matches no topic to which the Configuration Manager has subscribed. The publication has been written

to the WebSphere MQ dead letter queue.

Response: Look at the message on the dead letter queue to establish the application that created the subscription,

and why it was published on the <insert_0> queue. Correct the application.

BIP1515 Unable to find deploying broker data: UUID of broker is <insert_0>

Severity: 30 : Severe error

Explanation: The Configuration Manager received a response message from a broker that matches an outstanding

broker request, but can find no record in the configuration repository of the broker in question. The UUID of the

broker is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1000 to BIP1999 (Configuration Manager) 61

BIP1516 Unable to process XML document in message from broker <insert_1>: no <insert_0> element could be

found.

Severity: 30 : Severe error

Explanation: While processing a message received from broker <insert_1>, the XML document it contained was

found to be invalid. An element in the following list was expected but could not be found: <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1517 Cannot find entry in section <insert_0> of configuration repository: UUID of entry <insert_1>; table

<insert_2>.

Severity: 30 : Severe error

Explanation: A configuration repository entry could not be found. The UUID of the entry is <insert_1>, the

configuration repository table name is <insert_2> and section is <insert_0>. The configuration repository may be in an

inconsistent state.

Response: This situation should not arise under normal circumstances. Retry the operation and if the problem

persists contact your IBM support center.

BIP1518 Unexpected exception in Configuration Manager BrokerManager class purgeLogEntries method;

exception text: <insert_0>.

Severity: 10 : Warning

Explanation: An exception was caught by the Configuration Manager BrokerManager class purgeLogEntries

method. The CLOG table in the configuration repository was not cleared correctly. The exception text is: <insert_0>.

Response: This will not affect the operation of the Configuration Manager and you may continue to use it.

However, this is an internal error and you should contact your IBM support center if the problem persists.

BIP1519 Invalid topic tree found deploying topics.

Severity: 20 : Error

Explanation: When deploying topic data, the document for topic <insert_0> could not be found in the configuration

repository. The parent topic that references <insert_0> is <insert_1>.

Response: The topic document for <insert_0> has either been deleted or has not been saved to the Configuration

Manager. Correct the problem and retry the deploy operation.

BIP1520 The Configuration Manager has initiated a deployment operation.

Severity: 0 : Information

Explanation: The Configuration Manager received a request to deploy configuration data and has consequently

asked the following brokers to change their configuration: <insert_0> <insert_1>

Response: The receipt of this message does not necessarily mean that deployment was successful; view the Event

Log Editor in the Message Brokers Toolkit to check the outcome of the deployment. If you are deploying

programmatically using the Config Manager Proxy, check the returned DeployResult object or LogProxy. There will

be a separate set of log messages for each broker.

BIP1521 Start message flow operation successfully initiated for broker <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager has processed the start message flow request and initiated a start message

flow operation for the target message flows.

62 Diagnostic messages

BIP1522 Stop message flow operation successfully initiated for broker <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager has processed the stop message flow request and initiated a stop message

flow operation for the target message flows.

BIP1523 Stop trace operation successfully initiated for broker <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager has processed the stop trace request and initiated a stop trace operation

for the target resources.

BIP1524 Start trace operation successfully initiated for broker <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager has processed the start trace request and initiated a start trace operation

for the target resources.

BIP1525 Delete subscription operation successfully initiated on broker <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager has processed the delete subscription request and initiated a delete

operation for the target subscription.

Response: Consult the Event Log Editor in the Message Brokers Toolkit, or the LogProxy object in a Config

Manager Proxy application, to check the outcome of the operation.

BIP1526 Operation not initiated.

Severity: 10 : Warning

Explanation: The Configuration Manager attempted to process the request but no suitable resource was found.

Response: Check that the correct resources still exist. If the problem persists please contact your IBM support center.

BIP1527 Duplicate name <insert_1> deploying <insert_0> data.

Severity: 20 : Error

Explanation: When deploying <insert_0> data, two <insert_0>s with the same name were found in the configuration

repository. The <insert_0> name is <insert_1>. Names must be unique.

Response: Rename one of the <insert_0>s with name <insert_1>, then retry the deploy operation.

BIP1528 java.lang.OutOfMemoryError in Configuration Manager BrokerManager class <insert_0> method.

Severity: 20 : Error

Explanation: A java.lang.OutOfMemoryError was caught by the Configuration Manager BrokerManager class

<insert_0> method. This means the Java Virtual Machine has exhausted its available memory heap.

Response: Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java

Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the

WebSphere Message Brokers online documentation for guidance. Then restart the Configuration Manager and retry

the operation. Repeat if necessary until the error no longer occurs.

BIP1530 Unable to process XML document for broker <insert_1>. Attribute <insert_0> not found for element

<insert_2>.

Severity: 30 : Severe error

Explanation: While processing a message received from broker <insert_1>, the XML document it contained was

BIP1000 to BIP1999 (Configuration Manager) 63

found to be invalid. An attribute named <insert_0> could not be found for element <insert_2>.

Response: This is an internal error. Contact your IBM support center.

BIP1531 Deploy configuration failed. Message set with UUID <insert_0> returned an empty hashtable.

Severity: 30 : Severe error

Explanation: When attempting to deploy configuration data, a request to the message repository to generate the

message dictionary for a message set returned an empty hashtable. The UUID of the message set in question is

<insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1532 Deploy configuration failed processing broker data: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding broker data to the ’DPLING’ section of the

configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1533 Unable to deploy configuration data: unknown WebSphere MQ queue manager <insert_1> associated

with broker <insert_0>.

Severity: 20 : Error

Explanation: An attempt was made to deploy configuration data to one or more brokers. The WebSphere MQ queue

manager <insert_1> associated with broker <insert_0> is not known to the Configuration Manager’s WebSphere MQ

queue manager. The deploy operation was not performed.

Response: Check that the name of the queue manager is spelled correctly. Note that WebSphere MQ queue manager

names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue

manager <insert_1>, or a transmission queue called <insert_1>, is defined to the Configuration Manager’s queue

manager. For more information on this error see the WebSphere MQ Application Programming Reference manual,

code <insert_2>.

BIP1534 Unable to perform requested operation for broker <insert_0>: broker does not exist on queue

manager <insert_1>.

Severity: 10 : Warning

Explanation: An attempt was made to perform an operation against resources on broker <insert_0>, but the broker

does not exist on queue manager <insert_1>. The operation was not performed.

Response: This normally means that the broker has been prematurely deleted using the mqsideletebroker command.

Delete the broker from the configuration using the Message Brokers Toolkit or Config Manager Proxy, then redeploy

the topology to remove all traces of the broker from the configuration repository.

BIP1535 Operation not initiated: broker <insert_0> does not exist on queue manager <insert_1>.

Severity: 10 : Warning

Explanation: An attempt was made to process the request, but broker <insert_0> does not exist on queue manager

<insert_1>. The operation was not initiated.

Response: This normally means that the broker has been prematurely deleted using the mqsideletebroker command.

Delete the broker from the configuration using the Message Brokers Toolkit or Config Manager Proxy, then redeploy

the topology to remove all traces of the broker from the configuration repository.

64 Diagnostic messages

BIP1536 The Configuration Manager was unable to register for internal subscriptions with broker <insert_0>.

Severity: 30 : Severe error

Explanation: Although the preceding deploy operation was successful, a subsequent attempt by the Configuration

Manager to register for internal subscriptions with broker <insert_0> was not successful. This means that Message

Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to

broker <insert_0>.

Response: Look in the system log for messages that indicate the cause of this problem. Correct the cause and

redeploy to this broker. If this problem persists, contact your IBM support center.

BIP1537 Unable to remove configuration data from broker <insert_0>: broker no longer exists on queue

manager <insert_1>.

Severity: 10 : Warning

Explanation: Broker <insert_0> was deleted using the Message Brokers Toolkit or Config Manager Proxy, and a

deploy operation subsequently attempted to remove all configuration data. However the broker was found to no

longer exist on queue manager <insert_1>.

Response: No action is required. This message normally means that the broker been deleted using the

mqsideletebroker command.

BIP1538 Unable to deploy configuration data to broker <insert_0> on queue manager <insert_1>; WebSphere

MQ reason code <insert_2>.

Severity: 20 : Error

Explanation: An attempt was made to deploy configuration data to broker <insert_0> on queue manager <insert_1>,

but WebSphere MQ could not deliver the deploy request to the broker. The WebSphere MQ ReasonCode is

<insert_2>. No configuration data was deployed.

Response: For more information on this error refer to the WebSphere MQ Application Programming Reference

manual, code <insert_2>. Correct the problem and retry the deploy operation.

BIP1539 Unable to deploy configuration data to broker <insert_0>: broker does not exist on queue manager

<insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to deploy configuration data to broker <insert_0>, but WebSphere MQ could not

deliver the deploy request to the broker. The broker was found not to exist on queue manager <insert_1>. No

configuration data was deployed.

Response: Either the wrong WebSphere MQ queue manager has been specified for the broker, or the broker has not

been created using the mqsicreatebroker command, or the broker has been prematurely deleted using the

mqsideletebroker command. Note that WebSphere MQ queue manager names are case-sensitive. Depending on the

cause, either correct the queue manager name and redeploy, or create the broker using the mqsicreatebroker

command and redeploy. Alternatively, delete the broker from the Configuration Manager using the Message Brokers

Toolkit or Config Manager Proxy, and redeploy to remove all traces of the broker from the configuration repository.

BIP1540 Broker <insert_0> has been removed from the configuration repository.

Severity: 0 : Information

Explanation: Broker <insert_0> was deleted using the Message Brokers Toolkit or a Configuration Manager Proxy

application, and a deploy operation subsequently attempted to remove all configuration data. Either the deploy

operation succeeded, or the broker was found to no longer exist on the target queue manager, as indicated by earlier

messages. In either case, the Configuration Manager has removed all trace of the broker from the configuration

repository.

Response: No user action required.

BIP1000 to BIP1999 (Configuration Manager) 65

BIP1541 Unable to perform requested operation for broker <insert_0> on queue manager <insert_1>;

WebSphere MQ reason code <insert_2>.

Severity: 20 : Error

Explanation: An attempt was made to perform an operation against resources on broker <insert_0> on queue

manager <insert_1>, but WebSphere MQ could not deliver the operation request to the broker. The WebSphere MQ

ReasonCode is <insert_2>. No operation was performed.

Response: For more information on this error refer to the WebSphere MQ Application Programming Reference

manual, code <insert_2>. Correct the problem and retry the operation.

BIP1542 Unable to deploy configuration data.

Severity: 20 : Error

Explanation: An attempt was made to deploy configuration data to one or more brokers, but the Configuration

Manager is busy processing another deploy request. Your deploy operation was not performed.

Response: This is a transient situation. Wait for the Configuration Manager to complete its processing then retry the

operation.

BIP1543 Deploy of configuration data to broker <insert_0> not performed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a delta deploy of configuration data to broker <insert_0>, but no

changes have been made to the configuration for broker <insert_0> since the last deploy. The deploy operation for

broker <insert_0> was not performed.

Response: No user action required.

BIP1544 The NNSY Message Set cannot be deployed.

Severity: 20 : Error

Explanation: An attempt was made to deploy broker <insert_0>, but the broker has the NNSY Message Set assigned

to it.

Response: The NNSY Message Set is provided to allow users to view NNSY Formatter message/format definitions

within the Message Brokers Toolkit. It is not necessary to deploy this message set to a broker. You must unassign the

NNSY Message Set from the broker, and retry the operation.

BIP1545 Unable to find required broker document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for broker <insert_0> could not be found in the

configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing deploy document is of type <insert_1>.

Response: The broker document <insert_0> is not available. This is an internal error. Contact your IBM support

center.

BIP1546 Unable to find required broker document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for broker <insert_0> could not be found in the

configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing collective document is of type <insert_1>.

Response: The broker document <insert_0> is not available. This is an internal error. Contact your IBM support

center.

66 Diagnostic messages

BIP1547 Unable to find required mrm dictionary document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for MRM dictionary <insert_0> could not be found

in the configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing broker document is of type <insert_1>.

Response: The MRM dictionary document <insert_0> is not available. This is an internal error. Contact your IBM

support center.

BIP1548 Unable to find required collective document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for collective <insert_0> could not be found in the

configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing Topology document is of type <insert_1>.

Response: The collective document <insert_0> is not available. This is an internal error. Contact your IBM support

center.

BIP1549 Unable to find required execution group document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for execution group <insert_0> could not be found

in the configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing broker document is of type <insert_1>.

Response: The execution group document <insert_0> is not available. This is an internal error. Contact your IBM

support center.

BIP1550 Unable to find required message flow document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for message flow <insert_0> could not be found in

the configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing execution group document is of type <insert_1>.

Response: The message flow document <insert_0> is not available. This is an internal error. Contact your IBM

support center.

BIP1551 Unable to find required message set document in the configuration repository.

Severity: 20 : Error

Explanation: When deploying configuration data, the document for message set <insert_0> could not be found in

the configuration repository. Another document has referenced this document, and it is required for the successful

completion of the deploy operation. The referencing broker document is of type <insert_1>.

Response: The message set document <insert_0> is not available. This is an internal error. Contact your IBM support

center.

BIP1552 Deploy configuration failed processing execution group data: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding execution group data to the ’DPLING’ section of the

configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1000 to BIP1999 (Configuration Manager) 67

BIP1557 Deploy configuration failed processing topic data: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding topic data to the ’DPLING’ section of the

configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1558 Deploy configuration failed processing neighbor data: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding neighbor data to the ’DPLING’ section of the

configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1559 Deploy configuration failed processing outstanding reply data: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding outstanding reply data to the ’DPLING’ section of the

configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1560 Deploy configuration failed processing data of an unknown type: UUID of resource is <insert_0>.

Severity: 30 : Severe error

Explanation: An empty hash table was supplied when adding data of an unknown type to the ’DPLING’ section of

the configuration repository. The UUID of the resource in question is <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP1561 Deploy of configuration data to execution group <insert_0> not performed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a delta deploy of configuration data to execution group <insert_0>,

but no changes have been made to the configuration for execution group <insert_0> since the last deploy. The deploy

operation for execution group <insert_0> was not performed.

Response: No user action required.

BIP1562 Deploy of configuration data bar file failed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a bar file deploy. An unexpected IOException exception <insert_0>

occurred while parsing the bar file. The deploy operation was not performed.

Response: Correct the problem and retry the deploy operation.

BIP1563 Deploy of configuration data bar file failed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a bar file deploy. An unexpected SAXException exception <insert_0>

occurred while parsing the bar file. The deploy operation was not performed.

Response: Correct the problem and retry the deploy operation.

68 Diagnostic messages

BIP1564 Unable to serialize the parser tree.

Severity: 10 : Warning

Explanation: An attempt was made to serialize the parser tree built from a bar file deploy. An unexpected

IOException exception <insert_0> occurred in class <insert_1>. The deploy operation was not performed.

Response: Correct the problem and retry the deploy operation.

BIP1565 Deploy of configuration data bar file failed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a bar file deploy. An unexpected IOException exception <insert_0>

occurred in class <insert_1> while uncompressing the bar file. The deploy operation was not performed.

Response: Investigate the problem and retry the deploy operation.

BIP1566 Deploy of configuration data bar file failed.

Severity: 10 : Warning

Explanation: An attempt was made to perform a bar file deploy. An unexpected exception <insert_0> occurred in

class <insert_1> while extracting file <insert_2> from the bar file. The deploy operation was not performed.

Response: Investigate the problem and retry the deploy operation.

BIP1567 Delete subscription operation successful.

Severity: 0 : Information

Explanation: The Configuration Manager detected the subscription has already been deleted or never existed.

Response: No user action required.

BIP1568 The Configuration Manager has cancelled deployment to broker <insert_0>.

Severity: 0 : Information

Explanation: A request to cancel deployment was issued against broker <insert_0>. This was completed successfully,

and consequently the Configuration Manager has discarded any outstanding deployment records for that broker.

Furthermore, the Configuration Manager was able to remove the deployment message from the broker’s input queue

before it was processed.

It is now possible to send new deployment requests to that broker.

Response: No further action is required.

BIP1569 The Configuration Manager has removed any deployment lock associated with broker <insert_0>.

Severity: 10 : Warning

Explanation: A request to cancel deployment was issued against broker <insert_0>. This was completed successfully,

and consequently the Configuration Manager has discarded any outstanding deployment lock for that broker. It is

now possible to send new deployment requests to that broker.

However, the Configuration Manager was unable to ensure that the original deployment message cannot be

processed by the broker. If the broker has (or will) process this message and update its configuration as a result, the

Configuration Manager will no longer be able to update its records to match and the broker will become out of sync

with the Configuration Manager.

Response: If the broker is permanently unavailable, no further action is required.

If the broker may be only temporarily unavailable, you must take steps to remove the deployment message from the

broker’s input queue. Ensure that the broker is stopped and on the broker machine issue (for example) ’amqsget

SYSTEM.BROKER.ADMIN.QUEUE [qmgr]’ where [qmgr] is the name of the queue manager on which the broker is

running.

If you suspect that the broker has already processed the deployment message that has been cancelled, you must

redeploy the affected resources in order to resynchronize the Configuration Manager’s records with the broker.

BIP1000 to BIP1999 (Configuration Manager) 69

In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that the broker

can ever process the submitted deployment request.

BIP1570 The Configuration Manager has removed all deployment locks.

Severity: 10 : Warning

Explanation: A request to cancel deployment was issued against all brokers in the domain. This was completed

successfully, and consequently the Configuration Manager has discarded all outstanding deployment locks that

currently exist. It is now possible to send new deployment requests to all brokers in the domain.

However, the Configuration Manager was unable to ensure that any outstanding deployment messages cannot be

processed by the affected brokers. If these brokers have (or will) process these messages and update their

configurations as a result, the Configuration Manager will not be able to update its records to match and the brokers

will become out of sync with the Configuration Manager.

Response: If the brokers that had outstanding deploys are permanently unavailable, no further action is required.

If the brokers that had outstanding deploys may be only temporarily unavailable, you must take steps to remove the

deployment messages from the brokers’ input queues. Ensure that the brokers are stopped and on the broker

machines issue (for example) ’amqsget SYSTEM.BROKER.ADMIN.QUEUE [qmgr]’ where [qmgr] is the name of the

queue manager on which each broker is running.

If you suspect that one or more brokers have already processed a deployment message that has been cancelled, you

should redeploy the affected resources in order to resynchronize the Configuration Manager’s records with the

broker(s).

In order to prevent the situation reoccurring, ONLY cancel deployment when there is no possibility that a broker can

ever process the submitted deployment request.

BIP1571 Unable to find a required broker document in the configuration repository.

Severity: 20 : Error

Explanation: When attempting to deploy a broker archive file, the broker with unique identifier (UUID) <insert_0>

could not be found in the Configuration Manager’s repository. Either a Configuration Manager Proxy application has

recently modified the broker’s UUID, or the Configuration Manager’s repository has become corrupted. The

deployment request was not completed successfully.

Response: If a Configuration Manager Proxy application has recently modified the UUID of the broker, discard all

existing AdministeredObject handles to the broker or execution group, and reacquire them from the TopologyProxy

before attempting to deploy. If the Configuration Manager repository has become corrupted, restore the repository

from backups using the mqsirestoreconfigmgr command.

BIP1702 Unexpected exception in Configuration Manager RoleManager class <insert_1> method; exception

text: <insert_0>, <insert_2>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager RoleManager class <insert_1> method. The

exception text is: <insert_0>, <insert_2>.

Response: Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details

of the exception, and contact your IBM support center.

BIP1703 Access rights for user <insert_0> cannot be validated: parameter <insert_1> has an unrecognized

value (<insert_2>).

Severity: 30 : Severe error

Explanation: The <insert_1> parameter passed to the Configuration Manager RoleManager class validateUser

method has an unrecognized value (<insert_2>).

Response: This is an internal error. Contact your IBM support center.

70 Diagnostic messages

BIP1705 Access rights to the <insert_0> server not set up successfully by Configuration Manager

RoleManager class <insert_1> method.

Severity: 30 : Severe error

Explanation: A problem was encountered by the Configuration Manager RoleManager class <insert_1> method

while attempting to set up the access rights for the various groups.

Response: This is an internal error. Contact your IBM support center.

BIP1706 The access rights for a user cannot be validated.

Severity: 30 : Severe error

Explanation: The user parameter passed to RoleManager.validateUser() method is null and, therefore, cannot be

recognized.

Response: This is an internal error. Contact your IBM support center.

BIP1707 Unknown user encountered within the Configuration Manager.

Severity: 20 : Error

Explanation: An unknown user exception was caught by the Configuration Manager RoleManager class when

calling the UGRegistry class. The user has not been given access to the resource.

Response: Retry the operation. If the exception still occurs, turn on Configuration Manager tracing to capture details

of the exception, and contact your IBM support center.

BIP1708 Unexpected exception in the Configuration Manager RoleManager class <insert_0> method;

exception text: <insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager RoleManager class <insert_0> method when

calling the UGRegistry class. The exception text is: <insert_1>.

Response: Look at previous error messages for the Configuration Manager in the event log. Determine and correct

the cause of the problem before attempting the operation again. If the exception still occurs, turn on Configuration

Manager tracing to capture details of the exception, and contact your IBM support center.

BIP1711 The <insert_0> is not viewable by user <insert_2>

Severity: 10 : Warning

Explanation: An attempt was made to view or manipulate the <insert_0> with UUID <insert_1>, but the user who

initiated this operation does not have the required authority to do so.

Response: Ask the domain’s administrator to grant your user ID the necessary authority to perform the requested

action.

BIP1712 <insert_0> not found

Severity: 10 : Warning

Explanation: An attempt was made to view or modify the <insert_0> with UUID <insert_1>, but it does not exist in

the Configuration Manager’s repository.

Response: If you are trying to manipulate an object immediately after submitting a request to create it, it is likely

that there was a problem creating the object. An example of this is if you attempt to create a default execution group

without first ensuring that the parent broker was created successfully; this error suggests that there was a problem

creating the broker.

Check the Configuration Manager’s logs to see why the <insert_0> could not be found. If the object has previously

been available, the receipt of this error may indicate corruption in the Configuration Manager’s repository; if this is

the case, you may need to use mqsirestoreconfigmgr to restore the Configuration Manager’s repository, or if this is

not possible, contact your IBM support center for advice.

BIP1000 to BIP1999 (Configuration Manager) 71

BIP1751 Unexpected error deploying the broker topology: record for broker <insert_1> (UUID=<insert_2>)

with neighbor broker <insert_3> (UUID=<insert_4>) missing from CNEIGHBOURS table section

<insert_0>.

Severity: 30 : Severe error

Explanation: When deploying the broker topology, a record was found to be missing from the configuration

repository CNEIGHBOURS table (<insert_0> section). The record in question was for broker <insert_1>

(UUID=<insert_2>) with neighbor broker <insert_3> (UUID=<insert_4>).

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and

contact your IBM support center.

BIP1752 Unexpected error deploying configuration data: record for <insert_2> (UUID=<insert_3>) missing

from table <insert_0>, section <insert_1>.

Severity: 30 : Severe error

Explanation: When deploying configuration data, a record was found to be missing from the configuration

repository <insert_0> table (<insert_1> section). The record in question was for <insert_2> (UUID=<insert_3>).

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and

contact your IBM support center.

BIP1753 Invalid XML document found when deploying; missing <insert_0> tag.

Severity: 30 : Severe error

Explanation: When deploying configuration data, an XML document for <insert_2> <insert_1> (UUID=<insert_3>)

was retrieved from the configuration repository, but the XML document did not contain the expected <insert_0> tag

as the document element.

Response: Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the

application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the

problem, and contact your IBM support center.

BIP1754 Invalid XML document for topic <insert_0> found when deploying topics.

Severity: 30 : Severe error

Explanation: When deploying topics data, an XML document for topic <insert_0> was retrieved from the

configuration repository, but was found to be invalid. No UserRef or GroupRef element was found within one or

more TopicPolicy elements.

Response: Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the

application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the

problem, and contact your IBM support center.

BIP1755 Invalid message flow type <insert_0> when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, the document for message flow type <insert_0> was retrieved

from the configuration repository, but was found to be invalid for use as a top-level message flow type. It contains at

least one Input Terminal or Output Terminal, which is not permitted. The cause is the direct assignment to an

execution group of either one of the IBM primitive message flow types, or a user defined message flow type

containing an Input Terminal or an Output Terminal.

Response: Make sure that the only message flow types you assign to an execution group are those that do not

contain Input Terminals or Output Terminals. If <insert_0> is user defined, either remove any Input Terminals and

Output Terminals, or create a new top-level message flow type that embeds <insert_0>. Then retry the deploy

operation.

72 Diagnostic messages

BIP1756 Invalid top-level message flow type <insert_0> when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, the document for message flow type <insert_0> was retrieved

from the configuration repository, but was found to be invalid for use as a top-level message flow type. It does not

contain a reference to at least one other message flow type. The cause is the deployment to an execution group of

either one of the IBM primitive message flow types, or an empty user-defined message flow type.

Response: Make sure that the only message flow types you assign to an execution group are those that reference

other message flow types. If <insert_0> is user-defined, modify the message flow type and retry the deploy operation.

BIP1757 Invalid run-time message flow type <insert_0> when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, an XML document for message flow type <insert_0>,

(UUID=<insert_1>) was retrieved from the configuration repository, but was found to be invalid for use as a run-time

message processing node. It contains element <insert_2> which is not a permitted element in a message flow type

corresponding to a run-time message processing node.

Response: Establish the author of the message flow type. If the author is not IBM, contact the author to get the

message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to

capture details of the exception, and contact your IBM support center.

BIP1758 Invalid message flow type found when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, an attempt was made by a message flow type to override the

value of a nonexistent property of run-time message flow type <insert_1>. The property in question is <insert_0>. The

message flow type in error is the one that embeds <insert_1>, and may be identified from label <insert_2>.

Response: This is probably caused by a message flow type that corresponds to a run-time node having been

replaced by a later version with different property names. Update the message flow type in error to use the correct

property name. However if the problem persists, turn on Configuration Manager tracing to capture details of the

problem, and contact your IBM support center.

BIP1759 Invalid XML document found when deploying; missing <insert_2> element.

Severity: 30 : Severe error

Explanation: When deploying configuration data, an XML document for <insert_5>, <insert_3>, (UUID=<insert_4>)

was retrieved from the configuration repository, but was found to be invalid. The <insert_0> element, identified by

label <insert_1>, did not contain an <insert_2> element.

Response: Identify the application that created the document. If this is not the Message Brokers Toolkit, correct the

application. Otherwise this is an internal error; turn on Configuration Manager tracing to capture details of the

problem, and contact your IBM support center.

BIP1760 Invalid message flow type found when deploying message flows.

Severity: 20 : Error

Explanation: When resolving the connections between nodes in a message flow, a connection was found that could

not be resolved to Output Terminal <insert_0> in message flow type <insert_2>. The message flow type in error is the

one that embeds <insert_2>, and may be identified from label <insert_1>.

Response: The most likely cause is that <insert_0> has been modified to remove Output Terminal <insert_0>, but the

message flow type embedding <insert_2> was not modified to remove the connection to Output Terminal <insert_0>.

Ensure that all message flow types in the message flow are consistent, and retry the deploy operation.

BIP1000 to BIP1999 (Configuration Manager) 73

BIP1762 Invalid message flow type found when deploying message flows.

Severity: 20 : Error

Explanation: When resolving the connections between nodes in a message flow, a connection was found that could

not be resolved to Input Terminal <insert_0> in message flow type <insert_2>. The message flow type in error is the

one that embeds <insert_2>, and may be identified from label <insert_1>.

Response: The most likely cause is that <insert_0> has been modified to remove Input Terminal <insert_0>, but the

message flow type embedding <insert_2> was not modified to remove the connection to Input Terminal <insert_0>.

Ensure that all message flow types in the message flow are consistent, and retry the deploy operation.

BIP1764 Invalid message flow <insert_0> when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, the document for message flow <insert_0> could not be found in

the configuration repository.

Response: The message flow type document referenced by <insert_0> is not available. This is an internal error.

Contact your IBM support center.

BIP1765 Unexpected error processing a broker message: record for <insert_2> (UUID=<insert_3>) missing from

<insert_0> table, section <insert_1>.

Severity: 30 : Severe error

Explanation: When processing a response message from a broker, a record was found to be missing from the

configuration repository <insert_0> table, (<insert_1> section). The record in question was for <insert_2>

(UUID=<insert_3>).

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and

contact your IBM support center.

BIP1767 Unexpected exception in Configuration Manager ResolveXML class <insert_0> method; exception text

<insert_1>.

Severity: 30 : Severe error

Explanation: An exception was caught by the Configuration Manager ResolveXML class <insert_0> method. The

exception text is: <insert_1>.

Response: This is an internal error. Contact your IBM support center.

BIP1768 Invalid message flow type found when deploying message flows: badly formed <insert_0> attribute

value.

Severity: 30 : Severe error

Explanation: When deploying message flow data and resolving the connections between nodes, a Connection

element was found that had a badly formed <insert_0> attribute value. The ’UUID’ and ’terminal name’ components

of the value should be separated by a ’.’ character but there was no such character present.

Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and

contact your IBM support center.

BIP1769 Invalid message flow type <insert_0> deploying message flows; Input Terminal wired directly to

Output Terminal.

Severity: 20 : Error

Explanation: When deploying message flow data, the document for message flow type <insert_0> was retrieved

from the configuration repository, but was found to be invalid. It contains an Input Terminal and an Output Terminal

connected together, which is not permitted.

Response: Remove the connection between the Input Terminal and the Output Terminal. Alternatively, if ’passthru’

74 Diagnostic messages

behavior is required, insert a Check node with all checks set to ’no’, connect the Input Terminal to the Check node

’in’ terminal, and connect the Check node ’match’ terminal to the Output Terminal. Modify <insert_0> and retry the

deploy operation.

BIP1770 Invalid XML document for <insert_2> <insert_1> (UUID=<insert_3>) when processing a broker

message: missing <insert_0> tag.

Severity: 30 : Severe error

Explanation: When processing a response message received from a broker, an XML document for <insert_2>

<insert_1> (UUID=<insert_3>) was retrieved by the Configuration Manager from the configuration repository, but the

XML document did not contain the expected <insert_0> tag as the document element.

Response: This is an internal error; turn on Configuration Manager tracing to capture details of the problem, and

contact your IBM support center.

BIP1771 Invalid run-time message flow type <insert_0> when deploying message flows; no InTerminal or

OutTerminal.

Severity: 20 : Error

Explanation: When deploying message flow data, an XML document for message flow type <insert_0>

(UUID=<insert_1>) was retrieved from the configuration repository, but was found to be invalid for use as a run-time

message processing node. It does not contain an InTerminal or an OutTerminal.

Response: Establish the author of the message flow type. If the author is not IBM, contact the author to get the

message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to

capture details of the exception, and contact your IBM support center.

BIP1772 Invalid run-time message flow type <insert_0> when deploying message flows.

Severity: 20 : Error

Explanation: When deploying message flow data, an XML document for message flow type <insert_0>,

(UUID=<insert_1>), was retrieved from the configuration repository, but was found to be invalid for use as a

run-time message processing node. The value of the MessageProcessingNodeType element ’isPrimitive’ attribute is

not ’true’. Note that this error can occur if a user-defined message flow type is entirely empty or only contains

InTerminals or OutTerminals.

Response: Establish the author of the message flow type. If the author is not IBM, contact the author to get the

message flow type corrected. If the author is IBM, this is an internal error; turn on Configuration Manager tracing to

capture details of the exception, and contact your IBM support center.

BIP1773 Invalid recursive use of message flow type <insert_0> (label <insert_1>) when deploying message

flows.

Severity: 20 : Error

Explanation: When deploying message flow data, message flow type <insert_0> was found to be used recursively.

This is not permitted. The instance of this message flow type causing the problem is <insert_1>.

Response: Correct the message flow and retry the deploy operation.

BIP1775 Invalid AccessControlEntry permission <insert_0> for object type <insert_1>.

Severity: 30 : Severe error

Explanation: The Configuration Manager has been asked to create an Access Contol Entry with a permission of

<insert_0> for an object of type <insert_1>. This permission is invalid for this type.

Response: Retry the command with a valid permission for the given object type.

BIP1000 to BIP1999 (Configuration Manager) 75

BIP1776 Unexpected exception in the Configuration Manager ACLGroupEntry class <insert_1> method;

exception text: <insert_0>, <insert_2>.

Severity: 30 : Severe error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager ACLGroupEntry class <insert_1> method. The database operation did not complete

successfully. The exception text is: <insert_0>, <insert_2>.

Response: The exception text may indicate that the DB2 JDBC Driver could be found; check that the system

CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or

if the exception text indicates a different problem, please contact your IBM support center.

BIP1777 Possible database corruption found in the Configuration Manager database table <insert_0>

Severity: 30 : Severe error

Explanation: While attempting a database operation on the configuration repository, an exception was caught by the

Configuration Manager ACLGroupEntry class <insert_1> method. Possible database corruption was encountered. The

database operation did not complete successfully.

Response: The exception text may indicate that the DB2 JDBC Driver could be found; check that the system

CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or

if the exception text indicates a different problem, please contact your IBM support center.

BIP1778 <insert_0> - <insert_1> - <insert_2> - <insert_3> - <insert_4>

Severity: 0 : Information

BIP1779 Unable to validate specified user or group <insert_0>.

Severity: 20 : Error

Explanation: An unknown user or group exception was caught while attempting this operation. The user or group

<insert_0> has not been given access to the resource.

Response: Ensure that the user or group exists and is trusted by the calling domain or machine. Retry the operation.

If the exception still occurs, contact your IBM support center.

BIP1780 Unable to validate specified user <insert_0>.

Severity: 20 : Error

Explanation: User <insert_0> does not have the required authority to complete the requested operation on the

resource of type <insert_1> with UUID <insert_2>.

Response: Ensure that the user exists and has the necessary permissions to access the requested resource. Restart

the Configuration Manager and retry the operation. If the exception still occurs, contact your IBM support center.

76 Diagnostic messages

BIP2000 to BIP2999 (Broker)

BIP2001 The WebSphere Message Brokers service has started at version <insert_1>; process ID <insert_0>.

Severity: 0 : Information

Explanation: The WebSphere Message Brokers service executable has been started.

Response: No user action required.

BIP2002 The WebSphere Message Brokers service has stopped.

Severity: 10 : Warning

Explanation: The WebSphere Message Brokers service has been stopped.

Response: No user action required.

BIP2003 The WebSphere Message Brokers service has paused.

Severity: 10 : Warning

Explanation: The WebSphere Message Brokers service has paused.

Response: Restart the WebSphere Message Brokers service as soon as possible.

BIP2004 The WebSphere Message Brokers service is continuing.

Severity: 0 : Information

Explanation: The WebSphere Message Brokers service is now running.

Response: No user action required.

BIP2005 Unsuccessful WebSphere Message Brokers service initialization.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers service could not be registered.

Response: Check that the machine has adequate memory and that the userid and password used to start the broker

are correct.

BIP2006 Unable to start executable <insert_0>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers service could not start an executable.

Response: Make sure that the executable is in the correct directory and that the WebSphere Message Brokers service

userid has permission to start the executable. Ensure that there is adequate memory available on the system. Reissue

the command.

BIP2007 The WebSphere Message Brokers service has detected that its child process has ended abnormally,

process ID <insert_0>.

Severity: 20 : Error

Explanation: An executable started by the WebSphere Message Brokers service terminated abnormally.

Response: Check that the database and WebSphere are available. Determine the cause of the problem.

BIP2009 The WebSphere Message Brokers service detected an unknown serviceHandler request.

Severity: 20 : Error

Explanation: An unknown request was directed to the WebSphere Message Brokers service.

Response: Trace the problem and contact your IBM support center.

BIP2010 The WebSphere Message Brokers service has stopped, process ID <insert_0>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers service has stopped.

Response: Restart the WebSphere Message Brokers service when required.

BIP2011 The WebSphere Message Brokers service has been shutdown, process ID <insert_0>.

Severity: 10 : Warning

Explanation: The WebSphere Message Brokers service has stopped.

Response: Restart the WebSphere Message Brokers service when required.

BIP2012 Unable to access the broker’s database tables.

Severity: 20 : Error

Explanation: The broker is incorrectly configured.

Response: Check any previous messages to find the cause of the problem. Correct the problem and restart the

broker.

BIP2013 The broker was unable to access its database.

Severity: 20 : Error

Explanation: There was no running database available.

Response: Start the database, the broker will recover itself after a small delay.

BIP2014 The WebSphere Message Brokers service was unable to start executable <insert_0> due to a lack of

system storage.

Severity: 20 : Error

Explanation: The system is short on storage.

Response: Enable more system storage.

BIP2015 The WebSphere Message Brokers service detected that executable <insert_0> terminated, exit code

<insert_1>.

Severity: 20 : Error

Explanation: An executable terminated unexpectedly.

Response: The WebSphere Message Brokers service will restart the executable automatically unless the broker is

currently shutting down. Determine the reason for the unexpected termination of this executable.

BIP2025 Broker received Configuration Manager command message <insert_0>.

Severity: 0 : Information

Explanation: This message is issued when the broker receives a command request from the Configuration Manager.

Response: No user action required.

78 Diagnostic messages

BIP2026 Broker sent command <insert_0> to execution group <insert_1>.

Severity: 0 : Information

Explanation: This message is issued when the broker passes a command request from the Configuration Manager to

an execution group.

Response: No user action required.

BIP2027 Broker received response from execution group <insert_0>

Severity: 0 : Information

Explanation: This message is issued when the broker receives a command response from an execution group.

Response: No user action required.

BIP2028 Broker sent completed command response to Configuration Manager

Severity: 0 : Information

Explanation: This message is issued when the broker sends a completed command response to the Configuration

Manager.

Response: No user action required.

BIP2030 Execution Group <insert_0> could not be created, unable to open its process handle.

Severity: 20 : Error

Explanation: The Broker could not create an Execution Group process.

Response: Ensure that the system has adequate system resources and that the Execution Group executable is

available. Contact your IBM support center if this does not resolve the problem.

BIP2031 Unable to start Execution Group executable <insert_0>.

Severity: 20 : Error

Explanation: The Broker could not create an Execution Group process.

Response: Ensure that the system has adequate system resources and that the Execution Group executable is

available. Contact your IBM support center if this does not resolve the problem.

BIP2032 Unable to access the broker’s database tables, the broker’s database name is blank.

Severity: 20 : Error

Explanation: The broker is incorrectly configured.

Response: Correct the broker database name by deleting and recreating the broker selecting a valid database name.

Database names must not be ’blank’.

BIP2033 The broker was forced to stop an execution group process, process ID was <insert_0>.

Severity: 0 : Information

Explanation: An attempt was made to stop an execution group process. The execution group process would not

terminate itself normally and so was forced to terminate.

Response: One reason for this is that the WebSphere Message Brokers executable bipbroker failed unexpectedly.

Bipbroker is automatically restarted by executable bipservice. During the restart of bipbroker all execution groups are

terminated by bipbroker and then restarted. If executable bipbroker failed during normal shutdown then execution

groups may be left running. On broker restart these execution group will be terminated and a new set of execution

groups started. A system log message indicating that executable bipbroker failed unexpectedly would indicate this

type of problem. Investigate why the executable bipbroker terminated unexpectedly. Ensure that any database

in-doubt or un-commited locks held by the execution group are dealt with, this termination should be treated as an

BIP2000 to BIP2999 (Broker) 79

abnormal termination of the execution group and handled accordingly. Use the WebSphere documention together

with your database documention to determine the best course of action for dealing with ’In-doubt’ units of work.

Contact your IBM support center if you are unable to determine the cause of the problem.

BIP2034 An unexpected exception was thrown.

Severity: 20 : Error

Explanation: An unexpected event occurred and an exception was created.

Response: Contact your IBM support center.

BIP2035 The internal configuration message was rejected due to broker persistent store problem.

Severity: 20 : Error

Explanation: The broker’s persistent store is not available, the internal configuration message was rejected because

of this.

Response: Ensure that the broker’s database is restarted.

BIP2036 Unable to commit database information, rolling back for retry.

Severity: 20 : Error

Explanation: An exception occurred during database commit processing.

Response: The commit will be retried.

BIP2037 The internal configuration message has been discarded.

Severity: 20 : Error

Explanation: An internal configuration message could not be processed to completion, even though multiple

attempts were made to process the message.

Response: Examine the system log for database problems. Resolve them and redeploy the configuration.

BIP2038 The internal configuration message was rejected due to broker persistent store problem.

Severity: 0 : Information

Explanation: The broker’s persistent store could not be updated; the internal configuration message was rejected

because of this.

Response: Examine the system log for database problems. Resolve them and redeploy the configuration.

BIP2040 Unable to commit database information, rolling back for retry.

Severity: 0 : Information

Explanation: An exception occurred during database commit processing.

Response: The commit will be retried.

BIP2045 Broker <insert_0> running on WebSphere queue manager <insert_2> did not process a deployment

message, because it was addressed to a broker with a different identifier.

Severity: 20 : Error

Explanation: This message usually means that an attempt has been made to assign the broker to a second (or a

reinitialized) Configuration Manager.

Each broker is identified by a universally unique identifier (UUID) which is allocated when the Message Brokers

Toolkit or Configuration Manager Proxy creates a definition for the broker. When deployment occurs, a UUID check

is made to help prevent accidental deployment of changes to brokers not under the control of the Configuration

80 Diagnostic messages

Manager. In this case, the deployment message was addressed to a broker with a UUID <insert_3>, but this does not

match the UUID of the running broker (<insert_1>).

Response: If possible, re-issue the deployment request using the Configuration Manager that administers this

broker. If this is not possible, use the Configuration Manager Proxy API BrokerProxy.setUUID() method to set the

UUID of broker <insert_0> to <insert_1>. This will allow the Configuration Manager to deploy to the broker, although

you must then issue Remove Deployed Children for that broker, recreate your execution groups and redeploy your

applications to restore a working configuration.

If all else fails, complete the following tasks in order: (1) stop and delete the broker component using

mqsideletebroker, (2) remove the broker definition from the domain using the Message Brokers Toolkit or

Configuration Manager Proxy, (3) recreate the broker component using mqsicreatebroker, (4) add the broker definition

to the domain using the Message Brokers Toolkit or Configuration Manager Proxy (5) redeploy your message flows

and related artefacts to the broker. Note the order of tasks (1) and (2), which is the reverse of the usual order of

operations when deleting brokers.

To prevent this problem from recurring when deleting or recreating brokers, always remove the broker definition

from the domain BEFORE the running broker component is stopped and deleted. See the WebSphere Message

Brokers online documentation section ″Recovering after failure″ for more information.

BIP2046 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration message to

completion: the problem was caused by missing tag <insert_2>.

Severity: 20 : Error

Explanation: The configuration message deployed by the Configuration Manager could not be processed and was

rejected.

Response: Use the inserts within this message to determine the cause of the problem, if possible correct the broker’s

configuration and redeploy from the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy.

Contact your IBM support center if you are unable to resolve the problem.

BIP2047 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration message because the

broker name received in the message (<insert_2>) did not match that of this broker.

Severity: 20 : Error

Explanation: An internal configuration message could not be processed and was rejected. Each broker is given a

name when the Message Brokers Toolkit user creates a definition for the broker. This name must match the name

supplied on the mqsicreatebroker command used to create the broker itself. Although the configuration message

received contained the correct broker identity (UUID), it contained a broker name, <insert_2>, that did not match the

name of this broker, <insert_0>. The probable cause is that a Message Brokers Toolkit user has incorrectly renamed

the broker in the broker definition.

Response: Use the Message Brokers Toolkit or Config Manager Proxy to rename the broker back to the name

specified on the mqsicreatebroker command. This name can be found using the mqsilist command.

BIP2048 An Exception was caught while issuing database SQL command <insert_0>.

Severity: 20 : Error

Explanation: The broker’s Database could not be accessed and an exception was generated.

Response: Ensure that the Database is running.

BIP2049 The broker made an unsuccessful attempt to access its database while attempting to execute SQL

syncpoint/rollback.

Severity: 20 : Error

Explanation: The broker’s database could not be accessed for a syncpoint/rollback.

Response: Ensure that the database is running.

BIP2000 to BIP2999 (Broker) 81

BIP2050 Broker <insert_0> (UUID <insert_1>) received an internal configuration message that specified

version <insert_2>, this broker is only capable of supporting up to and including version <insert_3>.

Severity: 20 : Error

Explanation: The versions of internal configuration message that the broker supports is dependent upon the

WebSphere Message Brokers product that is installed.

Response: Ensure that the component that is sending the internal configuration message is capable of sending an

internal configuration message with the correct version. Consult the WebSphere Message Brokers online

documentation book for migration guidance. Contact your IBM support center if you are unable to resolve the

problem.

BIP2051 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration message to

completion, the problem was caused by <insert_2>.

Severity: 20 : Error

Explanation: The configuration message could not be processed and was rejected.

Response: Use the inserts within this message to determine the cause of the problem. Correct the broker’s

configuration and redeploy using the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy

application. Contact your IBM support center if you are unable to resolve the problem.

BIP2052 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration message to

completion: the problem was caused by XML tag <insert_2>; value <insert_3>.

Severity: 20 : Error

Explanation: An internal configuration message could not be processed and was rejected.

Response: Contact your IBM support center.

BIP2053 The broker made an unsuccessful attempt to access its database <insert_0> with userid <insert_1>.

Severity: 20 : Error

Explanation: The broker’s database could not be accessed using the userid and password supplied.

Response: Ensure that the database is running and that the userid and password are correct.

BIP2054 Unable to allocate memory for an internal function.

Severity: 20 : Error

Explanation: There is a shortage of memory on the system.

Response: Increase the amount of memory available to the system.

BIP2056 Broker <insert_0> successfully processed the entire internal configuration message.

Severity: 0 : Information

Explanation: An internal configuration message was processed to completion.

Response: No user action required.

BIP2057 Execution Group <insert_0> could not be started: broker name <insert_1>; UUID <insert_2>; label

<insert_3>; Pub-Sub server <insert_4> (1=Yes, 0=No).

Severity: 20 : Error

Explanation: The broker was unable to start an execution group process.

Response: Ensure that the executable is available and that the broker’s service userid has permission to run the

executable.

82 Diagnostic messages

BIP2059 The broker has detected that the Execution Group <insert_0>, process ID <insert_1>, has shut down

abnormally.

Severity: 20 : Error

Explanation: An Execution Group process ended abnormally.

Response: Investigate the reasons for the problem.

BIP2060 The broker has detected that the Execution Group <insert_0>, process ID <insert_1>, has shutdown.

Severity: 10 : Warning

Explanation: An Execution Group has shutdown. A new instance of the execution group will be started in

approximately <insert_2> seconds.

Response: Investigate any prior system log messages for possible problems. Contact your IBM support center if you

are unable to determine the cause of the shutdown.

BIP2061 Broker <insert_0> (UUID <insert_1>) Execution Group <insert_2> (UUID <insert_3>) detected that the

deployed configuration message received contained an unsupported XML tag.

Severity: 20 : Error

Explanation: The Broker does not support the XML tag it received. The configuration message is rejected.

Response: Determine why this tag was deployed to the broker, correct the problem and deploy the complete

configuration for this Execution Group. If you are unable to resolve this problem then you should collect

Configuration Manager and bipbroker service trace and contact your IBM support center.

BIP2062 Broker <insert_0> (UUID <insert_1>) execution group <insert_2> (UUID <insert_3>) detected that the

deployed configuration message received contained an invalid XML tag.

Severity: 20 : Error

Explanation: The configuration message received could not be applied to the broker’s configuration. This could

occur for either of the following reasons: (a) The configuration message XML tag directs an execution group to be

created but the execution group already exists. (b) The configuration message XML tag directs an execution group to

be changed but the execution group does not exist. The configuration message is rejected.

Response: Use the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy to redeploy to the

execution group. Contact your IBM support center if you are unable to resolve the problem.

BIP2063 Broker <insert_0> (UUID <insert_1>) execution group <insert_2> (UUID <insert_3>) detected that the

deployed configuration message received would cause an uninitialized object to be created.

Severity: 20 : Error

Explanation: The configuration message received could not be applied to the broker’s configuration. The

configuration message is rejected.

Response: Resolve the problem by using the Message Brokers Toolkit, mqsideploy command or Config Manager

Proxy to redeploy to the execution group. If you are unable to resolve the problem, collect broker service trace and

contact your IBM support center.

BIP2064 Broker <insert_0> (UUID <insert_1>) Execution Group <insert_2> (UUID <insert_3>), deployed

configuration message rejected.

Severity: 0 : Information

Explanation: This Execution Group’s configuration message was rejected because the deployed configuration

message would have caused more serious errors in other Execution Groups. This Execution Group was not the

primary cause for the rejection of this configuration message.

Response: Look at all the messages that were listed and resolve the problems that they describe. The Execution

Group mentioned in this message can be deployed individually.

BIP2000 to BIP2999 (Broker) 83

BIP2065 Broker <insert_0> has processed a topology deployment.

Severity: 0 : Information

Explanation: The Message Brokers Toolkit, mqsideploy command or Config Manager Proxy application has

deployed a topology configuration.

Response: Determine if the deployment was successful by analyzing the messages following this message.

BIP2066 Broker <insert_0> (UUID <insert_1>) was unable to retrieve an internal configuration response

message for execution group <insert_2> within the <insert_3> second Configuration Timeout.

Severity: 20 : Error

Explanation: The execution group did not respond within the Configuration Timeout period. A negative response is

returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length

of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration

Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option,

ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to

reduce the response turnaround time or increase it to allow for large and complex deployments.

Response: Investigate why the execution group was unable to respond before being timed out. Use the system log

messages to determine if there is a problem with the execution group. You should check that your system is not

running short of resources, for example, you may need to increase the WebSphere log size. Reducing the complexity

of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the

problem and redeploy the broker’s configuration from the Message Brokers Toolkit, mqsideploy command or Config

Manager Proxy. If there are no other failure diagnostics then you should consider increasing the Configuration

Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if

you are unable to resolve the problem.

BIP2067 Broker <insert_0> (UUID <insert_1>) unable to get internal configuration response message for

Execution Group <insert_2> from WebSphere MQ queue <insert_3>.

Severity: 20 : Error

Explanation: The Execution Group internal configuration response message queue has failed.

Response: Investigate why the WebSphere MQ queue failed. Use the system log messages to determine and correct

the problem. Redeploy the broker configuration message from the Message Brokers Toolkit, mqsideploy command or

Config Manager Proxy.

BIP2068 The broker was unable to put an internal configuration message to message queue <insert_0>.

Severity: 20 : Error

Explanation: The internal configuration message could not be sent because the message queue was not available.

Response: Investigate why the message queue was not available by reviewing messages issued to the system log.

Resolve the problem and redeploy the broker’s configuration.

BIP2069 The broker attempted to put an internal configuration message to a reserved message destination

<insert_0>.

Severity: 20 : Error

Explanation: The message destination is reserved for use by the broker only.

Response: Investigate why the internal configuration’s reply message destination name was sent to a reserved

destination.

84 Diagnostic messages

BIP2070 A problem was detected with WebSphere MQ while issuing <insert_0> for WebSphere MQ queue

<insert_1>, WebSphere MQ queue manager <insert_2>. MQCC=<insert_3>, MQRC=<insert_4>.

Severity: 20 : Error

Explanation: The operation on the specified queue or queue manager returned with the indicated WebSphere MQ

completion and reason code.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action. If an MQOPEN was unsuccessful because the queue

manager or queue did not exist, then define these objects to WebSphere MQ. If the problem was because incorrect

object names were specified, then the message broker will try to recover, if the problem persists it may be necessary

to restart the message broker.

BIP2071 A problem was detected on WebSphere MQ while issuing <insert_0> for WebSphere MQ queue

<insert_1>, queue manager <insert_2>. WebSphere MQ property <insert_3> had an unsupported value

of <insert_4>.

Severity: 20 : Error

Explanation: The operation on the specified queue was not successful because the message being received contained

a WebSphere MQ property that is not supported.

Response: Investigate why the unsupported property was being used.

BIP2072 Execution Group <insert_0>, process ID <insert_1> was terminated.

Severity: 20 : Error

Explanation: The Execution Group process was terminated in preparation for a broker shutdown.

Response: Restart the broker when required.

BIP2073 Unable to create a Java VM.

Severity: 30 : Severe error

Explanation: This is an internal error.

Response: Stop the Configuration Manager service and contact your IBM support center.

BIP2074 A problem was detected with WebSphere MQ while issuing <insert_0> for WebSphere MQ Queue

Manager <insert_1>. MQCC=<insert_2>, MQRC=<insert_3>.

Severity: 20 : Error

Explanation: The operation on the specified queue manager returned with the indicated WebSphere MQ completion

and reason code.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action. If an MQOPEN was unsuccessful because the queue

manager did not exist, then define this object to WebSphere MQ. If the problem was because incorrect object names

were specified, then the message broker will try to recover, if the problem persists it may be necessary to restart the

message broker.

BIP2075 The broker was unable to send an internal configuration <insert_0> message to Execution Group

<insert_1>.

Severity: 20 : Error

Explanation: The internal configuration message could not be sent.

Response: Investigate why the Execution Group message queue was not available by reviewing messages issued to

the system log. Resolve the problem described in the system log. The broker will retry this operation.

BIP2000 to BIP2999 (Broker) 85

BIP2076 The broker was unable to get an internal configuration <insert_0> message response from Execution

Group <insert_1>.

Severity: 20 : Error

Explanation: The internal configuration message response could not be retrieved.

Response: Investigate why the Execution Group was not able to respond by reviewing messages issued to the

system log. Resolve the problem described in the system log. The broker will retry this operation.

BIP2077 The broker received a negative response to an internal configuration <insert_0> message from

Execution Group <insert_1>.

Severity: 20 : Error

Explanation: The internal configuration message response indicates that the Execution Group is not able to either

start processing message flows or to stop processing message flows. If the negative response was for a start message

then the operation will be retried later. If the negative response was for a stop message then this would indicate the

Execution Group was being deleted or the broker was attempting to shutdown, restarting the broker will correct this

problem, (you may need to use the -i flag on mqsistop)

Response: Investigate why the Execution Group response was negative by reviewing messages issued to the system

log. Resolve the problem described in the system log.

BIP2078 The broker was unable to get an internal configuration message from message queue <insert_0>.

Severity: 20 : Error

Explanation: The internal configuration message could not be retrieved because the message queue was not

available.

Response: Investigate why the message queue was not available by reviewing messages issued to the system log.

Resolve the problem and redeploy the broker’s configuration.

BIP2079 The broker received a response without data for an internal configuration <insert_0> message from

Execution Group <insert_1>.

Severity: 20 : Error

Explanation: The internal configuration message response had no data with its structure, so, the broker was unable

to determine if the Execution Group acted upon the configuration message. This operation will be retried later.

Response: Investigate why the Execution Group response contained no data by reviewing messages issued to the

system log. Resolve the problems described in the system log. If this problem persists contact your IBM support

center.

BIP2080 Execution Group <insert_0> failed to return an internal configuration <insert_1> message response

within a <insert_2> second time period.

Severity: 20 : Error

Explanation: The internal configuration message response could not be retrieved. The Execution Group therefore

failed to move to the state described by the internal configuration message.

Response: Investigate why the Execution Group internal configuration message response was not returned within

the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease)

the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying

problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow

for large and complex deployments. Resolve any problems described in the system log. This ’internal configuration’

operation will be retried automatically, if you continue to see this message you should investigate the reason for the

Execution Groups failure to respond.

86 Diagnostic messages

BIP2081 Execution Group <insert_0> process ID <insert_1> could not be stopped by the broker.

Severity: 20 : Error

Explanation: An attempt was made by the broker to stop an Execution Group process. This may have been as a

result of deleting and deploying the Execution Group or a failed attempt at creating and deploying the Execution

group. After one of these actions the broker attempted to force the Execution Group process to stop but was unable

to carry out this action.

Response: Investigate the reason why the broker user ID lacked the permissions to stop the stalled Execution Group

process. Reviewing messages issued to the system log may give some indication of why this occurred. Resolve the

problem described in the system log. It is required that the user stop the Execution Group process using either

mqsistop with the -i flag selected or the KILL function.

BIP2086 Broker <insert_0> could only process parts of the internal configuration message.

Severity: 20 : Error

Explanation: Parts of the internal configuration message were not processed successfully.

Response: This response indicates that one or more Execution Groups could not process the internal configuration

message. Analyze all of the following messages to determine why the internal configuration message could not be

processed.

BIP2087 Broker <insert_0> was unable to process the internal configuration message.

Severity: 20 : Error

Explanation: The entire internal configuration message failed to be processed successfully.

Response: The internal configuration message failed to be processed, use the messages following this message to

determine the reasons for the failure.

BIP2088 An unexpected exception <insert_0> was caught.

Severity: 20 : Error

Explanation: The broker caught an unexpected exception.

Response: Use the information in this message and previous messages to determine the cause of the problem,

correct the error. A redeploy will be required if this error occurred as a result of a deploy operation.

BIP2089 An internal configuration message was received but it contained no data.

Severity: 20 : Error

Explanation: The internal configuration message contained no data, the message was treated as a null operation.

Response: Contact your IBM support center.

BIP2090 The <insert_0> environment variable is <insert_1> characters long. The variable contains the

following data: <insert_2>.

Severity: 30 : Severe error

Explanation: The attempt to dynamically set an environment variable was unsuccessful.

Response: Contact your IBM support center.

BIP2091 The broker has reconnected to WebSphere MQ successfully.

Severity: 0 : Information

Explanation: The broker was unable to communicate via WebSphere MQ transports, communication has been

reestablished.

Response: Investigate the reasons for the WebSphere MQ product termination.

BIP2000 to BIP2999 (Broker) 87

BIP2092 The broker has reconnected to its persistent store successfully.

Severity: 0 : Information

Explanation: The broker was unable to save information to its persistent store, this connection has been

reestablished.

Response: Investigate the reasons for the broker’s persistent store being unavailable.

BIP2093 Java class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the Configuration Manager service and contact your IBM support center.

BIP2094 Java method <insert_1> in class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the Configuration Manager service and contact your IBM support center.

BIP2095 Instance of Java class <insert_0> could not be instantiated.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the Configuration Manager service and contact your IBM support center.

BIP2096 Java exception caught via the JNI from the <insert_0> class: exception text <insert_1>.

Severity: 30 : Severe error

Explanation: This may be an internal error, possibly due to a faulty installation, however review of the exception

text may indicate a solution. In particular, if (on NT) the text indicates that mqjbnd02 cannot be found then this

suggests that your PATH environment variable has not been set up correctly following WebSphere MQ classes for

Java installation.

Response: Stop the Configuration Manager service and if the exception text does not allow you to solve the

problem then you should contact your IBM support center.

BIP2097 Java field <insert_1> in class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the Configuration Manager service and contact your IBM support center.

BIP2098 Unable to locate function <insert_0> in implementation file <insert_1>, entry point <insert_2>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst loading a loadable implementation file. The resource has

not been registered. See the following messages for details of the error.

Response: Contact your IBM support center.

88 Diagnostic messages

BIP2099 Unable to initialize a Parser Factory.

Severity: 20 : Error

Explanation: The message broker detected an error whilst initializing its parser factory environment. Examine

previous error messages for details of the cause of this problem.

Response: Contact your IBM support center.

BIP2101 Unable to allocate memory.

Severity: 20 : Error

Explanation: An operation was performed which needed to allocate virtual memory, but the request failed because

not enough memory was available. Operation of the message broker will probably be unpredictable. Other messages

may indicate similar problems or provide additional information.

Response: Since this is indicative of a shortage in virtual memory, then after performing initial problem

determination, it may be necessary to either increase the amount of memory available or reduce the requirements for

memory on the system. The former might involve increasing the available RAM or increasing the amount of swap or

paging space. The latter might involve stopping applications which are not required, that have high memory

requirements or reducing the amount of broker processes or instances running on the system.

BIP2102 Invalid value (<insert_0>) for attribute (<insert_1>); node class=<insert_2>.

Severity: 20 : Error

Explanation: A configuration request was received which specified a value for the indicated attribute of the node

class. However, this value could not be converted to a wide string. The configuration request is terminated.

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request.

BIP2103 Internal broker error; condition=<insert_0>.

Severity: 30 : Severe error

Explanation: An internal software error has occurred in the message broker. The operation of the message broker is

likely to be affected and may now be unpredictable. An internal condition is displayed which describes the internal

error situation which occurred.

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.

BIP2104 Error whilst retrieving username for uid <insert_0>.

Severity: 30 : Severe error

Explanation: The message broker caused an exception whilst retrieving the username for uid <insert_0>. Check the

userid setup for the uid listed.

Response: On Distributed check that the userid listed has a default group. On z/OS check that the userid has a

default GID and an OMVS segment.

BIP2106 Unable to allocate memory during operation performed by object <insert_0>.

Severity: 20 : Error

Explanation: An Execution Group performed an operation which needed to allocate memory, but the request failed

because insufficient memory was available. The execution group process will be stopped and an attempt made to

restart it.

Response: Since this is indicative of a shortage of memory, it may be necessary (after performing initial problem

determination) to either increase the amount of memory available or reduce the system’s requirement for memory.

The former might involve increasing the available RAM or increasing the amount paging space. The latter might

involve stopping applications which are not required or which have high memory requirements and reducing the

amount of broker processes running on the system.

BIP2000 to BIP2999 (Broker) 89

BIP2110 Message broker internal program error.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. There is no diagnostic information associated with this message

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.

BIP2111 Message broker internal error: diagnostic information <insert_0>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. 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.

BIP2112 Message broker internal error: diagnostic information <insert_0>, <insert_1>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2113 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2114 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2115 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>,

<insert_4>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

90 Diagnostic messages

BIP2116 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>,

<insert_4>, <insert_5>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2117 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>,

<insert_4>, <insert_5>, <insert_6>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2118 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>,

<insert_4>, <insert_5>, <insert_6>, <insert_7>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2119 Message broker internal error: diagnostic information <insert_0>, <insert_1>, <insert_2>, <insert_3>,

<insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

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.

BIP2120 Message tree has two properties folders.

Severity: 20 : Error

Explanation: The message tree has two properties folders which is not allowed. A message may only have one

properties folder and this folder must be the first child of root.

Response: Review the message flow and ESQL that caused this error and make sure that two properties folders are

not being created. By default, every OutputRoot has a properties folder created automatically and a user should not

create an additional one.

BIP2121 The thread bootstrap code caught an unhandled exception on thread <insert_0>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. The exception was issued on thread <insert_0>. Further information

may be in the exception information associated with this message.

Response: Restart the message broker. If the problem continues to occur, then restart the system. If the problem still

continues to occur, then contact your IBM support center.

BIP2000 to BIP2999 (Broker) 91

BIP2122 An exception has been caught in thread clean up: diagnostic information <insert_0>, <insert_1>,

<insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If

the problem still continues to occur, then contact your IBM support center.

BIP2123 Thread terminate handler invoked: execution group will end; diagnostic information <insert_0>,

<insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>, <insert_7>, <insert_8>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions.

Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If

the problem still continues to occur, then contact your IBM support center.

BIP2124 The Execution group has detected a condition which requires it to shutdown and restart.

Severity: 20 : Error

Explanation: A condition has occured which requires the Execution Group to shutdown and restart in order to

recover from this condition. Further messages will indicate the cause of this condition.

Response: Check the system log for message that indicate the cause of this condition. Resolve the issue that caused

the condition and check the system log to ensure that the Execution Group is started again without error.

BIP2130 Error <insert_1> converting a character string to or from codepage <insert_0>.

Severity: 20 : Error

Explanation: A character conversion between codepages has failed. This may be due to an invalid codepage being

specified in the header of a message, or may be due to a character being present in a message that does not appear

in the required codepage conversion table.

Response: Check that the application that generated the message is using a valid codepage in the message header

and that all characters used are valid in that codepage.

BIP2131 A character codepage conversion error has occurred.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker.

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.

BIP2132 Invalid codepage <insert_0> or conversion table <insert_1> missing or invalid.

Severity: 20 : Error

Explanation: A codepage is being used for which there is no corresponding character conversion table, or the

conversion table cannot be used, or the conversion table is invalid.

Response: Check that the application generating the source message is using the correct code page within the

message.

92 Diagnostic messages

BIP2133 Source field <insert_0> is too long for a target field of length <insert_1> when converting from

unicode to codepage <insert_2>.

Severity: 20 : Error

Explanation: When the character data in the source field is converted to the target codepage, the resulting character

string was longer than the defined length of the target field.

Response: Correct the application or compute expression that generated the message. Ensure that the definition of

the field in the output message is correctly specified bearing in mind the codepage required for the message and

check that the origin of the data within the source field is providing correct data.

BIP2134 Source field <insert_0> is too long for a target field of length <insert_1> when converting to unicode

from codepage <insert_2>.

Severity: 20 : Error

Explanation: An internal processing error has occurred.

Response: Contact your IBM support center.

BIP2135 Source character <insert_0> in field <insert_1> cannot be converted to unicode from codepage

<insert_2>.

Severity: 20 : Error

Explanation: The source character is an invalid code point within the given codepage.

Response: Correct the application that generated the message.

BIP2136 Source character <insert_0> in field <insert_1> cannot be converted from unicode to codepage

<insert_2>.

Severity: 20 : Error

Explanation: The source character is an invalid code point within the given codepage.

Response: Correct the application or message flow that generated the message to ensure that all data within the

message can be represented in the target codepage.

BIP2137 A call to create a new thread has failed.

Severity: 20 : Error

Explanation: This can be caused by insufficient kernel resources.

Response: Please check and if necessary increase the max_thread_proc setting in your kernel to at least the value

specified in the installation guide.

BIP2141 Unable to open WebSphere MQ queue manager object; MQCC=<insert_0>, MQRC=<insert_1>

Severity: 20 : Error

Explanation: An attempt to open the connected WebSphere MQ queue manager to inquire about its settings failed.

The WebSphere MQ completion code and reason code returned are as displayed. Recovery processing of a backed

out message may not work as expected.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2000 to BIP2999 (Broker) 93

BIP2142 Unable to issue MQINQ to inquire on WebSphere MQ queue; queue=<insert_0>, MQCC=<insert_1>,

MQRC=<insert_2>.

Severity: 20 : Error

Explanation: An attempt to issue an MQINQ function to inquire about the status of the specified queue failed. The

WebSphere MQ completion code and reason code returned are as displayed. Recovery processing of a backed out

message will not work as expected.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2143 Unable to close WebSphere MQ queue manager object; MQCC=<insert_0>, MQRC=<insert_1>.

Severity: 20 : Error

Explanation: An attempt to close the connected WebSphere MQ queue manager failed. The WebSphere MQ

completion code and reason code returned are as displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2144 Node <insert_0> received conversion error on either WebSphere MQ queue manager or queue name.

Severity: 20 : Error

Explanation: The specified node was unable to convert the WebSphere MQ queue manager or queue name to a

wide string. The current message flow is terminated.

Response: Check the message flow to determine the cause of the error.

BIP2145 Failed to connect to WebSphere MQ queue manager <insert_0>; MQCC=<insert_1>,

MQRC=<insert_2>.

Severity: 20 : Error

Explanation: The specified node failed to connect to the indicated WebSphere MQ queue manager. The completion

and reason codes returned by the MQCONN are as displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action. If the open failed because the queue manager did not

exist, then define this object to WebSphere MQ. If the failure of the open was because an incorrect queue manager

name was specified, then correct the message flow configuration and attempt to redeploy the message broker.

BIP2150 About to load <insert_0>.

Severity: 0 : Information

Explanation: An execution group is about to load a library. Includes IBM and non IBM user defined nodes and

parsers.

Response: No user action required.

BIP2151 Loaded library <insert_0>.

Severity: 0 : Information

Explanation: An execution group has loaded a library.

Response: No user action required.

94 Diagnostic messages

BIP2152 Configuration message received from broker.

Severity: 0 : Information

Explanation: An execution group received a command from the Broker.

Response: No user action required.

BIP2153 About to <insert_0> an execution group.

Severity: 0 : Information

Explanation: An execution group is about to perform an action.

Response: No user action required.

BIP2154 Execution group finished with Configuration message.

Severity: 0 : Information

Explanation: A command response will be sent to the broker.

Response: No user action required.

BIP2155 About to <insert_0> ’ the Message flow - <insert_1>.

Severity: 0 : Information

Explanation: An execution group is about to perform an action.

Response: No user action required.

BIP2160 Broker process terminating abnormally: The following diagnostic information will be required

when contacting IBM: <insert_0>.

Severity: 20 : Error

Explanation: A broker process is terminating abnormally.

Response: Contact your IBM support center.

BIP2161 Broker process terminating abnormally (stack full): diagnostic information for IBM <insert_0>.

Severity: 20 : Error

Explanation: A broker process is terminating abnormally because its stack is full. For execution group processes, this

may be caused by message flows containing loops or more than 500 nodes in series. Otherwise the following

information will be required when contacting IBM: <insert_0>.

Response: Check the definitions of all message flows deployed on the named execution group for loops and

excessive path length. If this does not resolve the problem, contact your IBM support center.

BIP2162 Header invalid, structure identifier incorrect at offset <insert_0>.

Severity: 30 : Severe error

Explanation: A parser was constructed to process part of a message. That part of the message does not appear to be

a valid bitstream for the parser constructed.

Response: Contact your IBM support center.

BIP2163 User environment is invalid.

Severity: 30 : Severe error

Explanation: The user environment was not adequately prepared to continue execution. Locate and run the profile

supplied with the product. This file is called mqsiprofile, and is located in the bin subdirectory for the product.

BIP2000 to BIP2999 (Broker) 95

Response: Run the product profile. Also ensure that the user environment is prepared for database access. Use the

Documentation supplied with this product and the database to complete this operation.

BIP2164 An error occurred while opening registry file <insert_0> to read it : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot proceed, because it cannot read the value in the registry for this key.

Response: Contact your WebSphere Message Brokers administrator.

BIP2165 An error occurred while reading registry file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The broker cannot proceed, because it cannot read the value in the registry for this key.

Response: Contact your WebSphere Message Brokers administrator.

BIP2166 An error occurred while opening registry file <insert_0> to write it : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot proceed, because it cannot record the value in the registry for this key.

Response: Contact your WebSphere Message Brokers administrator.

BIP2167 An error occurred while writing registry file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot proceed, because it cannot write the value in the registry for this key.

Response: Contact your WebSphere Message Brokers administrator.

BIP2168 An error occurred while deleting files from registry directory <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: Some of the files in the broker registry have not been deleted.

Response: Ask your WebSphere Message Brokers administrator to check why the files could not be deleted, then

retry the mqsidelete command.

BIP2169 An error occurred while deleting the registry directory <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The broker registry has not been deleted.

Response: Ask your WebSphere Message Brokers administrator to check why the registry directory could not be

deleted, then retry the mqsidelete command.

BIP2170 The registry is already locked.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2171 An error occurred while opening the registry lock file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: You do not have sufficient UNIX file system permissions to administer the broker.

Response: Ask your WebSphere Message Brokers administrator to add you to the ’mqbrkrs’ group on UNIX

96 Diagnostic messages

systems or to a group that has the correct authorities on z/OS. After this has been done, log in again and reissue the

command.

BIP2172 An error occurred while locking the registry file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2173 An error occurred while writing to the registry lock file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2174 The registry was not locked.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2175 An error occurred while unlocking the registry lock file : <insert_0>.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2176 Could not find message <insert_0> in catalogue <insert_1>, inserts are <insert_2> <insert_3> <insert_4>

<insert_5> <insert_6> <insert_7> <insert_8>.

Severity: 30 : Severe error

Explanation: The required message could not be located in the specified catalogue.

Response: Ensure that the message catalogue is available. This failure usually occurs if the environment variable

NLSPATH is not correctly set.

BIP2177 Tried to create two name managers

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP2178 Failed to create a UUID (Error code = <insert_0>).

Severity: 20 : Error

Explanation: The system could not create a UUID.

Response: None.

BIP2179 Failed to convert an ImbWstring to an ImbUuidValue (Error code = <insert_0>).

Severity: 20 : Error

Explanation: The system could not convert the input ImbWstring to an ImbUuidValue.

Response: Make sure the input is valid.

BIP2000 to BIP2999 (Broker) 97

BIP2180 Failed to convert a UUID string to an ImbUuidValue (Error code = <insert_0>).

Severity: 20 : Error

Explanation: The system could not convert the input UUID string to an ImbUuidValue.

Response: Make sure the input UUID string is in the right format.

BIP2181 Failed to convert a UUID string to an ImbByteArray (Error code = <insert_0>).

Severity: 20 : Error

Explanation: The system could not convert the input UUID string to an ImbByteArray.

Response: Make sure the input UUID string is valid.

BIP2182 Failed to convert an ImbByteValue to a string (Error code = <insert_0>).

Severity: 20 : Error

Explanation: The system could not convert the input ImbByteValue to a string.

Response: Make sure the input ImbByteArray is valid.

BIP2183 The beta licence for this product has expired.

Severity: 30 : Severe error

Explanation: The licence for the beta version of this product has expired. Please contact your IBM representative for

a full (GA) version of this product.

Response: Please contact your IBM representative for a full licence.

BIP2184 The licence for the beta version of this product will expire in <insert_0> days.

Severity: 10 : Warning

Explanation: Please contact your IBM representative to obtain the full (GA) version of this product before this time.

After <insert_0> days have passed, this product will cease to function.

Response: Please contact your IBM representative to obtain the GA version of this product before this time.

BIP2185 Unable to redirect <insert_0> to file <insert_1>. The broker was unable to open <insert_1>. The

operating system return code <insert_2>.

Severity: 10 : Warning

Explanation: The broker was unable to redirect <insert_0> as it was unable to open the redirect file.

Response: Check the return code and restart the broker.

BIP2186 A component attempted to read a log file that was too large for it to handle.

Severity: 10 : Warning

Explanation: A request was sent to a component to read its log. While preparing the resulting output to send back,

it detected that it was over the maximum message size for the transport used.

Response: To read the log directly from the file, please issue the mqsireadlog command, specifying the -f flag.

BIP2201 Execution Group started: process <insert_13>; thread <insert_14>; additional information:

brokerName <insert_0>; executionGroupUUID <insert_1>; executionGroupLabel <insert_2>;

defaultExecutionGroup <insert_3>; queueManagerName <insert_4>; trusted <insert_5>;

dataSourceName <insert_6>; userId <insert_7>; migrationNeeded <insert_9>; brokerUUID <insert_10>;

filePath <insert_11>; workPath <insert_12>; ICU Converter Path <insert_15>.

Severity: 0 : Information

98 Diagnostic messages

Explanation: The execution Group has started using process <insert_13> and thread <insert_14> and will now start

processing messages.

Response: No user action required.

BIP2202 Administrative agent to execution group communication error: invalid value <insert_1> supplied for

execution group parameter <insert_0>.

Severity: 20 : Error

Explanation: The invalid value <insert_1> was supplied for the execution group parameter <insert_0>.

Response: Stop and restart the broker. If the problem persists, stop, delete, recreate and then restart the broker.

BIP2203 An execution group has encountered a problem whilst starting.

Severity: 20 : Error

Explanation: An execution group has encountered a problem whilst starting and is unable to continue.

Response: Check the following error messages to try to identify the cause of the problem. If it is unclear what the

cause is, and the problem occurs continually after restarting the message broker contact your IBM support center.

BIP2204 Execution group using process <insert_0> thread <insert_1> stopped.

Severity: 0 : Information

Explanation: The execution group using process <insert_0> and thread <insert_1> has stopped. This may be because

it has been instructed to do so or because it has encountered a problem.

Response: No user action required. The execution group will be restarted automatically if need be.

BIP2208 Execution Group (large) started: process <insert_13>; thread <insert_14>; additional information:

brokerName <insert_0>; executionGroupUUID <insert_1>; executionGroupLabel <insert_2>;

defaultExecutionGroup <insert_3>; queueManagerName <insert_4>; trusted <insert_5>;

dataSourceName <insert_6>; userId <insert_7>; migrationNeeded <insert_9>; brokerUUID <insert_10>;

filePath <insert_11>; workPath <insert_12>.

Severity: 0 : Information

Explanation: The execution Group has started using process <insert_13> and thread <insert_14> and will now start

processing messages.

Response: No user action required.

BIP2210 Invalid configuration message: attribute name <insert_0> not valid for target object <insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the attribute name <insert_0> which

is not valid for the target object <insert_1>. This can be caused by a mismatch in levels between the Message Brokers

Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written user-defined node

where the implementation library installed at the broker does not match the node definition held at the

Configuration manager and Message Brokers Toolkit.

Response: Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and

Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this

is IBM, contact your IBM support center.

BIP2211 Invalid configuration message containing attribute value <insert_1> which is not valid for target

attribute <insert_0>, object <insert_3>; valid values are <insert_2>

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the attribute value <insert_1> which

is not valid for the target attribute <insert_0>, on object <insert_3>. Valid values are <insert_2>. This can be caused by

BIP2000 to BIP2999 (Broker) 99

a mismatch in levels between the Message Brokers Toolkit, the Configuration Manager and the Broker, or as a result

of a user or third party written user-defined node where the implementation library installed at the broker does not

match the node definition held at the Configuration manager and Message Brokers Toolkit.

Response: Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and

Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this

is IBM, contact your IBM support center.

BIP2212 Invalid configuration message containing action <insert_0> which is not valid for target object

<insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the action <insert_0> which is not

valid for the target object <insert_1>. This can be caused by a mismatch in levels between the Message Brokers

Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written user-defined node

where the implementation library installed at the broker does not match the node definition held at the

Configuration manager and Message Brokers Toolkit.

Response: Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and

Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this

is IBM, contact your IBM support center.

BIP2213 Invalid configuration message containing folder <insert_0> which is not valid for target object

<insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the folder <insert_0> which is not

valid for the target object <insert_1>. This can be caused by a mismatch in levels between the Message Brokers

Toolkit, the Configuration Manager and the Broker, or as a result of a user or third party written plug-in node where

the implementation library installed at the broker does not match the node definition held at the Configuration

manager and Message Brokers Toolkit.

Response: Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and

Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this

is IBM, contact your IBM support center.

BIP2214 Invalid configuration message with no value for attribute <insert_0>, object <insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message which failed to supply a value for the attribute

<insert_0>, on object <insert_1>. This can be caused by a mismatch in levels between the Message Brokers Toolkit, the

Configuration Manager and the Broker, or as a result of a user or third party written user-defined node where the

implementation library installed at the broker does not match the node definition held at the Configuration manager

and Message Brokers Toolkit.

Response: Ensure that the levels of code installed at the Message Brokers Toolkit, Configuration Manager and

Broker are all consistent. If they are, identify the supplier of the target object and report the problem to them. If this

is IBM, contact your IBM support center.

BIP2215 The <insert_0> node <insert_3> property <insert_1> has been overridden by the value <insert_2> from

the LocalEnvironment.

Severity: 0 : Information

Explanation: Local environment variables override their corresponding node attributes.

Response: None.

100 Diagnostic messages

BIP2216 The <insert_0> node <insert_4> could not use the value <insert_2> from the LocalEnvironment for

overriding property <insert_1>. The value is not valid; valid values are <insert_3>.

Severity: 10 : Warning

Explanation: The value is not valid for that property.

Response: Make sure only one of the <insert_3> values is used.

BIP2217 File name <insert_0> is invalid for resource manager <insert_1>.

Severity: 20 : Error

Explanation: The message broker is given a file name <insert_0> which is not valid for the resource manager

<insert_1>. This may be an invalid/unknown file name extension or simply an invalid file path.

Response: Ensure a valid file name is provided.

BIP2220 No database specified for broker.

Severity: 10 : Warning

Explanation: The message broker was created without a database being specified, its configuration will not be

stored persistently.

Response: No user action required.

BIP2221 Invalid installation set up.

Severity: 20 : Error

Explanation: The message broker detected an error whilst connecting to its database. Its configuration will not be

stored persistently. Messages describing the error follow.

Response: No user action required.

BIP2222 Invalid database state: no database records for resource <insert_0>, <insert_1>.

Severity: 20 : Error

Explanation: The message broker could not locate the database records for the resource <insert_0>, <insert_1>. The

active state of the broker may not be as expected.

Response: Check that the message broker’s configuration database is currently started. Redeploy the complete

broker configuration using the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy. If the

problem persists contact your IBM support center.

BIP2223 A database operation was retried: attempt <insert_0> of 10; diagnostic information <insert_1>.

Severity: 0 : Information

Explanation: The message broker encountered a database lock or timeout accessing its configuration database, and

has retried the operation. This is attempt number <insert_0> out of 10. Additional diagnostic information is

<insert_1>.

Response: No user action required.

BIP2224 A database operation failed after repeated attempts: diagnostic information <insert_0>.

Severity: 20 : Error

Explanation: The message broker encountered a database lock or timeout and has retried the operation repeatedly

without resolving the problem. Additional diagnostic information <insert_0>.

Response: Ensure that the message broker’s configuration database has been configured and is operating correctly.

BIP2000 to BIP2999 (Broker) 101

BIP2225 An unexpected return code <insert_0> was received from a thread state change callback function.

Severity: 10 : Warning

Explanation: A function which registered for thread state change callback with user context <insert_1> and state

type <insert_2> has returned a value of <insert_0>.

Response: If you have a user-defined extension running within the execution group, ensure that any callbacks

return one of the expected values.

BIP2226 firstAbort specified - calling abort()

Severity: 20 : Error

Explanation: An abnormal event has taken place, and the specified abend action was firstAbort. A core file should

have been generated.

Response: Examine any core files produced.

BIP2227 signal <insert_0> received during signal processing - terminating.

Severity: 20 : Error

Explanation: An abnormal event has taken place, and the diagnostic routines could not complete successfully.

Response: None

BIP2228 Severe error: <insert_0> <insert_1> <insert_2> Abend file: <insert_3> action: <insert_4>.

Severity: 20 : Error

Explanation: An abnormal event has taken place. See the referenced abend file for details

Response: Correct the problem that caused the abnormal event.

BIP2229 <insert_0> <insert_1>.

Severity: 20 : Error

Explanation: An abnormal event has taken place, and the diagnostic routines could not complete successfully.

Response: Ensure that the standard location for the storage of abend files is writable.

BIP2230 Error detected whilst processing a message in node <insert_0>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst processing a message in node <insert_0>. An exception

has been thrown to cut short the processing of the message.

Response: See the following messages for details of the error.

BIP2231 Error detected whilst processing a message in node <insert_0>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst processing a message in node <insert_0>. The message

has been augmented with an exception list and has been propagated to the node’s failure terminal for further

processing.

Response: See the following messages for details of the error.

102 Diagnostic messages

BIP2232 Error detected whilst handling a previous error in node <insert_0>.

Severity: 20 : Error

Explanation: The message broker has detected an error in node <insert_0> whilst handling a previous error.

Response: See the following messages for details of the exception list associated with the original error. Thereafter

messages will be associated with the new error.

BIP2233 Invoking user-defined extension <insert_0>(<insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>,

<insert_6>, <insert_7>).

Severity: 0 : Information

Explanation: About to invoke the specified user-defined extension with the specified parameters.

Response: No user action required.

BIP2234 Returned from user-defined extension <insert_0> with result: <insert_1>.

Severity: 0 : Information

Explanation: The execution of the specified user-defined extension has been completed with the specified result.

Response: No user action required.

BIP2235 An error occurred while opening LIL directory <insert_0>.

Severity: 10 : Warning

Explanation: An error occurred while opening LIL directory <insert_0>. This directory may not exist, or may be

unreadable by the broker.

Response: Ensure that all directories contained in the LIL path are valid and readable by the broker.

BIP2236 Product LIL directory <insert_0> is not the first entry in LIL path <insert_1>.

Severity: 10 : Warning

Explanation: Product LIL directory <insert_0> is not the first entry in LIL path <insert_1>. This may interfere with

core broker functionality, and cause unexpected behavior during broker operation.

Response: Change the broker LIL path to include the product LIL directory as the first entry.

BIP2237 Product LIL directory <insert_0> is not included in LIL path <insert_1>.

Severity: 20 : Error

Explanation: Product LIL directory <insert_0> is not included in LIL path <insert_1>. Core broker functionality may

be not be available during broker operation, and unexpected behavior may result.

Response: Change the broker LIL path to include the product LIL directory.

BIP2238 LIL <insert_0> has been unloaded.

Severity: 10 : Warning

Explanation: LIL <insert_0> has been unloaded. This could be because it contained no resources, or because the

resources were already provided by another LIL.

Response: Ensure that all LILs contain valid, non-duplicate resources.

BIP2000 to BIP2999 (Broker) 103

BIP2239 LIL <insert_0> contains no valid resource entry points.

Severity: 10 : Warning

Explanation: LIL <insert_0> contains at least one entry point, but none are valid. See earlier messages for more

details on the exact error.

Response: Please ensure that the specified LIL contains only valid, non-duplicate resources.

BIP2240 Existing message flow <insert_2> already contains message flow node <insert_1> (uuid=<insert_0>).

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create the message

flow node <insert_1> (uuid=<insert_0>), but this node already exists in the message flow <insert_2> .

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2241 Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type <insert_0>

in message flow <insert_1>.

Severity: 20 : Error

Explanation: The message broker received an instruction to create a message flow node of type <insert_0>, in

message flow <insert_1>. The broker does not have the capability to create nodes of this type because an

implementation library for this node type was not found in the LIL path.

Response: Ensure that the LIL path is correct and contains all the necessary node implementation libraries,

including those supplied by IBM. The node name is case sensitive so ensure the toolkit and runtime names match. If

the broker is trying to create a node type that ends in ’NodeNode’ then ensure that when the node was registered

with the toolkit the name registered didn’t end in ’Node’. Then ensure that the message flow and any nested

message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete

configuration option is used. If the problem persists contact your IBM support center.

BIP2242 Message flow <insert_1> could not be reconfigured because it remained busy for longer than the

timeout period of <insert_0>

Severity: 20 : Error

Explanation: A request to reconfigure the message flow <insert_1> was received but this could not be processed

because it remained busy processing a message for longer than the timeout specified.

Response: This can be caused by the timeout being too short considering the complexity of the flow and the size of

the messages being processed. In such cases the timeout should be increased. It can also be caused by message flows

containing infinite loops. In such cases the SQL should be corrected.

BIP2243 Message flow <insert_1> cannot find message flow node <insert_0>.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to handle the message

flow node <insert_0>, but this node does not exist in the message flow <insert_1>.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2244 Request to create a connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: connection already exists in message flow

<insert_6>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

104 Diagnostic messages

between two node terminals, but this connection already exists in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2245 Request to create connection between node uuid=<insert_0> (label unknown) terminal <insert_1>,

and node <insert_3> (uuid=<insert_2>) terminal <insert_4>: source could not be found in message

flow <insert_5>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

between two node terminals, but the source node could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2246 Request to create connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: source terminal could not be found in

message flow <insert_6>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

between two node terminals, but the source terminal could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2247 Request to create connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node uuid=<insert_3> (label unknown) terminal <insert_4>: target cannot be found in message flow

<insert_5>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

between two node terminals, but the target node could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2248 Request to create connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>;’, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: terminal cannot be found in message flow

<insert_6>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

between two node terminals, but the target terminal could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2249 Request to create connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: connection does not exist in message flow

<insert_6>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create a connection

BIP2000 to BIP2999 (Broker) 105

between two node terminals, but this connection does not exist in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2250 Request to delete connection between node uuid=<insert_0> (label unknown) terminal <insert_1>,

and node <insert_3> (uuid=<insert_2>) terminal <insert_4>: source does not exist in message flow

<insert_5>.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to delete a connection

between two node terminals, but the source node could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2251 Request to delete connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: source terminal does not exist in message flow

<insert_6>.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to delete a connection

between two node terminals, but the source terminal could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2252 Request to delete connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node uuid=<insert_3> (label unknown) terminal <insert_4>: target node does not exist in message

flow <insert_5>.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to delete a connection

between two node terminals, but the target node could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2253 Request to delete connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and

node <insert_4> (uuid=<insert_3>) terminal <insert_5>: target terminal does not exist in message flow

<insert_6>.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to delete a connection

between two node terminals, but the target terminal could not be found in the message flow.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2254 Message flow node <insert_2> (uuid=<insert_1>) type <insert_0> in message flow <insert_3>

successfully created.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to create a message

flow node in the message flow and successfully performed this action.

106 Diagnostic messages

Response: No user action required.

BIP2255 Message flow connection successfully created between node <insert_1> (uuid=<insert_0>) terminal

<insert_2> and node <insert_4> (uuid=<insert_3>) terminal <insert_5>.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to create a connection

between two nodes, and successfully performed this action.

Response: No user action required.

BIP2256 Attribute of message flow node <insert_1> (uuid=<insert_0>) in message flow <insert_2> successfully

changed.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to change an attribute

of the message flow node <insert_1> (uuid=<insert_0>,) in the message flow <insert_2> and successfully performed

this action.

Response: No user action required.

BIP2257 Request to change an attribute of message flow node <insert_0>: node does not exist in message

flow <insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to change an attribute

of the message flow node <insert_0>, but this node does not exist in the message flow <insert_1>.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2258 Message flow node <insert_1> (uuid=<insert_0>) in message flow <insert_2> successfully deleted.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to delete the message

flow node <insert_1> (uuid=<insert_0>), in the message flow <insert_2> and successfully performed this action.

Response: No user action required.

BIP2259 Connection between node <insert_1> (uuid=<insert_0>) terminal <insert_2>, and node <insert_4>

(uuid=<insert_3>) terminal <insert_5> successfully deleted.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to delete the

connection between two nodes and successfully performed this action.

Response: No user action required.

BIP2260 Invalid node class name <insert_0> in loadable implementation library <insert_1>

Severity: 20 : Error

Explanation: The message broker detected the node factory attempting to register an invalid node class name. Node

class names must end in ’Node’.

Response: Contact the author or supplier of the loadable implementation library and obtain a version which

satisfies the node class name requirement.

BIP2000 to BIP2999 (Broker) 107

BIP2261 Node class name <insert_0> for use in library <insert_1> already registered in library <insert_2>.

Severity: 20 : Error

Explanation: The message broker detected the node factory in loadable implementation library <insert_1>

attempting to register the node class name <insert_0>, but this name has already been registered with the broker by

the node factory in the library <insert_2>.

Response: If the two loadable implementation libraries are different instantiations of the same node, then remove

one of the two from the ’bin’ directory for the message broker. If the two loadable implementation libraries are for

different nodes, then contact the author or supplier of the nodes and request that one changes the registered node

class name.

BIP2262 Request to create message flow <insert_1> (uuid=<insert_0>): message flow already exists.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an instruction to create the message

flow <insert_1> (uuid=<insert_0>), but this message flow already exists.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2263 Request to delete message flow <insert_0>: message flow does not exist.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to delete the message

flow <insert_0>, but this message flow does not exist.

Response: Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If

the problem persists contact your IBM support center.

BIP2264 Message flow <insert_1> (uuid=<insert_0>) successfully created.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to create the message

flow <insert_1> (uuid=<insert_0>), and successfully performed this action.

Response: No user action required.

BIP2265 Attribute in message flow <insert_1> (uuid=<insert_0>) successfully changed.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to change an attribute

in the message flow <insert_1> (uuid=<insert_0>) and successfully performed this action.

Response: No user action required.

BIP2266 Request to change attribute in message flow <insert_1> (uuid=<insert_0>): message flow does not

exist or is predefined.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to change an attribute

in the message flow <insert_1> (uuid=<insert_0>) but this can not be completed because the message flow either does

not exist or is predefined.

Response: Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If

the problem persists contact your IBM support center.

108 Diagnostic messages

BIP2267 Message flow <insert_1> (uuid=<insert_0>) successfully deleted.

Severity: 0 : Information

Explanation: The message broker received a configuration message containing an instruction to delete the message

flow <insert_1> (uuid=<insert_0>), and successfully performed this action.

Response: No user action required.

BIP2268 Request to report on message flow node <insert_0>: message flow does not exist.

Severity: 10 : Warning

Explanation: The message broker received a configuration message containing an instruction to obtain a report of

the message flow node <insert_0>, but this message flow does not exist.

Response: Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If

the problem persists contact your IBM support center.

BIP2269 Message flow <insert_1> (uuid=<insert_0>) started successfully.

Severity: 0 : Information

Explanation: The message broker received an operational control message containing an instruction to start the

message flow <insert_1> (uuid=<insert_0>) and successfully performed this action.

Response: No user action required.

BIP2270 Request to start message flow <insert_0>: message flow does not exist.

Severity: 10 : Warning

Explanation: The message broker received an operational control message containing an instruction to start the

message flow <insert_0>, but this message flow does not exist.

Response: Ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact

your IBM support center.

BIP2271 Message flow <insert_1> (uuid=<insert_0>) successfully stopped.

Severity: 0 : Information

Explanation: The message broker received an operational control message containing an instruction to stop the

message flow <insert_1> (uuid=<insert_0>) and successfully performed this action.

Response: No user action required.

BIP2272 Request to stop message flow(s) in Execution Group <insert_0>: flow(s) do not exist.

Severity: 10 : Warning

Explanation: The message broker received an operational control message containing an instruction to stop one or

more message flows in <insert_0>, but these flows do not exist.

Response: Determine whether or not the message flow(s) should exist at the broker. If it should, ensure that the

message flow(s), and any nested message flows have been saved. Redeploy the new configuration to the broker

ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.

BIP2273 Request to report on message flow <insert_0>: message flow does not exist.

Severity: 10 : Warning

Explanation: The message broker received an operational control message containing an instruction to report the

status of the message flow <insert_0>, but this message flow does not exist.

Response: No user action required.

BIP2000 to BIP2999 (Broker) 109

BIP2274 Invalid database state.

Severity: 20 : Error

Explanation: The message broker found a database record associated with its persistent state of its message flows to

be empty. The active state of the message broker may be incomplete.

Response: Redeploy the complete broker configuration from the Message Brokers Toolkit, mqsideploy command or

Config Manager Proxy. If the problem persists contact the IBM support center.

BIP2275 Database record associated with message flow <insert_0> is not valid.

Severity: 20 : Error

Explanation: The message broker found a database record associated with the persistent state of message flow

<insert_0> to be invalid. The active broker state may not be as expected.

Response: See the following message or messages for details of the error. Attempt to correct the error or errors by

redeploying the complete broker configuration from the Message Brokers Toolkit, mqsideploy command or Config

Manager Proxy. If the problem persists, contact your IBM support center.

BIP2280 Invalid installation.

Severity: 20 : Error

Explanation: The message broker detected an error whilst loading a loadable implementation file. The resource has

not been registered.

Response: See the following messages for details of the error.

BIP2281 Resource name <insert_0> for use in library <insert_1>: name already registered in library <insert_2>.

Severity: 20 : Error

Explanation: The message broker detected the resource in loadable implementation library <insert_1> attempting to

register the resource name <insert_0>, but this name has already been registered with the broker by the resource in

the library <insert_2>.

Response: Contact the authors or suppliers of the loadable implementation libraries to resolve the duplicate name

situation. Install a new version of at least one of the loadable implementation libraries.

BIP2290 Parser class name <insert_0> for use in library <insert_1>: name already registered in library

<insert_2>.

Severity: 20 : Error

Explanation: The message broker detected the parser factory in loadable implementation library <insert_1>

attempting to register the parser class name <insert_0>, but this name has already been registered with the broker by

the parser factory in the library <insert_2>.

Response: Contact the authors or suppliers of the loadable implementation libraries to resolve the duplicate name

situation. Install a new version of at least one of the loadable implementation libraries.

BIP2291 No constant for parser class name for root element name <insert_0>.

Severity: 20 : Error

Explanation: The message broker could not locate a constant for a parser class name for a root element name.

Response: Contact the author or supplier of the loadable implementation library implementing the parser to check

whether or not the constant has been registered. If it has not, install an updated version of the loadable

implementation library. If registration has taken place, contact your IBM support center.

110 Diagnostic messages

BIP2292 Constant for a parser class name for the root element name <insert_0>: constant is not valid.

Severity: 20 : Error

Explanation: The message broker located a constant defining a parser class name for the root element name

<insert_0> but it was invalid.

Response: Contact the author or supplier of the loadable implementation library implementing the parser to check

the definition of the parser class name. If the definition is invalid, install an updated version of the loadable

implementation library. If the definition is correct, contact your IBM support center.

BIP2293 Invalid configuration message containing attribute value <insert_0>: not valid for target attribute

’messageDomainProperty’ on object <insert_1>.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing an attribute value which is not valid

for the target attribute ’messageDomainProperty’ on an object on this broker. The value is case sensitive and must

match one of the parsers registered with this broker.

Response: Ensure that the value of the attribute is correct and that all the required parser implementation libraries

have been installed, then redeploy the message flow.

BIP2301 File <insert_0> does not contain suitable entry points.

Severity: 20 : Error

Explanation: The message broker loaded the implementation file <insert_0> but this could not find any suitable

entry points in it.

Response: Contact either the author or the supplier of the loadable implementation library for further assistance. If

the supplier is IBM, contact your IBM support center.

BIP2302 File <insert_0> contains insufficient resources.

Severity: 20 : Error

Explanation: The message broker loaded the implementation file <insert_0> and found entry points in it but could it

not find either any node factories, parser factories, or any other kind of resource within it.

Response: Contact either the author or the supplier of the loadable implementation library for further assistance. If

the supplier is IBM, contact your IBM support center.

BIP2303 File <insert_0> could not be unloaded; operating system return code <insert_1>.

Severity: 10 : Warning

Explanation: The message broker detected the loadable implementation library <insert_0> but this could not be

unloaded by the operating system. The operating system return code was <insert_1>.

Response: Contact either the author or the supplier of the loadable implementation library for further assistance. If

the supplier is IBM, contact your IBM support center.

BIP2304 Exception caught whilst loading file <insert_0>, the broker will operate with reduced capability.

Severity: 10 : Warning

Explanation: The message broker caught an exception whilst loading the implementation file <insert_0>. The broker

will continue to operate but with reduced capabilities. See the following messages for details of the error.

Response: See your system log for other messages associated with this one to establish and correct the cause of the

problem.

BIP2000 to BIP2999 (Broker) 111

BIP2305 Exception caught whilst loading file <insert_0>, the broker will restart.

Severity: 20 : Error

Explanation: The message broker caught an exception whilst loading the implementation file <insert_0>. The broker

will restart. See the following messages for details of the error.

Response: See your system log for other messages associated with this one to establish and correct the cause of the

problem.

BIP2306 Exception <insert_1> caught whilst loading file <insert_0>, the broker will restart.

Severity: 20 : Error

Explanation: The message broker caught an exception whilst loading the implementation file <insert_0>. The

information contained within this exception is <insert_1>. The broker will restart.

Response: Establish and correct the cause of the problem.

BIP2307 Unknown exception caught whilst loading file <insert_0>, the broker will restart.

Severity: 20 : Error

Explanation: The message broker caught an unknown exception whilst loading the implementation file <insert_0>.

The broker will restart.

Response: Establish and correct the cause of the problem.

BIP2308 File <insert_0> could not be loaded; operating system return code <insert_1>.

Severity: 20 : Error

Explanation: The message broker detected the loadable implementation file <insert_0> but this could not be loaded

by the operating system. The operating system return code was <insert_1>.

Response: Determine the cause of the load failure by analyzing the operating system return code. If necessary

contact either the author or the supplier of the loadable implementation library for further assistance. If the supplier

is IBM, contact your IBM support center.

BIP2310 The broker is not capable of handling message of type <insert_0> on behalf of node <insert_1>.

Severity: 20 : Error

Explanation: The message broker received a message that requires the handling of data of type <insert_0> but the

broker does not have the capability to handle data of this type. This happened when processing a message on behalf

of node <insert_1>.

Response: Check both the message being sent to be message broker and the configuration data for the node.

References to the unsupported data type must be removed if the messages are to be processed by the broker.

BIP2311 Program error in library <insert_0> whilst creating parser on behalf of node <insert_1>.

Severity: 20 : Error

Explanation: The message broker detected a program error in a parser library whilst attempting to create a parser.

This happened when processing a message on behalf of node <insert_1>.

Response: Contact the author or supplier of the parser to resolve the problem. If the parser was supplied by IBM,

contact your IBM support center.

BIP2312 About to load file <insert_0>.

Severity: 0 : Information

Explanation: The message broker is about to load the implementation file <insert_0>.

Response: No action need be taken.

112 Diagnostic messages

BIP2313 About to call <insert_1> in file <insert_0>.

Severity: 0 : Information

Explanation: The message broker is about to call initialization function <insert_1> in implementation file <insert_0>.

Response: No action need be taken.

BIP2314 User Exit <insert_0> not found. Registered User Exits - <insert_1>.

Severity: 20 : Error

Explanation: A User Exit name <insert_0> has been specified as active or inactive but that user exit was not

provided by any library loaded by this execution group. No user message flows will be started until this is resolved.

The list of user exits registered in this execution group is <insert_1>.

Response: Review the name provided. If the name is incorrect, reissue the relevant command with the correct name.

If the user exit was set at the broker level, then run mqsichangebroker to correct it. If it was set at the execution

group level, then run mqsichangeflowuserexit to correct it. Issue mqsireportflowuserexit to help determine where the

invalid user exit name was set. If the name is correct, ensure that the user exit library is being loaded by the

execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker

property to ensure one of them includes the directory containing the user exit library. Check system log when

execution group starts for errors loading the user exit library.

BIP2315 User Exit <insert_0> not found for flow <insert_1>. Registered User Exits - <insert_2>.

Severity: 0 : Information

Explanation: A UserExit name <insert_0> has been specified as active or inactive for message flow <insert_1> but

that user exit was not provided by any library loaded by this execution group. This message flow will not be started

until this is resolved. The list of user exits registered in this execution group is <insert_2>.

Response: Review the name provided. If the name is correct, ensure that the user exit library is being loaded by the

execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker

property to ensure one of them includes the directory containing the user exit library. Check system log when

execution group starts for errors loading the user exit library.

BIP2316 User Exit <insert_0> caused exception from the node completion callback function.

Severity: 0 : Information

Explanation: A UserExit named <insert_0> has thrown or has caused an exception to be thrown. This occured

during a call to the node completion callback function while the flow was handling a previous exception. Following

messages will indicate the cause of this latest exception and the flow will continue to handle the original excpetion.

Response: No action required.

BIP2317 User Exit <insert_0> caused exception from the transaction event callback function.

Severity: 0 : Information

Explanation: A UserExit named <insert_0> has thrown or has caused an exception to be thrown. This occured

during a call to the transaction event callback function to indicate the end (commit or rollback) of a transaction.

Following messages will indicate the cause of this latest exception. This exception will not have any effect on the

transaction.

Response: No action required.

BIP2318 User Exit <insert_0> not being invoked because no callback is registered for <insert_1>

Severity: 0 : Information

Explanation: A UserExit named <insert_0> is active for the current flow and the relevant event has occurred.

However, the User Exit has not provided a function for this event so will not be invoked.

Response: No action required.

BIP2000 to BIP2999 (Broker) 113

BIP2321 Database error: ODBC return code <insert_0>.

Severity: 20 : Error

Explanation: The message broker encountered an error whilst executing a database operation. The ODBC return

code was <insert_0>. See the following messages for information obtained from the database pertaining to this error.

Response: Use the following messages to determine the cause of the error. This is likely to be such things as

incorrect datasource or table names. Then correct either the database or message broker configuration.

BIP2322 Database error: SQL State <insert_0>; Native Error Code <insert_1>; Error Text <insert_2>.

Severity: 20 : Error

Explanation: The error has the following diagnostic information: SQL State <insert_0> SQL Native Error Code

<insert_1> SQL Error Text <insert_2>

Response: This message may be accompanied by other messages describing the effect on the message broker itself.

Use the reason identified in this message with the accompanying messages to determine the cause of the error.

BIP2323 Unsupported DBMS (<insert_0>) for a coordinated transaction.

Severity: 20 : Error

Explanation: A message flow has been configured for a globally coordinated transaction, and a message processing

node has specified a database connection target as a participant in the global transaction. However, this DBMS is not

supported by WebSphere Message Brokers as a participant in a globally coordinated transaction. The message flow is

terminated and the input message is backed out.

Response: As this target DBMS is not supported as a participant in a coordinated transaction, the node may only

utilise this database outside any global transaction.

BIP2324 Unsupported datatype <insert_1> fetched from database table column <insert_0>.

Severity: 20 : Error

Explanation: A message flow node which performs a database fetch returned a datatype not supported by the

message broker. The database table column <insert_0> contain an unsupported datatype identified by <insert_1>.

Response: Either update the message flow to eliminate the reference to the database column with the unsupported

datatype, or modify the database schema to change the column to be of a type supported by the message broker.

BIP2325 Invalid datatype <insert_0> encountered.

Severity: 20 : Error

Explanation: An invalid datatype identified by <insert_0> was encountered during the processing of a message flow.

This indicates that an internal software error has occurred.

Response: Restart the broker. If the problem continues to occur contact your IBM support center.

BIP2326 Error casting <insert_2> hours <insert_3> minutes <insert_4> seconds to a TIME. State = <insert_0>

<insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: Numbers may only be converted to a time if they conform to the constraints of the 24 hour clock.

Response: Ensure that the values being cast have valid values.

BIP2327 Error casting <insert_2> years <insert_3> months <insert_4> days to a DATE. State = <insert_0>

<insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: Numbers may only be converted to a date if they conform to the constraints of the Gregorian calendar.

114 Diagnostic messages

Response: Ensure that the values being cast have valid values.

BIP2328 A value of SQL datatype <insert_0> encountered when datatype <insert_1> expected.

Severity: 20 : Error

Explanation: The value of SQL datatype <insert_0> was encountered, but a value of SQL datatype <insert_1> was

expected.

Response: This message will be accompanied with others which will give the higher level context for this error.

Look at these other messages to determine the root source of the problem.

BIP2329 An unexpected NULL value was encountered.

Severity: 20 : Error

Explanation: This message will be accompanied with others which will give the higher level context for this error.

Look at these other messages to determine the root source of the problem.

BIP2330 Field <insert_3>[<insert_4>]’ within field <insert_0> does not exist; diagnostic information <insert_1>,

<insert_2>.

Severity: 20 : Error

Explanation: The message broker attempted to locate the field <insert_3>[<insert_4>]’ contained within the field

<insert_0> but the message did not contain this field. Additional diagnostic information is <insert_1> <insert_2>.

Response: Check the message flow definition and the messages being processed by the message flow to ensure that

the referenced field has been correctly specified. If necessary change the message flow to eliminate the reference to

the nonexistent field.

BIP2331 Field <insert_1> within field <insert_0> does not exist.

Severity: 20 : Error

Explanation: The message broker attempted to locate the field <insert_1> contained within the field <insert_0> but

the message did not contain this field.

Response: Check the message flow definition and the messages being processed by the message flow to ensure that

the referenced field has been correctly specified. If necessary change the message flow to eliminate the reference to

the nonexistent field.

BIP2332 Error attaching field <insert_1> to field <insert_0> which already has a parent.

Severity: 20 : Error

Explanation: The message broker attempted to attach the field <insert_1> to the field <insert_0> but the latter field

already has a parent field.

Response: This error can arise as a result of an error in a the use of the SQL ATTACH statement. Examine the logic

of the SQL statements, correct it and redeploy.

BIP2333 Error attaching field <insert_1> as a sibling of field <insert_0> which has no parent.

Severity: 20 : Error

Explanation: The message broker attempted to attach the field <insert_1> as a sibling of the field <insert_0> but the

latter field does not have a parent field.

Response: This error can only arise as a result of an error in a node or parser implementation library. Contact the

author or supplier of the loadable implementation library and obtain a correct version.

BIP2000 to BIP2999 (Broker) 115

BIP2334 Unable to resolve union for the <insert_2> child of element <insert_1>. Additional diagnostic

information is <insert_0>

Severity: 10 : Warning

Explanation: An incoming message contained a union which was neither resolved by the message’s tagging nor by

the accesses made by SQL statements. Either the message was of an unexpected type or there is an error in the SQL.

See earlier messages for details of the node in which this error occurred and the action taken as a result.

Response: Check that the incoming messages are of the correct type and that the logic of the SQL of the node in

which the error occurred

BIP2335 Unable to perform copy. Element <insert_1> is a child of element <insert_3>. Additional diagnostic

information is <insert_0> <insert_2>

Severity: 10 : Warning

Explanation: A recursive copy was attempted but these are not allowed as they lead to indeterminate results. See

earlier messages for details of the node in which this error occurred and the action taken as a result.

Response: Check the logic of the SQL of the node in which the error occurred

BIP2336 Error attaching field <insert_1> to field <insert_0>. Field <insert_0> is a child of field <insert_1>.

Severity: 20 : Error

Explanation: A field cannot be attached as a child or sibling of one of its own children as this would create a closed

loop within a message tree. The broker does not support such structures.

Response: This error can arise as a result of an error in a the use of the SQL ATTACH statement. Examine the logic

of the SQL statements, correct it and redeploy.

BIP2337 Attempt to use an unsuitable domain in a shared tree.

Severity: 20 : Error

Explanation: In this release, shared trees are resticted in the message domains that may be used. For example the

Properties, MQMD, MQRFH2C, XMLNSC and most MQ headers may be used but the MQRFH2, XML, XMLNS,

MRM domains may not.

Response: Correct the logic of the message flow and re-deploy.

BIP2338 The data type <insert_0> is not supported by the <insert_1> database.

Severity: 20 : Error

Explanation: When queried the <insert_1> database manager did not return a value for the SQL type <insert_0>

indicating that it does not support this data type.

Response: Check that the datatype <insert_0> is the correct data type for your user database. Do not use Informix or

DB2 IICF databases for the broker database.

BIP2340 Error attaching field <insert_1> to field <insert_0> which belongs to a message in a different group.

Severity: 20 : Error

Explanation: The message broker attempted to attach the field <insert_1> to the field <insert_0> but the latter field

belongs to a message in a different group.

Response: This error can only arise as a result of an error in a node or parser implementation library. Contact the

author or supplier of the loadable implementation library and obtain a correct version.

116 Diagnostic messages

BIP2350 Unable to convert <insert_0> from UNICODE to the local code page.

Severity: 20 : Error

Explanation: The message broker was unable to convert the value <insert_0> from unicode to the local code page.

Response: Check that the source of the data containing the value that cannot be converted is intended to be

displayed in the local code page. If the intention is that the data should never be displayed in the local codepage,

modify the message flow to eliminate the cause of conversion. If the intention is that the data should be displayed,

then check the origin of the data to ensure that only characters capable of being displayed in the local code page are

generated.

BIP2351 Unable to convert <insert_0> from local code page to UNICODE.

Severity: 20 : Error

Explanation: The message broker was unable to convert the value <insert_0> from the local code page to unicode.

Response: This is an internal processing error. Contact your IBM support center.

BIP2352 Unable to convert <insert_0> to an integer from the local code page.

Severity: 20 : Error

Explanation: The message broker was unable to convert the value <insert_0> from the local code page to an integer.

Response: Check the source of the data for the value to determine why the value is not suitable for conversion to

an integer.

BIP2353 Unable to convert <insert_0> to a real number from the local code page.

Severity: 20 : Error

Explanation: The message broker was unable to convert the value <insert_0> from the local code page to a real

number.

Response: Check the source of the data for the value to determine why the value is not suitable for conversion to a

real number.

BIP2360 Syntax error in path specification missing ’)’ after type specification.

Severity: 20 : Error

Explanation: A ’)’ must close a type specification. A path string has been specified using an invalid syntax. The path

was specified as <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP2361 Syntax error in path specification, no closing ’]’ in index specification.

Severity: 20 : Error

Explanation: A ’]’ must close an index specification. A path string has been specified using an invalid syntax. The

path was specified as <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP2362 Syntax error in path specification missing ’.’ after index specification.

Severity: 20 : Error

Explanation: A ’.’ must follow an index specification. A path string has been specified using an invalid syntax. The

path was specified as <insert_0>.

Response: This is an internal error. Contact your IBM support center.

BIP2000 to BIP2999 (Broker) 117

BIP2370 Transaction compromised: message flow thread already connected to DSN <insert_0> in a different

coordination mode.

Severity: 20 : Error

Explanation: A thread executing a message flow node attempted to connect to a database. However, the message

flow thread already had a connection to the same data source name (DSN) <insert_0> in a different coordination

mode. On UNIX and Windows platforms, this request cannot be granted because this would compromise the

integrity of a globally coordinated transaction and would result in XA protocol errors and/or unpredictable behavior.

This can occur if a message flow has been configured with the Coordinated Transaction property of ’yes’ and the

nodes specifies a property which indicate that a commit to that database is to be performed.

Response: Correct the message flow and redeploy the message broker.

BIP2371 Database statement <insert_0> could not be executed.

Severity: 20 : Error

Explanation: An attempt to execute a database statement <insert_0> has failed (the database returned an error).

Response: Identify the cause of the problem and correct it before trying again. If relevant, correct the message flow

and redeploy the message broker.

BIP2380 WBIMB message flow statistics.

ProcessID=<insert_0>,

Key=<insert_1>,

Type=<insert_2>,

Reason=<insert_3>,

BrokerLabel=<insert_4>,

BrokerUUID=<insert_5>,

ExecutionGroupName=<insert_6>,

ExecutionGroupUUID=<insert_7>,

MessageFlowName=<insert_8>,

StartDate=<insert_9>,

StartTime=<insert_10>,

EndDate=<insert_11>,

EndTime=<insert_12>,

TotalElapsedTime=<insert_13>,

MaximumElapsedTime=<insert_14>,

MinimumElapsedTime=<insert_15>,

TotalCPUTime=<insert_16>,

MaximumCPUTime=<insert_17>,

MinimumCPUTime=<insert_18>,

CPUTimeWaitingForInputMessage=<insert_19>,

ElapsedTimeWaitingForInputMessage=<insert_20>,

TotalInputMessages=<insert_21>,

TotalSizeOfInputMessages=<insert_22>,

MaximumSizeOfInputMessages=<insert_23>,

MinimumSizeOfInputMessages=<insert_24>,

NumberOfThreadsInPool=<insert_25>,

TimesMaximumNumberOfThreadsReached=<insert_26>,

TotalNumberOfMQErrors=<insert_27>,

TotalNumberOfMessagesWithErrors=<insert_28>,

TotalNumberOfErrorsProcessingMessages=<insert_29>,

TotalNumberOfTimeOuts=<insert_30>,

TotalNumberOfCommits=<insert_31>,

TotalNumberOfBackouts=<insert_32>.

AccountingOrigin=<insert_33>.

Severity: 0 : Information

Explanation: Statistical information for message flow <insert_8> in broker <insert_4>.

Response: This is an information message produced by WBIMB statistics.

118 Diagnostic messages

BIP2381 WBIMB thread statistics.

ProcessID=<insert_0>,

Key=<insert_1>,

Number=<insert_2>,

TotalNumberOfInputMessages=<insert_3>,

TotalElapsedTime=<insert_4>,

TotalCPUTime=<insert_5>,

CPUTimeWaitingForInputMessage=<insert_6>,

ElapsedTimeWaitingForInputMessage=<insert_7>,

TotalSizeOfInputMessages=<insert_8>,

MaximumSizeOfInputMessages=<insert_9>,

MinimumSizeOfInputMessages=<insert_10>.

Severity: 0 : Information

Explanation: Statistical information for thread <insert_2>.

Response: This is an information message produced by WBIMB statistics.

BIP2382 WBIMB node statistics.

ProcessID=<insert_0>,

Key=<insert_1>,

Label=<insert_2>,

Type=<insert_3>,

TotalElapsedTime=<insert_4>,

MaximumElapsedTime=<insert_5>,

MinimumElapsedTime=<insert_6>,

TotalCPUTime=<insert_7>,

MaximumCPUTime=<insert_8>,

MinimumCPUTime=<insert_9>,

CountOfInvocations=<insert_10>,

NumberOfInputTerminals=<insert_11>,

NumberOfOutputTerminals=<insert_12>.

Severity: 0 : Information

Explanation: Statistical information for node <insert_2>.

Response: This is an information message produced by WBIMB statistics.

BIP2383 WBIMB terminal statistics.

ProcessID=<insert_0>,

Key=<insert_1>,

Label=<insert_2>,

Type=<insert_3>,

CountOfInvocations=<insert_4>,

Severity: 0 : Information

Explanation: Statistical information for terminal <insert_2>.

Response: This is an information message produced by WBIMB statistics.

BIP2384 Error updating the statistics message flow transaction container for message flow <insert_0>. Node

<insert_1> was not found.

Severity: 20 : Error

Explanation: The container used to gather statistics for a message flow transaction does not match the shape of the

message flow that processed the input message. Statistics gathering is unable to continue for this message flow.

Response: Check that the deploy of the message flow was successful. If the problem persists then you should

contact your IBM Support center.

BIP2000 to BIP2999 (Broker) 119

BIP2385 Error updating the statistics message flow transaction container for message flow <insert_0> and

node <insert_1>. The terminal <insert_2> was not found.

Severity: 20 : Error

Explanation: The container used to gather statistics for a message flow transaction does not match the shape of the

message flow that processed the input message. Statistics gathering is unable to continue for this message flow.

Response: Check that the deploy of the message flow was successful. If the problem persists then you should

contact your IBM Support center.

BIP2386 Error writing statistics collector record for message flow <insert_0>. The <insert_1> writer was not

available.

Severity: 20 : Error

Explanation: The statistics writer associated with the specified output format was either not found or there is a

problem with the output medium. Statistics output is unable to continue for this message flow.

Response: Check that the media for the required statistics output format is available and correctly configured. If the

problem persists then you should contact your IBM Support center.

BIP2387 Error encountered during <insert_0> operation for a statistics message flow transaction container for

message flow <insert_1>.

Severity: 20 : Error

Explanation: The statistics conveyor was not found for the operation specified or it was left in a locked state as the

result of a previous system error.

Response: Check the broker system error logs for previous errors. If the problem persists then you should contact

your IBM Support center.

BIP2388 Unable to obtain a statistics message flow transaction container for message flow <insert_0>.

Severity: 20 : Error

Explanation: The pool for the statistics message flow transaction containers was unable to create and dispense a

new container for the statistics gathering process.

Response: Check that the deploy of the message flow was successful. If the problem persists then contact your IBM

Support center.

BIP2390 Internal Error in WBIMB Statistics and Accounting <insert_0> <insert_1> <insert_2>

Severity: 20 : Error

Explanation: A processing error occurred while gathering statistics data for the message flow.

Response: Check that the deploy of the message flow was successful. If the problem persists then you should

contact your IBM Support center.

BIP2391 DB2 wrapper (64-bit) could not load the DB2 implementation library using library locations

<insert_0>, <insert_1>, or the location specified by the MQSI_64BIT_DB2_LIBRARY_NAME

environment variable. DB2 will not be accessible in this process.

Severity: 20 : Error

Explanation: The ODBC driver manager is attempting to load the DB2 application binding library using a 64-bit

DB2 wrapper. The wrapper has loaded correctly, but is itself unable to load the actual DB2 implementation library

needed for operation. See the Standard Output (stdout) and Standard Error (stderr) for this process for any additional

information.

Response: Ensure DB2 is accessible to the broker user id, and that the shared library search path is set to include

the DB2 64-bit library location. Setting MQSI_64BIT_DB2_LIBRARY_NAME to point to libdb2.so (or .sl or .a) may

help this problem.

120 Diagnostic messages

BIP2392 DB2 wrapper (64-bit) could not find the function <insert_0> in the DB2 implementation library

<insert_1>. This function will not be available to broker code in this process.

Severity: 20 : Error

Explanation: The ODBC driver manager has loaded the DB2 application binding library using a 64-bit DB2 wrapper,

but the wrapper cannot find the function <insert_0> which is needed for the broker to operate completely correctly.

Subsequent database errors may be caused by this problem.

Response: Ensure the DB2 wrapper library can find the correct DB2 application binding library. Setting

MQSI_64BIT_DB2_LIBRARY_NAME to point to the correct libdb2.so (or .sl or .a) may help this problem.

BIP2401 (<insert_0>, <insert_1>) : Syntax error : expected <insert_2> but found <insert_3>.

Severity: 20 : Error

Explanation: The expected token was not found.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2402 (<insert_0>, <insert_1>) : Syntax error : <insert_2>.

Severity: 20 : Error

Explanation: The token caused a syntax error.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2403 (<insert_0>, <insert_1>) : An interval qualifier is not allowed here.

Severity: 20 : Error

Explanation: An interval qualifier was specified after a pair of parentheses which did not contain a subtraction

expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2404 Illegal reference use.

Severity: 20 : Error

Explanation: A reference variable has been used when the entity to which it refers no longer exists.

Response: Correct the logic of the SQL program and redeploy the message flow.

BIP2405 (<insert_0>, <insert_1>) : Syntax error : <insert_2> is a keyword , an identifier was expected.

Severity: 20 : Error

Explanation: The token caused a syntax error.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2406 (<insert_0>, <insert_1>) : Syntax error : cannot specify ’[]’ in the middle of a field reference.

Severity: 20 : Error

Explanation: The list specifier (’[]’) can only be used at the end of a field reference.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 121

BIP2407 (<insert_0>, <insert_1>) : Precision must be > 0 and <= <insert_0>.

Severity: 20 : Error

Explanation: A precision value was given in the definition of a DECIMAL datatype which was outside of the valid

range.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct the definition of the DECIMAL datatype so that a valid precision is specified and

redeploy the message flow.

BIP2408 (<insert_0>, <insert_1>) : Scale must be >= 0 and <= <insert_0>.

Severity: 20 : Error

Explanation: A scale value was given in the definition of a DECIMAL datatype which was outside of the valid

range.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct the definition of the DECIMAL datatype so that a valid scale is specified and

redeploy the message flow.

BIP2409 (<insert_0>, <insert_1>) : An interval qualifier was expected.

Severity: 20 : Error

Explanation: INTERVAL data types must be qualified with a valid qualifier such as ’MONTH TO YEAR’. See the

documentation for a full list of valid qualifiers.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2410 (<insert_0>, <insert_1>) : A field reference was expected.

Severity: 20 : Error

Explanation: A field reference was expected here but there does not appear to be one.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2411 (<insert_0>, <insert_1>) : The source expression did not evaluate to a ROW.

Severity: 20 : Error

Explanation: When ″INSERT″ is specified as the target within a ROW, its source expression must also be a ROW.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2412 (<insert_0>, <insert_1>) : Expected one of ’ANY’, ’ALL’ or ’SOME’.

Severity: 20 : Error

Explanation: The token found did not match any of the expected values.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2413 (<insert_0>, <insert_1>) : Inconsistent number of values in VALUES clause.

Severity: 20 : Error

Explanation: The number of values specified in the VALUES clause does not match the number of columns

specified.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

122 Diagnostic messages

redeploy the message flow: Correct the number of values specified in the VALUES clause and redeploy the message

flow.

BIP2414 Unsupported datatype <insert_0>.

Severity: 20 : Error

Explanation: While preparing an ODBC statement a parameter with data type <insert_0> was encountered. This

data type is not yet supported for ODBC operations.

Response: Ensure that expressions which may return values of data type <insert_0> are not used as parameters in

statements or expressions that access external databases.

BIP2415 (<insert_0>, <insert_1>) : A correlation name must be specified.

Severity: 20 : Error

Explanation: The UPDATE and DELETE statements and also the SELECT function when applied to a database

require a correlation name to be defined. This name represents a variable which holds each row involved in the

operation in turn. Correlation names may be explicitly defined by an AS clause or may be implictly defined by a

hardcoded table name. It is an error to use a table name expression and not specify a correlation name explicitly.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2416 The target type <insert_0> and the number of parameters supplied <insert_1> do not correspond to

any valid CAST

Severity: 20 : Error

Explanation: Correct the syntax of the SQL program and re-deploy.

BIP2417 (<insert_0>, <insert_1>) : Invalid table reference.

Severity: 20 : Error

Explanation: A table reference consists of a correlation name (e.g. ″Database″) followed by one, two or three names

(or name expressions) giving the data source name, the schema name and the table name. The given field reference

does not meet this requirement.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2418 (<insert_0>, <insert_1>) : Invalid schema reference.

Severity: 20 : Error

Explanation: A schema reference consists of a correlation name (e.g. ″Database″) followed by one or two names (or

name expressions) giving the data source name and the schema name. The given field reference does not meet this

requirement.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2419 (<insert_0>, <insert_1>) : Invalid database reference.

Severity: 20 : Error

Explanation: A database reference consists of a correlation name (e.g. ″Database″) followed by a single name (or

name expression) giving the data source name. The given field reference does not meet this requirement.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 123

BIP2420 (<insert_0>, <insert_1>) : Invalid or incompatible data types for <insert_2> operator.

Severity: 20 : Error

Explanation: Either the data types of the operands of the operator were not valid for the operator, or the datatypes

were incompatible.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the data types of the operands are valid and compatible with each other.

BIP2421 (<insert_0>, <insert_1>) : Left hand operand to <insert_2> operator must be a scalar.

Severity: 20 : Error

Explanation: The left hand operand to the operator was not a scalar valued expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the left hand operator to the <insert_2> operator is a scalar.

BIP2422 (<insert_0>, <insert_1>) : Right hand operand to the <insert_2> operator must be a scalar.

Severity: 20 : Error

Explanation: The right hand operand to the operator was not a scalar valued expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the right hand operand to the <insert_2> operator is a scalar.

BIP2423 (<insert_0>, <insert_1>) : Interval qualifier only valid with datetime subtraction.

Severity: 20 : Error

Explanation: If an interval qualifier is specified after a subtraction expression, the operands of the expression must

be datetime values.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2424 (<insert_0>, <insert_1>) : Interval qualifier must be specified with a datetime subtraction.

Severity: 20 : Error

Explanation: When subtracting two datetime values, an interval qualifier must be given.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2425 Interval qualifier not valid for subtraction between values <insert_0> and <insert_1>.

Severity: 20 : Error

Explanation: If an interval qualifier is specified after a subtraction expression, the operands of the expression must

be datetime values. The subtraction was being performed between values <insert_0> and <insert_1>.

Response: Ensure that the operands of the expression are datetime values.

BIP2426 Interval qualifier required for subtraction between values <insert_0> and <insert_1>.

Severity: 20 : Error

Explanation: When two datetime values are subtracted, an interval qualifier must be given. The subtraction was

being performed between values <insert_0> and <insert_1>.

Response: Ensure that a valid interval qualifier is specified.

124 Diagnostic messages

BIP2427 (<insert_0>, <insert_1>) : The left operand of <insert_2> operator is not a boolean expression.

Severity: 20 : Error

Explanation: The left operand of this operator must be a boolean expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2428 (<insert_0>, <insert_1>) : The right hand operand to operator <insert_2> is not a boolean expression.

Severity: 20 : Error

Explanation: The right hand operand to this operator must be a boolean expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2429 The left hand operand to the <insert_0> operator must evaluate to a boolean value.

Severity: 20 : Error

Explanation: The left hand operand to this operator is <insert_1>, which does not evaluate to a boolean value.

Response: Ensure that the left hand operand evaluates to a boolean value.

BIP2430 Illegal operands <insert_0> and <insert_1> for concatenation operator.

Severity: 20 : Error

Explanation: The operands for the concatenation operator were <insert_0> and <insert_1>. The concatenation

operator can only be applied between two character string values, two bit string values, or two byte string values.

Response: Correct the syntax of the expression and redeploy the message flow.

BIP2431 The right hand operand to the <insert_0> operator must evaluate to a boolean value.

Severity: 20 : Error

Explanation: The right hand operand to this operator is <insert_1>, which does not evaluate to a boolean value.

Response: Ensure that the right hand operand evaluates to a boolean value.

BIP2432 (<insert_0>, <insert_1>) : The correlation name <insert_2> is not valid. Those in scope are: <insert_3>.

Severity: 20 : Error

Explanation: The first element of a field reference must be a valid correlation name, from those in scope. This

message may sometimes be due to an incorrectly formed or spelled expression which is not intended to be a field

reference being parsed as if it were a field reference because the parser does not recognize it.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2433 (<insert_0>, <insert_1>) : Illegal result type for expression. Valid types are <insert_2>.

Severity: 20 : Error

Explanation: The expression must evaluate to a value of a suitable type. The given expression cannot possibly do

so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 125

BIP2434 (<insert_0>, <insert_1>) : <insert_4> field index expression does not evaluate to INTEGER value;

<insert_2> evaluates to <insert_3>.

Severity: 20 : Error

Explanation: A field index must be an INTEGER value. The expression <insert_2> evaluates to a value of type

<insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only expressions evaluating to INTEGER values are used to designate field

indexes with <insert_4>.

BIP2435 Array index evaluated to <insert_0>.

Severity: 20 : Error

Explanation: The array index expression must evaluate to a positive, nonzero integer value.

Response: Correct the logic of the program redeploy the message flow.

BIP2436 Invalid indexed assignment to <insert_0>.

Severity: 20 : Error

Explanation: No indexed elements from the named array exist. In order to assign a value to an element with index

n, where ’n’ is a positive integer, n-1 elements with the same name must already exist.

Response: Correct the logic of the program redeploy the message flow.

BIP2437 Invalid indexed assignment to element <insert_1>. Only <insert_0> elements already exist.

Severity: 20 : Error

Explanation: An attempt was made to assign a value to an element, but the index is out of range. In order to assign

a value to an element with index n, the element with index n-1 must already exist.

Response: Correct the logic of the program redeploy the message flow.

BIP2438 Path must specify a name.

Severity: 20 : Error

Explanation: The path element identifies a parser and thus must have a name (but no type).

Response: Correct the logic of the program redeploy the message flow.

BIP2439 (<insert_0>, <insert_1>) : Error evaluating expression <insert_2>.

Severity: 20 : Error

Explanation: An error occurred while evaluating an expression. Subsequent messages will contain more information

about the nature of the error.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the expression is correctly formed.

BIP2440 (<insert_0>, <insert_1>) : Invalid first operand for BETWEEN predicate.

Severity: 20 : Error

Explanation: The first operand of a BETWEEN predicate must be a scalar.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

126 Diagnostic messages

BIP2441 (<insert_0>, <insert_1>) : Invalid second operand for BETWEEN predicate.

Severity: 20 : Error

Explanation: The second operand of a BETWEEN predicate must be a scalar.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2442 (<insert_0>, <insert_1>) : Invalid third operand for BETWEEN predicate.

Severity: 20 : Error

Explanation: The third operand of a BETWEEN predicate must be a scalar.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2443 (<insert_0>, <insert_1>) : Incompatible first and second operands for BETWEEN predicate.

Severity: 20 : Error

Explanation: The first and second operands of a BETWEEN predicate must be compatible data types.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2444 (<insert_0>, <insert_1>) : Incompatible first and third operands for BETWEEN predicate.

Severity: 20 : Error

Explanation: The data types of the first and third operands of a BETWEEN predicate must be compatible data

types.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2445 (<insert_0>, <insert_1>) : Illegal operand for unary minus.

Severity: 20 : Error

Explanation: The unary minus operator can only be applied to numeric or interval operands.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2446 (<insert_0>, <insert_1>) : Illegal operand for unary minus applied to value <insert_2>.

Severity: 20 : Error

Explanation: The unary minus operator can only be applied to numeric or interval operands. An attempt was made

to apply the unary minus operator to an inappropriate value.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the unary minus is only applied to numeric or interval operands.

BIP2447 (<insert_0>, <insert_1>) : Illegal operand for NOT operator.

Severity: 20 : Error

Explanation: The operand for the NOT operator must be a boolean valued expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 127

BIP2448 (<insert_0>, <insert_1>) : Illegal operand for NOT operator applied to value <insert_2>.

Severity: 20 : Error

Explanation: The operand for the NOT operator must be a boolean expression. An attempt was made to apply the

NOT operator to an inappropriate value.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the NOT operator is only applied to boolean expressions.

BIP2449 Arithmetic overflow evaluating expression <insert_2>. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: The result of this expression was outside the valid range for the data type.

Response: Either supply smaller values as operands or use a data type capable of holding larger values.

BIP2450 Divide by zero evaluating expression <insert_2>. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: A divide by zero error occurred.

Response: Ensure that the second operand of the division operator cannot be zero.

BIP2451 Incompatible types <insert_0> and <insert_1> for operator <insert_2>.

Severity: 20 : Error

Explanation: An attempt was made to combine the values <insert_0> and <insert_1> using the operator <insert_2>.

Response: Ensure that the data types passed to this operator are compatible.

BIP2452 Overflow casting integer to interval; value <insert_0> exceeds the maximum of <insert_1>.

Severity: 20 : Error

Explanation: The integer had the value <insert_0>, which was greater that the maximum allowed of <insert_1>.

Response: Ensure that the magnitude of the integer value does not exceed the maximum.

BIP2453 Overflow casting double to integer; value <insert_0> outside of range [<insert_1>, <insert_2>].

Severity: 10 : Warning

Explanation: The double had the value <insert_0>, which was outside of the range [<insert_1>, <insert_2>].

Response: Ensure that the double value does not exceed the maximum.

BIP2454 (<insert_0>, <insert_1>) : Conflicting table references.

Severity: 20 : Error

Explanation: In this release, all table references occuring in the same FROM clause must specify the same database

and the same coordination.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2455 Error casting character string <insert_0> to boolean.

Severity: 20 : Error

Explanation: The character string had the value <insert_0>. Only the character strings ’TRUE’, ’FALSE’, and

’UNKNOWN’ can be cast to booleans.

Response: Ensure that the character string being cast has one of the above values.

128 Diagnostic messages

BIP2456 The value <insert_0> was of an unsuitable length for casting.

Severity: 20 : Error

Explanation: The operand of a casting operation was of an unsuitable length for it to be cast to the target data type.

For example, BIT operands must have a length divisible by 8 when casting to BLOB.

Response: Check the logic of the message flow and redeploy

BIP2457 Error casting character string <insert_0> to double.

Severity: 20 : Error

Explanation: The character string must be of the form ’[+/-]d+[.d+][Ed+]’. The character string had the value

<insert_0>.

Response: Ensure that the character string being cast represents a valid number.

BIP2458 Error casting character string <insert_2> to a TIME. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: A character string must have the form ’TIME ’hh:mm:ss[.f+]’’, or ’hh:mm:ss[.f+]’ for it to be castable to

a time value.

Response: Ensure that the string represents a valid time value.

BIP2459 Error casting character string <insert_0> to a GMT time.

Severity: 20 : Error

Explanation: The character string had the value <insert_0>. A character string must have the form ’GMTTIME

’hh:mm:ss[.f+]’’, or ’hh:mm:ss[.f+]’ for it to be castable to a GMT time value.

Response: Ensure that the character string being cast has a valid format.

BIP2460 Error casting character string <insert_2> to a DATE. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: A character string must have the form ’DATE ’yyyy-mm-dd’’, or ’yyyy-mm-dd’ for it to be castable to

a date.

Response: Ensure that the string being cast has a valid value.

BIP2461 Error casting character string <insert_2> to a TIMESTAMP. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: The character string must have a the form ’TIMESTAMP ’yyyy-mm-dd hh:mm:ss[.f+]’’, or

’yyyy-mm-dd hh:mm:ss[.f+]’ for it to be castable to a timestamp.

Response: Ensure that the string represents a valid time value.

BIP2462 Error casting character string <insert_0> to a GMT timestamp.

Severity: 20 : Error

Explanation: The character string had the value <insert_0>. A character string must have the form

’GMTTIMESTAMP ’yyyy-mm-dd hh:mm:ss[.f+]’’, or ’yyyy-mm-dd hh:mm:ss[.f]’ for it to be castable to a GMT

timestamp.

Response: Ensure that the string being cast is formatted correctly.

BIP2000 to BIP2999 (Broker) 129

BIP2463 Error casting the character string <insert_0> to an interval.

Severity: 20 : Error

Explanation: A character string must have the format ’INTERVAL ’<field values>’ <qualifier>’ or ’<field values>’ for

it to be cast to an interval. Valid field values depend on the qualifier. For example, for a DAY TO SECOND interval

the format is ’[<sign>]<day> <hour>:<minute>:<second>’. Note that all except the first field are required to have two

digits. Seconds however may also have a fractional part.

Response: Ensure the string being cast is formatted correctly. Consult the the documentation for more information

concerning field values and qualifiers.

BIP2464 Error casting interval <insert_0> to a numeric type.

Severity: 20 : Error

Explanation: An interval must have a qualifier which specifies only one field in order to be castable to a numeric

type.

Response: Ensure that the interval is of the appropriate type.

BIP2465 Can’t cast <insert_0> to the type <insert_1>.

Severity: 20 : Error

Explanation: There is no way to convert <insert_0> into the data type <insert_1>.

Response: Ensure that the source and target data types and values in the casting operation are compatible.

BIP2466 (<insert_0>, <insert_1>) : The target database <insert_2> does not have the same characteristics as the

reference database <insert_3>

Severity: 20 : Error

Explanation: All databases accessed from any one node must have the same characteristics regarding the functions

and data types they support. This is certainly true if they are of the same type and level (e.g. they are both DB2 v

8.2) but may not be true otherwise.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Examine the database names reported in this message. If they are not as expected, correct

the logic of the flow. If they are as expected, then either re-arrange the flow to use separate nodes for the accesses or

re-arrange the data into databases of the same type.

BIP2467 (<insert_0>, <insert_1>) : Incompatible operands for IN predicate.

Severity: 20 : Error

Explanation: The values on the right of an IN predicate must be compatible with the data type of the expression on

the left.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2468 (<insert_0>, <insert_1>) : Data type constraint violation. Actual = <insert_2> Expected = <insert_3>

Severity: 20 : Error

Explanation: A field reference containing a type constraint reported that the specified field did not contain a scalar

value of the required data type.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

130 Diagnostic messages

BIP2469 (<insert_0>, <insert_1>) : Invalid field reference constraint.

Severity: 20 : Error

Explanation: Scalar type constraints may not be applied to list field references, references to declared scalar

variables or to references to database tables. UNCOORDINATED may only be applied to references to database

tables. References to database tables may not have the list indicator [].

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2470 (<insert_0>, <insert_1>) : Illegal type for operand <insert_3> of the operator <insert_2>. Valid types are

<insert_4>.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2471 (<insert_0>, <insert_1>) : The value <insert_4> supplied as operand <insert_3> of the operator

<insert_2> is of an unsuitable type. Valid types are <insert_5>.

Severity: 20 : Error

Explanation: The expression supplying the operand must evaluate to a value of a suitable type. The given

expression does not so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2472 Zero rows updated. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: The database DELETE or UPDATE operation affected zero rows. This has been reported as an error as

″Treat warnings as errors″ is set.

Response: It is expected that this condition will be handled by the the message flow’s error recovery.

BIP2473 (<insert_0>, <insert_1>) : Invalid search condition.

Severity: 20 : Error

Explanation: A search condition must produce a boolean result.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2474 (<insert_0>, <insert_1>) : <insert_2> is not boolean.

Severity: 20 : Error

Explanation: A search condition evaluated to <insert_2>, which is not a boolean value. Search conditions must

evaluate to boolean values.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the search condition evaluates to a boolean.

BIP2000 to BIP2999 (Broker) 131

BIP2475 (<insert_0>, <insert_1>) : Illegal argument type for EXTRACT function.

Severity: 20 : Error

Explanation: The argument to the EXTRACT function must be a datetime or interval valued expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2476 (<insert_0>, <insert_1>) : Illegal argument type for EXTRACT function called with value <insert_2>.

Severity: 20 : Error

Explanation: The argument to the EXTRACT function must be a datetime or interval valued expression. The

EXTRACT function was called with the value <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the argument supplied to the EXTRACT function is a datetime or an interval.

BIP2477 (<insert_0>, <insert_1>) : Cannot extract <insert_2> field from value <insert_3>.

Severity: 20 : Error

Explanation: It was not possible to extract the specified field from the value supplied.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the value supplied contains the necessary information and is correctly

formed.

BIP2478 (<insert_0>, <insert_1>) : Path argument to <insert_2> must not specify a list.

Severity: 20 : Error

Explanation: The path argument supplied to the <insert_2> function must point to a single field only.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the path argument points to a single field.

BIP2479 (<insert_0>, <insert_1>) : Illegal argument value <insert_2> to ABS function.

Severity: 20 : Error

Explanation: The ABS function was called with the value <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the value passed to the ABS function is valid.

BIP2480 (<insert_0>, <insert_1>) : The dynamic field reference does not resolve to a reference to a message

field.

Severity: 20 : Error

Explanation: The dynamic field reference supplied must resolve to a message field. References to declared variables

and uninitialized references are not acceptable.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2481 (<insert_0>, <insert_1>) : Illegal argument value <insert_3> to <insert_2> function.

Severity: 20 : Error

Explanation: The argument to <insert_2> must be a numeric type. <insert_3> is not a numeric type.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only numeric types are passed as an argument to <insert_2>.

132 Diagnostic messages

BIP2482 (<insert_0>, <insert_1>) : The dynamic field reference does not resolve to a valid reference.

Severity: 20 : Error

Explanation: The dynamic field reference supplied must resolve to a decalred variable or a message field.

Uninitialized references are not acceptable.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2483 (<insert_0>, <insert_1>) : Illegal arguments (values <insert_2> and <insert_3>) to MOD function;

integers required.

Severity: 20 : Error

Explanation: Both arguments to the MOD function must be integral values. The function was called with the

arguments <insert_2> and <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only integral values are passed to the MOD function.

BIP2484 (<insert_0>, <insert_1>) : Syntax error. See further messages for details of the error.

Severity: 20 : Error

Explanation: Superficially the SQL program is syntactically correct. However a value (eg a date string) does not

have the correct format. See further messages for details of the error.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2485 (<insert_0>, <insert_1>) : Illegal 1st argument (value <insert_3>) to function <insert_2>; numeric value

required; value of 2nd argument was <insert_4>.

Severity: 20 : Error

Explanation: First argument to the function <insert_2> must be a numeric value. The function was called with the

values <insert_3>, <insert_4>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the first argument to <insert_2> is a numeric type.

BIP2486 (<insert_0>, <insert_1>) : Illegal 2nd argument to function <insert_2>; values supplied were <insert_3>

and <insert_4>.

Severity: 20 : Error

Explanation: Second argument to the function <insert_2> must be an integral value. The function was called with

the values <insert_3>, <insert_4>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the second argument to <insert_2> is an integral type.

BIP2487 (<insert_0>, <insert_1>) : Duplicate schema ’%3’.

Severity: 20 : Error

Explanation: A schema of this name has already been defined. Another schema with the same name cannot be

created. Neither can further items be added to the existing schema.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 133

BIP2488 (<insert_0>, <insert_1>) Error detected whilst executing the SQL statement <insert_2>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst executing the given statement. An exception has been

thrown to cut short the SQL program.

Response: See the following messages for details of the error.

BIP2489 (<insert_0>, <insert_1>) : The value <insert_4> is not valid as parameter <insert_3> of the function

<insert_2>. Valid types are <insert_5>.

Severity: 20 : Error

Explanation: The parameter must be a value of a suitable type within the range for which the function is defined.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2490 (<insert_0>, <insert_1>) : Illegal data type for parameter <insert_3> of statement, function or operator

<insert_2>. Valid types are <insert_4>.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2491 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> of the function <insert_2>. A field

reference is required.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2492 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> of the function <insert_2>. A non-list

field reference is required.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2493 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> of the function <insert_2>. A list is

required.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

134 Diagnostic messages

BIP2494 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> of the function <insert_2>. A reference

to a variable of type <insert_4> is required.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2495 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> or parameter <insert_4> of the function

<insert_2>. The types must be comparable.

Severity: 20 : Error

Explanation: The expressions supplying the parameters must evaluate to values of types which can be compared.

The given expressions cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2496 (<insert_0>, <insert_1>) : Illegal data type for target. A non-list field reference is required.

Severity: 20 : Error

Explanation: The expression supplying the target must evaluate to a value of a suitable type. The given expression

cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2497 (<insert_0>, <insert_1>) : Illegal data type for target. A list field reference is required.

Severity: 20 : Error

Explanation: The expression supplying the target must evaluate to a value of a suitable type. The given expression

cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2498 (<insert_0>, <insert_1>) : An error occurred whilst navigating to the <insert_2>th path element of the

field reference at the given location.

Severity: 20 : Error

Explanation: See further messages for details of the error.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2499 (<insert_0>, <insert_1>) : Illegal arguments to SUBSTRING function called as <insert_2>.

Severity: 20 : Error

Explanation: Valid syntax for SUBSTRING is: SUBSTRING( source_string FROM start_position [FOR string_length]).

The function was called as <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 135

BIP2501 (<insert_0>, <insert_1>) : The value <insert_4> supplied as parameter <insert_3> of the function

<insert_2> is of an unsuitable type. Valid types are <insert_5>.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression does not so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2502 (<insert_0>, <insert_1>) : Illegal value <insert_4> for parameter <insert_3> of the function <insert_2>.

Valid values are <insert_5>.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value within a suitable range. The given

expression does not do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2503 Invalid shared variable operation.

Severity: 20 : Error

Explanation: An SQL statement has attempted an operation involving shared variables which is outside the range

permitted. You cannot move (by using DETACH/ATTACH) a subtree from one shared variable to another. You

cannot use functions with side effects to change shared variables when the expression invoking the function also

operates on shared variables.

Response: Correct the logic of the ESQL program and re-deploy the message flow.

BIP2504 (<insert_0>, <insert_1>) : The value <insert_4> supplied as parameter <insert_3> of the function

<insert_2> and the value <insert_6> supplied as parameter <insert_5> must be of the same type.

Severity: 20 : Error

Explanation: The expressions supplying the parameters must evaluate to values of the same type. The given

expressions do not so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2505 (<insert_0>, <insert_1>) : Illegal type for parameter <insert_3> of the function <insert_2>. A list is

required.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression does not do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2506 (<insert_0>, <insert_1>) : An error occurred while attempting to cast <insert_2> and <insert_3> to

<insert_4>

Severity: 20 : Error

Explanation: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>,

then redeploy the message flow.

136 Diagnostic messages

BIP2507 (<insert_0>, <insert_1>) : An error occurred while attempting to cast <insert_2>, <insert_3> and

<insert_4> to <insert_5>

Severity: 20 : Error

Explanation: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>,

then redeploy the message flow.

BIP2508 (<insert_0>, <insert_1>) : An error occurred while attempting to cast <insert_2>, <insert_3>, <insert_4>

and <insert_5> to <insert_6>

Severity: 20 : Error

Explanation: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>,

then redeploy the message flow.

BIP2509 (<insert_0>, <insert_1>) : An error occurred while attempting to cast <insert_2>, <insert_3>, <insert_4>,

<insert_5>, <insert_6> and <insert_7> to <insert_8>

Severity: 20 : Error

Explanation: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>,

then redeploy the message flow.

BIP2510 (<insert_0>, <insert_1>) : The value <insert_3> supplied as the parameter of the function <insert_2> is

not within the range for which the function is defined.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a suitable value. The given expression does

not do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2511 (<insert_0>, <insert_1>) : The values <insert_3> and <insert_4> supplied as parameters of the function

<insert_2> are not within the range for which the function is defined.

Severity: 20 : Error

Explanation: The expressions supplying the parameters must evaluate to a suitable value. The given expressions do

not do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2512 An operand was of type <insert_0> which is not suitable for the given function.

Severity: 20 : Error

Explanation: Correct the syntax of the SQL program and re-deploy.

BIP2513 Cannot construct a <insert_1> interval from <insert_0> parameters.

Severity: 20 : Error

Explanation: Correct the syntax of the SQL program and re-deploy.

BIP2514 Cannot construct a <insert_0> interval from the values <insert_1> and <insert_2>

Severity: 20 : Error

Explanation: Correct the syntax of the SQL program and re-deploy.

BIP2000 to BIP2999 (Broker) 137

BIP2515 (<insert_0>, <insert_1>) : Illegal trim character <insert_2> argument to TRIM function.

Severity: 20 : Error

Explanation: The trim character argument to the TRIM function must be a character string, a byte string or a bit

string, and must be of length 1. The trim character argument was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the trim character argument is an appropriate data type and length.

BIP2516 Cannot construct a <insert_0> interval from the values <insert_1>, <insert_2>, <insert_3> and

<insert_4>

Severity: 20 : Error

Explanation: Correct the syntax of the SQL program and re-deploy.

BIP2517 (<insert_0>, <insert_1>) : Variable <insert_2> has already been declared in the current scope.

Severity: 20 : Error

Explanation: An attempt was made to declare the variable <insert_2>, but this variable has already been declared

within the current scope. You cannot declare the same variable more than once within the same scope.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Remove the second declaration, or substitute a different variable name, and redeploy the

message flow.

BIP2518 Invalid value <insert_0> for <insert_1> field of INTERVAL.

Severity: 20 : Error

Explanation: <insert_0> is not a valid value for the <insert_1> field of an INTERVAL value.

Response: Ensure that only valid values for each of the INTERVAL fields are used to construct INTERVAL values.

BIP2519 (<insert_0>, <insert_1>) : A non scalar parameter was passed to statement <insert_3> against

datasource <insert_2>.

Severity: 20 : Error

Explanation: Only scalar parameters may be passed to stored procedures

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2520 (<insert_0>, <insert_1>) : Nested BEGIN ATOMIC statements.

Severity: 20 : Error

Explanation: The broker has detected an attempt to execute a BEGIN ATOMIC statement within the scope of

another BEGIN ATOMIC statement. This is not allowed as it may lead to deadly embraces.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2521 (<insert_0>, <insert_1>) : Error casting the value <insert_2> to <insert_3>.

Severity: 20 : Error

Explanation: An error occurred when casting a value to a different data type. This may be because no conversions

exist between the two data types or because the particular value was unsuitable.

Response: Subsequent messages will indicate the context of the error.

138 Diagnostic messages

BIP2522 (<insert_0>, <insert_1>) : Type mismatch in CASE expression.

Severity: 20 : Error

Explanation: The WHEN clause of a simple CASE expression must be compatible with the CASE clause.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2523 (<insert_0>, <insert_1>) : Cannot assign to a symbolic constant or input message.

Severity: 20 : Error

Explanation: Values cannot be assigned to symbolic constants or input message fields.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2524 (<insert_0>, <insert_1>) : Cannot assign a list to a non-list, nor a non-list to a list.

Severity: 20 : Error

Explanation: A list of values cannot be assigned to a scalar variable or single message field, nor can a scalar value

be assigned to a list.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2525 Error casting character string <insert_0> to an interval with qualifier <insert_1>.

Severity: 20 : Error

Explanation: The character string had the value <insert_0> which was not a valid representation of an interval with

qualifier <insert_1>. A character string must have the format ’INTERVAL ’<field values>’ <qualifier>’ or ’<value>’ for

it to be casted to an interval. Valid field values may depend on the qualifier.

Response: Ensure the string being cast is formatted correctly. Consult the manual, ’ESQL Reference’ for more

information concerning field values and qualifiers.

BIP2526 (<insert_0>, <insert_1>) : Illegal ATOMIC block usage.

Severity: 20 : Error

Explanation: The program is attempting an operation which may result in an atomic block being entered when

higher level code is already inside an atomic block. This is not allowed as it may result in deadlocks. This situation

may arise through code within an atomic block calling a function or procedure which also contains an atomic block.

It can also arise as a result of a the use of a PROPAGATE statement within an atomic block.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2527 (<insert_0>, <insert_1>) : The datasource <insert_2> does not support the data type <insert_3>.

Severity: 20 : Error

Explanation: The datasource <insert_2> does not support the data type <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Rewrite your expression to avoid the use of this data type, or connect to a different

datasource.

BIP2000 to BIP2999 (Broker) 139

BIP2528 (<insert_0>, <insert_1>) : Data type <insert_2> not supported for database interaction.

Severity: 20 : Error

Explanation: The data type <insert_2> cannot be passed to a database.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Do not attempt to pass values with this data type to the database.

BIP2529 (<insert_0>, <insert_1>) : The datasource <insert_2> does not support CASE expressions.

Severity: 20 : Error

Explanation: CASE expressions are not supported by this data source.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Rewrite the expression to avoid use of CASE, or connect to a different data source.

BIP2530 (<insert_0>, <insert_1>) : The datasource <insert_2> does not support the BETWEEN predicate.

Severity: 20 : Error

Explanation: BETWEEN is not supported by this data source.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Rewrite the expression to avoid use of BETWEEN, or connect to a different data source.

BIP2531 (<insert_0>, <insert_1>) : The datasource <insert_2> does not support the IN predicate.

Severity: 20 : Error

Explanation: IN is not supported by this data source.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Rewrite the expression to avoid use of IN, or connect to a different data source.

BIP2532 (<insert_0>, <insert_1>) : The datasource <insert_2> does not support the LIKE predicate.

Severity: 20 : Error

Explanation: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>,

then redeploy the message flow: Rewrite the expression to avoid use of LIKE, or connect to a different data source.

BIP2533 (<insert_0>, <insert_1>) : The data type <insert_2> is not a valid data type for parameter <insert_3> of

the <insert_4> function. This parameter should be of data type <insert_5>. The value passed was

<insert_6>.

Severity: 20 : Error

Explanation: Parameter <insert_3> is not of the correct data type for this function ( <insert_4> ).

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the argument(s) passed to this function are of the correct data type.

BIP2534 (<insert_0>, <insert_1>) : The dynamic field reference does not resolve to a modifiable quantity.

Severity: 20 : Error

Explanation: The dynamic field reference supplied must resolve to a modifyable quantity (a declared variable or a

field in a modifyable message) as the usage implies that its value is to be changed.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

140 Diagnostic messages

BIP2535 (<insert_0>, <insert_1>) : Field reference does not represent a database column.

Severity: 20 : Error

Explanation: A field reference which represents a database column must consist of at least two elements, the first of

which must be ’Database’.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2536 (<insert_0>, <insert_1>) : The dynamic field reference supplied to the <insert_2> statement does not

resolve to a non-list field in a modifiable message tree.

Severity: 20 : Error

Explanation: The dynamic field reference supplied to the <insert_2> statement must resolve to a non-list field in a

modifiable message tree.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only non-list references to modifiable trees are passed to the <insert_2>

statement.

BIP2537 Node <insert_3>: Executing statement <insert_2> at (<insert_0>, <insert_1>).

Severity: 0 : Information

BIP2538 Node <insert_3>: Evaluating expression <insert_2> at (<insert_0>, <insert_1>).

Severity: 0 : Information

BIP2539 Node <insert_5>: Evaluating expression <insert_4> at (<insert_0>, <insert_1>). This resolved to

<insert_2>. The result was <insert_3>.

Severity: 0 : Information

BIP2540 Node <insert_4>: Finished evaluating expression <insert_3> at (<insert_0>, <insert_1>). The result was

<insert_2>.

Severity: 0 : Information

BIP2541 Node <insert_5>: (<insert_0>, <insert_1>) : Comparing <insert_2> and <insert_3>; result is <insert_4>.

Severity: 0 : Information

BIP2542 Node <insert_2>: (<insert_0>, <insert_1>) : Navigating path element.

Severity: 0 : Information

Explanation: No user action required.

BIP2543 Node <insert_3>: (<insert_0>, <insert_1>) : Failed to navigate to path element number <insert_2>

because it does not exist.

Severity: 0 : Information

BIP2544 Node <insert_5>: Executing database SQL statement <insert_2> derived from (<insert_0>, <insert_1>);

expressions <insert_3>; resulting parameter values <insert_4>.

Severity: 0 : Information

BIP2000 to BIP2999 (Broker) 141

BIP2545 (<insert_0>, <insert_1>) : The expression <insert_2> evaluates to a value of type <insert_3> but a value

of type <insert_4> is expected.

Severity: 20 : Error

Explanation: The given expression evaluates to NULL or to a data type which is not acceptable for its usage.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2546 (<insert_0>, <insert_1>) : <insert_4> field type expression does not evaluate to INTEGER value;

<insert_2> evaluates to <insert_3>.

Severity: 20 : Error

Explanation: A field type must be an INTEGER value. The expression <insert_2> evaluates to a value of type

<insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only expressions evaluating to INTEGER values are used to designate field

types with <insert_4>.

BIP2547 (<insert_0>, <insert_1>) : <insert_2> field name expression cannot evaluate to a CHARACTER value.

Severity: 20 : Error

Explanation: A field name must be a CHARACTER value. The expression supplied to <insert_2> cannot evaluate to

a CHARACTER value.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2548 (<insert_0>, <insert_1>) : A correlation name must be given.

Severity: 20 : Error

Explanation: Database tables must be assigned a correlation name in the FROM clause of a SELECT statement. This

correlation name must then be used for subsequent references to that table.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2549 (<insert_0>, <insert_1>) : Type mismatch assigning to variable; value <insert_2> inconsistent with type

<insert_3>.

Severity: 20 : Error

Explanation: The source expression produced a value of <insert_2> but the target variable was declared with a type

of <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that only values of the appropriate data type are assigned to declared variables.

BIP2550 The first parameter of a PASSTHRU or EVAL function cannot evaluate to a list.

Severity: 20 : Error

Explanation: The first parameter of a PASSTHRU or EVAL function must evaluate to something that can be

represented as a character string.

Response: Check the first parameter of the PASSTHRU or EVAL function. Ensure that it is not an expression that

will evaluate to a list of values.

142 Diagnostic messages

BIP2551 (<insert_0>, <insert_1>) : The number <insert_2> was too large for an INTEGER or DECIMAL literal.

Severity: 20 : Error

Explanation: The number was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure the number is within the scale and precision limits for the specified data type and

redeploy the message flow.

BIP2552 (<insert_0>, <insert_1>) : The number being converted <insert_2> was too large/small to be

represented as a 64 bit floating point number.

Severity: 20 : Error

Explanation: The number being converted was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the number being converted is within the scale and precision limits for a 64

bit floating point number and redeploy the message flow.

BIP2553 (<insert_0>, <insert_1>) : Unexpected character <insert_2> in input.

Severity: 20 : Error

Explanation: The character was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2554 (<insert_0>, <insert_1>) : Unrecognized character <insert_2> in input.

Severity: 20 : Error

Explanation: The character was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2555 Error casting a character string <insert_0> to an interval (qualifier <insert_1>).

Severity: 20 : Error

Explanation: The interval qualifier given on the cast specification didn’t match the interval qualifier in the source

character string. The character string had the value <insert_0>. The interval qualifier given in the cast specification

was <insert_1>.

Response: See the documentation for details of which combinations of character strings and qualifiers are

acceptable.

BIP2556 An attempt has been made to assign a scalar, row or list quantity to a target of a different basic

type.

Severity: 20 : Error

Explanation: Scalar values may only be assigned to scalars, rows may only be assigned to rows and lists may only

be assigned to lists.

Response: Check and correct the ESQL program. Pay particular attention to SELECT functions. Normally these

return a list. However SELECT’s containing a THE clause return a row.

BIP2000 to BIP2999 (Broker) 143

BIP2557 (<insert_0>, <insert_1>) : Invalid function name.

Severity: 20 : Error

Explanation: Function names must be simple identifier chains and may not contain namespace identifiers or

expressions of any kind.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2558 (<insert_0>, <insert_1>) : Undefined function <insert_2>.<insert_3>.

Severity: 20 : Error

Explanation: The program is attempting to call a function which is not defined or is not in the schema path.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2559 (<insert_0>, <insert_1>) : Illegal argument(s) <insert_3> to <insert_2> function.

Severity: 20 : Error

Explanation: The arguments to the bit manipulation functions (BITAND, BITOR, BITNOT, BITXOR) must be

integers. The function was called with arguments <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2560 (<insert_0>, <insert_1>) : A reference variable is required here.

Severity: 20 : Error

Explanation: The statement or function requires a reference variable. The name given must therefore be the name of

a declared reference variable and may not be extended (ie by a dot and another name)

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2561 (<insert_0>, <insert_1>) : An attempt was made to call the function <insert_2>()’ with <insert_3>

parameters but this function requires <insert_4> parameters.

Severity: 20 : Error

Explanation: Most functions must be called with the correct number of arguments. Others will accept any number

of arguments above a given minimum.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2562 Node <insert_1>: Assigning a list to <insert_0>.

Severity: 0 : Information

BIP2563 Node <insert_2>: Deleting all <insert_0> instances of <insert_1>, since source list for assignment was

empty.

Severity: 0 : Information

BIP2564 Node <insert_3>: Deleting instance <insert_0> of <insert_1>, since source list for assignment had

<insert_2> instances.

Severity: 0 : Information

144 Diagnostic messages

BIP2565 Node <insert_4>: Deleting instances <insert_0> through <insert_1> of <insert_2>, since source list for

assignment had <insert_3> instances.

Severity: 0 : Information

BIP2566 Node <insert_2>: Assigning value <insert_0> to field / variable <insert_1>.

Severity: 0 : Information

BIP2567 Node <insert_1>: Assigning NULL to <insert_0>, thus deleting it.

Severity: 0 : Information

BIP2568 Node <insert_2>: Copying sub-tree from <insert_0> to <insert_1>.

Severity: 0 : Information

BIP2569 Node <insert_2>: (<insert_0>, <insert_1>) : WHERE clause evaluated to false or unknown. Iterating

FROM clause.

Severity: 10 : Warning

BIP2570 Node <insert_2>: (<insert_0>, <insert_1>) : There were no items in the FROM clause satisfying the

WHERE clause.

Severity: 10 : Warning

BIP2571 Node <insert_2>: (<insert_0>, <insert_1>) : Failed to find any more items in the FROM clause

satisfying the WHERE clause.

Severity: 10 : Warning

BIP2572 Node: <insert_2>: (<insert_0>, <insert_1>) : Finding one and only SELECT result.

Severity: 10 : Warning

BIP2573 Node <insert_2>: (<insert_0>, <insert_1>) : Finding first SELECT result.

Severity: 10 : Warning

BIP2574 Node <insert_2>: (<insert_0>, <insert_1>) : Finding next SELECT result.

Severity: 10 : Warning

BIP2575 A Filter expression must evaluate to the <insert_0> data type.

Severity: 20 : Error

Explanation: The expression given in the ’filterExpression’ attribute of a Filter node must evaluate to a <insert_0>

type value.

Response: Correct the expression so that it returns a value of the correct type and redeploy the message flow.

BIP2576 The expression in a Filter node resulted in the value <insert_0>; boolean value expected.

Severity: 20 : Error

Explanation: The filterExpression configuring a Filter node must evaluate to a boolean value. The filterExpression

resulted in the value <insert_0>.

Response: Correct the expression so that it always returns a value of the correct type.

BIP2000 to BIP2999 (Broker) 145

BIP2577 (<insert_0>, <insert_1>) : <insert_2> field type expression cannot evaluate to INTEGER.

Severity: 20 : Error

Explanation: A field type must be an INTEGER value. The field type expression supplied to <insert_2> cannot

evaluate to INTEGER.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2578 (<insert_0>, <insert_1>) : Dynamic field reference <insert_2> is not detached and therefore cannot be

attached to <insert_3>.

Severity: 20 : Error

Explanation: The message tree fragment pointed to by the dynamic field reference <insert_2> has not been detached.

Only message tree fragments which are detached can be attached to another message tree.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that you detach the message tree fragment before attempting to reattach it

elsewhere.

BIP2579 (<insert_0>, <insert_1>) : The function <insert_2> was not known.

Severity: 20 : Error

Explanation: <insert_2> was not known as a function.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Rewrite the SQL expression so that the condition does not occur.

BIP2580 (<insert_0>, <insert_1>) : No external data source specified for this node.

Severity: 20 : Error

Explanation: An attempt was made to access an external database table, but no database inputs have been specified

for this Compute, Filter or Database node.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Add database inputs for each table that is accessed, and redeploy the message flow.

BIP2581 (<insert_0>, <insert_1>) : Field reference <insert_2> does not exist and could not be created when

declaring <insert_3>.

Severity: 20 : Error

Explanation: A dynamic field reference may not point to a nonexistent target. The target field reference <insert_2>

specified for the declaration of dynamic field reference <insert_3> does not exist and could not be created.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: When declaring a dynamic field reference ensure that the specified target either exists or

can be created.

BIP2582 (<insert_0>, <insert_1>) : The argument <insert_2> passed to the function <insert_3> is not a valid

UUID

Severity: 20 : Error

Explanation: The argument <insert_2> is not a valid UUID.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the argument passed to this function is valid

146 Diagnostic messages

BIP2583 (<insert_0>,<insert_1>) : Expected a dynamic directional modifier but found <insert_2>.

Severity: 20 : Error

Explanation: One of FIRSTCHILD, LASTCHILD, NEXTSIBLING or PREVIOUSSIBLING was expected but <insert_2>

was found.

Response: Correct the expression and redeploy the message flow.

BIP2584 Cannot add interval <insert_1> to time value <insert_0>.

Severity: 20 : Error

Explanation: The interval value is not suitable because it contains one of the fields YEAR, MONTH or DAY.

Response: No user action required.

BIP2585 Invalid interval qualifier for time subtraction, subtracting <insert_1> from <insert_0> with qualifier

<insert_2>.

Severity: 20 : Error

Explanation: When giving an interval qualifier for the precision of a time subtraction, the qualifier must not contain

any of the fields YEAR, MONTH or DAY.

Response: Correct the logic of the SQL program redeploy the message flow.

BIP2586 Cannot add interval <insert_1> to date value <insert_0>.

Severity: 20 : Error

Explanation: The interval value is not suitable because it contains one of the fields HOUR, MINUTE, SECOND.

Response: No user action required.

BIP2587 Invalid interval qualifier for date subtraction, subtracting <insert_1> from <insert_0> with qualifier

<insert_2>.

Severity: 20 : Error

Explanation: When giving an interval qualifier for the precision of a date subtraction, the qualifier must not contain

any of the fields HOUR, MINUTE or SECOND.

Response: Correct the logic of the SQL program redeploy the message flow.

BIP2588 Node <insert_3>: (<insert_0>, <insert_1>) : Evaluating string <insert_2> as an SQL statement or

expression.

Severity: 0 : Information

BIP2589 Incompatible types for comparison between values <insert_0> and <insert_1>.

Severity: 20 : Error

Explanation: The values <insert_0> and <insert_1> cannot be compared, because they are of incompatible types.

Response: Other messages will give an indication of context of this error.

BIP2590 Error casting character string <insert_0> to a byte string.

Severity: 20 : Error

Explanation: An attempt was made to cast the character string <insert_0> to a byte string, but the string was of the

wrong format. There must be an even number of hexadecimal digits (0-9, a-f, A-F).

Response: Other messages will give an indication of context of this error.

BIP2000 to BIP2999 (Broker) 147

BIP2591 Error casting character string <insert_0> to a bit string.

Severity: 20 : Error

Explanation: An attempt was made to cast the character string <insert_0> to a bit string, but the string was of the

wrong format. The string must consist only of the characters ’0’ and ’1’.

Response: Other messages will give an indication of context of this error.

BIP2592 Error converting character string <insert_2> to decimal. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: An attempt was made to convert a character string to a decimal, but the string was of the wrong

format. The string must be of the form [<sign>]<digits>[.<digits>][[<sign>]E<digits>] where <sign> can be one of ’+’

or ’-’ and <digits> are one or more decimal digits (0-9). The E can be of either case. This string may be both

preceeded and followed by any number of blanks but no blanks may occur within the given format. The maximum

precision is 34 digits and the maximum exponent is 999,999,999.

Response: Other messages will give an indication of context of this error.

BIP2593 Error converting decimal <insert_2> to integer. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: An attempt was made to convert a decimal number to an integer but the given number could not be

converted. This could be because it is too big to be represented as an integer, the number the number has one of the

special values NAN or INFINITY or because the number had a fractional part and the operation was one which does

not allow the rounding of fractions.

Response: Other messages will give an indication of context of this error.

BIP2594 Error converting decimal <insert_2> to float. State = <insert_0> <insert_1> ’0’ ’’

Severity: 20 : Error

Explanation: An attempt was made to convert a decimal number to a float but the given number could not be

converted. This could either be because it is too big to be represented as a float or because the number the number

has one of the special values NAN or INFINITY.

Response: Other messages will give an indication of context of this error.

BIP2595 Error casting character string <insert_0> to an integer.

Severity: 20 : Error

Explanation: An attempt was made to cast the character string <insert_0> to an integer, but the string was of the

wrong format.

Response: Other messages will give an indication of context of this error.

BIP2596 (<insert_0>, <insert_1>) : Cannot take bitstream of partially complete output.

Severity: 20 : Error

Explanation: The BITSTREAM function can only be used with input messages.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2597 (<insert_0>, <insert_1>) : An expression which evaluates to a scalar value is required here.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

148 Diagnostic messages

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2598 Error scaling decimal. Attempted precision <insert_2> scale <insert_3>. State = <insert_0> <insert_1>

’0’ ’’

Severity: 20 : Error

Explanation: An attempt was made to convert a decimal value to a precision or scale which are beyond the limits of

the decimal data type. The maximum precision is 34 the maximum scale is 999,999,999

Response: Other messages will give an indication of the context of this error.

BIP2599 The ESQL deployed to the node <insert_0> is invalid.

Severity: 20 : Error

Explanation: The message could not be processed because the ESQL deployed to the node is invalid. Examine

previous error messages for details of the problem.

Response: Correct the logic of the ESQL program and re-deploy the message flow.

BIP2601 Unable to locate the WebSphere MQ manager class required by node <insert_0>.

Severity: 20 : Error

Explanation: The instance of the WebSphere MQ manager class could not be located when required by node

<insert_0>. The current message flow has been terminated. This error is probably indicative of an internal software

malfunction.

Response: If this occurs frequently, restart the message broker. If it continues to occur, contact your IBM support

center.

BIP2602 Unable to create thread context in message flow node <insert_0>.

Severity: 20 : Error

Explanation: During the execution of a message flow in node <insert_0>, a new thread was created. However, a

context data area could not be created for this thread. The current message flow is terminated.

Response: This may be indicative of a shortage of virtual memory. If other error messages seem to indicate this may

be the reason, then consider reducing the memory requirements for the system, or increase the amount of physical

and/or virtual memory available. If lack of storage does not seem to be the reason, and this problem occurs

continually contact your IBM support center.

BIP2603 Unable to insert thread context into list for message flow node <insert_0>.

Severity: 20 : Error

Explanation: During the execution of a message flow in node <insert_0>, a new thread was created. However, the

context data area could not be inserted into the list of contexts. The current message flow is terminated.

Response: This may be indicative of a shortage of virtual memory. If other error messages seem to indicate this may

be the reason, then consider reducing the memory requirements for the system, or increase the amount of physical

and/or virtual memory available. If lack of storage does not seem to be the reason, and this problem occurs

continually contact your IBM support center.

BIP2604 Node failed to open WebSphere MQ queue <insert_1> owned by queue manager <insert_0>:

completion code <insert_2>; reason code <insert_3>.

Severity: 20 : Error

Explanation: A message flow node failed to open the indicated WebSphere MQ queue, with the resulting

WebSphere MQ completion and reason codes. The message flow attempts to open the queue periodically until the

queue is defined. The message flow is not fully operational until this has been done.

BIP2000 to BIP2999 (Broker) 149

Response: Define the WebSphere MQ queue to the indicated queue manager. If the incorrect queue manager and/or

queue name were specified, then correct the queue name using the Message Brokers Toolkit and redeploy the

message broker.

BIP2605 Unable to start transaction coordinated by WebSphere MQ; MQBEGIN failed; MQCC=<insert_1>,

MQRC=<insert_2>, broker node <insert_3>, queue manager <insert_0>.

Severity: 20 : Error

Explanation: The message flow attribute ’coordinatedTransaction’ was specified as ’yes’. However, when the broker

node <insert_3> reading from queue manager <insert_0> attempted to start the coordinated transaction, the

MQBEGIN operation failed with the indicated WebSphere MQ reason code. The message flow continues, but the

transaction will not be coordinated, and this may cause subsequent errors or unpredictable results.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2606 Unable to get message from WebSphere MQ queue <insert_0>: MQCC=<insert_1>;

MQRC=<insert_2>; node <insert_3>.

Severity: 20 : Error

Explanation: A node <insert_3> failed to get a message from WebSphere MQ queue <insert_0> using the MQGET

function. The WebSphere MQ return code and reason code returned are as displayed. The node periodically retries

the MQGET until it is successful.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2607 Unable to rollback a WebSphere MQ transaction; MQBACK failed; queue manager=<insert_0>,

MQCC=<insert_1>, MQRC=<insert_2>; message flow node <insert_3>.

Severity: 20 : Error

Explanation: Message flow node <insert_3> attempted to rollback a WebSphere MQ unit of work using the

MQBACK function, but the rollback failed. The WebSphere MQ return code and reason code returned from

MQBACK are displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2608 Unable to inquire on WebSphere MQ queue <insert_0>: MQCC=<insert_1>; MQRC=<insert_2>; node

<insert_3>.

Severity: 20 : Error

Explanation: Node <insert_3> issued an MQINQ function to inquire about the status of queue <insert_0> but the

inquire failed. The WebSphere MQ completion code and reason code returned are as displayed. Recovery processing

of a backed out message may not work as expected.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2609 Unable to open WebSphere MQ queue manager <insert_2> for inquire: MQCC=<insert_0>;

MQRC=<insert_1>; node <insert_3>.

Severity: 20 : Error

Explanation: An attempt to open the named connected WebSphere MQ queue manager <insert_2> failed when

inquiring about its object attributes, during the processing of node <insert_3>. The WebSphere MQ completion and

reason codes are as displayed.

150 Diagnostic messages

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action. Recovery processing of a backed out message may not

work as expected.

BIP2610 Unable to close WebSphere MQ queue manager object: MQCC=<insert_0>; MQRC=<insert_1>; node

<insert_2>.

Severity: 20 : Error

Explanation: An attempt by node <insert_2> to close the connected WebSphere MQ queue manager failed. The

WebSphere MQ completion code and reason code returned are as displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2611 Unable to open WebSphere MQ backout requeue queue: queue manager=<insert_0>;

queue=<insert_1>; MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.

Severity: 20 : Error

Explanation: The message flow node <insert_4> was unable to open or get the backout requeue queue to backout a

WebSphere MQ message, with the indicated WebSphere MQ completion and reason codes. The message may not be

backed out as intended.

Response: If there is a previous message, take any recovery action described for that error. Otherwise examine the

WebSphere MQ completion and reason codes and take appropriate action.

BIP2612 Unable to open WebSphere MQ dead letter queue: queue manager=<insert_0>; queue=<insert_1>;

MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.

Severity: 20 : Error

Explanation: The message flow node <insert_4> was unable to open or get the WebSphere MQ dead letter queue to

backout a WebSphere MQ message, with the indicated WebSphere MQ completion and reason codes. A previous

message may provide further information. The message may not be backed out as intended.

Response: If there is a previous message, take any recovery action described for that error. Otherwise examine the

WebSphere MQ completion and reason codes and take appropriate action.

BIP2613 Unable to backout a message; MQPUT to queue <insert_0> failed: MQCC=<insert_1>;

MQRC=<insert_2>; message flow node <insert_3>.

Severity: 20 : Error

Explanation: The message flow node <insert_3> was unable to backout a message as it failed to put it to either the

backout requeue queue or the WebSphere MQ dead letter queue, defined as queue <insert_0>.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2614 Unable to commit a WebSphere MQ transaction to backout; MQCMIT failed;

queueName=<insert_0>, MQCC=<insert_1>, MQRC=<insert_2>.

Severity: 20 : Error

Explanation: The specified node was unable to commit a WebSphere MQ unit of work where the message needed to

be backed out, because the MQCMIT function failed. The state of the message flow and any messages processed

within the unit of work may be unpredictable, depending on the reason for the WebSphere MQ error.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2000 to BIP2999 (Broker) 151

BIP2615 The WebSphere MQ input node <insert_0> has backed out the message to the backout requeue or

the dead letter queue.

Severity: 0 : Information

Explanation: Message backout processing has been invoked, and the message has either been backed out by being

written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue

configuration.

Response: No user action required.

BIP2616 Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=<insert_0>,

MQCC=<insert_1>, MQRC=<insert_2>.

Severity: 20 : Error

Explanation: The message broker was unable to commit a WebSphere MQ unit of work because the MQCMIT

function failed. The state of any messages processed within the unit of work may be unpredictable, depending on the

reason for the WebSphere MQ error.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2617 Output message is empty; output node <insert_0>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers output node <insert_0> has received a message to write to an

WebSphere output queue, but the message appears to be empty. This error may be generated when 1) there is no

MQMD and no message content in the output bitstream (there really is no data) or 2) there is no MQMD and the size

of the message content is less that the size of the MQMD (it appears there is no content). This situation can occur

when a output message is built incorrectly using the Compute node.

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy the broker.

BIP2618 Output message does not contain a valid MQMD; output node <insert_0>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers output node <insert_0> has received a message to write to an

WebSphere output queue, but the message does not contain a valid MQMD. This situation can occur when a output

message is built incorrectly using the Compute node.

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy the broker.

BIP2619 Output node <insert_0> expected a distribution list but one did not exist.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers output node <insert_0> was invoked and the Destination Mode

property was set to ″list″. However, a valid distribution list was not found.

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy the broker.

BIP2620 Unable to write message to queue <insert_1> on queue manager <insert_0>. MQPUT failed:

MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.

Severity: 20 : Error

Explanation: The message flow node <insert_4> was unable to write a WebSphere MQ message as it failed to put it

to the queue <insert_1> belonging to queue manager <insert_0>. The completion and reason code from the MQPUT

operation are as displayed.

152 Diagnostic messages

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2621 Conversion error occurred with value <insert_0> for message flow node <insert_1>.

Severity: 20 : Error

Explanation: The message flow node <insert_1> was unable to convert the specified value to a multi byte character

string. The current message flow is terminated.

Response: Check the message flow to determine the cause of the error.

BIP2622 Message successfully output by output node <insert_2> to queue <insert_1> on queue manager

<insert_0>.

Severity: 0 : Information

BIP2623 Unable to open queue <insert_1> on WebSphere MQ queue manager <insert_0>: completion code

<insert_2>; reason code <insert_3>.

Severity: 20 : Error

Explanation: A message flow node failed to open the indicated WebSphere MQ message queue. The error codes

relate to the MQOPEN call.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action. If the open failed because the queue manager or

queue did not exist, define these objects to WebSphere MQ. If the failure of the open was because incorrect object

names were specified, correct the message flow configuration and attempt to redeploy the message broker.

BIP2624 Unable to connect to queue manager <insert_0>: MQCC=<insert_1>; MQRC=<insert_2>; message flow

node <insert_3>.

Severity: 20 : Error

Explanation: The message flow node <insert_3> failed to connect to the WebSphere MQ queue manager <insert_0>.

The return and reason codes returned by the MQCONN are as displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference online help to establish the cause of the error, taking any appropriate action. It may be necessary to restart

the message broker after you have performed this recovery action. If the open failed because the queue manager did

not exist, define this object to WebSphere MQ. If the failure of the open was because an incorrect queue manager

name was specified, correct the message flow configuration and attempt to redeploy the message broker.

BIP2625 Warning when writing message to queue <insert_1> on queue manager <insert_0>. MQPUT warning:

MQCC=<insert_2>; MQRC=<insert_3>; message flow node <insert_4>.

Severity: 20 : Error

Explanation: The message flow node <insert_4> received a warning when writing a WebSphere MQ message to

queue <insert_1> owned by queue manager <insert_0>; however, the message was successfully queued. The return

and reason code from the MQPUT are as displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2000 to BIP2999 (Broker) 153

BIP2626 Unable to open queue. Queue manager name <insert_0> is too long; node <insert_1>.

Severity: 20 : Error

Explanation: The node <insert_1> failed to open a WebSphere MQ queue as the specified queue manager name

<insert_0> was longer than the maximum size allowed by WebSphere MQ.

Response: Correct the message flow configuration and redeploy the message broker.

BIP2627 Unable to open queue <insert_0>: name is too long; node <insert_1>.

Severity: 20 : Error

Explanation: The node <insert_1> failed to open a WebSphere MQ queue as the specified queue name <insert_0>

was longer than the maximum size allowed by WebSphere MQ.

Response: Correct the message flow configuration and redeploy the message broker.

BIP2628 Exception condition detected on input node <insert_0>.

Severity: 20 : Error

Explanation: The input node <insert_0> detected an error whilst processing a message. The message flow has been

rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be

processed again. Following messages will indicate the cause of this exception.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP2629 Broker termination request received.

Severity: 0 : Information

Explanation: A request was received to terminate the message broker.

Response: No user action required.

BIP2630 No backout queue or DLQ defined for a message to be backed out; input node <insert_1> received

from queue <insert_0>

Severity: 0 : Information

Explanation: The input node <insert_1> received a message from queue <insert_0>, but was forced to attempt a

backout due to the detection of an internal failure condition associated with it. The message broker has now

attempted to propagate the message to the ’backoutRequeueQueueName’ or the dead letter queue, but neither of

these queues exist. The message is no longer processed by the message flow and continues to be backed out

periodically. This situation can cause other messages to build up on the input queue until this message is removed or

successfully processed.

Response: Examine previous messages and possibly the message flow to determine why the message is being

backed out. Defining either the ’backoutRequeueQueue’ or the dead letter queue will cause the message to be

propagated to one of those queues.

BIP2631 Backed out message being propagated to failure terminal; node <insert_0>.

Severity: 0 : Information

Explanation: Node <insert_0> has received a message which has previously been backed out because of a processing

error in the message flow. The MQMD ’backoutCount’ of the message exceeds (or equals) the ’backoutThreshold’

defined for the WebSphere MQ input queue. The message broker is propagating the message to the failure terminal

of the node.

Response: Examine the other messages and the message flow to determine why the message is being backed out.

Correct this situation if possible. Perform any local error recovery processing required.

154 Diagnostic messages

BIP2632 Message received and propagated to ’out’ terminal of MQ input node <insert_0>.

Severity: 0 : Information

BIP2633 Warning when starting transaction coordinated by WebSphere MQ; MQBEGIN failed:

MQCC=<insert_0>; MQRC=<insert_1>; node <insert_2>.

Severity: 10 : Warning

Explanation: The message flow attribute ’coordinatedTransaction’ was specified as ’yes’. However, when the broker

attempted to start the coordinated transaction in node <insert_2>, the MQBEGIN function returned a warning as

indicated by the WebSphere MQ reason code. The message flow continues, but the transaction may not be being

coordinated as expected, and this may cause subsequent errors or unpredictable results.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2634 Exception condition detected: object label <insert_0>; input node <insert_1>.

Severity: 20 : Error

Explanation: An input node detected an error whilst processing a message. The message flow has been rolled back

and, if the message was being processed in a unit of work, will remain on the input queue to be processed again.

Following messages will indicate the cause of this exception which was generated in the STL container classes.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP2635 Exception during destination list processing; output node <insert_0>.

Severity: 20 : Error

Explanation: While processing a destination list in the output node <insert_0> an error (or errors) occurred.

Response: Check the preceding error messages to determine what effect this error causes, taking any action as

described by those messages.

BIP2636 Warning when receiving a message: MQGET returned MQCC=<insert_0>, MQRC=<insert_1>;

message flow node <insert_2>.

Severity: 20 : Error

Explanation: The message flow node <insert_2> received a message from a queue, but a warning was generated.

The return and reason code from the MQGET operation are as displayed. The message will be propagated to the

failure terminal of the node.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2637 Message propagated to failure terminal; node <insert_0>.

Severity: 0 : Information

BIP2638 The MQ output node <insert_4> attempted to write a message to queue <insert_1> connected to

queue manager <insert_0>. The MQCC was <insert_2> and the MQRC was <insert_3>.

Severity: 0 : Information

BIP2000 to BIP2999 (Broker) 155

BIP2639 Unable to convert backout requeue queue name to Unicode for message flow node <insert_0>.

Severity: 20 : Error

Explanation: The message flow node <insert_0> was unable to convert the backout requeue queue name to a

Unicode string. The current message flow is terminated.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP2640 Unable to convert dead letter queue name to Unicode for message flow node <insert_0>.

Severity: 20 : Error

Explanation: The message flow node <insert_0> was unable to convert the dead letter queue name to a Unicode

string. The current message flow is terminated.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP2641 Unable to disconnect from the WebSphere MQ queue manager; MQDISC failed; queue

manager=<insert_0>, MQCC=<insert_1>, MQRC=<insert_2>.

Severity: 10 : Warning

Explanation: The message broker was unable to disconnect from the WebSphere MQ queue manager because the

MQDISC function failed. The broker operation is unlikely to be affected, since this situation will normally occur

during broker shutdown.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2642 ReplyToQ name not specified in message MQMD; output node <insert_0>.

Severity: 20 : Error

Explanation: The message flow node <insert_0> could not put the message to the ReplyToQ as its name is not

specified in the MQMD of the message.

Response: Make sure the name of the ReplyToQ is specified in the MQMD of the message.

BIP2643 Unable to commit a WebSphere MQ transaction; MQCMIT failed; queue manager=<insert_0>,

MQCC=<insert_1>, MQRC=<insert_2>.

Severity: 10 : Warning

Explanation: The message broker was unable to commit a WebSphere MQ unit of work because the MQCMIT

function failed. The state of any messages processed within the unit of work may be unpredictable, depending on the

reason for the WebSphere MQ error.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2644 Exception condition detected on input node: <insert_0>.

Severity: 0 : Information

Explanation: Node <insert_0> has received a message, but an exception was generated whilst initializing it’s internal

representation. The message broker is propagating the message to the failure terminal of the node.

Response: If ’complete’ or ’immediate’ MRM message body validation is being applied to messages received by this

node, it’s possible the format of the body of the received message is invalid. Examine further messages for

confirmation of this or to determine why the message is not being received as expected. Correct this situation if

possible. Perform any local error recovery processing required.

156 Diagnostic messages

BIP2645 Exception condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message, but an exception was generated whilst initializing it’s internal

representation. The failure terminal is not attached, so the message broker is putting the message directly to the

requeue or dead letter backout queue associated with this node.

Response: If ’complete’ or ’immediate’ MRM message body validation is being applied to messages received by this

node, it’s possible the format of the body of the received message is invalid. Examine further messages for

confirmation of this or to determine why the message is not being received as expected. Correct this situation if

possible. Perform any local error recovery processing required.

BIP2646 Exception condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message, but an exception was generated whilst initializing it’s internal

representation. The failure terminal is attached but previous attempts to successfully process this message down this

terminal have failed. The MQMD ’’backoutCount’’ of the message now equals the ’’backoutThreshold’’ defined for

the WebSphere MQ input queue. Having now reached the ’’attempt limit’’ for processing the message down the

failure terminal, the message broker is now putting the message to the requeue or dead letter backout queue

associated with this node.

Response: If ’complete’ or ’immediate’ MRM message body validation is being applied to messages received by this

node, it’s possible the format of the body of the received message is invalid. Examine further messages to confirm

this. Also, examine previous messages to determine why the exception is not being successfully processed when

routed down the failure terminal. Correct these situations if possible. Perform any local error recovery processing

required.

BIP2647 Error condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message, but a warning was received from the MQGET operation. The

failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter

backout queue associated with this node.

Response: Examine the other messages to determine why the message is not being received as expected. Correct

this situation if possible. Perform any local error recovery processing required.

BIP2648 Message backed out to a queue; node <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message which has previously been backed out one or more times

because of a processing error in the main path of the message flow. The failure terminal is not attached, so the

message broker is putting the message directly to the requeue or dead letter backout queue associated with this node.

The MQMD ’backoutCount’ of the message now equals the ’backoutThreshold’ defined for the WebSphere MQ input

queue.

Response: Examine previous messages and the message flow to determine why the message is being backed out.

Correct this situation if possible. Perform any local error recovery processing required.

BIP2649 Error condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message, but a warning was received from the MQGET operation. The

failure terminal is attached, but previous attempts to successfully process the message down this terminal have failed.

The MQMD ’’backoutCount’’ of the message now equals the ’’backoutThreshold’’ defined for the WebSphere MQ

input queue. Having now reached the ’’attempt limit’’ for processing the message down the failure terminal, the

message broker is now putting the message to the requeue or dead letter backout queue associated with this node.

Response: Examine previous messages to determine why the message is not being successfully processed when

BIP2000 to BIP2999 (Broker) 157

routed down the failure terminal. Correct the situation if possible. Perform any local error recovery processing

required.

BIP2650 Message backed out to a queue; node <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message which has previously been backed out one or more times

because of a processing error in the main path of the message flow. The failure terminal is attached, but previous

attempts to successfully process the message down this terminal have also failed. The MQMD ’’backoutCount’’ of the

message now equals twice the ’’backoutThreshold’’ defined for the WebSphere MQ input queue. Having now

reached the ’’attempt limit’’ for both these paths in the flow, the message broker is now putting the message to the

requeue or dead letter backout queue associated with this node.

Response: Examine previous messages and the message flow to determine why the message is being backed out.

Also, examine previous messages to determine why the error is not being successfully processed when routed down

the failure terminal. Correct these situations if possible. Perform any local error recovery processing required.

BIP2651 Error condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> received a message, but a warning was raised from the MQGET operation.

Response: Examine the other messages to determine why the message is not being received as expected. Correct

this situation if possible. Perform any local error recovery processing required.

BIP2652 Message backed out to a queue; node <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has received a message which has previously been backed out one or more times

because of a processing error in the main path of the message flow.

Response: Examine previous messages and the message flow to determine why the message is being backed out.

Correct this situation if possible. Perform any local error recovery processing required.

BIP2653 The WebSphere MQ Queue Manager <insert_0> does not support the MQOptimizedFlow

performance options.

Severity: 20 : Error

Explanation: The deploy is rejected

Response: None

BIP2654 MQOptimizedFlow is not supported on OS/390

Severity: 20 : Error

Explanation: The Configuration Message is rejected

Response: The deploy is rejected

BIP2655 MQOptimizedFlow has detected a non-JMS input message

Severity: 10 : Warning

Explanation: An MQOptimizedFlow can only process JMS MQ messages. All input messages must be JMS

compliant. If a dead letter queue (DLQ) is defined, the message will be sent to the dead letter queue. If a DLQ is not

defined the flow will block

Response: To take advantage of this optimized pubsub node, use the JMS message model

158 Diagnostic messages

BIP2656 Unable to open queue <insert_0> on WebSpehere Broker Queue Manager <insert_1> because the

serialization token <insert_2> is already in use.

Severity: 0 : Information

Explanation: An MQInput node in another message flow has already connected to the shared queue using the same

serialization token. This MQInput node will retry to connect to the queue.

Response: No user action required

BIP2657 MQGetNode <insert_5> has completed its MQGET() call. The returned MQ codes are:

MQCC=<insert_3>, MQRC=<insert_4>.

Severity: 0 : Information

Explanation: MQGetNode <insert_5> has made <insert_2> attempt(s) at calling MQGET() to read queue <insert_1>

of queue manager <insert_0>. The last call returned with MQ completion code <insert_3> and reason code <insert_4>.

Response: If the call(s) failed (returned with a non-zero return code), check the error codes and the other

information provided to determine the cause of the failure and take any action necessary to resolve the problem.

Possible causes include incorrect queue name, queue not readable, and message too large.

BIP2658 MQGetNode <insert_1> is propagating a message to the <insert_0> Terminal.

Severity: 0 : Information

Explanation: None

Response: None

BIP2660 The message received at output node <insert_4> is empty. State = <insert_0> <insert_1> <insert_2>

<insert_3>

Severity: 20 : Error

Explanation: The WebSphere Message Brokers output node <insert_4> has received a message for writing to a

queue, but the message’s bit stream is too short to be a valid message. This situation can occur when a message is

built incorrectly by a Compute node (e.g. there is no MQMD).

Response: Check the message flow to determine whether the message is being built correctly, correct the problem

and redeploy.

BIP2661 The message received at output node <insert_4> does not contain a valid MQMD. State = <insert_0>

<insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: The WebSphere Message Brokers output node <insert_4> has received a message to write to an

WebSphere output queue, but the message does not contain a valid MQMD. This situation can occur when a output

message is built incorrectly using a Compute node.

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy.

BIP2662 Invalid queue manager or queue name. State = <insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: The queue manager or queue name cannot be converted to a form acceptable to the queue manager.

This may be because it contains characters not available in the queue manager’s code page or because it is too long

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy the broker.

BIP2000 to BIP2999 (Broker) 159

BIP2663 Invalid reply to queue manager or queue name in output node <insert_4>. State = <insert_0>

<insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: The reply to queue manager or reply to queue name cannot be converted to a form acceptable to the

queue manager. This may be because it contains characters not available in the queue manager’s code page or

because it is too long

Response: Correct the output node’s configuration and redeploy the message flow.

BIP2664 It does not currently appear to be possible to get this message. Node <insert_4>. State = <insert_0>

<insert_1> <insert_2> <insert_3>

Severity: 20 : Error

BIP2665 Output node <insert_4> expected a distribution list but one did not exist. State = <insert_0>

<insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An MQ output node with the ″Destination Mode″ property set to ″list″ received a message but there

was no valid distribution list, that is, it did not contain a ″Destination″ folder in turn containing an ″MQ″ folder.

Response: Check the message flow to determine whether the message is being built correctly, correct the problem

and redeploy the broker.

BIP2666 An error occurred in node <insert_6> when opening queue <insert_5> on queue manager <insert_4>.

State = <insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An error occurred when a message flow node attempted to open a queue. The reason code from the

MQOPEN is displayed as the 3rd (native error) state.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2667 An error occurred in node <insert_6> writing message to queue <insert_5> on queue manager

<insert_4>. State = <insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An error occurred when a message flow node attempted to write a message to a queue. The reason

code from the MQPUT is displayed as the 3rd (native error) state.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2668 A single error occurred in output node <insert_0> during destination list processing.

Severity: 20 : Error

Explanation: One error occurred while processing a destination list (i.e. whilst putting many messages).

Response: Check the following messages for details of the errors and the preceding messages for details of the effect

these have had on message processing.

160 Diagnostic messages

BIP2669 Multiple errors occurred in output node <insert_4> during destination list processing. State =

<insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: More than one error occurred while processing a destination list (i.e. whilst putting many messages).

Response: Check the following messages for details of the errors and the preceding messages for details of the effect

these have had on message processing.

BIP2670 Output node <insert_4> received a distribution list containing an invalid folder. State = <insert_0>

<insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An MQ output node with the ″Destination Mode″ property set to ″list″ received a message containing

a distribution list. However the ″MQ″ folder contained an invalid folder. The only folders allowed in this situation

are ″Defaults″ and ″DestinationData″.

Response: Check the message flow to determine whether the message is being built correctly, correct the problem

and redeploy the broker.

BIP2671 Output node <insert_6> received a distribution list in which the folder <insert_4> contained the

invalid field <insert_5>. State = <insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An MQ output node with the ″Destination Mode″ property set to ″list″ received a message containing

a distribution list. However the ″Defaults″ or ″DestinationData″ folder contained an invalid field. Only specific field

names are allowed in this situation.

Response: Check the message flow to determine whether the message is being built correctly, correct the problem

and redeploy the broker.

BIP2672 Output node <insert_6> received a distribution list in which the field <insert_4> contained the

invalid value <insert_5>. State = <insert_0> <insert_1> <insert_2> <insert_3>

Severity: 20 : Error

Explanation: An MQ output node with the ″Destination Mode″ property set to ″list″ received a message containing

a distribution list. However the ″Defaults″ or ″DestinationData″ folder contained an field with an invalid value. Only

specific values are allowed in this situation.

Response: Check the message flow to determine whether the message is being built correctly, correct the problem

and redeploy the broker.

BIP2673 Unable to rollback a WebSphere MQ transaction; MQBACK failed; queue manager=<insert_0>,

MQCC=<insert_1>, MQRC=<insert_2>; message flow node. Use the WebSphere MQ return code and

reason code returned to establish the cause of the error and take appropriate action. To protect the

transaction this process will now terminate as the transaction state has become and may remain in

doubt.

Severity: 20 : Error

Explanation: An attempt to rollback a WebSphere MQ unit of work using the MQBACK functions has failed. The

WebSphere MQ return code and reason code returned from MQBACK are displayed.

Response: Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming

Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the

message broker after you have performed this recovery action.

BIP2000 to BIP2999 (Broker) 161

BIP2674 Broken connection to WebSphere MQ Queue Manager detected by a WebSphere MQ reason code of

<insert_0>;

Severity: 20 : Error

Explanation: A call to a WebSphere MQ API has returned with a reason code of <insert_0> which indicates the the

current connection is no longer useable. Further messages will indicate the effect this has on WebSphere Message

Broker components.

Response: Check the WebSphere MQ reason code in the WebSphere MQ Application Programming Reference

manual to establish the cause of the error, taking any appropriate action.

BIP2675 The queue manager is reporting the next message in our current message group is not available.

Severity: 10 : Warning

Explanation: Queue manager <insert_0> returned a 2033 whilst reading queue <insert_1>. The message group

identifier is <insert_2> and the last sequence number processed was <insert_3>. This message group is incomplete.

The MQInput nodes All Messages Available option was set to <insert_4>.

Response: If the All Messages Available option was selected then all the messages must have been available for the

message group to have started. Check to see if any messages have expired or if any other applications are retrieving

messages off this queue. If the All Messages Available option was not selected then the message group could have

started before all the messages were available. Check why all the group messages are not available on the input

queue.

BIP2801 Unable to load implementation file <insert_0>, rc=<insert_1>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst loading a loadable implementation file.

Response: Ensure that the file exists.

BIP2802 Unable to locate entry point <insert_1> in implementation file <insert_0>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst locating an entry point in a loadable implementation file.

Response: Ensure that you have the correct version of the loadable implementation file. If you cannot resolve the

problem contact your IBM support center.

BIP2803 Broker <insert_0> (UUID <insert_1>) received an internal configuration response message for

execution group <insert_2> that contained no data.

Severity: 0 : Information

Explanation: The execution group failed to provide an adequate internal configuration response message.

Response: Use the system log messages to determine why the execution group failed to provide a complete internal

configuration response message. You should check that your system is not running short of resources: for example,

you may need to increase the WebSphere log size. Reducing the complexity of the deploy by reducing the number of

execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker’s

configuration from the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy. Contact your IBM

support center if you are unable to resolve the problem.

BIP2804 The broker has detected that Execution Group <insert_0>, process ID <insert_1>, has not shutdown.

Severity: 20 : Error

Explanation: An attempt was made to stop an Execution Group process by issuing an internal configuration

message to the Execution Group. The Execution Group process has not yet shut down.

Response: Use the system Log to investigate why the Execution Group process could not shutdown. It is expected

that the Execution Group will eventually shutdown normally. This message is repeated at 1 minute intervals.

162 Diagnostic messages

However, it is possible that you may need to stop the Execution Group manually. If the broker was configured as a

WebSphere MQ trusted application then refer to the WebSphere MQ reference manuals to determine how to stop the

Execution Group executable. Ensure that any database locks held by the Execution Group are released if the process

is forced. Contact your IBM support center if you are unable to determine the reason for this problem.

BIP2805 Broker <insert_0> could not process an internal configuration message.

Severity: 20 : Error

Explanation: The problem was caused by a failure to parse the internal configuration message. The internal

configuration message is rejected.

Response: Use the system log messages output prior to this message to diagnose the problem with the internal

configuration message. Correct and redeploy the broker configuration message. Contact your IBM support center if

you are unable to resolve the problem.

BIP2806 The broker was unable to publish to WebSphere MQ Queue <insert_0>.

Severity: 20 : Error

Explanation: A publish event could not be sent because the WebSphere MQ message queue was not available.

Response: You should investigate why the message queue was not available by reviewing the system log messages.

The current published state of the broker will be incorrect.

BIP2807 The broker received a negative response to a ’stopped’ publish event, response is <insert_0>.

Severity: 20 : Error

Explanation: A ’stopped’ publish event failed, use the response to determine the cause of the failure.

Response: The broker continues to run but the current published state of the broker will be incorrect until the next

successful publish event. Contact your IBM support center.

BIP2808 The broker was unable to access its startup singleton classes.

Severity: 20 : Error

Explanation: An attempt was made to access a singleton class, this singleton class was not initialized correctly.

Response: The broker will not start. Obtain Service trace for the failing component and contact your IBM support

center.

BIP2809 The broker was unable to receive a ’started’ publish event response.

Severity: 20 : Error

Explanation: A response from a ’started’ publish event could not be received.

Response: The broker continues to start-up but the current published state of the broker will be incorrect. Contact

your IBM support center.

BIP2810 The broker received a negative response to a ’started’ publish event, response is <insert_0>.

Severity: 20 : Error

Explanation: A ’started’ publish event failed, use the response to determine the cause of the failure.

Response: The broker continues to run but the current published state of the broker will be incorrect until the next

successful publish event. Contact your IBM support center.

BIP2000 to BIP2999 (Broker) 163

BIP2811 The broker was unable to receive a ’stopped’ publish event response.

Severity: 20 : Error

Explanation: A response from a ’stopped’ publish event could not be received.

Response: The broker continues to shutdown but the current published state of the broker will be incorrect. Contact

your IBM support center.

BIP2812 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration response message

for Execution Group <insert_2>.

Severity: 20 : Error

Explanation: The problem was caused by a failure to parse the internal configuration response message. The

internal configuration response message is treated as an ’unknown’ failure.

Response: Use the system log messages to diagnose the reason for the parse failure. Correct and redeploy the

broker configuration message. Contact your IBM support center if you are unable to resolve the problem.

BIP2813 Broker <insert_0> (UUID <insert_1>) could not process an internal configuration response message

for Execution Group <insert_2> to completion: missing tag <insert_3>.

Severity: 20 : Error

Explanation: The internal configuration response message returned by the Execution Group was incomplete.

Response: Use the system log messages to determine why the Execution Group failed to respond correctly.

Redeploy the broker’s configuration if you are able to resolve the problem. Contact your IBM support center if you

are unable to resolve the problem.

BIP2814 Broker could not initialize semaphore <insert_0>.

Severity: 20 : Error

Explanation: An internal semaphore could not be initialized, this semaphore controls database access.

Response: Use the system log messages to determine why the semaphore failed to be initialized. Contact your IBM

support center if you are unable to resolve the problem.

BIP2815 Broker could not create a connection to its database.

Severity: 20 : Error

Explanation: An ODBC connection could not be created by the broker to access its internal persistent store tables.

Response: Use the system log messages to determine why the database connection failed to be created. Contact

your IBM support center if you are unable to resolve the problem.

BIP2816 Broker could not access database class ImbAAOdbc.

Severity: 20 : Error

Explanation: An ODBC connection class could not be accessed. An attempt was made to use the class instance after

it had been prepared for destruction.

Response: Use the system log messages to determine if there were any unusual circumstances prior to this message

being issued. Contact your IBM support center to report this logic error. Restart the broker.

BIP2817 Broker could not initialize.

Severity: 20 : Error

Explanation: A failure was detected while initializing data used by the bipbroker executable during broker startup.

This may have been caused as a result of a previous broker failing to shutdown normally. Use IPCS together with the

164 Diagnostic messages

information contained in the files in the products locks directory to verify that the brokers shared semaphores are

available for use.

Response: Collect all diagnostics produced and Contact your IBM support center.

BIP2818 Broker failed to create semaphore

Severity: 30 : Severe error

Explanation: An internal semaphore could not be created.

Response: Use the system log messages to determine why the semaphore failed to be created. Contact your IBM

support center if you are unable to resolve the problem.

BIP2819 Broker detected invalid semaphore

Severity: 30 : Severe error

Explanation: An internal semaphore has an invalid handle value.

Response: Use the system log messages to determine why the semaphore has become invalid. Contact your IBM

support center if you are unable to resolve the problem.

BIP2820 Broker detected uninitialized semaphore

Severity: 30 : Severe error

Explanation: An internal semaphore has not been initialized.

Response: Use the system log messages to determine why the semaphore has not been initialized. Contact your IBM

support center if you are unable to resolve the problem.

BIP2821 Broker detected initialized semaphore

Severity: 30 : Severe error

Explanation: An internal semaphore is initialized, which is an invalid state for the initialization phase.

Response: Use the system log messages to determine why the semaphore has apparently been initialized twice.

Contact your IBM support center if you are unable to resolve the problem.

BIP2822 Broker problem with time-related system call

Severity: 30 : Severe error

Explanation: A system call to determine or calculate a time failed.

Response: Use the system log messages to determine why the system call failed. Contact your IBM support center if

you are unable to resolve the problem.

BIP2823 Component integrity check failed.

Severity: 0 : Information

Explanation: The component startup ran an intergity check on the component configuration, and found errors. This

means that the component configuration is not correct in some way; previous messages should provide the exact

errors.

Response: Examine previous messages to determine the cause of the failure. Correct the errors, and restart the

component.

BIP2000 to BIP2999 (Broker) 165

BIP2824 Broker <insert_0> has failed to connect to WebSphere MQ with reason code <insert_1>. No broker

components will be started until the queue manager becomes available.

Severity: 0 : Information

Explanation: While starting Broker <insert_0>, an attempt to connect to the queue manager failed with a reason

code of <insert_1>. This will prevent any further broker components from starting.

Response: Ensure the queue manager is started succesfully. Investigate the WebSphere MQ queue manager problem

and resolve any problems that prevent this.

BIP2825 Broker <insert_0> (UUID <insert_1>) received an internal configuration message that specified a

64-bit Execution Group; this broker is only capable of supporting 32-bit Execution Groups.

Severity: 20 : Error

Explanation: The platform on which the broker is running does not support 64-bit Execution Group process; only

32-bit Execution Groups can be created on such platforms.

Response: Deploy only 32-bit Execution Groups to this broker, or create a broker on a 64-bit-capable platform and

deploy the configuration to that broker.

BIP2826 Execution Group termination wait timer reached.

Severity: 20 : Error

Explanation: An attempt was made to stop an Execution Group process by issuing an internal configuration

message to the Execution Group. The Execution Group process has not yet shut down.

Response: Please refer to previous messages for more details of Execution Group. Use the system Log to investigate

why the Execution Group process could not shutdown. This message is issued to enable customers to be aware of

possible shutdown problems. However, it is possible that you may need to stop the Execution Group manually.

Contact your IBM support center if you are unable to determine the reason for this problem.

BIP2901 The character data <insert_0> returned by the database could not be converted to unicode.

Severity: 10 : Warning

Explanation: This situation arises because databases sometimes return garbage for their SQL states or error text.

This usually has no significance.

Response: No user action required.

BIP2902 The text message returned from the database could not be converted to the local codepage, SQLState

(<insert_0>), native error (<insert_1>).

Severity: 10 : Warning

Explanation: The text message returned from the database could not be converted to the local codepage.

Response: No user action required.

BIP2903 (<insert_0>, <insert_1>) : Invalid Exception Type (<insert_2>) used when calling the THROW

statement. Valid exception types are <insert_3>.

Severity: 20 : Error

Explanation: An Invalid Exception Type (<insert_2>) was used as the first argument of the THROW statement. The

valid Exception Types are <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct the Exception Type and redeploy the messageflow.

166 Diagnostic messages

BIP2904 (<insert_0>, <insert_1>) : Mismatch found between EXTERNAL NAME and LANGUAGE clauses on

the a routine definition.

Severity: 20 : Error

Explanation: A routine with a LANGUAGE clause of ESQL is not allowed to have an EXTERNAL NAME clause,

but routines with a LANGUAGE J AVA or a LANGUAGE DATABASE clause require one

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2905 (<insert_0>, <insert_1>) : The expression passed to the <insert_2> statement as parameter <insert_4>

must evaluate to a <insert_3> value.

Severity: 20 : Error

Explanation: Parameter <insert_4> for the <insert_2> statement must evaluate to a <insert_3> value.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2906 (<insert_0>, <insert_1>) : The data type <insert_2> is not a valid data type for parameter <insert_3> of

the <insert_4> statement. This parameter should be of data type <insert_5>. The value passed was

<insert_6>.

Severity: 20 : Error

Explanation: The <insert_3> parameter is not of the correct data type for this statement ( <insert_4> ).

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the argument(s) passed to this statement are of the correct data type.

BIP2907 (<insert_0>, <insert_1>) : The Bitstream <insert_2> passed to the PARSE clause of the CREATE

statement is not a valid bitstream.

Severity: 20 : Error

Explanation: The bitstream <insert_2> is invalid.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the bitstream used in this statement is valid

BIP2908 (<insert_0>, <insert_1>) : The DOMAIN name <insert_2> passed to the DOMAIN clause of the

CREATE statement is not a valid Root Element Name.

Severity: 20 : Error

Explanation: The DOMAIN name <insert_2> is an invalid Root Element Name.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the DOMAIN name used in this statement is valid. You should check for

other messages issued with this one for the full context of this error.

BIP2909 (<insert_0>, <insert_1>) : Exception throw whilst processing the CREATE statement

Severity: 20 : Error

Explanation: The CREATE statement has been unable to be completed due to an exception being thrown whilst

evaluating the PARSE clause. . Additional information available is: <insert_2>

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: You should check for other messages issued with this one for the full context of this

error.

BIP2000 to BIP2999 (Broker) 167

BIP2910 (<insert_0>, <insert_1>) : SELECT list item must be a scalar

Severity: 20 : Error

Explanation: The SELECT clause of a SELECT statement contains an item which could be a list. This cannot be used

with the column functions: SUM, MAX or MIN.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2911 (<insert_0>, <insert_1>) : Search condition for an IF statement must be a boolean expression

Severity: 20 : Error

Explanation: The condition for an IF statement must be an expression which evaluates to a boolean result: TRUE,

UNKNOWN or FALSE The expression used was the wrong type.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2912 (<insert_0>, <insert_1>) : Type mismatch on RETURN

Severity: 20 : Error

Explanation: A RETURN expression is of an unexpected type. This can occur when a statement is implicitly parsed

as a RETURN statement, such as when a function is used without assigning the return value.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2913 An attempt was made to access a database without specifying a datasource. Please specify a

datasource and redeploy the message flow.

Severity: 20 : Error

Explanation: A database cannot be accessed without specifying a datasource.

Response: Specify the missing datasource and redeploy the message flow.

BIP2914 (<insert_0>, <insert_1>) : Duplicate label

Severity: 20 : Error

Explanation: A labelled statement may not contain another labelled statement with the same label either directly or

indirectly

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Choose a different label for one of the statements and redeploy the message flow.

BIP2915 (<insert_0>, <insert_1>) : Mismatched start and end labels

Severity: 20 : Error

Explanation: This error can simply be that the start and end labels are mismatched or it can be indicative of an

error in the nesting of statements.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct one of the labels or the nesting of statements and redeploy the message flow.

BIP2916 (<insert_0>, <insert_1>) : Correlation names cannot be qualified.

Severity: 20 : Error

Explanation: Correlation names (the first name in a field reference) must be a simple name identifier. They cannot

be qualified by a type, an index, a list specifier ([ ]) nor may the name be calculated by an expression.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

168 Diagnostic messages

redeploy the message flow: Ensure that all correlation names are unqualified.

BIP2917 A call to the Java method <insert_0> with parameters <insert_2> failed because a Java Exception

occured. The Java Exception information is <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to invoke the Java method <insert_0>, but the method threw an exception. This

is normally due to a coding error in the Java method or an error in the JVM (such as Out of Memory). The Java

exception information was <insert_1>. The parameters passed into the method were <insert_2>.

Response: Examine and correct the Java method

BIP2918 Node <insert_6>: Executing Java Method <insert_2> derived from (<insert_0>, <insert_1>). Parameters

passed <insert_3>. Resulting parameter values <insert_4>. Return value <insert_5>.

Severity: 0 : Information

BIP2919 (<insert_0>, <insert_1>) : An error occured whilst invoking the Java method <insert_2>. The

parameters passed to the method were <insert_3>.

Severity: 20 : Error

Explanation: Other messages will give an indication of context of this error.

BIP2920 Whilst attempting to obtain a procedure definition, the database reported that the procedure

<insert_0> does not exist, or cannot be accesed.

Severity: 20 : Error

Explanation: If the procedure <insert_0> does not exist it will need to be created before it can be called. Otherwise

ensure that the EXTERNAL NAME matches the name by which it is known to the database, including any necessary

schema/package qualifiers.

Response: Make sure that this procedure exists and you have authority to access it and have qualified the

EXTERNAL NAME if necessary. then redeploy the message flow.

BIP2921 The procedure <insert_0> with <insert_1> parameters could not be matched with a corresponding

Database stored procedure.

Severity: 20 : Error

Explanation: Stored Procedures must match the ESQL CREATE PROCEDURE definition in the following ways: 1:

The ESQL parameters must all be of SCALAR type. 2: The directions of each ESQL and Database parameter (IN /

OUT / INOUT) must match. 3: The number of parameters in both the ESQL and database definitions must match.

Response: Ensure these conditions are met and redeploy the message flow.

BIP2922 The database reports that the procedure <insert_0> in schema <insert_1> has <insert_2> overloaded

versions. This is not supported, as it cannot be determined which of the <insert_2> definitions is

required.

Severity: 20 : Error

Explanation: If the procedure <insert_0> is not already qualified with a schema name, qualification may remove this

problem. Otherwise ensure that the procedure <insert_0> is the only procedure of this name within schema <insert_1>

Response: Correct this problem and redeploy the messageflow.

BIP2923 (<insert_0>, <insert_1>) : A CALL to the procedure <insert_2> failed as it could not find a database

definition for this procedure. Please check that this procedure exists in the database and that it’s

definition matches the ESQL definition.

Severity: 20 : Error

BIP2000 to BIP2999 (Broker) 169

Explanation: If the procedure <insert_2> does not exist it will need to be created before it can be called. Otherwise

ensure that the EXTERNAL NAME <insert_3> matches the name by which it is known to the Database, including any

necessary schema/package qualifiers.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Make sure that this procedure exists and you have authority to access it and have

qualified the EXTERNAL NAME if necessary, then redeploy the message flow.

BIP2924 (<insert_0>, <insert_1>) : A CALL to the procedure <insert_2> failed as a database definition for this

procedure could not be found in the schema <insert_3>.

Severity: 20 : Error

Explanation: If the procedure <insert_2> does not exist it will need to be created before it can be called. Otherwise

ensure that the schema <insert_3> matches the schema name by which this procedure is known to the Database.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Please check that this procedure exists in the schema <insert_3> and that it’s definition

matches the ESQL definition. Otherwise you will need to qualify the EXTERNAL NAME of this procedure on the

CREATE PROCEDURE statement with the correct Database schema.

BIP2925 (<insert_0>, <insert_1>) : A byte array literal must have an even number of digits.

Severity: 20 : Error

Explanation: This is most likely to have been caused by attempting to use a X’’ literal with an odd number of digits

(0-9, A-F, a-f) between the quotes.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Ensure that the literal has an even number of digits.

BIP2926 (<insert_0>, <insert_1>) : A CALL to procedure <insert_2> failed as multiple procedure definitions

match this procedure in the schema <insert_3>. Change the database procedure name to make it

unique as overloaded procedures in the same schema are not supported.

Severity: 20 : Error

Explanation: The procedure definition must be unique within the schema <insert_3>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Please check with the database that this procedure exists once only in the supplied

schema.

BIP2927 The Java method <insert_0> was found but it has a ’throws’ clause

Severity: 20 : Error

Explanation: The Java method <insert_0> must not have a ’throws’ clause

Response: Examine and correct the SQL program to ensure that no referenced Java methods have ’throws’ clauses.

BIP2928 The Java method <insert_0> was found but its return type does not match the ESQL return type

Severity: 20 : Error

Explanation: The Java method <insert_0> has a return type that does not match its ESQL return type. Correct the

ESQL return type or change the Java return type

Response: Examine and correct the SQL program.

BIP2929 (<insert_0>, <insert_1>) : Mismatch found between LANGUAGE DATABASE and RETURNS clauses

Severity: 20 : Error

Explanation: A LANGUAGE DATABASE routine is not allowed to have a RETURNS clause.

170 Diagnostic messages

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2930 A function or procedure was called but the value supplied for the <insert_0> parameter was of type

<insert_1> but the function/procedure expects value of type <insert_2>

Severity: 20 : Error

Explanation: Functions and procedures require an exact matching between the data type of values supplied as

parameters and the data type in its definition.

Response: Examine and correct the SQL program

BIP2931 A function or procedure was called but the value supplied for the <insert_0> parameter was not a

reference but the function/procedure expects a reference.

Severity: 20 : Error

Explanation: Functions and procedures do not allow data types other than references (eg expressions) to be used for

IN or INOUT parameters defined to be references.

Response: Examine and correct the SQL program

BIP2932 A function or procedure was called but the value supplied for the <insert_0> parameter was not a

reference but the definition of the function/procedure requires a reference.

Severity: 20 : Error

Explanation: Functions and procedures require references to be supplied for OUT and INOUT scalar parameters so

that the resulting value can be assigned to its target.

Response: Examine and correct the SQL program

BIP2933 A function or procedure was called but the value supplied for the <insert_0> parameter was not a

reference to a reference variable but the definition of the function/procedure requires a reference to

a reference variable.

Severity: 20 : Error

Explanation: Functions and procedures require references to reference variables to be supplied for OUT and INOUT

reference parameters so that the resulting value can be assigned to its target.

Response: Examine and correct the SQL program

BIP2934 Error detected whilst executing the function or procedure <insert_0>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst executing the function or procedure <insert_0>. An

exception has been thrown to cut short the processing of the message.

Response: See the following messages for details of the error.

BIP2935 (<insert_0>, <insert_1>) : An expression which evaluates to a scalar variable or a field is required

here.

Severity: 20 : Error

Explanation: The expression supplying the parameter must evaluate to a value of a suitable type. The given

expression cannot possibly do so.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2000 to BIP2999 (Broker) 171

BIP2936 A RETURN statement attempted to return a value of type <insert_0> but the containing routine is

defined to return a value of type <insert_1>.

Severity: 20 : Error

Explanation: An exact match between the datatype of the value returned by a return statement and the datatype

specified on the routine declaration is required.

Response: Examine and correct the SQL program

BIP2937 An attempt was made to define the function or procedure <insert_0> but a function or procedure

with this name already exists.

Severity: 20 : Error

Explanation: An attempt was made to define the function or procedure <insert_0> but a function or procedure with

this name already exists. Function and procedure names are case insensitive, occupy the same name space and must

be unique regardless of the number or type of their parameters

Response: Examine and correct the SQL program

BIP2938 An attempt was made to execute the non existent function or procedure <insert_0>.

Severity: 20 : Error

Explanation: An attempt was made to execute the function or procedure <insert_0> but no such function or

procedure has been defined. All functions and procedures must be defined in the node that uses them.

Response: Examine and correct the SQL program

BIP2939 (<insert_0>, <insert_1>) : Unsuitable function or procedure <insert_2>.<insert_3>.

Severity: 20 : Error

Explanation: The program is attempting to call a function which is defined but either returns a value when none is

required or does not return a value when one is required

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2940 (<insert_0>, <insert_1>) : Wrong number of parameters. <insert_4> supplied but <insert_5> required

for function/procedure <insert_2>.<insert_3>.

Severity: 20 : Error

Explanation: The program is attempting to call a function which is defined but does not have the same number of

parameters as are present in the call

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP2941 The Datatype <insert_0> is not supported when invoking the Java method <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to pass data of datatype <insert_0> to or from a Java method either as a

parameter or as a return value. This type is not supported when invoking a Java method.

Response: Examine and correct the SQL program

BIP2942 The EXTERNAL NAME <insert_0> is not a valid name for a qualified Java method.

Severity: 20 : Error

Explanation: An attempt was made to invoke a Java method using an invalid qualified Java method name. The

name used was <insert_0>.

172 Diagnostic messages

Response: Examine and correct the SQL program

BIP2943 The Java Method <insert_0> could not be found as its containing class could not be found in the

broker classpath

Severity: 20 : Error

Explanation: The specified Java Method <insert_0> belongs to a class that could not be found in the broker

classpath. Ensure that the fully qualified name of the method is correct and that its containing class or jar file is in

the broker classpath.

Response: Examine and correct the SQL program.

BIP2944 The Java method <insert_0> does not have a valid return type.

Severity: 20 : Error

Explanation: The specified Java Method <insert_0> does not have a return type that is in the list of supported Java

return types.

Response: Examine and correct the SQL program.

BIP2945 The Java method <insert_0> has an invalid parameter type that is not on the list of supported Java

parameter types or is of the wrong direction.

Severity: 20 : Error

Explanation: One or more of the parameters to the specified Java Method <insert_0> is not of the list of supported

Java parameter types or is of the wrong direction. Ensure that all parameters to the Java method are on the list of

supported parameter datatypes and directions.

Response: Examine and correct the SQL program.

BIP2946 The Java method <insert_0> could not be found

Severity: 20 : Error

Explanation: The Java method <insert_0> with the specified signature could not be found in the specified class.

Ensure the method exists in the specified class and that it exactly matches its ESQL signature.

Response: Examine and correct the SQL program.

BIP2947 The Java method <insert_0> was found but it is not declared to be public

Severity: 20 : Error

Explanation: The Java method <insert_0> must be declared to be public

Response: Examine and correct the SQL program.

BIP2948 The Java method <insert_0> was found but is is not declared to be static

Severity: 20 : Error

Explanation: The Java method <insert_0> must be declared to be static

Response: Examine and correct the SQL program.

BIP2949 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

BIP2000 to BIP2999 (Broker) 173

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2950 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2951 Event generated by user code. Additional information : <insert_0> <insert_1> <insert_2> <insert_3>

<insert_4> <insert_5> <insert_6> <insert_7> <insert_8> <insert_9>

Severity: 0 : Information

Explanation: The event was generated by an SQL LOG or THROW statement. This is the normal behavior of these

statements.

Response: Since this is a user generated event, the user action is determined by the message flow and the type of

event.

BIP2952 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2953 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2954 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

174 Diagnostic messages

BIP2955 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2956 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2957 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2958 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2959 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2000 to BIP2999 (Broker) 175

BIP2960 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2961 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2962 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2963 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2964 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

176 Diagnostic messages

BIP2965 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2966 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2967 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2968 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2969 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2000 to BIP2999 (Broker) 177

BIP2970 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2971 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2972 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2973 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2974 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

178 Diagnostic messages

BIP2975 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2976 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2977 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2978 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2979 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2000 to BIP2999 (Broker) 179

BIP2980 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2981 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2982 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2983 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2984 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

180 Diagnostic messages

BIP2985 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2986 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2987 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2988 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2989 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2000 to BIP2999 (Broker) 181

BIP2990 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2991 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2992 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2993 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2994 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

182 Diagnostic messages

BIP2995 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2996 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2997 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2998 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2999 A user generated ESQL exception has been thrown. The additional information provided with this

exception is: <insert_0> <insert_1> <insert_2> <insert_3> <insert_4> <insert_5> <insert_6> <insert_7>

<insert_8> <insert_9>

Severity: 0 : Information

Explanation: This exception was thrown by a THROW EXCEPTION statement. This is the normal behavior of the

THROW statement.

Response: Since this is a user generated exception, the user action is determined by the message flow and the type

of exception thrown.

BIP2000 to BIP2999 (Broker) 183

184 Diagnostic messages

BIP3000 to BIP3999 (Built-in nodes)

BIP3001 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3002 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3003 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3004 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3005 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3006 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3007 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3008 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3009 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3010 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3011 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3012 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3013 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

186 Diagnostic messages

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3014 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3015 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3016 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3017 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3018 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3019 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3000 to BIP3999 (Built-in nodes) 187

BIP3020 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3021 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3022 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3023 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3024 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3025 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3026 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

188 Diagnostic messages

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3027 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3028 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3029 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3030 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3031 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3032 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3000 to BIP3999 (Built-in nodes) 189

BIP3033 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3034 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3035 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3036 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3037 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3038 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3039 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

190 Diagnostic messages

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3040 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3041 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3042 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3043 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3044 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3045 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3000 to BIP3999 (Built-in nodes) 191

BIP3046 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3047 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3048 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3049 Exception thrown by throw node <insert_1>; text is <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_1> has received a message and thus has thrown an exception as this is its

normal behavior. The message text associated with this exception is <insert_0>.

Response: Since this is application generated (by message flow behavior), the user action is determined by the

message flow and the type of exception generated.

BIP3051 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3052 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3053 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

192 Diagnostic messages

BIP3054 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3055 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3056 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3057 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3058 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3059 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3060 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3000 to BIP3999 (Built-in nodes) 193

BIP3061 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3062 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3063 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3064 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3065 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3066 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3067 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

194 Diagnostic messages

BIP3068 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3069 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3070 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3071 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3072 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3073 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3074 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3000 to BIP3999 (Built-in nodes) 195

BIP3075 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3076 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3077 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3078 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3079 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3080 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3081 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

196 Diagnostic messages

BIP3082 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3083 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3084 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3085 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3086 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3087 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3088 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3000 to BIP3999 (Built-in nodes) 197

BIP3089 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3090 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3091 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3092 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3093 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3094 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3095 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

198 Diagnostic messages

BIP3096 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3097 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3098 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3099 Error message <insert_0> from trace node <insert_1>.

Severity: 20 : Error

Explanation: The trace node <insert_1> has output the specified error message.

Response: This is an error message provided by the message flow designer. The user response will be determined

by the local environment.

BIP3101 The HTTP Listener has started successfully (process <insert_0> port <insert_1>)

Severity: 0 : Information

Explanation: The HTTP Listener process has started, and is currently listening on the broker-specific TCPIP port

Response: No user action required.

BIP3102 Unable to create a Java VM.

Severity: 30 : Severe error

Explanation: This is an internal error.

Response: Stop the broker and contact your IBM support center.

BIP3103 Java class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the broker and contact your IBM support center.

BIP3104 Java method <insert_1> in class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the broker and contact your IBM support center.

BIP3000 to BIP3999 (Built-in nodes) 199

BIP3105 An instance of Java class <insert_0> could not be created.

Severity: 30 : Severe error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the broker and contact your IBM support center.

BIP3106 Java exception caught via the JNI from the <insert_0> class: exception text <insert_1>.

Severity: 30 : Severe error

Explanation: This may be an internal error, possibly due to a faulty installation. Review of the exception text may

indicate a solution.

Response: Stop the broker and if the exception text does not allow you to solve the problem then you should

contact your IBM support center.

BIP3107 Java field <insert_1> in class <insert_0> could not be found.

Severity: 20 : Error

Explanation: This is an internal error, possibly due to a faulty installation.

Response: Stop the broker and contact your IBM support center.

BIP3108 Unable to initialise the listener environment. Exception text <insert_0>

Severity: 30 : Severe error

Explanation: The HTTP listener detected an error whilst initializing its working environment. Examine previous

error messages for details of the cause of this problem.

Response: Contact your IBM support center.

BIP3109 Invalid value (<insert_0>) for attribute (<insert_1>); node class=<insert_2>.

Severity: 20 : Error

Explanation: A configuration request was received which specified a value for the indicated attribute of the node

class. However, this value could not be converted to a wide string. The configuration request is terminated.

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request.

BIP3110 Message broker internal error: diagnostic information <insert_0>.

Severity: 20 : Error

Explanation: An internal software error has occurred in the message broker.Further messages will indicate the effect

of this error on the broker’s transactions.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.

BIP3111 An internal error has occurred in node <insert_0>.

Severity: 20 : Error

Explanation: The instance of the WebSphere MQ manager class could not be located when required by node

<insert_0>.The current message flow has been terminated.This error is probably indicative of an internal software

malfunction.

Response: If this occurs frequently, restart the message broker.If it continues to occur, contact your IBM support

center.

200 Diagnostic messages

BIP3112 An internal error has occurred in node <insert_3>.

Severity: 20 : Error

Explanation: A message flow node failed to connect to the WebSphere MQ queue manager <insert_0> with the

resulting WebSphere MQ completion and reason codes of <insert_1> and <insert_2>. This queue manager is used for

internal communication between the listener process and the message flow. The message flow attempts to open the

queue periodically until successful. The message flow is not fully operational until this has been done.

Response: Ensure the queue manager is operational. If this problem occurs frequently, restart the message broker. If

it continues to occur, contact your IBM support center.

BIP3113 Exception detected in message flow <insert_0> (broker <insert_1>)

Severity: 20 : Error

Explanation: This message is used as a faultstring in a SOAP fault message.

Response: None.

BIP3114 An internal error has occurred in node <insert_4>.

Severity: 20 : Error

Explanation: A message flow node failed to open the WebSphere MQ queue <insert_1> owned by queue manager

<insert_0> with the resulting WebSphere MQ completion and reason codes of <insert_2> and <insert_3>. This queue is

used for internal communication between the listener process and the message flow. The message flow attempts to

open the queue periodically until the queue is defined. The message flow is not fully operational until this has been

done.

Response: If this occurs frequently, restart the message broker. If it continues to occur, contact your IBM support

center.

BIP3115 An internal error has occurred in node <insert_3>.

Severity: 20 : Error

Explanation: Unable to get message from WebSphere MQ queue <insert_0>: MQCC=<insert_1>; MQRC=<insert_2>;

node <insert_3>. This queue is used for internal communication between the listener process and the message flow.

The node periodically retries the MQGET until it is successful.

Response: Ensure the queue manager is operational. If this problem occurs frequently, restart the message broker. If

it continues to occur, contact your IBM support center.

BIP3116 Reply message is empty; reply node <insert_0>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers reply node <insert_0> has received a response message to write to an

HTTP client, but the message appears to be empty (that is, it has no message content in the output bitstream). This

situation can occur when a output message is built incorrectly using the Compute node.

Response: Check the message flow to determine whether the message is being built correctly. If not, correct the

problem and redeploy the broker.

BIP3117 An internal error has occurred in node <insert_4>.

Severity: 20 : Error

Explanation: A message flow node failed to write to the WebSphere MQ queue <insert_1> owned by queue manager

<insert_0> with the resulting WebSphere MQ completion and reason codes of <insert_2> and <insert_3>. This queue is

used for internal communication between the listener process and the message flow.

Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently,

restart the message broker. If it continues to occur, contact your IBM support center.

BIP3000 to BIP3999 (Built-in nodes) 201

BIP3118 Reply message successfully sent by reply node <insert_2> to the requesting HTTP client

Severity: 0 : Information

Explanation: Reply message successfully sent by reply node <insert_2> to the requesting HTTP client via WebSphere

Message Brokers queue <insert_1> connected to queue manager <insert_0>.

Response: No user action required.

BIP3119 An internal error has occurred in node <insert_4>.

Severity: 20 : Error

Explanation: A message flow node received a warning when writing to the WebSphere MQ queue <insert_1> owned

by queue manager <insert_0> ; WebSphere MQ completion and reason codes were <insert_2> and <insert_3>. This

queue is used for internal communication between the listener process and the message flow, and warning messages

should not occur in normal operation.

Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently,

restart the message broker. If it continues to occur, contact your IBM support center.

BIP3120 Exception condition detected on input node <insert_0>.

Severity: 20 : Error

Explanation: The input node <insert_0> detected an error whilst processing a message. The message flow has been

rolled-back and a fault message returned to the requesting client. Following messages will indicate the cause of this

exception.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP3121 An internal error was detected, and the request has not been processed. See the error logs associated

with the broker for more details.

Severity: 20 : Error

Explanation: This message is used as a faultstring in a SOAP fault message.

Response: None.

BIP3122 Message received and propagated to ’out’ terminal of HTTP input node <insert_0>.

Severity: 0 : Information

BIP3123 Exception condition detected on input node <insert_1>: object label <insert_0>.

Severity: 20 : Error

Explanation: The input node <insert_1> detected an error whilst processing a message. The message flow has been

rolled-back and a fault message returned to the requesting client. Following messages will indicate the cause of this

exception which was generated in the STL container classes.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP3124 An internal error has occurred in node <insert_3>.

Severity: 20 : Error

Explanation: A warning was received when node <insert_3> got a message from WebSphere MQ queue <insert_0>:

MQCC=<insert_1>; MQRC=<insert_2>; node <insert_3>. This queue is used for internal communication between the

listener process and the message flow, and warning messages should not occur in normal operation.

Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently,

restart the message broker. If it continues to occur, contact your IBM support center.

202 Diagnostic messages

BIP3125 The HTTP Reply node has returned from waiting for an acknowledgement of the reply message

from the listener process.

Severity: 30 : Severe error

Explanation: The HTTP reply node <insert_4> attempted to receive a message from the specified queue <insert_1>

connected to queue manager <insert_0>. The MQCC was <insert_2> and the MQRC was <insert_3>.

Response: No action.

BIP3126 The HTTP Reply node has sent the reply message to the HTTP client via the listener process.

Severity: 0 : Information

Explanation: The HTTP reply node <insert_4> attempted to put a message to the specified queue <insert_1>

connected to queue manager <insert_0>. The MQCC was <insert_2> and the MQRC was <insert_3>.

Response: No action.

BIP3127 An internal error was detected. See the error logs associated with the broker for more details.

Severity: 20 : Error

Explanation: This message is used as a faultstring in a SOAP fault message.

Response: None.

BIP3128 Failed to locate Java class <insert_0>.

Severity: 30 : Severe error

Explanation: The Java class <insert_0> could not be found.

Response: This is an internal error and you should contact your IBM support center.

BIP3129 Failed to locate Java method <insert_0> in class <insert_1>.

Severity: 30 : Severe error

Explanation: The Java method <insert_0> in class <insert_1> could not be found.

Response: This is an internal error and you should contact your IBM support center.

BIP3130 An exception was detected during message flow processing: <insert_0> See the error logs associated

with the broker for more details.

Severity: 20 : Error

Explanation: This message is used as a faultstring in a SOAP fault message.

Response: None.

BIP3131 The HTTP Listener could not create a necessary working directory: <insert_0> (error code <insert_1>)

Severity: 20 : Error

Explanation: The HTTP Listener needs to create a working directory for the servlet engine to function correctly. This

directory could not be created, and the listener will exit.

Response: Make sure the broker has the necessary permissions to create the required directory.

BIP3132 The HTTP Listener has started listening on port <insert_0> for <insert_1> connections.

Severity: 0 : Information

Explanation: The HTTP Listener process is currently listening on the broker-specific TCPIP port <insert_0> for

connections of type <insert_1>

BIP3000 to BIP3999 (Built-in nodes) 203

Response: No user action required.

BIP3133 The HTTP Listener has stopped listening on port <insert_0> for <insert_1> connections.

Severity: 0 : Information

Explanation: The HTTP Listener process is no longer listening on the broker-specific TCPIP port <insert_0> for

connections of type <insert_1>.

Response: No user action required.

BIP3134 A necessary working directory could not be created: <insert_0> (error code <insert_1>)

Severity: 20 : Error

Explanation: A working directory is needed for a configuration file. This directory could not be created, and proper

operation of the broker is not assured.

Response: Make sure the broker has the necessary permissions to create the required directory.

BIP3135 An exception occurred while starting the servlet engine connector. Exception text is <insert_0>

Severity: 30 : Severe error

Explanation: There are many possible causes of this error. Common causes are:

1: The SSL keystoreFile does not exist or could not be found at the location specified in the ’keystoreFile’ property or

in the default location of: (<home directory of user-id running the broker>\.keystore)

2: The SSL keystoreFile was found but was accessed with an incorrect password.

3: The SSL key alias in the keystore has a password that is different from the keystore password.

However, this may be an internal error, possibly due to a faulty installation. A review of the exception text may

indicate a solution.

Response: Stop the broker and if the exception text does not allow you to solve the problem then you should

contact your IBM support center.

BIP3136 A timeout occurred whilst sending reply data to the HTTP client. Timeout in seconds: <insert_0>

Severity: 30 : Severe error

Explanation: This may be a transient error, such as a network timeout, or it could be that the client is no longer

responding.

Response: None.

BIP3137 An exception occurred whilst sending reply data to the HTTP client: <insert_0>

Severity: 30 : Severe error

Explanation: This may be a transient error, such as a network timeout, or it could be that the client is no longer

responding.

Response: Examine the exception text to determine what caused the error.

BIP3138 An attribute conflict was detected between two HTTP Input Nodes. The timeout value specified for

node <insert_0> using URL selector <insert_1> was <insert_2>, but a previous HTTP Input Node has

already specified a value of <insert_3> for the same URL selector. The new value of <insert_2> will

be used.

Severity: 10 : Warning

Explanation: The HTTP listener process can only use one timeout value for any given URL selector. Unexpected

results may occur when multiple input nodes specify different timeout values for the same URL selector.

Response: Change the timeout values for the HTTP Input Nodes to remove the conflict, and redploy the

configuration.

204 Diagnostic messages

BIP3139 A configuration file <insert_0> could not be opened for writing.

Severity: 20 : Error

Explanation: The configuration file needs to be updated to allow for correct broker operation, but the broker could

not open the file for writing.

Response: Make sure the broker has the necessary permissions to write to the required file.

BIP3140 The HTTP listener process could not be started. broker name <insert_0>;

Severity: 20 : Error

Explanation: The broker was unable to start an HTTP listener process.

Response: Ensure that the executable is available and that the broker’s service userid has permission to run the

executable.

BIP3141 The broker has detected that the HTTP listener (process ID <insert_0>), has shut down abnormally.

Severity: 20 : Error

Explanation: An HTTP listener process ended abnormally.

Response: Investigate the reasons for the problem.

BIP3142 Internal error in the Admin Agent: <insert_0>

Severity: 30 : Severe error

Explanation: An error has occurred during HTTP listener startup or shutdown.

Response: See other errors forinformation on how this error happened.

BIP3143 Message does not contain valid HTTP context information

Severity: 30 : Severe error

Explanation: HTTP context information is required for reply processing to be successful. The needed information

was not found in the incoming message, and no HTTP reply can be produced.

Response: Provide the required HTTP context information.

BIP3144 An error has occurred during HTTP listener startup: the specified TCPIP port (<insert_0>) is already

in use.

Severity: 30 : Severe error

Explanation: The HTTP listener needs to bind to a TCPIP port for correct operation to be possible. The

broker-specific TCPIP port number <insert_0> is in use by another application.

Response: Stop other applications from using the specified port, or change the broker-specific port.

BIP3145 Message propagated to failure terminal; node <insert_0>.

Severity: 0 : Information

Explanation: Node <insert_0> has received an HTTP request message, but an error occurred before the message

could be propagated to the output terminal. The message broker is propagating the message to the failure terminal of

the node.

Response: Examine the other messages and the message flow to determine why the message is not being received

as expected. Correct this situation if possible. Perform any local error recovery processing required.

BIP3000 to BIP3999 (Built-in nodes) 205

BIP3146 Error detected whilst processing a message <insert_0>.

Severity: 20 : Error

Explanation: The message broker detected an error whilst processing a message in node <insert_0>. The message

has been augmented with an exception list and has been propagated to the node’s catch terminal for further

processing.

Response: See the following messages for details of the error.

BIP3150 A socket error occurred. Operation: <insert_0>. Error Code: <insert_1>. Error Text: <insert_2>.

Severity: 30 : Severe error

Explanation: An error occurred whilst performing a TCP/IP socket operation. This may be a temporary error, such

as a server not responding, or a symptom of an invalid hostname or port number.

Response: See the following messages for information pertaining to this error.

BIP3151 A socket operation timed out. Operation: <insert_0>. Error Code: <insert_1>. Timeout in seconds:

<insert_3>. Error Text: <insert_2>.

Severity: 30 : Severe error

Explanation: A timeout occurred whilst performing a TCP/IP socket operation. This may be a transient error, such

as a server is busy or it could be that the server is no longer responding.

Response: See the following messages for information pertaining to this error.

BIP3152 Socket error detected whilst invoking Web service located at host <insert_0>, port <insert_1>, path

<insert_2>.

Severity: 30 : Severe error

Explanation: This may be a transient error, such as a server not responding, or a symptom of an invalid hostname

or port number.

Response: Check that the hostname and port number are valid, and point to a functioning Web service.

BIP3153 Error detected whilst invoking Web service located at host <insert_0>, port <insert_1>, path

<insert_2>.

Severity: 30 : Severe error

Explanation: This may be a transient error, such as a server not responding or it may be a symptom of an invalid

hostname and/or port number.

Response: Check that the hostname, port number and URL path are valid, and point to a functioning Web service.

BIP3154 An error has been detected whilst initializing the windows socket dll (WS2_32.dll). This could be

because the dll could not be found or the version found is backlevel (not 2.2 compliant). Error Code:

<insert_0>, Error Text: <insert_1>.

Severity: 30 : Severe error

Explanation: Make sure that WS2_32.dll exists, and is in the system path.

BIP3155 An error was found whilst parsing HTTP header data. Invalid non-numeric data found in the

Content Length Header. The Content Length value was: <insert_0>.

Severity: 30 : Severe error

Explanation: The Content Length value should only contain the digits ″1234567890″.

Response: Ensure the Content Length HTTP header contains only numeric data

206 Diagnostic messages

BIP3156 An error was found whilst parsing <insert_1> header data. A <insert_1> header name is empty or

contains invalid characters at position: <insert_0>.

Severity: 30 : Severe error

Explanation: A <insert_1> header name cannot be empty or contain invalid characters.

BIP3157 An error was found whilst parsing <insert_1> header data. Multiple occurences of a <insert_1>

Header were found, when only one is allowed, or a non-folding <insert_1> Header was folded. The

header was <insert_0>.

Severity: 30 : Severe error

Explanation: The <insert_1> Header <insert_0> cannot be folded or occur multiple times. Ensure that it occurs only

once, and is not folded.

BIP3158 An error was found whilst parsing HTTP header data. Bad http header data found, as the single line

limit was exceeded without a CRLF found. The first few characters from the data were: <insert_0>.

Severity: 30 : Severe error

Explanation: Ensure that the HTTP data contains CF-LF characters to delimit lines, and ensure that a single line is

not too long.

BIP3159 An error was found whilst parsing HTTP header data. The data is not an HTTP Request or

Response. Invalid HTTP Header data. The first few characters from the data were: <insert_1>. The

current index (offset) into the HTTP Header data was: <insert_0>.

Severity: 30 : Severe error

Explanation: Ensure that the HTTP data is valid.

BIP3160 A socket was closed before all expected data was received. Received: <insert_0>. Expected: <insert_3>.

Severity: 30 : Severe error

Explanation: An error occurred whilst performing a TCP/IP socket operation. The socket was closed before all

expected data was received, or the Content-Length returned by the server was invalid. HTTP Content-Length:

<insert_1>. HTTP Headers length: <insert_2>.

BIP3161 A socket was closed before all expected data was received. Total data received: <insert_0>.

Severity: 30 : Severe error

Explanation: An error occured whilst performing a TCP/IP socket operation. The socket was closed before all

expected data was received, as the end of the HTTP headers have not been found. Ensure that the HTTP data is

valid.

BIP3162 An HTTP error occurred. The HTTP Request-Line was: <insert_4>.

Severity: 30 : Severe error

Explanation: The HTTP Request Header bitstream (if any) to be used was: <insert_0>. The HTTP Request Message

Body bitstream (if any) to be used was: <insert_1>. The HTTP Reply Header bitstream (if any) received from the

server was: <insert_2>. The HTTP Reply Message Body bitstream (if any) received from the server was: <insert_3>.

Ensure that the HTTP data is valid.

Response: See the following messages for information pertaining to this error.

BIP3000 to BIP3999 (Built-in nodes) 207

BIP3163 An HTTP error occurred with Status Code <insert_0> and Status Line <insert_1>;

Severity: 30 : Severe error

Explanation: Ensure that the HTTP data is valid.

Response: See the following messages for information pertaining to this error.

BIP3164 The HTTPRequest Node <insert_1> failed to navigate to the message location specified. The location

specified was: <insert_0>.

Severity: 30 : Severe error

Explanation: Ensure that the Location <insert_0> is valid for the message tree where it is used.

Response: Correct the specified message location.

BIP3165 An error occurred whilst performing an SSL socket operation. Operation: <insert_0>. Error Text:

<insert_1>.

Severity: 30 : Severe error

Explanation: This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname

or port number.

Response: See the following messages for information pertaining to this error.

BIP3166 An SSL socket operation timed out. Operation: <insert_0>. Error Text: <insert_2>. Timeout in seconds:

<insert_1>

Severity: 30 : Severe error

Explanation: A timeout occurred whilst performing an SSL socket operation. This may be a transient error, such as a

server is busy, or it could be that the server is no longer responding.

Response: See the following messages for information pertaining to this error.

BIP3201 (<insert_0>, <insert_1>) : EXTERNAL SCHEMA clause specified for the routine <insert_2> that is not

defined to be LANGUAGE DATABASE.

Severity: 20 : Error

Explanation: The EXTERNAL SCHEMA clause is only valid for routines that have an implicit or explit LANGUAGE

DATABASE clause. The routine specified was <insert_2>.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP3202 (<insert_0>, <insert_1>) : An error occured whilst trying to resolve the Java class / method <insert_2>

referred to by the routine <insert_3>.

Severity: 20 : Error

Explanation: Further messages will explain the error in more detail.

Response: Correct the syntax of your Java expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP3203 <insert_0> is not a valid FORMAT expression for converting expression <insert_1> to type <insert_2>.

Parsing failed at <insert_3>.

Severity: 30 : Severe error

Explanation: The FORMAT expression contains an unrecognised character for the given conversion. This can occur

if a FORMAT expression for a numerical conversion is used to convert to or from a DATE, TIME, TIMESTAMP,

GMTTIME or GMTTIMESTAMP expression. It can also occur if an invalid character has not been quoted.

208 Diagnostic messages

Response: Either replace the FORMAT expression with one of applicable type or remove the offending character.

BIP3204 Input expression <insert_0> does not match FORMAT expression <insert_1>. Parsing failed to match

<insert_2> with <insert_3>.

Severity: 30 : Severe error

Explanation: The given expression contains data which does not match the current element of the FORMAT

expression.

Response: Either rewrite the FORMAT expression to match the input data or modify the input data to match the

FORMAT expression.

BIP3206 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of an

unexpected ’0’, Cannot have 0s after #s after 0s.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3207 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of a grouping

separator after the decimal point is illegal.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3208 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of multiple

decimal separators cannot be specified.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3209 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of multiple

exponential symbols cannot be specified.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3210 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of grouping

separators and exponents are mutually exclusive.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3000 to BIP3999 (Built-in nodes) 209

BIP3211 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of malformed

exponential pattern, must have at least one ’0’ in the exponent and at least one ’#’ or ’0’ in the

integral or mantissa.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3212 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of unquoted

special characters in suffix.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3213 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of unexpected

separator, separators not allowed in prefix or negative pattern.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3214 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of too many

percent characters.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3215 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of too many

perMill characters.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3216 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of multiple pad

specifiers, you can only pad once.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

210 Diagnostic messages

BIP3217 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of syntax error,

could be an unmatched quote.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3218 Error in parsing FORMAT expression <insert_0>, parsing failed at <insert_1> because of illegal pad

position.

Severity: 30 : Severe error

Explanation: The FORMAT expression was incorrect, and must be rewritten.

Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most

likely an incorrect character used.

BIP3219 (<insert_0>, <insert_1>) : End of ESQL file found whilst still inside a block comment.

Severity: 20 : Error

Explanation: There were <insert_2> open block comments when the end of the ESQL file was found. Please ensure

that all open block comments are closed (with the */ block comment termination sequence) before the end of the

ESQL file.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP3220 (<insert_0>, <insert_1>) : End of ESQL file found whilst still inside an executable block comment.

Severity: 20 : Error

Explanation: There were <insert_2> open executable block comments when the end of the ESQL file was found.

Please ensure that all open executable block comments are closed (with the }!*/ executable block comment

termination sequence) before the end of the ESQL file.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow.

BIP3400 The creation of adapter component <insert_0> has failed.

Severity: 20 : Error

Explanation: Review previous messages to find out why the error occurred.

BIP3401 Adapter component <insert_0> is not valid. Reason: <insert_1>.

Severity: 20 : Error

Explanation: The deployment of the WebSphere adapter component has failed for an unexpected reason. The most

likely cause is a mismatch between versions of the Message Broker Toolkit and the runtime components.

Response: Check that compatible versions of the runtime components and Message Broker Toolkit are being used. If

correct versions are being used then contact IBM Support.

BIP3402 The adapter component WSDL file contains the wrong namespace. The expected namespace is

<insert_0>; the actual namespace is <insert_1>.

Severity: 20 : Error

Explanation: The deployment of the WebSphere adapter component has failed for an unexpected reason. The most

likely cause is a mismatch between versions of the Message Broker Toolkit and the runtime components.

BIP3000 to BIP3999 (Built-in nodes) 211

Response: Check that compatible versions of the runtime components and Message Broker Toolkit are being used. If

correct versions are being used then contact IBM Support.

BIP3403 The adapter component <insert_0> cannot be deleted because it is in use by the following message

flow nodes: <insert_1>.

Severity: 20 : Error

Explanation: You have attempted to delete an adapter component that is in use by one or more message flows.

Response: Review the message flows that are using the adapter and delete any that are no longer required. Then

retry deleting the adapter component.

BIP3404 The adapter node <insert_0> in message flow <insert_1> has been configured to use adapter

component <insert_2>, but that adapter component has not been deployed to this execution group.

Severity: 20 : Error

Explanation: You have deployed a message flow containing an adapter node but have not yet deployed the adapter

component.

Response: Deploy a bar file containing the adapter component to the execution group.

BIP3405 The adapter input node <insert_0> in message flow <insert_1> has been configured to use adapter

component <insert_2>, but the node <insert_3> in message flow <insert_4> is already using it.

Severity: 20 : Error

Explanation: An inbound adapter component can only be used by one WebSphere adapter input node at a time,

within a particular execution group.

Response: Review the two message flows and decide which one should be deployed to the broker.

BIP3406 The adapter component <insert_0> does not define properties for connecting to a system of type

<insert_1>, so cannot be used by the adapter <insert_2> node called <insert_3> in message flow

<insert_4>.

Severity: 20 : Error

Explanation: The wrong type of adapter is being used with this node. Input nodes must use inbound adapters and

Request nodes must use outbound adapters.

Response: Change the node to use the correct type of adapter.

BIP3407 The adapter node <insert_0> in message flow <insert_1> has been configured to use adapter

component <insert_2>, but the adapter component has not been deployed yet.

Severity: 20 : Error

Explanation: The adapter component required by the node has not been deployed yet. The message node cannot be

deployed while a component it requires is missing.

Response: Deploy the adapter component required by the node.

BIP3408 The adapter component name <insert_0> is not valid.

Severity: 20 : Error

Explanation: Make sure the adapter name is valid.

BIP3409 An attempt to create the adapter component <insert_0> using the class <insert_1> failed. This class is

not a supported type of adapter.

Severity: 20 : Error

Explanation: An attempt was made to create an adapter component using a class not installed on the broker. The

212 Diagnostic messages

most likely cause is a mismatch between levels of the Message Broker Toolkit and the runtime components.

Response: Check that compatible versions of Message Broker Toolkit and the runtime components are being used. If

correct versions are being used then contact IBM Support.

BIP3410 The instantiation of the adapter class <insert_0> failed. Reason: <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to create an adapter component but it failed while being instantiated.

Response: Check that compatible versions of the Message Broker Toolkit and the runtime components are being

used. If correct versions are being used then contact IBM Support.

BIP3411 An attempt to set the property <insert_0> on adapter component <insert_1> failed because the

property is not supported.

Severity: 20 : Error

Explanation: The current version of the adapter installed on the runtime does not support a property given in the

adapter component configuration file. The most likely reason for this is a mismatch between the Message Broker

Toolkit and the runtime component levels.

Response: Check that compatible versions of the Message Broker Toolkit and the runtime components are being

used. If correct versions are being used then contact IBM Support.

BIP3412 An attempt to set the property <insert_0> on adapter component <insert_1> failed. Reason: <insert_2>.

Severity: 20 : Error

Explanation: The current version of the adapter installed on the runtime component had a problem setting a

property given in the adapter component configuration file. The most likely reason for this is a mismatch between

the Message Broker Toolkit and the runtime component levels.

Response: Check that compatible versions of the Message Broker Toolkit and the runtime components are being

used. If correct versions are being used then contact IBM Support.

BIP3413 An attempt to start adapter component <insert_0> failed. Reason: <insert_1>.

Severity: 20 : Error

Explanation: Try redeploying the adapter component. If this continues to fail then contact IBM Support.

BIP3414 An attempt to attach the message flow node <insert_0> in message flow <insert_1> to the adapter

component <insert_2> failed. Reason: <insert_3>.

Severity: 20 : Error

Explanation: The message flow node failed to register with the adapter component to receive events. The node

cannot function correctly until it has attached to the adapter component.

Response: Identify the adapter required by the node and make sure it is deployed to the correct execution group. If

the problem persists then redeploy the message flow containing the node and the adapter component the node

requires. The reason in the message may give additional information regarding what caused the problem.

BIP3415 The deletion of the adapter component <insert_0> failed.

Severity: 20 : Error

Explanation: Review previous messages to find out why the error occurred.

BIP3000 to BIP3999 (Built-in nodes) 213

BIP3416 A failure occurred during the process of committing or rolling back an adapter configuration.

Severity: 20 : Error

Explanation: A failure occurred when the adapter configuration was being commited (or backed out) from the

broker repository. The execution group is now in a undefined state where some components might be deployed and

others are not.

Response: Remove all deployed components from the execution group and redeploy the required components. If

the problem persists then contact IBM Support.

BIP3417 Adapter component <insert_0> does not contain any method bindings.

Severity: 20 : Error

Explanation: If the adapter component does not have any method bindings then it does not contain any useful

configurations. All calls to the adapter component are made using the method bindings.

Response: Review the adapter component configuration and make sure it has at least one method binding.

BIP3418 The adapter component <insert_0> does not define properties for connecting to a system of type

<insert_1>, so cannot be used by the <insert_2> adapter <insert_3> node <insert_4> in message flow

<insert_5>.

Severity: 20 : Error

Explanation: The wrong type of adapter is being used with this node. The node must be the right type of node for

the adapter it is trying to use. For example, a SAPInputNode must use an SAP adapter.

Response: Change the node to use the correct type of adapter.

BIP3419 The changes to adapter component <insert_0> might not have been successfully picked up by node

<insert_1> in message flow <insert_2>.

Severity: 20 : Error

Explanation: The adapter being used by the node is in an undetermined state.

Response: Redeploy the adapter configuration. If the error persists then restart the broker. On restart the node will

use the new configuration.

BIP3420 The message flow node <insert_0> in message flow <insert_1> failed to access the adapter component

<insert_2>.

Severity: 20 : Error

Explanation: The node failed to access the adapter because the adapter was in the process of being re-created due to

the deployment of its configuration.

Response: Redeploy the adapter configuration. If the error persists then restart the broker.

BIP3421 The adapter component <insert_0> is not an outbound adapter so cannot be used by the adapter

request node <insert_1> in message flow <insert_2>.

Severity: 20 : Error

Explanation: The wrong type of adapter is being used with this node. Input nodes must use inbound adapters and

Request nodes must use outbound adapters.

Response: Change the node to use the correct type of adapter.

214 Diagnostic messages

BIP3422 The adapter component <insert_0> does not define properties for connecting to a system of type

<insert_1>, so cannot be used by the <insert_2> adapter request node <insert_3> in message flow

<insert_4>.

Severity: 20 : Error

Explanation: The wrong type of adapter is being used with this node. The node must be the right type of node for

the adapter it is trying to use. For example, a SAPInputNode must use an SAP adapter.

Response: Change the node to use the correct type of adapter.

BIP3901 Exception condition detected on input node <insert_0>.

Severity: 0 : Information

Explanation: The input node <insert_0> detected an error whilst processing a message. The default message

recovery processing of the node will have been invoked. The message being processed may have been reinstated on

the input device or external software resource which provides the input data. This will be dependant on the

capabilities of such devices or resources and, in the case of user-defined input nodes, on the features of the node

itself. Other messages may be associated with this message which further describe the error condition.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP3903 Node (class=<insert_0>, name=<insert_1>) propagating to <insert_2> terminal.

Severity: 0 : Information

Explanation: The specified node is about to propagate a message to the specified terminal.

Response: No user action required. This is an information message.

BIP3904 Invoking the evaluate() method of node (class=<insert_0>, name=<insert_1>).

Severity: 0 : Information

Explanation: About to pass a message to the evaluate() method of the specified node.

Response: No user action required.

BIP3905 Invoking the cniEvaluate() implementation function of node (class=<insert_0>, name=<insert_1>).

Severity: 0 : Information

Explanation: About to pass a message to the cniEvaluate() implementation function of the specified node.

Response: No user action required.

BIP3906 The node <insert_1> failed to navigate to the message location specified. The location specified was:

<insert_0>.

Severity: 30 : Severe error

Explanation: Ensure that the location <insert_0> is valid for the message tree where it is used.

Response: Correct the specified message location.

BIP3907 Message received and propagated to ’out’ terminal of input node <insert_0>.

Severity: 0 : Information

BIP3000 to BIP3999 (Built-in nodes) 215

216 Diagnostic messages

BIP4000 to BIP4999 (Built-in nodes)

BIP4001 Syntax error in SQL statements in node <insert_0>.

Severity: 20 : Error

Explanation: The configuration failed due to errors in the SQL statement text. See the following messages for details

of the error

Response: The following error messages will give specific details of the location and nature of the error. Check and

correct the syntax of the SQL statements and redeploy.

BIP4002 Transaction state is not consistent with the value of ’transaction’ attribute in node <insert_0>.

Severity: 20 : Error

Explanation: The node <insert_0> would cause a commit of the database transaction on DSN <insert_1>. However,

an active transaction already exists on that database, which would be committed prematurely if this node did a

commit. This situation can arise if a previous node which caused a database update on the same DSN had the

transaction property of ’automatic’ specified. The message flow logic is regarded as inconsistent in such a situation.

Response: Examine the logic of the message flow, correct it and redeploy.

BIP4003 Incorrect return type <insert_0> in node <insert_2>. The value returned was <insert_1>.

Severity: 20 : Error

Explanation: Return statements in filter nodes (and filter expressions) must return a value of type BOOLEAN

Response: Examine the logic of the given node’s SQL statements, correct them and redeploy.

BIP4004 Message propagated to ’true’ terminal of filter node <insert_0>.

Severity: 0 : Information

BIP4005 Message propagated to ’false’ terminal of filter node <insert_0>.

Severity: 0 : Information

BIP4006 Message propagated to ’unknown’ terminal of filter node <insert_0>.

Severity: 0 : Information

BIP4007 Message propagated to ’out’ terminal of node <insert_0>.

Severity: 0 : Information

BIP4008 Message propagated to <insert_0> terminal of node <insert_1>.

Severity: 0 : Information

BIP4009 Invalid terminal identifier <insert_0>.

Severity: 20 : Error

Explanation: THE TERMINAL clause of a PROPAGATE statement did not identify a valid terminal

Response: Examine the logic of the given node’s SQL statements, correct them and redeploy.

BIP4010 Message propagated to label node <insert_0> by node <insert_1>.

Severity: 20 : Error

BIP4011 Invalid terminal identifier <insert_0>.

Severity: 20 : Error

Explanation: The LABEL clause of a PROPAGATE statement did not identify a valid label node

Response: Examine the logic of the given node’s SQL statements, correct them and redeploy.

BIP4012 (<insert_0>, <insert_1>) : Unexpectedly encountered end of trace pattern.

Severity: 20 : Error

Explanation: The trace pattern configuring a trace node contained mismatched braces (<insert_’, ’>) at the line and

column indicated. The preceding message will indicate the identity of the node and the message flow in which it was

defined.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct the trace pattern and redeploy the message flow.

BIP4013 (<insert_0>, <insert_1>) : An expression must be given between braces in a trace pattern.

Severity: 20 : Error

Explanation: The text between braces (<insert_’, ’>) in a trace pattern configuring a trace node must consist of a

valid SQL expression defining the value to be traced. The preceding message will give the identity of the trace node

and the message flow in which it was defined.

Response: Correct the syntax of your ESQL expression in node <insert_0>, around line and column <insert_1>, then

redeploy the message flow: Correct the trace pattern and redeploy the message flow.

BIP4014 <insert_1> : Invalid value <insert_0> for the ’treatWarningsAsErrors’ attribute of a database node;

’yes’ or ’no’ required.

Severity: 20 : Error

Explanation: The ’treatWarningsAsErrors’ attribute can have the values ’no’ or ’yes’. An attempt was made to set

the attribute to the value <insert_0>.

Response: Correct the value of the attribute to either ’no’ or ’yes’.

BIP4020 NeonRules node <insert_1> received an invalid message with the following parts: <insert_0>.

Severity: 20 : Error

Explanation: Messages received must consist of a Properties folder, an MQMD, an MQRFH or MQRFH2 (optional),

and a ’NEON’ body. The message consisted of the following parts : <insert_0>.

Response: Correct either the application or message flow which is originating the message being processed by the

NeonRules node so that it conforms to the rules described above. Alternatively augment the message flow processing

nodes prior to the NeonRules node to transform the incoming message into the desired form.

BIP4021 <insert_4>: Rules evaluation failed. Message details: application group <insert_0>; message type

<insert_1>; rules error # <insert_2>; rules error message <insert_3>.

Severity: 20 : Error

Explanation: Details of the message and the error raised whilst processing the message by the NNSY rules processor

are:- Application group: <insert_0>

Message type: <insert_1>

Rules Error #: <insert_2>

Rules Error Message: <insert_3>.

If the Rules Error Message refers to a problem parsing the input message, this may be due to a problem with the

218 Diagnostic messages

database connection rather than a problem with the message itself. Check that the file pointed to by

MQSI_PARAMETERS_FILE contains the correct parameters to allow the NeonRules node to connect to the database

containing your NNSY Rules and Formats.

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

BIP4022 Node <insert_2>: Rules evaluation succeeded: application group <insert_0>; message type <insert_1>.

Severity: 0 : Information

Explanation: Application group: <insert_0>, Message type: <insert_1>.

Response: No user action required.

BIP4023 <insert_4>: Unknown action detected. Message details: application group <insert_0>; message type

<insert_1>; action name <insert_2>; subscription ID <insert_3>.

Severity: 20 : Error

Explanation: The action resulting from processing a message through the NeonRules node is not supported. Full

details of the message and the resulting action are Application group: <insert_0>

Message type: <insert_1>

Action Name: <insert_2>

Subscription ID: <insert_3>

Response:

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

BIP4024 Node <insert_2>: The rules evaluation yielded a subscription. Message details: application group

<insert_0>; message type <insert_1>.

Severity: 0 : Information

Explanation: Application group: <insert_0>, Message type: <insert_1>.

Response: No user action required.

BIP4025 Node <insert_2>: No subscriptions found. Message details: application group <insert_0>; message

type <insert_1>.

Severity: 0 : Information

Explanation: Application group: <insert_0>, Message type: <insert_1>.

Response: No user action required.

BIP4026 An unknown error occurred processing the rules.

Severity: 20 : Error

Explanation: An unexpected error has occurred whilst processing a message by the NeonRules node.

Response: This is an internal error. Contact your IBM support center.

BIP4027 Node <insert_2>: Performing a reformat operation. Message details: input message type <insert_0>;

output message type <insert_1>.

Severity: 0 : Information

Explanation: Input Message Type: <insert_0>, Output Message Type: <insert_1>.

Response: No user action required.

BIP4000 to BIP4999 (Built-in nodes) 219

BIP4028 Failed to reformat message. Message details: input message type <insert_0>; output message type

<insert_1>; formatter error number <insert_2>; formatter error message <insert_3>.

Severity: 20 : Error

Explanation: Details of the message and the error raised whilst formatting the message by the NNSY formatter are:-

Input message type: <insert_0>

Output message type: <insert_1>

Formatter Error number: <insert_2>

Formatter Error Message: <insert_3>

Response:

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

BIP4029 Node <insert_2>: Reformat completed successfully. Message details: input message type <insert_0>;

output message type <insert_1>.

Severity: 0 : Information

Explanation: Input Message Type: <insert_0>, Output Message Type: <insert_1>.

Response: No user action required.

BIP4030 Target queue not set for putqueue action.

Severity: 20 : Error

Explanation: The NNSY rules processor has evaluated a message with a putqueue action, but has not specified a

target queue to which the resultant message should be sent.

Response: Correct the NNSY rules to ensure that the action is correctly specified.

BIP4031 Output type not set for reformat.

Severity: 20 : Error

Explanation: The NNSY rules processor has evaluated a message with a reformat action, but has not specified an

output type for the message.

Response: Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give

details of the correct specification of the actions.

BIP4032 Input type not set for reformat.

Severity: 20 : Error

Explanation: The NNSY rules processor has evaluated a message with a reformat action, but has not specified an

input type for the message.

Response: Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give

details of the correct specification of the actions.

BIP4033 Cannot propagate RF header, there is no RF header on the input message.

Severity: 20 : Error

Explanation: The NNSY rules processor has evaluated a message with a propagate action indicating that the rules

and formatter header should be included. However the incoming message did not include this header.

Response: Correct the NNSY rules to ensure that the action is correctly specified. The NNSY publications give

details of the correct specification of the actions.

220 Diagnostic messages

BIP4036 Node <insert_7>: Performing a putqueue action. Options: OPT_TARGET_QUEUE <insert_0>;

OPT_APP_GRP <insert_1>; OPT_MSG_TYPE <insert_2>; MQS_FORMAT <insert_3>; MQS_EXPIRY

<insert_4>; MQS_PERSIST <insert_5>; MQS_PROPAGATE <insert_6>.

Severity: 0 : Information

Explanation: The putqueue options are listed above.

Response: No user action required.

BIP4037 Node <insert_7>: Performing a propagate action. Options: OPT_APP_GRP <insert_1>;

OPT_MSG_TYPE <insert_2>; MQS_FORMAT <insert_3>; MQS_EXPIRY <insert_4>; MQS_PERSIST

<insert_5>; MQS_PROPAGATE <insert_6>.

Severity: 0 : Information

Explanation: The propagate options are listed above.

Response: No user action required.

BIP4038 <insert_0>: The ’targetFormat’ attribute cannot be empty.

Severity: 20 : Error

Explanation: The targetFormat attribute must specify a valid NNSY output format as the target of the format

operation. It cannot be the empty string.

Response: Use the Message Brokers Toolkit to set the value of the targetFormat attribute to the correct value and

redeploy the message flow.

BIP4039 The NeonFormatter node <insert_1> received an invalid message, body type <insert_0>.

Severity: 20 : Error

Explanation: The messages received by the NeonFormatter node must have a ’NEON’ body. The body type of the

message received was <insert_0>.

Response: Check that the application or message flow generating the messages destined for the current message

flow are producing the messages with a Rules and Formatter Header (MQRFH) identifying that the body of the

message is of type ’NEON’. If no Rules and Formatter Header is present, the MQInput node for the message flow

can specify that the body is of default type ’NEON’.

BIP4040 The Execution Group <insert_0> has processed a configuration message successfully.

Severity: 0 : Information

Explanation: A configuration message has been processed successfully. Any configuration changes have been made

and stored persistently.

Response: No user action required.

BIP4041 Execution group <insert_0> received an invalid configuration message. See the following messages

for details of the error.

Severity: 20 : Error

Explanation: The message broker received an invalid configuration message and has not updated its configuration.

This can arise as a result of errors in the specification of either message flows or message sets which the

configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is

not supported by the broker installation, from the broker having become out of step with the configuration database

or from other applications sending extraneous messages to the broker’s configuration queues

(SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Response: Check the relevant message flow and message set definitions, check that all necessary user-defined

extensions are installed, perform a complete redeploy of the broker’s configuration and ensure that no applications

are writing to the broker’s configuration queues.

BIP4000 to BIP4999 (Built-in nodes) 221

BIP4042 Invalid action <insert_0> in configuration message.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the invalid action <insert_0>. This

error can only result from configuration messages having an invalid structure.

Response: Ensure that no applications are writing to the broker’s configuration queues.

BIP4043 Invalid action <insert_0> on resource <insert_1> in configuration message.

Severity: 20 : Error

Explanation: The message broker received a configuration message which attempted the action <insert_0> on the

resource <insert_1> but this action is not valid for this type of resource.

Response: Check that all necessary user-defined extensions are installed.

BIP4044 Invalid configuration message.

Severity: 20 : Error

Explanation: The message broker received an invalid configuration message and has not been able to restore its

original configuration. It will now restart.

Response: If the problem is not cleared by the restart, check that the database being used to store the broker’s

persistent state is operating correctly then stop and restart the broker.

BIP4045 Configuration changed successfully.

Severity: 0 : Information

Explanation: The message broker received a configuration message and updated its configuration accordingly. This

change concerned its publish-subscribe capability.

Response: No user action required.

BIP4046 Invalid configuration message. See the following messages for details of the error.

Severity: 20 : Error

Explanation: The publish/subscribe function of the broker has received an invalid configuration message and has

not updated its configuration. This can arise as a result of errors in the specification of the broker topology or topics

which the Configuration Manager was unable to detect. It can also result from the broker having become out of step

with the configuration repository or from other applications sending extraneous messages to the configuration

queues of the broker (SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Response: Check the relevant topology and topic definitions, perform a complete redeploy of the configuration and

ensure that no applications are writing to the configuration queues.

BIP4047 Invalid body type <insert_0> in configuration message.

Severity: 20 : Error

Explanation: The message broker received a configuration message containing the invalid body type <insert_0>. This

error can only result from configuration messages having an invalid structure.

Response: Ensure that no applications are writing to the broker’s configuration queue.

BIP4048 The execution group has received a request to stop.

Severity: 0 : Information

Explanation: The execution group has received a request to stop and will terminate its process as soon as possible.

Response: No user action required.

222 Diagnostic messages

BIP4050 Duplicate labelName attribute <insert_0> in label node.

Severity: 20 : Error

Explanation: Two label nodes within a message flow have been found to have the same labelName attribute

<insert_0>.

Response: The message flow must be changed so that each label node has a unique labelName attribute.

BIP4051 Label node with Label Name attribute <insert_0> could not be found.

Severity: 20 : Error

Explanation: A Label node with Label Name attribute of <insert_0> could not be found by a RouteToLabel node.

Response: The destination list of the message contains a destination label that does not exist. Check the validity of

the SQL in the Compute node that created the destination list.

BIP4052 Unable to create the User Defined Attribute <insert_0> with a type of <insert_1> and a value of

<insert_2>. Recoverable Exception information <insert_3>.

Severity: 20 : Error

Explanation: The User Defined Attribute <insert_0> could not be created. The type <insert_1> or the value

<insert_2> might be invalid. Refer to the Exception information <insert_3> for further information.

Response: A deploy message sent to this broker contains an invalid User Defined Attribute. Correct the User

Defined Attribute and redeploy.

BIP4053 Attempt to create an existing User Defined Attribute <insert_0>.

Severity: 20 : Error

Explanation: The User Defined Attribute <insert_0> already exists

Response: A deploy message sent to this broker contains a message to create an existing User Defined Attribute.

BIP4054 User Defined Attribute <insert_0> does not exist.

Severity: 20 : Error

Explanation: The User Defined Attribute <insert_0> can not be reported or changed as it does not exist

Response: Correct the request for this User Defined Attribute.

BIP4055 (<insert_0>, <insert_1>) : User defined attribute must specify an initial value expression.

Severity: 20 : Error

Explanation: User defined attributes must either be given an initial value on the DECLARE statement or be given a

value at deploy time.

Response: Set the value of the User Defined Attribute at deploy time.

BIP4056 Unsupported data type <insert_0>.

Severity: 20 : Error

Explanation: Internal error during type conversion.

Response: See previous messages for more details.

BIP4000 to BIP4999 (Built-in nodes) 223

BIP4060 Data <insert_0> from trace node <insert_1>.

Severity: 0 : Information

Explanation: The trace node <insert_1> has output the specified trace data.

Response: This is an information message provided by the message flow designer. The user response will be

determined by the local environment.

BIP4061 Invalid trace file path specification for trace node <insert_0>.

Severity: 10 : Warning

Explanation: The trace node <insert_0> has its destination specified to be a file but the given file path is empty. The

message flow processing will continue, but trace output will not be written.

Response: Correct the message flow definition and redeploy it to the broker.

BIP4062 Node (class=<insert_0> name=<insert_1>) did not specify a closing brace in pattern attribute.

Severity: 20 : Error

Explanation: A Trace node in a message flow included an expression within a ’pattern’ attribute. However, the

expression was not terminated with a closing brace character.

Response: Correct the message flow configuration and redeploy the broker.

BIP4063 Node (class=<insert_0>, name=<insert_1>) contained an error in the trace pattern.

Severity: 20 : Error

Explanation: The pattern attribute in the specified trace node was not specified correctly.

Response: Correct the message flow configuration and redeploy the broker.

BIP4064 Operating system error <insert_1> opening trace file <insert_0> for trace node <insert_2>.

Severity: 10 : Warning

Explanation: The trace node <insert_2> attempted to open the trace file <insert_0> but the operating system reported

the error <insert_1>. Message flow processing will continue, but trace output will not be written. The node will

continually attempt to open the file until it succeeds.

Response: If the name or location of the file was not specified correctly, then correct the message flow configuration

and redeploy the broker. If the file could not be opened due to an environment or system error, take appropriate

action to correct this situation.

BIP4065 Operating system error <insert_1> attempting to write to trace file <insert_0> for trace node

<insert_2>.

Severity: 10 : Warning

Explanation: The trace node <insert_2> attempted write to open the trace file <insert_0> but the operating system

reported the error <insert_1>. Message flow processing will continue, but trace output will not be written. The node

will continually attempt to open the file until it succeeds.

Response: If the file could not be opened due to an environment or system error, take appropriate action to correct

this situation.

BIP4066 Unable to output trace data for trace node <insert_0>.

Severity: 10 : Warning

Explanation: The trace node <insert_0> was unable to output trace data during its execution. The following

messages will indicate the reason(s) for this.

Response: Refer to the following messages and take appropriate action.

224 Diagnostic messages

BIP4067 Message propagated to output terminal for trace node <insert_0>.

Severity: 0 : Information

Explanation: The trace node <insert_0> has received a message and is propagating it to any nodes connected to its

output terminal.

Response: No user action required.

BIP4080 Message propagated to try terminal from try-catch node <insert_0>.

Severity: 0 : Information

Explanation: The try-catch node <insert_0> has received a message and is propagating it to any nodes connected to

its try terminal.

Response: No user action required.

BIP4081 Message propagated to catch terminal from try-catch node <insert_0>.

Severity: 0 : Information

Explanation: The try-catch node <insert_0> has caught an exception which occurred in a node connected to its try

terminal. The message has been augmented with an exception list and is propagating it to any nodes connected to its

catch terminal for further processing. See the following messages for details of the exception list.

Response: No user action required.

BIP4101 Exception thrown by throw node <insert_0>.

Severity: 0 : Information

Explanation: The throw node <insert_0> has received a message and will throw an exception as this is its normal

behavior.

Response: No user action required.

BIP4120 Configuration message contained an invalid SQL expression; compute node <insert_0> in message

flow <insert_1>.

Severity: 20 : Error

Explanation: The compute node <insert_0> in message flow <insert_1> reported an error processing its compute

expression.

Response: See the following messages for details of the error.

BIP4121 Syntax error in SQL statements in compute node <insert_2>.

Severity: 20 : Error

Explanation: The configuration of compute node <insert_2> failed due to errors in the SQL expression. See the

following messages for details of the error. The statement text was <insert_1>.

Response: The next error message will give specific details of where the error occurred in the statement text. Check

the correct syntax for compute node SQL statements in the WebSphere Message Brokers publications. Correct the

statements configuring the node and redeploy the configuration.

BIP4123 Incorrect return type <insert_0> in compute node <insert_2>. The value returned was <insert_1>.

Severity: 20 : Error

Explanation: Return statements in compute nodes must return a value of type ’bool’

Response: Examine the logic of the given node’s SQL statements, correct them and redeploy.

BIP4000 to BIP4999 (Built-in nodes) 225

BIP4124 Message propagated to ’out’ terminal of compute node <insert_0>.

Severity: 0 : Information

BIP4140 Exception condition detected by user-defined node <insert_0>.

Severity: 0 : Information

Explanation: The user-defined node <insert_0> detected an error during processing. The behavior of the message

flow will depend upon how the user-defined node has reacted to the generation of the exception. A well behaved

user-defined node is expected to re-throw the exception for it to be caught and handled by the message flow as

normal.

Response: Check any error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP4141 Exception condition detected in user-defined node or parser <insert_6>. Arguments: type <insert_0>;

file <insert_1>; line <insert_2>; function <insert_3>; messageNumber <insert_4>; traceText <insert_5>.

Severity: 20 : Error

Explanation: The user-defined node or parser <insert_6> has attempted to throw an exception by calling the

cciThrowException() utility function, but the exception type specified in the ’type’ argument was invalid. This is a

problem within the user-defined extension software itself.

Response: Correct the problem in the user-defined extension software or contact the supplier of the user-defined

extension to report the problem.

BIP4142 Evaluating cniElementSet<insert_0>. Changing value from <insert_1> to <insert_2>.

Severity: 0 : Information

Explanation: Element <insert_0> has been changed to <insert_2>.

Response: No user action required.

BIP4143 Invalid terminal name.

Severity: 20 : Error

Explanation: An attempt was made to create a terminal with no name.

Response: Ensure the terminal has a valid name.

BIP4144 Entered function <insert_0>(<insert_1>, <insert_2>, <insert_3>, <insert_4>, <insert_5>, <insert_6>,

<insert_7>, <insert_8>, <insert_9>, <insert_10>, <insert_11>).

Severity: 0 : Information

Explanation: Entered the specified function with the specified parameters.

Response: No user action required.

BIP4145 Exiting function <insert_0> with result: <insert_1>(<insert_2>).

Severity: 0 : Information

Explanation: About to exit the specified the function with the specified result.

Response: No user action required.

226 Diagnostic messages

BIP4146 Evaluating cpiSetElement<insert_0>. Changing value from <insert_1> to <insert_2>.

Severity: 0 : Information

Explanation: Element <insert_0> has been changed to <insert_2>.

Response: No user action required.

BIP4147 User-defined extension input parameter failed debug validation check.

Severity: 20 : Error

Explanation: Input parameter <insert_1> passed into function <insert_0> is not a valid object.

Response: Correct user-defined extension implementation accordingly.

BIP4148 User-defined extension damaged broker’s object.

Severity: 20 : Error

Explanation: Function <insert_0> has damaged broker’s object passed as parameter <insert_1>.

Response: Correct user-defined extension implementation accordingly.

BIP4149 User-defined extension input parameter failed debug validation check.

Severity: 20 : Error

Explanation: Input parameter <insert_1> passed into function <insert_0> is a NULL pointer.

Response: Correct user-defined extension implementation accordingly.

BIP4150 User-defined extension input parameter failed debug validation check.

Severity: 20 : Error

Explanation: Input parameter <insert_1> passed into function <insert_0> does not have a valid value.

Response: Correct user-defined extension implementation accordingly.

BIP4151 An unexpected value was returned from User-defined extension implementation function <insert_0>.

Severity: 20 : Error

Explanation: The implementation function returned <insert_1> but the expected values are <insert_2>.

Response: Correct user-defined extension implementation accordingly.

BIP4152 User-defined extension Implementation function <insert_0> returned CCI_BUFFER_TOO_SMALL on

2nd attempt.

Severity: 20 : Error

Explanation: The implementation function <insert_0> has set the returnCode output parameter to

CCI_BUFFER_TOO_SMALL and returned <insert_1> as the required size of the buffer in characters. The function was

then invoked with a buffer of this size and again set returnCode to CCI_BUFFER_TOO_SMALL.

Response: Correct user-defined extension implementation accordingly.

BIP4153 The user-defined property (UDP) <insert_0> has an invalid data type <insert_1>.

Severity: 20 : Error

Explanation: The datatype <insert_1> is not supported as a UDP. This can be due to using versions of runtime

components that are incompatible with your Message Brokers Toolkit.

Response: Make sure that you are using versions of runtime components that are compatible with your Message

Brokers Toolkit.

BIP4000 to BIP4999 (Built-in nodes) 227

BIP4154 The user-defined property (UDP) <insert_0> of datatype <insert_1> has an incorrect structure. Reason:

<insert_2>

Severity: 20 : Error

Explanation: An internal problem has occurred trying to construct the datatype <insert_1>. This can be due to using

versions of runtime components that are incompatible with your Message Brokers Toolkit.

Response: Make sure that you are using versions of runtime components that are compatible with your Message

Brokers Toolkit.

BIP4155 A dynamic terminal called <insert_1> (of type <insert_0>) could not be created because there is

already a terminal with that name.

Severity: 20 : Error

Explanation: The message flow definition deployed to the broker either defines a new terminal with the same name

as one that already exists, or it defines the same terminal twice. This can be due to using versions of runtime

components that are incompatible with your Message Brokers Toolkit.

Response: Make sure that you are using versions of runtime components that are compatible with your Message

Brokers Toolkit.

BIP4156 A dynamic terminal of type <insert_0> (called <insert_1>) could not be created because this type of

dynamic terminal is not allowed.

Severity: 20 : Error

Explanation: You can only create a dynamic terminal of type ’output’ or ’input’.

Response: This is an internal error. Contact your IBM support center.

BIP4157 The user-defined node <insert_0> could not be deployed. Details: <insert_1>

Severity: 20 : Error

Explanation: The node could not be deployed because an error in the node’s ’onInitialize’ method prevented the

node from initializing.

Response: Review the details given above. Report the error to the node’s writer if you cannot correct the error

yourself.

BIP4160 Message propagated to match terminal by check node <insert_0>.

Severity: 0 : Information

Explanation: The check node <insert_0> has matched a received message against the criteria and is propagating it to

any nodes connected to its match terminal.

Response: No user action required.

BIP4161 Message propagated to failure terminal by check node <insert_6>. Values received: domain

<insert_0>; set <insert_1>; type <insert_2>. Values expected: domain <insert_3>; set <insert_4>; type

<insert_5>.

Severity: 20 : Error

Explanation: The check node <insert_6> has detected that a received message did not match the specified criteria

and that there is a message flow processing node attached to its failure terminal and thus the message is being

propagated to any nodes connected to that terminal.

228 Diagnostic messages

BIP4162 Nonmatching message rejected by check node <insert_6>. Values received: domain <insert_0>; set

<insert_1>; type <insert_2>. Values expected: domain <insert_3>; set <insert_4>; type <insert_5>.

Severity: 20 : Error

Explanation: The check node <insert_6> has detected that the input message did not match the specified criteria and

that there is NOT a message flow processing node attached to its failure terminal. An exception is therefore being

generated.

Response: Identify why invalid messages are either being sent into the broker or being generated, correcting the

problem if necessary. If the check node attributes are not being specified correctly, correct them and redeploy the

message broker.

BIP4163 Message propagated to the first terminal of the FlowOrder node <insert_0>.

Severity: 0 : Information

Explanation: The FlowOrder node has received a message and has propagated it to the output terminal called first.

Once the processing of the message down the first terminal has finished, the message will be propagated to the

second terminal.

Response: No user action required.

BIP4164 Message propagated to the second terminal of the FlowOrder node <insert_0>.

Severity: 0 : Information

Explanation: The FlowOrder node has finished processing a message down the first terminal and has propagated it

to the second terminal.

Response: No user action required.

BIP4180 Message propagated to output terminal by database node <insert_0>.

Severity: 0 : Information

Explanation: The database node <insert_0> has received a message and is propagating it to any nodes connected to

its output terminal.

Response: No user action required.

BIP4181 Syntax error in SQL statements in database node <insert_2>.

Severity: 20 : Error

Explanation: The configuration of database node <insert_2> failed due to errors in the SQL statement text. See the

following messages for details of the error. The statement text was <insert_1>.

Response: The next error message will give specific details of where the error occurred in the statement text. Check

the correct syntax for database node SQL statements in the WebSphere Message Brokers publications. Correct the

statements and redeploy the configuration.

BIP4183 Incorrect return type <insert_0> in database node <insert_2>. The value returned was <insert_1>.

Severity: 20 : Error

Explanation: Return statements in database nodes must return a value of type ’bool’

Response: Examine the logic of the given node’s SQL statements, correct them and redeploy.

BIP4184 Message propagated to ’out’ terminal of database node <insert_0>.

Severity: 0 : Information

BIP4000 to BIP4999 (Built-in nodes) 229

BIP4201 Message propagated to out terminal from node <insert_0>.

Severity: 0 : Information

Explanation: A reset content descriptor node has received a message and is propagating it to any nodes connected

to its out terminal.

Response: No user action required.

BIP4202 The WebSphere MQ Everyplace queue manager failed to start.

Severity: 30 : Severe error

Explanation: The WebSphere MQ Everyplace queue manager failed to start.

Response: Ensure that the queue manager has been created and that the registry entry is correct.

BIP4203 The internal WebSphere MQ Everyplace transformer component failed to initialize.

Severity: 30 : Severe error

Explanation: The internal WebSphere MQ Everyplace transformer component failed to initialize.

Response: Ensure that a valid transformer is being used within WebSphere MQ Everyplace.

BIP4204 WebSphere MQ Everyplace configuration error.

Severity: 30 : Severe error

Explanation: WebSphere MQ Everyplace configuration error.

Response: If using a WebSphere MQ Everyplace ini file, please ensure that it is valid.

BIP4205 A WebSphere MQ Everyplace error occurred. The exact nature of the problem could not be

determined.

Severity: 30 : Severe error

Explanation: A WebSphere MQ Everyplace error occurred. The exact nature of the problem could not be

determined.

Response: Please refer to trace messages before this error occurred.

BIP4206 The mqimqe.jar file could not be loaded.

Severity: 30 : Severe error

Explanation: The mqimqe.jar could not be read at runtime.

Response: Ensure that the file exists within the application.

BIP4207 A WebSphere MQ Everyplace method could not be accessed.

Severity: 20 : Error

Explanation: A WebSphere MQ Everyplace method within the mqimqe.jar file could not be accessed.

Response: Ensure that the mqimqe.jar file is not damaged.

BIP4208 WebSphere MQ Everyplace database error. Cannot write to inbound table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to write to the WebSphere MQ Everyplace inbound table.

Response: Ensure that the database tables exist and that the application has appropriate access.

230 Diagnostic messages

BIP4209 Error attempting to write to WebSphere MQ Everyplace outbound database table.

Severity: 30 : Severe error

Explanation: An error was encountered whilst attempting to write to the WebSphere MQ Everyplace outbound

database table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4210 WebSphere MQ Everyplace database error. Cannot write to outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to write to the WebSphere MQ Everyplace destination table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4211 WebSphere MQ Everyplace database error. Cannot read from inbound table.

Severity: 20 : Error

Explanation: An error occurred whilst attempting to read from the WebSphere MQ Everyplace inbound table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4212 WebSphere MQ Everyplace database error. Cannot read from outbound message table.

Severity: 20 : Error

Explanation: An error occurred whilst attempting to read from the WebSphere MQ Everyplace outbound message

table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4213 WebSphere MQ Everyplace database error. Cannot read a record from outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to read a record from the WebSphere MQ Everyplace destination

table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4214 WebSphere MQ Everyplace database error. Cannot delete record from inbound table.

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete the WebSphere MQ Everyplace inbound message table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4215 WebSphere MQ Everyplace database error. Cannot delete record from outbound table.

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete a record from the WebSphere MQ Everyplace outbound

message table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4216 WebSphere MQ Everyplace database error. Cannot delete record from outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete a WebSphere MQ Everyplace outbound destination

message record.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4000 to BIP4999 (Built-in nodes) 231

BIP4217 WebSphere MQ Everyplace database error. Cannot put non-publish/subscribe WebSphere MQ

Everyplace message to table.

Severity: 30 : Severe error

Explanation: Cannot put non-publish/subscribe WebSphere MQ Everyplace message to inbound WebSphere MQ

Everyplace table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4218 Cannot read non-publish/subscribe WebSphere MQ Everyplace message from table.

Severity: 30 : Severe error

Explanation: Cannot read a non-publish/subscribe WebSphere MQ Everyplace message from table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4219 WebSphere MQ Everyplace database error. Cannot delete non-publish/subscribe WebSphere MQ

Everyplace message from the database table.

Severity: 30 : Severe error

Explanation: Cannot delete a non-publish/subscribe WebSphere MQ Everyplace message from table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4220 Message propagated to out terminal from node <insert_0>.

Severity: 0 : Information

Explanation: A label node has received a message and is propagating it to any nodes connected to its out terminal.

Response: No user action required.

BIP4221 Some (but not all) of the WebSphere MQ Everyplace tables are missing.

Severity: 20 : Error

Explanation: Some (but not all) of the WebSphere MQ Everyplace tables are missing.

Response: Recreate the broker.

BIP4222 The mqisdp.jar file could not be loaded.

Severity: 30 : Severe error

Explanation: The mqisdp.jar could not be read at runtime.

Response: Ensure that the file exists within the application.

BIP4223 A SCADA method could not be accessed.

Severity: 30 : Severe error

Explanation: A SCADA method within the mqisdp.jar file could not be accessed.

Response: Ensure that the mqisdp.jar file is not damaged.

BIP4224 SCADA database error. Cannot write to inbound table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to write to the SCADA inbound table.

Response: Ensure that the database tables exist and that the application has appropriate access.

232 Diagnostic messages

BIP4225 Error attempting to write to SCADA outbound database table.

Severity: 30 : Severe error

Explanation: An error was encountered whilst attempting to write to the SCADA outbound database table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4226 SCADA database error. Cannot write to outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to write to the SCADA destination table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4227 SCADA database error. Cannot read from inbound table.

Severity: 20 : Error

Explanation: An error occurred whilst attempting to read from the SCADA inbound table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4228 SCADA database error. Cannot read from outbound message table.

Severity: 20 : Error

Explanation: An error occurred whilst attempting to read from the SCADA outbound message table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4229 SCADA database error. Cannot read from outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred whilst attempting to write to the SCADA destination table.

Response: Ensure that the database tables exist and that the application has appropriate access.

BIP4230 SCADA database error. Cannot delete record from inbound table.

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete the SCADA inbound message table.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4231 SCADA database error. Cannot delete record from outbound table

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete a record from the SCADA inbound message table

Response: Ensure that the database tables exist and that the application has appropriate access to the database

BIP4232 SCADA database error. Cannot delete record from outbound destination table.

Severity: 30 : Severe error

Explanation: An error occurred when attempting to delete a SCADA outbound destination message record.

Response: Ensure that the database tables exist and that the application has appropriate access to the database.

BIP4000 to BIP4999 (Built-in nodes) 233

BIP4233 Could not resolve destination node using specified port number.

Severity: 10 : Warning

Explanation: Could not resolve destination node using specified port number. A subscription has been made by a

node that no longer exists.

Response: Unsubscribe from all subscriptions for the node no longer being used.

BIP4234 Failed to get a message from the queue.

Severity: 10 : Warning

Explanation: Failed to get a message from the queue.

Response: No user action required.

BIP4235 Failed to put a message onto the queue.

Severity: 30 : Severe error

Explanation: Failed to put a message onto the queue.

Response: Queue may be full. No user action required.

BIP4236 Node <insert_0> failed to bind to port <insert_1>

Severity: 30 : Severe error

Explanation: The port number specified for the node is already being used in another message flow, or is

unavailable for some other reason.

Response: Change the port number to one not being used by another message flow or by another quite separate

application. If one message flow is replacing another using the same port number, use a full rather than a delta

deploy. This ensures that the old flow is removed from service at the broker before the new flow is introduced.

BIP4237 SCADA Initialization failed.

Severity: 10 : Warning

Explanation: An internal error stopped the SCADA server from starting.

Response: Redeploy the message flow.

BIP4238 MQIsdp manager not available.

Severity: 30 : Severe error

Explanation: Initialization problem with the SCADA node.

Response: Redeploy the message flow.

BIP4239 Some of the SCADA database tables are missing.

Severity: 30 : Severe error

Explanation: The SCADA Input node was unable to find all of the database tables required for correct operation

Response: Recreate the broker.

BIP4240 RouteToLabel node <insert_1> unable to locate Label node <insert_0>.

Severity: 20 : Error

Explanation: A RouteToLabel node has received a message containing a label but there is no Label node with this

label.

Response: This problem may result from the logic of the message flow as specified by the user not calculating a

234 Diagnostic messages

valid Label node name for all valid input messages, from the input message being of an unexpected nature or from

the deployed configuration not being as intended. Check the logic of the message flow to ensure that in all cases the

calculated Label node names will be correct and then check that the input message is not of an unexpected nature.

Finally ensure that the message flow, and any nested message flows have been saved. Redeploy the new

configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact

your IBM support center.

BIP4241 Message propagated to target Label node by RouteToLabel node <insert_0>.

Severity: 0 : Information

Explanation: A RouteToLabel node has received a message and is propagating it to the appropriate Label node.

Response: No user action required.

BIP4242 Failure putting message to <insert_3> queue manager <insert_0>, queue <insert_1>, from node type

<insert_2>

Severity: 20 : Error

Explanation: WebSphere Message Brokers failed in an attempt to put a message.

Response: Examine the message flow nodes, and make any corrections that may be necessary. For example, an

MQeOutput node may include an incorrect Destination Mode, Queue Manager Name or Queue Name property.

BIP4243 Unexpected message number <insert_0> received from <insert_1> for node type <insert_2>

Severity: 20 : Error

Explanation: An internal error occurred in communication within WebSphere Message Brokers.

Response: Your installation of WebSphere Message Brokers requires service. Pass details of this message to your

administrator.

BIP4244 WebSphere MQ Everyplace redirection error

Severity: 20 : Error

Explanation: An attempt to redirect output from WebSphere MQ Everyplace for the trace file failed.

Response: Check that the file details for the WebSphere MQ Everyplace trace file are correct and that the file can be

written to.

BIP4245 WebSphere MQ Everyplace configuration template error

Severity: 20 : Error

Explanation: An error occurred either creating or expanding a configuration template for WebSphere MQ

Everyplace.

Response: Refer to the WebSphere MQ Everyplace trace file for further information.

BIP4246 WebSphere Everyplace JNI initialization failure

Severity: 30 : Severe error

Explanation: A node is unable to communicate with WebSphere Everyplace using the JNI.

Response: Check that the Java code in the CLASSPATH used by WebSphere Message Brokers is not damaged.

BIP4247 Unable to get message from SCADA

Severity: 20 : Error

Explanation: The buffer allocated internally for a message from SCADA is too small.

Response: Report this error to your IBM Support Center.

BIP4000 to BIP4999 (Built-in nodes) 235

BIP4248 Unable to confirm WebSphere MQ Everyplace message with Unique ID <insert_0>

Severity: 10 : Warning

Explanation: The WebSphere MQ Everyplace message with the given Unique ID could not be confirmed. This may

be because no message with the ID was previously received, or because the message previously received can no

longer be referenced by the broker. The Unique ID comprises the 2 WebSphere MQ Everyplace properties

MQe.Msg_OriginQMgr and MQe.Msg_Time, concatenated with an intervening period.

Response: Check WebSphere MQ Everyplace client programs for the correct use of confirmPutMessage. Check that

there have been no broker database errors that may have caused messages to be lost during database recovery.

BIP4249 Scada Thread pool is busy.

Severity: 20 : Error

Explanation: The Scada thread pool is overloaded or has stopped working.

Response: If there is no co-responding BIP4250 message then the Scada thread pool may have stopped working or

is overloaded.

BIP4250 Scada Thread pool has recovered.

Severity: 10 : Warning

Explanation: The Scada thread pool has recovered from an overloaded period.

Response: This indicates that the Scada thread pool has recovered after an overloaded condition.

BIP4260 A memory allocation error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in allocating the thread local storage index.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4261 A thread creation error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in creating a thread responsible for transmitting the

breakpoint information.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4262 An initialization error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in creating the node factory provided by the interface

cniCreateNodeFactory.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4263 An operational error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in defining a node class within the node factory.

Response: Check if the XML definition of the node ImbDebugNode is valid and retry the operation. If this problem

persists, contact your IBM support center.

236 Diagnostic messages

BIP4264 A threading problem occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in blocking incoming threads, the Message Brokers Toolkit

debugger might not work properly.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4265 A mutual exclusion error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in releasing a mutex object.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4266 Unable to get an attribute from a node.

Severity: 20 : Error

Explanation: The attribute ’FlowUuid’ could not be received from the node ImbDebugNode.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4267 Unable to get an attribute from a node.

Severity: 20 : Error

Explanation: The attribute ’DebugNodeID’ could not be received from the node ImbDebugNode.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4268 A mutual exclusion error occurred.

Severity: 20 : Error

Explanation: An access violation occurred while waiting for a mutex object in the node ImbDebugNode.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4269 A propagation error occurred.

Severity: 10 : Warning

Explanation: The node ImbDebugNode was unsuccessful to propagate a message.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4270 A propagation error occurred.

Severity: 20 : Error

Explanation: An Output terminal is not connected.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4271 An element error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode received an unknown value type for an element.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4000 to BIP4999 (Built-in nodes) 237

BIP4272 An element error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in extracting an element value.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4273 An element error occurred.

Severity: 10 : Warning

Explanation: The node ImbDebugNode was unsuccessful in extracting an element name.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4274 An element error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in extracting an element type.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4275 An element error occurred.

Severity: 10 : Warning

Explanation: The node ImbDebugNode was unsuccessful in setting an element value.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4276 A terminal creation error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in creating an Input terminal.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4277 A terminal creation error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in creating an Output terminal.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4278 A create node error occurred.

Severity: 20 : Error

Explanation: The node name is not supported for the node ImbDebugNode.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

238 Diagnostic messages

BIP4279 A communication setting error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in getting the controller IP address.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4280 A reception error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in receiving information from the Message Brokers Toolkit.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4281 A socket error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in creating a socket.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4282 A socket error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in setting the socket options.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4283 A connection error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in connecting to a Message Brokers Toolkit socket.

Response: Restart your broker, restart your Message Brokers Toolkit and retry the operation. If this problem persists,

contact your IBM support center.

BIP4284 A sending error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in sending information to the Message Brokers Toolkit.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4285 A socket error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in binding a socket.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4000 to BIP4999 (Built-in nodes) 239

BIP4286 A socket error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in listening to a client connection.

Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact

your IBM support center.

BIP4287 A memory allocation error occurred.

Severity: 20 : Error

Explanation: The node ImbDebugNode was unsuccessful in allocating memory.

Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

BIP4302 WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.

Severity: 20 : Error

Explanation: WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.

Response: Add the required name/value pair and redeploy the message flow.

BIP4303 The trace file for WebSphere MQ Everyplace could not be created

Severity: 20 : Error

Explanation: The trace file specified for WebSphere MQ Everyplace trace could not be created.

Response: Ensure that your disk is not full and that this file is not write protected.

BIP4342 WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.

Severity: 20 : Error

Explanation: WebSphere MQ Everyplace bridge queue name is not specified. This is a mandatory field.

Response: Add the required name/value pair and redeploy the message flow.

BIP4343 The trace file for WebSphere MQ Everyplace could not be created

Severity: 20 : Error

Explanation: The trace file specified for WebSphere MQ Everyplace could not be created.

Response: Ensure that your disk is not full and that this file is not write protected.

BIP4350 An error has occurred in the debugger.

Severity: 30 : Severe error

Explanation: An internal error has occurred in the debugger.

Response: Contact your local IBM support center.

BIP4351 An error has occurred in the debugger’s Remote Agent Controller

Severity: 20 : Error

Explanation: The Remote Agent Controller is a separate process used to debug the broker.

Response: Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM

support center.

240 Diagnostic messages

BIP4352 An error occurred when trying to communicate with the debugger

Severity: 30 : Severe error

Explanation: Observe any following errors and try to correct them. If you are unable to do so, please contact your

IBM support center.

BIP4353 An error occurred in the JNI layer during flow debugging

Severity: 20 : Error

Explanation: Observe any following errors and try to correct them. If you are unable to do so, please contact your

IBM support center.

BIP4354 An error occurred when invoking the debugger

Severity: 30 : Severe error

Explanation: Observe any following errors and try to correct them. If you are unable to do so, please contact your

IBM support center.

BIP4360 Java node information: <insert_0>.

Severity: 0 : Information

Explanation: Information message generated by Java node.

Response: No user action required.

BIP4361 Java node warning: <insert_0>.

Severity: 10 : Warning

Explanation: Warning message generated by user Java node.

Response: Contact the node provider for further details.

BIP4362 Java node error: <insert_0>.

Severity: 20 : Error

Explanation: Error message generated by user Java node.

Response: Contact the node provider for further details.

BIP4363 The Java API framework could not locate the <insert_0>: <insert_1>.

Severity: 30 : Severe error

Explanation: An internal JNI error has occurred during property introspection.

Response: This is an internal error. Contact your IBM support center.

BIP4364 The Java API framework could not create an instance of <insert_0>.

Severity: 30 : Severe error

Explanation: An internal JNI error has occurred during object instantiation.

Response: This is an internal error. Contact your IBM support center.

BIP4000 to BIP4999 (Built-in nodes) 241

BIP4365 The Java API framework could not create an array of <insert_0>, size[<insert_1>].

Severity: 30 : Severe error

Explanation: An internal JNI error has occurred during the creation of an array.

Response: This is an internal error. Contact your IBM support center.

BIP4366 Unable to create Java node <insert_0> of type <insert_1>.

Severity: 20 : Error

Explanation: An exception has occurred during the creation of the Java node: <insert_2>

Response: Contact the node provider for further details.

BIP4367 The method <insert_0> in Java node <insert_1> has thrown the following exception: <insert_2>.

Severity: 20 : Error

Explanation: The method <insert_0> of the Java node has thrown an exception. Examine previous error messages for

details of the cause of the problem.

Response: This error is generated by the Java node API. It can occur in a Java Compute node or a Java user-defined

node. If the node is a user-defined node, contact the node provider for further details.

BIP4368 The method <insert_0> has thrown the following exception: <insert_1>.

Severity: 30 : Severe error

Explanation: The Java API framework has caught an unhandled Java exception.

Response: Contact the node provider for further details.

BIP4369 A memory allocation error has occurred.

Severity: 20 : Error

Explanation: The Java API framework was unsuccessful in allocating memory.

Response: Restart you broker and retry the operation. If the problem persists, contact your IBM support center.

BIP4370 Failure in CNI layer, return code is <insert_0>.

Severity: 20 : Error

Explanation: An internal error has occurred in the CNI layer of the user-defined node interface.

Response: This is an internal error. Contact your IBM support center.

BIP4371 Failure to locate Java class <insert_0>

Severity: 30 : Severe error

Explanation: The Java class <insert_0> could not be found by the Java API framework.

Response: This is an internal error. Contact your IBM support center.

BIP4372 Failure to locate Java method or field <insert_0> in class <insert_1>.

Severity: 30 : Severe error

Explanation: The Java method or field <insert_0> in class <insert_1> could not be found by the Java API framework.

Response: This is an internal error. Contact your IBM support center.

242 Diagnostic messages

BIP4373 Element value type <insert_0> is not valid.

Severity: 30 : Severe error

Explanation: The object supplied to MbElement.setValue(...) is not a supported type.

Response: Contact the node provider for further details.

BIP4374 An unexpected exception has occurred in the Java API framework.

Severity: 30 : Severe error

Explanation: An internal processing error has occurred.

Response: This is an internal error. Contact your IBM support center.

BIP4375 The transaction type <insert_0> is not recognized.

Severity: 20 : Error

Explanation: The transaction type supplied to the constructor of the SQL statement has not been recognized.

Response: Contact the node provider for further details.

BIP4376 Unable to locate resource bundle <insert_0>.

Severity: 30 : Severe error

Explanation: The Java resource bundle could not be found by the Java API framework.

Response: Make sure the Java resource bundle is in the CLASSPATH and restart the broker.

BIP4377 The user node <insert_0> does not have a default constructor.

Severity: 30 : Severe error

Explanation: The Java API framework was unable to find a default constructor for the user node.

Response: Contact the node provider for further details.

BIP4378 The <insert_0> object has been cleared

Severity: 30 : Severe error

Explanation: The node implementation has attempted to reference an object which has previously been cleared.

Response: Contact the node provider for further details.

BIP4379 An STL exception has been thrown by <insert_0>.

Severity: 30 : Severe error

Explanation: An unexpected STL exception has been thrown.

Response: This is an internal error. Contact your IBM support center.

BIP4380 The terminal <insert_0> already exists.

Severity: 20 : Error

Explanation: An attempt has been made to create a terminal with a name that has already been used.

Response: Make sure that the terminal name is unique.

BIP4000 to BIP4999 (Built-in nodes) 243

BIP4381 Element type <insert_0> is not valid.

Severity: 20 : Error

Explanation: An attempt has been made to create an element with an invalid type.

Response: Contact the node provider for further details.

BIP4382 XPath parse error at column <insert_1> in expression <insert_0>.

Severity: 20 : Error

Explanation: The XPath parser encountered a syntax error in the expression.

Response: Refer to the XPath 1.0 W3C recommendation for syntax rules.

BIP4383 XPath: Both arguments of the union operator must evaluate to nodesets

Severity: 10 : Warning

Explanation: One or both of the arguments to the union (|) operator evaluated to a non-nodeset type.

Response: Refer to the XPath 1.0 W3C recommendation for usage details.

BIP4384 XPath: Function <insert_0> is not in the XPath 1.0 specification or is not a broker extension function.

Severity: 10 : Warning

Explanation: The XPath processor encountered an unsupported function call in the expression.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4385 XPath: Function has been passed too many arguments.

Severity: 10 : Warning

Explanation: The XPath processor has encountered an unexpected comma (,) operator suggesting that a function has

been passed too many arguments.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4386 XPath: Expression before relative location path does not evaluate to a nodeset.

Severity: 10 : Warning

Explanation: The expression preceding the relative location path (starting with /) must evaluate to a nodeset.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4387 XPath: Predicates can only be applied to a nodeset.

Severity: 10 : Warning

Explanation: The expression preceding a predicate must evaluate to a nodeset type.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4388 XPath: The variable <insert_0> is not bound to a value.

Severity: 10 : Warning

Explanation: The XPath processor encountered an unbound variable reference in the expression.

Response: Bind a value to the variable reference before evaluating the expression.

244 Diagnostic messages

BIP4389 XPath: An internal state error was encountered by the XPath evaluator (opcode <insert_0>).

Severity: 20 : Error

Explanation: An internal state error was encountered by the XPath evaluator.

Response: Contact your IBM service representative.

BIP4390 XPath: The function <insert_0> has been passed the wrong number of arguments.

Severity: 10 : Warning

Explanation: The function has been passed the wrong number of arguments.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4391 XPath: The argument of function <insert_0> does not evaluate to a nodeset.

Severity: 10 : Warning

Explanation: The function argument must evaluate to a nodeset type.

Response: Refer to the XPath 1.0 W3C recommendation for syntax usage.

BIP4392 XPath: The function ’id’ is not supported by the broker.

Severity: 10 : Warning

Explanation: The function ’id’ is not supported by the broker.

Response: Avoid use of the XPath function ’id’.

BIP4393 XPath: The broker extension function <insert_0> requires one argument.

Severity: 10 : Warning

Explanation: The broker extension function requires one argument.

Response: Check the appropriate function call in the XPath expression.

BIP4394 Java exception: <insert_0>; thrown from class name: <insert_1>, method name: <insert_2>, file:

<insert_3>, line: <insert_4>; trace text: <insert_5>; resource bundle: <insert_6>; key: <insert_7>;

inserts(optional): <insert_8>, <insert_9>, <insert_10>, <insert_11>, <insert_12>, <insert_13>, <insert_14>,

<insert_15>, <insert_16>, <insert_17>

Severity: 20 : Error

Explanation: The message contains that data associated with a Java exception.

Response: No user action required.

BIP4395 Java exception: <insert_0>; thrown from class name: <insert_1>, method name: <insert_2>, file:

<insert_3>, line: <insert_4>

Severity: 20 : Error

Explanation: The message contains that data associated with a Java exception.

Response: No user action required.

BIP4396 <insert_0> is not a valid PAR. A PAR file must contain a classes directory.

Severity: 10 : Warning

Explanation: <insert_0> doesn’t contain a classes directory that is required by the PAR file format.

Response: Consult the product documentation and repackage the user-defined node into a valid PAR file.

BIP4000 to BIP4999 (Built-in nodes) 245

BIP4397 Loading class <insert_0> from path <insert_1> in <insert_2>.

Severity: 0 : Information

Explanation: Broker JVM class loading information.

Response: No user action required.

BIP4398 Loading class <insert_0> from path <insert_1> in JAR <insert_2> packaged in PAR <insert_3>.

Severity: 0 : Information

Explanation: Broker JVM class loading information.

Response: No user action required.

BIP4401 Message propagated to out terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateControl node has received a message and is propagating it to any nodes connected to its

out terminal

Response: No user action required

BIP4402 Message propagated to control terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateControl node has received a message and is propagating a control message to any nodes

connected to its control terminal

Response: No user action required

BIP4403 The control terminal is not connected.

Severity: 20 : Error

Explanation: The control terminal on the AggregateControl node is not connected to any other nodes.

Response: Check the message flow and ensure that the control terminal on the AggregateControl node is ultimately

connected to the control terminal on the corresponding AggregateReply node. This is to ensure control messages

from the AggregateControl node reach the AggregateReply node.

BIP4404 Existing aggregation data found in LocalEnvironment

Severity: 20 : Error

Explanation: The LocalEnvironment.ComIbmAggregateControlNode area reserved for AggregateControl node data

already contains information. This message may already have passed through an AggregateControl node.

Response: Check that the message flow does not contain two AggregateControl nodes which are connected in

series.

BIP4405 Aggregation data in LocalEnvironment is invalid

Severity: 20 : Error

Explanation: The LocalEnvironment.ComIbmAggregateControlNode area reserved for passing information from an

AggregateControl node to an AggregateRequest node does not contain valid data.

Response: Check that the message has passed through an AggregateControl node before arriving at the

AggregateRequest node. Check that this LocalEnvironment data has not been lost. Nodes such as the Compute node

should copy the LocalEnvironment before changing it, and should propagate it using a propagation option including

LocalEnvironment.

246 Diagnostic messages

BIP4406 Missing or invalid destination data in LocalEnvironment.WrittenDestination

Severity: 20 : Error

Explanation: Part of the destination data required by the AggregateRequest node and contained in

LocalEnvironment.WrittenDestination is missing or not valid. This data is usually inserted by an output node.

Response: Check that the message has previously passed through a node designed to support aggregation. The

MQOutput node and MQeOutput node are two examples. Check that this LocalEnvironment data has not been lost.

Nodes such as the Compute node should copy the LocalEnvironment before changing it, and should propagate it

using a propagation option including LocalEnvironment.

BIP4407 Message propagated to out terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateRequest node has received a message and is propagating it to any nodes connected to its

out terminal

Response: No user action required

BIP4408 Could not allocate a thread for timeout processing in AggregateReply node.

Severity: 30 : Severe error

Explanation: The AggregateReply node requires a thread to perform timeout processing. This demand has been

refused. Normal function cannot continue without this thread.

Response: The operating system may have run low on threads. Try to make more threads available. Try reducing

the number of threads used by a message flow by decreasing the value of the ’Additional Instances’ attribute from

the ’Assignments’ panel.

BIP4409 Control message arrived from different broker (UUID <insert_0>).

Severity: 20 : Error

Explanation: The control message received through the control terminal originated from an AggregateControl node

on another broker. The sending broker’s UUID is included in the message.

Response: Ensure that the AggregateControl node that the control message originated from, and the AggregateReply

node which received it, are on the same broker.

BIP4410 The AggregateReply node has a different aggregate name (<insert_0>) to the corresponding

AggregateControl node (<insert_1>)).

Severity: 20 : Error

Explanation: The control message originated from an AggregateControl node with a different aggregate name.

Response: Ensure that the AggregateControl node that the control message originated from, and the AggregateReply

node which received it, have the same value for the ’aggregate name’ attribute.

BIP4411 Message propagated to out terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateReply node has received a message and is propagating it to any nodes connected to its

out terminal

Response: No user action required

BIP4000 to BIP4999 (Built-in nodes) 247

BIP4412 Corresponding request record not found for the reply message.

Severity: 0 : Information

Explanation: An AggregateReply node has received a message at its ’in’ terminal. No corresponding record of a

request message being sent could be found. See subsequent messages to determine how this situation has been

handled.

Response: It is possible that extraneous messages are arriving at the AggregateReply node ’in’ terminal. Check your

flow to ensure that the only messages arriving here are replies to request messages previously sent out and passed

through an AggregateRequest node. It is possible that this message is a valid reply but part of an aggregation which

previously timed out. It is possible that this is a reply to a message which has not yet been recorded by an

AggregateRequest node. This can happen if request messages are sent outside of transactional control. Adjust your

transaction settings to ensure that messages are sent under transactional control.

BIP4413 Storing unknown message persistently for subsequent processing.

Severity: 0 : Information

Explanation: The message has been stored persistently by the AggregateReply node. If it is subsequently discovered

to be a valid reply in an aggregation then it will be processed as such at that time. If a number of seconds passes as

specified by the ’unknown timeout’ attribute, then the message will be propagated to the ’unknown’ terminal.

Response: No user action required.

BIP4414 Message propagated to unknown terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateReply node has propagated a message to the ’unknown’ terminal.

Response: No user action required

BIP4415 The record of the request that initiated this reply contains unexpected data.

Severity: 20 : Error

Explanation: An AggregateReply node received unexpected information when dealing with the record of the request

that was stored to correlate against this reply.

Response: Contact your IBM support center.

BIP4416 Message propagated to timeout terminal from node <insert_0>

Severity: 0 : Information

Explanation: An AggregateReply node has propagated a message to the ’timeout’ terminal.

Response: No user action required

BIP4417 Message could not be stored persistently. Missing Information : <insert_0>.

Severity: 20 : Error

Explanation: An AggregateReply node attempted to store a message persistently. In order to do so, it needs to

discover information from the message. Part of that information could not be found.

Response: Ensure that the message has a valid Properties folder and a payload (e.g. XML). Ensure the message has

the following information : <insert_0>.

BIP4418 Invalid control message received by AggregateReply node <insert_1>. Missing Information :

<insert_0>

Severity: 20 : Error

Explanation: An AggregateReply node received a control message at its control terminal. The message was not in

248 Diagnostic messages

the format that was expected. The following information was expected but not found: <insert_0>

Response: Ensure that the message received at the control terminal of the AggregateReply node was generated by

the control terminal of an AggregateControl node. If the message needed to be modified for delivery purposes (for

example, adding an MQMD), ensure that the XML payload was not affected by this modification.

BIP4419 Invalid reply message received by AggregateReply node <insert_1>. Missing Information : <insert_0>

Severity: 20 : Error

Explanation: An AggregateReply node received a message at its in terminal. The message was not in the format that

was expected. The following information was expected but not found: <insert_0>

Response: Ensure that the message received at the control terminal of the AggregateReply node has a ’Properties’

folder.

BIP4420 Request message identifier is not unique

Severity: 20 : Error

Explanation: The AggregateRequest node <insert_0> attempted to record the delivery of a request message, but the

message’s unique identifier has already been used.

Response: Ensure that a new unique identifier is generated for the request message you are passing to the

AggregateRequest node. This can be achieved by using the ’Request’ tab when configuring the MQOutput node or

the MQeOutput node. Check that the same message is not being propagated to more than one AggregateRequest

node.

BIP4421 Empty message received by the AggregateReply node.

Severity: 20 : Error

Explanation: An AggregateReply node is unable to process an empty message.

Response: Check the flow that has propagated the message to this node.

BIP4422 Unable to store request message in AggregateReply node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateReply node failed to store a message recording an aggregation request. This message is

used by the node to record the details of the reply it expects back from a particular request. Failed to put a message

to queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4423 Unable to store control message in AggregateReply node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateReply node failed to store a control message. This message is used by the node to

control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to put a

message to queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4424 Unable to retrieve control message in AggregateReply node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateReply node failed to retrieve a control message. This message is used by the node to

control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to get a

message from queue <insert_0> because of WebSphere MQ reason code <insert_1>

BIP4000 to BIP4999 (Built-in nodes) 249

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4425 Unable to retrieve request message in AggregateReply node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateReply node failed to retrieve a request message. This message is used to store state

about a request. Failed to get a message from queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4426 Unable to store request message in AggregateControl node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateControl node failed to store a request message. This message is used by the node to

control a particular aggregation. Failed to put a message to queue <insert_0> because of WebSphere MQ reason code

<insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4427 Unable to store control message in AggregateControl node. Queue=<insert_0>, Reason

Code=<insert_1>.

Severity: 20 : Error

Explanation: The AggregateControl node failed to store a control message. This message is used by the node to

control a particular aggregation. It is used both for normal processing and for timeout processing. Failed to put a

message to queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4428 Missing aggregate request information in Environment. The missing information was in aggregate

folder : <insert_0>.

Severity: 20 : Error

Explanation: An AggregateControl node attempted to process the information about individual aggregate requests.

In order to do so, it needs specific information to be stored by AggregateRequest nodes. Part of that information

could not be found.

Response: Ensure that the message flow is correctly designed for aggregation. In particular, verify that Output

nodes come before AggregateRequest nodes and that the Environment of the message tree is not changed by the flow

after the AggregateControl node.

BIP4429 Failed to find a matching control message for a reply message. Queue=<insert_2>, Reason

Code=<insert_0>, Correlid=<insert_1>.

Severity: 10 : Warning

Explanation: The Aggregation Reply node has matched an incoming reply message to an out going request message

but has failed to find a matching control message. This state should never be reached and is probably caused by

WebSphere MQ problems. The WebSphere MQ return code was <insert_0> when attempting to get a message with

correlid <insert_1> from queue <insert_2>. The reply message has been processed as an unknown message.

Response: Review the current state of the system and try to understand why the control message might be missing.

This could be due to another process or person removing contol messages from <insert_2>.

250 Diagnostic messages

BIP4430 Aggregation control message has a bad format. Queue=<insert_0>, Correlid=<insert_1>.

Severity: 20 : Error

Explanation: The Aggregation Reply node has tried to process a control message but it has a corrupt format. The

control message is on WebSphere MQ queue <insert_0> and it has Correlid <insert_1>.

Response: If the error persists then remove the control message form the WebSphere MQ queue. By removing the

control message all details of the aggregation will be lost.

BIP4431 Failed to store a reply message. Queue=<insert_0>, Reason Code=<insert_1>.

Severity: 20 : Error

Explanation: The Aggregation Reply node has tried to store a reply message but has failed. Failed to put a message

to queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4432 Storing a aggregation reply message persistently for subsequent processing.

Severity: 0 : Information

Explanation: The message has been stored persistently by the AggregateReply node. It will be stored until all replies

for the aggregation have returned. Message details: Reply Id = <insert_0>, Reply Protocol = <insert_1>. Reply Group

Id = <insert_2>.

Response: No user action required.

BIP4433 Failed to retrieve a reply message. Queue=<insert_0>, Reason Code=<insert_1>.

Severity: 20 : Error

Explanation: The Aggregation Reply node has tried to retrieve a reply message but has failed. Failed to get a

message from queue <insert_0> because of WebSphere MQ reason code <insert_1>

Response: Check that the underlying aggregation WebSphere MQ queue is functioning correctly.

BIP4435 The Aggregation Reply node has received a reply message which has a blank reply ID: <insert_0>.

Severity: 20 : Error

Explanation: This is not allowed because the reply ID is needed so that a reply message can be matched to the

original request message. If you are using WebSphere MQ to send and receive aggregation requests, the reply ID

must be stored in the correlation identifier (CorrelId) field of the message descriptor (MQMD) and it must be set to

the value of the message ID in the request message’s MQMD.

Response: Make sure that all reply messages have their reply IDs correctly set to match the ID of the request

message.

BIP4440 XMLT Transformation requested. The XMLT node has invoked the eXMLT engine to perform a

transformation of XML data. The supplied stylesheet name is <insert_1>. The input data is

<insert_0>.

Severity: 0 : Information

Explanation: The XMLT node has invoked the eXMLT engine to perform a transformation of XML data.

Response: No user action required.

BIP4441 XMLT transformation complete. The eXMLT engine has completed the transformation. Output data

is <insert_0>.

Severity: 0 : Information

Explanation: The eXMLT engine has completed the transformation. Output data is <insert_0>.

BIP4000 to BIP4999 (Built-in nodes) 251

Response: No user action required.

BIP4442 XMLT error <insert_1> reported by XMLT node <insert_0>.

Severity: 20 : Error

Explanation: The XMLT node <insert_0> has reported the following error <insert_1>.

Response: Inspect the error text to determine appropriate action

BIP4443 Stylesheet name not found. XMLT node <insert_0> requested a transformation of XML data but the

transformation could not be completed because the stylesheet name could not be determined using

the given selection priorities. Node attribute priority: <insert_1>. LocalEnvironment priority:

<insert_2>. Embedded XML Priority: <insert_3>.

Severity: 20 : Error

Explanation: An XMLT node requested a transformation of XML data but the transformation could not be

completed because the stylesheet name could not be determined using the given selection priorities. Node attribute

priority: <insert_1>. LocalEnvironment priority: <insert_2>. Embedded XML Priority: <insert_3>.

Response: Ensure that the stylesheet name is available.

BIP4444 XMLT warning <insert_1> reported by XMLT node <insert_0>.

Severity: 10 : Warning

Explanation: The XMLT node <insert_0> has reported the following warning <insert_1>.

Response: Inspect the warning message to determine appropriate action.

BIP4445 XMLT information message <insert_1> reported by XMLT Node <insert_0>.

Severity: 0 : Information

Explanation: The XMLT node <insert_0> has reported the following information message <insert_1>.

Response: No user action required.

BIP4446 XMLT node <insert_0> requested a transformation of XML data but the identified stylesheet,

<insert_1>, does not exist.

Severity: 20 : Error

Explanation: The transformation could not be completed because the stylesheet could not be found.

Response: Ensure that the identified style sheet is available.

BIP4447 XMLT node <insert_0> encountered a problem during the transformation. The error message is

<insert_1>.

Severity: 20 : Error

Explanation: The transformation could not be completed.

Response: Check the error message to identify the cause and correct the error.

BIP4448 Found Output CharSet specification <insert_0> from Local Environment (priority <insert_1>).

Severity: 0 : Information

Explanation: The XMLT node tried to read Output CharSet specification from Local Environment and got

<insert_0>. The specified priority for selecting Local Environment Output CharSet is <insert_1>.

Response: No user action required.

252 Diagnostic messages

BIP4449 Found Output CharSet specification <insert_0> from Node Attribute (priority <insert_1>).

Severity: 0 : Information

Explanation: The XMLT node tried to read Output CharSet specification from Node Attribute and got <insert_0>.

The specified priority for selecting Node Attribute Output CharSet is <insert_1>.

Response: No user action required.

BIP4450 No Output CharSet specification was found. Using default Output CharSet <insert_0>.

Severity: 0 : Information

Explanation: The XMLT node could not find any Output CharSet specification. The default Output CharSet

<insert_0> is therefore to be used.

Response: No user action required.

BIP4451 Found Stylesheet Name specification <insert_0> from Local Environment (priority <insert_1>).

Severity: 0 : Information

Explanation: The XMLT node tried to read Stylesheet Name specification from Local Environment and got

<insert_0>. The specified priority for selecting Local Environment Stylesheet Name is <insert_1>.

Response: No user action required.

BIP4452 Found Stylesheet Name specification <insert_0> from Node Attribute (priority <insert_1>).

Severity: 0 : Information

Explanation: The XMLT node tried to read Stylesheet Name specification from Node Attribute and got <insert_0>.

The specified priority for selecting Node Attribute Stylesheet Name is <insert_1>.

Response: No user action required.

BIP4460 Message propagated to out terminal from node <insert_0>.

Severity: 0 : Information

Explanation: A pass through node has received a message and is propagating it to any nodes connected to its out

terminal.

Response: No user action required.

BIP4500 Failed to deploy Java code resource <insert_0>. The Java stack trace is: <insert_1>

Severity: 20 : Error

Explanation: The Java JAR file deployment to the broker failed.

Response: This is an internal error. Contact your IBM support center.

BIP4501 Failed to delete Java code resource <insert_0>.

Severity: 20 : Error

Explanation: The Java JAR file failed to be deleted. This file may be locked by the operating system.

Response: Ensure there is sufficient disk space available on the machine running the broker runtime. Stop the

broker and delete this file manually.

BIP4000 to BIP4999 (Built-in nodes) 253

BIP4502 An unexpected error occurred during the deployment of a Java resource.

Severity: 20 : Error

Explanation: An error occurred during the deployment of a Java resource. This may have left the broker in an

inconsistent state.

Response: Ensure there is sufficient disk space available on the machine running the broker runtime. Stop the

broker, delete all files in <insert_0>, restart the broker and perform a full redeploy.

BIP4503 Failed to deploy Java code resource <insert_0>. An IOException was thrown during deployment. The

Java stack trace is: <insert_1>

Severity: 20 : Error

Explanation: The Java JAR file deployment to the broker failed.

Response: Ensure there is sufficient disk space available on the machine running the broker runtime.

BIP4504 Failed to deploy Java code resource <insert_0>. A ClassNotFoundException was thrown during

deployment. The Java stack trace is: <insert_1>

Severity: 20 : Error

Explanation: The Java JAR file deployment to the broker failed.

Response: Ensure all dependencies of the Java code have been deployed to the runtime.

BIP4505 Failed to deploy Java code resource <insert_0>. The Java class deployed to the Java Compute Node

must be public and extend MbJavaComputeNode. The Java stack trace is: <insert_1>

Severity: 20 : Error

Explanation: The Java JAR file deployment to the broker failed.

Response: The Java Compute Node class implementation must be public and extend MbJavaComputeNode

BIP4506 The attempted deletion of Java resource <insert_0> caused a ClassNotFoundException. Since this

resource is still required by the broker it has been restored.

Severity: 20 : Error

Explanation: The attempted deletion of the Java resource <insert_0> caused a ClassNotFoundException. The broker

still requires the Java resource so it has not be deleted.

Response: No user action required.

BIP4507 A cleared message was propagated.

Severity: 20 : Error

Explanation: A node tried to propagate a message that has already been cleared using clearMessage(). Clearing a

message releases all resources associated with it, so it can no longer be used.

Response: Modify node code to ensure that no cleared messages are propagated.

BIP4508 Unable to serialize Java exception <insert_0>.

Severity: 20 : Error

Explanation: The following exception <insert_1> was thrown when serializing a Java exception. The Java stack trace

is: <insert_2> As the serialization failed this exception will not be available in up stream nodes.

Response: If the exception being serialized is a user class, ensure that it is serializable.

254 Diagnostic messages

BIP4509 Unable to deserialize a Java exception.

Severity: 20 : Error

Explanation: The following exception <insert_0> was thrown when deserialize a Java exception. The Java stack trace

is: <insert_1> As the deserialization failed this exception will not be available.

Response: Ensure that the node catching the exception has access to the exception class.

BIP4510 Java compute class <insert_0> not found.

Severity: 20 : Error

Explanation: The class <insert_0> associated with Java compute node <insert_1> could not be found by the broker.

Response: Ensure that the class <insert_0> has been deployed and is available to the broker.

BIP4511 <insert_0> was thrown while loading Java compute class <insert_1>.

Severity: 20 : Error

Explanation: A NoClassDefFoundError was thrown while loading Java compute node class <insert_1>. This means

that a class used by <insert_1> could not be found.

Response: Ensure that all the dependencies of <insert_1> have been deployed to the broker.

BIP4512 <insert_1> was thrown while loading Java user-defined node class <insert_0>.

Severity: 30 : Severe error

Explanation: The stack trace of the exception is <insert_2>.

Response: Use the exception information to resolve the problem and restart the broker.

BIP4601 The Timeout Control Node <insert_1> failed to navigate to the message location specified. The

location specified was: <insert_0>.

Severity: 20 : Error

Explanation: Ensure that the Location <insert_0> is valid for the message tree where it is used.

Response: Correct the specified message location.

BIP4602 The Timeout Control Node <insert_1> received a timeout request that did not contain a valid

timeout action value.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout

action. The request message was correctly navigated to the specified timeout request location, and this location

contained an Action element, but the element did not have a valid value. The value contained was <insert_0>.

Response: Supply an Action element, with one of the valid values of SET or CANCEL.

BIP4603 The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout

action.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout action.

The request message was correctly navigated to the specified timeout request location, but this location did not

contain an Action element.

Response: Supply an Action element, with one of the valid values of SET or CANCEL.

BIP4000 to BIP4999 (Built-in nodes) 255

BIP4604 The Timeout Control Node <insert_0> received a timeout request that contained an empty timeout

identifier.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_0> received a timeout request that contained an empty timeout

identifier. The request message was correctly navigated to the specified timeout request location, and this location

contained an Identifer element, but the element was empty.

Response: Supply a non-empty Identifier element.

BIP4605 The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout

identifier.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_0> received a timeout request that did not contain a timeout

identifier. The request message was correctly navigated to the specified timeout request location, but this location did

not contain an Identifier element.

Response: Supply a non-empty Identifier element.

BIP4606 The Timeout Control Node <insert_1> received a timeout request that did not contain a valid

timeout start date value.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout

start date. The request message was correctly navigated to the specified timeout request location, and this location

contained a StartDate element, but the element did not have a valid value. The value contained was <insert_0>.

Response: Ensure the supplied timeout StartDate is not in the past. TODAY is a valid value.

BIP4607 The Timeout Control Node <insert_1> received a timeout request that did not contain a valid

timeout start time value.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout

start time. The request message was correctly navigated to the specified timeout request location, and this location

contained a StartTime element, but the element did not have a valid value. The value contained was <insert_0>.

Response: Ensure the supplied timeout StartTime is not in the past. NOW is a valid value.

BIP4608 The Timeout Control Node <insert_1> received a timeout request that did not contain a valid

timeout count value.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout

count. The request message was correctly navigated to the specified timeout request location, and this location

contained a Count element, but the element did not have a valid value. The value contained was <insert_0>.

Response: Ensure the supplied timeout Count is either -1 (for unlimited) or greater than zero.

BIP4609 The Timeout Control Node <insert_1> received a timeout request that did not contain a valid

timeout interval value.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that did not contain a valid timeout

interval. The request message was correctly navigated to the specified timeout request location, and this location

contained an Interval Count element, but the element did not have a valid value. The value contained was

<insert_0>.

Response: Ensure the supplied timeout Interval is not less than zero.

256 Diagnostic messages

BIP4610 The Timeout Control Node <insert_1> received a timeout request that contained an identifier which

clashes with an existing timeout request for this node.

Severity: 20 : Error

Explanation: The Timeout Control Node <insert_1> received a timeout request that contained an identifier which is

already in use for a previous timeout request to this node. The supplied identifier is <insert_0>.

Response: Supply a unique timeout Identifier element. Note also that this error can be avoided by setting

AllowOverwrite in future timeout requests to TRUE.

BIP4611 The Timeout Control Node <insert_2> failed to cancel an existing timeout request.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4612 The Timeout Control Node <insert_2> failed to store an incoming timeout request.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4613 The Timeout Control Node <insert_1> received a CANCEL request for an unmatched Identifier.

Severity: 20 : Error

Explanation: The supplied timeout CANCEL request contained an Identifier which was unmatched for this node.

The Identifier was <insert_0>.

Response: This error occurs when the CANCEL cannot be matched to an existing timeout for this node. The

Identifier in the CANCEL request may be incorrect, or the referenced timeout may have expired.

BIP4614 The Timeout Control Node <insert_2> failed to access its internal store.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4615 The Timeout Notification Node <insert_2> failed to delete a non-persistent timeout request.

Severity: 10 : Warning

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4616 The Timeout Notification Node <insert_2> failed to delete an overridden timeout request.

Severity: 10 : Warning

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4617 The Timeout Notification Node <insert_2> failed to access its internal store.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4000 to BIP4999 (Built-in nodes) 257

BIP4618 The Timeout Notification Node <insert_2> failed to get a message from its internal store.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4619 The Timeout Notification Node <insert_0> received a bad timeout request.

Severity: 20 : Error

Explanation: The node received a corrupt timeout request message.

Response: This error can occur if the message stored by the corresponding Timeout Control node cannot be

un-serialised. It can also occur if non-timeout control node messages have been put on the message store. Correct the

incoming data.

BIP4620 The Timeout Notification Node <insert_2> failed to update a message in its internal store.

Severity: 20 : Error

Explanation: The MQ return codes for the operation were completion code: <insert_0>, reason code: <insert_1>.

Response: correct the reason for the MQ failure.

BIP4621 Exception condition detected on input node: <insert_0>.

Severity: 20 : Error

Explanation: Node <insert_0> has detected a failure during message processing. The failure terminal is not attached,

so the message flow has been rolled back.

Response: Examine further messages to determine why the message is not being received as expected. Correct this

situation if possible. Perform any local error recovery processing required.

BIP4622 Exception condition detected on input node <insert_0>.

Severity: 20 : Error

Explanation: The input node <insert_0> detected an error whilst processing a message. Following messages will

indicate the cause of this exception.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP4623 Exception condition detected: object label <insert_0>; input node <insert_1>.

Severity: 20 : Error

Explanation: An input node detected an error whilst processing a message. The message flow has been rolled back.

Following messages will indicate the cause of this exception which was generated in the STL container classes.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP4624 Exception condition detected on input node: <insert_0>.

Severity: 0 : Information

Explanation: Node <insert_0> has detected a failure during message processing. The message broker is propagating

the message to the failure terminal.

Response: Examine further messages to determine why the message is not being received as expected. Correct this

situation if possible. Perform any local error recovery processing required.

258 Diagnostic messages

BIP4625 Message propagated to out terminal from node <insert_0>

Severity: 0 : Information

Explanation: A TimeoutControl node has received a message and is propagating it to any nodes connected to its out

terminal

Response: No user action required

BIP4626 Message propagated to out terminal from node <insert_0>

Severity: 0 : Information

Explanation: A TimeoutNotification node is propagating a message to any nodes connected to its out terminal

Response: No user action required

BIP4627 Timeout request set by node <insert_1>

Severity: 0 : Information

Explanation: A TimeoutControl node has set a timeout with identifier <insert_0>

Response: No user action required

BIP4628 Timeout request cancelled by node <insert_1>

Severity: 0 : Information

Explanation: A TimeoutControl node has cancelled a timeout with identifier <insert_0>

Response: No user action required

BIP4629 Timeout request being processed by node <insert_1>

Severity: 0 : Information

Explanation: A TimeoutNotification node is processing a timeout with identifier <insert_0>

Response: No user action required

BIP4630 An MQGET operation was unsuccessful. Completion Code <insert_0>; Reason Code <insert_1>.

Severity: 20 : Error

Explanation: An error occurred during a WebSphere MQ MQGET call.

Response: Examine the error codes to determine the cause of the failure.

BIP4631 The MQ Get node <insert_2> failed to navigate to the <insert_1> specified. The location specified

was: <insert_0>.

Severity: 20 : Error

Explanation: Ensure that the Location <insert_0> is valid for the message tree where it is used.

Response: Check the following exception output, if any, for more details about the problem and correct the specified

message location.

BIP4632 MQ Get node <insert_1> was unable to obtain MsgId/CorrelId for message matching from input

MQMD location: <insert_0>.

Severity: 20 : Error

Explanation: When ’Get by Message ID’/’Get by Correlation ID’ node properties are selected, a valid MQMD must

be provided in the input message to MQ Get node at the location specified by the ’Input MQMD Location’ node

attribute.

BIP4000 to BIP4999 (Built-in nodes) 259

Response: Examine the ’Get by Message ID’/’Get by Correlation ID’ and ’Input MQMD Location’ node attributes to

ensure that they are correctly specified and the input message to the node has the right structure. Check the

following exception output, if any, for more details about the problem.

BIP4633 An error occured whilst performing an MQGet node operation.

Severity: 20 : Error

Explanation: N/A.

Response: See the following messages for information pertaining to this error.

BIP4634 The MQ Get node <insert_2> received an configuration message containing an invalid attribute

value <insert_1> specified. The location specified was: <insert_0>.

Severity: 20 : Error

Explanation: Ensure that the Location <insert_0> is valid for the message tree where it is used.

Response: Check the following exception output, if any, for more details about the problem and correct the specified

message location.

BIP4635 The MQ Get node <insert_2> failed to navigate to the default location <insert_0> for <insert_1>.

Severity: 0 : Information

Explanation: Location <insert_0> is the default value for <insert_1> and it was not found. It is assumed that this

<insert_1> node property is not needed in this case and, therefore, the issue is ignored.

Response: Ignore this message (and the previous user trace message regarding this navigation, if there is one) if this

<insert_1> node property is not needed; Otherwise, make sure the location is available or correct the location

specification.

BIP4640 WBIMB JMSClient. <insert_0> There is a configuration problem with the JNDI Administered objects

where: Initial Context Factory = <insert_1>. Location of the bindings = <insert_2>. ConnectionFactory

Name = <insert_3>. JMS destination = <insert_4>. The exception text is : <insert_5>.

Severity: 20 : Error

Explanation: The node could not obtain a JNDI Administered Object because some of the values specified in the

node attributes are incorrect

Response: Check the JNDI Administered configuration for the JMS provider used by the node. Either modify the

JNDI Administered objects and rebuild the bindings, or change the node attributes and re-deploy the message flow.

BIP4641 WBIMB JMSClient.<insert_0> Invalid URL <insert_0> specified for Initial Context Factory <insert_1>.

Severity: 20 : Error

Explanation: The Initial Context Factory for the JMS provider could not be found by JNDI at the URL specified.

Response: Check the JNDI Administered objects are located at the URL path specified. If the administered objects

are stored using LDAP verify that the correct security credentials (userid and password) have been provided using

the mqsichangeproperties command. credentials have been

BIP4642 WBIMB JMSClient.<insert_0> There was JMS Exception while creating <insert_1> Destination. If

available the JMS provider return code is <insert_3>.

Severity: 20 : Error

Explanation: The Destination supplied in the node attributes ( or JMSReplyTo for a reply message ) could not be

created.

Response: Verify that the string supplied for the JMS destination is valid for the JMS Provider, and check that the

destination exists.

260 Diagnostic messages

BIP4643 WBIMB JMSClient.<insert_0>. Error Receiving JMS Message. If Available the text from the JMS

Exception is <insert_1>.

Severity: 20 : Error

Explanation: The node could not receive a JMS Message because of a JMS Exception on the JMS consumer and

session.

Response: Investigate the cause of the JMS exception.

BIP4644 WBIMB JMSClient.<insert_0> Unable to create a JMS Message for output. If available the text from

the JMS Exception is <insert_1>.

Severity: 0 : Information

Explanation: The node was unable to create a JMS Message because of a JMS Exception.

Response: Investigate the cause of the JMS Exception.

BIP4645 WBIMB JMSClient.<insert_0> The was JMS Exception while creating a JMS Session

Severity: 0 : Information

Explanation: The node was unable to establish a JMS Session on the JMS Connection.

Response: Verify that the JMS provider is available, and that sufficient resources have been allocated. destination

exists.

BIP4646 WBIMB JMSClient. <insert_0> The format of a JMS Message received by the node is invalid and

could not be processed.

Severity: 0 : Information

Explanation: The JMS message received by the node is unreadable. The message will be delivered to the failure

terminal of the node or rolled back if a fail path is not configured.

Response: Investigate the JMS Message for syntax errors. The message may be found at the destination configured

in the failure path of the deployed flow, or the backout destination if sepecified in the node, or it may have been

rolled back to the provider.

BIP4647 WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to create a JMS message

consumer. If available the JMS Exception text is : <insert_1>

Severity: 20 : Error

Explanation: The node was unable to create a JMS message consumer on the JMS session. The JMS provider

returned an exception.

Response: Investigate the cause of the JMS Exception. If the problem persist then contact the vendor of the JMS

provider.

BIP4648 WBIMB JMSClient.<insert_0> The Connection with the JMS provider was unable to start, or has

closed for Initial Conext factory <insert_1> . The node will attempt to re-establish the connection.

Severity: 20 : Error

Explanation: The JMS Connection with the JMS provide from this node has stopped. This could be due to the

message flow stopping or the connection could have ended abnormally because of a problem with the JMS provider.

Response: If the message flow is not shutting down then the node will attempt to re-connect to the JMS provider.

Check that the provider is available.

BIP4000 to BIP4999 (Built-in nodes) 261

BIP4649 WBIMB JMSClient.<insert_0> A Connection with the JMS provider has started for Initial Context

Factory <insert_1>.

Severity: 0 : Information

Explanation: The JMS Connection with the JMS provider has started for this node.

Response: No user action required.

BIP4650 WBIMB JMSClient.<insert_0> Invalid setting for node attribute ″Transaction Coordinated″ with a

non XA-Compliant JMS provider. Initial Context Factory: <insert_1> URL: <insert_2>.

Severity: 20 : Error

Explanation: The JMS Provider is not enabled for XA-Compliant transaction coordination .

Response: Modify the node attribute and re-deploy.

BIP4651 WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to send a JMS message

. If avaiable the JMS Exception text is : <insert_1>

Severity: 20 : Error

Explanation: The node was unable to send a JMS message on the JMS session. The JMS provider returned an

exception.

Response: Investigate the cause of the JMS Exception. If the problem persist then contact the vendor of the JMS

provider.

BIP4652 WBIMB JMSClient. <insert_0> There was a JMS Exception while attempting to acknowledge a JMS

message . If avaiable the JMS Exception text is : <insert_1>

Severity: 20 : Error

Explanation: The node was unable to acknowledge a JMS message on the JMS session. The JMS provider returned

an exception.

Response: Investigate the cause of the JMS Exception. If the problem persists then contact the vendor of the JMS

provider.

BIP4653 WBIMB JMSClient. <insert_0> There was an error while attempting to dispatch another instance of

the message flow.

Severity: 0 : Information

Explanation: The node was unable to dispatch another processing thread for an additional instance of the message

flow.

Response: Check the number of instances cnfigured for this message flow. If the problem persists then contact IBM.

BIP4654 WBIMB JMSClient. <insert_0> An error was returned downstream from the Input node. If available

the text of the exception is <insert_1>.

Severity: 0 : Information

Explanation: The message flow experienced processing errors downstream of the input node, which may have

returned an exception.

Response: Investigate the cause of the processing exception.If the problem persists then contact IBM.

BIP4655 WBIMB JMSClient.<insert_0> There was a problem extacting JMS header data from a JMS input

message.

Severity: 20 : Error

262 Diagnostic messages

Explanation: The node was unable to obtain header data from the received JMS Message because it was corrupted

or badly formed.

Response: Investigate the cause of the badly formed JMS Message.

BIP4656 WBIMB JMSClient.<insert_0> There was a problem extacting JMS properties data from a JMS input

message.

Severity: 20 : Error

Explanation: The node was unable to obtain property data from the received JMS Message because it was corrupted

or badly formed.

Response: Investigate the cause of the badly formed JMS Message.

BIP4657 WBIMB JMSClient. <insert_0> There was a problem extacting the data payload from a JMS input

message.

Severity: 20 : Error

Explanation: The node was unable to obtain the payload data from the JMS message received. This was because it

was either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.

Response: Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4658 WBIMB JMSClient.<insert_0> There was a problem putting JMS header related data to the

MbMessage.

Severity: 20 : Error

Explanation: The node was unable to write JMS message header data to the MbMessage. This was because it was

either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.

Response: Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4659 WBIMB JMSClient. <insert_0> There was a problem putting JMS payload data to the MbMessage.

Severity: 20 : Error

Explanation: The node was unable to write JMS message payload data to the MbMessage. This was because it was

either in an unexpected WBIMB message domain for the JMS message type, or it was badly formed.

Response: Modify the input node attribute for the message domain, and investigate the format of the data payload.

BIP4660 WBIMB JMSClient.<insert_0> There was a problem extracting JMS header related data from the

MbMessage.

Severity: 20 : Error

Explanation: The node was unable to extract JMS header related data from the MbMessage because it was badly

formed.

Response: If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4661 WBIMB JMSClient.<insert_0> There was a problem extracting the body data from the MbMessage.

Severity: 20 : Error

Explanation: The node was unable to extract data from the MbMessage because it was badly formed.

Response: If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4000 to BIP4999 (Built-in nodes) 263

BIP4662 WBIMB JMSClient. <insert_0> There was a problem setting JMS related header data to the JMS

output message.

Severity: 20 : Error

Explanation: The node was unable to set header related data to the JMS output message because it was either badly

formed or in an unexpected type.

Response: If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4663 WBIMB JMSClient.<insert_0> There was a problem setting JMS property data to the JMS output

message.

Severity: 20 : Error

Explanation: The node was unable to set JMS property data to the JMS output message because it was either badly

formed or in an unexpected type.

Response: If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4664 WBIMB JMSClient.<insert_0> There was a problem adding payload data to the JMS output message.

Severity: 20 : Error

Explanation: The node was unable to set payload data to the JMS output message because it was either badly

formed or in an unexpected type.

Response: If possible, turn on service trace and investigate the cause of the badly formed data.

BIP4665 WBIMB JMSClient.<insert_0>.There was a problem updating MRM related properties values in the

MbMessage.

Severity: 20 : Error

Explanation: The node was unable to set values for message Set, type or format in the MbMessage. an unexpected

type.

Response: If possible, turn on service trace and investigate the format of the data in the JMSType field in the hedaer

data of the JMS message.

BIP4666 WBIMB JMSClient.<insert_0> The JMS message recieved by the node was of an unxpected type

<insert_1> for message domain <insert_2>.

Severity: 20 : Error

Explanation: The node was unable to process the JMS Message because it was an unexpected type for the message

domain specified in the node attributes.

Response: Investigate

BIP4667 WBIMB JMSClient.<insert_0> There was an exception during shutdown of the message flow. If

available the text from the exception is <insert_1>.

Severity: 20 : Error

Explanation: An unxpected error occurred during shutdown of the message flow.

Response: Investigate the cause of the error. If the problem persists then contact IBM.

BIP4668 WBIMB JMSClient.<insert_0> There was an error while attempting to create a JMS message

producer.If available the text of the exception is <insert_1>.

Severity: 20 : Error

Explanation: The node was unable to create a JMS Message producer because of a JMS exception with the JMS

provider.

264 Diagnostic messages

Response: Investigate the cause of the JMS exception. If the error persists then contact the vendor of the JMS

provider.

BIP4669 WBIMB JMSClient.<insert_0> A JMS message was redelivered to the node and a backout destination

has not been configured .

Severity: 20 : Error

Explanation: The node was unable to process a JMS Message because of errors and could not send it to a backout

destination because none was configured.

Response: Investigate the cause of the message failure. Also consider setting a backout destination and threshold for

the node

BIP4670 WBIMB The node was unable to read the MQMD from the message.

Severity: 20 : Error

Explanation: The node was unable to transform an MQ Message because the MQMD header could not be found or

there are errors with the message structure

Response: Check that a correctly formed MQMD header is present in the message.

BIP4671 WBIMB The node was unable to find the body of the message.

Severity: 20 : Error

Explanation: The node was unable to transform a message because the body could not be found or there are errors

with the message structure

Response: Check that the message body is present in the message, and correctly formed.

BIP4672 WBIMB The node was unable to find a mandatory section of a JMS message.

Severity: 20 : Error

Explanation: The node was unable to transform a JMS message because the <insert_0> section could not be found or

there are errors with the message structure

Response: Check that the JMS message section has been correctly formed and is present in the message.

BIP4673 WBIMB JMSClient.<insert_0> Error finding local transaction in table for the Provider with Initial

Context Factory <insert_1>.

Severity: 20 : Error

Explanation: The underlying JMS Connection with the JMS provider has probably failed.

Response: Check the connectivity and availability of the JMS provider.

BIP4674 WBIMB JMSClient.<insert_0> Error committing a transaction for the Provider with Initial Context

Factory <insert_1>. The Requesting ID was <insert_2>.

Severity: 20 : Error

Explanation: The underlying JMS Connection with the JMS provider has probably failed.

Response: Check the connectivity and availability of the JMS provider.

BIP4675 WBIMB JMSClient.<insert_0> Error rolling back transaction for the Provider with Initial Context

Factory <insert_1>. The Requesting ID was <insert_2>.

Severity: 20 : Error

Explanation: The underlying JMS Connection with the JMS provider has probably failed.

Response: Check the connectivity and availability of the JMS provider.

BIP4000 to BIP4999 (Built-in nodes) 265

BIP4676 WBIMB JMSClient.<insert_0> Error closing JMS Sesssion for the Provider with Initial Context

Factory <insert_1>. The Requesting ID was <insert_2>.

Severity: 20 : Error

Explanation: The underlying JMS Connection with the JMS provider has probably failed.

Response: Check the connectivity and availability of the JMS provider.

BIP4677 WBIMB JMSClient. <insert_0> The type of JMS Message received by the node is invalid for the

message domain <insert_1>.

Severity: 20 : Error

Explanation: The JMS Message received by the node is not a valid type for the message domain. The message will

be delivered to the failure terminal of the node or rolled back if a fail path is not configured.

Response: Either reconfigure the JMSInput node to change the expected message domain , or modify the value of

the JMSType header in the JMS Message. The message may be found at the destination configured in the failure the

provider.

BIP4680 Unsupported message domain <insert_0> encountered in mapping node <insert_1>.

Severity: 20 : Error

Explanation: This error indicates that ESQL code generated for a mapping node has encountered a message domain

that it does not support.

Response: Ensure that the Body subtree of the logical message tree is owned by a message domain that is

supported by the Mapping node. The supported domains are ... MRM XML XMLNS XMLNSC JMSMap JMSStream

266 Diagnostic messages

BIP5000 to BIP5999 (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.

268 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 269

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

270 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 271

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.

272 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 273

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.

274 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 275

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.

276 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 277

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.

278 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 279

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.

280 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 281

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.

282 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 283

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.

284 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 285

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

286 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 287

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.

288 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 289

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.

290 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 291

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.

292 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 293

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.

294 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 295

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>\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.

296 Diagnostic messages

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

BIP5000 to BIP5999 (Parsers) 297

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>\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>\bin directory. Other platforms use the <MQSI dir>/lib directory. Check for other error

messages that may indicate which file is causing the problem.

298 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 299

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>\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

300 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 301

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.

302 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 303

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.

304 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 305

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.

306 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 307

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.

308 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 309

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.

310 Diagnostic messages

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>

BIP5000 to BIP5999 (Parsers) 311

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

312 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 313

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.

314 Diagnostic messages

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

BIP5000 to BIP5999 (Parsers) 315

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.

316 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 317

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.

318 Diagnostic messages

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>.

BIP5000 to BIP5999 (Parsers) 319

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 Ta g <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 Ta g 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.

320 Diagnostic messages

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>.

BIP5000 to BIP5999 (Parsers) 321

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.

322 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 323

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.

324 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 325

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>.

326 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 327

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.

328 Diagnostic messages

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>

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>

Check that the message model is correct. Review previous messages for details of the message set, message type and

element.

BIP5000 to BIP5999 (Parsers) 329

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>

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’.

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’.

330 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 331

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

332 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 333

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.

334 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 335

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.

336 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 337

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.

338 Diagnostic messages

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 \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.

BIP5000 to BIP5999 (Parsers) 339

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.

340 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 341

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>.

342 Diagnostic messages

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.

BIP5000 to BIP5999 (Parsers) 343

344 Diagnostic messages

BIP6000 to BIP6999 (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.

346 Diagnostic messages

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.

BIP6000 to BIP6999 (WebSphere MQ and New Era parsers) 347

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.

348 Diagnostic messages

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.

BIP6000 to BIP6999 (WebSphere MQ and New Era parsers) 349

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.

350 Diagnostic messages

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.

BIP6000 to BIP6999 (WebSphere MQ and New Era parsers) 351

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.

352 Diagnostic messages

BIP7000 to BIP7999 (Publish Subscribe)

BIP7001 ACL already exists for topic <insert_0> and principal <insert_1>.

Severity: 20 : Error

Explanation: The broker received a request to create an ACL which already exists.

Response: You must use change or delete to act on the existing ACL or respecify the topic or the principal to create

a new ACL entry. If you don’t expect this ACL to exist, check that the ACL has not already been created by another

user, and that you have deployed any changes you wish to make.

BIP7002 ACL update error on topic <insert_0> and principal <insert_1>.

Severity: 20 : Error

Explanation: An internal error caused the update on the ACL for topic <insert_0> and principal <insert_1> to fail.

Response: Verify the topic and principal are correct and retry the operation. If the operation continues to fail,

contact your IBM support center.

BIP7003 Syntax error in topic, reason code <insert_0>.

Severity: 20 : Error

Explanation: There is a syntax error in the filter expression. Possible reason codes are: (1245) Internal Error. (1246) A

topic wildcard character was used incorrectly. (1247) A topic segment separator appears in an incorrect position.

Response: Refer to the online help for more information on allowable topics, correct the syntax error and repeat the

operation. If an internal error has been reported you should contact your IBM support center.

BIP7005 ACL not found for topic <insert_0> and principal <insert_1>.

Severity: 20 : Error

Explanation: The ACL operation failed because there is no ACL for topic <insert_0> and principal <insert_1>.

Response: Create the ACL before the operation, or verify the topic and principal are correct and retry the operation.

If you expect this ACL to exist, check that the ACL has not been removed by another user, and that you have

deployed any changes you wish to make.

BIP7006 No such principal <insert_0>.

Severity: 20 : Error

Explanation: The operation failed because principal <insert_0> does not exist.

Response: Verify the principal is correct and retry the operation. If you expect this principal to exist, check that it

has not been changed by another user, and that you have deployed any changes you wish to make.

BIP7007 Syntax error in filter, reason code <insert_0>.

Severity: 20 : Error

Explanation: The topic contains a syntax error. Possible reason codes are: (1233) An exception occurred in the

matching engine. (1249) An exception occurred while parsing a subscription selector.

Response: Refer to the online help for more information on allowable SQL expressions, correct the syntax error and

repeat the operation.

BIP7008 Security not enabled.

Severity: 30 : Severe error

Explanation: The operation failed because security was not enabled.

Response: This is an internal error and you should contact your IBM Support center.

BIP7009 Security policy violation - <insert_0> <insert_1> <insert_2>.

Severity: 20 : Error

Explanation: There was a violation of security policy or authorization was denied.

Response: Ensure that the user has the required authority to complete the operation and retry.

BIP7011 Duplicate broker (Queue Manager <insert_0>).

Severity: 30 : Severe error

Explanation: The attempt to add a neighboring broker was unnecessary because the neighbor with Queue Manager

<insert_0> is already known. This could indicate that the Configuration Manager is in an invalid state.

Response: This is an internal error and you should contact your IBM support center.

BIP7012 Duplicate connection to broker (Queue Manager <insert_0>) with id <insert_1>.

Severity: 30 : Severe error

Explanation: A connection with id <insert_1> to broker (Queue Manager <insert_0>) was not created because it

already exists. This could indicate that the Configuration Manager is in an invalid state.

Response: This is an internal error and you should contact your IBM support center.

BIP7013 Unknown broker (Queue Manager <insert_0>).

Severity: 30 : Severe error

Explanation: The operation failed because the broker (Queue Manager <insert_0>) is unknown.

Response: This is an internal error and you should contact your IBM support center.

BIP7014 Unknown connection with id <insert_1> to broker (Queue Manager <insert_0>).

Severity: 30 : Severe error

Explanation: The operation failed because the connection with id <insert_1> to broker (Queue Manager <insert_0>)

is unknown.

Response: This is an internal error and you should contact your IBM support center.

BIP7015 Permission conflict <insert_0>.

Severity: 20 : Error

Explanation: The operation failed because of an attempt to set incompatible permissions <insert_0>.

Response: Ensure that the permissions specified are not mutually exclusive, and retry the operation. Refer to the

online help for more information on valid combinations of permissions.

BIP7016 Native security system error <insert_0>.

Severity: 20 : Error

Explanation: A call has been made to the operating system and there has been a error code returned.

Response: Look up the error code in your operating system documentation, and correct the problem. If the problem

persists, contact your IBM support center.

354 Diagnostic messages

BIP7017 Unknown user <insert_0>.

Severity: 10 : Warning

Explanation: The user <insert_0> was not found in the security information.

Response: This may be an unauthorized user. However, if you expect the user to be able to access the broker, then

this is an internal error, and you should contact your IBM support center.

BIP7018 Client (id <insert_0>) not registered.

Severity: 20 : Error

Explanation: An attempt was made to deregister a subscription registered by the client with id <insert_0>, but this

subscription was not found, or some other error prevented the subscription being deregistered.

Response: Other messages in the log may give more details why the subscription was not deregistered. If the

subscribing application involves a temporary dynamic queue, try stopping this application. If publications are no

longer being sent to the subscriber queue, this message may be ignored, otherwise this is an internal error and

should be reported to your IBM support center.

BIP7019 Problem accessing the broker database for publish/subscribe function.

Severity: 20 : Error

Explanation: A problem was encountered when accessing the broker database while processing a publish/subscribe

function. The available information is given above in other messages.

Response: Check that the database is started and accessible, by using your database management tools. You may

find some useful information in the problem determination section of the product documentation. Investigate any

error codes given in the message above in your database documentation.

BIP7020 Start up failure <insert_0>.

Severity: 30 : Severe error

Explanation: Initialization of the Publication node failed.

Response: Check the system log for possible errors and restart the broker.

BIP7021 Internal Error in the PubSub Matching Engine <insert_0>.

Severity: 20 : Error

Explanation: An internal error has occurred in the Matching Engine, recoverable work will be rolled back and then

processing will continue.

Response: This is an internal error and you should contact your IBM support center.

BIP7022 Problem removing expired subscription.

Severity: 30 : Severe error

Explanation: An exception has occurred whilst removing an expired subscription. Previous messages will indicate

the exact nature of this exception and its severity. The Publish/Subscribe Service has been rolled back.

Response: Check the error messages which precede this error to determine why the failure occurred, and take

action as described by those messages.

BIP7023 Subscription to topic <insert_1> was not found for client <insert_0>.

Severity: 30 : Severe error

Explanation: During processing of a RegisterSubscriber or a RequestUpdate request the subscription which client

<insert_0> had for topic <insert_1> could not be found. The broker will be terminated.

Response: This is an internal error. Contact your IBM support center.

BIP7000 to BIP7999 (Publish Subscribe) 355

BIP7024 Cannot create or modify ACLs without access to information on users and groups.

Severity: 20 : Error

Explanation: The operation failed because the user/group cache for the broker is empty. The broker maintains a

persistent cache of user and group information which it initially receives from the User Name Server. The cache will

be empty if the broker has never successfully registered with the User Name Server, or if the registration is not

complete at the time the ACL creation or modification request is processed.

Response: Check that the User Name Server has been started, and that the broker has successfully registered with

the User Name Server. If the registration occurs after this failure, then retry the operation. Check preceding system

log entries for related errors. Contact your IBM support center if the problem persists.

BIP7025 User does not have permission to subscribe to a topic: <insert_0>.

Severity: 10 : Warning

Explanation: Authorization to subscribe or request an update on a topic has been denied.

Response: Ensure that the user has the required authority to complete the operation and retry.

BIP7026 User does not have publish permission on a topic: <insert_0>.

Severity: 10 : Warning

Explanation: Authorization to publish or delete a publication on a topic has been denied.

Response: Ensure that the user has the required authority to complete the operation and retry.

BIP7027 User cannot receive a message because they do not have subscribe permission on a topic: <insert_0>.

Severity: 0 : Information

Explanation: Authorization to deliver a publication on a topic to a subscriber has been denied.

Response: If you require that the user should receive such publications revise the appropriate group or user ACLs

and retry.

BIP7028 A Type Exception occurred in the PubSub Matching Engine when processing a publication against a

filter: <insert_0>.

Severity: 10 : Warning

Explanation: The PubSub Matching Engine encountered a mismatch in data types when driving a publication

against a filter.

Response: Check the types of the subscription filter’s fields against those supplied in the corresponding publications

and retry the operation.

BIP7029 A Parsing Exception occurred when processing a published message to see if it matched a

subscriber’s filter.

Severity: 10 : Warning

Explanation: The PubSub Matching Engine requested that a message be parsed in order to determine whether it

matched a subscriber’s filter. The parsing operation was unsuccessful.

Response: See related messages.

BIP7030 Publish/Subscribe state recovery failed.

Severity: 20 : Error

Explanation: A problem was encountered when accessing the broker database while processing transactional

recovery for publish/subscribe information following some other error. The available information is given above in

other messages. Refer to earlier messages for the original cause of the transaction failure.

356 Diagnostic messages

Response: Check that the database is started and accessible, by using your database management tools. You may

find some useful information in the problem determination section of the product documentation. Investigate any

error codes given in the message above in your database documentation.

BIP7031 Publish/Subscribe state recovery started due to transaction rollback.

Severity: 0 : Information

Explanation: A transaction which involved an update to the Publish/Subscribe state has been rolled back in the

broker. In order to restore the Publish/Subscribe state to its prior value, it will be recovered from the broker’s

database. The available information is given above in other messages. Refer to earlier messages for the original cause

of the transaction failure.

Response: This message is for information only. There should be a matching message to indicate that recovery is

complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.

BIP7032 Publish/Subscribe state recovery started due to incorrect sequence number.

Severity: 0 : Information

Explanation: An internal Publish/Subscribe message has been received with an incorrect sequence number. This

indicates that the broker’s Publish/Subscribe state is inconsistent, and will be recovered from the broker’s database.

Response: This message is for information only. There should be a matching message to indicate that recovery is

complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.

BIP7033 Publish/Subscribe state recovery completed.

Severity: 0 : Information

Explanation: Recovery of the Publish/Subscribe state from the broker’s database is complete.

Response: This message is for information only. No action is required.

BIP7040 Unknown parameter name <insert_0>.

Severity: 20 : Error

Explanation: The parameter name <insert_0> is not a valid configuration parameter of the node.

Response: If this error has occurred as a result of an action from the Message Brokers Toolkit, it is an internal error

and you should contact your IBM support center. Otherwise, correct the invalid parameter name, then retry the

operation.

BIP7041 Invalid parameter value <insert_0> <insert_1>.

Severity: 20 : Error

Explanation: The parameter <insert_0> had a value <insert_1> which is outside its allowed range, contains

disallowed characters, is not a member of the permitted set of values, or was invalid for some other reason.

Response: If this error has occurred as a result of an action from the Message Brokers Toolkit, it is an internal error

and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation.

BIP7047 Neighbor (Queue Manager <insert_0>) failed to register the subscription request with reason code

<insert_1>.

Severity: 10 : Warning

Explanation: The Neighbor broker could not process the subscription request successfully. Broker will send the

subscription request again.

Response: Check the reason code and resolve the issue on Neighbor broker.

BIP7000 to BIP7999 (Publish Subscribe) 357

BIP7049 Unexpected Java exception <insert_0>.

Severity: 20 : Error

Explanation: An unexpected exception was thrown from Java code. The detail shows the Java stack trace where the

exception occurred. The broker may continue to run but may produce unexpected results.

Response: Restart the broker. If the problem persists you should contact your IBM support center.

BIP7050 Failed to locate Java class <insert_0>.

Severity: 30 : Severe error

Explanation: The Java class <insert_0> could not be found.

Response: This is an internal error and you should contact your IBM support center.

BIP7051 Failed to locate Java method <insert_0> in class <insert_1>.

Severity: 30 : Severe error

Explanation: The Java method <insert_0> in class <insert_1> could not be found.

Response: This is an internal error and you should contact your IBM support center.

BIP7052 Failed to create Java object <insert_0>.

Severity: 30 : Severe error

Explanation: The Java object <insert_0> could not be created.

Response: This is an internal error and you should contact your IBM support center.

BIP7053 Unexpected Java exception <insert_0>.

Severity: 30 : Severe error

Explanation: An unexpected exception was thrown from Java code. The detail shows the Java stack trace where the

exception occurred.

Response: This is an internal error and you should contact your IBM support center.

BIP7054 Unexpected null pointer for instance of class <insert_0>.

Severity: 30 : Severe error

Explanation: An unexpected null pointer exception was thrown from Java code on an object of class <insert_0>.

Response: This is an internal error and you should contact your IBM support center.

BIP7055 Invalid attribute value <insert_0> <insert_1>.

Severity: 20 : Error

Explanation: The attribute <insert_0> had a value <insert_1> which is outside its allowed range, contains disallowed

characters, is not a member of the permitted set of values, or was invalid for some other reason.

Response: If this error has occurred as a result of an action from the Message Brokers Toolkit, it is an internal error

and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation.

BIP7056 Attribute value not found or invalid <insert_0>.

Severity: 20 : Error

Explanation: The attribute <insert_0> had no value or the value could not be determined.

Response: If this error has occurred as a result of an action from the Message Brokers Toolkit, it is an internal error

358 Diagnostic messages

and you should contact your IBM support center. Otherwise, check the attribute has a valid value, then retry the

operation.

BIP7057 Invalid neighbor with queue manager <insert_0>.

Severity: 20 : Error

Explanation: The queue manager <insert_0> could not be contacted for the purpose of sending publications between

brokers. The connection has not been made.

Response: Ensure that the appropriate WebSphere MQ configuration is in place to allow the broker to communicate

with the given queue manager, and that there is a broker currently installed and configured on that queue manager.

BIP7058 Failed to create message element <insert_0>.

Severity: 30 : Severe error

Explanation: While attempting to build a message a failure occurred on creating element <insert_0>.

Response: This is an internal error and you should contact your IBM support center.

BIP7059 Failed to navigate to message element <insert_0>.

Severity: 30 : Severe error

Explanation: While attempting to explore the contents of a message an error occurred because the element

<insert_0> was missing or unreachable.

Response: This is an internal error and you should contact your IBM support center.

BIP7060 Unexpected filter in RFH message.

Severity: 20 : Error

Explanation: A filter was found in an RFH message, for which filters are not supported.

Response: Review the message and remove the filter, then retry the operation.

BIP7061 Invalid client identifier <insert_0>.

Severity: 30 : Severe error

Explanation: The client identifier <insert_0> is incomplete or invalid.

Response: This is an internal error and you should contact your IBM support center.

BIP7062 An invalid PCF message has been detected: diagnostic data <insert_0>.

Severity: 30 : Severe error

Explanation: An invalid PCF message has been detected.

Response: This is an internal error and you should contact your IBM support center.

BIP7063 Not an RFH message.

Severity: 30 : Severe error

Explanation: The message was found not to be an RFH message while performing an operation only supported for

RFH format messages.

Response: Ensure that the message sent for this operation has an RFH header and retry.

BIP7000 to BIP7999 (Publish Subscribe) 359

BIP7064 Failed to create Java VM <insert_0>.

Severity: 30 : Severe error

Explanation: The broker creates a Java Virtual Machine to support internal operations, but in this case has been

unable to do so. There may have been a problem with the way the product was installed, or something has

subsequently affected the installation.

Response: This is an internal error and you should contact your IBM support center.

BIP7065 Failed to attach thread to JVM.

Severity: 30 : Severe error

Explanation: The broker creates a Java Virtual Machine to support internal operations. This error indicates that there

has been an internal problem using the JVM.

Response: This is an internal error and you should contact your IBM support center.

BIP7066 Failed to get the Java Native Interface pointer.

Severity: 30 : Severe error

Explanation: The broker creates a Java Virtual Machine to support internal operations. This error indicates that there

has been an internal problem using the JVM.

Response: This is an internal error and you should contact your IBM support center.

BIP7067 Caught exception while deleting message flow <insert_0> <insert_1>.

Severity: 20 : Error

Explanation: There was a problem while attempting to delete the named message flow.

Response: This is an internal error and you should contact your IBM support center.

BIP7069 Tried to create two instances of <insert_0> where only one is allowed.

Severity: 30 : Severe error

Explanation: Some publish subscribe resources, such as the internal node which processes control messages, must

not be created more than once. This error indicates that an attempt was made to create a second instance of such a

resource.

Response: This is an internal error and you should contact your IBM support center.

BIP7071 Message (of type <insert_1>) on incorrect queue <insert_0>.

Severity: 20 : Error

Explanation: An application put a message of type <insert_1> on queue <insert_0>. This queue is not intended for

messages of that type and the message was not processed.

Response: Ensure that your applications are putting messages on the correct queue. Publish and Delete Publication

messages should only be put on application queues. Control messages should only be put on

SYSTEM.BROKER.CONTROL.QUEUE. Correct the application, then retry the operation.

BIP7072 Neighbor (queue manager <insert_0>) is already an WebSphere publish/subscribe neighbor.

Severity: 20 : Error

Explanation: An attempt has been made to join this broker with a WebSphere Message Brokers broker on queue

manager <insert_0>. This request was unsuccessful because the broker is already joined as an WebSphere

publish/subscribe neighbor.

Response: If queue manager <insert_0> is a WebSphere Message Brokers broker then it can only be joined to this

360 Diagnostic messages

broker when the WebSphere publish/subscribe link has been removed. This can be achieved using the

mqsiclearmqpubsub command.

BIP7073 Invalid publisher event message received in subordinate process.

Severity: 30 : Severe error

Explanation: A publisher event message, which is used to synchronize publish/subscribe information between two

execution groups, had no message body, so was not correctly processed.

Response: If you have several execution groups, they may be out of step. They can be resynchronized by restarting

the broker, but this is an internal error and you should contact your IBM support center.

BIP7074 Exception <insert_1> condition detected while recovering client <insert_0> from the database.

Severity: 20 : Error

Explanation: An exception condition was detected in the message broker when trying to recover a client from the

database.

Response: Ensure that the client id exists and is valid and re-try the operation.

BIP7075 Unable to find client id <insert_0> for subscription registered to topic <insert_1>.

Severity: 20 : Error

Explanation: While trying to recover the subscriptions a matching client id could not be found.

Response: Ensure that the client id is valid and re-try the operation.

BIP7076 Unable to find client id <insert_0> for publisher registered to topic <insert_1>.

Severity: 20 : Error

Explanation: While trying to recover the Publisher a matching client id could not be found.

Response: This is an internal error and you should contact your IBM support center.

BIP7077 Unable to start Publish/Subscribe Service.

Severity: 30 : Severe error

Explanation: The message broker was unable to start the Publish/Subscribe Service. See the following messages for

details of the error.

Response: If the error persists contact your IBM support center.

BIP7078 Failed to detach thread from the JVM.

Severity: 30 : Severe error

Explanation: The broker creates a Java Virtual Machine to support internal operations. This error indicates that there

has been an internal problem using the JVM.

Response: This is an internal error and you should contact your IBM support center.

BIP7079 Node <insert_1>: The Publish/Subscribe service has received a message of type <insert_0>.

Severity: 0 : Information

Explanation: The Publish/Subscribe service has started processing a control message.

Response: No user action required.

BIP7000 to BIP7999 (Publish Subscribe) 361

BIP7080 Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received a message of

type <insert_0>.

Severity: 0 : Information

Explanation: The Publication Node with Subscription Point <insert_1> has started processing a message.

Response: No user action required.

BIP7081 The Publication Node has matched <insert_0> subscriptions to topic <insert_1> for subscription point

<insert_2>.

Severity: 0 : Information

Explanation: The Publication Node has matched subscriptions for the current publication and topic.

Response: No user action required.

BIP7082 Node <insert_2>: Publishing to destination <insert_0> for user <insert_1>.

Severity: 0 : Information

Explanation: A publication destination is being added to the list of destinations to <insert_0> for user <insert_1>.

Response: No user action required.

BIP7083 Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received an error code

<insert_0>.

Severity: 0 : Information

Explanation: The Publication Node with Subscription Point <insert_1> has received an error with code <insert_0>. A

response message has been sent to the originator’s reply queue.

Response: No user action required.

BIP7084 Node <insert_1>: The Publish/Subscribe service has received an error code <insert_0>.

Severity: 0 : Information

Explanation: The Publish/Subscribe service has received an error with code <insert_0>. A response message has

been sent to the originator’s reply queue.

Response: No user action required.

BIP7085 Node <insert_1>: The Publication Node has propagated a message to its output terminal for

subscription point <insert_0>.

Severity: 0 : Information

Explanation: The Publication Node has propagated the current message to its output terminal.

Response: No user action required.

BIP7086 Node <insert_2>: The Publication Node with Subscription Point <insert_1> has received an error code

<insert_0>.

Severity: 0 : Information

Explanation: The Publication Node with Subscription Point <insert_1> has received an error with code <insert_0>.

No response message has been sent as one was not requested.

Response: No user action required.

362 Diagnostic messages

BIP7087 Node <insert_1>: The Publish/Subscribe service has received an error code <insert_0>.

Severity: 0 : Information

Explanation: The Publish/Subscribe service has received an error with code <insert_0>. No response message has

been sent because one was not requested.

Response: No user action required.

BIP7088 publish/subscribe configuration request <insert_0> cannot be processed until after WebSphere

publish/subscribe migration has completed.

Severity: 10 : Warning

Explanation: The broker has been created as a replacement for an existing WebSphere publish/subscribe broker.

Until all subscriptions and retained publications have been successfully migrated into the WebSphere Message

Brokers broker it is not possible to deploy any new publish/subscribe configuration changes.

Response: Redeploy the configuration changes after migration has completed successfully.

BIP7089 Publish/Subscribe migration logic error.

Severity: 30 : Severe error

Explanation: The broker has been created as a replacement for an existing WebSphere Publish/Subscribe broker. A

logic error has been detected which has caused the broker to terminate.

Response: This error should be reported to your IBM support center. Until the problem is corrected you can not

continue to use your existing WebSphere Publish/Subscribe broker.

BIP7090 Configuration Manager’s subscription cannot be processed at this time.

Severity: 0 : Information

Explanation: The broker has been created as a replacement for an existing WebSphere Publish/Subscribe broker. As

part of its normal processing for newly created brokers the Configuration Manager has subscribed to event

publications at the new broker. It is not possible for the migrating broker to process this request at this time.

Response: None. This is an expected occurrence when deploying to a broker which is being migrated. The

Configuration Manager will reissue its subscription the next time you deploy to this broker. This should be done

after migration has completed.

BIP7091 Caught exception <insert_2> while deregistering subscriptions for client id <insert_0>: error code

<insert_1>.

Severity: 20 : Error

Explanation: There was a problem while attempting to deregister all subscriptions for a client.

Response: Due to the error deregistering the subscription, the subscription state of the broker may be inconsistent. It

may be necessary to restart the broker to eliminate the problem. If the problem persists, you should contact your IBM

support center.

BIP7092 Problem removing expired retained publication.

Severity: 20 : Error

Explanation: An exception has occurred whilst removing an expired retained publication. Previous messages will

indicate the exact nature of this exception and its severity. The Dynamic Subscription Engine state has been rolled

back.

Response: Check the error messages which precede this error to determine why the failure occurred, and take

action as described by those messages.

BIP7000 to BIP7999 (Publish Subscribe) 363

BIP7093 Attribute style properties not allowed in publish/subscribe message.

Severity: 20 : Error

Explanation: A publish/subscribe message was received where the properties were expressed like XML attributes.

For example, <psc Command=″Publish″ />. This is not allowed - you should use the nested tag syntax to express the

publish/subscribe information. The above example should be <psc><Command>Publish</Command></psc>. See

the WebSphere Message Brokers Programming Guide, for more information and examples.

Response: Change the application which generated the message to use syntax as described above.

BIP7094 Exception condition detected while sending deferred message of type <insert_0>. Failure count is

<insert_1>.

Severity: 10 : Warning

Explanation: The publish/subscribe service detected an error whilst sending a deferred message of type <insert_0>,

where 1 indicates an administrative event publication, 2 indicates a command message destined for another broker,

and 3 indicates an internal command message destined for another execution group. The number of times this

message has been tried is <insert_1>. The attempt to send the message will be retried later, unless the message is an

administrative event publication, in which case it will only be retried three times before being discarded. Following

messages will indicate the cause of this exception.

Response: Check the error messages which follow to determine why the exception was generated, and take action

as described by those messages.

BIP7095 Requested response cannot be sent for non-RFH message.

Severity: 20 : Error

Explanation: A message requesting a response was received by the Publish/Subscribe Service. In order to send a

response, the Publish/Subscribe Service requires that the message contains an RFH or RFH2 format header. The

received message contained neither.

Response: Ensure that the message was placed on the correct queue for the required message flow. If the correct

queue was used, ensure that the message sent for this operation has an RFH or RFH2 header, or ensure that the

report options in the message descriptor are set so that a response is not requested.

BIP7096 Node <insert_0>: The ComIbmJmsIpInput Node has propagated a message to its output terminal.

Severity: 0 : Information

Explanation: The ComIbmJmsIpInput Node has propagated the current message to its output terminal.

Response: No user action required.

BIP7097 Java Virtual Machine OutOfMemoryError occurred.

Severity: 20 : Error

Explanation: The JVM has reported an OutOfMemoryError situation.

Response: It may be neccasary to stop and restart the Broker and increase the Java Virtual Machine Heap size

BIP7098 Unable to find user <insert_0> for subscription registered to topic <insert_1>.

Severity: 10 : Warning

Explanation: While trying to recover a subscription, a user id could not be found. The subscription will be removed

from the broker.

Response: None.

364 Diagnostic messages

BIP7101 Could not access MQConnectionManager resource.

Severity: 30 : Severe error

Explanation: The Publish/Subscribe Service, implemented in imbdfjps.lil, requires the presence of the WebSphere

MQ library, imbdfmqm.lil. This library is either missing or invalid. Other messages may indicate the reasons for the

failure to load imbdfmqm.lil.

Response: Ensure that imbdfmqm.lil is valid and in the correct location. Check other messages for reasons why

imbdfmqm.lil might not have loaded.

BIP7102 Requesting broker <insert_0> has inconsistent Queue Manager value <insert_1>.

Severity: 10 : Warning

Explanation: A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) has been defined with this

broker as a neighbor, and has attempted to make contact. This broker has been configured for the other broker, but

with a different Queue Manager name. This may occur because a broker at one end of a connection in the broker

topology has not been running for some time, and may receive old configuration messages from brokers which have

since been reconfigured.

Response: Ensure that the communication paths exist between both brokers, and are running correctly. If the

brokers do not subsequently connect successfully (which will be identified by another message), reestablish the

broker topology by redeploying. If the problem persists, contact your IBM support center.

BIP7103 Requesting broker <insert_0> (Queue Manager <insert_1>) is currently unknown.

Severity: 10 : Warning

Explanation: A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) has been defined with this

broker as a neighbor, and has attempted to make contact. As the requesting broker is not currently known by this

broker, the request has been rejected. This message occurs because the configuration message updating the broker

topology has reached one broker before the other. If the communication paths between the brokers are set up and

running correctly, this message will be followed by another one which will indicate that the connection between the

brokers has been successful. If the communication paths are not set up correctly, no such message will be produced,

and publications will not flow between the brokers.

Response: If no message indicating the successful connection of the broker is produced, ensure that the

communication paths exist between both brokers, and are running correctly. If the brokers do not subsequently

connect successfully (which will be identified by another message), reestablish the broker topology by redeploying. If

the problem persists, contact your IBM support center.

BIP7104 Interbroker message flow <insert_0> not found.

Severity: 30 : Severe error

Explanation: The message flow <insert_0> dedicated to serving interbroker function was not found.

Response: Examine the system log for errors on startup to see if there was an error which might have led to the

interbroker message flow not being created. This problem may be resolved by stopping and restarting the broker.

Otherwise contact your IBM support center.

BIP7105 Interbroker node not found in messageflow <insert_0>.

Severity: 30 : Severe error

Explanation: An attempt was made to locate the Interbroker node within message flow <insert_0>. This message

flow is internally created and managed by the broker. This is an internal error.

Response: Examine the system log for errors on startup to see if there was an error which might have lead to the

message flow not being created correctly. This problem may be resolved by stopping and restarting the broker. If the

problem cannot be resolved contact your IBM support center.

BIP7000 to BIP7999 (Publish Subscribe) 365

BIP7106 Accepting broker <insert_0> (Queue Manager <insert_1>) is currently unknown.

Severity: 10 : Warning

Explanation: A broker (identified by its UUID <insert_0> and Queue Manager <insert_1>) has been defined with this

broker as a neighbor, and has sent this broker a connection acceptance message. This broker is not currently

configured for the other broker, although it was at some time in the past. This may occur because a broker at one end

of a connection in the broker topology has not been running for some time, and may receive old configuration

messages from brokers which have since been reconfigured.

Response: Ensure that the communication paths exist between both brokers, and are running correctly. If the

brokers do not subsequently connect successfully (which will be identified by another message), reestablish the

broker topology by redeploying. If the problem persists, contact your IBM support center.

BIP7107 The ComIbmJmsIpInput Node <insert_1> code caught an unknown exception on thread <insert_0>.

Severity: 30 : Severe error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. The exception was issued on thread <insert_0>. Futher information

may be in the exception information associated with this message.

Response: The broker should shutdown and restart automatically. If the problem continues to occur, then restart the

system. If the problem still continues to occur, then contact your IBM support center.

BIP7108 The ComIbmJmsIpInput Node <insert_1> code caught a fatal exception on thread <insert_0>.

Severity: 30 : Severe error

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. The exception was issued on thread <insert_0>. Futher information

may be in the exception information associated with this message.

Response: The broker should shutdown and restart automatically. If the problem continues to occur, then restart the

system. If the problem still continues to occur, then contact your IBM support center. Exception details follow.

BIP7109 The ComIbmJmsIpInput Node <insert_1> code caught a recoverable exception on thread <insert_0>.

Severity: 10 : Warning

Explanation: An internal software error has occurred in the message broker. Further messages will indicate the

effect of this error on the broker’s transactions. The exception was issued on thread <insert_0>. Futher information

may be in the exception information associated with this message.

Response: The broker should continue to operate normally. If the problem continues to occur, then shutdown and

restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details

follow.

BIP7110 A recoverable exception on thread <insert_0> was caught while trying to convert message.

Severity: 10 : Warning

Explanation: An exception caught whilst trying to convert a message to or from a WebSphere MQ message. The

exception was issued on thread <insert_0>. Futher information may be in the exception information associated with

this message.

Response: The broker should continue to operate normally. If the problem continues to occur, then shutdown and

restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details

follow.

366 Diagnostic messages

BIP7111 A fatal exception on thread <insert_0> was caught while trying to convert message.

Severity: 30 : Severe error

Explanation: An exception caught whilst trying to convert a message to or from a WebSphere MQ message. The

exception was issued on thread <insert_0>. Futher information may be in the exception information associated with

this message.

Response: The broker should shutdown and restart automatically. If the problem continues to occur, then shutdown

and restart the system. If the problem still continues to occur, then contact your IBM support center. Exception details

may follow.

BIP7112 Requesting broker (UUID <insert_0>, queue manager <insert_1>) has an incorrect value <insert_2> for

this broker’s UUID, which is <insert_3>.

Severity: 10 : Warning

Explanation: A broker (identified by its UUID and queue manager name) has been defined with this broker as a

neighbor, and has attempted to make contact. However the neighboring broker’s definition for this broker has used a

different UUID from that which this broker is running under. This may occur because a broker at one end of a

connection in the broker topology has not been running for some time, and may receive old configuration messages

from brokers which have since been reconfigured.

Response: Ensure that the communication paths exist between both brokers, and are running correctly. If the

brokers do not subsequently connect successfully (which will be identified by another message), reestablish the

broker topology by redeploying. If the problem persists, contact your IBM support center.

BIP7113 Interbroker connection established with neighbor (Queue Manager <insert_0>).

Severity: 0 : Information

Explanation: A connection has been established with neighboring broker (Queue Manager <insert_0>) for the

purposes of sending publications between the brokers.

Response: This message is for information only, to confirm that the interbroker connection has been made

successfully.

BIP7114 Interbroker connection ended with neighbor (Queue Manager <insert_0>).

Severity: 0 : Information

Explanation: An active connection has been ended with the neighboring broker (Queue Manager <insert_0>).

Publications will not flow between the brokers until the connection is reestablished.

Response: This message is for information only, to confirm that the connection has been ended.

BIP7115 Failure to create message flow for neighboring broker: error code <insert_0>.

Severity: 30 : Severe error

Explanation: An attempt to create a message flow to connect to a neighboring broker was unsuccessful.

Response: This is an internal error and you should contact your IBM support center.

BIP7116 Failure to modify message flow for neighboring broker: error code <insert_0>.

Severity: 30 : Severe error

Explanation: An attempt to modify a message flow to connect to a neighboring broker was unsuccessful.

Response: This is an internal error and you should contact your IBM support center.

BIP7000 to BIP7999 (Publish Subscribe) 367

BIP7117 Broker must be restarted for topology update to take effect.

Severity: 10 : Warning

Explanation: In some cases, updates to topology information require the broker to be restarted. The broker may

produce unpredicatable results until it is restarted.

Response: Restart the broker.

BIP7118 A recoverable exception was caught while trying to publish a subscription event message.

Severity: 10 : Warning

Explanation: A recoverable exception caught whilst trying to publish a subscription event message. The exception

was issued on thread <insert_0>. Futher information may be in the exception information associated with this

message.

Response: The broker should continue to operate normally. If the problem continues to occur, then shutdown and

restart the broker. If the problem still continues to occur, then contact your IBM support center. Exception details

follow.

BIP7119 A fatal exception was caught while trying publish a subscription event message

Severity: 30 : Severe error

Explanation: A fatal exception caught whilst trying to publish a subscription event message. The exception was

issued on thread <insert_0>. Futher information may be in the exception information associated with this message.

Response: The broker should shutdown and restart automatically. If the problem continues to occur, then shutdown

and restart the system. If the problem still continues to occur, then contact your IBM support center. Exception details

may follow.

BIP7150 User id <insert_2> not authorized to put to queue <insert_1> on queue manager <insert_0> using

accounting token <insert_3>.

Severity: 20 : Error

Explanation: The user is not authorized to put a message on the named queue.

Response: Ensure the user is allowed to perform this operation. This may involve configuring the WebSphere MQ

settings for this queue, or using an alternative userid which is authorized.

BIP7151 Tried to create two pub/sub user/group data stores.

Severity: 30 : Severe error

Explanation: The internal object which represents the data store for users or groups, must not be created more than

once. This error indicates that an attempt was made to create a second instance of such a resource.

Response: This is an internal error and you should contact your IBM support center.

BIP7201 Tried to create two PubSubResources.

Severity: 30 : Severe error

Explanation: The internal object which represents state information for publish subscribe resources, must not be

created more than once. This error indicates that an attempt was made to create a second instance of such a resource.

Response: This is an internal error and you should contact your IBM support center.

BIP7202 Invalid tag <insert_0>.

Severity: 30 : Severe error

Explanation: A tag (<insert_0>) found in a configuration message was not understood.

Response: This is an internal error and you should contact your IBM support center.

368 Diagnostic messages

BIP7203 Missing tag <insert_0>.

Severity: 30 : Severe error

Explanation: A <insert_0> tag in a configuration message was expected, but not found.

Response: This is an internal error and you should contact your IBM support center.

BIP7204 Exception while creating <insert_0> message flow <insert_1>.

Severity: 30 : Severe error

Explanation: A problem occurred while trying to create a <insert_0> type of message flow. The exception detail was

<insert_1>

Response: This is an internal error and you should contact your IBM support center.

BIP7205 Attribute <insert_0> of tag <insert_1> missing from the configuration message.

Severity: 30 : Severe error

Explanation: The configuration message is invalid. The attribute <insert_0> is required for the <insert_1> tag.

Response: This is an internal error and you should contact your IBM support center.

BIP7250 Unexpected message received on WebSphere Publish/Subscribe interbroker communications queue

<insert_0>: PutApplName <insert_1>; additional diagnostic data <insert_2>.

Severity: 30 : Severe error

Explanation: The broker has read a message from a queue used by the broker to receive messages from WebSphere

Publish/Subscribe neighbors and command line requests. The format of the message received by the broker has not

been recognized. It may have been put on the wrong queue by an application.

Response: The message will be left on the queue and will need to be removed from the queue before the broker

will continue to operate normally. Browse queue <insert_0> to determine the source of the invalid message. Remove

the offending message from the queue and restart your broker. If the offending message was not put onto the queue

by one of your applications, capture the message and all other diagnostic data contained within this message and

contact your IBM support center.

BIP7251 Invalid state <insert_1> detected for WebSphere Publish/Subscribe neighbor <insert_0> whilst

processing control message of type <insert_2>.

Severity: 30 : Severe error

Explanation: This is an internal error within the broker.

Response: Keep all diagnostic information contained within this message and contact your IBM support center.

BIP7252 Failed to map <insert_0> parameter/value <insert_1>.

Severity: 30 : Severe error

Explanation: This is an internal error within the broker.

Response: Keep all diagnostic information contained within this message and contact your IBM support center.

BIP7255 WebSphere Publish/Subscribe broker <insert_0> is already a neighbor.

Severity: 30 : Severe error

Explanation: An internal error has occurred while adding WebSphere Publish/Subscribe broker <insert_0> as a

neighbor. Broker <insert_0> is already a neighbor.

Response: Contact your IBM support center.

BIP7000 to BIP7999 (Publish Subscribe) 369

BIP7256 WebSphere Publish/Subscribe broker <insert_0> is not a neighbor.

Severity: 30 : Severe error

Explanation: An internal error has occurred within the broker which has resulted in an attempt to remove a

WebSphere Publish/Subscribe broker which is not a neighbor.

Response: Contact your IBM support center.

BIP7257 WebSphere Publish/Subscribe neighbor <insert_0> state <insert_1> unsuitable to be made active.

Severity: 30 : Severe error

Explanation: An internal error has occurred within the broker which has resulted in an attempt to activate a

WebSphere Publish/Subscribe broker which not in a valid state.

Response: Contact your IBM support center.

BIP7258 A message has been received from unknown WebSphere Publish/Subscribe broker: link identifier

<insert_0>.

Severity: 10 : Warning

Explanation: A message was received from a WebSphere Publish/Subscribe broker which is not known to this

broker. A failure response will be sent to the sending broker.

Response: No user action required.

BIP7259 Message broker <insert_0> has failed to import a migrated subscription: diagnostic information

<insert_1>, <insert_2>.

Severity: 20 : Error

Explanation: The migmqbrk command has been issued to migrate a WebSphere Publish/Subscribe broker. The

message broker has failed to import a subscription. The diagnostic information associated with this error is <insert_1>

and <insert_2>

Response: Contact your IBM support center.

BIP7260 Message broker <insert_0> already has a parent WebSphere Publish/Subscribe broker <insert_1>.

Severity: 10 : Warning

Explanation: The mqsijoinmqpubsub command has been used to join this message broker to a WebSphere

Publish/Subscribe broker. This broker already has a parent broker so the command has been rejected.

Response: Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with.

BIP7261 An invalid control message from a WebSphere Publish/Subscribe neighbor has been detected:

diagnostic information <insert_0>, <insert_1>.

Severity: 20 : Error

Explanation: This is an internal error.

Response: Contact your IBM support center.

BIP7262 A WebSphere Publish/Subscribe control message intended for broker <insert_1> has been detected:

diagnostic information <insert_0>.

Severity: 20 : Error

Explanation: This is an internal error.

Response: Contact your IBM support center.

370 Diagnostic messages

BIP7263 Unexpected communication received from WebSphere Publish/Subscribe broker <insert_0>.

Severity: 10 : Warning

Explanation: The broker has received an inter-broker communication from a WebSphere Publish/Subscribe broker

that it did not expect. The message was sent by broker <insert_0>. The most likely reason for this message is that the

broker topology has been changed while inter-broker communication messages were in transit (for example, on a

transmission queue) and that a message relating to the previous broker topology arrived at a broker in the new

topology.

Response: If the broker topology has changed and the broker named in the message is no longer related to the

broker issuing this message, this message can be ignored. If the mqsiclearmqpubsub was issued to unilaterally

remove knowledge of broker <insert_0> from this broker, the clrmqbrk command should also be used at broker

<insert_0> to remove knowledge of this broker.

BIP7264 Message broker could not send completion code <insert_0> to a command line request.

Severity: 10 : Warning

Explanation: An mqsijoinmqpubsub or mqsiclearmqpubsub request has been made from the command line. The

request has been processed by the message broker, but a failure has occurred when trying to respond to the reply

queue used by the command line program. If the completion code is zero, the request succeeded. A nonzero

completion code means that the request failed or was rejected by the message broker.

Response: Look for a previous error message, usually BIP2623, outlining the cause of the problem. If message

BIP2623 reports a WebSphere MQ reason code of 2085 or 2052, this means that the temporary reply queue used by

the command line program no longer exists, perhaps because Ctrl-C has been pressed or the request has timed out.

Any other reason code is unexpected and should be looked up in the WebSphere MQ Application Programming

Reference manual.

BIP7265 Bad data returned from WebSphere Publish/Subscribe database table: diagnostic information

<insert_0>, <insert_1>.

Severity: 20 : Error

Explanation: This is an internal error within the broker.

Response: Keep all diagnostic information contained within this message and contact your IBM support center.

BIP7266 Invalid WebSphere publish/subscribe migration message detected on queue <insert_2>: diagnostic

information <insert_0>, <insert_1>.

Severity: 20 : Error

Explanation: The message broker has been processing migration messages arriving on a queue as a result of the

migmqbrk command being issued against an WebSphere publish/subscribe broker. The message broker has detected

an invalid message on this queue.

Response: This is an internal error, contact your IBM support center with the diagnostic information. The migration

attempt can be retried by issuing the migmqbrk command again. If repeated attempts all fail with this error,

providing both WebSphere and WebSphere Message Brokers traces will help with problem resolution.

BIP7267 Invalid WebSphere Publish/Subscribe control message detected on queue <insert_2>: diagnostic

information <insert_0>, <insert_1>.

Severity: 30 : Severe error

Explanation: The message broker has been processing messages on a queue. Messages are sent to the queue by

neighboring WebSphere Publish/Subscribe brokers or as a result of the mqsijoinmqpubsub or mqsiclearmqpubsub

commands being issued. The message broker has detected an invalid message on the queue. The message will be

backed out and retried until such time as the backout threshold of the queue has been exceeded at which time it will

be put to the dead letter queue.

Response: This is an internal error, contact your IBM support center. The diagnostic information will need to be

reported along with the message which is causing the problem. To recover from this problem, set an appropriate

BIP7000 to BIP7999 (Publish Subscribe) 371

backout threshold for the queue which will cause the invalid message to be put to the dead letter queue. From here

the message can be captured by running the amqsbcg sample program against the dead letter queue and saving the

output to a file. If you do not have a dead letter queue, you will need to remove the invalid message manually from

the queue. The message broker will need to be stopped and again you should capture the invalid message by

running the amqsbcg sample program against the queue before the message is removed.

BIP7268 WebSphere Publish/Subscribe broker <insert_0> is not known by this message broker.

Severity: 10 : Warning

Explanation: The mqsiclearmqpubsub command has been used to remove WebSphere Publish/Subscribe broker

<insert_0>. This broker is not known by this message broker so the command has been rejected.

Response: Reissue the mqsiclearmqpubsub command specifying the correct broker to be removed.

BIP7269 WebSphere Publish/Subscribe broker <insert_0> is already known by this message broker.

Severity: 10 : Warning

Explanation: The mqsijoinmqpubsub command has been used to join this message broker to WebSphere

Publish/Subscribe broker <insert_0>. This broker is already known so the command has been rejected.

Response: Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with.

BIP7270 Attempt to join with parent WebSphere Publish/Subscribe broker <insert_0> failed because a parent

<insert_1> already exists.

Severity: 10 : Warning

Explanation: The mqsijoinmqpubsub command has been used to join this message broker to WebSphere

Publish/Subscribe broker. The attempt has been rejected because the message broker already has a parent broker.

Response: The message broker can only be joined to a single parent WebSphere Publish/Subscribe broker. To

change the parent broker you will need to remove the existing parent. This can be achieved by issuing

mqsiclearmqpubsub at this broker and clrmqbrk at the WebSphere Publish/Subscribe broker.

BIP7271 Loop joining message broker <insert_0> to WebSphere Publish/Subscribe broker <insert_1>.

Severity: 10 : Warning

Explanation: The mqsijoinmqpubsub command has been used to join a message broker to a parent WebSphere

Publish/Subscribe broker. The action has caused a loop to created in the WebSphere Publish/Subscribe hierarchy.

Response: Use the mqsiclearmqpubsub at the broker and clrmqbrk at the WebSphere Publish/Subscribe broker to

remove the loop from the hierarchy.

BIP7272 WebSphere Publish/Subscribe migration has started for message broker <insert_0>.

Severity: 0 : Information

Explanation: The migmqbrk command has been issued to start migration of a WebSphere Publish/Subscribe broker.

Response: No user action required. A further message will be issued when the migration has finished.

BIP7273 WebSphere publish/subscribe migration has completed successfully for message broker <insert_0>.

Severity: 0 : Information

Explanation: The migration of the WebSphere publish/subscribe broker has been successful.

Response: All subscriptions, retained publications and local publisher registrations have been loaded into message

broker <insert_0>. The message broker will automatically start to process new subscription messages arriving on

queue SYSTEM.BROKER.CONTROL.QUEUE. You now need to manually deploy publication message flows for each

of the stream queues which were supported by the WebSphere publish/subscribe broker. Guidance for this task can

be found in the WebSphere Message Brokers Introduction and Planning guide.

372 Diagnostic messages

BIP7274 WebSphere Publish/Subscribe migration has failed for message broker <insert_0> with reason code

<insert_1>.

Severity: 20 : Error

Explanation: An attempt has been made to migrate a WebSphere Publish/Subscribe broker. This has failed with a

reason code of <insert_1>.

Response: Investigate the reason for the failure. Look for previous messages issued by message broker <insert_0>

and also look for any WebSphere MQ messages issued by the migmqbrk command. The migration can be retried by

issuing the migmqbrk command again. If repeated migration attempts all fail then you should contact your IBM

support center.

BIP7275 Unexpected message of type <insert_1> received from WebSphere Publish/Subscribe broker

<insert_0>.

Severity: 20 : Error

Explanation: A unexpected message has been received from a neighboring WebSphere Publish/Subscribe broker.

Response: This is an internal error and you should contact your IBM support center.

BIP7276 WebSphere Message Brokers broker has failed to join with WebSphere publish/subscribe broker

<insert_0> for reason <insert_1>.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub command has been issued to join with WebSphere publish/subscribe broker

<insert_0>. The WebSphere Message Brokers broker attempted to register as a child of the WebSphere

publish/subscribe broker but received an exception response indicating that this was not possible.

Response: Investigate why the problem occurred and take appropriate action to correct the problem. The problem is

likely to be caused by the parent broker not yet existing, or a problem with the

SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS queue at the parent broker. Once the problem has been

resolved, the mqsijoinmqpubsub command should be reissued to retry the joining of the two brokers.

BIP7277 WebSphere Message Brokers broker has failed to subscribe to WebSphere publish/subscribe broker

<insert_0>. Reason codes <insert_1> and <insert_2>.

Severity: 20 : Error

Explanation: The strmqbrk command has been issued at WebSphere publish/subscribe broker <insert_0>

nominating this WebSphere Message Brokers broker as its parent. While handling the resultant join request the

WebSphere Message Brokers broker sent an internal subscription to the admininstration stream of broker <insert_0>.

The subscription failed and as a result the two brokers are not yet joined together. The broker will reissue the

subscription immediately.

Response: Investigate why the problem occurred and take appropriate action to correct the problem. The most likely

cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker <insert_0>, or a problem

with the definition of route between this broker and broker <insert_0>. Once the problem has been rectified this error

message will no longer be issued. If you cannot rectify the problem then consider reversing the attempted joining of

the two brokers. This can be achieved using the clrmqbrk command at broker <insert_0> and the mqsiclearmqpubsub

command at this broker.

BIP7278 WebSphere Message Brokers broker has failed to propagate a subscription to WebSphere

publish/subscribe broker <insert_0>. Reason codes <insert_1> and <insert_2>.

Severity: 20 : Error

Explanation: An application has either registered or deregistered a global subscription. The broker has attempted to

propagate the subscription change to WebSphere publish/subscribe broker <insert_0> but the request has not been

successful. The WebSphere Message Brokers broker will immediately attempt to refresh the state of all global

subscriptions at broker <insert_0>. Until the subscription state has been successfully refreshed, messages published

through broker <insert_0> might not reach this broker.

BIP7000 to BIP7999 (Publish Subscribe) 373

Response: Investigate why the problem occurred and take appropriate action to correct the problem. The most likely

cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker <insert_0>, or a problem

with the definition of route between this broker and broker <insert_0>. When the problem has been rectified, this

error message will no longer be issued.

BIP7279 WebSphere Message Brokers broker failed to inform parent WebSphere publish/subscribe broker

<insert_0> of a new broker for reason <insert_1>.

Severity: 10 : Warning

Explanation: When a new broker is added to an WebSphere publish/subscribe network the integrity of the new

hierarchy is checked by forwarding notification of the new broker to other brokers in the network. The WebSphere

Message Brokers broker has failed to notify its parent on queue manager <insert_0> of the new broker. A failure to

notify a broker of a new broker will mean that loop detection cannot be performed for the new broker.

Response: Diagnose and correct the problem on the parent queue manager. One possible reason for this is that the

parent broker does not yet exist.

BIP7280 Message broker failed to propagate a delete publication command on topic <insert_2> to WebSphere

Publish/Subscribe broker <insert_0> for reason <insert_1>.

Severity: 20 : Error

Explanation: When an application issues a delete publication command to delete a global publication, the command

is propagated to all neighboring WebSphere Publish/Subscribe brokers. The delete publication command has failed to

be forwarded to from the broker, and as such the retained publication on the topic will not have been deleted.

Response: Investigate why the delete publication for the topic has failed, and take the appropriate action to recover

the failed command. It is likely that the delete publication message sent to the broker will be present on a dead letter

queue either at one or other broker.

BIP7281 Request <insert_0> from WebSphere publish/subscribe broker <insert_2> contains an invalid topic

<insert_1>.

Severity: 10 : Warning

Explanation: The broker has received a request from neighboring a WebSphere publish/subscribe broker. The

request contained an invalid topic and will be ignored.

Response: In a mixed network of WebSphere Message Brokers and WebSphere publish/subscribe brokers it is not

possible for information to flow between the two types of broker on topics which contain wildcard characters # or +.

Client applications within the WebSphere publish/subscribe network need to be modified to use topics which do not

contain characters which are invalid to the WebSphere Message Brokers broker.

BIP7282 mqsijoinmqpubsub command from broker <insert_0> rejected because it named a WebSphere

Message Brokers broker <insert_1> instead of an WebSphere publish/subscribe broker as parent.

Severity: 10 : Warning

Explanation: The command mqsijoinmqpubsub named an WebSphere publish/subscribe broker as its parent. This

has been rejected because the named broker is an WebSphere Message Brokers broker. The two brokers have not been

joined together.

Response: Use the Message Brokers Toolkit to join the two WebSphere Message Brokers brokers together.

BIP7283 Message broker is waiting for WebSphere Publish/Subscribe migration.

Severity: 0 : Information

Explanation: The broker has been created in migration mode. No publication message flows should be created until

migration has completed successfully.

Response: Use the migmqbrk command to migrate the WebSphere Publish/Subscribe broker. If the broker has been

created incorrectly, the broker will need to be deleted and recreated.

374 Diagnostic messages

BIP7284 WebSphere publish/subscribe inter-broker queue <insert_0> cannot be accessed.

Severity: 10 : Warning

Explanation: The broker has WebSphere publish/subscribe neighbors. These neighbors communicate with this

broker using queue <insert_0>. The queue cannot be accessed which will affect inter-operability with all WebSphere

publish/subscribe neighbors.

Response: Check whether queue <insert_0> exists. If it does exist, ensure that the queue manager is running and

restart the broker. This will allow the broker to process messages from WebSphere publish/subscribe neighbors. If the

queue does not exist, consult the WebSphere Message Brokers Introduction and Planning manual for guidance about

how to define the queue. After the queue has been defined the broker will need to be restarted.

BIP7285 Subscription to topic <insert_0> will not be propagated to WebSphere publish/subscribe neighbors.

Severity: 10 : Warning

Explanation: A subscription to topic <insert_0> has been received. This will not be propagated to any of the

WebSphere publish/subscribe neighbors of this broker.

Response: You can ignore this message if the client making the subscription to topic <insert_0> is not interested in

any potential matching publications made within the WebSphere publish/subscribe part of your mixed broker

network. If this is not the case, the client will need to change its subscription to something more specific. Consult the

WebSphere Message Brokers Introduction and Planning guide for more information about using wildcard

subscriptions in a mixed broker network.

BIP7286 Message broker needs to be restarted after Publish/Subscribe migration.

Severity: 0 : Information

Explanation: The Message Broker <insert_0> has been created in migration mode. Once migration has completed,

the Message Broker needs to be restarted

Response: Use the migmqbrk command to migrate the WebSphere Publish/Subscribe broker. Once the migration is

complete, The Message Broker needs to be restarted.

BIP7350 Tried to create two data flow stores.

Severity: 30 : Severe error

Explanation: The internal object which represents the data store for publish/subscribe information, must not be

created more than once. This error indicates that an attempt was made to create a second instance of such a resource.

Response: This is an internal error and you should contact your IBM support center.

BIP7351 No data source supplied, so data flow configuration will not be persistent.

Severity: 10 : Warning

Explanation: The start up parameters for the broker did not include a database name, so this configuration will not

be saved anywhere.

Response: If persistence is required, ensure a database name is provided in the start up parameters for the broker.

BIP7352 Some (but not all) tables exist, pub/sub state will not be persistent.

Severity: 10 : Warning

Explanation: Some of the tables the broker requires in the database were missing so the broker state will not be

saved anywhere.

Response: The database may need to be rebuilt.

BIP7000 to BIP7999 (Publish Subscribe) 375

BIP7353 Tried to access a nonexistent data flow store.

Severity: 30 : Severe error

Explanation: An attempt was made to read from or write to a database that has not been properly initialized.

Response: Examine the system log for indications of a startup failure.

BIP7354 The multicast topics file name is empty.

Severity: 30 : Severe error

Explanation: The property MULTICAST_TOPICS_CONFIG_FILE does not contain a file name.

Response: Set the property MULTICAST_TOPICS_CONFIG_FILE to a vaild multicast topics file name.

BIP7355 Unable to locate file: <insert_0>.

Severity: 30 : Severe error

Explanation: The broker was unable to find the multicast topics file: <insert_0>.

Response: Check that the multicast topic file exists and try again.

BIP7356 Unable to parse entry for topic <insert_0>, <insert_1> is not a valid boolean. Entries must of the form

<topic>=<true|false>.

Severity: 30 : Severe error

Explanation: An error occured while parsing the multicast topics file.

Response: Correct the multicast topics file and restart the broker.

BIP7357 Message protection (Quality of Protection) has been enabled for the JMS/IP Input Node.

Severity: 0 : Information

Explanation: The broker has enabled message protection (Quality of Protection) for the JMS/IP Input Node.

Response: No user action required.

BIP7358 The new message protection (Quality of Protection) updates deployed have been deferred.

Severity: 10 : Warning

Explanation: The new message protection (Quality of Protection) updates deployed have been deferred.

Response: The broker must be restarted before the updated Quality of Protection settings will take effect.

BIP7359 The keyring file was not found at it’s specified location.

Severity: 30 : Severe error

Explanation: The keyring file used for SSL Authentication was not found at it’s specified location.

Response: Ensure that this file exists and that the broker has sufficient permission to access this file.

BIP7360 The pass phrase file was not found at it’s specified location.

Severity: 30 : Severe error

Explanation: The pass phrase file used for SSL Authentication was not found at it’s specified location.

Response: Ensure that this file exists and that the broker has sufficient permission to access this file.

376 Diagnostic messages

BIP7361 The pass phrase file specified is either invalid or does not contain the correct password to access the

SSL keyring file.

Severity: 30 : Severe error

Explanation: The pass phrase file specified is either invalid or does not contain the correct password to access the

SSL keyring file.

Response: The pass phrase file specified is either invalid or does not contain the correct password to access the SSL

keyring file.

BIP7362 The keyring file used for SSL Authentication has expired.

Severity: 30 : Severe error

Explanation: The keyring file used for SSL Authentication has expired.

Response: The keyring file used for SSL Authentication has expired.

BIP7363 The keyring file specified is invalid and cannot be read.

Severity: 30 : Severe error

Explanation: The keyring file specified is invalid and cannot be read.

Response: The keyring file specified is invalid and cannot be read.

BIP7364 The usernameserver has propagated an authentication protocol requiring SSL certificates although

the certificate and / or pass phrase have not been specified.

Severity: 30 : Severe error

Explanation: The usernameserver has propagated an authentication protocol requiring SSL certificates although the

certificate and / or pass phrase have not been specified.

Response: The usernameserver has propagated an authentication protocol requiring SSL certificates although the

certificate and / or pass phrase have not been specified.

BIP7365 An error occurred starting SSL Authentication: <insert_0>.

Severity: 30 : Severe error

Explanation: Refer to previous event messages for likely causes of this failure

Response: An SSL Exception occured. Please correct the problem then restart the broker.

BIP7366 An error occurred starting Real-time node with name <insert_0> listening on port <insert_1>.

Severity: 30 : Severe error

Explanation: An error occurred starting Real-time node with name <insert_0> listening on port <insert_1>. This is

normally because the Real-time node can not open the port specified.

Response: Find a port that is not being used by another application or node. Change the Real-time node in the

Message Brokers Toolkit and redeploy the messageflow.

BIP7370 A new multicast configuration has been deployed. The new configuration will not take effect until

the broker is restarted.

Severity: 10 : Warning

Explanation: A new multicast configuration has been deployed. The new configuration will not take effect until the

broker is restarted.

Response: The broker must be restarted for the settings to take effect.

BIP7000 to BIP7999 (Publish Subscribe) 377

BIP7371 The broker has bound to interface <insert_0> for multicast.

Severity: 0 : Information

Explanation: The broker will use interface <insert_0> for multicast transmission.

Response: This message is for information only, no response is required.

BIP7372 An attempt to <insert_0> one or more multicast topics failed as the broker is not enabled for

multicast.

Severity: 10 : Warning

Explanation: Although a deploy to the broker was successful, an attempt to <insert_0> one or more multicast topics

failed because the broker is not enabled for multicast. The <insert_0> request(s) will not be performed.

Response: To correct this action, the broker needs to be enabled for multicast and a complete re-deploy of the topic

tree needs to be made.

BIP7373 RMM Warning: <insert_0>

Severity: 10 : Warning

Explanation: RMM Warning: <insert_0>

Response: This is a warning message. No user action required.

BIP7374 RMM Error: <insert_0>

Severity: 30 : Severe error

Explanation: RMM Error: <insert_0>

Response: This is an internal error. Contact your IBM support center.

BIP7375 RMM Error: Missing configuration entry: <insert_0>

Severity: 30 : Severe error

Explanation: The configuration entry <insert_0> is missing.

Response: Change the multicast configuration and try again.

BIP7376 RMM Error: Bad argument. Parameter <insert_0>, value: <insert_1>

Severity: 30 : Severe error

Explanation: Multicast support failed to start because of illegal configuration values.

Response: Check multicast configuration and try again.

BIP7377 RMM Error: Socket creation failed. Port:<insert_0>

Severity: 30 : Severe error

Explanation: Failed to create a socket. This may indicate a host network configuration problem.

Response: Failed to create a socket. This may indicate a host network configuration problem. For example, trying to

create a multicast socket when multicast is disabled on the host.

BIP7378 RMM Error: Multicast interface setting to <insert_0> failed

Severity: 30 : Severe error

Explanation: Failed to set the interface on the multicast socket. This may indicate a wrong configured interface

address.

378 Diagnostic messages

Response: This may indicate a wrong configured interface address. Check the multicast interface setting and try

again.

BIP7379 RMM Error: Service <insert_0> interrupted

Severity: 30 : Severe error

Explanation: The multicast service <insert_0> was interrupted.

Response: This is an internal error. Contact your IBM support center.

BIP7380 RMM Error: Failed to set Time-To-Live to: <insert_0>

Severity: 30 : Severe error

Explanation: Failed to set the Time-To-Live parameter on the multicast socket

Response: This is an internal error. Contact your IBM support center.

BIP7381 RMM Error: Failed to join multicast group <insert_0>

Severity: 30 : Severe error

Explanation: Failed to join a multicast group address. This may indicate of a multicast network configuration

problem.

Response: A possible cause for this problem is a configured system limit on the maximum number of multicast

groups.

BIP7382 RMM Error: Failed to leave multicast group <insert_0>

Severity: 30 : Severe error

Explanation: Failed to leave a multicast group address. This may indicate a multicast network configuration

problem.

Response: Check your multicast group address configuration and try again.

BIP7383 RMM Error: Failed to allocate memory: <insert_0> bytes

Severity: 30 : Severe error

Explanation: Failed to allocate enough memory to deal with an incoming message. Stream data reception stops.

Response: Consider increasing the JVM memory heap size or lowering messaging rate of other transmitters.

BIP7384 RMM Error: Encoding <insert_0> not supported on this host

Severity: 30 : Severe error

Explanation: Failed to encode/decode a String because the local operating system does not support the specified

encoding.

Response: This is an internal error. Contact your IBM support center.

BIP7385 RMM Error: Failed to resolve addess: <insert_0>

Severity: 30 : Severe error

Explanation: Failed to resolve an internet address.

Response: This is probably because of a DNS problem, check your DNS setting and try again.

BIP7000 to BIP7999 (Publish Subscribe) 379

BIP7386 RMM Error: Failed to set socket buffer <insert_0> to <insert_1>

Severity: 30 : Severe error

Explanation: Failed to set the buffer size on the socket.

Response: This probably indicates a configured limitation in the operating system. This warning may lead to

inferior transport performance. Check operating system network configuration.

BIP7387 RMM Error: Received packet larger than configured PacketBufferLength <insert_0> from <insert_1>

Severity: 30 : Severe error

Explanation: Another machine sent a packet longer than the configured buffer length for incoming packets.

Response: This might indicate that another application is using multicast with a larger configured packet size or

that a malicious sender attempts to send large packets to local machine. Check identity and configuration of the

specified sending machine.

BIP7388 RMM Error: Terminating Service/Thread <insert_0> following unrecoverable problem

Severity: 30 : Severe error

Explanation: A multicast thread had to stop, due to a general unexpected error.

Response: This is an internal error. Contact your IBM support center.

BIP7389 RMM Error: Failed to send a packet to <insert_0>

Severity: 30 : Severe error

Explanation: Failed to send a data packet because of a network connectivity problem.

Response: Check network connectivity and try again.

BIP7390 RMM Error: Clock moved <insert_0>

Severity: 30 : Severe error

Explanation: RMM Error: Clock moved <insert_0>

Response: No user action required.

BIP7391 RMM Error: Failed to set socket parameter <insert_0> to <insert_1>

Severity: 30 : Severe error

Explanation: Failed to set socket parameter <insert_0> to <insert_1>. Exception is <insert_2>.

Response: Check operating system network configuration.

BIP7392 The broker was unable to load the native library required for PGM/IP.

Severity: 30 : Severe error

Explanation: A native library required for PGM/IP could not be loaded. The broker will not be able to provide

multicast support.

Response: Check that the broker has been installed correctly and contact you IBM support center

BIP7393 The broker multicast protocol has been set to PGM/IP. However, the broker is not running with

sufficient authority. The broker will revert to UDP encapsulated PGM.

Severity: 10 : Warning

Explanation: PGM/IP requires the broker to be run with administrator privileges. The broker has been started

without this authority. PGM/IP will not be available.

380 Diagnostic messages

Response: Restart the broker with administrator privileges to use PGM/IP.

BIP7401 Successfully cloned broker.

Severity: 0 : Information

Explanation: Broker <insert_0> has been successfully registered as a publish/subscribe clone of broker <insert_1>.

Response: No user action required.

BIP7402 Failed to connect to cloned broker’s Queue Manager <insert_0>.

Severity: 30 : Severe error

Explanation: The Queue Manager <insert_0> specified by the publish/subscribe clone broker request could not be

opened.

Response: Check that the queue manager specified is the correct one for the broker you widh to register as a clone.

BIP7403 Incorrect Broker name received during publish/subscribe cloning registration.

Severity: 30 : Severe error

Explanation: The Broker name <insert_0> specified by the publish/subscribe clone broker request did not match the

broker associated with Queue Manager <insert_1>.

Response: Check that the queue manager specified is the correct one for the broker you widh to register as a clone.

BIP7404 Neighbor (<insert_0>) is already known as a publish/subscribe neighbor.

Severity: 30 : Severe error

Explanation: The Neighbor <insert_0> is already known as a publish/subscribe neighbor and can not be created as

a clone.

Response: Either remove broker <insert_0> as a Neighbor and retry the command, or choose another broker to be a

clone.

BIP7405 Blank Broker Name <insert_0> or blank Queue Manager Name <insert_1>.

Severity: 30 : Severe error

Explanation: Blank Broker Name <insert_0> or blank Queue Manager Name <insert_1>.

Response: Check that you have specified values for the Broker Name, or Queue Manager name. Also check that the

command contains \″ for the value data. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o

DynamicSubscriptionEngine -n clonedPubSubBrokerList -v \″Broker1,QM1\″

BIP7406 The following database table is missing: <insert_0>.

Severity: 10 : Warning

Explanation: Take corrective action and re-try the operation.

BIP7407 Publish/Subscribe subscriptions recovery started. Found <insert_0> subscriptions.

Severity: 0 : Information

Explanation: The Publish/Subscribe broker is recovering subscriptions from the broker’s database.

Response: This message is for information only. There should be a matching message to indicate that recovery is

complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.

BIP7000 to BIP7999 (Publish Subscribe) 381

BIP7408 The broker is being run using Java version <insert_0>, not the version it was shipped with.

Severity: 10 : Warning

Explanation: The broker is running a version of Java it was not shipped with. This may result in unexpected

behavior.

Response: Check that the broker profile has been run before starting the broker and insure that the library path

contains the broker JRE lib directories.

BIP7409 The broker was unable to create a JVM. The return code indicates that an unrecognized option was

passed in to it. The broker may be being run with a different level of Java than it was shipped with.

Severity: 30 : Severe error

Explanation: The creation of the broker JVM failed with a return code indicating that an argument was not

recognized. It is likely that this has been cause by the broker trying to run a different level of Java than it was

shipped with.

Response: Check that the broker profile has been run before starting the broker and insure that the library path

contains the broker JRE lib directories.

BIP7410 Publish/Subscribe subscriptions recovery. Recovered <insert_0> subscriptions.

Severity: 0 : Information

Explanation: The Publish/Subscribe broker is recovering subscriptions from the broker’s database.

Response: This message is for information only. There should be a matching message to indicate that recovery is

complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.

382 Diagnostic messages

BIP8000 to BIP8999 (Commands)

BIP8001 Unknown flag <insert_0> selected.

Severity: 20 : Error

Explanation: When using this command interface the user should only select the supported flags.

Response: Correct and reissue the command.

BIP8002 Selected flag <insert_0> badly formed.

Severity: 20 : Error

Explanation: Command flag should be properly specified.

Response: Correct and reissue the command.

BIP8003 Duplicate flag detected.

Severity: 20 : Error

Explanation: A flag was selected more than once.

Response: Correct and reissue the command.

BIP8004 Invalid argument <insert_0> specified.

Severity: 20 : Error

Explanation: Argument specified should be well formed.

Response: Correct and reissue the command.

BIP8005 Flag or argument <insert_0> missing.

Severity: 20 : Error

Explanation: The command will result in no action being taken, a required flag or a flag’s argument is missing.

Response: Correct and reissue the command.

BIP8006 Flag missing. One of the flags in list (<insert_0>) must be specified.

Severity: 20 : Error

Explanation: When using this command interface the user should select all required flags.

Response: Correct and reissue the command.

BIP8007 Mandatory argument missing.

Severity: 20 : Error

Explanation: When using this command interface the user should supply the mandatory argument.

Response: Correct and reissue the command.

BIP8008 Unable to create the Java environment.

Severity: 20 : Error

Explanation: The Java environment could not be created.

Response: Ensure that the Java CLASSPATH variable is correct and ensure that the Java runtime executable (JRE)

shipped with the product is in its correct directory.

BIP8009 Program name incorrect.

Severity: 20 : Error

Explanation: Ensure that the program name (executable) has not been modified.

Response: Correct and reissue the command.

BIP8010 No component name supplied.

Severity: 20 : Error

Explanation: This command requires a component name to be supplied.

Response: Correct and reissue the command.

BIP8011 Unable to create the components configuration data.

Severity: 20 : Error

Explanation: The command is unable to store the component’s configuration data.

Response: Ensure that the userid that is running this command has adequate authority to update the configuration

or registry files. Without this authority the registry or configuration files cannot be updated. Also check that the

broker name does not contain invalid characters or is too long.

BIP8012 Unable to connect to system components.

Severity: 20 : Error

Explanation: This command was unable to connect to required system services.

Response: Check your system log for failure information. Ensure that the user name used to issue this command

has the required permissions to modify NT services. Reissue the command when this has been resolved.

BIP8013 Component does not exist.

Severity: 20 : Error

Explanation: A component may only be used if it has first been created.

Response: No user action required.

BIP8014 Component could not be created.

Severity: 10 : Warning

Explanation: Unable to create the component, the required resources were unavailable.

Response: Investigate the reasons for the failure, ensure that the userid permissions are correct and that there are

sufficient system resources available. Contact your IBM support center if you are unable to resolve the problem.

BIP8015 The component cannot be started.

Severity: 20 : Error

Explanation: The command could not start the required component.

Response: Trace the command and investigate the reasons for this failure, insufficient userid permissions or lack of

system resources may cause this problem. If you are unable to resolve the problem, contact your IBM support center.

384 Diagnostic messages

BIP8016 Unable to stop component.

Severity: 20 : Error

Explanation: A request to stop this component was refused.

Response: Investigate the reason for this failure and reissue the command. The problem may be that the component

was in the process of being stopped or started, in this case just reissue the command. It may be that the command

could not be issued because of insufficient userid permissions. If you are unable to resolve the problem, contact your

IBM support center.

BIP8017 The component could not be deleted.

Severity: 20 : Error

Explanation: Ensure that the component is in a valid state to be deleted.

Response: Make sure that the component is stopped and reissue the command. Check your system log for failures.

If you are unable to resolve the problem contact your IBM support center.

BIP8018 Component running.

Severity: 20 : Error

Explanation: This component is running, the command issued cannot be run against a running component.

Response: Stop the component and reissue the command.

BIP8019 Component stopped.

Severity: 20 : Error

Explanation: A previous command was issued to stop this component or it has never been started.

Response: This component may be started, changed or deleted.

BIP8020 Unable to access the broker’s database tables.

Severity: 20 : Error

Explanation: This command interacts with the broker’s database tables using the database userid selected for this

component.

Response: Ensure that the database is running, that all broker tables are available and that the database userid

provided for this broker or Configuration Manager still has the permissions to modify the database tables.

BIP8021 Ensure that the userid and/or password supplied are correct.

Severity: 20 : Error

Explanation: Ensure that the password is valid and that the userid is defined. Ensure that the service does not

interact with the desktop.

Response: Correct and reissue the command.

BIP8022 Invalid service userid and password combination supplied.

Severity: 20 : Error

Explanation: The userid/password pair are not correct.

Response: Correct and reissue the command.

BIP8000 to BIP8999 (Commands) 385

BIP8023 A valid password must be supplied.

Severity: 20 : Error

Explanation: When a userid is altered, a valid password must also be supplied. If you supply a password it must

contain at least two characters.

Response: Correct and reissue the command.

BIP8024 Unable to locate the component’s executable.

Severity: 20 : Error

Explanation: The component’s executable is not in the expected directory.

Response: Ensure that the product has not been moved from its installation directory. Check that executable

’bipservice’ is in the product’s ’bin’ directory.

BIP8025 Component disabled.

Severity: 20 : Error

Explanation: The component should not be in a disabled state. The component could not be started.

Response: Investigate why the component is disabled and correct the problem, on Windows NT this may be

because the component’s service was ’disabled’.

BIP8026 Unable to start the component.

Severity: 20 : Error

Explanation: The component could not be started using the service userid that was supplied when the component

was created.

Response: Ensure that the service userid and password are still valid. Ensure that the service userid has permission

to access all of the products directories, specifically the ’bin’ and ’log’ directories. Check for system messages (on

Windows NT this would be the application event log).

BIP8027 Unable to start WebSphere.

Severity: 20 : Error

Explanation: WebSphere Message Brokers requires that WebSphere is installed and its service is available.

Response: On NT the WebSphere service must be available before the WebSphere Message Brokers component can

be started. The WebSphere service was unable to start, correct the problem and reissue this command.

BIP8028 Required product unavailable.

Severity: 20 : Error

Explanation: WebSphere Message Brokers requires that WebSphere is installed and that its service

’WebSphereServices’ is available.

Response: Ensure that WebSphere is installed.

BIP8029 The broker’s configuration is not yet deployed.

Severity: 20 : Error

Explanation: This command results in an internal configuration message to the broker, this message may only be

sent after at least one deployment to the broker from the Message Brokers Toolkit.

Response: Reissue the command after the broker’s configuration has been deployed.

386 Diagnostic messages

BIP8030 Unable to modify userid privileges.

Severity: 20 : Error

Explanation: On NT this command modifies a userid’s privileges, (’logon as service’).

Response: Ensure that the userid issuing this command has sufficient privileges to modify the privileges of the

userid supplied in the command. Ensure that a Domain Controller, either Primary or Backup, is available. Re-execute

the command. If the problem persists then please contact your IBM support center.

BIP8031 Invalid flag argument supplied.

Severity: 20 : Error

Explanation: Ensure that the correct flag arguments are selected.

Response: Correct and reissue the command.

BIP8032 Unable to connect to a WebSphere MQ queue.

Severity: 20 : Error

Explanation: An attempt was made to connect to the component’s WebSphere MQ Queue Manager and queue, this

attempt was unsuccessful.

Response: Ensure that the components WebSphere MQ Queue Manager and queue are available, running and that

the user has sufficient authority to access them.

BIP8033 Unable to send an internal configuration message to the broker.

Severity: 20 : Error

Explanation: This command was unable to send an internal configuration message to the broker using WebSphere

MQ.

Response: Ensure that WebSphere MQ is installed and that the broker and its Queue Manager are running.

BIP8034 An internal configuration response message not received.

Severity: 20 : Error

Explanation: This command sends an internal configuration message to the broker, a internal configuration response

message was not received from that broker.

Response: Ensure that the broker and its WebSphere MQ Queue Manager are running.

BIP8035 An internal configuration response message was expected from the broker but was not received

within its 1 hour timeout or the internal configuration message was rejected as an invalid message.

Severity: 20 : Error

Explanation: This command sends an internal configuration message to the broker, it has a predefined 1 hour

timeout, if a request exceeds this time then the command is terminated. The internal configuration messages may

also be rejected if their format is incorrect.

Response: Investigate why the internal configuration response message was not received within this period. Check

the system log messages and ensure that your WebSphere MQ channels and listeners are active and that the broker

or User Name Server is active. Contact your IBM support center if you are unable to resolve this problem.

BIP8036 Negative response received.

Severity: 20 : Error

Explanation: This command sends an internal configuration message to the broker, the response received indicated

that the internal configuration message was unsuccessful.

Response: Check that the WebSphere MQ transport is available. Check the system log for further information.

BIP8000 to BIP8999 (Commands) 387

BIP8037 Unsupported flag. The flags listed in (<insert_0>) are not supported.

Severity: 20 : Error

Explanation: When using this command interface the user should only select from the set of supported flags.

Response: Check the list of supported flags, correct and then reissue the command.

BIP8038 An invalid combination of options was selected.

Severity: 20 : Error

Explanation: The command specified represents an invalid combination of options and parameters.

Response: Refer to the WebSphere Message Brokers online documentation for the list of valid options for this

command. Correct and reissue the command.

BIP8039 The execution group is not available.

Severity: 20 : Error

Explanation: The execution group could not be found; it may have been deleted by the Message Brokers Toolkit or

Config Manager Proxy application.

Response: Use the Message Brokers Toolkit or Config Manager Proxy to see if the execution group exists.

BIP8040 Unable to connect to the database.

Severity: 20 : Error

Explanation: The database cannot be accessed with the userid and password that were specified with the broker.

Response: - Check that the database is running.

- On Windows check that an ODBC connection has been created.

- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.

- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker

command are capable of being used to connect to the database using an ODBC connection.

- Check that the database has a adequate number of database connections available for use.

BIP8041 Unable to open the selected file <insert_0>.

Severity: 20 : Error

Explanation: The file selected could not be opened for read or write.

Response: Ensure that, if specified as input, the file exists and not also for output; and that the file path is valid in

any cases. Also ensure that the file is not locked by another user.

BIP8042 Insufficient memory.

Severity: 20 : Error

Explanation: This command requires a significant amount of memory.

Response: Ensure that there is enough memory available to execute the command.

BIP8043 File selected was not a broker trace file.

Severity: 20 : Error

Explanation: Broker trace files have an XML tag indicating that they are trace files.

Response: Repeat the trace extraction and reissue the command.

388 Diagnostic messages

BIP8044 Unable to get the message text for WBIMB command response <insert_0>.

Severity: 20 : Error

Explanation: A response was generated for which there is no message available. This is an internal error and should

be reported to IBM together with a trace of the command that caused this message to be issued.

Response: Contact your IBM support center.

BIP8045 The message flow is not available.

Severity: 20 : Error

Explanation: The message flow could not be found; it may have been deleted by the Message Brokers Toolkit or a

Config Manager Proxy application.

Response: Use the Message Brokers Toolkit or Config Manager Proxy to see if the message flow exists.

BIP8046 Unable to initialize parser data, exception caught <insert_0>.

Severity: 20 : Error

Explanation: The command initializes parser functions prior to analyzing XML data, this parser cannot be

initialized. Use the line number and column number (inserts 2 and 3 in the exception), to locate the XML causing the

problem.

Response: Contact your IBM support center.

BIP8047 Unable to parse the data received, exception caught <insert_0>.

Severity: 20 : Error

Explanation: The command uses parser functions to analyze XML data, the parser has detected an error in the

format of the XML data being parsed. Use the line number and column number to locate the XML causing the

problem.

Response: Check that the data being parsed is correctly formatted. The command may produce partial output. It

may also be possible to modify the XML data that the command is parsing so that the error does not occur.

BIP8048 Unable to start WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to start a WebSphere MQ Queue Manager. The Queue Manager could not be

started.

Response: Check your system log for failure information. Ensure that the user name used to issue this command

has the required permissions to start the WebSphere MQ Queue Manager. Check that you have an appropriate

installation of WebSphere MQ to support a WebSphere Message Broker component. Please see the ″Diagnosing

errors″ section in the Information Center for more information.

BIP8049 Unable to stop WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to stop a WebSphere MQ Queue Manager. The Queue Manager could not be

stopped.

Response: Locate and resolve the problem and retry the command.

BIP8050 Unable to create WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to create a WebSphere MQ Queue Manager. The Queue Manager could not be

created.

BIP8000 to BIP8999 (Commands) 389

Response: Locate and resolve the problem and retry the command.

BIP8051 Unable to create WebSphere MQ Queue <insert_0> on Queue Manager <insert_1>.

Severity: 20 : Error

Explanation: This command attempts to create a WebSphere MQ Queue but was unable to do so.

Response: Locate and resolve the problem and retry the command.

BIP8052 Unable to delete WebSphere MQ Object <insert_0> from Queue Manager <insert_1>.

Severity: 20 : Error

Explanation: This command attempts to delete a WebSphere MQ Object but was unable to do so.

Response: Locate and resolve the problem and retry the command. This could be because a WebSphere MQ channel

is still running. If this is the case, stop all WebSphere MQ channels running on behalf of this Queue Manager. If your

Message Brokers Toolkit is connected to your configuration manager, you may need to disconnect it as well.

BIP8053 Unable to set the security attributes for WebSphere Queue Manager <insert_0>, Group <insert_1>.

Severity: 20 : Error

Explanation: This command attempts to set the Group security attributes for a WebSphere Queue Manager.

Response: Ensure that the required Group is available and that the user issuing this command is a member of the

mqm group.

BIP8054 Unable to set the security attributes for WebSphere Queue <insert_0> on Queue Manager <insert_1>,

Group <insert_2>.

Severity: 20 : Error

Explanation: This command attempts to set the Group security attributes for a WebSphere Queue.

Response: Ensure that the required Group is available and that the user issuing this command is a member of the

mqm group.

BIP8055 Unable to load a Java class or method <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to use a Java class or method, but was unable to run the class or method.

Response: Ensure that the required Java archives (jar files) are in the broker’s classes directory.

BIP8056 The component’s WebSphere MQ Queue Manager <insert_0> does not exist.

Severity: 20 : Error

Explanation: The command cannot be executed because the Queue Manager associated with this component does

not exist.

Response: Recover the queue manager or delete and then recreate the component. If the component is a

Configuration Manager, you should be careful NOT to delete its database tables.

BIP8057 The command has failed because of an unexpected Queue Manager error.

Severity: 20 : Error

Explanation: During execution of the command an unexpected response has been returned from an MQI call.

Response: A message containing further details of the failure will have been issued to your system log. Consult this

message for problem resolution.

390 Diagnostic messages

BIP8058 A command has failed because of an unexpected WebSphere MQ failure. A <insert_0> request

against object <insert_1> has failed with reason code <insert_2>.

Severity: 20 : Error

Explanation: A command has been issued but during execution of the command an unexpected WebSphere MQ

failure was returned from MQI call <insert_1>.

Response: Using reason code <insert_2>, consult the WebSphere MQ Application Programming Reference manual to

establish the cause of the failure. Take appropriate action to correct the problem before reissuing the command.

BIP8059 Command has failed because the component’s Queue Manager is not available.

Severity: 20 : Error

Explanation: The command has failed because the Queue Manager associated with the component is currently

unavailable.

Response: Reissue the command after the queue manager has been restarted.

BIP8060 Command has failed because of problem with queue

SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub and mqsiclearmqpubsub commands send their requests to the broker on queue

SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS. The request has not been sent because a problem has been

detected with the queue.

Response: First check whether the queue exists or not. If not, consult the WebSphere Message Brokers Introduction

and Planning guide for more information about how the queue needs to be defined. After the queue has been

defined you will need to stop and restart the broker before it will start to receive messages on this queue. If the

queue already existed then stop and restart the broker before reissuing the command. If the command still fails with

this error, check that the broker is not waiting for migration to complete. If this is the case, message BIP7283 will

have been issued when the broker was last started.

BIP8061 Broker has failed to reply to command.

Severity: 20 : Error

Explanation: The request has been sent to the broker but no reply message has been received. The command may or

may not have been successful.

Response: Investigate why the broker failed to respond to the request. If the broker has terminated, restart it and

reissue the command.

BIP8062 Join request has failed because parent broker is already a neighbor.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub command has failed because the named parent broker is already a neighbor.

Response: If a previous attempt to join the two brokers using the mqsijoinmqpubsub command has failed then it

may be necessary to use mqsiclearmqpubsub first before reissuing the command.

BIP8063 Clear request has failed because specified broker is not a neighbor.

Severity: 20 : Error

Explanation: The mqsiclearmqpubsub command has failed because the named broker was not a neighbor.

Response: Reissue the command specifying a broker which is a neighbor.

BIP8000 to BIP8999 (Commands) 391

BIP8064 Command has failed because of an internal component error

Severity: 20 : Error

Explanation: The command has failed because of an internal error at the component.

Response: A message containing the further details of the failure will have been issued to the system log. Consult

this message for problem resolution.

BIP8065 Join request has failed because broker already has a parent.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub command has failed because the message broker already has a parent

WebSphere Publish/Subscribe broker.

Response: Remove the existing parent broker before reissuing the command.

BIP8066 Request has failed because an invalid broker name was specified.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub or mqsiclearmqpubsub command has failed because the WebSphere

Publish/Subscribe broker name supplied was invalid.

Response: Reissue the command with a valid WebSphere Publish/Subscribe broker name.

BIP8067 Request has failed because couldn’t contact the parent WebSphere publish/subscribe broker.

Severity: 20 : Error

Explanation: The mqsijoinmqpubsub command has failed because the supplied WebSphere publish/subscribe

broker could not be contacted.

Response: A message containing further details of the failure will have been issued to the system log. The problem

is likely to be caused by the parent broker name not resolving to the name of a transmission queue at the queue

manager which is hosting the WebSphere Message Brokers broker. Correct the underlying problem with the

WebSphere network and reissue the command.

BIP8068 Argument <insert_0> is not a valid integer value for this flag.

Severity: 20 : Error

Explanation: Ensure that the argument used is a valid integer and in the allowable range.

Response: Correct and reissue the command.

BIP8069 Unable to find message <insert_0> in message catalog <insert_1>.

Severity: 20 : Error

Explanation: A message could not be found in the message catalog specified.

Response: Ensure that the message is available in the message catalog and that the catalog is in the product

message directory.

BIP8070 Exception accessing database table executing SQL statement <insert_0>: SQL state <insert_1>;

exception <insert_2>.

Severity: 20 : Error

Explanation: An SQL command has failed.

Response: Ensure that the broker’s database is available. Examine the exception and SQL state code to determine

and correct the cause of the error.

392 Diagnostic messages

BIP8071 Successful command completion.

Severity: 0 : Information

BIP8072 Exception accessing a database table, executing SQL statement <insert_0>: exception <insert_1>.

Severity: 20 : Error

Explanation: An SQL command has failed.

Response: Ensure that the database is available, examine the exception to determine and correct the cause of the

error.

BIP8073 <insert_0> is not a valid component.

Severity: 20 : Error

Explanation: The name selected is not a valid component.

Response: Select a different component.

BIP8074 Unable to create a JVM.

Severity: 20 : Error

Explanation: A Java Virtual Machine could not be created.

Response: Ensure that the Java CLASSPATH variable is correct and that it is not too large, ensure that the Java

runtime executable (JRE) shipped with the product is in its correct directory.

BIP8075 A Java exception was caught from class <insert_0>. The text is <insert_1>.

Severity: 20 : Error

Explanation: A Java exception was caught via the JNI.

Response: Check preceding messages for related errors and retry the operation. If the exception still occurs, contact

your IBM support center.

BIP8076 Current working directory could not be set to <insert_0>.

Severity: 20 : Error

Explanation: An error has occurred while the command was running. The command has cleaned up and

terminated.

Response: Investigate why the directory <insert_0> can’t be accessed, correct the problem and retry the command. If

the problem still occurs, contact your IBM support center.

BIP8077 A problem was encountered while attempting to create/delete the Configuration Manager.

Severity: 20 : Error

Explanation: The operation was not completed successfully. An internal error generated an invalid return code of

<insert_0>.

Response: Check messages in the system log for related errors and retry the operation. If the problem still occurs

contact your IBM support center.

BIP8078 A problem was encountered while attempting to create/delete the Configuration Manager.

Severity: 20 : Error

Explanation: The operation was not completed successfully.

Response: Check messages in the system log for related errors and retry the operation. If the problem still occurs,

contact your IBM support center.

BIP8000 to BIP8999 (Commands) 393

BIP8079 Unable to find service user id <insert_0>.

Severity: 20 : Error

Explanation: This user ID is not defined to the operating system, so it cannot be used as a component service user

ID.

Response: Create the user ID and reissue the command, or specify a user ID which exists on this system.

BIP8080 Unable to initialize a parser factory.

Severity: 20 : Error

Explanation: The command executable detected an error whilst initializing its parser factory.

Response: Contact your IBM support center.

BIP8081 An error occurred while processing the command.

Severity: 20 : Error

Explanation: An error has occurred while the command was running. The command has cleaned up and

terminated.

Response: Use messages prior to this one to determine the cause of the error. Correct the problem and retry the

command. Check for some common problems :- Does the user id have the correct authorities (for example a member

of the mqbrkrs group)? Is the broker database started and operating correctly? Is any operating system limit set too

low to allow the command to run? Is the environment correctly set up? Contact your IBM support center if you are

unable to resolve the problem.

BIP8082 Unable to delete WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to delete an WebSphere MQ Queue Manager, but the Queue Manager could

not be deleted.

Response: This could be because an WebSphere MQ channel or WebSphere MQ Listener is still running. Stop all

WebSphere MQ channels and WebSphere MQ Listeners running for this Queue Manager and retry the command.

BIP8083 The component name supplied contains invalid characters.

Severity: 20 : Error

Explanation: This command requires that the component name is made up of a set of characters supported by the

platform on which the command is being executed.

Response: Correct and reissue the command.

BIP8084 Unable to create directory <insert_0>, return code <insert_1>.

Severity: 20 : Error

Explanation: The specified directory could not be created. Ensure that the characters are valid, that you have the

required permissions and that the parent directory exists.

Response: Correct and reissue the command.

BIP8085 The environment variable <insert_0> is not defined.

Severity: 20 : Error

Explanation: An attempt to read an environment variable was unsuccessful.

Response: Ensure the environment variable is defined.

394 Diagnostic messages

BIP8086 WebSphere MQ Queue Manager <insert_0> is already reserved for use by component <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to use a WebSphere MQ Queue Manager that was already reserved for use by

another component. It is acceptable for a broker, User Name Server and Configuration Manager to all share a single

WebSphere MQ Queue Manager. It is not acceptable for multiple components of the same type (brokers, User Name

Servers, or Configuration Managers) to share a single WebSphere MQ Queue Manager.

Response: Choose another WebSphere MQ Queue Manager and reissue the command.

BIP8087 <insert_0> already exists and cannot be created.

Severity: 20 : Error

Explanation: An attempt was made to create a component that already exists.

Response: Ensure that the component name you have selected for creation is the correct one, and investigate the

reasons why this component name already exists. Additionally, if you are running on a Windows platform and

mqsilist does not report the existence of the component the component’s service may still be running. This may be

because of a previous delete failed to complete and left the component’s service running (this can be caused by an

open Administrative Tools - Services window, which prevents the deletion being completed.) If the component’s

service still exists try deleting the component after resolving any relevant issues and retry this create command.

BIP8088 There are no WebSphere Publish/Subscribe neighbors.

Severity: 0 : Information

BIP8089 WebSphere Publish/Subscribe neighbor <insert_0> is inactive.

Severity: 0 : Information

BIP8090 WebSphere Publish/Subscribe neighbor <insert_0> is active.

Severity: 0 : Information

BIP8091 Common stream <insert_0>.

Severity: 0 : Information

BIP8092 Unable to locate WebSphere Message Brokers response <insert_0> in message catalog <insert_1>.

Severity: 20 : Error

Explanation: The WebSphere Message Brokers response could not be found in the message catalog.

Response: Make sure that the message catalog is available and that the WebSphere Message Brokers response is in

the message catalog. If the problem persists contact your IBM support center.

BIP8093 Unable to access the WebSphere MQ Queue Manager.

Severity: 20 : Error

Explanation: The WebSphere MQ Queue Manager is currently being created by another user.

Response: Wait until the Queue Manager has been created, then reissue this command.

BIP8094 Unable to access the WebSphere MQ Queue Manager.

Severity: 20 : Error

Explanation: The WebSphere MQ Queue Manager is currently being stopped by another user.

Response: Wait until the stop has completed and reissue this command.

BIP8000 to BIP8999 (Commands) 395

BIP8095 WebSphere queue manager <insert_0> is reserved for use by WebSphere Message Brokers

component <insert_1>.

Severity: 20 : Error

Explanation: An attempt was made to delete an WebSphere queue manager that was being shared by another

WebSphere Message Brokers component.

Response: It is acceptable for a broker, User Name Server and Configuration Manager to all share a single

WebSphere queue manager. The ’WebSphere queue manager delete’ option provided by this command may only be

selected if there are no other WebSphere Message Brokers components currently configured to share this WebSphere

queue manager.

BIP8096 Successful command initiation, check the system log to ensure that the component started without

problem and that it continues to run without problem.

Severity: 0 : Information

BIP8097 Unable to instantiate Java object of class <insert_0>.

Severity: 20 : Error

Explanation: An instance of the Java class could not be instantiated.

Response: This is an internal error, possibly due to a faulty installation. Check messages in the system log for

related errors and retry the operation. If the problem persists, contact your IBM support center.

BIP8098 Trace level: <insert_0>, mode: <insert_1>, size: <insert_2> KB.

Severity: 0 : Information

BIP8099 <insert_0>: <insert_1> - <insert_2>

Severity: 0 : Information

BIP8101 Changes a broker’s configuration.

Syntax:

mqsichangebroker brokerName [[-i serviceUserId] -a servicePassword] [-p dataSourcePassword] [-s

unsQMgrName] [-j | -d] [-t | -n] [-l userLilPath] [-g configurationTimeout] [-k

configurationDelayTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-c ICU converter path]

[-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker to change

’-i serviceUserId’ the userid that the broker should run under

’-a servicePassword’ the password for the broker userid

’-p dataSourcePassword’ the password for the broker’s database userid

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-j’ indicates that publish/subscribe access control is to be enabled for this broker

’-d’ indicates that publish/subscribe access control is to be disabled for this broker

’-t’ indicates WebSphere MQ fastpath is to be used for this broker (not supported on all platforms)

’-n’ indicates WebSphere MQ fastpath is not to be used for this broker

’-l userLilPath’ indicates where user-written ’lil’ and ’jar’ files are loaded from

’-g configurationTimeout’ the maximum time (in seconds) to allow a broker to process a deployed message

’-k configurationDelayTimeout’ the maximum time (in seconds) to allow a broker to process a minimum size

deployed message

’-v statisticsMajorInterval’ the time (in minutes) for the duration of the interval for collecting statistics archive records

’-P httpListenerPort’ the port that the broker’s HTTP listener will use

’-c ICU converter path’ delimited list (’;’ in windows, ’:’ on unix) of paths to search for ICU converters or converter

packages.

’-y ldapPrincipal’ the LDAP Principal (userId)

396 Diagnostic messages

’-z ldapCredentials’ the LDAP Credentials (password)

’-x userExitPath’ the directory from which the broker searches for all user exits. This path will be added to the

system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.

’-e activeUserExits’ the active user exits. By default, user exits are inactive. Adding a userExit name to this list,

changes its default state to active for this broker. The default state can be overridden at the execution group or

message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found

to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and

the execution group will fail to start.

BIP8102 Changes a Configuration Manager’s configuration.

Syntax:

mqsichangeconfigmgr configMgrName [[-i serviceUserId] -a servicePassword] [-s unsQMgrName] [-p

dataBasePassword] [-j maxJVMHeapSize]

Severity: 10 : Warning

Explanation: Command Options:

’configMgrName’ name of the Configuration Manager (may be omitted on Windows)

’-i serviceUserId’ the userid that the Configuration Manager should run under

’-a servicePassword’ the password for the Configuration Manager userid

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-p dataBasePassword’ the password for the DB2 database being migrated

’-j maxJVMHeapSize’ the maximum Java virtual machine heap size, in megabytes (default 256) (minimum 64).

Note: On Windows platforms, if the Configuration Manager name is omitted ’ConfigMgr’ will be used.

BIP8103 Changes a User Name Server’s configuration.

Syntax:

mqsichangeusernameserver [[-i serviceUserId] -a servicePassword] [-d securityDomainName] [-r

refreshInterval] [-g authProtocolDataSource] [-j | -o]

Severity: 10 : Warning

Explanation: Command Options:

’-i serviceUserId’ the userid that the User Name Server should run under

’-a servicePassword’ the password for the User Name Server userid

’-d securityDomainName’ the security domain that the User Name Server will use

’-r refreshInterval’ number of seconds between each refresh of the User Name Server internal cache

’-g authProtocolDataSource’ the name of the data source required by the authentication protocol

’-j’ indicates that groups and group memberships will be defined in the data source for the authentication protocol

(rather than drawn from the Operating System)

’-o’ indicates that groups and group memberships will be drawn from the Operating System (rather than defined in

the data source for the authentication protocol).

BIP8104 Changes a component’s trace options.

Syntax (1):

mqsichangetrace componentName [-u | -t] -e egName [-f messageFlow] [-l level] [-m mode] [-c size]

[-r]

Syntax (2):

mqsichangetrace componentName -t -b [-l level] [-m mode] [-c size]

Severity: 10 : Warning

Explanation: Command Options:

’componentName’ Name of the component whose trace options are to be changed

’-u’ indicates user trace (may only be used with ’-e’)

’-t’ indicates service trace.

’-b’ denotes tracing of a component other than an execution group

’-e egName’ Name of the execution group

’-f messageFlow’ Name of the message flow

’-l level’ specifies the trace level, ’none’, ’normal’ or ’debug’

’-m mode’ specifies the trace mode, ’safe’ or ’fast’

’-c size’ specifies the trace file size in kilobytes

BIP8000 to BIP8999 (Commands) 397

’-r’ specifies that the log should be reset.

Certain conditions apply to these optional parameters. Please check the online documentation for more information.

BIP8105 Creates a broker.

Syntax:

mqsicreatebroker brokerName -i serviceUserId -a servicePassword -q queueManagerName -n

dataSourceName [-u dataSourceUserId] [-p dataSourcePassword] [-s unsQMgrName [-j]] [-g

configurationTimeout] [-k configurationDelayTimeout] [-w workPath] [-l userLilPath] [-t] [-m] [-v

statisticsMajorInterval] [-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z

ldapCredentials] [-x userExitPath]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-i serviceUserId’ the userid that the broker will run under

’-a servicePassword’ the password for the broker userid

’-q queueManagerName’ the WebSphere MQ queue manager that the broker will use. This is created if it does not

exist

’-n dataSourceName’ the broker’s database name

’-u dataSourceUserId’ the userid that the broker uses to access its database

’-p dataSourcePassword’ the password for the broker’s database userid

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-j’ enables publish/subscribe access control for the broker

’-g configurationTimeout’ the maximum time (in seconds) to allow a broker to process a deployed message

’-k configurationDelayTimeout’ the maximum time (in seconds) to allow a broker to process a minimum size

deployed message

’-w workPath’ the directory into which trace logs are placed

’-l userLilPath’ the directory from which the broker searches for user-supplied libraries

’-t’ enables WebSphere MQ fastpath for this broker

’-m’ indicates that migration is required from an WebSphere publish/subscribe broker

’-v statisticsMajorInterval’ the time (in minutes) for the duration of the interval for collecting statistics archive records

’-P httpListenerPort’ the port that the broker HTTP listener will use

’-c icuConverterPath’ delimited list (’;’ in windows, ’:’ on unix) of paths to search for ICU converters or converter

packages.

’-y ldapPrincipal’ the LDAP Principal (userId)

’-z ldapCredentials’ the LDAP Credentials (password)

’-x userExitPath’ the directory from which the broker searches for all user exits. This path will be added to the

system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.

BIP8106 Creates a Configuration Manager.

Syntax:

mqsicreateconfigmgr configMgrName -i serviceUserId -a servicePassword -q queueManagerName

[-n db2DatabaseToMigrate -u migrationDatabaseUserId -p migrationDatabasePassword] [-s

unsQMgrName] [-w workPath]

Severity: 10 : Warning

Explanation: Command Options

’configMgrName’ name of the Configuration Manager (may be omitted on Windows)

’-i serviceUserId’ the userid that the Configuration Manager will run under

’-a servicePassword’ the password for the Configuration Manager userid

’-q queueManagerName’ the WebSphere MQ queue manager that the Configuration Manager will use (this is created

if it does not exist)

’-n db2DatabaseToMigrate’ the name of the DB2 database that contains existing domain data to migrate

’-u migrationDatabaseUserId’ the userid of the DB2 database being migrated

’-p migrationDatabasePassword’ the password of the DB2 database being migrated

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-w workPath’ the directory into which trace logs and the Configuration Manager repository will be placed.

Note: On Windows platforms, if the Configuration Manager name is omitted ’ConfigMgr’ will be used.

398 Diagnostic messages

BIP8107 Creates a User Name Server.

Syntax:

mqsicreateusernameserver -i serviceUserId -a servicePassword -q queueManagerName [-d

securityDomainName] [-r refreshInterval] [-w workPath] [-g authProtocolDataSource] [-j]

Severity: 10 : Warning

Explanation: Command Options:

’-i serviceUserId’ the userid that the User Name Server will run under

’-a servicePassword’ the password for the User Name Server userid

’-q queueManagerName’ the WebSphere MQ queue manager that the User Name Server will use (it will be created if

it does not exist)

’-d securityDomainName’ the Security Domain that the User Name Server will use

’-r refreshInterval’ number of seconds between each refresh of the User Name Server internal cache

’-w workPath’ the directory into which trace logs will be placed

’-g authProtocolDataSource’ the name of the data source required by the authentication protocol

’-j’ indicates that groups and group memberships will be defined in the data source for the authentication protocol

rather than drawn from the Operating System.

BIP8108 Deletes a broker.

Syntax:

mqsideletebroker brokerName [-q] [-w]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ Name of the component to delete

’-q’ deletes the broker’s WebSphere MQ queue manager

’-w’ deletes the broker’s trace files from its work directory.

BIP8109 Deletes a Configuration Manager.

Syntax:

mqsideleteconfigmgr configMgrName [-q] [-w] [-n]

Severity: 10 : Warning

Explanation: Command Options

’configMgrName’ name of the Configuration Manager to delete (may be omitted on Windows)

’-q’ deletes the Configuration Manager’s WebSphere MQ queue manager

’-w’ deletes the Configuration Manager’s trace files from its work directory

’-n’ deletes the Configuration Manager’s repository (use with caution).

Note: On Windows platforms, if the Configuration Manager name is omitted ’ConfigMgr’ will be used.

BIP8110 Deletes the User Name Server.

Syntax:

mqsideleteusernameserver [-q] [-w]

Severity: 10 : Warning

Explanation: Command Options:

’-q’ deletes the User Name Server’s WebSphere MQ queue manager.

’-w’ deletes the User Name Server’s trace files from its work directory.

BIP8111 Formats the trace log retrieved using mqsireadlog.

Syntax:

mqsiformatlog -i inputFileName [-o outputFileName]

Severity: 10 : Warning

Explanation: Command Options:

’-i inputFileName’ the file name of a trace log that requires formatting

’-o outputFileName’ the file name to write the formatted trace log (default=stdout).

BIP8000 to BIP8999 (Commands) 399

BIP8112 Joins a broker with a neighboring WebSphere publish/subscribe broker.

Syntax:

mqsijoinmqpubsub brokerName -p qMgrName

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker to modify

’-p qMgrName’ the WebSphere MQ queue manager of the broker to be joined with.

BIP8113 Lists the components that have been created and their WebSphere MQ queue managers.

Syntax:

mqsilist [-a] [brokerName [-e egName]]

Severity: 10 : Warning

Explanation: Command Options:

’-a’ lists all components on this machine.

’brokerName’ lists execution groups configured for a broker

’-e egName’ lists message flows configured for an execution group.

BIP8114 Retrieves the trace log.

Syntax (1):

mqsireadlog componentName (-u | -t) -e executionGroupName [-f] [-o outputFileName]

Syntax (2):

mqsireadlog componentName -t -b subcomponent -f [-o outputFileName]

Severity: 10 : Warning

Explanation: Command Options:

’-u’ indicates user trace (may only be used with ’-e’)

’-t’ indicates service trace

’-b subcomponent’ name of the command or subcomponent (for example, ’agent’)

’-e executionGroupName’ Name of the execution group

’-f’ specifies that the log file is to be read directly from the file system (this flag is mandatory for service trace)

’-o outputFileName’ file name to write the trace log.

BIP8115 Displays trace settings.

Syntax (1):

mqsireporttrace componentName (-u | -t) -e executionGroupName [-f messageFlow]

Syntax (2):

mqsireporttrace componentName -t -b

Severity: 10 : Warning

Explanation: Command Options

’-u’ indicates user trace (may only be used with ’-e’)

’-t’ indicates service trace

’-b’ used for components other than execution groups

’-e executionGroupName’ execution group name

’-f messageFlow’ message flow name.

BIP8116 Starts a component.

Syntax:

mqsistart componentName

Severity: 10 : Warning

Explanation: Command Options:

’componentName’ broker name, Configuration Manager name or ’UserNameServer’.

400 Diagnostic messages

BIP8117 Stops a component.

Syntax:

mqsistop componentName [-q] [-i]

Severity: 10 : Warning

Explanation: Command Options:

’componentName’ broker name, Configuration Manager name or ’UserNameServer’

’-q’ stops the WebSphere MQ queue manager used by the component

’-i’ forces the broker to stop immediately (use with caution).

BIP8118 Removes knowledge of a neighboring WebSphere publish/subscribe broker.

Syntax:

mqsiclearmqpubsub brokerName -n neighboringQMgrName

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ Broker to modify

’-n neighboringQMgrName’ the queue manager name of the WebSphere publish/subscribe broker.

BIP8119 Displays neighboring WebSphere Publish/Subscribe brokers.

Syntax:

mqsilistmqpubsub brokerName

Severity: 10 : Warning

Explanation: Command options:

’brokerName’ Name of the broker whose neighbors are to be displayed.

BIP8120 Migrates broker database tables.

Syntax:

migratetables

Severity: 10 : Warning

BIP8121 Lists the contents of a components persistent store.

Syntax:

mqsibrowse componentName -t persistentStoreTable

Severity: 10 : Warning

Explanation: Command Options:

’componentName’ Name of the component to browse

’-t persistentStoreTable’ the persistent store table to browse.

BIP8122 Displays broker property settings.

Syntax:

mqsireportproperties brokerName ( -e executionGroupName | -b httplistener | -c externalResource )

-o object [-n attribute | -a | -r]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-e executionGroupName’ name of the execution group

’-b httplistener’ report properties for the HTTP Listener component

’-c externalResource’ report properties for an external resource used by the Broker. Use AllTypes for a list of all

resource types

’-o object’ object name to report on. Use AllReportableEntityNames for a list of allowable object names

’-n attribute’ display the value of the attribute with this name

’-a’ display all attribute values (non-recursive)

’-r’ display all attribute values (recursive).

BIP8000 to BIP8999 (Commands) 401

BIP8123 This command changes broker property values.

Syntax:

mqsichangeproperties brokerName ( -e executionGroupName | -b httplistener | -c

configurableService ) -o object -n name -v value

Severity: 10 : Warning

Explanation: Command options:

’brokerName’: name of the broker

’-e executionGroupName’: execution group name

’-b httplistener’: change properties for the HTTP Listener component

’-c configurableService’: change properties for a configurable service used by the broker

’-o object’: object name

’-n name’: attribute name

’-v value’: attribute value

BIP8124 Changes and reports a component’s details.

Syntax:

mqsiservice [-v] [componentName [-r label=value]] [-m messageNumber [-c messageCatalog]] [-t]

Severity: 10 : Warning

Explanation: Command Options:

’-v’ is the product version information

’componentName’ is the name of the component to query for its registry data

’-r label=value’ sets the registry key ’label’ to ’value’. Use with caution.

’-r label=’ sets the registry key ’label’ to null. Use with caution.

’-r label’ deletes the registry key ’label’. Use with caution.

’-m messageNumber’ is a message number to output.

’-c messageCatalog’ is the name of the message catalog to use.

’-t’ Output information about current time and timezone

BIP8125 Exports or Imports a message set from or into a repository.

Syntax (1):

mqsiimpexpmsgset -e -n mrmDataSourceName -u mrmDataSourceUserId -p

mrmDataSourcePassword -s sourceMessageSetName -l sourceMessageSetLevel -f fileName

Syntax (2):

mqsiimpexpmsgset -i -n mrmDataSourceName -u mrmDataSourceUserId -p

mrmDataSourcePassword -f fileName

Severity: 10 : Warning

Explanation: Command Options

’-e’ exports a message set.

’-i’ imports a message set.

’-n mrmDataSourceName’ the component’s database name.

’-u mrmDataSourceUserId’ the userid that the component uses to access the database.

’-p mrmDataSourcePassword’ the password that the component uses to access its database

’-s sourceMessageSetName’ the message set being exported or imported

’-l sourceMessageSetLevel’ the level of the message set

’-f fileName’ the file being imported, or the file being exported.

BIP8126 Creates a new message set as a copy of an existing message set within a repository.

Syntax:

mqsicopymsgset -n mrmDataSourceName -u mrmDataSourceUserId -p mrmDataSourcePassword -s

sourceMessageSetName -l sourceMessageSetLevel -t targetMessageSetName -k

targetMessageSetLevel

Severity: 10 : Warning

Explanation: Command Options

’-n mrmDataSourceName’ the component’s database name

’-u mrmDataSourceUserId’ the userid that the component uses to access the database

402 Diagnostic messages

’-p mrmDataSourcePassword’ the password that the component uses to access its database

’-s sourceMessageSetName’ the message set being copied

’-l sourceMessageSetLevel’ the level of the message set being copied

’-t targetMessageSetName’ the name of the target message set

’-k targetMessageSetLevel’ the target message set level.

BIP8127 Checks the contents of a broker’s subscriptions table looking for CBR filters that include string

literals with escape characters.

Syntax:

mqsicbrreport brokerName

Severity: 10 : Warning

Explanation: Command Options

’brokerName’ Name of the broker.

BIP8128 Reloads a broker’s execution groups.

Syntax:

mqsireload brokerName [-e egName]

Severity: 0 : Information

Explanation: Command Options:

’brokerName’ Broker name

’-e egName’ Execution group name to reload.

BIP8129 Sets the username and password to be used in a compute node in the broker.

Syntax (1):

mqsisetdbparms brokerName -n dataSourceName [-u dataSourceUserId] -p dataSourcePassword

Syntax (2):

mqsisetdbparms brokerName -n dataSourceName -d

Severity: 10 : Warning

Explanation: Command Options

’brokerName’ the broker name

’-n dataSourceName’ the database name

’-u dataSourceUserId’ the userid used to access the database

’-p dataSourcePassword’ the password used to access its database

’-d’ delete the database userid and password information.

BIP8130 Execution Group: <insert_0> - <insert_1>

Severity: 0 : Information

BIP8131 MessageFlow: <insert_0>

Severity: 0 : Information

BIP8132 <insert_0> is not a valid subcomponent name.

Severity: 20 : Error

Explanation: The name selected is not a valid subcomponent.

Response: The name selected is not supported. Select a different subcomponent name.

BIP8133 Unable to write to the selected output file <insert_0>

Severity: 20 : Error

Explanation: The file selected could not be written to.

Response: Ensure that the file selected is not in a protected directory, that it is not read-only and that it is not being

BIP8000 to BIP8999 (Commands) 403

used or locked by another user. Also check that the directory into which the file will be written has adequate free

space.

BIP8134 Unable to alter WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be

altered.

Response: Locate and resolve the problem and retry the command.

BIP8135 Unable to create files: operating system return code <insert_0>.

Severity: 20 : Error

Explanation: An error occurred creating files in response to a command. This may be because the user does not

have the required authorization.

Response: Check that the user has the required authority to create files and retry.

BIP8136 Unable to change the ownership of files: operating system return code <insert_0>.

Severity: 20 : Error

Explanation: An error occurred changing the ownership of files in response to a command. This may be because the

user does not have the required authorization.

Response: Check that the user has the required authority to create files and retry.

BIP8137 Unable to change the access permission mode of file <insert_0> : operating system return code

<insert_1>.

Severity: 20 : Error

Explanation: An error occurred while changing the access permissions for the specified file. This may be because

the user does not have the required authorization to carry out this action.

Response: Check that the user has the required authority to create and modify files. Retry the operation.

BIP8138 Userid <insert_0> cannot be used by this component.

Severity: 20 : Error

Explanation: The userId selected cannot be used by the component. This may be because the userId does not have

the required authorization or that the userId is invalid for operations that the component requires, for example, if a

component is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId ’mqm’.

Response: Check that the user has the required authority to create files and retry.

BIP8139 The user issuing this command does not have the required permissions to complete the command.

Severity: 20 : Error

Explanation: The userId that the command is being run under must have the authority to end broker processes.

Response: Check that the user has the required authority to end the broker’s processes.

BIP8140 Unable to find service userid <insert_0> in component <insert_1>.

Severity: 20 : Error

Explanation: Cannot authenticate service userid in component.

Response: Use mqsichangebroker to alter the service userid and then retry the command.

404 Diagnostic messages

BIP8141 Unauthorized userid <insert_0> in component <insert_1>.

Severity: 20 : Error

Explanation: The service userid is not authorized to run the component.

Response: Use mqsichangebroker to alter the service userid and retry the command.

BIP8142 Unable to set process userid.

Severity: 20 : Error

Explanation: UNIX setuid command had failed.

Response: Verify with your system administrator that file permissions for this command are set correctly.

BIP8143 Unable to change group ownership of directory <insert_1> to <insert_2>. (error <insert_0>)

Severity: 20 : Error

Explanation: Directory <insert_1> is required to have <insert_2> as group owner.

Response: Use a different -w value or consult system administrator for possible causes of this error.

BIP8144 Unable to create directory <insert_0>. (error <insert_1>)

Severity: 20 : Error

Explanation: Directory <insert_0> creation has failed due to directory permission setting.

Response: Use a different -w value or consult system administrator for possible causes of this error.

BIP8145 Execution Group process IDs <insert_0> were forced to terminate.

Severity: 0 : Information

Explanation: The Broker was shutdown forcibly, this caused Execution Group processes to be killed.

Response: This action may leave system, database, WebSphere MQ or Application resources in a locked state. Some

resource locks may need freeing manually, others will not need any action to be taken.

BIP8146 Unable to retrieve the SQL primitives supported by the Database.

Severity: 20 : Error

Explanation: The command attempted to retrieve the SQL primitives that the Database supports, however the

primitives retrieved indicate that the Database could not be contacted successfully. Refer to the Administration Guide

for information about Database setup, ensure that the Database libraries are available in the library path and that the

ODBC ini file is correct.

Response: Correct the problem and retry the command.

BIP8147 Changes a broker’s configuration. Syntax: changebroker [s=unsQMgrName] [l=userLilPath]

[g=configurationTimeout] [k=configurationDelayTimeout] [x=userExitPath] [e=activeUserExits]

Severity: 10 : Warning

Explanation: Command Options:

’s=unsQMgrName’ the WebSphere MQ queue manager of the User Name Server.

’l=userLilPath’ indicates where ’lil’ files are loaded from.

’g=configurationTimeout’ the maximum time (in seconds) to allow a broker to process a deployed message.

’k=configurationDelayTimeout’ the maximum time (in seconds) to allow a broker to process a minimum size

deployed message.

’x=userExitPath’ the directory from which the broker searches for all user exits. This path will be added to the system

library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.

’e=activeUserExits’ the active user exits. By default, user exits are inactive. Adding a userExit name to this list,

BIP8000 to BIP8999 (Commands) 405

changes its default state to active for this broker. The default state can be overridden at the execution group or

message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found

to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and

the execution group will fail to start.

BIP8148 Changes a User Name Server’s configuration. Syntax: changeusernameserver [r=refreshInterval] [-g

authProtocolDataSource] [-j | -o]

Severity: 10 : Warning

Explanation: Command Options

’r=refreshInterval’ number of seconds between each refresh of the User Name Server internal cache

’g=authProtocolDataSource’ the name of the data source required by the authentication protocol

’j=yes’ indicates that groups and group memberships will be defined in the data source for the authentication

protocol (rather than drawn from the Operating System)

’o=yes’ indicates that groups and group memberships will be drawn from the Operating System (rather than defined

in the data source for the authentication protocol)

BIP8149 Changes a component’s trace options. Syntax (1): changetrace (u=yes | t=yes)

,e=executionGroupName [,f=messageFlow] [,l=level] [,m=mode] [,c=size] [,r=yes] Syntax (2):

changetrace t=yes ,b=yes [,l=level] [,m=mode] [,c=size]

Severity: 10 : Warning

Explanation: Command Options

’u=yes’ indicates user trace (only with flag ’e’)

’t=yes’ indicates service trace

’b=yes’ is for components other than execution groups

’e=executionGroupName’ execution group name

’f=messageFlow’ message flow name

’l=level’ specifies the trace level, ’none’, ’normal’ or ’debug’

’m=mode’ specifies the trace mode, ’safe’ or ’fast’

’c=size’ specifies the trace size in kilobytes

’r=yes’ specifies that the log should be reset

Certain conditions apply to these optional parameters. Please check the online documentation for more information.

BIP8150 Displays trace settings. Syntax (1): reporttrace (u=yes | t=yes) ,e=executionGroupName

[,f=messageFlow] Syntax (2): reporttrace t=yes ,b=yes

Severity: 10 : Warning

Explanation: Command Options

’u=yes’ indicates user trace (only with flag ’e’)

’t=yes’ indicates service trace

’b=yes’ is for components other than execution groups

’e=executionGroupName’ execution group name

’f=messageFlow’ message flow name.

BIP8151 Lists the components that have been created and their WebSphere MQ queue managers. Syntax: list

[e=executionGroupName]

Severity: 10 : Warning

Explanation: Command Options

’e=executionGroupName’ requests a list of message flows configured for an execution group.

If the execution group is not specified, this command requests a list of execution groups configured for the broker.

BIP8152 Stops a component. Syntax: stopcomponent

Severity: 10 : Warning

406 Diagnostic messages

BIP8153 Migrated database tables for broker <insert_0>

Severity: 0 : Information

BIP8154 An error occurred while locking the registry file <insert_0> : <insert_1>.

Severity: 20 : Error

Explanation: The program cannot continue, because of an internal error.

Response: Contact your WebSphere Message Brokers administrator.

BIP8155 Migrates database tables for a broker.

Syntax:

mqsimigratetables brokerName [-i serviceUserId] [-a servicePassword]

Severity: 10 : Warning

Explanation: Command options

’brokerName’ name of the broker whose tables are to be migrated

’-i’ the userid that the broker service should run under

’-a’ the password for the broker service userid.

BIP8156 Broker database being migrated is in an inconsistent state

Severity: 20 : Error

Explanation: The Broker database being migrated is in an inconsistent state. ClientId’s referenced in tables can not

be found in the BCLIENTUSER table.

Response: Restore your Broker database tables to a known good state, then try migrating the tables again.

BIP8158 Invalid format for command.

Severity: 20 : Error

Explanation: The string <insert_0> contained no valid formatted command.

Response: Consult the user manual and correct your errors.

BIP8159 Unknown parameter <insert_0>.

Severity: 20 : Error

Explanation: The parameter <insert_0> is not valid for this command.

Response: Check the spelling of the parameter and check if it is valid for this command.

BIP8160 The verb <insert_0> is unknown.

Severity: 20 : Error

Explanation: The verb <insert_0> is not a valid verb.

Response: Consult the user manual and correct your errors.

BIP8161 Start was issued.

Severity: 0 : Information

Explanation: Start was issued and recognized.

Response: Everything was OK.

BIP8000 to BIP8999 (Commands) 407

BIP8162 MVS stop was issued.

Severity: 0 : Information

Explanation: MVS stop was issued and recognized.

Response: Everything was OK.

BIP8163 Missing closing single quote. Opened at <insert_0>.

Severity: 20 : Error

Explanation: You opened a quoted text at <insert_0>, but never closed it.

Response: Check where you intended to end the quoted text and issue the corrected command.

BIP8164 A problem was encountered while attempting to create/delete/list security ACL information.

Severity: 20 : Error

Explanation: The operation was not completed successfully.

Response: Check messages in the system log for related errors and retry the operation. If the problem still occurs,

contact your IBM support center.

BIP8165 An internal error has occurred while accessing the message repository.

Severity: 20 : Error

Explanation: This is an internal error. There may be insufficient memory to complete the operation.

Response: Increase the amount of virtual memory available on your system and retry the command. If the problem

persists turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry the operation and contact your

IBM support center.

BIP8166 The message set to be imported has been finalized in this repository since the export file was

created.

Severity: 20 : Error

Explanation: A record of this message set, indicating that it was finalized, exists in this repository because another

message set was based on it before it was deleted.

Response: Delete all message sets based on this message set or import a finalized version of the message set.

BIP8167 Unknown message repository database name <insert_0>.

Severity: 20 : Error

Explanation: The message repository database name <insert_0> could not be located.

Response: This error is most probably a result of either, an incorrect name that was provided for the

MRMDataSourceName on the mqsiimpexpmsgset command, or the ODBC data source name <insert_0> was not set

up correctly, or has been deleted. Check that the message repository database name has been correctly set up as an

ODBC system data source that has been configured for the correct database.

BIP8168 The userid and/or password are not authorized for connection to the message repository database

<insert_0>.

Severity: 20 : Error

Explanation: The message repository database name <insert_0> could not be opened because the userid and/or

password is not authorized.

Response: This error is most probably a result of either, incorrect userid and password that were provided for the

MRMDataSourceUserId and MRMDataSourcePassword on the mqsiimpexpmsgset command, or the userid has not

been assigned access rights to the message repository database by the database management system. Check that the

408 Diagnostic messages

message repository database access rights have been correctly configured.

BIP8169 An internal error has occurred while accessing the message repository.

Severity: 10 : Warning

Explanation: A SAX parser exception occurred. The text of the exception is <insert_0>.

Response: If the error persists contact your IBM support center.

BIP8170 Failed to import as all plug-ins registered for the message set have not been installed.

Severity: 20 : Error

Explanation: The import file refers to plug-ins which have not been installed.

Response: Install all plug-ins registered for the message set and retry the command.

BIP8171 An internal error has occurred while accessing the message repository.

Severity: 10 : Warning

Explanation: A DOM parser exception occurred. The text of the exception is <insert_0>.

Response: If the error persists contact your IBM support center.

BIP8172 An unexpected exception has occurred while accessing the message repository.

Severity: 10 : Warning

Explanation: The text of the exception is <insert_0>.

Response: If the error persists contact your IBM support center.

BIP8173 An internal error has occurred while accessing the message repository.

Severity: 20 : Error

Explanation: The error was due to invalid content of an XML document.

Response: If the error persists contact your IBM support center.

BIP8174 An internal error has occurred while accessing the message repository.

Severity: 20 : Error

Explanation: The error was due to invalid content of an XML document.

Response: If the error persists contact your IBM support center.

BIP8175 Duplicate message set identifier.

Severity: 20 : Error

Explanation: The message set to be imported already exists in this repository.

Response: Delete the message set and retry the command.

BIP8176 Failed to access export file <insert_0>.

Severity: 20 : Error

Explanation: The error code <insert_1> was detected.

Response: Check that you have access rights to the export file.

BIP8000 to BIP8999 (Commands) 409

BIP8177 Failed to open import file <insert_0>.

Severity: 20 : Error

Explanation: There was a failure opening the import file <insert_0>.

Response: Check the filename and path entered and that you have access rights to the file.

BIP8178 The database transaction log size has been exceeded.

Severity: 20 : Error

Explanation: You have exceeded the transaction log size of the database.

Response: Increase the size of the database transaction log size on your system and retry the command.

BIP8179 Internal error while accessing message repository.

Severity: 10 : Warning

Explanation: An internal inconsistency has been detected while accessing the message repository. The MRM return

code <insert_0> was detected.

Response: This is an internal error. Turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry

the operation and contact your IBM support center.

BIP8180 The message repository database <insert_0> has not been initialized correctly.

Severity: 20 : Error

Explanation: It is not possible to access the message repository because the database <insert_0> has not been

properly initialized.

Response: This error is most probably a result of a setup inconsistency. You must delete your Configuration

Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then recreate your

Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options).

BIP8181 An error has occurred while connecting to the message repository.

Severity: 20 : Error

Explanation: This error is most probably a result of an incorrect userid that was provided for the

MRMDataSourceUserId on the mqsiimpexpmsgset command, or the userid has not been assigned access rights to the

message repository database by the database management system.

Response: Check that the message repository database access rights have been correctly configured. Alternatively, if

the userid is correct, then this is an internal error. The SQL code (<insert_1>) and SQL state (<insert_2>) were

returned. Check your database manager documentation for further information on this error.

BIP8182 Database manager not started.

Severity: 20 : Error

Explanation: The message repository database name, <insert_0>, could not be accessed. The database manager has

either not been started, or has been stopped.

Response: Start the database manager and retry the command.

BIP8183 A referenced resource does not exist in the message repository.

Severity: 20 : Error

Explanation: A resource was referenced, but it does not exist in the message repository.

Response: This is an internal error. Turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry

the operation and contact your IBM support center.

410 Diagnostic messages

BIP8184 Message set is not complete.

Severity: 20 : Error

Explanation: A message set must be complete before performing an export. A message set is incomplete if it

contains any incomplete messages. A message is incomplete if its type is incomplete. An empty type is incomplete if

the type composition is not empty except for type composition message where the type content is not closed. A type

is also incomplete if it has incomplete plug-in layer information or if it has an incomplete child. Similarly, a child is

incomplete if its type is incomplete.

Response: Complete the message set and retry the command.

BIP8185 Duplicate message set name.

Severity: 20 : Error

Explanation: A message set named <insert_0> already exists in this repository.

Response: Delete the message set and retry the command.

BIP8186 The message set <insert_0> with level <insert_1> does not exist in the message repository.

Severity: 20 : Error

Explanation: The message set <insert_0> with level <insert_1> is referenced, but it does not exist in the message

repository.

Response: Correct the problem and retry the command.

BIP8187 Statistics <insert_0> settings for flow <insert_1> in execution group <insert_2> - On?: <insert_3>,

ThreadDataLevel: <insert_4>, NodeDataLevel: <insert_5>, OutputFormat: <insert_6> ,

AccountingOrigin <insert_7>.

Severity: 0 : Information

BIP8188 Invalid message set level.

Severity: 20 : Error

Explanation: The level <insert_0> for message set <insert_1> is invalid.

Response: Correct the message set level and retry the command.

BIP8189 Changes a broker’s statistics options.

Syntax:

mqsichangeflowstats brokerName (-a | -s) (-e executionGroupName | -g) (-f messageFlow | -j) [-c

control] [-t threadData] [-n nodeData] [-r] [-o outputFormat] [-b accountingOrigin]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-a’ indicates archival of statistics

’-s’ indicates snapshot publishing

’-e executionGroupName’ execution group name

’-g’ indicates all execution groups

’-f messageFlow’ message flow name

’-j’ indicates all message flows

’-c control’ starts/stops collection: values allowed are ’active’ or ’inactive’

’-t threadData’ specifies the thread statistics level: values allowed are ’none’ or ’basic’

’-n nodeData’ specifies the node statistics level: values allowed are ’none’, ’basic’ or ’advanced’

’-r’ resets the archival, i.e. deletes all previous records currently held

’-o outputFormat’ specifies the output format: values allowed are ’usertrace’, ’xml’ or (on zOS only) ’smf’

’-b accountingOrigin’ indicates using accounting origin to segregate the statistics.

BIP8000 to BIP8999 (Commands) 411

BIP8190 Displays statistics settings.

Syntax:

mqsireportflowstats BrokerName ( -a | -s | -a -s ) ( -e executionGroupName | -g ) ( -f messageFlow

| -j )

Severity: 10 : Warning

Explanation: Command Options

’brokerName’ name of the broker

’-a’ indicates archival of statistics

’-s’ indicates snapshot publishing

’-e executionGroupName’ execution group name

’-g’ indicates all execution groups

’-f messageFlow’ message flow name

’-j’ indicates all message flows.

BIP8191 Changes a component’s statistics options. Syntax : changeflowstats ( a=yes [,r=yes] | s=yes ) (

,e=ExecutionGroupLabel | ,g=yes ) ( ,f=MessageFlow | ,j=yes ) [ ,l=Level ] [ ,t=ThreadData ] [

,n=NodeData ] [,o=OutputFormat] [,b=AccountingOrigin]

Severity: 10 : Warning

Explanation: Command Options

’a’ indicates Archival of statistics. ’r’ resets the Archival, i.e. deletes all previous records currently held. ’s’ indicates

Snapshot publishing. ’e’ Execution Group name. ’g’ indicates all Execution Groups. ’f’ Message Flow name. ’j’

indicates all Message Flows. ’c’ starts/stops collection: values allowed are ’active’ or ’inactive’. ’t’ specifies the thread

statistics level: ThreadData values allowed are ’none’ or ’basic’. ’n’ specifies the node statistics level: NodeData values

allowed are ’none’, ’basic’ or ’advanced’. ’o’ specifies the output format: values allowed are ’usertrace’, ’xml’ or ’smf’.

’b’ indicates using Accounting Origin to segregate the statistics.

BIP8192 Displays statistics settings. Syntax : reportflowstats ( a=yes, | s=yes, | a=yes,s=yes, ) (

,e=ExecutionGroupLabel | ,g=yes ) ( ,f=MessageFlow | ,j=yes )

Severity: 10 : Warning

Explanation: Command Options

’a’ indicates Archival of statistics. ’s’ indicates Snapshot publishing. ’e’ Execution Group name. ’g’ indicates all

Execution Groups. ’f’ Message Flow name. ’j’ indicates all Message Flows.

BIP8193 Creates a security ACL group entry.

Syntax:

mqsicreateaclgroup (-f fileName | ( (-g groupName | -u userName) -x accessLevel (-b broker | -e

executionGroup | -s | -t | -r) ) )

Severity: 10 : Warning

Explanation: Command Options:

’-f fileName’ Imported ACL list file name.

’-g groupName’ Windows group name for the desired action.

’-u userName’ Windows user name for the desired action.

’-x accessLevel’ Desired security access level for specified object (F, E, D, V).

’-b broker’ The operation references the specified broker.

’-e executionGroup’ The operation references the specified execution group.

’-s’ The operation references the subscriptions.

’-t’ The operation references the topology.

’-r’ The operation references the root topic.

BIP8194 Deletes a security ACL group entry.

Syntax:

mqsideleteaclgroup (-f fileName | (-g groupName | -u userName) (-b broker | -e executionGroup |

-s | -t | -r) )

Severity: 10 : Warning

412 Diagnostic messages

Explanation: Command Options:

’-f fileName’ Imported ACL list file name

’-g groupName’ Group name for the desired action

’-u userName’ User name for the desired action

’-b broker’ The operation references the specified broker

’-e executionGroup’ The operation references the specified execution group

’-s’ The operation references the subscriptions

’-t’ The operation references the topology

’-r’ The operation references the root topic

BIP8195 Lists the current security ACL group(s).

Syntax:

mqsilistaclgroup [-g groupName | -u userName | -b broker | -e executionGroup | -s | -t | -r]

Severity: 10 : Warning

Explanation: Command Options:

’-g groupName’ ACLs referencing the specified group

’-u userName’ ACLs referencing the specified user

’-b broker’ ACLs referencing the specified broker

’-e executionGroup’ ACLs referencing the specified execution group

’-s’ ACLs referencing the subscriptions table

’-t’ ACLs referencing the publish/subscribe topology

’-r’ ACLs referencing the root topic.

BIP8196 Statistics <insert_0> settings for flow <insert_1> in execution group <insert_2> - On?: <insert_3>,

ThreadDataLevel: <insert_4>, NodeDataLevel: <insert_5>, OutputFormat: <insert_6>.

Severity: 0 : Information

BIP8197 Unable to set the security attributes for WebSphere MQ Queue <insert_1> on Queue Manager

<insert_0>.

Severity: 20 : Error

Explanation: This command attempts to set the Group or Principal security attributes for a WebSphere MQ Queue

for the related Queue Manager.

Response: Ensure that the required Group or Principal, <insert_2> is available and that the user issuing this

command is a member of the mqm group.

BIP8198 An attempt to start the Queue Manager for WebSphere MQ Queue Manager <insert_0> was

unsuccessful and returned WebSphere MQ code <insert_1>.

Severity: 20 : Error

Explanation: This command attempts to start the required WebSphere MQ Queue Manager.

Response: Ensure that the required Queue Manager, <insert_0> is available and that the user issuing this command

is a member of the mqm group.

BIP8199 Unable to set the security attributes for WebSphere MQ Queue Manager <insert_0>.

Severity: 20 : Error

Explanation: This command attempts to set the Group or Principal security attributes for a WebSphere MQ Queue

Manager.

Response: Ensure that the required Group or Principal, <insert_1> is available and that the user issuing this

command is a member of the mqm group.

BIP8000 to BIP8999 (Commands) 413

BIP8201 User Name Server starting with refresh interval <insert_0>.

Severity: 0 : Information

Explanation: The User Name Server is being started with a refresh interval that determines (in seconds) how

frequently the native security subsystem’s user/group registry will be reread.

Response: No user action required.

BIP8202 User Name Server UUID has been set to <insert_0>.

Severity: 0 : Information

Explanation: The User Name Server requires a UUID to identify it to the domain.

Response: No user action required.

BIP8203 User Name Server UUID could not be established.

Severity: 30 : Severe error

Explanation: The User Name Server requires a UUID to identify it to the domain, a new UUID was not successfully

generated.

Response: Restart the User Name Server. Contact your IBM support center if the problem persists.

BIP8204 User Name Server is registering a client with UUID <insert_0>, and cache version <insert_1>.

Severity: 0 : Information

Explanation: The User Name Server maintains a registry of clients, uniquely identified by their UUID, and uses the

cache version to determine whether a client that is re-registering has an up-to-date version of user and group

information.

Response: No user action required.

BIP8205 User Name Server failed to send a response/report to a configuration request,

Severity: 20 : Error

Explanation: The User Name Server could not deliver a response/report message.

Response: Check preceding system log entries for errors from the underlying messaging subsystem.

BIP8206 User Name Server received an acknowledgement from an unregistered client with UUID <insert_0>.

Severity: 10 : Warning

Explanation: The User Name Server maintains a registry of clients, uniquely identified by their UUID, an

acknowledgement has been received from a client whose UUID is not in the registry.

Response: Contact your IBM support center if the problem persists.

BIP8207 User Name Server failed to send updated user/group information to client with UUID <insert_0>.

Severity: 20 : Error

Explanation: The User Name Server could not deliver user/group information to a registered client.

Response: Check preceding system log entries for errors from the underlying messaging subsystem.

BIP8208 User Name Server refresh interval has been reset to <insert_0>.

Severity: 0 : Information

Explanation: The User Name Server’s refresh interval determines (in seconds) how frequently the native security

subsystem’s user/group registry will be reread.

414 Diagnostic messages

Response: No user action required.

BIP8209 User Name Server could not retrieve user/group information from the native security subsystem.

Severity: 10 : Warning

Explanation: The User Name Server will continue processing using its cached version of user/group information.

Response: Check preceding system log entries for errors from the underlying security subsystem.

BIP8210 User Name Server has processed <insert_0> of <insert_1> usernames.

Severity: 0 : Information

Explanation: The User Name Server retrieves user/group information from the native security subsystem’s

user/group registry.

Response: No user action required.

BIP8211 User Name Server failed to retrieve <insert_1> <insert_0> entries from the native security subsystem.

Severity: 0 : Information

Explanation: The User Name Server failed to read a number (<insert_1>) of user or group (<insert_0>) entries, and

will continue processing using an incomplete cache of user/group information.

Response: Check trace entries for an indication of which <insert_0> entries could not be read.

BIP8212 User Name Server failed to retrieve more than <insert_1> <insert_0> entries from the native security

subsystem.

Severity: 10 : Warning

Explanation: The User Name Server failed to read more than a given number (<insert_1>) of user or group

(<insert_0>) entries, and will not attempt to read any further <insert_0> entries. Processing will continue using an

incomplete cache of user/group information.

Response: Check trace entries for an indication of which <insert_0> entries could not be read.

BIP8213 User Name Server failed to retrieve any <insert_0> entries from the native security subsystem.

Severity: 20 : Error

Explanation: The User Name Server did not read any user or group (<insert_0>) entries, and will not continue

processing.

Response: Check trace entries for an indication of why no <insert_0> entries were found.

BIP8214 Object not found

Severity: 20 : Error

Explanation: The Configuration Manager repository object <insert_0> of type <insert_1> does not exist.

Response: Ensure that you have specified the correct object name, type and that the object has been defined to the

Configuration Manager.

BIP8215 The ACL command resulted in no change.

Severity: 10 : Warning

Explanation: The ACL command resulted in no change.

Response: The most likely cause of this return code is attempting to delete an Access Control Entry which does not

exist or create one which already exists.

BIP8000 to BIP8999 (Commands) 415

BIP8216 Trace file <insert_0> is not readable by this version of the product. The file was written by version

<insert_1>, while this product is version <insert_2>.

Severity: 20 : Error

Explanation: The trace file contains data that cannot be understood by this product, and the trace reader command

was not able to process the file.

Response: Ensure that the correct version of the product is used to read the trace files.

BIP8217 Trace file <insert_0> is corrupt, and has not been fully read.

Severity: 30 : Severe error

Explanation: The trace file contains data other than complete trace records for the current product version, and the

trace reader command was not able to process the file.

Response: Ensure that the correct product version is used to read trace files. If the correct version is being used and

this error still occurs, ensure that enough disk space is available to store trace data, and that none of the files are

limited by other means (e.g., ulimit on UNIX platforms).

BIP8218 Unable to clear messages for WebSphere MQ Queue <insert_0> from Queue Manager <insert_1>.

Severity: 20 : Error

Explanation: This command attempts to clear a WebSphere MQ queue but was unable to do so.

Response: Locate and resolve the problem and retry the command. This could be because a whole broker, an

Execution Group, a Config Manager, or a User Name Server is still running. Stop all processes associated with the

queue manager, and retry the command.

BIP8219 Service binary path for component <insert_0> changed to <insert_1>; previous value was <insert_2>.

Severity: 10 : Warning

Explanation: The service location for this component was incorrect for this installation. The location has been

updated to the correct value.

Response: None.

BIP8220 Service binary path for component <insert_0> could not be changed to <insert_1>: error <insert_3>.

Current value remains <insert_2>.

Severity: 20 : Error

Explanation: The service location for this component is incorrect for this installation. The command attempted to

change this location, but was unsuccessful.

Response: Determine why the change was unsuccessful, correct the problem, and re-run the command.

BIP8221 <insert_0>: <insert_1> (Version <insert_3>) - <insert_2>

Severity: 0 : Information

BIP8222 Unable to find ODBCINI file <insert_0>.

Severity: 20 : Error

Explanation: Could not find the ODBCINI file <insert_0>, which is specified by the ODBCINI environment variable.

Response: Ensure that the ODBCINI environment variable points to an existing ODBCINI file.

416 Diagnostic messages

BIP8223 User <insert_1> is not a member of group <insert_0>.

Severity: 20 : Error

Explanation: User <insert_1> is not a member of group <insert_0> and therefore does not have the privilege to use

this command.

Response: Talk to your system administrator to obtain the membership of group <insert_0> or login as a user who

does have the membership.

BIP8224 Internal error while trying trying to load library <insert_0>.

Severity: 20 : Error

Explanation: Could not load an internal library <insert_0>.

Response: Ensure that the library is correctly installed.

BIP8225 <insert_0> is not a known component.

Severity: 20 : Error

Explanation: The name provided is not a known component.

Response: Provide a different component name.

BIP8226 Executing system command <insert_0>.

Severity: 0 : Information

BIP8250 The Configuration Manager’s user/group cache is empty.

Severity: 10 : Warning

Explanation: The Configuration Manager receives user and group information from the User Name Server. The

cache will be empty if the Configuration Manager has not yet successfully registered with the User Name Server.

Response: Check preceding system log entries for related errors. Check that the User Name Server has been started.

Contact your IBM support center if the problem persists.

BIP8251 The Configuration Manager failed to send a registration/heartbeat message to the User Name Server.

Severity: 10 : Warning

Explanation: The Configuration Manager could not deliver a registration/heartbeat message to the User Name

Server.

Response: Check preceding system log entries for errors from the underlying messaging subsystem. Contact your

IBM support center if the problem persists.

BIP8252 The Configuration Manager failed to send an acknowledgement message to the User Name Server.

Severity: 10 : Warning

Explanation: The Configuration Manager could not deliver an acknowledgement message to the User Name Server.

Response: Check preceding system log entries for errors from the underlying messaging subsystem. Contact your

IBM support center if the problem persists.

BIP8253 Error in parsing a message from the User Name Server, invalid tag <insert_0>.

Severity: 20 : Error

Explanation: The Configuration Manager has received a message from the User Name Server that it is unable to

parse.

Response: Contact your IBM support center if the problem persists.

BIP8000 to BIP8999 (Commands) 417

BIP8254 Internal Error while parsing a message from the User Name Server.

Severity: 20 : Error

Explanation: The Configuration Manager has encountered an internal error while attempting to parse a message

from the User Name Server.

Response: Contact your IBM support center if the problem persists.

BIP8255 User Name Services are disabled.

Severity: 0 : Information

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs.

Response: No action unless you want to manage topic ACLs. If you want to manage topic ACLs you must

reconfigure the Configuration Manager by providing a queue manager name for the User Name Server.

BIP8256 Failed to initialize the interface to the User Name Server.

Severity: 20 : Error

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. Initialization failures occur when the underlying transport encounters

problems.

Response: Check preceding system log entries for related errors.

BIP8257 The Configuration Manager has reconnected to WebSphere MQ for User Name Services.

Severity: 0 : Information

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. The Configuration Manager was unable to communicate via

WebSphere MQ transports but communication has been reestablished.

Response: Investigate the reasons for the failure of the WebSphere MQ product.

BIP8258 Successfully registered with the User Name Server using UUID <insert_0>.

Severity: 0 : Information

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. The initial registration with the User Name Server succeeded.

Response: No user action required.

BIP8259 The Configuration Manager has not yet registered with the User Name Server.

Severity: 10 : Warning

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. Registration is an asynchronous operation but severe delays require

investigation.

Response: Check that the User Name Server has been started. Check preceding system log entries for related errors.

BIP8260 Successfully initialized the interface to the User Name Server.

Severity: 0 : Information

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. The Configuration Manager will now asynchronously register with the

User Name Server.

Response: No user action required.

418 Diagnostic messages

BIP8261 The Configuration Manager is encountering problems in communicating with the User Name

Server.

Severity: 20 : Error

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. Messaging failures are occurring.

Response: Check preceding system log entries for related errors. If the problem persists contact your IBM support

center.

BIP8262 Failed to initialize the interface to the User Name Server, a UUID could not be established.

Severity: 20 : Error

Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and

group information for configuring topic ACLs. The Configuration Manager requires a UUID to identify it to the User

Name Server, a new UUID was not successfully generated.

Response: Restart the Configuration Manager. Contact your IBM support center if the problem persists.

BIP8263 User Name Server has found a user <insert_0> that is not a member of any groups. This user will be

ignored.

Severity: 10 : Warning

Explanation: Each user must be a member of at least one group.

Response: Use the OS tools to assign the user <insert_0> to at least one group.

BIP8280 Successfully initialized interface to the NT security domain, <insert_0>.

Severity: 0 : Information

Explanation: A component of WebSphere Message Brokers has successfully initialized the NT security domain.

Response: No user action required.

BIP8281 Error in initializing the NT security domain: return code <insert_0>; subsystem error code <insert_1>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use

as a supplier of user and group information, without success.

Response: Check NT security subsystem documentation for the reported error.

BIP8282 Error in call <insert_0> to the NT security domain with return code <insert_1>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to call the NT security domain. The

security subsystem returned an error code.

Response: Check NT security subsystem documentation for the reported error. Restart the relevant service

component (UserNameServer, or Configuration Manager). Ensure that a Domain Controller, either Primary or

Backup, is available.

BIP8283 Error in determining the domain controller in the NT security domain, return code <insert_0>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use

as a supplier of user and group information. The security subsystem returned an error code.

Response: Check NT security subsystem documentation for the reported error.

BIP8000 to BIP8999 (Commands) 419

BIP8284 Failed to find NT security domain, <insert_0>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers has failed to locate the specified NT security domain.

Response: Check that the domain name was correctly specified and that it is accessible from this machine.

BIP8285 Insufficient authority to access NT security domain, <insert_0>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use

as a supplier of user and group information. The userid under which the component is running does not have the

authority to access this information in the specified domain.

Response: Check that the correct domain name was specified in the configuration command that created this

component and check that its service id has administrative or account operator privilege in that domain.

BIP8286 Error in Operating System call <insert_0>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to call the Operating System. The security

subsystem returned an error code.

Response: Check Operating system documentation and environment.

BIP8301 Failed to send initial registration to the User Name Server.

Severity: 20 : Error

Explanation: The Broker communicates with the User Name Server in order to procure user and group information

for configuring topic ACLs. This broker has never established communication with the User Name Server and has no

cached user and group information. The process will be terminated.

Response: Check that the User Name Server is running. Check preceding system log entries for related errors.

BIP8302 A problem occurred in registering with the User Name Server.

Severity: 20 : Error

Explanation: The Broker communicates with the User Name Server in order to procure user and group information

for processing topic ACLs. The Broker will use the user and group information that it last successfully retrieved from

the User Name Server until communications are reestablished. Registration is an asynchronous operation but severe

delays and repetitions of this message require investigation.

Response: Check that the User Name Server has been started. Check preceding system log entries for related errors.

BIP8303 The Broker’s user/group cache is empty.

Severity: 10 : Warning

Explanation: The Broker maintains a persistent copy of user and group information which it initially receives from

the User Name Server. The cache will be empty if the Broker has never successfully registered with the User Name

Server.

Response: Check preceding system log entries for related errors. Check that the User Name Server has been started.

Contact your IBM support center if the problem persists.

BIP8304 Starting deferred JMS/IP Input Node with authentication enabled.

Severity: 0 : Information

Explanation: The broker has received authentication information from the User Name Server and JMS/IP Input

nodes with authentication enabled will now be started.

420 Diagnostic messages

Response: No user action required.

BIP8305 Cannot start a JMS/IP Input Node with authentication support.

Severity: 10 : Warning

Explanation: Authentication has been enabled for a JMS/IP Input Node but the broker has received either no

authentication information or invalid authentication information from the User Name Server.

Response: Check preceding system log entries for related errors. Check the authentication parameters specified

during User Name Server configuration. Contact your IBM support center if the problem persists.

BIP8306 Starting deferred JMS/IP Input Node with authorization enabled.

Severity: 0 : Information

Explanation: The broker has received authorization information from the User Name Server and JMS/IP Input

nodes will now be started.

Response: No user action required.

BIP8307 The start of a JMS/IP Input Node has been deferred.

Severity: 10 : Warning

Explanation: Authorization has been enabled but the broker has yet to receive authorization information from the

User Name Server. The JMS/IP node will be started when this information has been received.

Response: Check preceding system log entries for related errors. Check that the User Name Server has been started.

Contact your IBM support center if the problem persists.

BIP8308 The start of a JMS/IP Input Node has been deferred.

Severity: 10 : Warning

Explanation: Authentication has been enabled for a JMS/IP Input Node but the broker has yet to receive

authentication information from the User Name Server. The node will be started when this information has been

received.

Response: Check preceding system log entries for related errors. Check that the User Name Server has been started.

Contact your IBM support center if the problem persists.

BIP8309 The broker has successfully processed the initial message from the User Name Server.

Severity: 0 : Information

Explanation: The broker has received the latest authentication and/or authorization information from the User

Name Server. If this is the first time that the broker and User Name Server have ever communicated, then the broker

will now be ready to support pubsub security services.

Response: No user action required.

BIP8310 User Name Server has completed processing a command request.

Severity: 0 : Information

Explanation: This message is issued when the User Name Server has finished processing a command request from a

broker or Configuration Manager.

Response: No user action required.

BIP8000 to BIP8999 (Commands) 421

BIP8311 User Name Server received command message <insert_0>.

Severity: 0 : Information

Explanation: This message is issued when the User Name Server receives a command request from a broker or

Configuration Manager.

Response: No user action required.

BIP8380 Successfully initialized the plug-in user/group registry.

Severity: 0 : Information

Explanation: A component of WebSphere Message Brokers has successfully initialized the plug-in user/group

registry.

Response: No user action required.

BIP8381 Error in initializing the plug-in user/group registry.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to initialize the plug-in service for use as a

supplier of user and group information.

Response: Check the plug-in service’s diagnostic report for initialization errors.

BIP8382 Error in call <insert_0> to the plug-in user/group registry with return code <insert_1>.

Severity: 20 : Error

Explanation: A component of WebSphere Message Brokers is attempting to call the plug-in user/group registry. The

plug-in returned an error code.

Response: Check the plug-in service’s diagnostic report for the reported error.

BIP8390 Successfully initialized support for authentication.

Severity: 0 : Information

Explanation: A component of WebSphere Message Brokers has successfully loaded and initialized the authentication

support module.

Response: No user action required.

BIP8391 Error in initializing support for authentication.

Severity: 10 : Warning

Explanation: A component of WebSphere Message Brokers is attempting to initialize support for authentication

Response: Check preceding system log entries for related errors. Check the authentication service’s diagnostic report

for initialization errors.

BIP8392 Authentication Protocol Type not recognised, <insert_0>.

Severity: 10 : Warning

Explanation: The User Name Server component of WebSphere Message Brokers is attempting to initialize support

for authentication but does not recognise the specified authentication type. Authentication support will be disabled.

Response: Check that a valid authentication protocol type string was specified in the configuration command that

created the User Name Server. Processing will continue but authentication support will be disabled.

422 Diagnostic messages

BIP8393 Authentication support is disabled.

Severity: 10 : Warning

Explanation: A component of WebSphere Message Brokers is attempting to initialize support for authentication but

authentication services have been disabled.

Response: Check preceding system log entries for related errors. Check that a valid authentication protocol type

string was specified in the configuration command that created the User Name Server. Check the authentication

service’s diagnostic report for initialization errors.

BIP8394 Error in initialising Data Source for Authentication Service.

Severity: 10 : Warning

Explanation: The User Name Server component of WebSphere Message Brokers is attempting to initialize support

for authentication but has encountered a problem in initialising its Data Source. Authentication support will be

disabled.

Response: Check that a valid file was specified as Data Source in the configuration command that created the User

Name Server. The User Name Server may not have successfully read the file. In order to check for errors, you should

enable service trace and restart the User Name Server. When service trace is enabled the User Name Server produces

a log file named auth<pid>.out (where pid is a process id) in the product log directory that records any errors

encountered in reading the Data Source. Processing will continue but authentication support will be disabled.

BIP8401 Message associated with internal message number <insert_0> was not found: data supplied

<insert_1>

Severity: 20 : Error

Explanation: An internal message number was used for which no associated message text could be found.

Response: This is an internal error. Contact your IBM support center.

BIP8403 MAX_CLIENT_READ_THREADS was < 0, it must be >= 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value.

Response: Respecify the MAX_CLIENT_READ_THREADS value to be greater or equal to 0 and restart the broker.

Note that MAX_CLIENT_READ_THREADS is 0 by default and should not be specified as non-zero in normal

operation. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n

maxClientReadThreads -v value

BIP8404 PING_TIMEOUT_MULTIPLE was <= 0, it must be > 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value.

Response: Respecify the PING_TIMEOUT_MULTIPLE value to be greater than 0 and restart the broker. Note that

PING_TIMEOUT_MULTIPLE=3 is the default and usually does not require overriding. To change the value, use the

following mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n

pingTimeoutMultiple -v value

BIP8405 PING_MIN was <= 0, it must be > 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value.

Response: Respecify the PING_MIN value to be greater than 0 and restart the broker. Note that PING_MIN is 100

by default and usually does not require overriding. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o

DynamicSubscriptionEngine -n pingMin -v value

BIP8000 to BIP8999 (Commands) 423

BIP8406 EXPECTED_MESSAGE_SIZE was <= 0, it must be > 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value.

Response: Respecify the EXPECTED_MESSAGE_SIZE value to be greater than 0 and restart the broker. Note that

EXPECTED_MESSAGE_SIZE=200 by default. While setting this value to something more like the true expected size

can improve performance slightly, this parameter does not affect correctness, and the default is normally satisfactory.

mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n expectedMessageSize

-v value

BIP8407 MAX_MESSAGE_SIZE was <= 0, it must be > 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value. The MAX_MESSAGE_SIZE

value is used for the Real Time transport to declare the maximum size for messages to be delivered to client

applications

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request. This can

be set by using : mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n

maxMessageSize -v value A broker restart is required to activate the change.

BIP8408 MESSAGE_SIZE_EXTRA_ALLOWANCE was < 0, it must be >= 0.

Severity: 20 : Error

Explanation: A configuration request was received which specified an invalid value. The

MESSAGE_SIZE_EXTRA_ALLOWANCE value is used for the Real Time transport to declare the extra allowance size

for messages to be delivered to client applications

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request. This can

be set by using : mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n

messageSizeExtraAllowance -v value A broker restart is required to activate the changes.

BIP8410 An exception occured while attempting to specify a ″strong″ crypto library for use by MinCrypto.

MinCrypto will default to the standard exportable library instead. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: This is an internal error and you should contact your IBM support center.

BIP8411 An attempt to specify the default ″exportable″ crypto library in MinCrypto failed with an exception.

The exception is <insert_0>.

Severity: 20 : Error

Explanation: A security error has occurred. The error is described in the message.

Response: This is an internal error and you should contact your IBM support center.

BIP8412 A failure has occured when attempting to log an event. The type of event is <insert_0>, the severity

of the event is <insert_1>, and the exception is <insert_2>.

Severity: 10 : Warning

Explanation: An event recording error has occurred. The error is described in the message.

Response: This is an internal error and you should contact your IBM support center.

424 Diagnostic messages

BIP8413 The broker received an invalid or unexpected control message. The type of the message is

<insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8414 Authentication on a broker-broker connection failed. This is non-fatal but must be repaired in order

to allow multibroker routing. The name of the attempted broker-broker connection is <insert_0>, and

the InauthenticBrokerException that was caught is <insert_1>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: Correct the error and retry the operation.

BIP8415 Authentication on a broker-broker connection timed out after too many unsuccessful attempts. This

is non-fatal but must be repaired in order to allow multibroker routing. The name of the attempted

broker-broker connection is <insert_0>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: Correct the error and retry the operation.

BIP8416 The broker caught an exception while attempting to update its broker-broker connection status

using a local SemaphoreClient. The attempted update is <insert_0> and the exception is <insert_1>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8417 A VMX message received on a broker-broker connection had a bad MDT. The associated connection

will be closed. The MsgDistException which triggered the event is <insert_0>, and the name of the

broker-broker connection is <insert_1>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8418 An error was encountered while parsing the BROKERS_THRU_SOCKS parameter. This is non-fatal

but will disable any socksified broker-broker connections. The caught exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8419 An error occurred while attempting to instantiate the non-blocking IO library. The regular blocking

IO library will be used instead. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8000 to BIP8999 (Commands) 425

BIP8420 A request was made to add an initial state processor to a topic which was alread assigned a

processor. The requested processor will be ignored. The full name of the requested topic is

<insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8421 A SecurityGeneralException was encountered while processing a message received on a connection.

The caught exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8422 A client attempted to publish on a topic for which it was not authorized. The message was dropped.

The client connection is <insert_0>, and the topic is <insert_1>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: Correct the error and retry the operation.

BIP8423 A client connection failed on authentication and will be disconnected. The hostname and port of the

failed connection is <insert_0>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: Correct the error and retry the operation.

BIP8424 A client connection was closed because it failed to finish authentication within a preset time limit.

The hostname and port of the failed connection is <insert_0>.

Severity: 10 : Warning

Explanation: A security error has occurred. The error is described in the message.

Response: Correct the error and retry the operation by attempting to reconnect the client

BIP8425 The broker configuration of MAX_BROKER_QUEUE_SIZE is between 0 and 500 bytes. This is

rather small and may cause many broker-broker messages to be discarded. The value of

MAX_BROKER_QUEUE_SIZE is <insert_0>.

Severity: 10 : Warning

Explanation: A configuration request was received which specified an unexpected value.

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request. The

MAX_BROKER_QUEUE_SIZE is used for queueing Real Time transport broker to broker messages.

mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxBrokerQueueSize

-v value

BIP8426 The broker configuration of MAX_CLIENT_QUEUE_SIZE is between 0 and 500 bytes. This is rather

small and may cause many client-broker messages to be discarded. The value of

MAX_CLIENT_QUEUE_SIZE is <insert_0>.

Severity: 10 : Warning

Explanation: A configuration request was received which specified an invalid value.

426 Diagnostic messages

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request. This can

be done using mqsichangeproperties: mqsichangeproperties BrokerName -e ExecutionGroupLabel -o

DynamicSubscriptionEngine -n maxClientQueueSize -v value A broker restart is required to activate the change

BIP8427 ENABLE_SOCKS is true but BROKERS_THRU_SOCKS is zero-length. Processing will continue but

no broker-broker connections will be socksified. This may not be the intended behavior.

Severity: 10 : Warning

Explanation: A configuration request was received which specified an invalid value.

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request.

mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n enableThruSocks -v

value

BIP8428 ENABLE_SOCKS is true but SOCKS_HOST is zero-length. Processing will continue but no

broker-broker connections will be socksified. This may not be the intended behavior.

Severity: 10 : Warning

Explanation: A configuration request was received which specified an invalid value.

Response: Modify the configuration request to specify a valid value for the attribute, and retry the request.

mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n socksHost -v value

BIP8429 An exception was caught in the run loop of the StatsEPImpl thread. Processing continues. The

exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8430 An exception occurred while closing the segment reader portion of a non-blocking threaded socket

segment. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8431 An exception occurred while closing the segment writer portion of a non-blocking threaded socket

segment. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8432 An exception occurred while deregistering the client associated with a non-blocking threaded socket

segment. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8000 to BIP8999 (Commands) 427

BIP8433 An exception occurred while closing the socket associated with a non-blocking threaded socket

segment. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8437 A broker connection on socket <insert_0> established with name <insert_1> received a topology

message from broker <insert_2>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8438 An attempt to establish a broker connection on socket <insert_0> failed with exception <insert_1>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error may be caused by an application attempting to use the port

that has been configured for broker connections.

Response: Investigate whether an application is incorrectly using the socket that has been configured for broker

connections.

BIP8439 An alpha services reload was requested but the wrong directory is in use.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8440 An error occurred during locking. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8441 An exception occurred during reset after a lock error. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8442 A service failure was reported to BrokerControl. The service reference is <insert_0>, the reason for

the failure is <insert_1>, and the exception is <insert_2>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8443 The LogRecorder generated an exception while recording a log entry. The log mask is <insert_0> and

the exception is <insert_1>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

428 Diagnostic messages

Response: This is an internal error and you should contact your IBM support center.

BIP8444 An exception was caught while changing the state of an internal ControlHandler. Processing

continues. The exception is <insert_0>.

Severity: 10 : Warning

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8445 An exception was caught at the end of the scheduling loop of StatsEPImpl. As a result, the statistics

entry point is now disabled. Processing continues, but statistics are no longer be available from this

broker. The exception is <insert_0>.

Severity: 20 : Error

Explanation: An unexpected error occurred. The error is described in the error message.

Response: This is an internal error and you should contact your IBM support center.

BIP8446 Message queue exceeded limit. Discarded <insert_0> bytes in <insert_1> messages.

Severity: 10 : Warning

Explanation: The message queue exceeded its configured limit for the Real Time transport.

Response: Consider increasing the value of MAX_CLIENT_QUEUE_SIZE and MAX_BROKER_QUEUE_SIZE. These

can be set using mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n

maxClientQueueSize -v value or mqsichangeproperties BrokerName -e ExecutionGroupLabel -o

DynamicSubscriptionEngine -n maxBrokerQueueSize -v value MAX_CLIENT_QUEUE_SIZE is used for Broker to

Client messages. MAX_BROKER_QUEUE_SIZE is used for Broker to Broker messages.

BIP8447 Client <<insert_0>> tried to publish a <insert_1> byte message, exceeding the limit <insert_2>.

Severity: 10 : Warning

Explanation: A client connection was closed (culled) because it tried to publish a message that exceeded the

configured limit, MAX_MESSAGE_SIZE. A string giving the hostname and port of the failed connection is included

as the first parameter of this event. The size of the message is the second parameter. And the configured maximum is

the third parameter.

Response: If the failing client was publishing a message within the expected size range, consider increasing the

value of the MAX_MESSAGE_SIZE This can be set using : mqsichangeproperties BrokerName -e

ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxMessageSize -v value A broker restart is required to

activate the change parameter.

BIP8448 A broker-broker connection with <insert_0> has been disconnected due to failure to respond to a

ping

Severity: 10 : Warning

Explanation: A connection did not respond to pings to it is about to be reaped. A string representing the host and

port of the remote broker is the sole parameter of this event.

Response: This message is for information only, to indicate disconnection of a broker due to its inactivity.

Reconnection will be attempted automatically.

BIP8449 A broker-broker connection with <insert_0> has been disconnected due to Exception <insert_1>.

Severity: 10 : Warning

Explanation: An exception occurred while processing messages on a broker-broker connection. The exception may

have occurred either due to a message processing error or a dropped connection.

BIP8000 to BIP8999 (Commands) 429

Response: This message is for information only, to indicate disconnection of a broker due to an exception.

Reconnection will be attempted automatically.

BIP8450 Server-to-server authentication failed because id of other broker <insert_0> was not in the server

principals directory.

Severity: 10 : Warning

Explanation: The would-be partner broker authenticated with an id that was not known to this broker.

Response: Ensure that the id <insert_0> is known to the broker

BIP8451 Client-to-server authentication failed because id of the client <insert_0> was not in the client

principals directory.

Severity: 20 : Error

Explanation: The would-be client authenticated with an id that was not known to this broker.

Response: Ensure that the client <insert_0> is known to the broker

BIP8452 <insert_0> is not allowed in BROKER_AUTH_PROTOCOLS.

Severity: 20 : Error

Explanation: We don’t allow the use of protocol <insert_0> for broker to broker authentication.

Response: This is an internal error and you should contact your IBM support center.

BIP8453 Broker-Broker connection on socket <insert_0> with broker <insert_1> has been established

Severity: 0 : Information

Explanation: Broker-Broker connection on socket <insert_0> with broker <insert_1> has been established and

authenticated with id=<insert_1> and protocol=<insert_2>.

Response: This message is for information only

BIP8454 The authentication timeout thread for an instance of Security caught an exception

Severity: 20 : Error

Explanation: The authentication timeout thread for an instance of Security caught the exception <insert_0>

Response: This is a warning message, client authentication may be affected.

BIP8460 Could not create internal non-blocking socket on the loopback address 127.0.0.1. Using the address

of the adapter associated with the host name of the machine.

Severity: 0 : Information

Explanation: An exception occurred while creating an internal communication socket bound to the loopback address

127.0.0.1. The operaton will be retried using the address of the adapter bound to the hostname of the computer.

Response: This message is for information only.

BIP8461 Broker <insert_0> has an incorrectly configured Broker Topology: <insert_1> with <insert_2>

neighbours: <insert_3>.

Severity: 10 : Warning

Explanation: A Broker Topology has been incorrectly configured.

Response: Correct the topology configuration using either the Message Brokers Toolkit or the Config Manager

Proxy.

430 Diagnostic messages

BIP8462 Disthub caught a fatal exception [<insert_0>].

Severity: 30 : Severe error

Explanation: A fatal exception occurred within the Broker <insert_0>. The behavior of the Broker is now undefined

and further use will produce unpredictable results

Response: Restart the broker, if the problem persists you should contact your IBM support center

BIP8463 Broker <insert_0> detected a cycle in its own topology configuration.

Severity: 20 : Error

Explanation: The broker found a cycle in the topology. This will result in publications looping around brokers in the

topology.

Response: Correct and redeploy the topology in the Message Brokers Toolkit, or programmatically using the Config

Manager Proxy.

BIP8464 Error while trying to open Interbroker Port <insert_0>.

Severity: 20 : Error

Explanation: While trying to open port <insert_0> for Real-time Communications from a Neighbor, a

java.net.BindException occurred.

Response: This normally occurs because another application is holding the socket open. If required, change the

InterbrokerPort Broker property in the Message Brokers Toolkit to a port that isn’t in use. This can also be done

programmatically using the Config Manager Proxy.

BIP8465 A connection from client at <insert_0> has been disconnected due to inactivity.

Severity: 10 : Warning

Explanation: A connection did not respond to pings so it is about to be reaped. A string representing the host and

port of the reaped connection is the sole parameter of this event.

Response: This message is for information only, to indicate disconnection of a client due to its inactivity.

BIP8601 This program requires VGA or better resolution.

Severity: 20 : Error

Explanation: The installation of this product requires that you use a display with at least VGA resolution.

Response: Check your display/display settings.

BIP8602 Setup requires Windows NT Server 4.0/SP5 or later.

Severity: 20 : Error

Explanation: The installation of this product requires that your system level is Windows NT Server 4.0/SP5 or later.

Response: Upgrade your NT system.

BIP8603 WebSphere Message Brokers install or uninstall is already running.

Severity: 20 : Error

Explanation: The install has detected a conflicting install/uninstall process running on your machine.

Response: Exit this instance of the install/uninstall and terminate the conflicting process.

BIP8000 to BIP8999 (Commands) 431

BIP8604 The system has detected that you do not have administrator equivalent rights. You must log on as

an administrator and run setup again.

Severity: 20 : Error

Explanation: To install WebSphere Message Brokers you need administrator authority.

Response: Terminate the installation, log off, log on as an administrator, and retry.

BIP8606 Before setup can display help, this computer’s help system needs upgrading to HTML Help 1.3.

Would you like to upgrade now? You might need to restart the computer.

Severity: 10 : Warning

Explanation: Help for install and uninstall requires that HTML Help 1.3 to be installed.

Response: If you want to see the install/uninstall help then you can allow WebSphere Message Brokers to upgrade

your system. Note that in order to activate this help you might need to terminate this install, reboot and then start

install again.

BIP8610 Help cannot be displayed as Internet Explorer level is less than 4.01.

Severity: 10 : Warning

Explanation: The install or uninstall cannot display help unless IE 4.01 or later is installed on your machine.

Response: If you wish to see the help for install/uninstall then you must exit this instance of the installation or

uninstallation and upgrade your system.

BIP8611 Uninstall cannot continue, administrator authority is required.

Severity: 20 : Error

Explanation: You require administrator authority to uninstall WebSphere Message Brokers.

Response: Access the machine with the same user authority that the product was installed with.

BIP8612 Select at least one component to proceed.

Severity: 0 : Information

Explanation: You need to select at least one component for installation/uninstallation.

Response: Select one or more components to proceed.

BIP8613 WebSphere Message Brokers setup or uninstallation is already running.

Severity: 10 : Warning

Explanation: WebSphere Message Brokers uninstall has detected that there is an instance of install or uninstall

already running.

Response: Terminate this uninstall instance and restart (if necessary) when the already running install or uninstall

has finished.

BIP8614 One or more problems occurred during uninstallation. Review <insert_0> for details.

Severity: 10 : Warning

Explanation: One (or more) problems were encountered during uninstallation of the product. You may have seen a

previous message(s) indicating the nature of the problem. The install/uninstall log <insert_0> may contain additional

information on the nature of the problem.

Response: Review the install/uninstall log <insert_0> to aid resolution of the problem. If the problem persists,

contact your IBM support center.

432 Diagnostic messages

BIP8615 Problem encountered stopping broker <insert_0>. Return from wmqpsstop was <insert_1>.

Severity: 10 : Warning

Explanation: The uninstall attempted to stop a broker named <insert_0> using wmqpsstop but encountered an error.

The return code from this command was <insert_1>.

Response: The command can be retried by choosing Retry, this is the suggested action. If you choose Abort or

Cancel then uninstall will end. Before relaunching the uninstall you should try to manually stop the broker

identified. If you choose Ignore (if available) then uninstall will continue, but it is possible that the problem with

wmqpsstop may cause additional errors to appear when the uninstall attempts to delete the broker. Additional help

is available using the Help button.

BIP8616 Unable to delete broker <insert_0>. Return Code from wmqpsdeletebroker was <insert_1>. Abort,

Retry, or Ignore?

Severity: 10 : Warning

Explanation: The uninstall attempted to delete a broker (<insert_0>) but encountered an error. The return code from

wmqpsdeletebroker was <insert_1>.

Response: The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will

terminate. Before relaunching the uninstall you should try to manually delete the broker identified. If you choose

Ignore (if available) then uninstall will continue, but it is possible that additional errors will be encountered later.

Additional help is available using the Help button.

BIP8617 Unable to stop Configuration Manager. Return Code from wmqpsstop was <insert_0>.

Severity: 10 : Warning

Explanation: The uninstall attempted to stop the Configuration Manager using wmqpsstop but encountered a

problem. The return code from wmqpsstop was <insert_0>.

Response: The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will end.

Before relaunching the uninstall you should try to manually stop the Configuration Manager. If you choose Ignore (if

available) then uninstall will continue, but it is possible that the problem with wmqpsstop may cause additional

errors to appear when the uninstall attempts to delete the Configuration Manager. Additional help is available using

the Help button.

BIP8618 Unable to delete configuration manager. Return Code from wmqpsdeleteconfigmgr was <insert_0>.

Severity: 10 : Warning

Explanation: The uninstall attempted to delete the Configuration Manager but encountered an error. The return

code from wmqpsdeleteconfigmgr was <insert_0>.

Response: The command can be retried by choosing Retry. If you choose Abort then uninstall will terminate. Before

relaunching the uninstall you should try to manually delete the Configuration Manager. If you choose Ignore (if

available) then uninstall will continue, but it is possible that additional errors will be encountered later. Additional

help is available using the Help button.

BIP8619 Unable to stop User Name Server. Return Code from wmqpsstop was <insert_0>. See message

Severity: 10 : Warning

Explanation: The uninstall attempted to stop the User Name Server using wmqpsstop but encountered a problem.

The return code from wmqpsstop was <insert_0>.

Response: The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will be

terminated. Before relaunching the uninstall you should try to manually stop the User Name Server. If you choose

Ignore (if available) then uninstall will continue, but it is possible that the problem with wmqpsstop may cause

additional errors to appear when the uninstall attempts to delete the User Name Server. Additional help is available

using the Help button.

BIP8000 to BIP8999 (Commands) 433

BIP8620 Unable to delete User Name Server. Return Code from wmqpsdeleteusernameserver was <insert_0>.

Severity: 10 : Warning

Explanation: The uninstall attempted to delete the User Name Server but encountered an error. The return code

from wmqpsdeleteusernameserver was <insert_0>.

Response: The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will

terminate. Before relaunching the uninstall you should try to manually delete the User name Server. If you choose

Ignore (if available) then uninstall will continue, but it is possible that additional errors will be encountered later.

Additional help is available using the Help button.

BIP8621 Install of <insert_0> has started

Severity: 0 : Information

Explanation: The install of product <insert_0> has started. The end of the install will be signaled by BIP8622.

Response: No user action required

BIP8622 Install of <insert_0> has finished successfully

Severity: 0 : Information

Explanation: Install of product <insert_0> has finished without any errors.

Response: No user action required

BIP8623 Uninstall of <insert_0> has started

Severity: 0 : Information

Explanation: The uninstall of product <insert_0> has started. The end of the uninstall will be signaled by BIP8624.

Response: No user action required

BIP8624 Uninstall of <insert_0> has finished successfully

Severity: 0 : Information

Explanation: Uninstall of product <insert_0> has finished without any errors.

Response: No user action required

BIP8640 symlink returned EACCES when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: Write access to the directory containing <insert_1> is denied, or one of the directories in the path prefix

of <insert_1> did not allow search permission.

BIP8641 symlink returned EEXIST when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: <insert_1> already exists.

BIP8642 symlink returned EFAULT when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: This is an internal error, please contact your IBM support center.

434 Diagnostic messages

BIP8643 symlink returned EIO when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: And I/O error occurred, please check the state of the filesystems and retry the command. If the

problem persists please contact your IBM support center.

BIP8644 symlink returned ELOOP when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: Too many symbolic links were encountered in resolving <insert_1>.

BIP8645 symlink returned ENAMETOOLONG when attempting to create a symbolic link with target

<insert_0> and link name <insert_1>.

Severity: 30 : Severe error

Explanation: <insert_0> or <insert_1> was too long for the filesystem to handle.

BIP8646 symlink returned ENOENT when attempting to create a symbolic link with target <insert_0> and

link name <insert_1>.

Severity: 30 : Severe error

Explanation: A directory component in <insert_1> does not exist or is a dangling symbolic link, or <insert_0> is the

empty string.

BIP8647 symlink returned ENOMEM when attempting to create a symbolic link with target <insert_0> and

link name <insert_1>.

Severity: 30 : Severe error

Explanation: Insufficient kernel memory was available.

BIP8648 File rename operation returned ENOSPC when attempting to create a symbolic link with target

<insert_0> and link name <insert_1>.

Severity: 30 : Severe error

Explanation: The device containing <insert_1> path prefix has no room for the <insert_1> directory entry.

BIP8649 symlink returned ENOTDIR when attempting to create a symbolic link with target <insert_0> and

link name <insert_1>.

Severity: 30 : Severe error

Explanation: A component used as a directory in <insert_1> is not, in fact, a directory.

BIP8650 symlink returned EPERM when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: The filesystem containing <insert_1> does not support the creation of symbolic links.

BIP8651 symlink returned EROFS when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: <insert_1> is on a read-only filesystem.

BIP8000 to BIP8999 (Commands) 435

BIP8652 symlink operation failed when attempting to create a symbolic link with target <insert_0> and link

name <insert_1>.

Severity: 30 : Severe error

Explanation: The operation failed for an unknown reason, please attempt to create the symbolic manually and

resolve the errors before re-running the command.

BIP8653 Creating a symbolic link with target <insert_0> and link name <insert_1>

Severity: 0 : Information

BIP8654 Moving filesystem artefacts from <insert_0> to <insert_1>

Severity: 0 : Information

BIP8655 Removing <insert_0>.

Severity: 0 : Information

BIP8656 Cannot remove non-empty directory <insert_0> due to unhandled file <insert_1>

Severity: 10 : Warning

BIP8657 Creating directory <insert_0>

Severity: 0 : Information

BIP8658 Unable to determine necessary information for migrating broker <insert_0>, does it really exist?

Severity: 20 : Error

BIP8659 Could not determine the Data Source Name for broker <insert_0>, could be wrong version?

Severity: 20 : Error

BIP8660 Could not determine the Queue Manager for broker <insert_0>, could be wrong version?

Severity: 20 : Error

BIP8661 Detected source version <insert_0>.<insert_1>.<insert_2>.<insert_3>

Severity: 0 : Information

BIP8662 Detected target version <insert_0>.<insert_1>.<insert_2>.<insert_3>

Severity: 0 : Information

BIP8663 Creating temporary new tables

Severity: 0 : Information

BIP8664 Migrating from existing tables to temporary new tables

Severity: 0 : Information

436 Diagnostic messages

BIP8665 Dropping existing tables

Severity: 0 : Information

BIP8666 Creating new tables

Severity: 0 : Information

BIP8667 Copying all rows from temporary new tables to new tables

Severity: 0 : Information

BIP8668 Dropping temporary new tables

Severity: 0 : Information

BIP8669 Database migration successful

Severity: 0 : Information

BIP8670 Database migration started

Severity: 0 : Information

BIP8671 Database migration failed

Severity: 20 : Error

BIP8672 Rolling back database changes

Severity: 10 : Warning

BIP8673 Migration of broker <insert_0> from version <insert_1>.<insert_2>.<insert_3>.<insert_4> to version

<insert_5>.<insert_6>.<insert_7>.<insert_8> failed, see previous messages for reasons.

Severity: 20 : Error

BIP8674 Configuration Manager <insert_0> (Version <insert_1>.<insert_2>) specified for migration.

Severity: 0 : Information

BIP8675 UserNameServer <insert_0> (Version <insert_1>.<insert_2>) specified for migration.

Severity: 0 : Information

BIP8676 Component <insert_0> is of a type which cannot be migrated. Only Brokers, Configuration Managers

and UserNameServers may be migrated.

Severity: 30 : Severe error

BIP8677 Component <insert_0> was specified with a source version of

<insert_1>.<insert_2>.<insert_3>.<insert_4>, whilst version <insert_5>.<insert_6>.<insert_7>.<insert_8>

was detected.

Severity: 10 : Warning

BIP8000 to BIP8999 (Commands) 437

BIP8678 Component <insert_0> is sharing a database schema with component <insert_1>.

Severity: 10 : Warning

Explanation: Migrate one component first and then migrate just the registry (using the ’-1’ flag) and MQ (using the

’-2’ flag) components of the others.

BIP8679 Found a 64 bit execution group: <insert_0>. Brokers with 64 bit execution groups cannot be migrated

to versions prior to 6.

Severity: 10 : Warning

BIP8680 Pre-migration check succeeded.

Severity: 0 : Information

BIP8681 Pre-migration check failed.

Severity: 10 : Warning

BIP8682 Unable to open root registry key <insert_0> for query.

Severity: 10 : Warning

BIP8683 Unable to query values under key <insert_0>.

Severity: 10 : Warning

BIP8684 Rolling back WebSphere MQ changes

Severity: 10 : Warning

BIP8685 Rolling back Registry changes

Severity: 10 : Warning

BIP8686 Finished Rolling back WebSphere MQ changes

Severity: 10 : Warning

BIP8687 Finished Rolling back Registry changes

Severity: 10 : Warning

BIP8688 Following migration, Message Set <insert_0>(<insert_1>) should be redeployed to Execution Group

<insert_2>(<insert_3>).

Severity: 10 : Warning

BIP8689 The source and target version are compatible, no migration is necessary.

Severity: 0 : Information

BIP8700 Post-migration check started.

Severity: 0 : Information

Explanation: The migration utility is checking the component configuration to ensure that migration was successful.

Response: None.

438 Diagnostic messages

BIP8701 Post-migration check succeded

Severity: 0 : Information

Explanation: The migration utility did not find any configuration errors for the component.

Response: None.

BIP8702 Post-migration check failed; see previous messages for possible causes.

Severity: 10 : Warning

Explanation: The migration utility found configuration errors for the component. This means that the component

configuration is not correct in some way; previous messages should provide the exact errors.

Response: Examine previous messages, and errors reported during migration steps, to determine the cause of the

failure. The migration may need to be reversed, or completed manually.

BIP8703 Column <insert_0> is missing from database table <insert_1>

Severity: 30 : Severe error

Explanation: Table <insert_1> must have the correct set of columns for this component to function correctly, and

column <insert_0> is missing. This could be because a migration step has not been performed, or because the table

itself has become damaged.

Response: If this broker is being started after a migration, ensure all migration steps have completed successfully. If

this broker is newly created, and the database tables were created manually by a database administrator, ensure all

columns specified are correct.

BIP8704 Column <insert_0> should not be present in database table <insert_1>

Severity: 30 : Severe error

Explanation: Table <insert_1> must have the correct set of columns for this component to function correctly, and an

extra column <insert_0> is present. This could be because a migration step has not been performed, or because the

table itself has become damaged.

Response: If this broker is being started after a migration, ensure all migration steps have completed successfully. If

this broker is newly created, and the database tables were created manually by a database administrator, ensure all

columns specified are correct.

BIP8705 WebSphere MQ queue <insert_0> is missing.

Severity: 30 : Severe error

Explanation: The WebSphere MQ queue manager must have the correct set of queues for this component to

function correctly, and queue <insert_0> is missing. This could be because a migration step has not been performed,

or because the queue manager itself has become damaged.

Response: If this broker is being started after a migration, ensure all migration steps have completed successfully. If

this broker is newly created, and the WebSphere MQ queues were created manually by a WebSphere MQ

administrator, ensure all queues specified are correct.

BIP8706 WebSphere MQ queue <insert_0> exists, but is not accessible; reason code <insert_1>.

Severity: 20 : Error

Explanation: The WebSphere MQ queue manager must have the correct set of queues for this component to

function correctly, and queue <insert_0> is not accessible. This could be because the permissions have been changed,

or because the queue manager itself has become damaged.

Response: If this broker is being started after a migration, ensure all migration steps have completed successfully. If

this broker is newly created, and the WebSphere MQ queues were created manually by a WebSphere MQ

administrator, ensure all queues specified are correct, and the correct permissions. Examine the reason code, and

correct any faults that might lead to this code.

BIP8000 to BIP8999 (Commands) 439

BIP8750 Starting registry migration for component <insert_0>.

Severity: 0 : Information

Explanation: Registry data is being migrated for component <insert_0>.

Response: None.

BIP8751 Created top-level ’CurrentVersion’ key.

Severity: 0 : Information

Explanation: As part of the registry migration, the ’CurrentVersion’ key has been created.

Response: None.

BIP8752 Created <insert_0> subkey

Severity: 0 : Information

Explanation: As part of the registry migration, the <insert_0> key has been created.

Response: None.

BIP8753 Created value named <insert_0>; value data is <insert_1>

Severity: 0 : Information

Explanation: As part of the registry migration, the <insert_0> value has been created and set to <insert_1>

Response: None.

BIP8754 Moving registry data into ’CurrentVersion’

Severity: 0 : Information

Explanation: As part of the registry migration, the legacy data is being moved into the new location.

Response: None.

BIP8755 Copied value <insert_0> into the new location

Severity: 0 : Information

Explanation: As part of the registry migration, the legacy data element <insert_0> is being copied into the new

location.

Response: None.

BIP8756 Finished moving registry data into ’CurrentVersion’

Severity: 0 : Information

Explanation: The registry portion of the migration process has completed.

Response: None.

BIP8757 Error moving registry value <insert_0>: <insert_1>

Severity: 20 : Error

Explanation: An error has occured when moving registry value <insert_0>. The registry migration will now be

reversed.

Response: None.

440 Diagnostic messages

BIP8758 Reversing registry migration for component <insert_0>.

Severity: 10 : Warning

Explanation: Registry data is being unmigrated for component <insert_0>.

Response: None.

BIP8759 Found registry subkey <insert_0> that is not valid in either source or target; left unchanged.

Severity: 10 : Warning

Explanation: During migration, the command found a registry subkey <insert_0> that is not valid in either source or

target version; this value will be left unchanged.

Response: None.

BIP8760 Found registry value <insert_0> that is not valid in either source or target; left unchanged.

Severity: 10 : Warning

Explanation: During migration, the command found a registry value <insert_0> that is not valid in either source or

target version; this value will be left unchanged.

Response: None.

BIP8761 Found registry value <insert_0> for DSN <insert_1> that is not valid in either source or target; left

unchanged.

Severity: 10 : Warning

Explanation: During migration, the command found a registry value <insert_0> in DSN-specific subkey <insert_1>

that is not valid in either source or target version; this value will be left unchanged.

Response: None.

BIP8762 Copied registry value from <insert_0> to HTTP value <insert_1>; set to <insert_2>

Severity: 0 : Information

Explanation: During migration, the command found a registry value <insert_0> whose name must be changed for

the new version into <insert_1>. The value data is still <insert_2>.

Response: None.

BIP8763 Deleted value <insert_0> from the old location

Severity: 0 : Information

Explanation: As part of the registry migration, the legacy data element <insert_0> is being copied into the new

location.

Response: None.

BIP8764 Found registry subkey <insert_0> that is not valid in the source version; left unchanged.

Severity: 10 : Warning

Explanation: During migration, the command found a registry subkey <insert_0> that is not valid in the source

version; this value will be left unchanged.

Response: None.

BIP8000 to BIP8999 (Commands) 441

BIP8765 Found registry value <insert_0> that is not valid in the source version; left unchanged.

Severity: 10 : Warning

Explanation: During migration, the command found a registry value <insert_0> that is not valid in the source

version; this value will be left unchanged.

Response: None.

BIP8766 Copied value <insert_0> for DSN <insert_1> into the new location

Severity: 0 : Information

Explanation: As part of the registry migration, the legacy data element <insert_0> is being copied into the new

location for DSN <insert_1>.

Response: None.

BIP8767 Found registry value <insert_0> that is not valid in the target version; not copied.

Severity: 10 : Warning

Explanation: During migration, the command found a registry value <insert_0> that is not valid in the target

version; this value will not be copied, though no functionality will be lost.

Response: None.

BIP8768 Finished registry migration for component <insert_0>.

Severity: 0 : Information

Explanation: Registry data has been sucessfully migrated for component <insert_0>.

Response: None.

BIP8785 Starting WebSphere MQ queue migration for component <insert_0>.

Severity: 0 : Information

Explanation: Queue data is being migrated for component <insert_0>.

Response: None.

BIP8786 Created WebSphere MQ queue <insert_0>

Severity: 0 : Information

Explanation: As part of the WebSphere MQ queue migration, the queue <insert_0> has been created.

Response: None.

BIP8787 Cleared WebSphere MQ queue <insert_0>

Severity: 0 : Information

Explanation: As part of the WebSphere MQ queue migration, the queue <insert_0> has been cleared of messages.

Response: None.

BIP8788 Deleted WebSphere MQ queue <insert_0>

Severity: 0 : Information

Explanation: As part of the WebSphere MQ queue migration, the queue <insert_0> has been deleted.

Response: None.

442 Diagnostic messages

BIP8789 Finished WebSphere MQ queue migration for component <insert_0>.

Severity: 0 : Information

Explanation: Queue data has been sucessfully migrated for component <insert_0>.

Response: None.

BIP8790 Duplicate rows were detected in table <insert_0>. This will prevent migration from succeeding.

Severity: 30 : Severe error

Explanation: Duplicate rows were detected in table <insert_0>. The destination product requires unique indexes to

be added to the table for correct operation, and duplicate rows will prevent the index add from succeding.

Response: Contact IBM service for more assistance; do not attempt to correct the problem.

BIP8791 Duplicate rows check started.

Severity: 0 : Information

Explanation: The migration utility is checking the broker database for entries that could cause migration to fail.

Response: None.

BIP8792 Duplicate rows check passed.

Severity: 0 : Information

Explanation: No duplicate rows were detected in the broker database.

Response: None.

BIP8793 Duplicate rows check failed.

Severity: 30 : Severe error

Explanation: Duplicate rows were detected in the broker database. See previous errors for more information.

Response: Contact IBM service for more assistance; do not attempt to correct the problem.

BIP8794 Table <insert_0> has no duplicated rows.

Severity: 0 : Information

Explanation: The destination product requires unique indexes to be added to the table for correct operation, and

duplicate rows will prevent the index add from succeding.

Response: None.

BIP8795 A previously migrated Configuration Manager repository found at <insert_0>

Severity: 0 : Information

Explanation: A previously migrated repository will be used by the Configuration Manager being migrated. No

previous configuration data from the DB2 database will be migrated to the Configuration Manager repository when

starting the new Configuration Manager. If you want to fully migrate all existing configuration data from the DB2

database then you must delete the directory <insert_0> before starting the new Configuration Manager.

Response: None.

BIP8796 All configuration data from the DB2 database will be migrated to the new Configuration Manager

repository when the Configuration Manager is first started.

Severity: 0 : Information

Explanation: None.

BIP8000 to BIP8999 (Commands) 443

BIP8797 Topic syntax check succeded

Severity: 0 : Information

Explanation: No topic syntax errors where found in the broker database.

Response: None.

BIP8798 Topic syntax check failed; see previous messages for possible causes.

Severity: 10 : Warning

Explanation: An invalid topic has been found in the Broker Database.

Response: Examine previous messages, and errors reported during migration steps, to determine the cause of the

failure. The migration may need to be reversed, or completed manually.

BIP8799 Invalid topic syntax was detected in table <insert_0>. Topic is <insert_1>. This will prevent migration

from succeeding.

Severity: 20 : Error

Explanation: Invalid topic syntax was detected in table <insert_0>. Topic is <insert_1>. The destination product

requires a new topic syntax and any invalid topic will cause the Broker to be unable to start.

Response: Contact IBM service for more assistance; do not attempt to correct the problem.

BIP8800 No invalid topic syntax was detected in table <insert_0>.

Severity: 0 : Information

BIP8801 Unable to migrate the registry for broker <insert_0>

Severity: 10 : Warning

Explanation: The broker database for the given broker has been migrated successfully, however while attempting to

migrate its registry to the current location a failure occurred.

Response: Migrate this broker’s registry to the current location manually.

BIP8802 Sets the license processor count.

Syntax:

mqsisetcapacity -c processorCount

Severity: 0 : Information

Explanation: Command Options:

’-c processorCount’ is the number of processors on this machine for which WebSphere Message Brokers is licensed.

BIP8803 Displays the license processor count. Syntax : mqsidisplaycapacity

Severity: 0 : Information

Explanation: Shows the processor count entered via the mqsisetcapacity command.

BIP8804 This copy of WebSphere Message Brokers is now running in Production mode.

Severity: 0 : Information

Explanation: A Production license has been installed for this copy of WebSphere Message Brokers.

444 Diagnostic messages

BIP8805 No license installed for this copy of WebSphere Message Brokers.

Severity: 20 : Error

Explanation: No Production license has been installed for this copy of WebSphere Message Brokers.

Response: A valid Production license must be installed before the WebSphere Message Brokers product can be run,

ensure that the product installation completed successfully.

BIP8806 A license could not be installed for this copy of WebSphere Message Brokers.

Severity: 20 : Error

Explanation: A Production license could not be installed for this copy of WebSphere Message Brokers. This is

because the ’nodelock’ file in the ’/bin’ directory could not be created or updated.

Response: Check the ownership and permissions for the ’/bin’ directory.

BIP8807 The Production license for this copy of WebSphere Message Brokers has expired.

Severity: 20 : Error

Explanation: The production license for this copy of WebSphere Message Brokers has an expiry date. This date has

been passed.

Response: Contact your IBM support center.

BIP8808 License file <insert_0> not found or not valid. For more information refer to the WebSphere Message

Brokers online help.

Severity: 20 : Error

Explanation: WebSphere Message Brokers requires that the file <insert_0> is present and available and is a valid

license file. For more information refer to the online help.

Response: Check that the specified file exists.

BIP8809 This copy of WebSphere Message Brokers is already running in Production mode.

Severity: 0 : Information

Explanation: A Production license has previously been installed for this copy of WebSphere Message Brokers.

BIP8810 Insufficient license units.

Severity: 10 : Warning

Explanation: The purchased processor allowance (<insert_0>) is less than the number of processors (<insert_1>) in

this machine.

Response: Ensure sufficient license units have been purchased and use the WebSphere Message Brokers

mqsisetcapacity command to set the purchased processor allowance for this installation. For more information refer

to the online help.

BIP8811 The purchased processor allowance is set to <insert_0>.

Severity: 0 : Information

Explanation: The purchased processor allowance for this installation of WebSphere Message Brokers has been set to

<insert_0> using the mqsisetcapacity command.

BIP8000 to BIP8999 (Commands) 445

BIP8812 The purchased processor allowance is <insert_0>

Severity: 0 : Information

Explanation: The purchased processor allowance is currently set to <insert_0>

Response: Ensure sufficient license units have been purchased and, if necessary, use the WebSphere Message

Brokers mqsisetcapacity command to change the purchased processor allowance for this installation. For more

information refer to the online help.

BIP8813 The number of processors in this machine is <insert_0>

Severity: 0 : Information

Explanation: The operating system reports that the number of processors in this machine is <insert_0>.

BIP8814 The number of license units is sufficient for all future possible upgrades to this machine.

Severity: 0 : Information

Explanation: The purchased processor allowance for this installation of WebSphere Message Brokers has been set to

-1, which allows any permitted processor configuration.

BIP8815 Purchased processor allowance not set (use the mqsisetcapacity command).

Severity: 10 : Warning

Explanation: The purchased processor allowance for this installation has not been set.

Response: Ensure sufficient license units have been purchased for WebSphere Message Brokers and use the

mqsisetcapacity command to set the purchased processor allowance for this installation. For more information refer

to the online help.

BIP8816 QueueManagerName does not exist for component <insert_0>.

Severity: 20 : Error

Explanation: No queues were deleted because QueueManagerName does not exist in the component registry.

Response: Ensure the component registry is correct and has not been deleted. Recreate the component registry if

necessary.

BIP8817 DataSourceName does not exist for component <insert_0>.

Severity: 20 : Error

Explanation: No database rows were deleted because DataSourceName does not exist in the component registry.

Response: Ensure the component registry is correct and has not been deleted. Recreate the component registry if

necessary.

BIP8818 Creates queues on a WebSphere MQ queue manager for use with a migrated broker.

Syntax:

mqsimigratequeues brokerName

Severity: 10 : Warning

Explanation: Command options

’brokerName’ the name of broker whose queues are to be migrated.

BIP8819 Migrates WebSphere MQ queues for brokers. Syntax: mqsimigratequeues

Severity: 10 : Warning

Explanation: Creates queues on a WebSphere MQ queue manager for use with a migrated broker.

446 Diagnostic messages

BIP8820 Enter password for userid

Severity: 10 : Warning

Explanation: This is used to prompt for a password for service userid on the console.

Response: Enter password for userid

BIP8821 Enter password for database userid

Severity: 10 : Warning

Explanation: This is used to prompt for a password for service userid on the console.

Response: Enter password for database userid

BIP8822 The supplied password is invalid. Ensure that the password is within the range of 2 - 255 characters

in length.

Severity: 10 : Warning

Explanation: Re-enter the password.

BIP8823 Retype password for userid

Severity: 10 : Warning

Explanation: This is used to prompt for a password for service userid on the console.

Response: Retype password for userid

BIP8824 Retype password for database userid

Severity: 10 : Warning

Explanation: This is used to prompt for a password for service userid on the console.

Response: Retype password for database userid

BIP8825 Passwords do not match.

Severity: 10 : Warning

Explanation: Passwords do not match.

Response: Passwords do not match.

BIP8827 Creates a broker.

Syntax:

mqsicreatebroker brokerName -q queueManagerName -n dataSourceName -u dataSourceUserId [-l

userLilPath] [-1 | -2 | -3] [-s unsQMgrName [-j]] [-g configurationTimeout] [-k

configurationDelayTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-y ldapPrincipal -z

ldapCredentials] [-x userExitPath]

Severity: 10 : Warning

Explanation: Command Options

’brokerName’ name of the broker to create

’-q queueManagerName’ the WebSphere MQ Queue Manager that the broker should use

’-1’ creates only the broker’s registry

’-2’ creates only the broker’s WebSphere MQ resources

’-3’ creates only the broker’s database resources

’-n dataSourceName’ the broker’s database name

’-u dataSourceUserId’ the userid that the broker uses to access its database

’-l userLilPath’ the directory from which the broker searches for user-supplied libraries

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

BIP8000 to BIP8999 (Commands) 447

’-j’ indicates that Publish/Subscribe access control is to be enabled for this broker

’-g configurationTimeout’ the maximum time (in seconds) to allow a broker to process a deployed message

’-k configurationDelayTimeout’ the maximum time (in seconds) to allow a broker to process a minimum size

deployed message

’-v statisticsMajorInterval’ the time (in minutes) for the duration of the interval for collecting statistics archive records

’-P httpListenerPort’ the port that the broker HTTP listener will use.

’-y ldapPrincipal’ the LDAP Principal (userId)

’-z ldapCredentials’ the LDAP Credentials (password)

’-x userExitPath’ the directory from which the broker searches for all user exits. This path will be added to the

system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.

BIP8828 Deletes a broker.

Syntax:

mqsideletebroker brokerName [-1 | -2 | -3]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker to delete

’-1’ deletes only the broker’s registry.

’-2’ deletes only the broker’s WebSphere MQ queues.

’-3’ deletes only the broker’s database resources.

BIP8829 Creates the User Name Server.

Syntax:

mqsicreateusernameserver -q queueManagerName [-1 | -2] [-r refreshInterval] [-g

authProtocolDataSource] [-j]

Severity: 10 : Warning

Explanation: Command Options:

’-q queueManagerName’ the WebSphere MQ queue manager that the User Name Server should use.

’-1’ only creates the User Name Server’s registry.

’-2’ only creates the User Name Server’s WebSphere MQ resources.

’-r refreshInterval’ number of seconds between each refresh of the User Name Server internal cache.

’-g authProtocolDataSource’ the name of the data source required by the authentication protocol

’-j’ indicates that groups and group memberships will be defined in the data source for the authentication protocol

rather than drawn from the Operating System.

BIP8830 Deletes the User Name Server.

Syntax:

mqsideleteusernameserver [-1 | -2]

Severity: 10 : Warning

Explanation: Command Options

’-1’ deletes only the User Name Server’s registry.

’-2’ deletes only the User Name Server’s WebSphere MQ queues.

BIP8831 Creates the Configuration Manager.

Syntax:

mqsicreateconfigmgr configMgrName -q queueManagerName [-1 | -2] [-n db2DatabaseToMigrate -u

migrationDataBaseUserId -p migrationDataBasePassword] [-s unsQMgrName]

Severity: 10 : Warning

Explanation: Command Options

’configMgrName’ name of the Configuration Manager

’-q queueManagerName’ the Configuration Manager’s WebSphere MQ queue manager

’-1’ creates only the Configuration Manager’s registry.

’-2’ creates only the Configuration Manager’s WebSphere MQ resources.

’-n db2DatabaseToMigrate’ the DB2 database name, used only for migration from earlier versions.

’-u migrationDataBaseUserId’ the userid that the Configuration Manager uses to access the DB2 database.

448 Diagnostic messages

’-p migrationDataBasePassword’ the password for the DB2 database userid.

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server.

BIP8832 Deletes the Configuration Manager.

Syntax:

mqsideleteconfigmgr (-1 | -2) [-n]

Severity: 10 : Warning

Explanation: Command Options

’-1’ deletes only the Configuration Manager’s registry

’-2’ deletes only the Configuration Manager’s WebSphere MQ queues

’-n’ indicates that the Configuration Manager table should be deleted; use with caution.

BIP8833 Changes a broker’s configuration.

Syntax:

mqsichangebroker brokerName [-s unsQMgrName] [-j | -d] [-l userLilPath] [-g

configurationTimeout] [-k configurationDelayTimeout] [-v statisticsMajorInterval] [-P

httpListenerPort] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-j’ indicates that Publish/Subscribe access control is to be enabled for this broker

’-d’ indicates that Publish/Subscribe access control is to be disabled for this broker

’-l userLilPath’ indicates where ’lil’ files are loaded from

’-g configurationTimeout’ the maximum time (in seconds) to allow a broker to process a deployed message

’-k configurationDelayTimeout’ the maximum time (in seconds) to allow a broker to process a minimum size

deployed message

’-v statisticsMajorInterval’ the time (in minutes) for the duration of the interval for collecting statistics archive records

’-P httpListenerPort’ the port that the broker HTTP listener will use.

’-y ldapPrincipal’ the LDAP Principal (userId)

’-z ldapCredentials’ the LDAP Credentials (password)

’-x userExitPath’ the directory from which the broker searches for all user exits. This path will be added to the

system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.

’-e activeUserExits’ the active user exits. By default, user exits are inactive. Adding a userExit name to this list,

changes its default state to active for this broker. The default state can be overridden at the execution group or

message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found

to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and

the execution group will fail to start.

BIP8834 Changes a User Name Server’s configuration.

Syntax:

mqsichangeusernameserver -r refreshInterval [-g authProtocolDataSource] [-j | -o]

Severity: 10 : Warning

Explanation: Command Options:

’-r refreshInterval’ number of seconds between each refresh of the User Name Server internal cache.

’-g authProtocolDataSource’ the name of the data source required by the authentication protocol

’-j’ indicates that groups and group memberships will be defined in the data source for the authentication protocol

(rather than drawn from the Operating System)

’-o’ indicates that groups and group memberships will be drawn from the Operating System (rather than defined in

the data source for the authentication protocol).

BIP8000 to BIP8999 (Commands) 449

BIP8835 Changes a Configuration Manager’s configuration.

Syntax:

mqsichangeconfigmgr configMgrName [-s unsQMgrName] [-j MaxJVMHeapSize]

Severity: 10 : Warning

Explanation: Command Options:

’configMgrName’ Name of the Configuration Manager

’-s unsQMgrName’ the WebSphere MQ queue manager of the User Name Server

’-j MaxJVMHeapSize’ the maximum Java virtual machine heap size, in megabytes (default=256) (minimum=64).

BIP8836 Changes a Configuration Manager’s configuration. Syntax: changeconfigmgr [s=unsQMgrName]

[j=MaxJVMHeapSize]

Severity: 10 : Warning

Explanation: Command Options:

’s=unsQMgrName’ the WebSphere MQ queue manager of the User Name Server.

’j=MaxJVMHeapSize’ the maximum Java virtual machine heap size, in megabytes (default=256) (minimum=64).

BIP8837 Creates a security Access Control Entry in the Configuration Manager repository. Syntax:

createaclentry (f=fileName | ((g=groupName | (u=userName (m=machineName | a=yes)))

x=accessLevel ((b=broker [e=executionGroup]) | s=yes | r=yes | t=yes | p=yes))) [w=timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’f=fileName’ File containing list of Access Control Entries to create

’g=groupName’ Add Access Control Entry for the specified group

’u=userName’ Add Access Control Entry for the specified user (must be accompanied by either a=yes or

m=machineName)

’m=machineName’ Add the Access Control Entry for the user for this specific machine/domain name only

’a=yes’ Add an Access Control Entry for this user for all machines/domains

’p=yes’ Add access to the ConfigManagerProxy. Also known as the ″All resources″ Access Control Entry

’x=accessLevel’ desired security access level for specified object (D, E, V, F)

’b=broker’ Add access to the specified broker

’e=executionGroup’ Add access to the specified execution group (must be accompanied by b=broker)

’s=yes’ Add access to the subscriptions table

’r=yes’ Add access to the root topic

’t=yes’ Add access to the pub/sub topology

’w=timeoutValue’ value in seconds to wait for responses.

BIP8838 Deletes a security Access Control Entry in the Configuration Manager repository. Syntax:

deleteaclentry (f=fileName | ((g=groupName | (u=userName (m=machineName | a=yes)))

((b=broker [e=executionGroup]) | s=yes | r=yes | t=yes | p=yes))) [w=timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’f=fileName’ File containing list of Access Control Entries to delete.

’g=groupName’ Delete Access Control Entry for the specified group

’u=userName’ Delete Access Control Entry for the specified user (must be accompanied by either a=yes or

m=machineName)

’m=machineName’ Delete the Access Control Entry for the specified user which applies to this specific

machine/domain name only

’a=yes’ Delete the ″All machines/domains″ Access Control Entry for the specified user

’p=yes’ Delete access to the ConfigManagerProxy. Also known as the ″All resources″ Access Control Entry.

’b=broker’ Delete Access Control Entry for the specified broker

’e=executionGroup’ Delete Access Control Entry for the specified execution group (must be accompanied by

b=broker)

’s=yes’ Delete subscriptions Access Control Entry

’r=yes’ Delete root topic Access Control Entry

450 Diagnostic messages

’t=yes’ Delete pub/sub topology Access Control Entry

’w=timeoutValue’ value in seconds to wait for responses.

BIP8839 Lists the security Access Control Entries in the Configuration Manager repository. Syntax:

listaclentry [g=groupName | (u=userName (m=machineName | a=yes))] [(b=broker

[e=executionGroup]) | s=yes | r=yes | t=yes | p=yes] [f=fileName] [w=timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’f=fileName’ Output list of Access Control Entries to given filename

’g=groupName’ Display Access Control Entries for the specified group

’u=userName’ Display Access Control Entries for the specified user (must be accompanied by either a=yes or

m=machine)

’m=machineName’ Display Access Control Entries for the specified user which apply to this specific

machine/domain name only

’a=yes’ Display only those Access Control Entries for the specified user which apply to ALL machines/domain names

’p=yes’ Display Access Control Entries for the ConfigManagerProxy. Also known as the ″All resources″ Access

Control Entries

’b=broker’ Display Access Control Entries for the specified broker

’e=executionGroup’ Display Access Control Entries for the specified execution group (must be accompanied by

b=broker)

’s=yes’ Display Access Control Entries for the subscriptions table

’r=yes’ Display Access Control Entries for the root topic

’t=yes’ Display Access Control Entries for the pub/sub topology

’w=timeoutValue’ value in seconds to wait for responses.

BIP8840 Deploys pub/sub topology, topics or BAR file configuration data to the specified broker(s). Syntax:

deploy ((b=brokerName [e=executionGroupName [a=BARFileName | d=deployedObjects]]) | l=yes

| t=yes | c=yes | m=yes) [w=timeoutValue] [v=traceFile]

Severity: 10 : Warning

Explanation: Command Options:

’b=brokerName’ name of broker to deploy to

’e=executionGroupName’ name of execution group to deploy to

’a=BARFileName’ deploy the specified Broker Archive file

’d=deployedObjects’ colon separated list of deployed objects to remove

’l=yes’ deploy Topology configuration to all brokers

’t=yes’ deploy Topics configuration to all brokers

’c=yes’ cancel all outstanding deploy requests

’m=yes’ deploy complete information (default is to perform incremental deploy; changes to the deployed state)

’w=timeoutValue’ value in seconds to wait for the broker to reply to the deploy request

’v=traceFile’ send verbose internal trace to the specified file.

BIP8841 Deploys pub/sub neighbors, topics or BAR file configuration data to the specified broker(s).

Syntax 1 (deploy pub/sub neighbors):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -l [-m] [-w timeoutValue] [-v

traceFileName]

Syntax 2 (deploy topics hierarchy):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -t [-m] [-w timeoutValue] [-v

traceFileName]

Syntax 3 (deploy BAR file):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName -e

executionGroupName -a BARFileName [-m] [-w timeoutValue] [-v traceFileName]

Syntax 4 (deploy broker configuration):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName [-w

timeoutValue] [-v traceFileName]

Syntax 5 (remove previously deployed objects):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -b brokerName -e

executionGroupName -d deployedObjects [-w timeoutValue] [-v traceFileName]

BIP8000 to BIP8999 (Commands) 451

Syntax 6 (cancel deployment):

mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -c [-b brokerName] [-w

timeoutValue] [-v traceFileName]

Severity: 0 : Information

Explanation: Command Options:

’-n cfgParameterFileName’ Configuration Manager connection parameters (.configmgr)

’-i ipAddress’ IP address or hostname of the Configuration Manager

’-p port’ port number of the Configuration Manager

’-q queueManager’ queue manager of the Configuration Manager

’-b brokerName’ name of broker to deploy to

’-e executionGroupName’ name of execution group to deploy to

’-a BARFileName’ deploy the specified Broker Archive file

’-d deployedObjects’ remove a colon separated list of deployed objects from the execution group

’-c’ tells the Configuration Manager to stop waiting for broker responses to currently outstanding deploy requests,

across the domain or on the specified broker. Use this flag with caution; any subsequent responses to cancelled

deploys will be ignored by the Configuration Manager, meaning that the status reported by the Configuration

Manager may be incorrect.

’-l’ deploy pub/sub neighbor (topology) configuration to all brokers

’-t’ deploy topics hierarchy to all brokers

’-m’ deploy complete information (default is to perform incremental deploy; changes to the deployed state)

’-w timeoutValue’ value in seconds to wait for the broker to reply to the deploy request

’-v traceFileName’ send verbose internal trace to the specified file.

BIP8842 Invalid options for ConfigMgr ignored.

Severity: 10 : Warning

Explanation: From version 6.0 of Message Brokers, the -l and -d options are no longer valid for mqsicreateconfigmgr

and mqsichangeconfigmgr. For most purposes in which non-default values were used on these commands, an

equivalent effect can be achieved in V6.0 onwards by appropriate use of the -a and/or -m options on the

mqsicreateaclentry command.

Response: No action is required, the command will safely ignore the -d or -l parameter.

BIP8843 Creates a security Access Control Entry in the Configuration Manager repository.

Syntax:

mqsicreateaclentry configMgrName (-f fileName | ((-g groupName | (-u userName (-m

machineName | -a))) -x accessLevel ((-b broker (-e executionGroup)) | -s | -t | -r | -p))) [-n

connectionFile] [-w timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’configMgrName’ name of the Configuration Manager (may be omitted on Windows)

’-f fileName’ File containing list of Access Control Entries to create.

’-g groupName’ Add Access Control Entry for the specified group

’-u userName’ Add Access Control Entry for the specified user (must be accompanied by either -a or -m)

’-m machineName’ Add the Access Control Entry for the user for this specific machine/domain name only

’-a’ Add an Access Control Entry for the user for all machines/domains

’-x accessLevel’ Level of authority to grant (F, E, D, V)

’-b broker’ Add access to the specified broker

’-e executionGroup’ Add access to the specified execution group (must be accompanied by -b)

’-s’ Add access to the subscriptions table

’-t’ Add access to the pub/sub topology

’-r’ Add access to the root topic

’-p’ Add access to the ConfigManagerProxy. Also known as the ″All resources″ Access Control Entry.

’-w timeoutValue’ value in seconds to wait for responses.

’-n connectionFile’ Optional ″connection file″ to allow the command to communicate with a remote ConfigMgr.

Note: On Windows platforms, if the Configuration Manager name is omitted ’ConfigMgr’ will be used.

452 Diagnostic messages

BIP8844 Deletes a security Access Control Entry in the Configuration Manager repository.

Syntax:

mqsideleteaclentry configMgrName (-f fileName | ((-g groupName | -u userName (-m

machineName | -a)) ((-b broker [-e executionGroup]) | -s | -t | -r | -p))) [-n connectionFile] [-w

timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’configMgrName’ name of the Configuration Manager (may be omitted on Windows)

’-f fileName’ File containing list of Access Control Entries to delete.

’-g groupName’ Delete Access Control Entry for the specified group

’-u userName’ Delete Access Control Entry for the specified user (must be accompanied by either -a or -m)

’-m machineName’ Delete the Access Control Entry for the specified user which applies to this specific

machine/domain name only

’-a’ Delete the ″ALL machines/domains″ Access Control Entry for the specified user

’-b broker’ Delete Access Control Entry for the specified broker

’-e executionGroup’ Delete Access Control Entry for the specified execution group (must be accompanied by -b)

’-s’ Delete subscriptions Access Control Entry

’-t’ Delete pub/sub topology Access Control Entry

’-r’ Delete root topic Access Control Entry

’-p’ Delete Access Control Entry for the ConfigManagerProxy. Also known as the ″All resources″ Access Control

Entry.

’-w timeoutValue’ value in seconds to wait for responses.

’-n connectionFile’ Optional ″connection file″ to allow the command to communicate with a remote ConfigMgr.

Note: On Windows platforms, if the Configuration Manager is omitted ’ConfigMgr’ will be used.

BIP8845 Lists the security Access Control Entries in the Configuration Manager repository.

Syntax:

mqsilistaclentry configMgrName [-g groupName | (-u userName (-m machineName | -a))] [(-b

broker [-e executionGroup]) | -s | -t | -r | -p] [-f filename] [-n connectionFile] [-w timeoutValue]

Severity: 10 : Warning

Explanation: Command Options:

’configMgrName’ name of the Configuration Manager (may be omitted on Windows)

’-g groupName’ Display Access Control Entries for the specified group

’-u userName’ Display Access Control Entries for the specified user (must be accompanied by either -a or -m)

’-m machineName’ Display Access Control Entries for the specified user which apply to this specific

machine/domain name only

’-a’ Display only those Access Control Entries for the specified user which apply to ALL machines/domain names

’-b broker’ Display Access Control Entries for the specified broker

’-e executionGroup’ Display Access Control Entries for the specified execution group (must be accompanied by -b)

’-s’ Display Access Control Entries for the subscriptions table

’-t’ Display Access Control Entries for the pub/sub topology

’-r’ Display Access Control Entries for the root topic.

’-p’ Display Access Control Entries for the ConfigManagerProxy. Also known as the ″All resources″ Access Control

Entries.

’-f filename’ Output list of Access Control Entries to given filename rather than to the screen.

’-w timeoutValue’ value in seconds to wait for responses.

’-n connectionFile’ Optional ″connection file″ to allow the command to communicate with a remote ConfigMgr.

Note: On Windows platforms, if the Configuration Manager name is omitted ’ConfigMgr’ will be used.

BIP8846 Configuration data for component <insert_0> is not usable by this product version (level <insert_1>;

should be <insert_2>).

Severity: 30 : Severe error

Explanation: Each component has configuration data associated with it, and this data is versioned to ensure that the

component can only be run under a product version that supports this level. The component level is <insert_1> and

the current code level only supports <insert_2>.

BIP8000 to BIP8999 (Commands) 453

BIP8847 migrates a components queues, registry, database and file-system information between different

versions.

Syntax:

mqsimigratecomponents componentName [ -s sourceVersion ] [ -t targetVersion ] [ -c ] [ -1 ] [ -2 ] [ -3

] [ -v ] [ -q ] [ -u ]

Severity: 10 : Warning

Explanation: Command Options:

’componentName’ is the name of the component to query for its registry data

’-s sourceVersion’ The current version of the component.

’-t targetVersion’ The version of the component to migrate to.

’-c’ Do a pre-migration check of the specified component. This will attempt to determine whether the current state of

the component is such that it can be safely migrated.

’-1’ Do only registry and file-system related migration work. Use this when security restrictions prevent the

command from migrating WebSphere MQ, registry and file-system and database in one step.

’-2’ Do only WebSphere MQ related migration work. Use this when security restrictions prevent the command from

migrating WebSphere MQ, registry and file-system and database in one step.

’-3’ Do only database related migration work. Use this when security restrictions prevent the command from

migrating WebSphere MQ queues, registry and file-system and database in one step.

’-v’ Do a post-migration check of the specified component. This will double-check whether the migration has

completed successfully.

’-q’ reduce the verbosity of the progress of the command.

’-u’ Undo a failed migration step. At least one of -1, -2 or -3 must also be specified. This should only be used when

migration has failed, and also failed to auto-recover.

BIP8848 Invalid version <insert_0>.<insert_1>.<insert_2>.<insert_3> supplied.

Severity: 30 : Severe error

Explanation: The supplied version is not compatible to migrate to or from with this component.

Response: Check that the string given to the ’-s’ or ’-t’ argument is of the form

<version>.<release>.<modification>.<fix>.

The minimum supported versions for migration to or from WebSphere Message Brokers Version 6.0 are:

- WebSphere MQ Event Broker or WebSphere MQ Integrator Broker or WebSphere MQ Integrator, Version 2.1 with fix

pack 02 or later

- WebSphere Business Integration Event Broker or WebSphere Business Integration Message Broker or WebSphere

Business Integration Message Broker with Rules and Formatter Extension, Version 5.0 with fix pack 04 or later

Version 2.1 fix pack 02 is identified by the four digit version number 2.1.0.3

Version 5.0 fix pack 04 is identified by the four digit version number 5.0.0.4

If the version has already been specified correctly the component cannot be automatically migrated.

BIP8849 Broker <insert_0> (Version <insert_3>.<insert_4>) with Queue Manager <insert_1> and Data Source

<insert_2> specified for migration.

Severity: 0 : Information

BIP8850 Displays broker property settings.

Syntax:

mqsireportodbcconnectioninfo -q dsn1 -u userName1 -p password1 [-c dsn2 -i userName2 -a

password2] [-v]

Severity: 10 : Warning

Explanation: Command Options:

’-q dsn1’ First DataSource to query

’-u userName1’ Username to use when connecting to DSN1

’-p password1’ Password to use when connecting to DSN1

’-c dsn2’ Second DataSource to compare to DSN1

’-i userName2’ Username to use when connecting to DSN2

’-a password2’ Password to use when connecting to DSN2

’-v’ verbose output

454 Diagnostic messages

Specifing only -q provides ODBC information about DSN1. If -c is also specified then DSN2 is compared to DSN1 for

equality of functionality.

BIP8851 Migration Failed

Severity: 30 : Severe error

Explanation: One of the migration steps failed, please see messages above for more details.

BIP8852 sets list of active or inaction user exits.

Syntax:

mqsichangeflowuserexits brokerName -e egName [-f messageFlowName] (-a activeUserExitList |-i

inactiveUserExitList)

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-e egName’ name of the execution group

’-f messageFlowName’ name of message flow

’-a activeUserExitList’ colon separated list of names of user exits to be set to active state

’-i inactiveUserExitList’ colon separated list of names of user exits to be set to inactive state

The command will not alter the existing vlaue of a user exit list, if the corresponding name/value pair is not

specified. To clear a user exit list, use an empty string (″″), e.g., ’-i ″″’.

BIP8853 queries the lists of active and inactive user exits.

Syntax:

mqsireportflowuserexits brokerName [-e egName [-f messageFlowName]]

Severity: 10 : Warning

Explanation: Command Options:

’brokerName’ name of the broker

’-e egName’ name of the execution group

’-f messageFlowName’ name of message flow

BIP8854 User Exits active for Execution Group <insert_0>: <insert_1>.

Severity: 0 : Information

BIP8855 User Exits inactive for Execution Group <insert_0>: <insert_1>.

Severity: 0 : Information

BIP8856 User Exits active for Message Flow <insert_0>: <insert_1>.

Severity: 0 : Information

BIP8857 User Exits inactive for Message Flow <insert_0>: <insert_1>.

Severity: 0 : Information

BIP8858 Invalid user exit name <insert_0> specified

Severity: 20 : Error

Explanation: User exit name <insert_0> specified on the <insert_1> flag does not correspond to any user exit

available to the target execution group.

Response: Review the name provided. If the name is incorrect, reissue the command with the correct name. If the

name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for

MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes

BIP8000 to BIP8999 (Commands) 455

the directory containing the user exit library. Check system log when execution group starts for errors loading the

user exit library.

BIP8859 User Exits active for broker <insert_0>: <insert_1>.

Severity: 0 : Information

BIP8860 User Exit <insert_0> not found