MQSeries Integrator

Messages
V ersion 2.0.2

GC34-5601-02

MQSeries Integrator

Messages
V ersion 2.0.2

GC34-5601-02

Note! Before using this information and the product it supports, be sure to read the general information under Appendix. Notices on page 153.

Third edition (April 2001) This edition applies to IBM MQSeries Integrator Version 2 and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2000,2001. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
About this book . . . . . . . . . . . v
Terms used in this book Who this book is for. . How to use this book . Reading a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v v v v BIP7000-BIP7999 (Publish Subscribe). BIP8000-BIP8199 (Commands) . . . . . . . . . . . . 115 . 127

Appendix. Notices . . . . . . . . . 153

Trademarks . . . . . . . . . . . . . . 155

Chapter 1. Contacting Your IBM Support Center . . . . . . . . . . . . . . . 1 Chapter 2. Messages . . . . . . . . . 3

BIP0001-BIP0999 BIP1000-BIP1999 BIP2000-BIP2999 BIP3000-BIP3999 BIP4000-BIP4999 BIP5000-BIP5999 BIP6000-BIP6999 (Control Center) . . . . . (Configuration Manager) . . (Broker) . . . . . . . . (IBM Primitives) . . . . . (IBM Primitives) . . . . . (Parsers) . . . . . . . (MQSeries and NEON Parsers) . . . . . . . 3 . 11 . 43 . 82 . 84 . 94 111

Bibliography . . . . . . . . . . . . 157
MQSeries Integrator Version 2.0.2 cross-platform publications . . . . . . . . . . . . . . MQSeries Integrator Version 2.0.2 platform-specific publications . . . . . . . . . . . . . . MQSeries Everyplace publications . . . . . . NEONRules and NEONFormatter Support for MQSeries Integrator publications . . . . . . . Softcopy books . . . . . . . . . . . . . Portable Document Format (PDF) . . . . . MQSeries information available on the Internet . . 157 157 157 157 158 158 159

Copyright IBM Corp. 2000,2001

iii

iv

MQSeries Integrator Messages

About this book

This book describes the user messages returned by the MQSeries products listed below, with explanations and suggested actions. It is designed for use as a quick reference. This book applies to the following MQSeries Integrator products: v MQSeries Integrator for Windows NT Version 2.0.2 v MQSeries Integrator for Sun Solaris Version 2.0.2 v MQSeries Integrator for AIX Version 2.0.2 v MQSeries Integrator for HP-UX Version 2.0.2

Terms used in this book

All references in this book to Windows NT are also applicable to Windows 2000 unless otherwise stated. MQSeries Integrator components that are installed and operated on Windows NT can also be installed and operated on Windows 2000.

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 MQSeries Integrator user messages.

How to use this book

MQSeries Integrator user messages are numbered BIP0001 through BIP8999, 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 an MQSeries Integrator user message is: v The message identifier, in three parts: 1. The characters BIP which identify the message as being from MQSeries Integrator 2. A four-digit decimal code 3. A letter indicating the severity of the message. The letter will be one of the following: I: This is an information message W: This is a warning message E: This is an error message S: This is a severe error message v The text of the message

Message information
For each message, this information is provided: Explanation: Why the message was issued. User action: Instructions to the user.
Copyright IBM Corp. 2000,2001

Reading a message

Message variables
Some messages display text or numbers that vary according to the circumstances giving rise to the message; these are known as message variables. The message variables are indicated in this book by the use of the & symbol and a number: &1, &2, and so on. In some cases a message may have variables in the Explanation or User action. Find the values of the message variables by looking in your local error or system log. On Windows NT the complete message, including the explanation and user action, will be recorded in the Event log. Syslog on Sun Solaris, HP-UX, and AIX will only record the message. Note: Always look at the whole message as shown in this book, including the Explanation and the User action, before taking any action.

vi

MQSeries Integrator Messages

Chapter 1. Contacting Your IBM Support Center

If you are unable to resolve problems that you find when you use MQSeries Integrator, or if you are directed to do so by an error message generated by MQSeries Integrator, you can request assistance from your IBM support center. Before you contact them, use the checklist below to gather key information. Some items may not necessarily be relevant in every situation. But you should provide as much information as possible to enable the IBM support center to recreate your problem. v For MQSeries Integrator: CSDs applied. E-fixes applied. All current trace and error logs, including relevant Windows NT Event log or UNIX platform syslog entries. User trace log files at debug level should be obtained for all relevant message flows and should preferably be formatted. A list of the components installed. This should include details of the number of machines and their operating systems, the number of brokers and the machine on which they are running, and the existence and details of any User Name Servers. The file obtained by exporting your workspace. This action is performed from the Control Center; see the MQSeries Integrator Using the Control Center manual for details of how to do this. The files obtained by exporting all relevant message sets. This action is performed for each message set by using the mqsiimpexpmsgset command with the -e flag set. A sample of the messages being used when the problem arose. If relevant, the report file from the C or COBOL importer. This is located in the directory from which the file import was attempted. v For MQSeries: CSDs applied. E-fixes applied. All current trace and error logs, including relevant Windows NT Event log or UNIX platform syslog entries and First Failure Support Technology(TM) (FFST(TM)) output files. You can find these files, which have the extension FDC, in the errors subdirectory within the MQSeries home directory. Details of MQSeries client software, if appropriate. v For each database you are using: Product and release level (for example, DB2 7.1). CSDs applied. E-fixes applied. All current trace and error logs, including relevant Windows NT Event log or UNIX platform syslog entries and First Failure Support Technology (FFST) output files. Check database product documentation for where to find these files.

Copyright IBM Corp. 2000,2001

Contacting IBM
v For Windows NT: Version. Service Pack level. The version of the system files msvcrt.dll, msvcp60.dll, msvcirt.dll, and mfc42.dll. You can find these files in the WINNT\SYSTEM32 directory. Use the Windows NT Explorer file properties to display the versions. v For Sun Solaris: Version. You can find the version of Sun Solaris installed by using the uname -a command. Service level applied. v For AIX: Version. You can find the version of AIX installed by using the uname -a command. For more detailed information about the lslpp -l bos.rte command, see the MQSeries Integrator Administration Guide. | | | | Service level applied. v For HP-UX: Version. You can find the version of HP-UX installed by using the uname -a command. Service level applied. v Details of the operation you were performing, the results that occurred, and the results you were expecting.

MQSeries Integrator Messages

Chapter 2. Messages
BIP0001-BIP0999 (Control Center)
BIP0003E Cannot add the XML element &0. Explanation: This is an internal error. The insertion of this XML element is not permitted as it does not conform to the Document Type Definition. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0004E Cannot create or add the XML element &0. Explanation: An XML element by that name already exists. User Response: Try again with a different name. BIP0005E An invalid request was received. Explanation: This is an internal error. The method was: &0. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0006E Incorrect parameters were supplied. Explanation: This is an internal error. The method was: &0. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0006E Incorrect parameters were supplied. Explanation: This is an internal error. The method was: &0. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0007E Cannot create or add the object with identifier &0. Explanation: An object by that identifier already exists. User Response: Try again with a different identifier. BIP0009E The format of the URL is invalid. Explanation: Either no legal protocol could be found or the string could not be parsed. The URL was: &0. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0010E Unknown host &0. Explanation: The IP address of a host could not be determined. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0011E An error in the underlying protocol occurred, such as a TCP error. Explanation: This could be a TCP error. The resource path was: &0. The message from the exception was: &1. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0012E NotBoundException: a communication error occurred. Explanation: The resource path was: &0. The message from the execption was: &1. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0013E The resource &0 has never been checked in. Explanation: A resource that has never been checked in cannot be locked or checked out. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0014E The XML document is missing a root element. Explanation: This is an internal error. The XML document has an invalid internal structure: &0. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0015E An I/O error occurred when accessing the document. Explanation: The URL was: &0. The I/O Exception message was: &1. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center.

Copyright IBM Corp. 2000,2001

BIP0016E BIP0034E
BIP0016E The XML element &0 has no owning document. Explanation: This is an internal error. The XML element has an invalid internal structure. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0017E The XML element &0 does not contain a UUID. Explanation: This is an internal error. The XML element has an invalid internal structure. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0018E The XML element &0 has no parent. Explanation: This is an internal error. The XML element has an invalid internal structure. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0019E An attempt to dynamically load a Java class failed. Explanation: This is an internal error. The class &0 was found but could not be instantiated. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0027E Cannot load a properties file. Explanation: This is an internal error. The properties file &0 could not be loaded. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0028E Cannot replace the XML element &0. Explanation: This is an internal error. The XML element &1 does not conform to the Document Type Definition. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0029E Cannot delete the XML element &0. Explanation: This is an internal error. The XML element is required by the Document Type Definition. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0030E Cannot modify the resource &0. Explanation: The resource cannot be modified because it has not been checked out to you. User Response: You must check out the resource. BIP0031E Cannot check out the resource &0. Explanation: The resource has already been checked out. Locking userid: &1, Locking user workstation: &2. User Response: No user action required. BIP0032E Cannot check out the resource &0. Explanation: This is a new resource you have just created. It has never been saved and never been checked in. User Response: You can modify the resource, but you must save and check it in before you can check it out. BIP0033E Cannot check in the resource &0. Explanation: The resource has not been checked out to you. User Response: No user action required. BIP0034E Cannot create the WebDAV document &0. Explanation: This is an internal error. The WebDAV document already exists. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center.

BIP0020E

An attempt to dynamically load a Java class failed. Explanation: This is an internal error. The class &0 was found but access was denied. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0021E The file does not exist. Explanation: The file &0 could not be located. User Response: Verify the file exists and try again. BIP0022E The XML element &0 has no parent. Explanation: This is an internal error. The XML element has an invalid internal structure. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0025E Missing document property. Explanation: The document &0 is expected to have the attribute: &1. User Response: The WebDAV (.wdp) properties file may be missing or it may not contain the property &1.

MQSeries Integrator Messages

BIP0035E BIP0056E
BIP0035E The XML element &0 is not a reference. Explanation: This is an internal error. A reference was expected. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0036E Cannot delete the resource &0. Explanation: The resource has been checked out. Locking userid: &1, Locking user workstation: &2. User Response: The resource must be checked-in to be deleted. BIP0038E Cannot find resource &1. Explanation: The resource type &0 could not be found at that location. The resource may have been deleted. User Response: You can remove this resource from your workspace. BIP0040E The XML element &0 does not contain an ID. Explanation: This is an internal error. The XML element has an invalid internal structure. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0042E The XML element is missing an <href> attribute. Explanation: This is an internal error. The XML element type &0 named &1 is expected to have an <href> XML attribute. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0043E Cannot lock the resource &0. Explanation: The resource has already been locked. The locking userid is: &1, The locking user workstation is: &2. User Response: Wait until the resource has been unlocked. BIP0044E Cannot unlock the resource &0. Explanation: The resource has not been locked by you. The locking userid is: &1, The locking user workstation is: &2. User Response: You cannot unlock a resource that you did not lock. BIP0045E Cannot lock the resource &0. Explanation: This is a new resource you have just created. It has never been saved and never been checked in. User Response: You can modify the resource, but you must save and check it in before you can lock it. BIP0046E Cannot unlock the resource &0. Explanation: This is a new resource you have just created. It has never been saved and never been checked in. User Response: You can modify the resource or check it in. BIP0047I Cannot unlock the resource &0. Explanation: The resource has not been locked. User Response: You can check out or lock the resource. BIP0052E The file &0 cannot be updated. Explanation: The file cannot be written to, it may be read only. User Response: Verify the file can be written to and try again. BIP0053E The file &0 cannot be updated. Explanation: An I/O error occurred when accessing the file. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0054E Cannot open message catalog file &0. Explanation: The message catalog file could not be opened. The text for the message &1 could not be obtained. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0055E Cannot find message &0. Explanation: The message number does not exist in the message catalog file &1. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0056E Cannot read the XML file for a resource. Explanation: This is an internal error. The following errors occurred when parsing the XML file: &0, &1, &0, At line &0, &1, At line &0 before column &1, &2. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center.

Chapter 2. Messages

BIP0060E BIP0201I
BIP0060E The name &0 is not a valid property name. Explanation: This is an internal error. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0070E The paste operation cannot be performed. Explanation: Some resource referred to by the data in the clipboard cannot be found. User Response: Use the appropriate menu to create the resource. BIP0071E The workspace file does not exist. Explanation: The workspace file &0 could not be located. User Response: Verify the workspace file exists and try again. BIP0072E BIP0062E Cannot read the XML data stream for a resource. Explanation: This is an internal error. The following error occurred when parsing an XML data stream: &0 Processing &0, &1. Processing &0, at line &1, &2. Processing &0, at line &1 before column &2, &3. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0066E Invalid Java class name. Explanation: This is an internal error. The name &0 is not a valid class name. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0067E An unexpected exception occurred: &0. Explanation: A &1 exception occurred which reported the following message: &2. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0068E An unexpected exception occurred: &0. Explanation: A &1 exception occurred but provided no additional information. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0069E The paste operation cannot be performed. Explanation: There are no suitable recipient for the resource being pasted. User Response: Locate the appropriate recipient or create a new resource. An error occurred when accessing an XML data stream for a resource. Explanation: This is an internal error. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0073E Cannot open this file as a workspace file. Explanation: The file provided appears to be an import file rather than a workspace file. &0. User Response: Select a valid workspace file and try again. BIP0074E Cannot check in the elements you specified. Explanation: A recursive relationship was found. User Response: Remove Element &0 from Compound Type &1 and retry the operation. BIP0100I WebDAV Response Status Code: 100. Explanation: Continue. User Response: No user action required. BIP0101I WebDAV Response Status Code: 101. Explanation: Switching Protocols. User Response: No user action required. BIP0102I WebDAV Response Status Code: 102. Explanation: Processing. User Response: No user action required. BIP0200I WebDAV Response Status Code: 200. Explanation: OK. User Response: No user action required. BIP0201I WebDAV Response Status Code: 201. Explanation: Created. User Response: No user action required.

BIP0061E

A number of resources could not be added. Explanation: The Control Center was not able to add some resources to your workspace. User Response: The following messages provide information for each resource that could not be added.

MQSeries Integrator Messages

BIP0202I BIP0411E
BIP0202I WebDAV Response Status Code: 202. Explanation: Accepted. User Response: No user action required. BIP0203I WebDAV Response Status Code: 203. Explanation: Non-Authoritative Information. User Response: No user action required. BIP0204I WebDAV Response Status Code: 204. Explanation: No Content. User Response: No user action required. BIP0205I WebDAV Response Status Code: 205. Explanation: Reset Content. User Response: No user action required. BIP0206I WebDAV Response Status Code: 206. Explanation: Partial Content. User Response: No user action required. BIP0207I WebDAV Response Status Code: 207. Explanation: Multi-Status. User Response: No user action required. BIP0300E WebDAV Response Status Code: 300. Explanation: Multiple Choices. User Response: Contact your IBM support center. BIP0301E WebDAV Response Status Code: 301. Explanation: Moved Permanently. User Response: Contact your IBM support center. BIP0302E WebDAV Response Status Code: 302. Explanation: Moved Temporarily. User Response: Contact your IBM support center. BIP0303E WebDAV Response Status Code: 303. Explanation: See Other. User Response: Contact your IBM support center. BIP0304E WebDAV Response Status Code: 304. Explanation: Not Modified. User Response: Contact your IBM support center. BIP0305E WebDAV Response Status Code: 305. Explanation: Use Proxy. User Response: Contact your IBM support center. BIP0400E WebDAV Response Status Code: 400. Explanation: Bad Request. User Response: Contact your IBM support center. BIP0401E You are not authorized to perform this task. Explanation: The current user has tried to issue a task which is not authorized for the authority group the current user belongs to. User Response: To issue this task you must log on as a user which belongs to the appropriate authority group as listed in Using the Control Center manual. BIP0402E WebDAV Response Status Code: 402. Explanation: Payment Required. User Response: Contact your IBM support center. BIP0403E WebDAV Response Status Code: 403. Explanation: The request is not permitted. On a local file system, the document may be read only. User Response: Contact your IBM support center. BIP0404E The requested resource could not be found either on the local repository or on the Configuration Manager. Explanation: The resource may have been deleted by another user. User Response: No user action required. BIP0405E WebDAV Response Status Code: 405. Explanation: Method Not Allowed. User Response: Contact your IBM support center. BIP0406E WebDAV Response Status Code: 406. Explanation: Not Acceptable. User Response: Contact your IBM support center. BIP0407E WebDAV Response Status Code: 407. Explanation: Proxy Authentication Required. User Response: Contact your IBM support center. BIP0408E WebDAV Response Status Code: 408. Explanation: Request Time-out. User Response: Contact your IBM support center. BIP0409E WebDAV Response Status Code: 409. Explanation: Conflict. User Response: Contact your IBM support center. BIP04010E WebDAV Response Status Code: 410. Explanation: Gone. User Response: Contact your IBM support center. BIP0411E WebDAV Response Status Code: 411. Explanation: Length Required. User Response: Contact your IBM support center.

Chapter 2. Messages

BIP0412E BIP0609E
BIP0412E WebDAV Response Status Code: 412. Explanation: Precondition Failed. User Response: Contact your IBM support center. BIP0413E WebDAV Response Status Code: 413. Explanation: Request Entity Too Large. User Response: Contact your IBM support center. BIP0414E WebDAV Response Status Code: 414. Explanation: Request-URI Too Large. User Response: Contact your IBM support center. BIP0415E WebDAV Response Status Code: 415. Explanation: Unsupported Media Type. User Response: Contact your IBM support center. BIP0422E WebDAV Response Status Code: 422. Explanation: The Entity cannot be processed. User Response: Contact your IBM support center. BIP0423E The resource is locked. Explanation: The requested resource is currently locked by another user. User Response: No user action required. BIP0424E WebDAV Response Status Code: 424. Explanation: Method Failure. User Response: Contact your IBM support center. BIP0425E WebDAV Response Status Code: 425. Explanation: Insufficient Space On Resource. User Response: Contact your IBM support center. BIP0500E WebDAV Response Status Code: 500. Explanation: Internal Server Error. User Response: Contact your IBM support center. BIP0501E WebDAV Response Status Code: 501. Explanation: Not Implemented. User Response: Contact your IBM support center. BIP0502E WebDAV Response Status Code: 502. Explanation: Bad Gateway. User Response: Contact your IBM support center. BIP0503E WebDAV Response Status Code: 503. Explanation: Service Unavailable. User Response: Contact your IBM support center. BIP0504E WebDAV Response Status Code: 504. Explanation: Gateway Time-out. User Response: Contact your IBM support center. BIP0505E WebDAV Response Status Code: 505. Explanation: HTTP Version not supported. User Response: Contact your IBM support center. BIP0600E Cannot add &0. Explanation: It has an invalid or missing Type. The Type may have been deleted. User Response: Try to add another one. BIP0601E Cannot add &0. Explanation: &1 has an invalid or missing Type. The Type may have been deleted. User Response: Try to add another one. BIP0602E Cannot add &0. Explanation: It has the same Type as the parent. User Response: Try to add another one. BIP0603E Cannot add &0. Explanation: It has been suspended. User Response: No user action required. BIP0604E Cannot add &0. Explanation: It contains an Element of the same Type as &1. User Response: Try to add another one. BIP0605E Cannot assign the base Message Set &0. Explanation: Base Message Set must be finalized. User Response: Finalize the Message Set &0 or try to assign another one. BIP0606E Invalid Type for Element Valid Value. Explanation: Type must be of logical type String, Float or Integer. User Response: Select another Type. BIP0607E Cannot add Element Valid Value &0 to Element Qualifier &1. Explanation: They do not have the same type. User Response: Try to add another one. BIP0608E Cannot add Element Valid Value &0 to Element &1. Explanation: They do not have the same type. User Response: Try to add another one. BIP0609E Cannot add Length to Element &0. Explanation: Only Elements with logical type of String can have a Length. User Response: No user action required.

MQSeries Integrator Messages

BIP0610E BIP0627E
BIP0610E Cannot assign this Element Qualifier &0. Explanation: Element Qualifier &0 is not valid for the current Element. User Response: Try to assign another one. BIP0611E Cannot finalize Message Set &0. Explanation: &1 &2 is not checked in. User Response: Use Check in List from the File menu to check in all components that are not checked in. Then try finalize again. BIP0612E Cannot freeze Message Set &0. Explanation: &1 &2 is not checked in. User Response: Use Check in List from the File menu to check in all components that are not checked in. Then try freeze again. BIP0613E Cannot freeze Message Set &0. Explanation: &0 is not checked out or locked. User Response: Check out or lock &0 and try freeze again. BIP0614E Cannot add Message &0. Explanation: Only one request or one response message is allowed. User Response: Try to add another one. BIP0615E Execution Group &0 cannot be deleted. Explanation: A Broker must contain at least one Execution Group. User Response: Create another Execution Group and then &0 may be deleted. BIP0616E Cannot add Broker. Explanation: A Broker may not be contained in more than one Collective. User Response: Try removing the Broker from its current Collective. BIP0617E Cannot add Connection. Explanation: Cycles are not allowed in the Topology. User Response: Ensure that a new Connection does not create a loop. BIP0618E Cannot execute action. Explanation: This action requires the Topology to be checked out. User Response: Check out the Topology and try again. BIP0619E Invalid date format. Explanation: A date was entered that does not follow the given format. User Response: Please use the specified date format and check that a valid date has been entered. BIP0620E Invalid date received from Configuration Manager. Explanation: The value was &0. This is an internal error. User Response: Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. BIP0621E Problems were encountered when retrieving the logged messages. Explanation: Some messages may not appear correctly. User Response: No user action required. BIP0622E Cannot execute action. Explanation: This action requires all ExecutionGroups in Broker &0 to be unlocked. Either you or another user has ExecutionGroup &1 checked out. User Response: Unlock ExecutionGroup &1 and try again. BIP0623E Cannot execute action. Explanation: This action requires Broker &0 to be checked out. User Response: Check out Broker &0 and try again. BIP0624E Cannot execute action. Explanation: This action requires the parent topic &0 to be checked out. User Response: Check out &0 and try again. BIP0625E Cannot delete topic &0 and its child topics. Explanation: The following problems were encountered: &1. User Response: The problems listed above will help you resolve the error. BIP0626E Cannot start a NEON application. The following error occurred: &0. Explanation: Either the file &1 could not be located, or an error occurred while executing this file. User Response: Verify that the file exists and it contains the correct command to start the NEON application at the installed location. BIP0627E The import file contained &0 brokers with the same names but different unique identifiers as existing brokers. Explanation: These brokers were not imported in to the workspace.
Chapter 2. Messages

BIP0628E BIP0647W
User Response: Investigate why the brokers had the same names, but different unique identifiers as existing brokers. BIP0628E The topology cannot be imported unless the topology resource is checked out. Explanation: You cannot import the topology unless the topology resource is checked out. User Response: If you check out the topology resource, the imported topology will be merged with the current topology. BIP0629E Cannot reorder elements under &0. Explanation: It has an external relationship with its external element. User Response: No user action required. BIP0630E Cannot paste &0 to this message set. Explanation: It already exists in this message set. User Response: No user action required. BIP0631E Cannot check in the elements you specified. Explanation: A recursive relationship was found. User Response: Remove element &0 from Compound type &1 and retry the operation. BIP0632E Cannot check in the elements you specified. Explanation: A recursive relationship was found. User Response: Break the recursive loop of message flows, and retry the operation. BIP0633E The name entered for this resource is not valid. Explanation: Please follow the rules for naming a resource when entering a name. User Response: Select a different name for the resource and try the operation again. BIP0634I No resources were imported into your local repository. Explanation: The import operation only imports those resources in the import file that either do not exist in the shared configuration repository or that are currently checked out to you. User Response: No user action required. BIP0635I No resources were exported. Explanation: The element you selected to export does not contain any exportable resource. User Response: No user action required. BIP0636E Cannot import file &0. Explanation: The file does not conform with the format of an exported file. Only files exported from the Control Center can be imported. User Response: Select a valid import file and try again. BIP0637E Cannot paste the elements you specified. Explanation: A recursive relationship was found. User Response: Remove Element &0 from Compound Type &1 and retry the operation. BIP0640E An I/O error occurred while creating or connecting to the socket. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0641E An I/O error occurred when establishing connection to the socket. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0642E An I/O error occurred when transferring data through the socket connection. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0643E An unexpected direction received from ComIbmDebug node. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0644E The IP address of the client machine could not been found. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0645E Timeout expired when establishing connection to the socket. Explanation: Check the deployment status. User Response: Retry the operation and contact your IBM support center. BIP0647W This message flow is currently involved in an active debug session. Explanation: You tried to open a message flow that is in use. User Response: Do not modify it or quit from the debug session.

10

MQSeries Integrator Messages

BIP0648W BIP1004S
BIP0648W No message flow was found in the Workspace. Explanation: No message flows could be found. User Response: Load a message flow and choose this option again. BIP0649W The selected message flow was not found in the Workspace. Explanation: The selected message flow is no longer in the workspace and / or repository. User Response: Choose another message flow. BIP0650E Breakpoint Information was not sent. Explanation: A thread responsible for transmitting Breakpoint Information was not properly initialized. User Response: Restart your Control Center. If this problem persists, contact your IBM support center. BIP0651E An I/O error occurred while closing or disconnecting a socket. Explanation: This is an internal error. User Response: Retry the operation and contact your IBM support center. BIP0652E The Control Center is not connected to the Debug Plugin node. Explanation: Either a socket action was not performed properly or a thread is in an undefined state. User Response: Restart your Control Center. If this problem persists, contact your IBM support center. BIP0653E A Problem with the selected Message Flow was encountered. Explanation: This Message Flow might have been unassigned from an execution group, removed or deleted. User Response: Assign or create this Message Flow again. BIP0655E The Broker or the Execution Group are in an invalid state. Explanation: This Debug Session will neither start nor continue. User Response: Get your Broker or the Execution Group back to a valid state and retry. If this problem persists, contact your IBM support center. BIP0656E The initiated Deploy failed. Explanation: This Debug Session will not start and will return itself to a valid state. User Response: Get your Broker or the Execution Group back to a valid state and retry. If this problem persists, contact your IBM support center. BIP0657E Cannot check in the resource &0. Explanation: The resource has not been checked out to you. User Response: In the designer view, you might have to add the resource to your Workspace and then check it out. BIP0658E Data type violation detected. Explanation: One or more field values were changed to incorrect data types. User Response: The message will be reset and all changes done in the previous step are discarded.

BIP1000-BIP1999 (Configuration Manager)

BIP1001S Message associated with number &1 was not found: data supplied &2. Explanation: A message number was used for which no associated message text could be found. User Response: This is an internal error. Contact your IBM support center. BIP1002S Unexpected exception in ConfigurationManager class &2 method; exception text: &1, &3. Explanation: An exception was caught by the ConfigurationManager class &2 method while the Configuration Manager was being started or stopped. The exception text is: &1, &3. User Response: Retry the operation. If the exception still occurs, contact your IBM support center. BIP1003I The Configuration Manager is available for use. Explanation: The Configuration Manager has started successfully. User Response: No user action required. BIP1004S The Configuration Manager is not available for use. Explanation: A problem has been encountered while trying to start the Configuration Manager. The problem is not expected to be transient. User 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.
Chapter 2. Messages

11

BIP1005E BIP1101S
BIP1005E The Configuration Manager is no longer available for use. 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. User Response: Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem if necessary. BIP1006S The Configuration Manager is no longer available for use. Explanation: The Configuration Manager has encountered a situation where it is unable to continue. The problem is not expected to be transient. User 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. BIP1007E The Configuration Manager is not available for use. 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. User 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. BIP1008S Unable to locate XML DTD file &1 in directory &2. Explanation: An XML DTD file could not be found. This may be the result of an inconsistent installation of the Configuration Manager. User Response: Ensure that the file exists in the MQSeries Integrator 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. BIP1009W Trace level not restored due to invalid trace level &1 in the configuration repository. Explanation: An invalid trace level &1 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. User 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. BIP1010W Trace level not preserved due to invalid trace level &1. Explanation: An invalid trace level &1 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. User Response: This is an internal error. Contact your IBM support center. BIP1011I Trace level &1 successfully restored. Explanation: A trace level of &1 has been restored from the configuration repository. The Configuration Manager is now running with trace active at level &1. User Response: No user action required. BIP1012S Unexpected exception creating or deleting Configuration Manager in ConfigurationData class &1 method; exception text: &2. Explanation: An exception was caught by the ConfigurationData class &1 method while the Configuration Manager was being created or deleted. The exception text is: &2. User Response: Retry the operation. If the exception still occurs, contact your IBM support center. BIP1013S Unexpected exception in Configuration Manager PersistentTrace class &2 method; exception text: &1, &3. Explanation: While restoring or preserving the trace level in the configuration repository, an exception was caught by the PersistentTrace class &2 method. The exception text is: &1, &3. User Response: This is an internal error. Contact your IBM support center. BIP1101S Unknown MQSeries queue manager name &1. Explanation: When connecting to the MQSeries queue manager during Configuration Manager startup, the name supplied is not that of a queue manager known to MQSeries. User 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 respository and message repository, do not specify the -n and -m flags on the mqsideleteconfigmgr command. Note also that MQSeries queue manager names are case-sensitive. For more information on this error see the MQSeries Application Programming Reference manual, code 2058.

12

MQSeries Integrator Messages

BIP1102S BIP1111E
BIP1102S The MQSeries queue manager &1 is not currently available. Explanation: When connecting to the MQSeries queue manager during Configuration Manager startup, queue manager &1 is not up and running. This is expected to be a transient situation and the Configuration Manager will restart after a short interval. User Response: Start the MQSeries queue manager and its associated listener. For more information on this error see the MQSeries Application Programming Reference manual, codes 2059, 2161, and 2162. BIP1103S MQSeries queue manager &1 no longer available. Explanation: The Configuration Managers connections to MQSeries queue manager &1, 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. User Response: Restart the MQSeries queue manager. For more information on this error see the MQSeries Application Programming Reference manual, codes 2009, 2161, and 2162. BIP1104S An authorization error occurred when the Configuration Manager accessed MQSeries object &1. Explanation: MQSeries has raised an authorization exception while connecting to the MQSeries queue manager, or opening one of the MQSeries queues used by the Configuration Manager. The name of the MQSeries object in question is &1. User Response: Check that the user name passed as the ServiceUserId argument to the mqsicreateconfigmgr utility program is authorized to connect to MQSeries and access the necessary queues. See the MQSeries Integrator Administration Guide, section Setting Up Security for guidance. You may also find help in the MQSeries Application Programming Reference manual, codes 2035 and 2063. BIP1105S Unknown MQSeries queue name &1. Explanation: When opening the MQSeries queues used by the Configuration Manager, the name supplied is not that of a queue known to MQSeries queue manager. User Response: Check that the MQSeries queue manager you specified has a definition for queue &1. Check that you are using the correct queue manager, as the mqsicreateconfigmgr command creates the required MQSeries queues automatically. Note that MQSeries queue names are case-sensitive. For more information on this error see the MQSeries Application Programming Reference manual, code 2085. BIP1106S MQSeries error detected, reason code &1. Explanation: An error has occurred while making an MQSeries call from the Configuration Manager. The MQSeries reason code is &1. The Configuration Manager will continue processing if it is possible to do so. User Response: For more information on this error see the MQSeries Application Programming Reference manual, code &1. BIP1107S Unexpected exception in Configuration Manager MQProcessor class &2 method; exception text: &1. Explanation: An exception was caught by the Configuration Manager MQProcessor class &2 method. The exception text is: &1. The Configuration Manager will continue processing if it is safe to do so. User 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. BIP1109S MQSeries error writing to dead letter queue, reason code &1. Explanation: An error occurred while the Configuration Manager was putting a message on the dead letter queue. The MQSeries reason code is &1. A previous message will indicate the reason why the message was put to the dead letter queue in the first place. User Response: For more information on this error see the MQSeries Application Programming Reference manual, code &1. BIP1110W Unrecognized MQSeries message received by the Configuration Manager on input queue &2; reason code &1. Explanation: A message was received by the Configuration Manager on input queue &2, but the message could not be processed. The MQSeries reason code is &1. The message has been written to the MQSeries dead letter queue. User 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 MQSeries Application Programming Reference manual, code &1. BIP1111E java.lang.OutOfMemoryError in Configuration Manager MQProcessor class &1 method. Explanation: A java.lang.OutOfMemoryError was caught by the Configuration Manager MQProcessor class &1 method. This means the Java Virtual Machine has exhausted its available memory heap. User Response: Stop the Configuration Manager using the mqsistop command. Increase the maximum size of
Chapter 2. Messages

13

BIP1151S BIP1159E
the Java Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the MQSeries Integrator Administration Guide for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs. BIP1151S Unprocessable request received by the Configuration Manager; server type &2 invalid for resource type &1. Explanation: A request was received by the Configuration Manager, but the URI identifies a target server type (&2) which is not valid for resource type &1. User Response: If the request did not originate from the Control Center, correct the application issuing the request. Otherwise retry the operation from the Control Center. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center. BIP1152S Internal error in the Configuration Manager; resource type &1. 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 &1. User 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. BIP1153S Unprocessable request received by the Configuration Manager; URI is &1. 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 &1. User Response: If the request did not originate from the Control Center, correct the application issuing the request. Otherwise retry the operation from the Control Center. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center. BIP1154S Unprocessable request received by the Configuration Manager; &2 operation not permitted for resource type &1. Explanation: A request was received by the Configuration Manager, but a &2 operation is never permitted for target resource type &1. User Response: If the request did not originate from the Control Center, correct the application issuing the request. Otherwise retry the operation from the Control Center. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center. BIP1155S Internal error in the Configuration Manager; resource type &1. Explanation: A request was received by the Configuration Manager but the URI identifies a target resource type &1 for which no corresponding RoleManager object type can be found. User 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. BIP1156S Internal error within the Configuration Manager; server type &1. Explanation: A request was received by the Configuration Manager but the URI identifies a target server type (&1) for which no corresponding RoleManager server type can be found. User 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. BIP1157S The properties for the target resource cannot be located. 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. User 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. BIP1158S Unprocessable request received by the Configuration Manager; resource type &1. Explanation: A request was received by the Configuration Manager but the URI identifies target resource type &1 for which the Configuration Manager is not configured. User Response: If the request did not originate from the Control Center, correct the application issuing the request. Otherwise retry the operation from the Control Center. If the exception still occurs, turn on Configuration Manager tracing to capture details of the request, and contact your IBM support center. BIP1159E Broker &1 has a blank queue manager name. Explanation: An attempt was made to check in a broker with no associated MQSeries queue manager name. This is a mandatory property. The broker name is &1. User Response: Provide a queue manager name for the broker and retry the operation.

14

MQSeries Integrator Messages

BIP1160E BIP1207E
BIP1160E Duplicate name &2 for &1 within configuration repository. Explanation: An error occurred when attempting to save &1 &2 to the configuration repository because another &1 already exists with the same name. User Response: Rename the &1 and retry the operation. BIP1161S Unable to locate MQSeries Java classes. Explanation: When connecting to the MQSeries queue manager at Configuration Manager startup, the MQSeries Java classes could not be located. User Response: Ensure that the required level of MQSeries Java classes are installed and have been correctly added to the CLASSPATH. Different versions of MQSeries Java classes require different entries in the CLASSPATH (in particular version 5.2 of MA88 requires connector.jar to be identified in the CLASSPATH). You should consult the documentation provided with your version of MQSeries 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. You must also ensure that the userid under which the Configuration Manager is running is a member of the mqm group and of the Administrators group and that mqjbnd02.dll (supplied with MQSeries classes for Java) is available via the PATH. BIP1201S Unknown or unsupported database of type &1. Explanation: While attempting to determine the type of database being used for the configuration repository, the database type &1 was returned. This is an unknown or unsupported database. User Response: This is an internal error. Contact your IBM support center. BIP1202S Unexpected exception in the Configuration Manager DBManager class &2 method; exception text: &1, &3. Explanation: While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager DBManager class &2 method. The database operation did not complete successfully. The exception text is: &1, &3. User Response: This is an internal error. Contact your IBM support center. BIP1203S Unknown database column type &1. Explanation: While attempting to construct the database tables for the configuration repository, a column type of &1 was found. This is an unknown column type. The database tables have not been constructed successfully. User Response: This is an internal error. Contact your IBM support center. BIP1204S Unable to locate required &1 &2 in directory &3. 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. User Response: Ensure that the file or directory exists in the MQSeries Integrator &3 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. BIP1205E Unexpected exception accessing configuration repository; exception text: &2. Explanation: While attempting a database operation on the configuration repository, a SQL 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: &2. User Response: For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository (for example, for DB2 refer to the DB2 SQL Reference manual). BIP1206E Database not running; exception text: &1. Explanation: While attempting a database operation on the configuration repository, a SQL 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: &1. User Response: For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository (for example, for DB2 refer to the DB2 SQL Reference manual). BIP1207E Database &1 not found; exception text: &2. Explanation: While attempting a database operation on the configuration repository, a SQL exception was caught by the Configuration Manager. This was because the database name &1 is not recognized and the database cannot be found. The database operation did not complete successfully. The exception text is: &2. User Response: For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository
Chapter 2. Messages

15

BIP1208S BIP1217E
(for example, for DB2 refer to the DB2 SQL Reference manual). BIP1208S Database product name cannot be found: object &1 is null. Explanation: A problem was encountered while attempting to get information from the configuration repository database manager. The &1 object is null. User Response: This is an internal error. Contact your IBM support center. BIP1209E The userid and/or password are not authorized for connection to the configuration repository &1. Explanation: When starting, creating, or deleting the Configuration Manager, the configuration repository database &1 could not be opened because the userid and/or password is not authorized. User 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. BIP1210S Missing or blank configuration repository JDBC driver name. 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. User Response: This is an internal error. Contact your IBM support center. BIP1211S Missing or blank configuration repository JDBC connection name. 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. User Response: This is an internal error. Contact your IBM support center. BIP1212S Missing or blank configuration repository database name. Explanation: The configuration repository database name supplied to the Configuration Manager is either blank or is missing. This is a mandatory property of the Configuration Manager. The most likely cause of this is manual editing of the Windows NT registry entries created by the mqsicreateconfigmgr command. User 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 -n option. Refer to the MQSeries Integrator Administration Guide for guidance. If the problem persists, contact your IBM support center. BIP1213S User &1 is not allowed to unlock resource locked by user &2. Explanation: An attempt has been made to unlock a resource in the configuration repository, but the principal supplied with the unlock request (&1) does not match the principal associated with the locked resource (&2). User Response: The resource was locked by a different user. You cannot unlock a resource for which you do not own the lock. BIP1214S Cannot unlock resource with lock token &1 as the resource is not locked. Explanation: An attempt has been made to unlock a resource in the configuration repository, but the lock token supplied with the unlock request (&1) does not exist in the configuration repository, implying that the resource is not locked. User Response: The resource has already been unlocked. You can not unlock a resource for which no lock exists. BIP1215S Invalid configuration repository table name &1 detected by Configuration Manager DBManager class &2 method. Explanation: The Configuration Manager DBManager class &2 method has detected an unknown table name &1 when processing a request against the configuration repository. User Response: This is an internal error. Contact your IBM support center. BIP1216S Can not update resource &1 which is not locked. Explanation: An attempt has been made to update an existing resource &1 in the configuration repository but the resource has not been locked. User Response: You must first lock a resource before you update it. BIP1217E Referenced &2 not found, (UUID &1). Explanation: A referenced &2 has not been found in the configuration repository. User Response: It is possible the parent of the &2 has been checked in but the &2 itself has not. Alternatively, the referenced &2 may have been deleted. If this problem persists, contact your IBM support center.

16

MQSeries Integrator Messages

BIP1301S BIP1352S
BIP1301S Invalid call to Configuration Manager PrincipalsManager class &1 method. Explanation: An invalid method call was made to the Configuration Manager PrincipalsManager class &1 method. User Response: This is an internal error. Contact your IBM support center. BIP1302S Unexpected exception in Configuration Manager PrincipalsManager class makeTXDoc method; exception text: UnsupportedEncodingException, character set &1. 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 &1. User Response: This is an internal error. Contact your IBM support center. BIP1303S Unexpected exception in Configuration Manager PrincipalsManager class &1 method; exception text: &2. Explanation: An exception was caught by the Configuration Manager PrincipalsManager class &1 method. The exception text is: &2. User 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. BIP1304S Error accessing User Name Server from Configuration Manager PrincipalsManager class &1 method; exception text: &2. Explanation: An exception was caught by the Configuration Manager PrincipalsManager class &1 method whilst getting information from the User Name Server UGRegistry client. The exception text is: &2. User 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. BIP1305S Invalid call to Configuration Manager PrincipalsManager class &1 method; Section parameter value &2 encountered. Explanation: An attempt was made by the Configuration Manager to call the PrincipalsManager class &1 method using value &2 for the Section parameter. Only a value of SHARED is supported. User Response: This is an internal error. Contact your IBM support center. BIP1306S Invalid call to Configuration Manager PrincipalsManager class &1 method; Container parameter value &2 encountered. Explanation: An attempt was made by the Configuration Manager to call the PrincipalsManager class &1 method using value &2 for the Container parameter. Only values of USER, GROUP and PUBLICGROUP are supported. User Response: This is an internal error. Contact your IBM support center. BIP1350E The current operation has timed out. 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. User 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 MQSeries, 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. For example, if a check in operation timed out then the update may have occurred, but the object may still be locked. A subsequent check in would then fail with a locked response. The action would then be to unlock the object. BIP1351S MQSeries queue manager &1 unknown on host system &2. Explanation: When connecting to the MQSeries queue manager, the name supplied is not that of a queue manager known to MQSeries on host system &2. The Control Center is unable to communicate with the Configuration Manager. User Response: Check that the queue manager name entered in the Control Center File->Connection dialog box has been correctly specified, and that an MQSeries queue manager with the required name exists on the specified host system. Note that MQSeries queue manager names are case-sensitive. For more information on this error, see the MQSeries Application Programming Reference manual, code 2058. BIP1352S MQSeries queue manager &1 on host system &2 not available. Explanation: When connecting to the MQSeries queue manager, queue manager &1 is not up and running and not listening for input on host system &2. The Control Center is unable to communicate with the Configuration Manager. User Response: Check that the queue manager name entered in the Control Center File->Connection dialog box has been correctly specified. Start the MQSeries
Chapter 2. Messages

17

BIP1353S BIP1360E
queue manager if it is not running. Ensure that the MQSeries listener is running and listening on the correct port, that only one listener is listening on that port. Ensure that MQSeries server connection channel SYSTEM.BKR.CONFIG is defined to the queue manager. For more information on this error, see the MQSeries Application Programming Reference manual, codes 2059, 2161, 2162, and 2009. BIP1353S MQSeries queue manager &1 no longer available. Explanation: The Control Centers connection to MQSeries queue manager &1 has been lost. The Control Center is unable to communicate with the Configuration Manager. User Response: Restart the MQSeries queue manager and the MQSeries listener. If necessary also restart the Configuration Manager. For more information on this error, see the MQSeries Application Programming Reference manual, codes 2009, 2161 and 2162. BIP1354S An authorization error occurred when the Control Center accessed MQSeries object &1. Explanation: MQSeries has raised an authorization exception while connecting to the MQSeries queue manager or opening one of the MQSeries queues used by the Control Center. The name of the MQSeries object in question is &1. The Control Center is unable to communicate with the Configuration Manager. User Response: Check that the user name under which you are logged on is a member of one or more of the following operating system security groups: mqbrdevt, mqbrasgn, mqbrops, mqbrtpic. If the problem reoccurs, check that the groups listed have authority to open the SYSTEM.BROKER.CONFIG.QUEUE and SYSTEM.BROKER.CONFIG.REPLY queues. For more information on this error, see the MQSeries Application Programming Reference manual, codes 2035 and 2063. BIP1355S Unknown MQSeries queue name &1. Explanation: When opening the MQSeries queues used by the Control Center, the name supplied is not that of a queue known to the MQSeries queue manager. The Control Center is unable to communicate with the Configuration Manager. User Response: Check that the queue manager name entered in the Control Center 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 &1. Note that MQSeries queue and queue manager names are case-sensitive. For more information on this error, see the MQSeries Application Programming Reference manual, code 2085. BIP1356S MQSeries error detected, reason code &1. Explanation: An error has occurred while making an MQSeries call from the Control Center. The MQSeries reason code is &1. User Response: For more information on this error, see the MQSeries Application Programming Reference manual, code &1. BIP1357E Unrecognized reply received from the Configuration Manager. 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 Control Center. User Response: The most likely cause is that another MQSeries application is erroneously processing messages on SYSTEM.BROKER.CONFIG.QUEUE. Check that the Configuration Manager is up and running and is the only MQSeries application processing messages on the queue. If no other application can be identified and the problem persists, contact your IBM support center. BIP1358S Unexpected exception in Control Center &2 class &3 method; exception text: &1, &4. Explanation: An exception was caught by the &2 class &3 method when the Control Center was communicating with the Configuration Manager. The exception text is: &1, &4. User Response: Retry the operation. If the exception still occurs, restart the Control Center, then retry the operation again. If the exception still occurs, turn on Control Center tracing to capture details of the exception, and contact your IBM support center. BIP1359S The connection to MQSeries queue manager &1 has been lost. Explanation: When communicating with MQSeries, queue manager &1 is no longer up and running and listening for input. The Control Center is unable to communicate with the Configuration Manager. User Response: Restart the MQSeries queue manager if it is not running. Ensure that the MQSeries 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 MQSeries Application Programming Reference manual, codes 2161, 2162, and 2009. BIP1360E Configuration Manager is not at the required software level. 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 from your level of Control Center.

18

MQSeries Integrator Messages

BIP1361S BIP1409S
User Response: The most likely cause is that the Control Center 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 Control Center, or connect the Control Center to a different Configuration Manager. BIP1361S Unable to locate MQSeries Java classes. Explanation: When connecting to the MQSeries queue manager at Configuration Manager startup, the MQSeries Java classes could not be located. The Control Center is unable to communicate with the Configuration Manager. User Response: Ensure that the required level of MQSeries 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 MQSeries Java classes are installed. If you do not have permission, either change the permissions on the directory or add your userid to the Administrators group. BIP1401S Invalid call to Configuration Manager MRMManager class &1 method. Explanation: An invalid method call was made to the Configuration Manager MRMManager class &1 method. User Response: This is an internal error. Contact your IBM support center. BIP1402S Unexpected exception in Configuration Manager MRMManager class &2 method; exception text: &1. Explanation: An exception was caught by the Configuration Manager MRMManager class &2 method. The exception text is: &1. User 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. BIP1403S Missing or blank message repository database name. 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 Windows NT registry entries created by the mqsicreateconfigmgr command. User 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 MQSeries Integrator Administration Guide for guidance. If the problem persists, contact your IBM support center. BIP1404S Update or create message repository resource &2 of type &1 in server &3 failed: empty hashtable. Explanation: An empty hashtable was supplied when updating or creating resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1405S Update or create message repository resource &2 of type &1 in server &3 failed: no XML document. Explanation: No XML document was supplied when updating or creating resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1406S Unable to lock message repository resource &2 of type &1 in server &3: no ActiveLock object. Explanation: No ActiveLock object was supplied when checking out or locking resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1407S Update or create resource &2 of type &1 in server &3 failed: empty hashtable. Explanation: An empty hashtable was supplied when updating or creating the properties for resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1408S Update or create resource &2 of type &1 in server &3 failed: no XML document. Explanation: No XML document was supplied when updating or creating the properties for resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1409S Unable to unlock resource &2 of type &1 in server &3: no ActiveLock object. Explanation: No ActiveLock object was supplied when checking in or unlocking resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center.

Chapter 2. Messages

19

BIP1410S BIP1503E
BIP1410S Update or create resource &2 of type &1 in server &3 failed: no ActiveLock object. Explanation: No ActiveLock object was supplied when updating or creating resource &2 of type &1 in server &3 within the message repository. User Response: This is an internal error. Contact your IBM support center. BIP1411S Unable to save NEON resource to the configuration repository. Explanation: Changes to NEON resources cannot be performed using the Control Center. User Response: The Control Center provides a read-only view of NEON resources. To update a NEON resource, use the NEON Formatter GUI instead. BIP1412S Unable to save the properties for the NEON resource to the configuration repository. Explanation: Changes to NEON resources cannot be performed using the Control Center. User Response: The Control Center provides a read-only view of NEON resources. To update a NEON resource, use the NEON Formatter GUI instead. BIP1413S Unable to lock a NEON resource. Explanation: Changes to NEON resources cannot be performed using the Control Center, so it is not possible to put a lock on a NEON resource. User Response: The Control Center provides a read-only view of NEON resources. To update a NEON resource, use the NEON Formatter GUI instead. BIP1414S Unable to unlock a NEON resource. Explanation: Changes to NEON resources cannot be performed using the Control Center, and so it is not possible to release a lock on a NEON resource. User Response: The Control Center provides a read-only view of NEON resources. To update a NEON resource, use the NEON Formatter GUI instead. BIP1415S Unable to delete a NEON resource. Explanation: Changes to NEON resources cannot be performed using the Control Center, so it is not possible to delete a NEON resource. User Response: The Control Center provides a read-only view of NEON resources. To update a NEON resource, use the NEON Formatter GUI instead. BIP1449S Configuration Manager cannot locate one or more Java classes; exception text: &1. Explanation: There was an error establishing the correct Java environment for accessing the message repository. User Response: This normally indicates an inconsistent installation of the Configuration Manager. Check that the Configuration Manager has been installed correctly and that no .jar files have been deleted. If the problem persists, contact your IBM support center. BIP1450S Error loading library imbMRMInterface; error text: &1. Explanation: The Configuration Manager was unsuccessful when loading the imbMRMInterface library. Any error text follows: &1. User Response: This normally indicates an inconsistent installation of the Configuration Manager. Check that the Configuration Manager has been installed correctly and that the PATH enviroment variable includes the directory containing the Configuration Manager libraries and executables. If the problem persists, contact your IBM support center. BIP1461S Invalid call to Configuration Manager CacheManager class &1 method. Explanation: An invalid method call was made to the Configuration Manager CacheManager class &1 method. User Response: This is an internal error. Contact your IBM support center. BIP1462S Unexpected exception in Configuration Manager CacheManager class &2 method; exception text: &1. Explanation: An exception was caught by the Configuration Manager CacheManager class &2 method. The exception text is: &1. User 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. BIP1502S Unexpected exception in Configuration Manager BrokerManager class &1 method; exception text: &2. Explanation: An exception was caught by the Configuration Manager BrokerManager class &1 method. The exception text is: &2. The current operation will end. User 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. BIP1503E Unable to find required &1 document in the configuration repository. Explanation: When deploying configuration data, the document for &1 &2 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 document is &3 &4.

20

MQSeries Integrator Messages

BIP1504S BIP1513W
User Response: The &1 document &2 has either been deleted or has not been checked in. Correct the problem and retry the deploy operation. BIP1504S Unknown deploy type or action type &1. Explanation: The Configuration Manager BrokerManager class received a request to perform the action &1. This action is not recognized. User Response: This is an internal error. Contact your IBM support center. BIP1505E Subscription can not be deleted. Explanation: An attempt was made to delete a subscription, but the subscription in question was created by an MQSeries Integrator component for its own internal use. Such subscriptions can not be deleted. User Response: Retry the operation on a different subscription. BIP1507S Cannot find root element &1 in XML document. Explanation: The Configuration Manager could not find a root element named &1 in the XML document it was attempting to parse. User Response: This is an internal error. Contact your IBM support center. BIP1508S Unexpected root element &1 in XML document: root element &2 expected. Explanation: The Configuration Manager found an unexpected root element named &1 while parsing an XML document looking for root element &2. User Response: This is an internal error. Contact your IBM support center. BIP1509W Unable to deploy configuration data. Explanation: An attempt was made to deploy configuration data to one or more brokers, but none of the brokers in the set could be found in the configuration repository. The deploy operation was not performed. User Response: Make sure that all brokers in the set have been checked in, then retry the operation. BIP1510E Unable to deploy configuration data. Explanation: An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker &1. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed. User Response: Wait for the outstanding deploy to complete before retrying the operation. The Log view 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 MQSeries 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 retry the deploy operation specifying the Forced option which overrides any outstanding deploy. Note that Forced causes all configuration throughout the entire domain to be re-deployed so you may not have authority to perform this. The Forced option may only be selected when deploying Complete configuration (all types) from the File menu. BIP1511E Queue manager &3 cannot be associated with broker &1; already associated with broker &2. Explanation: An attempt was made to associate broker &1 with MQSeries queue manager &3, but broker &2 already has this association. An MQSeries queue manager can only have one broker associated with it. User Response: Change the queue manager for one of the brokers. If this problem occurs after you have deleted broker &2 using the Control Center, then tried to recreate it, you must first initiate a deploy operation to automatically delete the configuration from the real broker (a broker is first created outside of the Control Center, then it is defined to the Control Center). It is only after all types of configuration data (assignment, 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. BIP1512S No Topology document found. Explanation: When attempting to deploy configuration data, the Topology document could not be found in the configuration repository. User Response: This is an internal error. Contact your IBM support center. BIP1513W Unprocessable response received by Configuration Manager on input queue &1. Explanation: A message was received by the Configuration Manager on input queue &1, but the message was not a response to an outstanding broker request. Either this message has erroneously appeared on queue &1, or a Control Center user has deployed configuration data to a broker with the Forced option which removes details of any oustanding deploy request. The message has been written to the MQSeries dead letter queue. User Response: Look at the message on the dead letter queue to establish which application sent the
Chapter 2. Messages

21

BIP1514W BIP1523I
message. If the message was a reply from a broker to which a forced deploy was subsequently issued, then it can be safely ignored. Otherwise correct the application. BIP1514W Unprocessable publication received by Configuration Manager on input queue &1. Explanation: A publication was received by the Configuration Manager on input queue &1, but the publication matches no topic to which the Configuration Manager has subscribed. The publication has been written to the MQSeries dead letter queue. User 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 &1 queue. Correct the application. BIP1515S Unable to find deploying broker data: UUID of broker is &1 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 &1. User Response: This is an internal error. Contact your IBM support center. BIP1516S Unable to process XML document in message from broker &2: no &1 element could be found. Explanation: While processing a message received from broker &2, the XML document it contained was found to be invalid. An element in the following list was expected but could not be found: &1. User Response: This is an internal error. Contact your IBM support center. BIP1517S Cannot find &1 in section &2 of configuration repository: UUID of entry &3; table &4. Explanation: A configuration repository &1 entry could not be found. The UUID of the entry is &3, the configuration repository table name is &4 and section is &2. The configuration repository may be in an inconsistent state. User Response: This situation should not arise under normal circumstances. Retry the operation and if the problem persists, contact your IBM support center. BIP1518W Unexpected exception in Configuration Manager BrokerManager class purgeLogEntries method; exception text: &1. 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: &1. User 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. BIP1519E Invalid topic tree found deploying topics. Explanation: When deploying topic data, the document for topic &1 could not be found in the configuration repository. The parent topic that references &1 is &2. User Response: The topic document for &1 has either been deleted or has not been checked in. Correct the problem and retry the deploy operation. BIP1520I Deploy operations successfully initiated. Explanation: The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: &1. Deleted brokers: &2. User Response: Switch to the Log view to check the outcome of the operations. There will be a separate set of log messages for each broker. BIP1521I Start message flow operation successfully initiated for broker &1. Explanation: The Configuration Manager has processed the start message flow request and initiated a start message flow operation for the target message flows. User Response: Switch to the Log view to check the outcome of the operation. BIP1522I Stop message flow operation successfully initiated for broker &1. Explanation: The Configuration Manager has processed the stop message flow request and initiated a stop message flow operation for the target message flows. User Response: Switch to the Log view to check the outcome of the operation. BIP1523I Stop trace operation successfully initiated for broker &1. Explanation: The Configuration Manager has processed the stop trace request and initiated a stop trace operation for the target resources. User Response: Switch to the Log view to check the outcome of the operation.

22

MQSeries Integrator Messages

BIP1524I BIP1535W
BIP1524I Start trace operation successfully initiated for broker &1. Explanation: The Configuration Manager has processed the start trace request and initiated a start trace operation for the target resources. User Response: Switch to the Log view to check the outcome of the operation. BIP1525I Delete subscription operation successfully initiated on broker &1. Explanation: The Configuration Manager has processed the delete subscription request and initiated a delete operation for the target subscription. User Response: Switch to the Log view to check the outcome of the operation. BIP1526W Operation not initiated. Explanation: The Configuration Manager attempted to process the request but no suitable resource was found. User Response: Refresh the Operations view in the Control Center, using the refresh button, and check that the correct resources still exist. BIP1527E Duplicate name &2 deploying &1 data. Explanation: When deploying &1 data, two &1s with the same name were found in the configuration repository. The &1 name is &2. Names must be unique. User Response: Check out one of the &1s with name &2, rename it and check it back in. Then retry the deploy operation. BIP1528E java.lang.OutOfMemoryError in Configuration Manager BrokerManager class &1 method. Explanation: A java.lang.OutOfMemoryError was caught by the Configuration Manager BrokerManager class &1 method. This means the Java Virtual Machine has exhausted its available memory heap. User 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 MQSeries Integrator Administration Guide for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs. BIP1530S Unable to process XML document for broker &2. Attribute &1 not found for element &3. Explanation: While processing a message received from broker &2, the XML document it contained was found to be invalid. An attribute named &1 could not be found for element &3. User Response: This is an internal error. Contact your IBM support center. BIP1531S Deploy configuration failed. Message set with UUID &1 returned an empty hashtable. 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 &1. User Response: This is an internal error. Contact your IBM support center. BIP1532S Deploy configuration failed processing &1 data: UUID of resource is &2. Explanation: An empty hash table was supplied when adding &1 data to the deploying section of the configuration repository. The UUID of the resource in question is &2. User Response: This is an internal error. Contact your IBM support center. BIP1533E Unable to deploy configuration data: unknown MQSeries queue manager &2 associated with broker &1. Explanation: An attempt was made to deploy configuration data to one or more brokers. The MQSeries queue manager &2 associated with broker &1 is not known to the Configuration Managers MQSeries queue manager. The deploy operation was not performed. User Response: Check that the name of the queue manager is spelt correctly. Note that MQSeries queue manager names are case sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager &2, or a transmission queue called &2, is defined to the Configuration Managers queue manager. For more information on this error see the MQSeries Application Programming Reference manual, code 2087. BIP1534W Unable to perform requested operation for broker &1: broker does not exist on queue manager &2. Explanation: An attempt was made to perform an operation against resources on broker &1, but the broker does not exist on queue manager &2. The operation was not performed. User Response: This normally means that the broker has been prematurely deleted using the mqsideletebroker command. Delete the broker from the configuration using the Control Center, then redeploy the configuration to remove all traces of the broker from the configuration repository. BIP1535W Operation not initiated: broker &1 does not exist on queue manager &2. Explanation: An attempt was made to process the request, but broker &1 does not exist on queue manager &2. The operation was not initiated.
Chapter 2. Messages

23

BIP1536S BIP1543W
User Response: This normally means that the broker has been prematurely deleted using the mqsideletebroker command. Delete the broker from the configuration using the Control Center, then redeploy the configuration to remove all traces of the broker from the configuration repository. BIP1536S Configuration Manager unable to register for internal subscriptions with broker &1. Explanation: Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker &1 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker &1. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem. User Response: Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center. BIP1537W Unable to remove configuration data from broker &1: broker no longer exists on queue manager &2. Explanation: Broker &1 was deleted using the Control Center and a deploy operation subsequently attempted to remove all configuration data. However the broker was found to no longer exist on queue manager &2. User Response: No action should be required. This normally means that the broker has been deleted using the mqsideletebroker command. BIP1538E Unable to deploy configuration data to broker &1 on queue manager &2; MQSeries reason code &3. Explanation: An attempt was made to deploy configuration data to broker &1 on queue manager &2, but MQSeries could not deliver the deploy request to the broker. The MQSeries reason code is &3. No configuration data was deployed. User Response: For more information on this error refer to the MQSeries Application Programming Reference manual, code &3. Correct the problem and retry the deploy operation. BIP1539E Unable to deploy configuration data to broker &1: broker does not exist on queue manager &2. Explanation: An attempt was made to deploy configuration data to broker &1, but MQSeries could not deliver the deploy request to the broker. The broker was found not to exist on queue manager &2. No configuration data was deployed. User Response: Either the wrong MQSeries 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 MQSeries 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, or delete the broker from the configuration using the Control Center and redeploy to remove all traces of the broker from the configuration repository. BIP1540I Broker &1 has been removed from the configuration repository. Explanation: Broker &1 was deleted using the Control Center 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. Accordingly the Configuration Manager has removed all trace of the broker from the configuration repository. User Response: No user action required. If you refresh the Control Center Operations view the broker will no longer be shown. BIP1541E Unable to perform requested operation for broker &1 on queue manager &2; MQSeries reason code &3. Explanation: An attempt was made to perform an operation against resources on broker &1 on queue manager &2, but MQSeries could not deliver the operation request to the broker. The MQSeries ReasonCode is &3. No operation was performed. User Response: For more information on this error refer to the MQSeries Application Programming Reference manual, code &3. Correct the problem and retry the operation. BIP1542E Unable to deploy configuration data. 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. User Response: This is a transient situation. Wait for the Configuration Manager to complete its processing then retry the operation. BIP1543W Deploy of configuration data to broker &1 not performed. Explanation: An attempt was made to perform a delta deploy of configuration data to broker &1, but no changes have been made to the configuration for broker &1 since the last deploy. The deploy operation for broker &1 was not performed. User Response: No user action required.

24

MQSeries Integrator Messages

BIP1544E BIP1709I
BIP1544E The NEON Message Set cannot be deployed. Explanation: An attempt was made to deploy broker &1, but the broker has the NEON Message Set assigned to it. User Response: The NEON Message Set is provided to allow users to view NEON Formatter message/format definitions within the Control Center. It is not necessary to deploy this message set to a broker. You must unassign the NEON Message Set from the broker, and retry the operation. BIP1701S Missing Windows NT security domain name. Explanation: The Windows NT security domain name supplied to the Configuration Manager is missing. The most likely cause of this is manual editing of the Windows NT registry entries created by the mqsicreateconfigmgr command. User 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. See the MQSeries Integrator Administration Guide for guidance. If the problem persists, contact your IBM support center. BIP1702S Unexpected exception in Configuration Manager RoleManager class &2 method; exception text: &1, &3. Explanation: An exception was caught by the Configuration Manager RoleManager class &2 method. The exception text is: &1, &3. User 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. BIP1703S Access rights for user &1 cannot be validated: parameter &2 has an unrecognized value (&3). Explanation: The &2 parameter passed to the Configuration Manager RoleManager class validateUser method has an unrecognized value (&3). User Response: This is an internal error. Contact your IBM support center. BIP1704S Required Windows NT security groups missing from domain &2: missing groups &1. Explanation: The Configuration Manager has detected that one or more of the mandatory MQSeries Integrator security groups are not present in the Windows NT security domain &2. A complete set must be present. The missing groups are: &1. User Response: Using operating system facilities, add the missing groups to the security domain, add the appropriate users to these groups, and then restart the Configuration Manager. BIP1705S Access rights to the &1 server not set up successfully by Configuration Manager RoleManager class &2 method. Explanation: A problem was encountered by the Configuration Manager RoleManager class &2 method while attempting to set up the access rights for the various groups. User Response: This is an internal error. Contact your IBM support center. BIP1706S The access rights for a user cannot be validated. Explanation: The user parameter passed to RoleManager.validateUser method is null and, therefore, cannot be recognized. User Response: This is an internal error. Contact your IBM support centre. BIP1707E Unknown user encountered within the Configuration Manager. 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. User 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. BIP1708S Unexpected exception in the Configuration Manager RoleManager class &1 method; exception text: &2. Explanation: An exception was caught by the Configuration Manager RoleManager class &1 method when calling the UGRegistry class. The exception text is: &2. User 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. BIP1709I All required Windows NT security groups (&1) found within domain &2. Explanation: The Configuration Manager has detected a complete set of MQSeries Integrator security groups in the Windows NT security domain &2. The groups that will be used are: &1. User Response: No user action required.

Chapter 2. Messages

25

BIP1710S BIP1757E
BIP1710S All required Windows NT security groups are missing from domain &1. Explanation: The Configuration Manager has detected that none of the mandatory MQSeries Integrator security groups are present in the Windows NT security domain &1. A complete set must be present. User Response: Using operating system facilities, add the groups to the security domain, add the appropriate users to these groups, and then restart the Configuration Manager. See the MQSeries Integrator Administration guide for information about the names of the groups that must be added. BIP1751S Unexpected error deploying the broker topology: record for broker &2 (UUID=&3) with neighbor broker &4 (UUID=&5) missing from CNEIGHBOURS table section &1. Explanation: When deploying the broker topology, a record was found to be missing from the configuration repository CNEIGHBOURS table (&1 section). The record in question was for broker &2 (UUID=&3) with neighbor broker &4 (UUID=&5). User Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center. BIP1752S Unexpected error deploying configuration data: record for &3 (UUID=&4) missing from table &1, section &2. Explanation: When deploying configuration data, a record was found to be missing from the configuration repository &1 table (&2 section). The record in question was for &3 (UUID=&4). User Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center. BIP1753S Invalid XML document found when deploying; missing <&1> tag. Explanation: When deploying configuration data, an XML document for &3 &2 (UUID=&4) was retrieved from the configuration repository, but the XML document did not contain the expected <&1> tag as the document element. User Response: Identify the application that created the document. If this is not the Control Center, 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. BIP1754S Invalid XML document for topic &1 found when deploying topics. Explanation: When deploying topics data, an XML document for topic &1 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. User Response: Identify the application that created the document. If this is not the Control Center, 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. BIP1755E Invalid message flow &1 when deploying message flows. Explanation: When deploying message flow data, the document for message flow &1 was retrieved from the configuration repository, but was found to be invalid for use as a top-level message flow. 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, or a user defined message flow containing an Input terminal or an Output terminal. User Response: Make sure that the only message flows you assign to an execution group are those that do not contain Input terminals or Output terminals. If &1 is user defined, either check it out and remove any Input terminals and Output terminals, or create a new top-level message flow that embeds &1. Check everything back in and retry the deploy operation. BIP1756E Invalid top-level message flow &1 when deploying message flows. Explanation: When deploying message flow data, the document for message flow &1 was retrieved from the configuration repository, but was found to be invalid for use as a top-level message flow. It does not contain a reference to at least one other message flow. The cause is the direct assignment to an execution group of either one of the IBM primitive message flow, or an empty user-defined message flow. User Response: Make sure that the only message flows you assign to an execution group are those that reference other message flows. If &1 is user-defined, check out and complete the message flow. Check it back in and retry the deploy operation. BIP1757E Invalid run-time message flow &1 when deploying message flows. Explanation: When deploying message flow data, an XML document for message flow &1, (UUID=&2) was retrieved from the configuration repository, but was found to be invalid for use as a run-time message processing node. It contains element &3 which is not a permitted element in a message flow corresponding to a run-time message processing node. User Response: Establish the author of the message flow type. If the author is not IBM, contact the author to get the message flow 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.

26

MQSeries Integrator Messages

BIP1758E BIP1767S
BIP1758E Invalid message flow found when deploying message flows. Explanation: When deploying message flow data, an attempt was made by a message flow to override the value of a non-existent property of run-time message flow &2. The property in question is &1. The message flow in error is the one that embeds &2, and may be identified from label &3. User Response: This is probably caused by a message flow that corresponds to a run-time node having been replaced by a later version with different property names. Update the message flow 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. BIP1759S Invalid XML document found when deploying; missing &3 element. Explanation: When deploying configuration data, an XML document for &6, &4, (UUID=&5) was retrieved from the configuration repository, but was found to be invalid. The &1 element, identified by label &2, did not contain an &3 element. User Response: Identify the application that created the document. If this is not the Control Center, 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. BIP1760E Invalid message flow found when deploying message flows. Explanation: When resolving the connections between nodes in a message flow, a connection was found that could not be resolved to Output terminal &1 in message flow &3. The message flow in error is the one that embeds &3, and may be identified from label &2. User Response: The most likely cause is that &1 has been modified to remove Output terminal &1, but the message flow embedding &3 was not modified to remove the connection to Output terminal &1. Ensure that all message flows in the message flow are consistent, and retry the deploy operation. BIP1761E Invalid message flow &1 when deploying message flows. Explanation: When resolving the connections between nodes in a message flow, a connection was found that resolved to an Output terminal in message flow &1, but the Output terminal is not connected to an Output terminal of an embedded message flow. User Response: Check out message flow &1 and ensure that all Output terminals are correctly connected. Check in &1 and retry the deploy operation. BIP1762E Invalid message flow found when deploying message flows. Explanation: When resolving the connections between nodes in a message flow, a connection was found that could not be resolved to Input terminal &1 in message flow &3. The message flow in error is the one that embeds &3, and may be identified from label &2. User Response: The most likely cause is that &1 has been modified to remove Input terminal &1, but the message flow embedding &3 was not modified to remove the connection to Input terminal &1. Ensure that all message flows in the message flow are consistent, and retry the deploy operation. BIP1763E Invalid message flow &1 when deploying message flows. Explanation: When resolving the connections between nodes in a message flow, a connection was found that resolved to an Input terminal in message flow &1, but the Input terminal is not connected to an Input terminal of an embedded message flow. User Response: Check out message flow &1 and ensure that all Input terminals are correctly connected. Check in &1 and retry the deploy operation. BIP1764E Invalid message flow &1 when deploying message flows. Explanation: When deploying message flow data, the document for message flow &1 could not be found in the configuration repository. User Response: The message flow document referenced by &1 has either been deleted or has not been checked in. Correct the problem and retry the deploy operation. BIP1765S Unexpected error processing a broker message: record for &3 (UUID=&4) missing from &1 table, section &2. Explanation: When processing a response message from a broker, a record was found to be missing from the configuration repository &1 table, (&2 section). The record in question was for &3 (UUID=&4). User Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center. BIP1767S Unexpected exception in Configuration Manager ResolveXML class &1 method; exception text &2. Explanation: An exception was caught by the Configuration Manager ResolveXML class &1 method. The exception text is: &2. User Response: This is an internal error. Contact your IBM support center.

Chapter 2. Messages

27

BIP1768S BIP1801S
BIP1768S Invalid message flow type found when deploying message flows: badly formed &1 attribute value. Explanation: When deploying message flow data and resolving the connections between nodes, a Connection element was found that had a badly formed &1 attribute value. The UUID and terminal name components of the value should be separated by a . character but there was no such character present. User Response: This is an internal error. Turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center. BIP1769E Invalid message flow type &1 deploying message flows; Input terminal wired directly to Output terminal. Explanation: When deploying message flow data, the document for message flow &1 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. User Response: Check out &1 and remove the connection between the Input terminal and the Output terminal. Alternatively, if passthru behaviour 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. Check in &1 and retry the deploy operation. BIP1770S Invalid XML document for &3 &2 (UUID=&4) when processing a broker message: missing <&1> tag. Explanation: When processing a response message received from a broker, an XML document for &3 &2 (UUID=&4) was retrieved by the Configuration Manager from the configuration repository, but the XML document did not contain the expected <&1> tag as the document element. User Response: This is an internal error; turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center. BIP1771E Invalid run-time message flow &1 when deploying message flows; no Input terminal or Output terminal. Explanation: When deploying message flow data, an XML document for message flow &1 (UUID=&2) 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 Input terminal or an Output terminal. User Response: Establish the author of the message flow. If the author is not IBM, contact the author to get the message flow 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. BIP1772E Invalid run-time message flow &1 when deploying message flows. Explanation: When deploying message flow data, an XML document for message flow &1, (UUID=&2), 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 is entirely empty or only contains Input terminals or Output terminals. User Response: Establish the author of the message flow. If the author is not IBM, contact the author to get the message flow 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. BIP1773E Invalid recursive use of message flow &1 (label &2) when deploying message flows. Explanation: When deploying message flow data, message flow &1 was found to be used recursively. This is not permitted. The instance of this message flow causing the problem is &2. User Response: Correct the message flow and retry the deploy operation. BIP1774E Invalid message flow found when deploying message flows. Explanation: When deploying message flow data, the document for message flow &2 was retrieved from the configuration repository but was found to be invalid. It contains a promoted property &1 which contains no reference to any underlying properties. User Response: The usual cause of this problem is deleting all underlying property references from a promoted property and not replacing them, when using the Promote Property dialog of the Control Center. Check out message flow &2 and using the Promote Properties dialog either delete empty promoted property &1 or promote one or more properties into it. Check in &1 and retry the deploy operation. BIP1801S Internal error within the Configuration Manager accessing message repository: file &1, line &2; MRM return code &3. Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. The MRM return code &3 was detected in File &1, Line &2. User 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.

28

MQSeries Integrator Messages

BIP1802E BIP1813W
BIP1802E Unknown message repository database name &1. Explanation: When starting (creating or deleting) the Configuration Manager, the message repository database name &1 could not be located. User Response: This error is most probably a result of either, an incorrect name was provided for the -m option on the mqsicreateconfigmgr command, or the ODBC data source name &1 was not set up correctly, or has been deleted. First 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. Then, if necessary, delete your Configuration Manager (using the mqsideleteconfigmgr command). To preserve your configuration data in the configuration repository and message repository, do not specify the -n and -m flags on the mqsideleteconfigmgr command. Then re-create your Configuration Manager (using the mqsicreateconfigmgr command). BIP1805E The userid and/or password are not authorized for connection to the message repository database &1. Explanation: When starting (creating or deleting) the Configuration Manager, the message repository database name &1 could not be opened because the userid and/or password is not authorized. User Response: This error is most probably a result of either, incorrect userid and password were provided for the -e and -r options on the mqsicreateconfigmgr command, or the userid has not been assigned access rights to the message repository database by the database management system. First check that the message repository database 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. BIP1806E The Configuration Manager is not authorized to access the message repository database &1. Explanation: When starting the Configuration Manager, the userid is not authorized to access the message repository database &1. User Response: This error is most probably a result of a setup inconsistency. You must delete your Configuration Manager (using the mqsideleteconfigmgr command) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command), ensuring that the -m, -e, and -r options are set correctly. BIP1807S The message repository database &1 has not been initialized correctly. Explanation: When starting the Configuration Manager, it is not possible to access the message repository because the database &1 has not been properly initialized. User 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 re-create your Configuration Manager (using the mqsicreateconfigmgr command). BIP1809E The message repository resource (&1) cannot be deleted: referenced by resource &2 which is checked out. Explanation: The message repository resource (&1), cannot be deleted because it is referenced by the following resources that are checked out : &2. User Response: Retry the delete operation once all the listed resources have been checked in. BIP1810S Internal error within Configuration Manager while accessing message repository: file &1, line &2; insufficient memory. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository, due to insufficient memory. The error was detected in File &1, Line &2. User Response: Stop and restart the Configuration Manager and retry the operation. If the error persists turn on Configuration Manager tracing to capture details of the error, retry the operation and contact your IBM support center. BIP1812S An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An unexpected exception has been detected within the Configuration Manager code while accessing the message repository. User 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. BIP1813W Message repository resource (&2, &3) not locked: &1 operation not permitted. Explanation: The &1 operation is not permitted because the message repository resource (&2, &3) is not locked, or is locked by another user. User Response: Check out &2, &3 and retry the operation.

Chapter 2. Messages

29

BIP1814E BIP1824E
BIP1814E Element qualifier already assigned within message (&1): element qualifier (&2) already assigned. Explanation: An error occurred when creating or updating the message (&1), because the element qualifier (&2) has already been assigned to another element within this message. User Response: Remove assignment of element qualifier (&2), or select a different element qualifier. BIP1816E An internal error has occurred within the Configuration Manager while accessing the message repository. The repository has not been initialized Explanation: An internal error has occurred within the Configuration Manager while accessing the message repository. The message repository has not been opened. User 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. BIP1817S An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. The message repository WebDav DLL (mrxwebdv.dll) is not correctly installed. User 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 re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1818E Invalid property type (&4) of property (&3) for message repository resource (&1, &2): type should be (&5). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the type (&4) of a property (&3) is not correct. The type of the property should be (&5). User Response: The resource may have been corrupted. For an existing resource, check it out again. For a new resource delete and recreate it, then retry the operation. If the error persists contact your IBM support center. BIP1819E Invalid property group (&2) for message repository resource: property (&1); expected property group (&3). Explanation: An error occurred when updating or creating the message repository resource because the property group (&2), of a property (&1), is not correct. The group of the property should be (&3). User Response: The resource may have been corrupted. For an existing resource, check it out again. For a new resource, first delete it, then recreate it and try the operation again. If the error persists contact your IBM support center. BIP1820E Resource &1 (UUID=&2) does not exist in message repository. Explanation: The resource (&1) is referenced, but it does not exist in the message repository. The UUID of the resource is &2. User Response: It is probable that the resource (&1) has been newly created, and never checked in. Retry the operation once it has been checked in. BIP1821E Operation &1 cannot be completed; file name must be specified. Explanation: The operation &1 could not be completed, as a file name must be provided. User Response: Enter a filename and retry the operation. BIP1822E Generate language bindings operation not completed successfully: report file xtrcterr.log created in &1. Explanation: The generate language bindings (C header files) operation encountered one or more errors. A report file, (xtrcterr.log, located in &1), has been created. User Response: See the xtrcterr.log file for details of the error. BIP1823E Generate Language Bindings operation not completed successfully: report file xtrcterr.log created in &1. Explanation: The generate language bindings (COBOL copybook files) operation encountered one or more errors. A report file, (xtrcterr.log, located in &1), has been created. User Response: See the xtrcterr.log file for details of the error. BIP1824E Generate Glossary operation not completed successfully: report file xtrcterr.log created in &1. Explanation: The generate Glossary documentation operation encountered one or more errors. A report file, (xtrcterr.log, located in &1), has been created. User Response: See the xtrcterr.log file for details of the error.

30

MQSeries Integrator Messages

BIP1825E BIP1837E
BIP1825E Generate Message Book operation not completed successfully: report file xtrcterr.log created in &1. Explanation: The generate message book documentation operation encountered one or more errors. A report file, (xtrcterr.log, located in &1), has been created. User Response: See the xtrcterr.log for details of the error. BIP1826E Generate DTD operation not completed successfully: report file DTDERR.LOG created in &1. Explanation: The generate DTD operation encountered one or more errors. A report file, (DTDERR.LOG, located in &1), has been created. User Response: See the DTDERR.LOG file for details of the error. BIP1827E Invalid value (&4) for property (&3) in message repository resource (&1, &2). Explanation: An error has been detected when creating or updating a message repository resource (&1, &2). The value (&4), for property (&3), is not valid. User Response: Change the value and retry the operation. BIP1829E Error occurred while setting the suspend property to No for message repository resource (&1, &2). Explanation: An error occurred while setting the suspend property for message repository resource (&1, &2) to Noas the message repository resource is referencing one (or more) of the following resources which are currently suspended:- (&3) User Response: Set the suspend property to No for each of the listed resources and re-try the operation. BIP1830E Operation (&1) not completed: file (&2) does not exist. Explanation: The operation (&1) could not be completed because the specified file (&2) does not exist. User Response: Enter another file that is valid for the Configuration Manager and retry the operation. BIP1831E Operation (&1) cannot be completed: cannot open file (&2). Explanation: The operation (&1) could not be completed because the file (&2) could not be opened as it is in use by another program or user. The Configuration Manager requires access to this file in order to complete the operation. User Response: Retry the operation once the file is available for use. BIP1832E An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. The message repository Documentation DLL (mrxdoc.dll) is not registered for the message set. User Response: This error is most probably a result of a set-up inconsistency. You must delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1834E Internal error within Configuration Manager while accessing message repository. Open failed for message set (&1, &2): MRM return code &3. Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. An open failed for a message set (&1, &2). The MRM return code is &3. User 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. BIP1835E The create runtime message dictionary operation has not completed successfully. Explanation: The create runtime message dictionary operation encountered one or more errors. A report file, (rtderror.log), has been created in &1. User Response: See the rtderror.log file for details of the error. BIP1836E The create wire format descriptor operation has not completed successfully. Explanation: The create wire format descriptor operation encountered one or more errors. A report file, (cwferror.log), has been created in &1. User Response: See the cwferror.log file for details of the error. BIP1837E The message set (&1, Level &2) is not locked. Explanation: An attempt to freeze the message set (&1, Level &2) has failed because the message set is not locked. User Response: Check out the message set and retry the operation.

Chapter 2. Messages

31

BIP1838E BIP1856E
BIP1838E Cannot freeze the message set (&1, Level &2). Explanation: A freeze operation has failed for the message set (&1, Level &2). The probable cause for this is one or more incomplete messages. For example: A message containing an element of an empty compound type. User Response: Update any incomplete resources that belong to the message set and then retry the operation. BIP1839E A resource within the message set (&1, Level &2) is locked. Explanation: An attempt to freeze or finalize a message set has failed because one or more resources within the message set are locked. User Response: Check in or unlock all resources within the message set and retry the operation. BIP1840E Cannot finalize the message set (&1). Explanation: A finalize operation has failed for the message set (&1). The probable cause for this is one or more incomplete messages. For example: A message containing an element of an empty compound type. User Response: Update any incomplete resources that belong to the message set and then retry the operation. BIP1841E The message set (&1, Level &2) is not locked. Explanation: An attempt to unfreeze the message set (&1, Level &2) has failed because the message set is not locked. User Response: Check out the message set and retry the operation. BIP1842E Cannot unfreeze the message set (&1, level &2). Explanation: An unfreeze operation has failed for the message set (&1, Level &2). User 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. BIP1843E Error creating or updating message repository resource (&1, &2): referenced resource (&3, &4) does not exist. Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because it contains a reference to the resource (&3, &4) that does not exist in the message repository. The probable cause of this is that (&3, &4) has never been checked in. User Response: Check in (&3, &4) and try again. BIP1851E Operation &1 cannot be completed: path must be specified. Explanation: The operation &1 could not be completed, as a path must be provided. User Response: Enter a fully-qualified path name and try again. BIP1852W The operation &1 was not completed. Explanation: The operation &1 was not completed because no message repository resources of the selected type exist. User Response: Check in any new resources of the selected type, or select an alternative resource type and retry the operation. BIP1853E Error creating or updating message repository resource (&1, &2): invalid identifier (&3). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the identifier is invalid. The first character of an identifier must be an alpha character, and remaining characters must be alpha or numeric. An identifier may not exceed 254 characters. User Response: Change the identifier and try again. BIP1854E Error creating or updating message repository resource (&1, &2): duplicate identifier (&3). Explanation: An error occurred when updating or creating the message repository resource (&1 &2) because another resource in the message set exists with a duplicate identifier. No two resources in the message set may have the same identifier. Also no two resources of the same type in the message set may have identifiers that differ only in case. User Response: Change the identifier and try again. If this is not permitted, delete the resource and recreate it with a different identifier. BIP1855E Error updating message repository resource (&1, &2): identifier may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the identifier may not be modified. User Response: Check out the resource again to refresh your copy of the resource. BIP1856E Error creating or updating message repository resource (&1, &2): invalid name. Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the name is invalid. A name must be specified and must not exceed 254 characters. User Response: Change the name and try again.

32

MQSeries Integrator Messages

BIP1857E BIP1867E
BIP1857E Identifier may not be modified. Check In for &1, &2 was not successful as the &1 name may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the name may not be modified. User Response: Check out the resource again to refresh your copy of the resource. BIP1858E Error updating message repository resource (&1, &2): property value may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the values of one or more properties may not be changed. User Response: Check out the resource again to refresh your copy of the resource. BIP1859E Internal error updating message repository resource (&1, &2). Explanation: An internal inconsistency has been detected within the Configuration Manager code when creating or updating a message repository resource (&1, &2). Invalid value for class. User 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. BIP1860E An internal error has occurred within the Configuration Manager while accessing the message repository. Check In for &1, &2 was not successful as an invalid category has been specified. Explanation: An internal inconsistency has been detected within the Configuration Manager code when creating or updating a message repository resource (&1, &2). Invalid value for category. User 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. BIP1861E Error creating or updating message repository resource (&1, &2): invalid type. Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the type is not valid. The probable cause for this is that the type has been suspended. User Response: Resume or change the type and try again. BIP1862E Error creating or updating message repository resource (&1, &2): invalid message mode. Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the mode is invalid. User Response: Change the mode and try again. BIP1863E Error updating message repository resource (&1, &2): type may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the type may not be modified. User Response: Check out the resource again to refresh your copy of the resource. BIP1864E Error updating message repository resource (&1, &2): element may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the element may not be modified. User Response: Check out the resource again to refresh your copy of the resource. BIP1865E Error updating message repository resource (&1, &2): invalid element (&3). Explanation: An error occurred when updating the message repository resource (&1, &2) because a valid element is not referenced. User Response: It is probable that the element (&3) has been suspended from use. Alternatively, the element (&3) has been newly created and never checked in. Retry the operation after it has been resumed or checked in. BIP1866E Error creating or updating message repository resource (&1, &2): invalid value for minimum value property (&3). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the value of the minimum value property is not valid. User Response: Correct the minimum value and try again. Note for INTEGER element valid values, the minimum value must be a valid integer. BIP1867E Error creating or updating message repository resource (&1, &2): invalid value for maximum value property (&3). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the value of the maximum value property is not valid. User Response: Correct the maximum value and try again. Note for INTEGER element valid values, the maximum value must be a valid integer and equal to
Chapter 2. Messages

33

BIP1868E BIP1876E
or greater than the minimum value. BIP1868E Error creating message set (&1, &2): base message set (&3) does not exist. Explanation: An error occurred when creating the message set (&1, &2) because the base message set does not exist. User Response: Check that the base message set has been checked in and retry the operation. BIP1869E Error creating message set (&1, &2): base message set (&3) is not finalized. Explanation: An error occurred when creating the message set (&1, &2) because the base message set has not been finalized. User Response: Retry the operation once the base message set has been finalized. BIP1870E Error creating message set (&1, &2): invalid level (&2). Explanation: An error occurred when creating the message set (&1) because the level number is invalid. The level number must be greater than zero. If the new message set is based on another message set of the same name, the level number must be greater than that of the base message set. User Response: Change the level number and retry the operation. BIP1871E Duplicate message set name (&1). Explanation: An error occurred when creating the new message set (&1) because another message set exists with the same name, or an existing message set is based on a message set with the same name. You can create a new message set with the same name as an existing message set but, the new message set must be based on an existing message set with the same name, and the base message set must have a higher level number than any existing message set with the same name. User Response: Correct the message set name and retry the operation. BIP1872E Internal error within Configuration Manager accessing message repository, whilst creating or updating message set (&1): base mode (&2) is invalid. Explanation: An internal inconsistency has been detected within the Configuration Manager code when creating or updating a message set (&1). The base mode (&2) is invalid. User 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. BIP1873E Error creating or updating message repository resource (&1, &2): invalid element length (&3). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the element length has not been specified correctly. All elements of type STRING require an element length. In addition to this, the associated length cannot be suspended. Other elements should not have an element length. User Response: Make sure that the element length is specified correctly based on the type of the element. If the element length has been newly created, make sure it has been checked in before retrying the operation. Alternatively, if the element length is suspended, set its suspend property to No before retrying the operation. BIP1874E Error creating or updating message repository resource (&1, &2): invalid maximum length value (&3). Explanation: An error occurred when updating or creating the message repository resource (&1, &2) because the maximum length value is invalid. The maximum length value must be a number greater than zero. User Response: Correct the maximum length value and retry the operation. BIP1875E Error creating or updating message repository resource (&1, &2): message set (&3) not open. Explanation: An internal inconsistency has been detected within the Configuration Manager code when creating or updating a message repository resource (&1, &2). The message set (&3) is not open. User 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. BIP1876E Error creating or updating message repository resource (&1, &2): message set (&3) is frozen. Explanation: An error has been detected when creating or updating a message repository resource (&1, &2). The message set (&3) is frozen. User Response: In the case of a new resource, Unfreeze the message set and retry the operation. In the case of an existing resource, this is an internal error that may be due to data corruption in the message repository. Turn on Configuration Manager tracing to capture details of the error, retry the operation and contact your IBM support center.

34

MQSeries Integrator Messages

BIP1877E BIP1886S
BIP1877E Error creating or updating message repository resource (&1, &2): message set (&3) not open for write access Explanation: An internal inconsistency has been detected within the Configuration Manager code when creating or updating a message repository resource (&1, &2). The message set (&3) is not open for write access. User 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. BIP1878E Error updating message repository resource (&1, &2): property value(s) for resource (&3, &4) may not be modified. Explanation: An error occurred when updating the message repository resource (&1, &2) because the values of one or more properties relating to the resource (&3, &4) may not be changed. User Response: Check out the resource (&1, &2) again to refresh your copy of the resource. BIP1879E Error updating message repository resource (&1, &2): insert of resource (&3, &4) is not valid. Explanation: An error occurred when updating the message repository resource (pointed to by the inserts) because the resource (pointed to by the inserts) may not be inserted. User Response: Remove (&3, &4) from (&1, &2) and retry the operation. BIP1880E Error updating message repository resource (&1, &2): removal of resource (&3, &4) is not valid. Explanation: An error occurred when updating the message repository resource (&1, &2) because the resource (&3, &4) may not be removed. User Response: Check out the resource (&1, &2) again to refresh your copy of the resource. BIP1881S An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. The message repository WebDav DLL (mrxwebdv.dll) is not correctly installed. User Response: This error is most probably a result of a set-up inconsistency. You must delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1882E Error creating or updating message repository resource (&1, &2): invalid value (&6) for property (&5) or resource (&3, &4). Explanation: An error has been detected when creating or updating a message repository resource. The value of the property, for the resource is not valid. The value, property, and resource in question are indicated by the inserts in the message above. User Response: Change the value and retry the operation. BIP1883S Internal error within Configuration Manager accessing message repository: exception text &1. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. An XML parser exception occurred. The text of the exception is (&1). User 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. BIP1884S Internal error within Configuration Manager accessing message repository: exception text &1. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. A DOM parser exception occurred. The text of the exception is (&1). User 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. BIP1885S Internal error within Configuration Manager accessing message repository: CFileException cause &3 IOserror &4; file &1, line &2. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. A file access error, (CFileException cause &3 IOserror &4), was detected in File &1, Line &2. User 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. BIP1886S An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. The error was due to invalid content of an XML document. User Response: This is an internal error. Turn on
Chapter 2. Messages

35

BIP1887S BIP1898E
Configuration Manager tracing to capture details of the error, retry the operation and contact your IBM support center. BIP1887S An internal error has occurred within the Configuration Manager while accessing the message repository. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. The error was due to invalid content of an XML document. User 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. BIP1888E Operation &1 could not be completed. Access to the specified path is not permitted for the Configuration Manager. Explanation: The operation &1 could not be completed because access to the specified path is not permitted for the Configuration Manager. The Configuration Manager requires access to the path in order to create new files as a result of the operation. User Response: Enter another path for which the Configuration Manager has the correct authorization and retry the operation. BIP1889E Operation &1 could not be completed. No space available at location specified by path. Explanation: The operation &1 could not be completed because there is not sufficient space available at the location specified by path. The Configuration Manager requires space in order to create new files as a result of the operation. User Response: Free up some space, or enter another path at which sufficient space is available and retry the operation. BIP1890E Operation &1 could not be completed. Invalid path (&2). Explanation: The operation &1 could not be completed because the specified path is not valid for the Configuration Manager. The Configuration Manager requires access to the path in order to create new files as a result of the operation. User Response: Enter another path that is valid for the Configuration Manager and retry the operation. BIP1891E C Importer operation failed: report file (&1) created. Explanation: The C Importer operation encountered one or more errors or conflicts. A report file, (&1) has been created that contains further details on the result of the import and any errors. User Response: See the report file for the details. BIP1892E COBOL Importer operation failed: report file (&1) created. Explanation: The COBOL Importer operation encountered one or more errors or conflicts. A report file, (&1), has been created that contains further details on the result of the import and any errors. User Response: See the report file for the details. BIP1893S Unexpected exception (&1) detected whilst accessing the message repository: exception text &2. Explanation: An unexpected exception (&1) has been detected within the Configuration Manager code while accessing the message repository. The text of the exception is (&2). User 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. BIP1895S Delete is not permitted. Explanation: An attempt to delete a message repository resource has failed because delete is not permitted for this resource. User Response: The probable reason for this error is an attempt to delete a resource that was inherited from the base message set. Delete is not permitted for such a resource. As an alternative to delete, modify the resource setting Removed from View to true. BIP1897E An internal error has occurred within the Configuration Manager while creating the message repository: DLL (&1) is not valid. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because a message repository DLL (&1) is not valid. User Response: This error is most probably a result of a set-up inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1898E An internal error has occurred within the Configuration Manager while creating the message repository. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file WSMRI.INST is empty. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the

36

MQSeries Integrator Messages

BIP1899E BIP1904E
Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1899E An internal error has occurred within the Configuration Manager while creating the message repository: DLL (&1) could not be loaded. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because a message repository DLL (&1) could not be loaded. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1900E An internal error has occurred within the Configuration Manager while creating the message repository: defaults in file &1 are invalid. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file (&1), Defaults section is not valid. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1901E An internal error has occurred within the Configuration Manager while creating the message repository: plug-in section of file (&1) is invalid. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file (&1), plug-in section is not valid. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1902E An internal error has occurred within the Configuration Manager while creating the message repository: file (&1) cannot be opened. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file (&1), could not be opened. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1903E An internal error has occurred within the Configuration Manager while creating the message repository: file (&1) is not valid. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file (&1), is not valid. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then 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). If the error persists contact your IBM support center. BIP1904E An internal error has occurred within the Configuration Manager while creating the message repository: message repository DLL (&1) is a duplicate. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because a message repository DLL, (&1), is a duplicate. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager, (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center.

Chapter 2. Messages

37

BIP1905E BIP1911E
BIP1905E Create ConfigMgr was unsuccessful as the Import Export DLL, &1, could not be located. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the message repository Import Export DLL, (&1), could not be loaded. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager, (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1906E An internal error has occurred within the Configuration Manager while creating the message repository: Import Export DLL (&1) is not valid. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the message repository Import Export DLL, (&1), is not valid. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1907E An internal error has occurred within the Configuration Manager while creating the message repository: updates could not be saved to the message repository database (&1); MRM return code &2. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database, (&1), updates could not be saved. The MRM return code is &2. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1908E An internal error has occurred within the Configuration Manager while accessing the message repository: exception text &1. Explanation: An internal error has been detected within the Configuration Manager code while accessing the message repository. A SAX parser exception occurred. The text of the exception is (&1). User 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. BIP1909E An internal error has occurred within the Configuration Manager while creating the message repository: failed to import file &1. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file, (&1), failed to import due to an error in the XML content. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1910E An internal error has occurred within the Configuration Manager while creating the message repository: wrong release for message repository DLL (&1). Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because a message repository DLL, (&1), is not the correct release. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1911E An internal error has occurred within the Configuration Manager while creating the message repository: message set (&1) is already loaded. Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because a message set, (&1), is already loaded. User Response: This error is most probably a result of

38

MQSeries Integrator Messages

BIP1912E BIP1921E
a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager, (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1912E An internal error has occurred within the Configuration Manager while creating the message repository: XML parser error importing file (&1). Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because an XML parser error occurred when importing the file (&1). User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1913E An internal error has occurred within the Configuration Manager while creating the message repository: XML DOM error importing file (&1). Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because an XML DOM error occurred when importing the file (&1). User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1915E An internal error has occurred within the Configuration Manager while creating the message repository: MRM error importing file (&1). Explanation: An internal inconsistency has been detected within the Configuration Manager code while creating the message repository. The message repository database could not be initialized because the file, (&1), failed to import due to an MRM error. User Response: This error is most probably a result of a setup inconsistency. You should first reinstall the Configuration Manager, then delete your Configuration Manager, (using the mqsideleteconfigmgr command with the -n and -m options). Then recreate your Configuration Manager, (using the mqsicreateconfigmgr command with the -n and -m options). If the error persists contact your IBM support center. BIP1916E An error has occurred within the Configuration Manager while connecting to the message repository database (&1). Explanation: An error has occurred within the Configuration Manager code while creating (or deleting) the message repository. An unexpected error was detected when connecting to the message repository database (&1). User 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. BIP1917E Database manager not started: message repository database (&1) could not be accessed. Explanation: When either accessing, starting, creating, or deleting the Configuration Manager, the message repository database name, &1, could not be accessed. The database manager has either not been started, or has been stopped. User Response: Start the database manager and try again. BIP1918I C import completed successfully: report file (&1) created. Explanation: A report file, (&1), has been created that contains further details of the import operation. User Response: No user action required. BIP1919I COBOL import completed successfully: report file (&1) created. Explanation: A report file, (&1), has been created that contains further details of the import operation. User Response: No user action required. BIP1920E Error creating or updating message repository resource (&1, &2): message set (&3, level &4) finalized. Explanation: An error occurred when creating or updating the message repository resource, (&1, &2), because the message set (&3, level &4) is finalized. User Response: Do you really intend to update the messages that are defined within this message set? If so, you may create a new message set based on the message set (&3, level &4) in which you can create new resources and modify existing resources. BIP1921E Error updating message set (&1, level &2): message set is finalized. Explanation: An error occurred when updating the message set (&1, level &2) because the message set is finalized. User Response: Do you really intend to update the
Chapter 2. Messages

39

BIP1922E BIP1932E
messages that are defined within this message set? If so, you may create a new message set based on the message set (&1, level &2) in which you can create new resources and modify existing resources. BIP1922E Error updating message set (&1, level &2): message set is frozen. Explanation: An error occurred when updating the message set (&1, level &2) because the message set is frozen. User Response: Unfreeze the message set and retry the operation. BIP1923E Error creating or updating message repository resource (&1, &2): message set (&3, level &4) is frozen. Explanation: An error occurred when creating or updating the message repository resource (&1 &2) because the message set (&3, level &4) is frozen. User Response: Unfreeze the message set and retry the operation. BIP1924E Error creating or updating message repository resource: message set (&1, level &2) is frozen. Explanation: An error occurred when creating a new message repository resource because the message set (&1, level &2) is frozen. User Response: Unfreeze the message set and retry the operation. BIP1925E The message set (&1, level &2) is finalized. Explanation: An error occurred when creating a new message repository resource because the message set (&1, level &2) is finalized. User Response: Do you really intend to update the messages that are defined within this message set? If so, you may create a new message set based on the message set (&1, level &2) in which you can create new resources and modify existing resources. BIP1926S Message repository resource (&1, &2) cannot be deleted: referenced by resources (&3). Explanation: An attempt to delete a message repository resource (&1, &2) has failed because it is currently referenced by the following resources: (&3). User Response: If you really do need to delete this resource, you must first remove all references. BIP1927I The Documentation Glossary extraction has completed successfully: see &1 for output. Explanation: See &1 for the Documentation Glossary extraction output. User Response: No user action required. BIP1928S URI (&1) references collection (&2) that does not exist within message set (&3, level &4). Explanation: An internal inconsistency has been detected within the Configuration Manager code while accessing the message repository. The URI (&1) provided references a collection that does not exist within the message set. User 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. BIP1929E A resource within the message set (&1, level &2) is locked. Explanation: An attempt to delete a message set has failed because one or more resources within the message set are locked. User Response: Retry the delete operation once all the listed resources have been checked in. BIP1930E The message repository resource (&1) cannot be checked in because of consequential changes to resource (&2) which is checked out. Explanation: An error occurred when updating the message repository resource (&1) because the change to &1 would also cause some changes to the following resources that are checked out: &2. User Response: Retry the Check In operation once all the listed resources have been checked in or unlocked. BIP1931E Error updating message repository resource (&1, &2): remove (or re-order) resource (&3, &4) is not valid. Explanation: An error occurred when updating the message repository resource because the relative position of the external resource has changed. The external resource must maintain its position relative to all other external resources within the message repository resource. User Response: Check in the resource (&1, &2) again to refresh your copy of the resource. BIP1932E Error updating message repository resource (&1, &2): reference to resource (&3, &4) cannot be suspended. Explanation: An error occurred when updating the message repository resource (&1, &2) because the reference to the resource (&3, &4) may not be suspended. User Response: If you really do need to update this resource you must first remove the reference to (&3, &4) and retry the operation.

40

MQSeries Integrator Messages

BIP1933E BIP1966E
BIP1933E Error updating message repository resource (&1, &2) while setting the suspend property for the child resource (&3, &4) to No. Explanation: The most probable cause of this error is that the referenced child resource (&3, &4) in turn references one or more suspended resources. User Response: Set the suspend property to No for one or more of the listed resources and retry the operation: (&3). BIP1934E Message Set (&1, Level &2) is incomplete. Explanation: A Runtime Dictionary or Custom Wire Format extract cannot be run on incomplete message set (&1, Level &2). The probable cause for this is one or more incomplete messages. For example: a message containing an element of an empty compound type. User Response: Update any incomplete resources that belong to the message set and then retry the operation. BIP1935S Message repository resource (&1, &2) cannot be suspended: referenced by resources (&3). Explanation: An attempt to suspend a message repository resource (&1, &2) has failed because it is currently referenced by the following resources: (&3). User Response: If you really do need to suspend this resource, you must first remove all references. BIP1936E An error has occurred while accessing the message repository database (&1). The SQL code (&2) and SQL state (&3) were returned. Explanation: The message repository database name, &1, could not be accessed. The SQL code (&2) and SQL state (&3) were returned. User Response: Check your database manager documentation for further information on this error. BIP1937I The Documentation Message Book extraction has completed successfully: see &1 for output. Explanation: See &1 for the Message Book extraction output. User Response: No user action required. BIP1961W Message set is not complete. Explanation: A message set must be complete before performing an export. User Response: Complete the message set and retry the command. BIP1962W The database transaction log size has been exceeded. Explanation: You have exceeded the transaction log size of the database. User Response: Increase the size of the database transaction log on your system and retry the command. BIP1963W An internal error has occurred while accessing the message repository. Explanation: There may insufficient memory to complete the operation. User Response: Increase the amount of virtual memory available on your system and retry the command. BIP1964W The message set to be imported has been finalized in this repository since the export file was created. Explanation: A record of this message set, indicating that it was finalized, exists in this repository because anothermessage set was based on it before it was deleted. User Response: Delete all message sets based on this message set or import a finalized version of the message set. BIP1965E Unknown message repository database name &1. Explanation: The message repository database name &1 could not be located. User Response: This error is most probably a result of either, an incorrect name that was provided for the MRMDataSourceName on the mqsimrmimpexp command, or the ODBC data source name &1 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. BIP1966E The userid and/or password are not authorized for connection to the message repository database &1. Explanation: The message repository database name &1 could not be opened because the userid and/or password is not authorized. User Response: This error is most probably a result of either, incorrect userid and password that were provided for the MRMDataSourceUserId and MRMDataSourcePassword on the mqsimrmimpexp command, or the userid has not been assigned access rights to the message repository database by the database management system. Check that the message repository database access rights have been correctly configured.

Chapter 2. Messages

41

BIP1967W BIP1983W
BIP1967W An internal error has occurred while accessing the message repository. Explanation: A SAX parser exception occurred. The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP1968W An internal error has occurred while accessing the message repository. Explanation: An XML parser error occurred. The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP1969W An internal error has occurred while accessing the message repository. Explanation: A DOM parser exception occurred. The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP1970W An unexpected exception has occurred while accessing the message repository. Explanation: The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP1971W An internal error has occurred while accessing the message repository. Explanation: The error was due to invalid content of an XML document. User Response: If the error persists contact your IBM support center. BIP1972W An internal error has occurred while accessing the message repository. Explanation: The error was due to invalid content of an XML document. User Response: If the error persists contact your IBM support center. BIP1973W Duplicate message set identifier. Explanation: The message set to be imported already exists in this respository. User Response: Delete the message set and retry the command. BIP1974W Failed to access export file &1. Explanation: The error code &2 was detected. User Response: Check that you have access rights to the export file. BIP1975W Failed to open import file &1. Explanation: There was a failure opening the import file &1. User Response: Check the file name entered and that you have access rights to the file. BIP1977W Mandatory argument missing. Explanation: When using this command interface the user should supply the mandatory arguments. User Response: Correct and retry the command. BIP1978W An internal inconsistency has been detected while accessing the message repository. Explanation: The MRM return code &1 was detected. This is an internal error. User Response: If the error persists contact your IBM support center. BIP1980W The message repository database &1 has not been initialized correctly. Explanation: It is not possible to access the message repository because the database &1 has not been properly initialized. This error is most probably a result of a set-up inconsistency. User Response: You must delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). BIP1981W An error has occurred while connecting to the message repository. Explanation: An unexpected error was detected when connecting to the message repository database &1. User Response: This is an internal error. Contact your IBM support center. BIP1982W Database manager not started. Explanation: The message repository database name, &1, could not be accessed. The database manager has either not been started, or has been stopped. User Response: Start the database manager and retry the command. BIP1983W The resource &1 does not exist in the message repository. Explanation: The resource &1 is referenced, but it does not exist in the message repository. User Response: Correct the problem and retry the command.

42

MQSeries Integrator Messages

BIP1998E BIP2014E
BIP1998E An error has occurred while accessing the NEON message repository database. Explanation: The Configuration Manager has failed to start because an error has occurred while instantiating the NEON Formatter Management API interface object. Details of the NEON error are recorded in the NEONMessageLog.nml file. The NEONMessageLog.nml is normally located in the MQSI bin directory. User Response: Correct the NEON configuration and retstart the Configuration Manager.

BIP2000-BIP2999 (Broker)
BIP2001I The MQSeries Integrator service has started, process ID &1. Explanation: The MQSeries Integrator service executable has been started. User Response: No user action required. BIP2002W The MQSeries Integrator service has stopped. Explanation: The MQSeries Integrator service has been stopped. User Response: No user action required. BIP2003W The MQSeries Integrator service has paused. Explanation: The MQSeries Integrator service has paused. User Response: Restart the MQSeries Integrator service as soon as possible. BIP2004I The MQSeries Integrator service is continuing. Explanation: The MQSeries Integrator service is now running. User Response: No user action required. BIP2005E Unsuccessful MQSeries Integrator service initialization. Explanation: The MQSeries Integrator service could not be registered. User Response: Check that the machine has adequate memory and that the userid and password used to start the broker are correct. BIP2006E Unable to start executable &1. Explanation: The MQSeries Integrator service could not start an executable. User Response: Make sure that the executable is in the correct directory and that the MQSeries Integrator service userid has permission to start the executable. Ensure that there is adequate memory available on the system. Reissue the command. BIP2007E The MQSeries Integrator service has detected that its child process has ended abnormally, process ID &1. Explanation: An executable started by the MQSeries Integrator service terminated abnormally. User Response: Check that the database and MQSeries are available. Determine the cause of the problem. BIP2009E The MQSeries Integrator service detected an unknown serviceHandler request. Explanation: An unknown request was directed to the MQSeries Integrator service. User Response: Trace the problem and contact your IBM support center. BIP2010E The MQSeries Integrator service has stopped, process ID &1. Explanation: The MQSeries Integrator service has stopped. User Response: Restart the MQSeries Integrator service when required. BIP2011W The MQSeries Integrator service has been shutdown, process ID &1. Explanation: The MQSeries Integrator service has stopped. User Response: Restart the MQSeries Integrator service when required. BIP2012E Unable to access the brokers database tables, the brokers database name is blank. Explanation: The broker is incorrectly configured. User Response: Correct the broker database name by deleting and recreating the broker, selecting a valid database name. Database names must not be blank. BIP2013E The broker was unable to access its database. Explanation: There was no running database available. User Response: Start the database, the broker will recover itself after a small delay. BIP2014E The MQSeries Integrator service was unable to start executable &1 due to a lack of system storage. Explanation: The system is short on storage. User Response: Enable more system storage.

Chapter 2. Messages

43

BIP2015E BIP2040I
BIP2015E The MQSeries Integrator service detected that executable &1 terminated, exit code &2. Explanation: An executable terminated unexpectedly. User Response: The MQSeries Integrator service will restart the executable automatically unless the broker is currently shutting down. Determine the reason for the unexpected termination of this executable. BIP2030E Execution group &1 could not be created, unable to open its process handle. Explanation: The broker could not create an execution group process. User 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. BIP2031E Unable to start execution group executable &1. Explanation: The broker could not create an execution group process. User 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. BIP2032E Unable to access the brokers database tables, the brokers database name is blank. Explanation: The broker is incorrectly configured. User Response: Correct the broker database name by deleting and recreating the broker selecting a valid database name. Database names must not be blank. BIP2033I The broker was forced to stop an execution group process, process ID was &1. 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. User Response: One reason for this is that the MQSeries Integrator 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 abnormal termination of the execution group and handled accordingly. Use the MQSeries 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. BIP2034E An unexpected exception was thrown. Explanation: An unexpected event occurred and an exception was created. User Response: Contact your IBM support center. BIP2035E The internal configuration message was rejected due to broker persistent store problem. Explanation: The brokers persistent store is not available, the internal configuration message was rejected because of this. User Response: Ensure that the brokers database is restarted. BIP2036E Unable to commit database information, rolling back for retry. Explanation: An exception occurred during database commit processing. User Response: The commit will be retried. BIP2037E The internal configuration message has been discarded. Explanation: An internal configuration message could not be processed to completion, multiple attempts were made to process the message. User Response: Examine the system log for problems, resolve the problems and redeploy the internal configuration message from the Control Center. BIP2038I The internal configuration message was rejected due to broker persistent store problem. Explanation: The brokers persistent store could not be updated, the internal configuration message was rejected because of this. User Response: Examine the system log for database problems, resolve the problems and redeploy the internal configuration message from the Control Center. BIP2040I Unable to commit database information, rolling back for retry. Explanation: An exception occurred during database commit processing. User Response: The commit will be retried.

44

MQSeries Integrator Messages

BIP2045E BIP2052E
BIP2045E Broker &1 (UUID &2) running on MQSeries queue manager &3 could not process an internal configuration message because the broker identity received in the message (UUID &4) did not match that of this broker. Explanation: An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the Control Center user creates a definition for the broker. The configuration message received contained a broker UUID (&4) that does not match the UUID of broker &1 running on MQSeries queue manager &3. There are two possible reasons for this. Either a Control Center user has accidentally specified queue manager &3 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker &1 was deleted and recreated on the Control Center which has the effect of giving broker &1 a new, different UUID. User Response: If the queue manager name specified in the Control Center was incorrect then use the Control Center to correct the broker definition in error. The mqsilist command may be used to display broker queue manager names. Otherwise, if the broker definition was deleted and recreated, you must use the mqsideletebroker and mqsicreatebroker commands to recreate the broker, then redeploy the configuration for the broker in order to re-establish the correct broker identity. To avoid loss of data when recreating the broker, make sure that you follow the sequence of actions defined in the MQSeries Integrator Administration Guide section Recovery and restart. BIP2046E Broker &1 (UUID &2) could not process an internal configuration message to completion: the problem was caused by missing tag &3. Explanation: The configuration message deployed by the Control Center could not be processed and was rejected. User Response: Use the inserts within this message to determine the cause of the problem, if possible correct the brokers configuration and redeploy from the Control Center. Contact your IBM support center if you are unable to resolve the problem. BIP2047E Broker &1 (UUID &2) could not process an internal configuration message because the broker name received in the message (&3) did not match that of this broker. Explanation: An internal configuration message could not be processed and was rejected. Each broker is given a name when the Control Center 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, &3, that did not match the name of this broker, &1. The probable cause is that a Control Center user has incorrectly renamed the broker in the broker definition. User Response: Use the Control Center to rename the broker back to the name specified on the mqsicreatebroker command. This name can be found using the mqsilist command. BIP2048E An exception was caught while issuing database SQL command &1. Explanation: The brokers database could not be accessed and an exception was generated. User Response: Ensure that the database is running. BIP2049E The broker made an unsuccessful attempt to access its database while attempting to execute SQL syncpoint/rollback. Explanation: The brokers database could not be accessed for a syncpoint/rollback. User Response: Ensure that the database is running. BIP2050E Broker &1 (UUID &2) received an internal configuration message that specified version &3, this broker is only capable of supporting up to and including version &4. Explanation: The versions of internal configuration message that the broker supports is dependent upon the MQSeries Integrator product that is installed. User 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 MQSeries Integrator Administration Guide book for migration guidance. Contact your IBM support center if you are unable to resolve the problem. BIP2051E Broker &1 (UUID &2) could not process an internal configuration message to completion, the problem was caused by &3. Explanation: The configuration message deployed by the Control Center could not be processed and was rejected. User Response: Use the inserts within this message to determine the cause of the problem. Correct the brokers configuration and redeploy from the Control Center. Contact your IBM support center if you are unable to resolve the problem. BIP2052E Broker &1 (UUID &2) could not process an internal configuration message to completion: the problem was caused by XML tag &3; value &4. Explanation: An internal configuration message could not be processed and was rejected.
Chapter 2. Messages

45

BIP2053E BIP2066E
User Response: Contact your IBM support center. BIP2053E The broker made an unsuccessful attempt to access its database &1 with userid &2. Explanation: The brokers database could not be accessed using the userid and password supplied. User Response: Ensure that the database is running and that the userid and password are correct. BIP2054E Unable to allocate memory for an internal function. Explanation: There is a shortage of memory on the system. User Response: Increase the amount of memory available to the system. BIP2056I Broker &1 successfully processed the entire internal configuration message. Explanation: An internal configuration message was processed to completion. User Response: No user action required. BIP2057E Execution group &1 could not be started: broker name &2; UUID &3; label &4; Pub-Sub server &5 (1=Yes, 0=No). Explanation: The broker was unable to start an execution group process. User Response: Ensure that the executable is available and that the brokers service userid has permission to run the executable. BIP2059E The broker has detected that the execution group &1, process ID &2, has shut down abnormally. Explanation: An execution group process ended abnormally. User Response: Investigate the reasons for the problem. BIP2060E The broker has detected that the execution group &1, process ID &2, has terminated. Explanation: An execution group stopped processing unexpectedly. A new instance of the execution group will be started in approximately &3 seconds. User 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 problem. BIP2061E Broker &1 has detected that applying the internal configuration would result in an unknown execution group state. Explanation: Applying the last internal configuration message received would result in undefined action. User Response: Contact your IBM support center. BIP2062E Broker &1 has rejected the internal configuration message received as it would have result in an invalid broker configuration. Explanation: The internal configuration message received could not be applied to the brokers configuration. This could occur for any of the following reasons: The internal configuration message directs an execution group to be created but the execution group already exists. The internal configuration message directs an execution group to be deleted but the execution group does not exist. The internal configuration message directs an execution group to be changed but the execution group does not exist. The internal configuration message is rejected. User Response: Correct the brokers configuration in the Control Center and redeploy. Contact your IBM support center if you are unable to resolve the problem. BIP2063E Broker &1 has detected that applying the internal configuration would result in a null execution group state. Explanation: Applying the last internal configuration message received would result in undefined action. User Response: Contact your IBM support center. BIP2064E Broker &1 has detected that applying the internal configuration would result in an unreportable state. Explanation: Applying the last internal configuration message received would result in undefined action. User Response: Contact your IBM support center. BIP2065I Broker &1 has processed a topology deployment. Explanation: The Control Center has deployed topology configuration. User Response: Determine if the deployment was successful by analysing the messages following this message. BIP2066E Broker &1 (UUID &2) unable to retrieve internal configuration response message for execution group &3. Explanation: The execution group did not respond in a timely manner. The internal configuration message response will be discarded if it arrives after this point. User 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 MQSeries 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

46

MQSeries Integrator Messages

BIP2067E BIP2076E
brokers configuration from the Control Center. Contact your IBM support center if you are unable to resolve the problem. BIP2067E Broker &1 (UUID &2) unable to get internal configuration response message for execution group &3 from MQSeries queue &4. Explanation: The execution group internal configuration response message queue has failed. User Response: Investigate why the MQSeries queue failed. Use the system log messages to determine and correct the problem. Redeploy the broker configuration message from the Control Center. BIP2068E The broker was unable to put an internal configuration message to message queue &1. Explanation: The internal configuration message could not be sent because the message queue was not available. User Response: Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the brokers configuration. BIP2069E The broker attempted to put an internal configuration message to an reserved message destination &1. Explanation: The message destination is reserved for use by the broker only. User Response: Investigate why the internal configurations reply message destination name was sent to a reserved destination. BIP2070E A problem was detected with MQSeries while issuing &1 for MQSeries queue &2, MQSeries queue manager &3. MQCC=&4, MQRC=&5. Explanation: The operation on the specified queue or queue manager returned with the indicated MQSeries completion and reason code. User Response: Check the MQSeries completion and reason codes in the MQSeries 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 MQSeries. 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. BIP2071E A problem was detected on MQSeries while issuing &1 for MQSeries queue &2, queue manager &3. MQSeries property &4 had an unsupported value of &5. Explanation: The operation on the specified queue was not successful because the message being received contained an MQSeries property that is not supported. User Response: Investigate why the unsupported property was being used. BIP2072E Execution group &1, process ID &2 was terminated. Explanation: The execution group process was terminated in preparation for a broker shutdown. User Response: Restart the broker when required. BIP2073S Unable to create a Java VM. Explanation: This is an internal error. User Response: Stop the Configuration Manager service and contact your IBM support center. BIP2074E A problem was detected with MQSeries while issuing &1 for MQSeries Queue Manager &2. MQCC=&3, MQRC=&4. Explanation: The operation on the specified queue manager returned with the indicated MQSeries completion and reason code. User Response: Check the MQSeries completion and reason codes in the MQSeries 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 MQSeries. 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. BIP2075E The broker was unable to send an internal configuration &1 message to Execution Group &2. Explanation: The internal configuration message could not be sent. User 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. BIP2076E The broker was unable to get an internal configuration &1 message response from Execution Group &2. Explanation: The internal configuration message response could not be retrieved. User Response: Investigate why the Execution Group
Chapter 2. Messages

47

BIP2077E BIP2089E
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. BIP2077E The broker received a negative response to an internal configuration &1 message from Execution Group &2. 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 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) User 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. BIP2078E The broker was unable to get an internal configuration message from message queue &1. Explanation: The internal configuration message could not be retrieved because the message queue was not available. User Response: Investigate why the message queue was not available by reviewing messages issued to the system log. Resolve the problem and redeploy the brokers configuration. BIP2079E The broker received a response without data for an internal configuration &1 message from Execution Group &2. 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. User 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. BIP2080E Execution Group &1 failed to return an internal configuration &2 message response within a &3 second time period. 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. User 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. Resolve the problem described in the system log. The broker will retry this operation later. BIP2081E Execution Group &1 process ID &2 could not be stopped by the broker. 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. User 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 occured. 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. BIP2086I Broker &1 could only process parts of the internal configuration message. Explanation: Parts of the internal configuration message were not processed successfully. User 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. BIP2087I Broker &1 was unable to process the internal configuration message. Explanation: The entire internal configuration message failed to be processed successfully. User Response: Use the messages following this message to determine the reasons for the failure. BIP2088E An unexpected exception &1 was caught. Explanation: The broker caught an unexpected exception. User 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. BIP2089E An internal configuration message was received but it contained no data. Explanation: The internal configuration message contained no data, the message was treated as a null operation. User Response: Contact your IBM support center.

48

MQSeries Integrator Messages

BIP2090S BIP2103S
BIP2090S The &1 environment variable is &2 characters long. The variable contains the following data: &3. Explanation: The attempt to dynamically set an environment variable was unsuccessful. User Response: Contact your IBM support center. BIP2091I The broker has reconnected to MQSeries successfully. Explanation: The broker was unable to communicate via MQSeries transports, communication has been re-established. User Response: Investigate the reasons for the MQSeries product termination. BIP2092I The broker has reconnected to its persistent store successfully. Explanation: The broker was unable to save information to its persistent store, this connection has been re-established. User Response: Investigate the reasons for the brokers persistent store being unavailable. BIP2093E Java class &1 could not be found. Explanation: This is an internal error, possibly due to a faulty installation. User Response: Stop the Configuration Manager service and contact your IBM support center. BIP2094E Java method &2 in class &1 could not be found. Explanation: This is an internal error, possibly due to a faulty installation. User Response: Stop the Configuration Manager service and contact your IBM support center. BIP2095E Instance of Java class &1 could not be instantiated. Explanation: This is an internal error, possibly due to a faulty installation. User Response: Stop the Configuration Manager service and contact your IBM support center. BIP2096S Java exception caught via the JNI from the &1 class: exception text &2. 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 MQSeries classes for Java installation. User 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. BIP2097E Java field &2 in class &1 could not be found. Explanation: This is an internal error, possibly due to a faulty installation. User Response: Stop the Configuration Manager service and contact your IBM support center. BIP2098E Unable to locate function &1 in implementation file &2, entry point &3. 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. User Response: Contact your IBM support center. BIP2099E Unable to initialize a parser factory. 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. User Response: Contact your IBM support center. BIP2101E Unable to allocate memory. 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. User 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. BIP2102E Invalid value (&1) for attribute (&2); node class=&3. 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. User Response: Modify the configuration request to specify a valid value for the attribute, and retry the request. BIP2103S Internal broker error; condition=&1. 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.
Chapter 2. Messages

49

BIP2106E BIP2117E
User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2106E Unable to allocate memory during operation performed by object &1. 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. User 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 systems 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. BIP2110E Message broker internal program error. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. There is no diagnostic information associated with this message User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2111E Message broker internal error: diagnostic information &1. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. The diagnostic information associated with this message is: &1. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2112E Message broker internal error: diagnostic information &1, &2. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2113E Message broker internal error: diagnostic information &1, &2, &3. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2114E Message broker internal error: diagnostic information &1, &2, &3, &4. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2115E Message broker internal error: diagnostic information &1, &2, &3, &4, &5. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2116E Message broker internal error: diagnostic information &1, &2, &3, &4, &5, &6. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2117E Message broker internal error: diagnostic information &1, &2, &3, &4, &5, &6, &7. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center.

50

MQSeries Integrator Messages

BIP2118E BIP2134E
BIP2118E Message broker internal error: diagnostic information &1, &2, &3, &4, &5, &6, &7, &8. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2119E Message broker internal error: diagnostic information &1, &2, &3, &4, &5, &6, &7, &8, &9. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2121E The thread bootstrap code caught an unhandled exception on thread &1. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. The exception was issued on thread &1. Futher information may be in the exception information associated with this message. User Response: Restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, then contact your IBM support center. BIP2122E An exception has been caught in thread clean up: diagnostic information &1, &2, &3, &4, &5, &6, &7, &8, &9. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, then contact your IBM support center. BIP2123E Thread terminate handler invoked: execution group will end; diagnostic information &1, &2, &3, &4, &5, &6, &7, &8, &9. Explanation: An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the brokers transactions. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, then contact your IBM support center. BIP2130E Error &2 converting a character string to or from codepage &1. 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. User 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. BIP2131E A character codepage conversion error has occurred. Explanation: An internal software error has occurred in the message broker. User Response: Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem continues to occur, contact your IBM support center. BIP2132E Invalid codepage &1 or conversion table &2 missing or invalid. 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. User Response: Check that the application generating the source message is using the correct code page within the message. BIP2133E Source field &1 is too long for a target field of length &2 when converting from unicode to codepage &3. 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. User 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. BIP2134E Source field &1 is too long for a target field of length &2 when converting to unicode from codepage &3. Explanation: An internal processing error has occurred. User Response: Contact your IBM support center.

Chapter 2. Messages

51

BIP2135E BIP2162S
BIP2135E Source character &1 in field &2 cannot be converted to unicode from codepage &3. Explanation: The source character is an invalid code point within the given codepage. User Response: Correct the application that generated the message. BIP2136E Source character &1 in field &2 cannot be converted from unicode to codepage &3. Explanation: The source character is an invalid code point within the given codepage. User 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. BIP2141E Unable to open MQSeries queue manager object; MQCC=&1, MQRC=&2. Explanation: An attempt to open the connected MQSeries queue manager to inquire about its settings failed. The MQSeries completion code and reason code returned are as displayed. Recovery processing of a backed-out message may not work as expected. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2142E Unable to issue MQINQ to inquire on MQSeries queue; queue=&1, MQCC=&2, MQRC=&3. Explanation: An attempt to issue an MQINQ function to inquire about the status of the specified queue failed. The MQSeries completion code and reason code returned are as displayed. Recovery processing of a backed out message will not work as expected. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2143E Unable to close MQSeries queue manager object; MQCC=&1, MQRC=&2. Explanation: An attempt to close the connected MQSeries queue manager failed. The MQSeries completion code and reason code returned are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2144E Node &1 received conversion error on either MQSeries queue manager or queue name. Explanation: The specified node was unable to convert the MQSeries queue manager or queue name to a wide string. The current message flow is terminated. User Response: Check the message flow to determine the cause of the error. BIP2145E Failed to connect to MQSeries queue manager &1; MQCC=&2, MQRC=&3. Explanation: The specified node failed to connect to the indicated MQSeries queue manager. The completion and reason codes returned by the MQCONN are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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 MQSeries. 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. BIP2160E Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: &1. Explanation: A broker process is terminating abnormally. User Response: Contact your IBM support center. BIP2161E Broker process terminating abnormally (stack full): diagnostic information for IBM &1. 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: &1. User 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. BIP2162S Header invalid, structure identifier incorrect at offset &1. 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. User Response: Contact your IBM support center.

52

MQSeries Integrator Messages

BIP2163S BIP2212E
BIP2163S Users environment is invalid. Explanation: The users environment was not adequately prepared to continue execution. Locate and run the sample profile supplied with the product. This is located in the product subdirectory sample/profiles. User Response: Run the sample 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. BIP2201I Execution group started: process &14; thread &15; additional information &1, &2, &3, &4, &5, &6, &7, &8, &9, &10, &11, &12, &13. Explanation: The execution group has been started using the following values: process &14; thread &15; broker &1; execution group UUID &2; execution group label &3; default execution group &4; queue manager &5; trusted &6; datasource &7; userid &8; password &9; migration needed &10; broker UUID &11; file path &12; work path &13. It will now start processing messages. User Response: No user action required. BIP2202E Administrative agent to execution group communication error: invalid value &2 supplied for execution group parameter &1. Explanation: The invalid value &2 was supplied for the execution group parameter &1. User Response: Stop and restart the broker. If the problem persists, stop, delete, recreate and then restart the broker. BIP2203E An execution group has encountered a problem whilst starting. Explanation: An execution group has encountered a problem whilst starting and is unable to continue. User 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. BIP2204I Execution group using process &1 thread &2 stopped. Explanation: The execution group using process &1 and thread &2 has stopped. This may be because it has been instructed to do so or because it has encountered a problem. User Response: No user action required. The execution group will be restarted automatically if need be. BIP2210E Invalid configuration message: attribute name &1 not valid for target object &2. Explanation: The message broker received a configuration message containing the attribute name &1 which is not valid for the target object &2. This can be caused by a mismatch in levels between the Control Center, 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 Control Center. User Response: Ensure that the levels of code installed at the Control Center, 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. BIP2211E Invalid configuration message containing attribute value &2 which is not valid for target attribute &1, object &4; valid values are &3. Explanation: The message broker received a configuration message containing the attribute value &2 which is not valid for the target attribute &1, on object &4. Valid values are &3. This can be caused by a mismatch in levels between the Control Center, 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 Control Center. User Response: Ensure that the levels of code installed at the Control Center, 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. BIP2212E Invalid configuration message containing action &1 which is not valid for target object &2. Explanation: The message broker received a configuration message containing the action &1 which is not valid for the target object &2. This can be caused by a mismatch in levels between the Control Center, 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 Control Center. User Response: Ensure that the levels of code installed at the Control Center, 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.

Chapter 2. Messages

53

BIP2213E BIP2240E
BIP2213E Invalid configuration message containing folder &1 which is not valid for target object &2. Explanation: The message broker received a configuration message containing the folder &1 which is not valid for the target object &2. This can be caused by a mismatch in levels between the Control Center, 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 Control Center. User Response: Ensure that the levels of code installed at the Control Center, 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. BIP2214E Invalid configuration message with no value for attribute &1, object &2. Explanation: The message broker received a configuration message which failed to supply a value for the attribute &1, on object &2. This can be caused by a mismatch in levels between the Control Center, 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 Control Center. User Response: Ensure that the levels of code installed at the Control Center, 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. BIP2220W No database specified for broker. Explanation: The message broker was created without a database being specified. Its configuration will not be stored persistently. User Response: No user action required. BIP2221E Invalid installation set up. Explanation: The message broker detected an error whilst connecting to its database. Its configuration will not be stored persistently. Messages describing the error follow. User Response: No user action required. BIP2222E Invalid database state: no database records for resource &1, &2. Explanation: The message broker could not locate the database records for the resource &1, &2. The active state of the broker may not be as expected. User Response: Check that the message brokers configuration database is currently started. Redeploy the complete broker configuration from the Control Center. If the problem persists, contact your IBM support center. BIP2223I A database operation was retried: attempt &1 of 10; diagnostic information &2. Explanation: The message broker encountered a database lock or timeout accessing its configuration database, and has retried the operation. This is attempt number &1 out of 10. Additional diagnostic information is &2. User Response: No user action required. BIP2224E A database operation failed after repeated attempts: diagnostic information &1. Explanation: The message broker encountered a database lock or timeout and has retried the operation repeatedly without resolving the problem. Additional diagnostic information &1. User Response: No user action required. BIP2230E Error detected whilst processing a message in node &1. Explanation: The message broker detected an error whilst processing a message in node &1. An exception has been thrown to cut short the processing of the message. User Response: See the following messages for details of the error. BIP2231E Error detected whilst processing a message &1. Explanation: The message broker detected an error whilst processing a message in node &1. The message has been augmented with an exception list and has been propagated to the nodes failure terminal for further processing. User Response: See the following messages for details of the error. BIP2232E Error detected whilst handling a previous error in node &1. Explanation: The message broker has detected an error in node &1 whilst handling a previous error. User 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. BIP2240E Configuration message requests the creation of message flow node &2 (UUID=&1) which already exists in message flow &3. Explanation: The message broker received a configuration message containing an instruction to create the message flow node &2 (UUID=&1), but this node already exists in the message flow &3. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring

54

MQSeries Integrator Messages

BIP2241E BIP2248E
that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2241E Configuration message requests creation of message flow node &1 in message flow &2; broker cannot create nodes of this type. Explanation: The message broker received a configuration message containing an instruction to create a message flow node of type &1, in message flow &2, but the broker does not have the capability to create nodes of this type. User Response: Ensure that all necessary node implementation libraries have been installed. Then ensure that the message flow and any nested message flows have been checked in. Re-deploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2242E Program error in node library. Explanation: The message broker detected a program error in a message flow node library whilst attempting to create a node. User Response: Ensure that the machine is not running low on virtual memory. If the problem persists, contact your IBM support center. BIP2243W Configuration message requests deletion of message flow node &1 which does not exist in message flow &2. Explanation: The message broker received a configuration message containing an instruction to delete the message flow node &1, but this node does not exist in the message flow &2. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2244E Request to create a connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6: connection already exists in message flow &7. Explanation: The message broker received a configuration message containing an instruction to create a connection between two node terminals, but this connection already exists in the message flow. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2245E Request to create connection between node UUID=&1 (label unknown) terminal &2, and node &4 (UUID=&3) terminal &5: source could not be found in message flow &6. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2246E Request to create connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6: source terminal could not be found in message flow &7. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2247E Request to create connection between node &2 (UUID=&1) terminal &3, and node UUID=&4 (label unknown) terminal &5: target cannot be found in message flow &6. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2248E Request to create connection between node &2 (UUID=&1) terminal &3;, and node &5 (UUID=&4) terminal &6: terminal cannot be found in message flow &7. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in.
Chapter 2. Messages

55

BIP2249E BIP2257E
Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2249E Request to create connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6: connection does not exist in message flow &7. Explanation: The message broker received a configuration message containing an instruction to create a connection between two node terminals, but this connection does not exist in the message flow. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2250W Request to delete connection between node UUID=&1 (label unknown) terminal &2, and node &4 (UUID=&3) terminal &5: source does not exist in message flow &6. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2251W Request to delete connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6: source terminal does not exist in message flow &7. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2252W Request to delete connection between node &2 (UUID=&1) terminal &3, and node UUID=&4 (label unknown) terminal &5: target node does not exist in message flow &6. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2253W Request to delete connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6: target terminal does not exist in message flow &7. 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. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2254I Message flow node &3 (UUID=&2) type &1 in message flow &4 successfully created. 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. User Response: No user action required. BIP2255I Message flow connection successfully created between node &2 (UUID=&1) terminal &3 and node &5 (UUID=&4) terminal &6. Explanation: The message broker received a configuration message containing an instruction to create a connection between two nodes, and successfully performed this action. User Response: No user action required. BIP2256I Attribute of message flow node &2 (UUID=&1) in message flow &3 successfully changed. Explanation: The message broker received a configuration message containing an instruction to change an attribute of the message flow node &2 (UUID=&1,) in the message flow &3 and successfully performed this action. User Response: No user action required. BIP2257E Request to change an attribute of message flow node &1: node does not exist in message flow &2. Explanation: The message broker received a configuration message containing an instruction to change an attribute of the message flow node &1, but

56

MQSeries Integrator Messages

BIP2258I BIP2268W
this node does not exist in the message flow &2. User Response: Ensure that the message flow, and any nested message flows have been checked in. Re-deploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center. BIP2258I Message flow node &2 (UUID=&1) in message flow &3 successfully deleted. Explanation: The message broker received a configuration message containing an instruction to delete the message flow node &2 (UUID=&1), in the message flow &3 and successfully performed this action. User Response: No user action required. BIP2259I Connection between node &2 (UUID=&1) terminal &3, and node &5 (UUID=&4) terminal &6 successfully deleted. Explanation: The message broker received a configuration message containing an instruction to delete the connection between two nodes and successfully performed this action. User Response: No user action required. BIP2260E Invalid node class name &1 in loadable implementation library &2. Explanation: The message broker detected the node factory attempting to register an invalid node class name. Node class names must end in Node. User Response: Contact the author or supplier of the loadable implementation library and obtain a version which satisfies the node class name requirement. BIP2261E Node class name &1 for use in library &2 already registered in library &3. Explanation: The message broker detected the node factory in loadable implementation library &2 attempting to register the node class name &1, but this name has already been registered with the broker by the node factory in the library &3. User 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. BIP2262E Request to create message flow &2 (UUID=&1): message flow aleady exists. Explanation: The message broker received a configuration message containing an instruction to create the message flow &2 (UUID=&1), but this message flow already exists. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2263W Request to delete message flow &1: message flow does not exist. Explanation: The message broker received a configuration message containing an instruction to delete the message flow &1, but this message flow does not exist. User 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. BIP2264I Message flow &2 (UUID=&1) successfully created. Explanation: The message broker received a configuration message containing an instruction to create the message flow &2 (UUID=&1), and successfully performed this action. User Response: No user action required. BIP2265I Attribute in message flow &2 (UUID=&1) successfully changed. Explanation: The message broker received a configuration message containing an instruction to change an attribute in the message flow &2 (UUID=&1) and successfully performed this action. User Response: No user action required. BIP2266W Request to change attribute in message flow node &1: message flow does not exist. Explanation: The message broker received a configuration message containing an instruction to change an attribute in the message flow node &1 but this message flow does not exist. User 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. BIP2267I Message flow &2 (UUID=&1) successfully deleted. Explanation: The message broker received a configuration message containing an instruction to delete the message flow &2 (UUID=&1), and successfully performed this action. User Response: No user action required. BIP2268W Request to report on message flow node &1: message flow does not exist. Explanation: The message broker received a configuration message containing an instruction to obtain a report of the message flow node &1, but this message flow does not exist.
Chapter 2. Messages

57

BIP2269I BIP2290E
User 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. BIP2269I Message flow &2 (UUID=&1) started successfully. Explanation: The message broker received an operational control message containing an instruction to start the message flow &2 (UUID=&1) and successfully performed this action. User Response: No user action required. BIP2270W Request to start message flow &1: message flow does not exist. Explanation: The message broker received an operational control message containing an instruction to start the message flow &1, but this message flow does not exist. User Response: Ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2271I Message flow &2 (UUID=&1) successfully stopped. Explanation: The message broker received an operational control message containing an instruction to stop the message flow &2 (UUID=&1) and successfully performed this action. User Response: No user action required. BIP2272W Request to stop message flow &1: message does not exist. Explanation: The message broker received an operational control message containing an instruction to stop the message flow &1, but this message flow does not exist. User Response: Determine whether or not the message flow should exist at the broker. If it should, ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP2273W Request to report on message flow &1: message flow does not exist. Explanation: The message broker received an operational control message containing an instruction to report the status of the message flow &1, but this message flow does not exist. User Response: No user action required. BIP2274E Invalid database state. 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. User Response: Redeploy the complete broker configuration from the Control Center. If the problem persists, contact the IBM support center. BIP2275E Database record associated with message flow &1 is not valid. Explanation: The message broker found a database record associated with the persistent state of message flow &1 to be invalid. The active broker state may not be as expected. User 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 Control Center. If the problem persists, contact your IBM support center. BIP2280E Invalid installation. Explanation: The message broker detected an error whilst loading a loadable implementation file. The resource has not been registered. User Response: See the following messages for details of the error. BIP2281E Resource name &1 for use in library &2: name already registered in library &3. Explanation: The message broker detected the resource in loadable implementation library &2 attempting to register the resource name &1, but this name has already been registered with the broker by the resource in the library &3. User 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. BIP2290E Parser class name &1 for use in library &2: name already registered in library &3. Explanation: The message broker detected the parser factory in loadable implementation library &2 attempting to register the parser class name &1, but this name has already been registered with the broker by the parser factory in the library &3. User 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.

58

MQSeries Integrator Messages

BIP2291E BIP2310E
BIP2291E No constant for parser class name for root element name &1. Explanation: The message broker could not locate a constant for a parser class name for a root element name. User 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. BIP2292E Constant for a parser class name for the root element name &1: constant is not valid. Explanation: The message broker located a constant defining a parser class name for the root element name &1 but it was invalid. User 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. BIP2293E Invalid configuration message containing attribute value &1: not valid for target attribute messageDomainProperty on object &2. 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. User 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. BIP2300E File &1 could not be loaded; operating system return code &2. Explanation: The message broker detected the loadable implementation file &1 but this could not be loaded by the operating system. The operating system return code was &2. User Response: Determine the cause of the load failure by analysing 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. BIP2301E File &1 does not contain suitable entry points. Explanation: The message broker loaded the implementation file &1 but this could not find any suitable entry points in it. User 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. BIP2302E File &1 contains insufficient resources. Explanation: The message broker loaded the implementation file &1 and found entry points in it but could not find either any node factories, parser factories, or any other kind of resource within it. User 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. BIP2303W File &1 could not be unloaded; operating system return code &2. Explanation: The message broker detected the loadable implementation library &1 but this could not be unloaded by the operating system. The operating system return code was &2. User 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. BIP2304W Exception caught whilst loading file &1; message broker may operate with reduced capability. Explanation: The message broker caught an exception whilst loading the implementation file &1. The broker will continue to operate but with reduced capabilities. See the following messages for details of the error. User Response: No user action required. BIP2305E Error initializing broker. Explanation: The message broker caught an unkown exception whilst loading the implementation file &1. The broker will restart. User Response: See your system log for other messages associated with this one. BIP2310E The broker is not capable of handling messages of type &1 on behalf of node &2. Explanation: The message broker received a message that requires the handling of data of type &1 but the broker does not have the capability to handle data of this type. This happened when processing a message on behalf of node &2. User Response: Check both the message being sent to the message broker and the configuration data for the node. References to the unsupported data type must be
Chapter 2. Messages

59

BIP2311E BIP2329E
removed if the messages are to be processed by the broker. BIP2311E Program error in library &1 whilst creating parser on behalf of node &2. 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 &2. User 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. BIP2321E Database error: ODBC return code &1. Explanation: The message broker encountered an error whilst executing a database operation. The ODBC return code was &1. See the following messages for information obtained from the database pertaining to this error. User 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. BIP2322E Database error: SQL State &1; Native Error Code &2; Error Text &3. Explanation: The error has the following diagnostic information: SQL State &1 SQL Native Error Code &2 SQL Error Text &3. User 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. BIP2323E Unsupported DBMS (&1) for a coordinated transaction. 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 MQSeries Integrator as a participant in a globally coordinated transaction. The message flow is terminated and the input message is backed out. User 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. BIP2324E Unsupported datatype &2 fetched from database table column &1. Explanation: A message flow node which performs a database fetch returned a datatype not supported by the message broker. The database table column &1 contains an unsupported datatype identified by &2. User 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. BIP2325E Invalid datatype &1 encountered. Explanation: An invalid datatype identified by &1 was encountered during the processing of a message flow. This indicates that an internal software error has occurred. User Response: Restart the broker. If the problem continues to occur, contact your IBM support center. BIP2326E Invalid fields for a time value: Hours &1; Minutes &2; Seconds &3. Explanation: An attempt was made to interpret the following fields as a valid time Hours : &1 Minutes : &2 Seconds : &3 User Response: Correct the message flow definition to ensure that the values being provided as a time value are correct. This may involve validating that data being read from either a database or a message content is suitable for use as a time. BIP2327E Invalid fields for Giegorian date value: Year &1; Month &2; Day &3. Explanation: An attempt was made to interpret the following fields as a valid date in the Gregorian calendar. Year: &1, Month: &2, Day: &3. (January is represented by a month value of 1.) User Response: Correct the message flow definition to ensure that the values being provided as a date value are correct. This may involve validating that data being read from either a database or a message content is suitable for use as a date. BIP2328E A value of SQL datatype &1 encountered when datatype &2 expected. Explanation: The value of SQL datatype &1 was encountered, but a value of SQL datatype &2 was expected. User 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. BIP2329E An unexpected NULL value was encountered.

Explanation: User 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.

60

MQSeries Integrator Messages

BIP2330E BIP2361E
BIP2330E Field &4[&5] within field &1 does not exist; diagnostic information &2, &3. Explanation: The message broker attempted to locate the field &4[&5] contained within the field &1 but the message did not contain this field. Additional diagnostic information is &2 &3. User 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 non-existent field. BIP2331E Field &2 within field &1 does not exist. Explanation: The message broker attempted to locate the field &2 contained within the field &1 but the message did not contain this field. User 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 non-existent field. BIP2332E Error attaching field &2 to field &1 which already has a parent. Explanation: The message broker attempted to attach the field &2 to the field &1 but the latter field already has a parent field. User 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. BIP2333E Error attaching field &2 as a sibling of field &1 which has no parent. Explanation: The message broker attempted to attach the field &2 as a sibling of the field &1 but the latter field does not have a parent field. User 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. BIP2340E Error attaching field &2 to field &1 which belongs to a message in a different group. Explanation: The message broker attempted to attach the field &2 to the field &1 but the latter field belongs to a message in a different group. User 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. BIP2350E Unable to convert &1 from UNICODE to the local code page. Explanation: The message broker was unable to convert the value &1 from unicode to the local code page. User 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. BIP2351E Unable to convert &1 from loal code page to UNICODE. Explanation: The message broker was unable to convert the value &1 from the local code page to unicode. User Response: This is an internal processing error. Contact your IBM support center. BIP2352E Unable to convert &1 to an integer from the local code page. Explanation: The message broker was unable to convert the value &1 from the local code page to an integer. User Response: Check the source of the data for the value to determine why the value is not suitable for conversion to an integer. BIP2353E Unable to convert &1 to a real number from the local code page. Explanation: The message broker was unable to convert the value &1 from the local code page to a real number. User Response: Check the source of the data for the value to determine why the value is not suitable for conversion to a real number. BIP2360E Syntax error in path specification missing ) after type specification. Explanation: A ) must close a type specification. A path string has been specified using an invalid syntax. The path was specified as &1. User Response: This is an internal error. Contact your IBM support center. BIP2361E Syntax error in path specification, no closing ] in index specification. Explanation: A ] must close an index specification. A path string has been specified using an invalid syntax. The path was specified as &1. User Response: This is an internal error. Contact your IBM support center.

Chapter 2. Messages

61

BIP2362E BIP2411E
BIP2362E Syntax error in path specification missing . after index specification. Explanation: A . must follow an index specification. A path string has been specified using an invalid syntax. The path was specified as &1. User Response: This is an internal error. Contact your IBM support center. BIP2370E Database connection compromised: message flow thread already connected to DSN &1 in a different coordination mode. Explanation: A message flow node attempted to connect to a database in a particular coordination mode. However, the message flow thread already had a connection to the data source name (DSN) &1 in a different coordination mode. This can occur when your message flow has been configured with the property Coordinated Transaction=yes and the attributes of one of the nodes which perform database operations has been incorrectly specified. User Response: Correct the message flow and redeploy the message broker. BIP2371E Database statement &1 could not be executed. Explanation: A message flow node attempted to execute a database statement. However, the database returned an error when executing the statement &1. User Response: If necessary, correct the message flow and redeploy the message broker. BIP2401E (&1, &2) : Syntax error : expected &3 but found &4. Explanation: The expected token was not found. User Response: Correct the syntax of your expression and redeploy the message flow. BIP2402E (&1, &2) : Syntax error : &3. Explanation: The token caused a syntax error. User Response: Correct the syntax of your expression and redeploy the message flow. BIP2403E (&1, &2) : An interval qualifier is not allowed here. Explanation: An interval qualifier was specified after a pair of parentheses which did not contain a subtraction expression. User Response: Correct the syntax of your expression and redeploy the message flow. BIP2404E (&1, &2) : Could not resolve the symbolic constant &3. Explanation: The constant &3 did not match any defined symbolic constant. User Response: Correct &3 and redeploy the message flow. BIP2405E (&1, &2) : Syntax error : &3 is a keyword , an identifier was expected. Explanation: The token caused a syntax error. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2406E (&1, &2) : Syntax error : cannot specify [] in the middle of a field reference. Explanation: The list specifier ([]) can only be used at the end of a field reference. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2407E (&1, &2) : Precision must be > 0 and <= &1. Explanation: A precision value was given in the definition of a DECIMAL datatype which was outside of the valid range. User Response: Correct the definition of the DECIMAL datatype so that a valid precision is specified and redeploy the message flow. BIP2408E (&1, &2) : Scale must be >= 0 and <= &1. Explanation: A scale value was given in the definition of a DECIMAL datatype which was outside of the valid range. User Response: Correct the definition of the DECIMAL datatype so that a valid scale is specified and redeploy the message flow. BIP2409E (&1, &2) : An interval qualifier was expected. 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. User Response: Correct the syntax of the expression and reploy the message flow. BIP2410E (&1, &2) : A field reference was expected. Explanation: A field reference was expected here but there does not appear to be one. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2411E (&1, &2) : Expected one of YEAR, MONTH, DAY, HOUR, MINUTE or SECOND. Explanation: The token found did not match any of the expected values. User Response: Correct the syntax of the expression and redeploy the message flow.

62

MQSeries Integrator Messages

BIP2412E BIP2426E
BIP2412E (&1, &2) : Expected one of ANY, ALL or SOME. Explanation: The token found did not match any of the expected values. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2413E (&1, &2) : Inconsistent number of values in VALUES clause. Explanation: The number of values specified in the VALUES clause does not match the number of columns specified. User Response: Correct the number of values specified in the VALUES clause and redeploy the message flow. BIP2414E Unsupported datatype &1. Explanation: While preparing an ODBC statement a parameter with datatype &1 was encountered. This datatype is not yet supported for ODBC operations. User Response: Ensure that expressions which may return values of datatype &1 are not used as parameters in statements or expressions that access external databases. BIP2415E (&1, &2) : Datatypes of TRIM source string (&3) and trim character (&4) do not match. Explanation: The datatype of the source string passed to the TRIM function does not match that of the trim character. User Response: Ensure that the datatypes of the source string and the trim character are the same and redeploy the message flow. BIP2416E (&1, &2) : Datatypes of OVERLAY target string (&3) and source string (&4) do not match. Explanation: The datatype of the target string passed to the OVERLAY function does not match the datatype of the source string. User Response: Ensure the the datatypes of the target string and the source string are the same and redeploy the message flow. BIP2417E (&1, &2) : Invalid field reference correlation name &3 for BITSTREAM function. Explanation: The correlation name for a field reference passed as a parameter to the BITSTREAM function is not valid. Only field references beginning with InputRoot, InputBody, Root or Body are valid as parameters to this function. User Response: Ensure that the field reference passed to the BITSTREAM function starts with one of the permitted correlation names and redeploy the message flow. BIP2420E (&1, &2) : Invalid or incompatible datatypes for &3 operator. Explanation: Either the datatypes of the operands of the operator were not valid for the operator, or the datatypes where incompatible. User Response: Ensure that the datatypes of the operands are valid and compatible with each other and redeploy the message flow. BIP2421E (&1, &2) : Left hand operand to &3 operator must be a scalar. Explanation: The left hand operand to the operator was not a scalar valued expression. User Response: Ensure that the left hand operator to the &3 operator is a scalar and reploy the message flow. BIP2422E (&1, &2) : Right hand operand to the &3 operator must be a scalar. Explanation: The right hand operand to the operator was not a scalar valued expression. User Response: Ensure that the right hand operand to the &3 operator is a scalar and redeploy the message flow. BIP2423E (&1, &2) : Interval qualifier only valid with datetime subtraction. Explanation: If an interval qualifier is specified after a subtraction expression, the operands of the expression must be datetime values. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2424E (&1, &2) : Interval qualifier must be specified with a datetime subtraction. Explanation: When subtracting two datetime values, an interval qualifier must be given. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2425E Interval qualifier not valid for subtraction between values &1 and &2. 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 &1 and &2. User Response: Ensure that the operands of the expression are datetime values. BIP2426E Interval qualifier required for subtraction between values &1 and &2. Explanation: When two datetime values are subtracted, an interval qualifier must be given. The subtraction was being performed between values &1 and &2.
Chapter 2. Messages

63

BIP2427E BIP2439E
User Response: Ensure that a valid interval qualifier is specified. BIP2427E (&1, &2) : The left operand of &3 operator is not a boolean expression. Explanation: The left operand of this operator must be a boolean expression. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2428E (&1, &2) : The right hand operand to operator &3 is not a boolean expression. Explanation: The right hand operand to this operator must be a boolean expression. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2429E The left hand operand to the &1 operator must evaluate to a boolean value. Explanation: The left hand operand to this operator is &2, which does not evaluate to a boolean value. User Response: Ensure that the left hand operand evaluates to a boolean value. BIP2430E Illegal operands &1 and &2 for concatenation operator. Explanation: The operands for the concatenation operator were &1 and &2. The concatenation operator can only be applied between two character string values, two bit string values, or two byte string values. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2431E The right hand operand to the &1 operator must evaluate to a boolean value. Explanation: The right hand operand to this operator is &2, which does not evaluate to a boolean value. User Response: Ensure that the right hand operand evaluates to a boolean value. BIP2432E (&1, &2) : The correlation name &3 is not valid. Those in scope are: &4. 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. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2433E (&1, &2) : The array index is not an intergral expression. Explanation: An array index must be an expression which evaluates to an integer value. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2434E (&1, &2) : Array index evaluated to &3. Explanation: Array index expressions must evaluate to a non-null integral value. User Response: Ensure that the array index evaluates to a non-null integral value. BIP2435E (&1, &2) : Array index evaluated to &3. Explanation: The array index expression must evaluate to a positive, non-zero integer value. User Response: Ensure that the array index expression evaluates to a positive, non-zero integer value. BIP2436E (&1, &2) : Invalid indexed assignment to &3[&4]. 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. User Response: Ensure that element n-1 is created before an attempt is made to create element n. BIP2437E (&1, &2) : Invalid indexed assignment to element &4[&5]: only &3 elements. 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, where n is a positive integer, the element with index n-1 must already exist. User Response: Ensure that element n-1 exists before attempting to create element n. BIP2438E (&1, &2) : Path element error. Explanation: The path element identifies a parser and must have a name and no type. User Response: Ensure that the field reference is specified correctly. BIP2439E (&1, &2) : Error evaluating expression &3. Explanation: An error occurred while evaluating an expression. Subsequent messages will contain more information about the nature of the error. User Response: Ensure that the expression is correctly formed.

64

MQSeries Integrator Messages

BIP2440E BIP2454E
BIP2440E (&1, &2) : Invalid first operand for BETWEEN predicate. Explanation: The first operand of a BETWEEN predicate must be a scalar. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2441E (&1, &2) : Invalid second operand for BETWEEN predicate. Explanation: The second operand of a BETWEEN predicate must be a scalar. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2442E (&1, &2) : Invalid third operand for BETWEEN predicate. Explanation: The third operand of a BETWEEN predicate must be a scalar. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2443E (&1, &2) : Incompatible first and second operands for BETWEEN predicate. Explanation: The first and second operands of a BETWEEN predicate must be compatible datatypes. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2444E (&1, &2) : Incompatible first and third operands for BETWEEN predicate. Explanation: The datatypes of the first and third operands of a BETWEEN predicate must be compatible datatypes. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2445E (&1, &2) : Illegal operand for unary minus. Explanation: The unary minus operator can only be applied to numeric or interval operands. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2446E (&1, &2) : Illegal operand for unary minus applied to value &3. 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. User Response: Ensure that the unary minus is only applied to numeric or interval operands. BIP2447E (&1, &2) : Illegal operand for NOT operator. Explanation: The operand for the NOT operator must be a boolean valued expression. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2448E (&1, &2) : Illegal operand for NOT operator applied to value &3. 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. User Response: Ensure that the NOT operator is only applied to boolean expressions. BIP2449E Arithmetic overflow evaluating expression &1. Explanation: The result of this expression was outside the valid range for the datatype. User Response: Either supply smaller values as operands or use a datatype capable of holding larger values. BIP2450E Divide by zero evaluating expression &1. Explanation: A divide by zero error occurred. User Response: Ensure that the second operand of the division operator cannot be zero. BIP2451E Incompatible types &1 and &2 for operator &3. Explanation: An attempt was made to combine the values &1 and &2 using the operator &3. User Response: Ensure that the datatypes passed to this operator are compatible. BIP2452E Overflow casting integer to interval; value &1 exceeds the maximum of &2. Explanation: The integer had the value &1, which was greater than the maximum allowed of &2. User Response: Ensure that the size of the integer value does not exceed the maximum. BIP2453W Overflow casting double to integer; value &1 outside of range [&2, &3]. Explanation: The double had the value &1, which was outside of the range [&2, &3]. User Response: Ensure that the double value does not exceed the maximum. BIP2454E Overflow casting decimal to interval; value &1 exceeds the maximum of &2. Explanation: The decimal had the value &1, which was greater than the maximum allowed of &2. User Response: Ensure that the decimal value does not exceed the maximum.

Chapter 2. Messages

65

BIP2455E BIP2466W
BIP2455E Error casting character string &1 to boolean. Explanation: The character string had the value &1. Only the character strings TRUE, FALSE, and UNKNOWN can be cast to booleans. User Response: Ensure that the character string being cast has one of the above values. BIP2456E Overflow casting a character string &1 to a double. Explanation: The character string represented a number which was too large or too small to be represented using a 64-bit number. The character string had the value &1. User Response: Ensure that the character string represents a number within the range of a 64-bit double. BIP2457E Error casting character string &1 to double. Explanation: The character string must be of the form [+/-]d+[.d+][Ed+]. The character string had the value &1. User Response: Ensure that the character string being cast represents a valid number. BIP2458E Error casting character string &1 to a time. Explanation: The character string had the value &1. A character string must have the form TIME hh:mm:ss[.f+], or hh:mm:ss[.f+] for it to be cast to a time value. User Response: Ensure that the string represents a valid time value. BIP2459E Error casting character string &1 to a GMT time. Explanation: The character string had the value &1. 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. User Response: Ensure that the character string being cast has a valid format. BIP2460E Error casting character string &1 to a date. Explanation: The character string had the value &1. A character string must have the form DATE yyyy-mm-dd, or yyyy-mm-dd for it to be castable to a date. User Response: Ensure that the string being cast has a valid value. BIP2461E Error casting character string &1 to a timestamp. Explanation: The character string had the value &1. A character string must have 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. User Response: Ensure that the string being cast is formatted correctly. BIP2462E Error casting character string &1 to a GMT timestamp. Explanation: The character string had the value &1. 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. User Response: Ensure that the string being cast is formatted correctly. BIP2463E Error casting character string &1 to an interval. Explanation: The character string had the value &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. User Response: Ensure the the string being cast is formatted correctly. Consult the manual, ESQL Reference for more information concerning field values and qualifiers. BIP2464E Error casting interval &1 to a numeric type. Explanation: An interval must have a qualifier which specifies only one field in order to be castable to a numeric type. User Response: Ensure that the interval is of the appropriate type. BIP2465E Cannot cast &1 to the type &2. Explanation: There is no way to convert &1 into the data type &2. User Response: Ensure that the source and target data types and values in the casting operation are compatible. BIP2466W (&1, &2) : Left hand operand of IN predicate must be a scalar. Explanation: The values on the left of an IN predicate must be compatable with the datatype of the expression on the left. User Response: Correct the syntax of the expression and redeploy the message flow.

66

MQSeries Integrator Messages

BIP2467E BIP2481E
BIP2467E (&1, &2) : Incompatible operands for IN predicate. Explanation: The values on the right of an IN predicate must be compatible with the datatype of the expression on the left. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2468E (&1, &2) : Invalid data type for left-hand operand of LIKE. Explanation: The left-hand operand of LIKE predicate must be a character string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2469E (&1, &2) : Invalid data type for right-hand operand of LIKE. Explanation: The right-hand operand of LIKE predicate must be a character string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2470E (&1, &2) : Invalid value &3 for left-hand operand of LIKE predicate. Explanation: The left-hand operand of a LIKE predicate must be a character string. User Response: Ensure that the left hand operand of the LIKE predicate is a character string. BIP2471E (&1, &2) : Invalid value &3 for right-hand operand of LIKE predicate. Explanation: The right-hand operand of a LIKE predicate must be a character string. User Response: Ensure that the right-hand operand of the LIKE predicate is a character string. BIP2472E (&1, &2) : Invalid LIST member. Explanation: A LIST cannot contain another LIST as one of its members. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2473E (&1, &2) : Invalid search condition. Explanation: A search condition must produce a boolean result. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2474E (&1, &2) : &3 is not boolean. Explanation: A search condition evaluated to &3, which is not a boolean value. Search conditions must evaluate to boolean values. User Response: Ensure that the search condition evaluates to a boolean. BIP2475E (&1, &2) : Illegal argument type for EXTRACT function. Explanation: The argument to the EXTRACT function must be a datetime or interval valued expression. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2476E (&1, &2) : Illegal argument type for EXTRACT function called with value &3. Explanation: The argument to the EXTRACT function must be a datetime or interval valued expression. The EXTRACT function was called with the value &3. User Response: Ensure that the argument supplied to the EXTRACT function is a datetime or an interval. BIP2477E (&1, &2) : Cannot extract &3 field from value &4. Explanation: It was not possible to extract the specified field from the value supplied. User Response: Ensure that the value supplied contains the necessary information and is correctly formed. BIP2478E (&1, &2) : Path argument to &3 must not specify a list. Explanation: The path argument supplied to the &3 function must point to a single field only. User Response: Ensure that the path argument points to a single field. BIP2479E (&1, &2) : Illegal argument value &3 to ABS function. Explanation: The ABS function was called with the value &3. User Response: Ensure that the value passed to the ABS function is valid. BIP2480E (&1, &2) : Illegal argument to ABS function. Explanation: The argument passed to the ABS function was invalid. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2481E (&1, &2) : Illegal argument value &4 to &3 function. Explanation: The argument to &3 must be a numeric type. &4 is not a numeric type. User Response: Ensure that only numeric types are passed as an argument to &3.

Chapter 2. Messages

67

BIP2482E BIP2495E
BIP2482E (&1, &2) : Illegal argument to &3 function. Explanation: The argument passed to &3 must be a numeric type. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2483E (&1, &2) : Illegal arguments (values &3 and &4) to MOD function; integers required. Explanation: Both arguments to the MOD function must be integral values. The function was called with the arguments &3 and &4. User Response: Ensure that only integral values are passed to the MOD function. BIP2484E (&1, &2) : Illegal argument to MOD function. Explanation: Both arguments to the MOD function must be integral values. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2485E (&1, &2) : Illegal first argument (value &4) to function &3; numeric value required; value of second argument was &5. Explanation: First argument to the function &3 must be a numeric value. The function was called with the values &4, &5. User Response: Ensure that the first argument to &3 is a numeric type. BIP2486E (&1, &2) : Illegal second argument to function &3; values supplied were &4 and &5. Explanation: Second argument to the function &3 must be an integral value. The function was called with the values &4, &5. User Response: Ensure that the second argument to &3 is an integral type. BIP2487E (&1, &2) : Illegal first argument to &3 function. Explanation: First argument to the function &3 must be a numeric value. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2488E (&1, &2) : Illegal second argument to &3 function. Explanation: Second argument to the function &3 must be an integral value. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2489E (&1, &2) : Illegal first argument (value &3) to SQRT function; numeric value required. Explanation: First argument must be a numeric value. The function was called with the value &3. User Response: Ensure that the first argument to SQRT is a numeric value. BIP2490E (&1, &2) : Illegal argument to SQRT function. Explanation: First argument must be a numeric value. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2491E (&1, &2) : Illegal argument (value &4) to function &3; character string required. Explanation: The argument must be a character string value. The function was called with the value &4. User Response: Ensure the the argument passed to &3 is a character string. BIP2492E (&1, &2) : Illegal argument to &3 function. Explanation: The argument must be a character string value. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2493E (&1, &2) : Illegal first argument (value &3) to function SUBSTRING. Explanation: The first argument must be a character, byte or bit string. The function was called with a first argument of &3. User Response: Ensure that the first argument to SUBSTRING is a character, byte or bit string. BIP2494E (&1, &2) : Illegal first argument to SUBSTRING function. Explanation: The first argument must be a character string, byte string or bit string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2495E (&1, &2) : Illegal index (value &4) into string &3 for function SUBSTRING. Explanation: The second argument must be an integer giving a valid start position in the string. The function was called with arguments &3, &4. User Response: Ensure that the second argument is an integer with a valid value relative to the length of the source string.

68

MQSeries Integrator Messages

BIP2496E BIP2510E
BIP2496E (&1, &2) : Illegal second argument to SUBSTRING function. Explanation: The second argument must be an integer giving a valid start position in the string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2497E (&1, &2) : Illegal third argument to function SUBSTRING; values supplied were &3, &4, &5. Explanation: The third argument must be an integer giving a valid length for the substring. The function was called with arguments &3, &4, &5. User Response: Ensure that the third argument to SUBSTRING is an integer with a valid value relative to the length of the source string. BIP2498E (&1, &2) : Illegal third argument to SUBSTRING function. Explanation: The third argument must be an integer giving a valid length for the substring. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2499E (&1, &2) : Illegal arguments to SUBSTRING function called as &3. Explanation: Valid syntax for SUBSTRING is: SUBSTRING( source_string FROM start_position [FOR string_length]). The function was called as &3. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2501E (&1, &2) : Illegal argument (value &3) to function LENGTH. Explanation: The argument to the LENGTH function must be a character string, byte string or bit string. The function was called with the argument &3. User Response: Ensure that the argument passed to LENGTH is an appropriate data type. BIP2502E (&1, &2) : Illegal argument to LENGTH function. Explanation: The argument to the LENGTH function must be a character string, byte string or bit string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2503E (&1, &2) : Illegal arguments (values &3, &4) to function POSITION. Explanation: The arguments for the POSITION function must both be character strings, byte strings or bit strings. The function was called with the arguments &3, &4. User Response: Ensure that the arguments passed to POSITION are of an appropriate and consistent data type. BIP2504E (&1, &2) : Illegal arguments (values &3, &4) to function POSITION. Explanation: The arguments for the POSITION function must both be character strings, byte strings or bit strings. The function was called with the arguments &3, &4. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2505E (&1, &2) : Illegal first argument (value &3) to function OVERLAY. Explanation: The first argument must be a character string, byte string or bit string. The first argument passed to the function was &3. User Response: Ensure the the first argument passed to OVERLAY is an appropriate data type. BIP2506E (&1, &2) : Illegal first argument to OVERLAY function. Explanation: The first argument must be a character string, byte string or bit string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2507E (&1, &2) : Illegal second argument value &4 to function OVERLAY; first argument value is &1. Explanation: The second argument must be a character string, byte string or bit string. User Response: Ensure the the second argument passed to OVERLAY is an appropriate data type. BIP2508E (&1, &2) : Illegal second argument to OVERLAY function. Explanation: The second argument must be a character string, byte string or bit string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2509E (&1, &2) : Illegal third argument value &5 to OVERLAY function; first argument value is &3; second argument value is &4. Explanation: The third argument must be an integer giving a valid start position within the string. User Response: Ensure that the third argument is an integer type. BIP2510E (&1, &2) : Illegal third argument to OVERLAY function. Explanation: The third argument must be an integer giving a valid start position within the string. User Response: Correct the syntax of the expression and redeploy the message flow.

Chapter 2. Messages

69

BIP2511E BIP2524E
BIP2511E (&1, &2) : Illegal fourth argument value &6 to OVERLAY function; first argument value is &3; second argument value is &4; third argument value is &5. Explanation: The fourth argument must be an integer giving the number of characters to copy. User Response: Ensure that the fourth argument to OVERLAY is an integer with a value appropriate to the length of the target string. BIP2512E (&1, &2) : Illegal fourth argument to OVERLAY function. Explanation: The fourth argument must be an integer giving the number of characters to copy. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2513E (&1, &2) : Illegal source string &3 argument to TRIM function. Explanation: The source string argument to the TRIM function must be a character string, a byte string or a bit string. The argument passed was &3. User Response: Ensure that the source string argument to TRIM is an appropriate datatype. BIP2514E (&1, &2) : Illegal source string argument to TRIM function. Explanation: The source string argument to the TRIM function must be a character string, a byte string or a bit string. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2515E (&1, &2) : Illegal trim character &3 argument to TRIM function. 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 &3. User Response: Ensure that the trim character argument is an appropriate datatype and length. BIP2516E (&1, &2) : Illegal trim character argument to TRIM function. 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. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2517E (&1, &2) : Variable &3 has already been declared in the current scope. Explanation: An attempt was made to declare the variable &3, but this variable has already been declared within the current scope. You cannot declare the same variable more than once within the same scope. User Response: Remove the second declaration, or substitute a different variable name, and redeploy the message flow. BIP2518E Invalid value &1 for &2 field of INTERVAL. Explanation: &1 is not a valid value for the &2 field of an INTERVAL value. User Response: Ensure that only valid values for each of the INTERVAL fields are used to construct INTERVAL values. BIP2519E (&1, &2) : Error executing SQL statement &4 against datasource &3 with parameters &5. Explanation: The following error occurred during execution of a database SQL statement against datasource &3. The SQL statement was &4. The parameters passed were &5. User Response: BIP2520E (&1, &2) : Error retrieving results of SQL statement &4 against datasource &3. Explanation: The following error occurred retrieving the results from a database SQL query against datasource &3. The SQL statement was &4. User Response: BIP2521E (&1, &2) : Error casting a value from &3 to &4. Explanation: An error occurred when casting a value of data type &3 to a value of data type &4. User Response: Subsequent messages will indicate the context of the error. BIP2522E (&1, &2) : Type mismatch in CASE expression. Explanation: The WHEN clause of a simple CASE expression must be compatible with the CASE clause. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2523E (&1, &2) : Cannot assign to a symbolic constant or input message. Explanation: Values cannot be assigned to symbolic constants or input message fields. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2524E (&1, &2) : Cannot assign a list to a non-list, or a non-list to a list. Explanation: A list of values cannot be assigned to a scalar variable or single message field, or a scalar value cannot be assigned to a list.

70

MQSeries Integrator Messages

BIP2525E BIP2539I
User Response: Correct the syntax of the expression and redeploy the message flow. BIP2525E Error casting character string &1 to an interval with qualifier &2. Explanation: The character string had the value &1 which was not a valid representation of an interval with qualifier &2. 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. User Response: Ensure the the string being cast is formatted correctly. Consult the manual, ESQL Reference for more information concerning field values and qualifiers. BIP2526E (&1, &2) : The datasource &3 does not support the function &4. Explanation: The datasource &3 does not support the function &4. User Response: Rewrite your expression to avoid the use of this function, or connect to an alternative datasource. BIP2527E (&1, &2) : The datasource &3 does not support the datatype &4. Explanation: The datasource &3 does not support the datatype &4. User Response: Rewrite your expression to avoid the use of this datatype, or connect to a different datasource. BIP2528E (&1, &2) : Datatype &3 not supported for database interaction. Explanation: The datatype &3 cannot be passed to a database. User Response: Do not attempt to pass values with this datatype to the database. BIP2529E (&1, &2) : The datasource &3 does not support CASE expressions. Explanation: CASE expressions are not supported by this data source. User Response: Rewrite the expression to avoid use of CASE, or connect to a different data source. BIP2530E (&1, &2) : The datasource &3 does not support the BETWEEN predicate. Explanation: BETWEEN is not supported by this data source. User Response: Rewrite the expression to avoid use of BETWEEN, or connect to a different data source. BIP2531E (&1, &2) : The datasource &3 does not support the IN predicate. Explanation: IN is not supported by this data source. User Response: Rewrite the expression to avoid use of IN, or connect to a different data source. BIP2532E (&1, &2) : The datasource &3 does not support the LIKE predicate.

Explanation: User Response: BIP2533E (&1, &2) : Cannot generate database SQL for the quantified predicate.

Explanation: User Response: BIP2534E (&1, &2) : Cannot generate suitable database SQL for the BETWEEN predicate.

Explanation: User Response: BIP2535E (&1, &2) : Field reference does not represent a database column. Explanation: A field reference which represents a database column must consist of at least two elements, the first of which must be Database. User Response: Correct the syntax of the field reference. BIP2536E (&1, &2) : Cannot generate database SQL to represent a LIST constructor.

Explanation: User Response: BIP2537I Node &4: Executing statement &3 at (&1, &2). Explanation: The statement being executed was &3. User Response: No user action required. BIP2538I Node &4: Evaluating expression &3 at (&1, &2). Explanation: The expression being evaluated was &3. User Response: No user action required. BIP2539I Node &6: Finished evaluating expression &5 at (&1, &2); resolved to &3; result was &4. Explanation: The expression &5 evaluated to &3 which evaluated to &4. User Response: No user action required.

Chapter 2. Messages

71

BIP2540I BIP2554E
BIP2540I Node &5: Finished evaluating &4 at (&1, &2); result was &3. Explanation: The result of evaluating the expression &4 was &3. User Response: No user action required. BIP2541I Node &6: (&1, &2) : Comparing &3 and &4; result is &5. Explanation: The result of comparing &3 and &4 is &5. User Response: No user action required. BIP2542I Node &3: (&1, &2) : Navigating path element. subsequent references to that table. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2549E (&1, &2) : Type mismatch assigning to variable; value &3 inconsistent with type &4. Explanation: The source expression produced a value of &3 but the target variable was declared with a type of &4. User Response: Ensure that only values of the appropriate data type are assigned to declared variables. BIP2550E The first parameter of a PASSTHRU or EVAL function cannot evaluate to a list. Explanation: The first parameter of a PASSTHRU or EVAL function must evaluate to something that can be represented as a character string. User 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. BIP2551E (&1, &2) : The number &3 was too large for an INTEGER or DECIMAL literal. Explanation: The number was &3. User Response: Ensure the number is within the scale and precision limits for the specified data type and redeploy the message flow. BIP2552E (&1, &2) : The number being converted &3 was too large/small to be represented as a 64-bit floating point number. Explanation: The number being converted was &3. User Response: 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. BIP2553E (&1, &2) : Unexpected character &3 in input. Explanation: The character was &3. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2554E (&1, &2) : Unrecognised character &3 in input. Explanation: The character was &3. User Response: Correct the syntax of the expression and redeploy the message flow.

Explanation: User Response: No user action required. BIP2543E Node &3: (&1, &2) : Failed to navigate to path element. Explanation: The specified path element did not exist. User Response: No user action required. BIP2544I Node &6: Execution database SQL statement &3 derived from (&1, &2); expressions &4; resulting parameter values &5. Explanation: The database SQL that is being executed is &3. The following is a list of the expressions used to derive the parameter values (if any): &4. The above expressions resulted in the following paramater values being passed to the database: &5. User Response: No user action required. BIP2545E (&1, &2) : Cannot join a database table with a list.

Explanation: User Response: BIP2546E (&1, &2) : Cannot generate database SQL for CONCAT function. Explanation: Database SQL cannot be generated for a CONCAT function, only one of whose arguments is a parameter marker. User Response: BIP2547E (&1, &2) : No database SQL can be generated for the The OVERLAY function.

Explanation: User Response: BIP2548E (&1, &2) : A correlation name must be given. 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

72

MQSeries Integrator Messages

BIP2555E BIP2569W
BIP2555E Error casting a character string &1 to an interval (qualifier &2). Explanation: The interval qualifier given on the cast specification did not match the interval qualifier in the source character string. The character string had the value &1. The interval qualifier given in the cast specification was &2. User Response: See the documentation for details of which combinations of character strings and qualifiers are acceptable. BIP2556E An attempt has been made to assign a scalar quantity to a list. Explanation: This is most likely to have been caused by attempting to assign the list result of an EVAL function to a scalar. The type of result of an EVAL function can only be known at runtime. User Response: Check the usage of the EVAL function. Ensure that it is not an expression that will evaluate to a list of values. BIP2557E (&1, &2) : Path argument to function &3 must specify a list. Explanation: The path argument passed to the &3 function must evaluate to a list. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2558E (&1, &2) : Illegal argument to &3 function. Explanation: The arguments to the bit manipulation functions (BITAND, BITOR, BITNOT, BITXOR) must be integers. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2559E (&1, &2) : Illegal argument(s) &4 to &3 function. Explanation: The arguments to the bit manipulation functions (BITAND, BITOR, BITNOT, BITXOR) must be integers. The function was called with arguments &4. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2560E (&1, &2) : Illegal number of arguments to BITNOT function. Explanation: The BITNOT function takes one integer argument. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2561E (&1, &2) : Illegal number of arguments to bit manipulation function. Explanation: The BITAND, BITOR and BITXOR functions take two or more arguments. User Response: Correct the syntax of the expression and redeploy the message flow. BIP2562I Node &2: Assigning a list to &1. Explanation: A list of values of being assigned to &1. User Response: No user action required. BIP2563I Node &3: Deleting all &1 instances of &2, since source list for assignment was empty. Explanation: The source list contained no items, therefore all currently existing items in the target list are being deleted. User Response: No user action required. BIP2564I Node &4: Deleting instance &1 of &2, since source list for assignment had &3 instances. Explanation: The source list had one fewer item than the target list, therefore the last item in the target is being deleted. User Response: No user action required. BIP2565I Node &5: Deleting instances &1 through &2 of &3, since source list for assignment had &4 instances. Explanation: The source list had fewer items than the target list, therefore all extra items in the target are being deleted. User Response: No user action required. BIP2566I Node &3: Assigning value &1 to &2. Explanation: The value &1 is being assigned to the path &2. User Response: No user action required. BIP2567I Node &2: Assigning NULL to &1, thus deleting it. Explanation: Assigning NULL to a path causes the item identified by the path reference to be deleted. User Response: No user action required. BIP2568I Node &3: Performing tree copy of &1 to &2. Explanation: The parsed message tree identified by path &1 is being copied to &2. User Response: No user action required. BIP2569W Node &3: (&1, &2) : WHERE clause evaluated to false or unknown. Iterating FROM clause. Explanation: An item in the FROM list of a SELECT clause failed to satisfy the WHERE clause. User Response: No user action required.

Chapter 2. Messages

73

BIP2570W BIP2583E
BIP2570W Node &3: (&1, &2) : Failed to find any items in the FROM clause satisfying the WHERE clause. Explanation: None of the items specified in the FROM clause satisfied the conditions specified in the WHERE clause. User Response: No user action required. BIP2571W Node &3: (&1, &2) : Failed to find any more items in the FROM clause satisfying the WHERE clause. Explanation: There were no more items in the FROM clause that satisfied the conditions specified in the WHERE clause. User Response: No user action required. BIP2572W Node: &3: (&1, &2) : Finding one and only SELECT result. the condition does not occur. BIP2578E (&1, &2) : The datasource &3 does not support the function &4. Explanation: Only a restricted set of well known functions are supported in SQL targeted at an external database, and only then if the datasource reports that the function is supported. Function &4 was not supported by datasource &3. User Response: Rewrite the SQL expression so that the condition does not occur. BIP2579E (&1, &2) : The function &3 was not known. Explanation: &3 was not known as a function. User Response: Rewrite the SQL expression so that the condition does not occur. BIP2580E (&1, &2) : No external data source specified for this node. 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. User Response: Add database inputs for each table that is accessed, and redeploy the message flow. BIP2581E (&1, &2) : References to fields in a message cannot be included in the SELECT clause of a SELECT on an external database. Explanation: The SELECT clause of a select on an external database can only consist of references to columns defined in the table, or of simple expressions based on those columns. It cannot include references to fields in a message. User Response: Rewrite the SQL expression so that the condition does not occur. BIP2582E Interval &1 cannot be converted with qualifier &2. Explanation: The interval &1 cannot be converted to one with qualifier &2 because the qualifier is incompatible. User Response: No user action required. BIP2583E Interval values &1 and &2 incompatible for arithmetic or comparison. Explanation: The interval values &1 and &2 cannot be combined with the plus or minus operators, or compared with comparison operators. Year-month intervals are incompatible with day-second intervals. User Response: No user action required.

Explanation: User Response: No user action required. BIP2573W Node &3: (&1, &2) : Finding first SELECT result.

Explanation: User Response: No user action required. BIP2574W Node &3: (&1, &2) : Finding next SELECT result.

Explanation: User Response: No user action required. BIP2575E A Filter expression must evaluate to the &1 data type. Explanation: The expression given in the Filter Expression property of a Filter node must evaluate to a &1 type value. User Response: Correct the expression so that it returns a value of the correct type and redeploy the message flow. BIP2576E The expression in a Filter node resulted in the value &1; boolean value expected. Explanation: The Filter Expression configuring a Filter node must evaluate to a boolean value. The Filter Expression resulted in the value &1. User Response: Correct the expression so that it always returns a value of the correct type. BIP2577E (&1, &2) : Cannot generate database SQL for this function call. Explanation: A function call was included in an SQL expression targeted at an external database which had references to database columns and references to fields in the message as arguments. This is a restriction on SQL expressions targeted at external databases. User Response: Rewrite the SQL expression so that

74

MQSeries Integrator Messages

BIP2584E BIP2596E
BIP2584E Cannot add interval &2 to time value &1. Explanation: The interval value is not suitable because it contains one of the fields YEAR, MONTH or DAY. User Response: No user action required. BIP2585E Invalid interval qualifier for time subtraction, subtracting &2 from &1 with qualifier &3. 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. An attempt was made to subtract &2 from &1, giving qualifier &3. User Response: No user action required. BIP2586E Cannot add interval &2 to date value &1. Explanation: The interval value is not suitable because it contains one of the fields HOUR, MINUTE, SECOND. User Response: No user action required. BIP2587E Invalid interval qualifier for date subtraction, subtracting &2 from &1 with qualifier &3. Explanation: when giving an interval qualifier for the precision of a date subtraction, the qualifier must not contain any of the fields HOUR, MINUTE, SECOND. An attempt was made to subtract &2 from &1, giving qualifier &3. User Response: No user action required. BIP2588I Node &4: (&1, &2) : About to dynamically evaluate a string &3 as an SQL statement or expression. Explanation: The EVAL function or statement has evaluated its argument, and is about to interpret the resulting character string as if it were part of the original SQL text. The text to be interpreted is &3. User Response: No user action is required. BIP2589E Incompatible types for comparison between values &1 and &2. Explanation: The values &1 and &2 cannot be compared, because they are of incompatible types. User Response: Other messages will give an indication of context of this error. BIP2590E Error casting character string &1 to a byte string. Explanation: An attempt was made to cast the character string &1 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). User Response: Other messages will give an indication of context of this error. BIP2591E Error casting character string &1 to a bit string. Explanation: An attempt was made to cast the character string &1 to a bit string, but the string was of the wrong format. The string must consist only of the characters 0 and 1. User Response: Other messages will give an indication of context of this error. BIP2592E Error casting character string &1 to decimal; maximum decimal precision is &2 digits. Explanation: An attempt was made to cast the character string &1 to a decimal, but the string was of the wrong format. The string must be of the form [sign]digits[.digits], where sign can be one of + or - and digits are one or more decimal digits. The string must not be empty and must not contain more than &2 digits. User Response: Other messages will give an indication of context of this error. BIP2593E Error converting integer &1 to real or decimal with precision &2 and scale &3. Explanation: An attempt was made to convert the number &1 to a decimal with precision &2 and scale &3. It does not fall in the valid range of numbers for the given scale and precision. User Response: Other messages will give an indication of context of this error. BIP2594E Error converting decimal &1 to a &1 bit integer. Explanation: An attempt was made to convert the number &1 to an integer with &1 bits of precision. However the number was outside the range of valid values for such an integer. User Response: Other messages will give an indication of context of this error. BIP2595E Error casting character string &1 to an integer. Explanation: An attempt was made to cast the character string &1 to an integer, but the string was of the wrong format. User Response: Other messages will give an indication of context of this error. BIP2596E (&1, &2) : Cannot take bitstream of partially complete output. Explanation: The BITSTREAM function can only be used with input messages. User Response: Correct the syntax of the expression and redeploy the message flow.

Chapter 2. Messages

75

BIP2597E BIP2607E
BIP2597E (&1, &2) : It is not appropriate to use a list in this situation. Explanation: The expression indicated would result in a list, but the expression is being used in a situation where a non-list is expected. User Response: Correct the SQL expression being evaluated. BIP2598E Unable to convert decimal value &1 to the specified precision &2 and scale &3. Explanation: An attempt was made to cast the decimal value &1 to a decimal with precision &2 and scale &3, but the value was too large to be cast with the specified precision. User Response: Other messages will give an indication of the context of this error. BIP2601E Unable to locate the MQSeries manager class required by node &1. Explanation: The instance of the MQSeries manager class could not be located when required by node &1. The current message flow has been terminated. This error is probably indicative of an internal software malfunction. User Response: If this occurs frequently, restart the message broker. If it continues to occur, contact your IBM support center. BIP2602E Unable to create thread context in message flow node &1. Explanation: During the execution of a message flow in node &1, a new thread was created. However, a context data area could not be created for this thread. The current message flow is terminated. User 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. BIP2603E Unable to insert thread context into list for message flow node &1. Explanation: During the execution of a message flow in node &1, 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. User 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. BIP2604E Node failed to open MQSeries queue &2 owned by queue manager &1: completion code &3; reason code &4. Explanation: A message flow node failed to open the indicated MQSeries queue, with the resulting MQSeries 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. User Response: Define the MQSeries queue to the indicated queue manager. If the incorrect queue manager and/or queue name were specified, then correct the queue name using the Control Center and redeploy the message broker. BIP2605E Unable to start transaction co-ordinated by MQSeries; MQBEGIN failed; MQCC=&2, MQRC=&3, broker node &4, queue &1. Explanation: The message flow property Coordinated Transaction was specified as yes. However, when the broker node &4 reading from queue &1 attempted to start the co-ordinated transaction, the MQBEGIN operation failed with the indicated MQSeries reason code. The message flow continues, but the transaction will not be co-ordinated, and this may cause subsequent errors or unpredictable results. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2606E Unable to get message from MQSeries queue &1: MQCC=&2; MQRC=&3; node &4. Explanation: A node &4 failed to get a message from MQSeries queue &1 using the MQGET function. The MQSeries return code and reason code returned are as displayed. The node periodically retries the MQGET until it is successful. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2607E Unable to rollback MQSeries transaction on queue &1: MQCC=&2; MQRC=&3; message flow node &4. Explanation: Message flow node &4 attempted to rollback an MQSeries unit of work using the MQBACK function, but the rollback failed. The MQSeries return code and reason code returned from MQBACK are displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries Application

76

MQSeries Integrator Messages

BIP2608E BIP2615I
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. BIP2608E Unable to inquire on MQSeries queue &1: MQCC=&2; MQRC=&3; node &4. Explanation: Node &4 issued an MQINQ function to inquire about the status of queue &1 but the inquire failed. The MQSeries completion code and reason code returned are as displayed. Recovery processing of a backed out message may not work as expected. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2609E Unable to open MQSeries queue manager &3 for inquire: MQCC=&1; MQRC=&2; node &4. Explanation: An attempt to open the named connected MQSeries queue manager &3 failed when inquiring about its object attributes, during the processing of node &4. The MQSeries completion and reason codes are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2610E Unable to close MQSeries queue manager object: MQCC=&1; MQRC=&2; node &3. Explanation: An attempt by node &3 to close the connected MQSeries queue manager failed. The MQSeries completion code and reason code returned are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2611E Unable to open MQSeries backout requeue queue: queue manager=&1; queue=&2; MQCC=&3; MQRC=&4; message flow node &5. Explanation: The message flow node &5 was unable to open or get the backout requeue queue to backout an MQSeries message, with the indicated MQSeries completion and reason codes. The message may not be backed out as intended. User Response: If there is a previous message, take any recovery action described for that error. Otherwise examine the MQSeries completion and reason codes and take appropriate action. BIP2612E Unable to open MQSeries dead letter queue: queue manager=&1; queue=&2; MQCC=&3; MQRC=&4; message flow node &5. Explanation: The message flow node &5 was unable to open or get the MQSeries dead letter queue to backout an MQSeries message, with the indicated MQSeries completion and reason codes. A previous message may provide further information. The message may not be backed out as intended. User Response: If there is a previous message, take any recovery action described for that error. Otherwise examine the MQSeries completion and reason codes and take appropriate action. BIP2613E Unable to backout a message; MQPUT to queue &1 failed: MQCC=&2; MQRC=&3; message flow node &4. Explanation: The message flow node &4 was unable to backout a message as it failed to put it to either the backout requeue queue or the MQSeries dead letter queue, defined as queue &1. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2614E Unable to commit an MQSeries transaction to backout; MQCMIT failed; queueName=&1, MQCC=&2, MQRC=&3. Explanation: The specified node was unable to commit an MQSeries 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 MQSeries error. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2615I The MQSeries input node &1 has backed out the message to the backout queue or the dead letter queue. Explanation: Message backout processing has been invoked, and the message has either been backed out by being written to the backout queue or dead letter queue, as determined by the MQSeries queue manager and queue configuration.
Chapter 2. Messages

77

BIP2616E BIP2624E
User Response: No user action required. BIP2616E Unable to commit an MQSeries transaction; MQCMIT failed; queue manager=&1, MQCC=&2, MQRC=&3. Explanation: The message broker was unable to commit an MQSeries 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 MQSeries error. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2617E Output message is empty; output node &1. Explanation: The MQSeries Integrator output node &1 has received a message to write to an MQSeries 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. User Response: Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker. BIP2618E Output message does not contain a valid MQMD; output node &1. Explanation: The MQSeries Integrator output node &1 has received a message to write to an MQSeries 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. User Response: Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker. BIP2619E Output node &1 expected a distribution list but one did not exist. Explanation: The MQSeries Integrator output node &1 was invoked and the Destination Mode property was set to list. However, a valid distribution list was not found. User Response: Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker. BIP2620E Unable to write message to queue &2 on queue manager &1. MQPUT failed: MQCC=&3; MQRC=&4; message flow node &5. Explanation: The message flow node &5 was unable to write an MQSeries message as it failed to put it to the queue &2 belonging to queue manager &1. The completion and reason code from the MQPUT operation are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2621E Conversion error occurred with value &1 for message flow node &2. Explanation: The message flow node &2 was unable to convert the specified value to a multi-byte character string. The current message flow is terminated. User Response: Check the message flow to determine the cause of the error. BIP2622I Message successfully output by output node &3 to queue &2 on queue manager &1. Explanation: The MQSeries Integrator output node &3 successfully wrote an output message to the specified queue &2 connected to queue manager &1. User Response: No user action required. BIP2623E Unable to open queue &2 on MQSeries queue manager &1: completion code &3; reason code &4. Explanation: A message flow node failed to open the indicated MQSeries message queue. The error codes relate to the MQOPEN call. User Response: Check the MQSeries completion and reason codes in the MQSeries 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 MQSeries. 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. BIP2624E Unable to connect to queue manager &1: MQCC=&2; MQRC=&3; message flow node &4. Explanation: The message flow node &4 failed to connect to the MQSeries queue manager &1. The return and reason codes returned by the MQCONN are as displayed. User Response: Check the MQSeries completion and

78

MQSeries Integrator Messages

BIP2625E BIP2633W
reason codes in the MQSeries 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, define this object to MQSeries. 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. BIP2625E Warning when writing message to queue &2 on queue manager &1. MQPUT warning: MQCC=&3; MQRC=&4; message flow node &5. Explanation: The message flow node &5 received a warning when writing an MQSeries message to queue &2 owned by queue manager &1; however, the message was successfully queued. The return and reason code from the MQPUT are as displayed. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2626E Unable to open queue. Queue manager name &1 is too long; node &2. Explanation: The node &2 failed to open an MQSeries queue as the specified queue manager name &1 was longer than the maximum size allowed by MQSeries. User Response: Correct the message flow configuration and redeploy the message broker. BIP2627E Unable to open queue &1: name is too long; node &2. Explanation: The node &2 failed to open an MQSeries queue as the specified queue name &1 was longer than the maximum size allowed by MQSeries. User Response: Correct the message flow configuration and redeploy the message broker. BIP2628E Exception condition detected on input node &1. Explanation: The input node &1 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. User Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. BIP2629I Broker termination request received. Explanation: A request was received to terminate the message broker. User Response: No user action required. BIP2630I No backout requeue or DLQ defined for a message to be backed out; input node &2 received from queue &1. Explanation: The input node &2 has received a message from queue &1 but this message has previously been backed out because of a processing error in the message flow. The MQMD backoutCount of the message exceeds (or equals) the backout threshold (property BOTHRESH) defined for the MQseries input queue. The message broker has attempted to propagate the message to the backout requeue queue (property BOQNAME of the input queue) or the dead letter queue (property DEADQ of the queue manager), 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. User Response: Examine the other messages and the message flow to determine why the message is being backed out. Defining either the backout requeue queue or the dead letter queue will cause the message to be propagated to one of those queues. BIP2631I Backed out message being propagated to failure terminal; node &1. Explanation: Node &1 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 backout threshold (property BOTHRESH) defined for the MQSeries input queue. The message broker is propagating the message to the failure terminal of the node. User 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. BIP2632I Message being propagated to the output terminal; node &1. Explanation: An input message received from MQSeries input queue in node &1 is being propagated to any nodes connected to the Output terminal. User Response: No user action required. BIP2633W Warning when starting transaction co-ordinated by MQSeries; MQBEGIN failed: MQCC=&1; MQRC=&2; node &3. Explanation: The message flow property Coordinated Transaction was specified as yes. However, when the
Chapter 2. Messages

79

BIP2634E BIP2804E
broker attempted to start the co-ordinated transaction in node &3, the MQBEGIN function returned a warning as indicated by the MQSeries reason code. The message flow continues, but the transaction may not be being co-ordinated as expected, and this may cause subsequent errors or unpredictable results. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2634E Exception condition detected: object label &1; input node &2. 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. User Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. BIP2635E Exception during destination list processing; output node &1. Explanation: While processing a destination list in the output node &1 an error (or errors) occurred. User Response: Check the preceding error messages to determine what effect this error causes, taking any action as described by those messages. BIP2636E Warning when receiving a message: MQGET returned MQCC=&1, MQRC=&2; message flow node &3. Explanation: The message flow node &3 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. User Response: Check the MQSeries completion and reason codes in the MQSeries 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. BIP2637I Message propagated to failure terminal; node &1. Explanation: Node &1 has received a message, but a warning was received from the MQGET operation. The message broker is propagating the message to the failure terminal of the node. User 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. BIP2638E MQPUT to queue &2 on queue manager &1: MQCC=&3, MQRC=&4; node &5. Explanation: The node &5 attempted to write a message to the specified queue &2 connected to queue manager &1. The MQCC was &3 and the MQRC was &4. User Response: No user action required. BIP2801E Unable to load implementation file &1, rc = &2. Explanation: The message broker detected an error whilst loading a loadable implementation file. User Response: Ensure that the file exists. BIP2802E Unable to locate entry point &1 in implementation file &2. Explanation: The message broker detected an error whilst locating an entry point in a loadable implementation file. User Response: Ensure that you have the correct version of the loadable implementation file. If you cannot resolve the problem contact your IBM support center. BIP2803I Broker &1 (UUID &2) received an internal configuration response message for execution group &3 that contained no data. Explanation: The execution group failed to provide an adequate internal configuration response message. User 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 MQSeries 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 brokers configuration from the Control Center. Contact your IBM support center if you are unable to resolve the problem. BIP2804E The broker has detected that execution group &1, process ID &2, has not shutdown. 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. User 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. However, it is possible that you may

80

MQSeries Integrator Messages

BIP2805E BIP2814E
need to stop the execution group manually. If the broker was configured as an MQSeries trusted application then refer to the MQSeries 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. BIP2805E Broker &1 could not process an internal configuration message. Explanation: The problem was caused by a failure to parse the internal configuration message. The internal configuration message is rejected. User 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. BIP2806E The broker was unable to publish to MQSeries queue &1. Explanation: A publish event could not be sent because the MQSeries message queue was not available. User 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. BIP2807E The broker received a negative response to a stopped publish event, response is &1. Explanation: A stopped publish event failed, use the response to determine the cause of the failure. User 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. BIP2808E The broker was unable to access it startup singleton classes. Explanation: An attempt was made to access a singleton class, this singleton class was not initialized correctly. User Response: The broker will not start. Obtain Service trace for the failing component and contact your IBM support center. BIP2809E The broker was unable to receive a started publish event response. Explanation: A response from a started publish event could not be received. User Response: The broker continues to start-up but the current published state of the broker will be incorrect. Contact your IBM support center. BIP2810E The broker received a negative response to a started publish event, response is &1. Explanation: A started publish event failed, use the response to determine the cause of the failure. User 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. BIP2811E The broker was unable to receive a stopped publish event response. Explanation: A response from a stopped publish event could not be received. User Response: The broker continues to shutdown but the current published state of the broker will be incorrect. Contact your IBM support center. BIP2812E Broker &1 (UUID &2) could not process an internal configuration response message for execution group &3. 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. User 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. BIP2813E Broker &1 (UUID &2) could not process an internal configuration response message for execution group &3 to completion: missing tag &4. Explanation: The internal configuration response message returned by the execution group was incomplete. User Response: Use the system log messages to determine why the execution group failed to respond correctly. Redeploy the brokers configuration if you are able to resolve the problem. Contact your IBM support center if you are unable to resolve the problem. BIP2814E Broker could not initialize semaphore &1. Explanation: An internal semaphore could not be initialized, this semaphore controls database access. User 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.

Chapter 2. Messages

81

BIP2815E BIP3008I
BIP2815E Broker could not create a connection to its database. Explanation: An ODBC connection could not be created by the broker to access its internal persistent store tables. User 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. BIP2817E Broker could not initialize. 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 information contained in the files in the products locks directory to verify that the brokers shared semaphores are available for use. User Response: Collect all diagnostics produced and Contact your IBM support center. BIP2925E (&1, &2) : A byte array literal must have an even number of digits. 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. User Response: Ensure that the literal has an even number of digits.

BIP3000-BIP3999 (IBM Primitives)

BIP3001I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3002I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3003I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3004I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3005I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3006I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3007I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3008I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its

82

MQSeries Integrator Messages

BIP3009I BIP3018I
normal behavior. The message text associated with this exception is &1. User 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. BIP3009I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3010I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3011I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3012I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3013I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3014I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3015I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3016I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3017I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3018I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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.
Chapter 2. Messages

83

BIP3019I BIP4009E
BIP3019I Exception thrown by throw node &2; text is &1. Explanation: The throw node &2 has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is &1. User 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. BIP3901I Attempt to commit transaction when a coordinated transaction is pending; message flow node &1. Explanation: The message flow node &1 attempted to commit a database transaction, but there is already a pending transaction on the same database connection. This situation is not supported by database managers, such as DB2. User Response: Change the message flow definition and redeploy the broker. BIP3903I Node (class=&1, name=&2) propagating to &3 terminal. Explanation: The specified node is about to propagate a message to the specified terminal. User Response: No user action required.

BIP4000-BIP4999 (IBM Primitives)

BIP4002E &2 : Invalid value &1 for the Transaction attribute of a Database node. Explanation: The Transaction attribute can have the values none, commit, or rollback. An attempt was made to set the attribute to the value &1. User Response: Ensure that the levels of code installed at the Control Center, Configuration Manager and broker are all consistent. If they are, contact your IBM support center. BIP4003E &4 : The following error occurred processing the SQL statement &1 configuring node &2 in message flow &3. Explanation: The configuration of node &2 in message flow &3 failed due to errors in the SQL statement. The SQL statement text was &1 User Response: The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for statements in a Database, DataInsert, DataUpdate, DataDelete or Warehouse node in the MQSeries Integrator 2 publications. Correct the statements configuring the node and retry the configuration. BIP4004I Filter &1 : Filter evaluated to UNKNOWN. Explanation: The filter evaluated to UNKNOWN and the message will be propagated to the unknown terminal. User Response: No user action required. BIP4005I Filter &1 : Filter evaluated to FALSE. Explanation: The filter evaluated to FALSE and the message will be propagated to the false terminal. User Response: No user action required. BIP4006I Filter &1 : Filter evaluated to TRUE. Explanation: The filter evaluated to TRUE and the message will be propagated to the true terminal. User Response: No user action required. BIP4007E &4 : Error processing SQL expression &1 configuring filter node &2 in message flow &3. Explanation: The configuration of filter node &2 in message flow &3 failed due to errors in the SQL expression. The SQL expression text was &1. User Response: The next error message will give specific details of where the error occurred in the expression text. Check the correct syntax for filter expressions in the MQSeries Integrator publications. Correct the expression configuring the node and retry the configuration. BIP4008E The error detailed in following messages occurred processing &2 &1. Explanation: The error occurred during the processing of the node. User Response: Read the following messages to determine the details of the error and take the necessary corrective action. BIP4009E The error detailed in following messages occurred processing &2 &1. Explanation: The error occurred during the processing of the node. The message will be propagated to the failure terminal. User Response: Read the following messages to determine the details of the error and take the necessary corrective action.

84

MQSeries Integrator Messages

BIP4010E BIP4023E
BIP4010E &4 : Error processing the SQL statement &1 configuring Compute node &2 in message flow &3. Explanation: The configuration of Compute node &2 in message flow &3 failed due to errors in the SQL statements. The SQL statement text was &1. User Response: The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for Compute statements in the MQSeries Integrator ESQL Reference publication. Correct the statements configuring the node and retry the configuration. BIP4011E Trace node &2 reported an error processing trace pattern &1. Explanation: The error occurred processing the trace pattern &1. User Response: Check the correct syntax for the trace pattern in the MQSeries Integrator ESQL Reference publication. Correct the statements configuring the node and retry the configuration. BIP4012E (&1, &2) : Unexpectedly encountered end of trace pattern. Explanation: The trace pattern configuring a trace node contained mismatched braces ({, }) 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. User Response: Correct the trace pattern and redeploy the message flow. BIP4013E (&1, &2) : An expression must be given between braces in a Trace pattern. Explanation: The text between braces ({, }) 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. User Response: Correct the Trace pattern and redeploy the message flow. BIP4014E &2 : Invalid value &1 for the Treat Warnings As Errors attribute of a database node; yes or no required. Explanation: The Treat Warnings As Errors attribute can have the values no or yes. An attempt was made to set the attribute to the value &1. User Response: Correct the value of the attribute to either no or yes. BIP4020E NEONRules node &2 received an invalid message with the following parts: &1. 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 : &1. User 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. BIP4021E &5: Rules evaluation failed. Message details: application group &1; message type &2; rules error # &3; rules error message &4. Explanation: Details of the message and the error raised whilst processing the message by the NEON rules processor are:-

Application group: &1 Message type: &2 Rules Error #: &3 Rules Error Message: &4. If the Rules Error Message refers to a problem parsing the input message, this may be due to a problem with the database connection rather than a problem with the message itself. Check that the the file pointed to by MQSI_PARAMETERS_FILE contains the correct parameters to allow the NEONRules node to connect to the database containing your NEONRules and Formats. User Response: Further details of the error message and corrective actions can be found in the NEON manuals. BIP4022I Node &3: Rules evaluation succeeded: application group &1; message type &2. Explanation: Application group: &1, Message type: &2. User Response: No user action required. BIP4023E &5: Unknown action detected. Message details: application group &1; message type &2; action name &3; subscription ID &4. 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: &1 Message type: &2 Action Name: &3 Subscription ID: &4 User Response: Correct the NEON rules to ensure that the resultant actions are supported by MQSeries Integrator.
Chapter 2. Messages

85

BIP4024I BIP4037I
BIP4024I Node &3: The rules evaluation yielded a subscription. Message details: application group &1; message type &2. Explanation: Application group: &1, Message type: &2. User Response: No user action required. BIP4025I Node &3: No subscriptions found. Message details: application group &1; message type &2. Explanation: Application group: &1, Message type: &2. User Response: No user action required. BIP4026E An unknown error occurred processing the rules. Explanation: An unexpected error has occurred whilst processing a message by the NEONRules node. User Response: This is an internal error. Contact your IBM support center. BIP4027I Node &3: Performing a reformat operation. Message details: input message type &1; output message type &2. Explanation: Input Message Type: &1, Output Message Type: &2. User Response: No user action required. BIP4028E Failed to reformat message. Message details: input message type &1; output message type &2; formatter error number &3; formatter error message &4. Explanation: Details of the message and the error raised whilst formatting the message by the NEON formatter are:BIP4030E Target queue not set for putqueue action. Explanation: The NEON 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. User Response: Correct the NEON rules to ensure that the action is correctly specified. BIP4031E Output type not set for reformat. Explanation: The NEON rules processor has evaluated a message with a reformat action, but has not specified an output type for the message. User Response: Correct the NEON rules to ensure that the action is correctly specified. The NEON publications give details of the correct specification of the actions. BIP4032E Input type not set for reformat. Explanation: The NEON rules processor has evaluated a message with a reformat action, but has not specified an input type for the message. User Response: Correct the NEON rules to ensure that the action is correctly specified. The NEON publications give details of the correct specification of the actions. BIP4033E Cannot propagate RF header, there is no RF header on the input message. Explanation: The NEON 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. User Response: Correct the NEON rules to ensure that the action is correctly specified. The NEON publications give details of the correct specification of the actions. BIP4036I Input message type: &1 Output message type: &2 Formatter Error number: &3 Formatter Error Message: &4 User Response: Further details of the error message and corrective actions can be found in the NEON manuals. BIP4029I Node &3: Reformat completed successfully. Message details: input message type &1; output message type &2. Explanation: Input Message Type: &1, Output Message Type: &2. User Response: No user action required. Node &8: Performing a putqueue action. Options: OPT_TARGET_QUEUE &1; OPT_APP_GRP &2; OPT_MSG_TYPE &3; MQS_FORMAT &4; MQS_EXPIRY &5; MQS_PERSIST &6; MQS_PROPAGATE &7. Explanation: The putqueue options are listed above. User Response: No user action required. BIP4037I Node &8: Performing a propagate action. Options: OPT_APP_GRP &2; OPT_MSG_TYPE &3; MQS_FORMAT &4; MQS_EXPIRY &5; MQS_PERSIST &6; MQS_PROPAGATE &7. Explanation: The propagate options are listed above. User Response: No user action required.

86

MQSeries Integrator Messages

BIP4038E BIP4046E
BIP4038E &1: The Target Format attribute cannot be empty. Explanation: The Target Format attribute must specify a valid NEON output format as the target of the format operation. It cannot be the empty string. User Response: Use the Control Center to set the value of the Target Format attribute to the correct value and redeploy the message flow. BIP4039E The NEONFormatter node &2 received an invalid message, body type &1. Explanation: The messages received by the NEON Formatter node must have a NEON body. The body type of the message received was &1. User 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) identifiying 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. BIP4040I The execution group &1 has processed a configuration message successfully. Explanation: A configuration message has been processed successfully. Any configuration changes have been made and stored persistently. User Response: No user action required. BIP4041E Execution group &1 received an invalid configuration message. See the following messages for details of the 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 brokers configuration queues (SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE). User Response: Check the relevant message flow and message set definitions, check that all necessary plug-ins are installed, perform a complete redeploy of the brokers configuration and ensure that no applications are writing to the brokers configuration queues. BIP4042E Invalid action &1 in configuration message. Explanation: The message broker received a configuration message containing the invalid action &1. This error can only result from configuration messages having an invalid structure. User Response: Ensure that no applications are writing to the brokers configuration queues. BIP4043E Invalid action &1 on resource &2 in configuration message. Explanation: The message broker received a configuration message which attempted the action &1 on the resource &2 but this action is not valid for this type of resource. User Response: Check that all necessary plug-ins are installed. BIP4044E Invalid configuration message. Explanation: The message broker received an invalid configuration message and has not been able to restore its original configuration. It will now restart. User Response: If the problem is not cleared by the restart, check that the database being used to store the brokers persistent state is operating correctly then stop and restart the broker. BIP4045I Configuration changed successfully. Explanation: The message broker received a configuration message and updated its configuration accordingly. This change concerned its publish/subscribe capability. User Response: No user action required. BIP4046E Invalid configuration message. See the following messages for details of the 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). User 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.

Chapter 2. Messages

87

BIP4047E BIP4080I
BIP4047E Invalid body type &1 in configuration message. Explanation: The message broker received a configuration message containing the invalid body type &1. This error can only result from configuration messages having an invalid structure. User Response: Ensure that no applications are writing to the brokers configuration queue. BIP4048I The execution group has received a request to stop. Explanation: The execution group has received a request to stop and will terminate its process as soon as possible. User Response: No user action required. BIP4050E Duplicate Label Name attribute &1 in Label node. Explanation: Two Label nodes within a message flow have been found to have the same Label Name attribute &1. User Response: The message flow must be changed so that each Label node has a unique Label Name attribute. BIP4051E Label node with Label Name attribute &1 could not be found. Explanation: A Label node with Label Name attribute of &1 could not be found by a RouteToLabel node. User 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. BIP4060I Data &1 from Trace node &2. Explanation: The Trace node &2 has output the specified trace data. User Response: This is an information message provided by the message flow designer. The user response will be determined by the local environment. BIP4061W Invalid trace file path specification for trace node &1. Explanation: The trace node &1 has its destination specified to be a file but the given file path is empty. The message flow processing will continue, but trace output will not be written. User Response: Correct the message flow definition and redeploy it to the broker. BIP4062E Node (class=&1 name=&2) did not specify a closing brace in pattern attribute. 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. User Response: Correct the message flow configuration and redeploy the broker. BIP4063E Node (class=&1, name=&2) contained an error in the trace pattern. Explanation: The pattern attribute in the specified Trace node was not specified correctly. User Response: Correct the message flow configuration and redeploy the broker. BIP4064W Operating system error &2 opening trace file &1 for Trace node &3. Explanation: The Trace node &3 attempted to open the trace file &1 but the operating system reported the error &2. Message flow processing will continue, but trace output will not be written. The node will continually attempt to open the file until it succeeds. User 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. BIP4065W Operating system error &2 attempting to write to trace file &1 for Trace node &3. Explanation: The Trace node &3 attempted write to open the trace file &1 but the operating system reported the error &2. Message flow processing will continue, but trace output will not be written. The node will continually attempt to open the file until it succeeds. User Response: If the file could not be opened due to an environment or system error, take appropriate action to correct this situation. BIP4066W Unable to output trace data for Trace node &1. Explanation: The Trace node &1 was unable to output trace data during its execution. The following messages will indicate the reason(s) for this. User Response: Refer to the following messages and take appropriate action. BIP4067I Message propagated to Output terminal for Trace node &1. Explanation: The Trace node &1 has received a message and is propagating it to any nodes connected to its Output terminal. User Response: No user action required. BIP4080I Message propagated to try terminal from TryCatch node &1. Explanation: The TryCatch node &1 has received a message and is propagating it to any nodes connected to its try terminal. User Response: No user action required.

88

MQSeries Integrator Messages

BIP4081I BIP4201I
BIP4081I Message propagated to catch terminal from TryCatch node &1. Explanation: The TryCatch node &1 has caught an exception which occurred in a node connected to its try terminal. The message has been augmented with an exception list and is propagating it to any nodes connected to its catch terminal for further processing. See the following messages for details of the exception list. User Response: No user action required. BIP4101I Exception thrown by Throw node &1. Explanation: The Throw node &1 has received a message and will throw an exception as this is its normal behavior. User Response: No user action required. BIP4120E Configuration message contained an invalid SQL expression; Compute node &1 in message flow &2. Explanation: The Compute node &1 in message flow &2 reported an error processing its compute expression. User Response: See the following messages for details of the error. BIP4121I Message propagated to Output terminal from Compute node &1. Explanation: The Compute node &1 has received a message and is propagating it to any nodes connected to its Output terminal. User Response: No user action required. BIP4140I Exception condition detected by plug-in node &1. Explanation: The plug-in node &1 detected an error during processing. The behavior of the message flow will depend upon how the plug-in has reacted to the generation of the exception. A well-behaved plug-in is expected to re-throw the exception for it to be caught and handled by the message flow as normal. User Response: Check any error messages which follow to determine why the exception was generated, and take action as described by those messages. BIP4141E Exception condition detected in plug-in node or parser &7. Arguments: type &1; file &2; line &3; function &4; messageNumber &5; traceText &6. Explanation: The plug-in node or parser &7 has attempted to throw an exception by calling the cciThrowException() utility function, but the exception type specified in the type argument was invalid. This is a problem within the plug-in software itself. User Response: Correct the problem in the plug-in software or contact the supplier of the plug-in to report the problem. BIP4142I Evaluating cniElementSet&1. Changing value from &2 to &3. Explanation: Element &1 has been changed to &3. User Response: No user action required. BIP4160I Message propagated to match terminal by Check node &1. Explanation: The Check node &1 has matched a received message against the criteria and is propagating it to any nodes connected to its match terminal. User Response: No user action required. BIP4161E Message propagated to failure terminal by Check node &7. Values received: domain &1; set &2; type &3. Values expected: domain &4; set &5; type &6. Explanation: The Check node &7 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. User Response: No user action required. BIP4162E Non-matching message rejected by Check node &7. Values received: domain &1; set &2; type &3. Values expected: domain &4; set &5; type &6. Explanation: The Check node &7 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. User 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. BIP4180I Message propagated to Output terminal by Database node &1. Explanation: The Database node &1 has received a message and is propagating it to any nodes connected to its Output terminal. User Response: No user action required. BIP4201I Message propagated to Output terminal from node &1. Explanation: A Reset Content Descriptor node has received a message and is propagating it to any nodes connected to its Output terminal. User Response: No user action required.

Chapter 2. Messages

89

BIP4202S BIP4215S
BIP4202S The MQSeries Everyplace queue manager failed to start. Explanation: The MQSeries Everyplace queue manager failed to start. User Response: Ensure that the queue manager has been created and that the registry entry is correct. BIP4203S The internal MQSeries Everyplace transformer component failed to initialize. Explanation: The internal MQSeries Everyplace transformer component failed to initialize. User Response: Ensure that a valid transformer is being used within MQSeries Everyplace. BIP4204S MQSeries Everyplace configuration error. Explanation: MQSeries Everyplace configuration error. User Response: If using an MQSeries Everyplace ini file, please ensure that it is valid. BIP4205S An MQSeries Everyplace error occured. The exact nature of the problem could not be determined. Explanation: An MQSeries Everyplace error occured. The exact nature of the problem could not be determined. User Response: Please refer to trace messages before this error occured. BIP4206S The mqimqe.jar file could not be loaded. Explanation: The mqimqe.jar could not be read at runtime. User Response: Ensure that the file exists within the application. BIP4207E An MQSeries Everyplace method could not be accessed. Explanation: An MQSeries Everyplace method within the mqimqe.jar file could not be accessed. User Response: Ensure that the mqimqe.jar file is not damaged. BIP4208S MQSeries Everyplace database error. Cannot write to inbound table. Explanation: An error occured whilst attempting to write to the MQSeries Everyplace inbound table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4209S Error attempting to write to MQSeries Everyplace outbound database table. Explanation: An error was encountered whilst attempting to write to the MQSeries Everyplace outbound database table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4210S MQSeries Everyplace database error. Cannot write to outbound destination table. Explanation: An error occured whilst attempting to write to the MQSeries Everyplace destination table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4211E MQSeries Everyplace database error. Cannot read from inbound table. Explanation: An error occured whilst attempting to read from the MQSeries Everyplace inbound table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4212E MQSeries Everyplace database error. Cannot read from outbound message table. Explanation: An error occured whilst attempting to read from the MQSeries Everyplace outbound message table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4213S MQSeries Everyplace database error. Cannot read a record from outbound destination table. Explanation: An error occured whilst attempting to read a record from the MQSeries Everyplace destination table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4214S MQSeries Everyplace database error. Cannot delete record from inbound table. Explanation: An error occured when attempting to delete the MQSeries Everyplace inbound message table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4215S MQSeries Everyplace database error. Cannot delete record from outbound table. Explanation: An error occured when attempting to delete the MQSeries Everyplace inbound message table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database.

90

MQSeries Integrator Messages

BIP4216S BIP4230S
BIP4216S MQSeries Everyplace database error. Cannot delete record from outbound destination table. Explanation: An error occured when attempting to delete an MQSeries Everyplace outbound destination message record. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4217S MQSeries Everyplace database error. Cannot put non-publish/subscribe MQSeries Everyplace message to table. Explanation: Cannot put non-publish/subscribe MQSeries Everyplace message to inbound MQSeries Everyplace table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4218S Cannot read non-publish/subscribe MQSeries Everyplace message from table. Explanation: Cannot read a non-publish/subscribe MQSeries Everyplace message from table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4219S MQSeries Everyplace database error. Cannot put non-publish/subscribe MQSeries Everyplace message to table. Explanation: Cannot delete a non-publish/subscribe MQSeries Everyplace message from table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4220I Message propagated to Output terminal from node &1. Explanation: A Label node has received a message and is propagating it to any nodes connected to its Output terminal. User Response: No user action required. BIP4221E Some (but not all) of the MQSeries Everyplace tables are missing. Explanation: Some (but not all) of the MQSeries Everyplace tables are missing. User Response: Recreate the broker. BIP4222S The mqisdp.jar file could not be loaded. Explanation: The mqisdp.jar could not be read at runtime. User Response: Ensure that the file exists within the application. BIP4223S A SCADA method could not be accessed. Explanation: A SCADA method within the mqisdp.jar file could not be accessed. User Response: Ensure that the mqisdp.jar file is not damaged. BIP4224S SCADA database error. Cannot write to inbound table. Explanation: An error occured whilst attempting to write to the SCADA inbound table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4225S Error attempting to write to SCADA outbound database table. Explanation: An error was encountered whilst attempting to write to the SCADA outbound database table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4226S SCADA database error. Cannot write to outbound destination table. Explanation: An error occured whilst attempting to write to the SCADA destination table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4227E SCADA database error. Cannot read from inbound table. Explanation: An error occured whilst attempting to read from the SCADA inbound table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4228E SCADA database error. Cannot read from outbound message table. Explanation: An error occured whilst attempting to read from the SCADA outbound message table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4229S SCADA database error. Cannot read from outbound destination table. Explanation: An error occured whilst attempting to write to the SCADA destination table. User Response: Ensure that the database tables exist and that the application has appropriate access. BIP4230S SCADA database error. Cannot delete record from inbound table. Explanation: An error occured when attempting to delete the SCADA inbound message table. User Response: Ensure that the database tables exist and that the application has appropriate access to the database.
Chapter 2. Messages

91

BIP4231S BIP4262E
BIP4231S SCADA database error. Cannot delete record from outbound table Explanation: An error occured when attempting to delete a record from the SCADA inbound message table User Response: Ensure that the database tables exist and that the application has appropriate access to the database BIP4232S SCADA database error. Cannot delete record from outbound destination table. Explanation: An error occured when attempting to delete a SCADA outbound destination message record. User Response: Ensure that the database tables exist and that the application has appropriate access to the database. BIP4233W Could not resolve destination node using specified port number. Explanation: Could not resolve destination node using specified port number. A subscription has been made by a node that no longer exists. User Response: Unsubscribe from all subscriptions for the node no longer being used. BIP4234W Failed to get a message from the queue. Explanation: Failed to get a message from the queue. User Response: No user action required. BIP4235S Failed to put a message onto the queue. Explanation: Failed to put a message onto the queue. User Response: Queue may be full. No user action required. BIP4236S Failed to bind to specified port number. Explanation: The port number specified within the Control Center for this node is already being used or is unobtainable. User Response: Change the port number to one not being used by another application or node. BIP4237W SCADA Initialization failed. Explanation: An internal error stopped the SCADA server from starting. User Response: Redeploy the message flow. BIP4238S MQIsdp manager not avaliable. Explanation: Initialisation problem with the SCADA node. User Response: Redeploy the message flow. BIP4239S Some of the SCADA database tables are missing. Explanation: The SCADA Input node was unable to find all of the database tables required for correct operation User Response: Recreate the broker. BIP4240E RouteToLabel node &2 unable to locate Label node &1. Explanation: A RouteToLabel node has received a message containing a label but there is no Label node with this label. User Response: This problem may result from the logic of the message flow as specified by the user not calculating a 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 checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center. BIP4241I Message propagated to target Label node by RouteToLabel node &1. Explanation: A RouteToLabel node has received a message and is propagating it to the appropriate Label node. User Response: No user action required. BIP4260E A memory allocation error occurred. Explanation: The node ImbDebugNode was unsuccessful in allocating the thread local storage index. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4261E A thread creation error occurred. Explanation: The node ImbDebugNode was unsuccessful in creating a thread responsible for transmitting the breakpoint information. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4262E An initialization error occurred. Explanation: The node ImbDebugNode was unsuccessful in creating the node factory provided by the interface cniCreateNodeFactory. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center.

92

MQSeries Integrator Messages

BIP4263E BIP4277E
BIP4263E An operational error occurred. Explanation: The node ImbDebugNode was unsuccessful in defining a node class within the node factory. User 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. BIP4264E A threading problem occurred. Explanation: The node ImbDebugNode was unsuccessful in blocking incoming threads, the Control Center debugger might not work properly. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4265E A mutual exclusion error occurred. Explanation: The node ImbDebugNode was unsuccessful in releasing a mutex object. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4266E Unable to get an attribute from a node. Explanation: The attribute FlowUuid could not be received from the node ImbDebugNode. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4267E Unable to get an attribute from a node. Explanation: The attribute DebugNodeID could not be received from the node ImbDebugNode. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4268E A mutual exclusion error occurred. Explanation: An access violation occurred while waiting for a mutex object in the node ImbDebugNode. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4269W A propagation error occurred. Explanation: The node ImbDebugNode was unsuccessful to propagate a message. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4270E A propagation error occurred. Explanation: An Output terminal is not connected. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4271E An element error occurred. Explanation: The node ImbDebugNode received an unknown value type for an element. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4272E An element error occurred. Explanation: The node ImbDebugNode was unsuccessful in extracting an element value. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4273W An element error occurred. Explanation: The node ImbDebugNode was unsuccessful in extracting an element name. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4274E An element error occurred. Explanation: The node ImbDebugNode was unsuccessful in extracting an element type. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4275W An element error occurred. Explanation: The node ImbDebugNode was unsuccessful in setting an element value. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4276E A terminal creation error occurred. Explanation: The node ImbDebugNode was unsuccessful in creating an Input terminal. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4277E A terminal creation error occurred. Explanation: The node ImbDebugNode was unsuccessful in creating an Output terminal. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center.

Chapter 2. Messages

93

BIP4278E BIP4343E
BIP4278E A create node error occurred. Explanation: The node name is not supported for the node ImbDebugNode. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4279E A communication setting error occurred. Explanation: The node ImbDebugNode was unsuccessful in getting the controller IP address. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4280E A reception error occurred. Explanation: The node ImbDebugNode was unsuccessful in receiving information from the Control Center. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4281E A socket error occurred. Explanation: The node ImbDebugNode was unsuccessful in creating a socket. User Response: Restart your broker, redeploy the mesage flow and retry the operation. If this problem persists, contact your IBM support center. BIP4282E A socket error occurred. Explanation: The node ImbDebugNode was unsuccessful in setting the socket options. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4283E A connection error occurred. Explanation: The node ImbDebugNode was unsuccessful in connecting to a Control Center socket. User Response: Restart your broker, restart your Control Center and retry the operation. If this problem persists, contact your IBM support center. BIP4284E A sending error occurred. Explanation: The node ImbDebugNode was unsuccessful in sending information to the Control Center. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4285E A socket error occurred. Explanation: The node ImbDebugNode was unsuccessful in binding a socket. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4286E A socket error occurred. Explanation: The node ImbDebugNode was unsuccessful in listening to a client connection. User Response: Restart your broker, redeploy the message flow and retry the operation. If this problem persists, contact your IBM support center. BIP4287E A memory allocation error occurred. Explanation: The node ImbDebugNode was unsuccessful in allocating memory. User Response: Restart your broker and retry the operation. If this problem persists, contact your IBM support center. BIP4302E MQSeries Everyplace bridge queue name is not specified. This is a manditory field. Explanation: MQseries Everyplace bridge queue name is not specified. This is a manditory field. User Response: Add the required name/value pair and redeploy the message flow. BIP4303E The trace file for MQSeries Everyplace could not be created. Explanation: The trace file specified for MQSeries Everyplace trace could not be created. User Response: Ensure that your disk is not full and that this file is not write protected. BIP4342E MQSeries Everyplace bridge queue name is not specified. This is a manditory field. Explanation: MQseries Everyplace bridge queue name is not specified. This is a manditory field. User Response: Add the required name/value pair and redeploy the message flow. BIP4343E The trace file for MQSeries Everyplace could not be created Explanation: The trace file specified for MQSeries Everyplace trace could not be created. User Response: Ensure that your disk is not full and that this file is not write protected.

BIP5000-BIP5999 (Parsers)

94

MQSeries Integrator Messages

BIP5001E BIP5105E
BIP5001E Internal error. Invalid buffer offsets for output: start offset &1; end offset &2; end of buffer &3. Explanation: The offsets for an XML element are invalid. Start offset = &1, End offset = &2. End of buffer : &3. User Response: Record the full details provided with this message and contact your IBM Support Center. BIP5002E Error creating AsgardParser. Explanation: A failure was encountered while attempting to create a parser object. User Response: Increase the memory capacity of your system or try to free up some system memory by closing other applications. BIP5003E Internal Error. Invalid buffer parameters: offset &1; size &2. Explanation: An invalid buffer was passed to the XML parser. Offset = &1 . Size = &2. User Response: Record the full details provided with this message and contact your IBM support center. BIP5004E An error has been reported by the BIPXML4C component: code &1; public id &2; line number &3; column number &4; current element &6; error text &5. Explanation: The above error was reported by the XML parser. User Response: Check that the XML message is well-formed and that it adheres to the XML specification. BIP5005E No valid body of the document could be found. Explanation: There should be one, and only one, top level element of type element or EmptyElement and this is not the case for the current message. User Response: Check that the XML message being passed in is a well formed XML message that adheres to the XML specification and that only one of the above exists as a child of the root. BIP5006E Duplicate XML or DOCTYPE declaration of element &1. Explanation: The element &1 has been defined more than once as type xmlXmlDecl or xmlDocTypeDecl. Only one element may be defined as one of these types. User 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. BIP5007E The element &1 has an invalid element type for a top level element. Explanation: A top level element was found which didnt have type xmlXmlDecl, xmlDocTypeDecl, xmlParserRoot, xmlComment, xmlProcessingInstruction or xmlWhiteSpace. User 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. BIP5008E Invalid element name &1. Explanation: An invalid element name found. This could mean an element name was a comment ( User 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. BIP5009E XML Parsing Errors have occurred. Explanation: Errors have occurred during parsing of XML. User Response: Review further error messages for an indication to the cause of the errors. BIP5010E XML Writing Errors have occurred. Explanation: Errors have occurred during writing of XML. User Response: Review further error messages for an indication to the cause of the errors. BIP5102E Data overflow. The field &1 in message &2 with a value of &3 has caused an overflow. 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. User Response: Modify the message model or custom wire format mapping, redeploy to the parser and send the message through again. BIP5103E The message identifier is not available to the parser. Explanation: The message identifier, for this message, is not being passed to the parser correctly. User Response: Correct the mapping, redeploy to the parser and send the message through again. BIP5105E Memory allocation failed. Explanation: A failure was encountered while attempting to allocate memory. User Response: Increase the memory capacity of your

Chapter 2. Messages

95

BIP5107E BIP5125E
system or try to free up some system memory by closing other applications. BIP5107E Unknown internal time representation. Explanation: While mapping a time field to a physical type, an invalid physical type was encountered. User Response: Modify the message model or custom wire format mapping, redeploy to the parser and send the message through again. BIP5113E Error retrieving message definition from dictionary. Explanation: The message identifier encountered was not found in the runtime dictionary. User Response: Check that you are using an appropriate dictionary for the message being sent and resubmit the message. BIP5115E Element &1 is not a member of the message. Explanation: While handling a message, the element &1 was not defined as a direct member of the current message as defined in the runtime dictionary. User Response: Check that you are using an appropriate dictionary for the message being sent and resubmit the message. BIP5116E Unexpected XML element encountered: message set &1; message &2; tag encountered &3. 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 = &1, Message = &2, Tag encountered = &3. User Response: Check that you are using an appropriate dictionary for the message being sent and resubmit the message. BIP5117E An error has been reported by the BIPXML4C component: code &1; public identifier &2; line number &3; column number &4; error text &5; current message &6, current element &7. Explanation: The above error was reported by the XML parser. User Response: Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. BIP5118E XML input / output exception reported. Explanation: The above error was reported by the XML parser. User Response: Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. BIP5119E XML Exception reported. Explanation: The error was reported by the BIPXML4C parser. User Response: Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. BIP5120E XML parser reported by the BIPXML4C parser: error text &1. Explanation: The error was reported by the BIPXML4C parser error text &1. User Response: Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. BIP5121E Invalid buffer offsets on element: start offset &1; end offset &2. Explanation: An internal error occurred when attempting to write an XML message. An element has a start element offset of &1 and an end offset of &2. User Response: Check that the XML message being passed in is a well-formed XML message that adheres to the XML specification. BIP5122E Unidentified field identifier &1 in data stream. Explanation: While handling a PDF message, a field identifier, &1 was encountered which was not found in the runtime dictionary. User Response: Check that you have deployed and are using the appropriate dictionary for the message being sent and resubmit the message. BIP5123E Invalid buffer parameters: index &1; size &2. Explanation: An internal processing error has occurred. An invalid buffer was passed to the MRM parser. Properties of the buffer are : Index = &1; Size = &2. User Response: Record the full details provided with this message and contact your IBM support center BIP5124E Internal Error: A call to DumpCWFMsgInfo failed with error code &1. Explanation: An internal processing error has occurred while writing out Custom Wire Format debug information. Error code &1. User Response: Record the full details provided with this message and contact your IBM support center. BIP5125E Error extracting a message from the record oriented bitstream. Explanation: The error was encountered while reading the bitstream. User Response: Ensure that the message being passed, is modelled correctly and that the appropriate runtime

96

MQSeries Integrator Messages

BIP5126E BIP5145E
dictionary and Custom Wire Format information have been deployed successfully. BIP5126E Error freeing temporary resources. Explanation: The error was encountered while freeing temporary resource used during the handling of a record-oriented bitstream. User Response: Record the full details provided with this message and contact your IBM support center. BIP5127E Internal error while processing custom wire format data for &1. Explanation: An error was encountered while extracting information from the deployed Custom Wire Format resource. User Response: Record the full details provided with this message and contact your IBM support center. BIP5128E Error initializing MRM message &2 with dictionary identifier &1. Explanation: The message &2 could not be initialized using the dictionary &1. User Response: Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message. BIP5129E Error retrieving Message Translation Interface table entry from message handle: message &2; dictionary &1. Explanation: An error occuring while trying to get a table entry using the message &2 and the dictionary &1. User Response: Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message. BIP5130E Parser error retrieving dictionary handle: current message set id &1; current message id &2. Explanation: Error retrieving dictionary handle from message handle. Current message set id = &1, current message id = &2. User Response: Check that you have deployed and are using the appropriate dictionary for the message being processed and resubmit the message. BIP5131E Message set identifier is not valid. Explanation: When parsing an MRM message the broker requires a valid message set identifier. User Response: Record the full details provided with this message and contact your IBM support center. BIP5132E Custom Wire Format identifier is not valid. Explanation: When parsing an MRM, Custom Wire Format message the broker requires a valid message set identifier and a valid Custom Wire Format identifier.
Chapter 2. Messages

User Response: Record the full details provided with this message and contact your IBM support center. BIP5133E An internal MRM parser error occurred. 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. User Response: Record the full details provided with this message and contact your IBM support center. BIP5134E Message identifier is not valid. Explanation: When parsing an MRM message the broker requires a valid message identifier. User Response: Record the full details provided with this message and contact your IBM support center. BIP5135E Error writing Custom Wire Format message. Explanation: An error occurred while writing to the message buffer. User Response: Please refer back to any previous error messages to determine why the error might have occurred. BIP5136E Invalid Wire format &1. Explanation: When processing an MRM message the broker requires a valid wire format indicator. Expected XML, PDF or Custom Wire Format prefix and got &1. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5140E Error deploying Custom Wire Format module: message set id &1; format descriptor id &2; format module &3. Explanation: An error was detected when trying to deploy a Custom Wire Format module. Message set id = &1, Custom Wire Format descriptor id = &2, Custom Wire Format module = &3. User Response: Record the full details provided with this message and contact your IBM support center. BIP5145E Error setting up runtime dictionary resource using message set identifier &1. Explanation: An error was detected when trying to deploy message set. Use the Control Center to match the message set identifier : &1, to a message set name. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center.

97

BIP5146E BIP5158E
BIP5146E Error setting up Custom Wire Format resource: message set identifier &1; Custom Wire Format descriptor identifier &2. Explanation: An error was detected when trying to deploy a Custom Wire Format description record. Message set identifier = &1, Custom Wire Format descriptor identifier = &2. User Response: Record the full details provided with this message and contact your IBM support center. BIP5147E Error setting up relationship of Custom Wire Format to plug-in: message set identifier &1; format descriptor identifier &2; format module &3. 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 identifier = &1, Custom wire format descriptor identifier = &2, Custom Wire Format module = &3. User Response: Record the full details provided with this message and contact your IBM support center. BIP5148E Unexpected detail type &1 received from broker. Explanation: An error was detected when trying to deploy a detail from the broker. The detail type: &1 is unknown to the current MRM parser. User Response: Record the full details provided with this message and contact your IBM support center. BIP5149E Error deleting runtime dictionary resource: message set &1. Explanation: An error was detected when trying to remove a deployed resource from the broker for message set &1. User Response: Record the full details provided with this message and contact your IBM support center. BIP5151E Error parsing PDF bit stream: message set identifier &1; message identifier &2. Explanation: An error was detected when trying to parse a MRM native bitstream. User Response: Record the full details provided with this message and contact your IBM support center. BIP5152E Message definition does not contain element: message set identifier &1; message identifier &2; element found &3. 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. User 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. BIP5153E Retrieving Message Definition from dictionary: message &2; message set &1. 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. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5154E Structure &1 does not contain element &2. Explanation: The current message content implies that structure &1 contains element &2. The message set definition does not support this. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5155E An error occurred while retrieving definition of structure &1 from run-time dictionary. Explanation: The message set definition does not have a definition for structure &1. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5156E Definition for element &1 not found in dictionary. Explanation: The deployed message set does not have a definition for element &1. User Response: Check that you have packaged the message set and the correct message properties correctly then resubmit the message. BIP5157E Error allocating buffer for list of deployed formats. Explanation: A failure was encountered while attempting to allocate memory. User Response: Increase the memory capacity of your system or try to free up some system memory by closing other applications. BIP5158E Error retrieving list of deployed formats. Explanation: Error retrieving list of deployed formats. User Response: Record the full details provided with this message and contact your IBM support center.

98

MQSeries Integrator Messages

BIP5159E BIP5173E
BIP5159E Error deleting Custom Wire Format resource: message set identifier &1; Custom Wire Format &2. Explanation: An error was detected when trying to remove a deployed resource from the broker. Error removing Custom Wire Format: &2. Message set identifier = &1. User Response: Record the full details provided with this message and contact your IBM support center. BIP5160E Error retrieving Custom Wire Format for dictionary: message set &1. Explanation: An error was detected when trying to retrieve a list of deployed Custom Wire Formats from the broker for message set &1. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5161E Error allocating buffer for list of deployed Custom Wire Formats. Explanation: A failure was encountered while attempting to allocate memory. User Response: Increase the memory capacity of your system or try to free up some system memory by closing other applications. BIP5162E Internal error initializing the Message Translation Interface with the Resource Manager. Explanation: An internal processing error has occurred. User Response: Record the full details provided with this message and contact your IBM support center. BIP5163E Invalid data source for broker database. Explanation: An internal error has occurred when trying to connect to a data source through the resource manager. User Response: Record the full details provided with this message and contact your IBM support center. BIP5164E Error setting internal value: element &1. Explanation: An error has occurred when trying to match the value set in the element &1 with the type of the element. User Response: Check that the field is in the correct format for the data type expected. BIP5167E Error with Custom Wire Format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Custom Wire Format general error. User Response: Record the full details provided with this message and contact your IBM support center. BIP5168E Overflow error with Custom Wire Format: message set &3; message &4; parent element &5; current element &6. Explanation: While mapping a physical data type to a logical type, a data overflow occurred. The value being set in the logical representation is larger than the maximum value possible for the chosen logical type. User Response: Change the incoming message so that the current element given above is in the correct range. BIP5169E Data type error with Custom Wire Format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Examined the physical type of an element. Data type is not catered for. User Response: Check that you have a valid physical type associated with this field in the Custom Wire Format characteristics. BIP5170E Custom Wire Format. Read Legacy Error: message set &3; message &4; parent element &5; current element &6. Explanation: Data compared against the boolean representations. Read legacy error. User Response: Record the full details provided with this message and contact your IBM support center. BIP5171E Custom Wire Format. Write Legacy Error: message set &3; message &4; parent element &5; current element &6. Explanation: The actual length of a 1 or 2-byte length encoded string is greater than the maximum number which can be set as the length part of the string. User Response: Record the full details provided with this message and contact your IBM support center. BIP5172E Custom Wire Format. Read Bitstream Error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Read Custom Wire Format Bitstream Error. User Response: Record the full details provided with this message and contact your IBM support center. BIP5173E Invalid Custom Wire Format data: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Custom Wire Format error. Invalid Data. User Response: Record the full details provided with this message and contact your IBM support center.

Chapter 2. Messages

99

BIP5174E BIP5184E
BIP5174E Custom Wire Format error. Insufficient memory: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Unable to allocate any more space. Insufficient memory available. User Response: Increase the memory capacity of your system or try to free up some system memory by closing other applications. BIP5175E Custom Wire Format. Error opening file: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while opening a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5176E Custom Wire Format. Error reading file: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5177E Custom Wire Format. NLS conversion error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: During translation of a string between unicode and ASCII representations an error occurred. User Response: Record the full details provided with this message and contact your IBM support center. BIP5178E Custom Wire Format. Tree read error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading the tree from the Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5179E Internal error writing elements in Custom Wire Format: message set &3; message &4; parent element &5; current element &6. Explanation: An internal error has occurred whilst processing elements in the message set above. User Response: Record the full details provided with this message and contact your IBM support center. BIP5180E Message identifier not in Custom Wire Format File: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: When parsing an MRM, Custom Wire Format message the broker requires a valid message set identifier and a valid Custom Wire Format identifier. The Message identifier was not found in the Custom Wire Format file. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5181E Custom Wire Format error. Message bitstream smaller than expected: message set &3; message &4; parent element &5; current element &6. Explanation: The bitstream of the message being parsed by the MRM parser is smaller than the size expected for a CWF message of that message type. User Response: The message bit stream has been incorrectly constructed. Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5182E Custom Wire Format error. Write buffer overflow: message set &3; message &4; parent element &5; current element &6. Explanation: A result would not fit in the supplied buffer. User Response: Increase the memory capacity of your system or try to free up some system memory by closing other applications. BIP5183E Custom Wire Format error. Invalid buffer: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: A null buffer has been encountered. User Response: Record the full details provided with this message and contact your IBM support center. BIP5184E Custom Wire Format. Repeat logic error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The number of repeats assigned to an element is invalid. User Response: Record the full details provided with this message and contact your IBM support center.

100

MQSeries Integrator Messages

BIP5185E BIP5196E
BIP5185E Custom Wire Format. Resource error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error in Custom Wire Format. The resource manager successfully loaded the resource but the details are invalid. User Response: Record the full details provided with this message and contact your IBM support center. BIP5186E Custom Wire Format. Error reading date: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a logical date from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5187E Custom Wire Format. Error reading time: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a logical time from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5188E Custom Wire Format. Error reading date and time: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a logical date and time from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5189E Custom Wire Format. Error writing date: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while writing a logical date from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5190E Custom Wire Format. Error writing time: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while writing a logical time from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5191E Custom Wire Format. Error writing date and time: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while writing a logical date and time from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5192E Custom Wire Format error. Invalid date format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a date format string from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5193E Custom Wire Format error. Invalid time format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a time format string from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5194E Custom Wire Format error. Invalid DateTime format string time: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An error has occurred while reading a datetime format string from a Custom Wire Format file. User Response: Record the full details provided with this message and contact your IBM support center. BIP5195E Custom Wire Format error. Invalid element length: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An invalid element length was encountered for a Custom Wire Format element. User Response: Record the full details provided with this message and contact your IBM support center. BIP5196E Custom Wire Format error. Invalid extended decimal: message set &3; message &4; parent element &5; current element &6. Explanation: Custom Wire Format invalid extended decimal. User Response: Record the full details provided with this message and contact your IBM support center.
Chapter 2. Messages

101

BIP5197E BIP5207E
BIP5197E Custom Wire Format error. Invalid packed decimal: message set &3; message &4; parent element &5; current element &6. Explanation: Custom Wire Format invalid packed decimal. User Response: Check that the packed decimal has been constructed correctly. BIP5198E Custom Wire Format error. Field length overflow: message set &3; message &4; parent element &5; current element &6. Explanation: A field length overflow has occurred. User 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. BIP5199E Data overflow in field &1 of message &2: length &4 exceeds maximum of &3. Explanation: The field &1 in message &2 has a maximum length defined in the dictionary of &3. The actual value of the field has a length of &4. User Response: Modify the message set or message flow and redeploy to the broker or modify the input message and resubmit to the broker. BIP5200E Invalid buffer for conversion between text and binary: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An invalid buffer has been passed for conversion from text to binary data during the deployment process. User Response: Record the full details provided with this message and contact your IBM support center. BIP5201E Message Translation Interface error. Invalid field type: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error code is returned by MTIAddField and MTIAddFieldInstance if the field type parameter is invalid. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5202E Message Translation Interface error. Invalid message handle: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The message handle parameter passed into the Message Translation Interface API function that requires a message handle, which is not a valid handle for the message. User Response: Record the full details provided with this message and contact your IBM support center. BIP5203E Message Translation Interface error. Invalid mode: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The mode parameter is not set to one of the specified values. User Response: Record the full details provided with this message and contact your IBM support center. BIP5204E Message Translation Interface error. Invalid Mode For Process order: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The mode is not set to one of the specified values for the process order that has been specified. User Response: Record the full details provided with this message and contact your IBM support center. BIP5205E Message Translation Interface error. Invalid Node Class: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Node Class parameter in a function call is not a valid value for that function. User Response: Record the full details provided with this message and contact your IBM support center. BIP5206E Message Translation Interface error. Invalid Process Order: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Process Order parameter passed into the Message Translation Interface function is not a valid value. User Response: Record the full details provided with this message and contact your IBM support center. BIP5207E Message Translation Interface error. Invalid Relative Position: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Relative Position parameter passed into the Message Translation Interface function is not valid. User Response: Record the full details provided with this message and contact your IBM support center.

102

MQSeries Integrator Messages

BIP5208E BIP5218E
BIP5208E Message Translation Interface error. Invalid Return Code: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5209E Message Translation Interface error. Invalid syntax version: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The version number of the message is not correct. User Response: Record the full details provided with this message and contact your IBM support center. BIP5210E Message Translation Interface error. Invalid relative position for element: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Message Translation Interface tried to add a new message element as a child element to another message element that is not a predefined or self-defining structure. User Response: Record the full details provided with this message and contact your IBM support center. BIP5211E Message Translation Interface error. Invalid operation for element: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The type of a message element is not valid for the sort of operation that you are trying to perform on it. User Response: Record the full details provided with this message and contact your IBM support center. BIP5212E Message Translation Interface error. Invalid message: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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. User Response: Record the full details provided with this message and contact your IBM support center. BIP5213E Message Translation Interface error. Invalid structure: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error in the Message Translation Interface for an invalid structure. User Response: Record the full details provided with this message and contact your IBM support center. BIP5214E Message Translation Interface error. Invalid message operation: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: An operation carried out on a predefined message element is illegal. User Response: Record the full details provided with this message and contact your IBM support center. BIP5215E Message Translation Interface error. Invalid identifier: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5216E Message Translation Interface error. Invalid version number: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5217E Message Translation Interface error. Invalid dump format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error is returned from MTIDumpMessage when the dump format parameter is invalid. User Response: Record the full details provided with this message and contact your IBM support center. BIP5218E Message Translation Interface error. Invalid message name: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error code is returned by the function MTIGetMessageIdent when the message name
Chapter 2. Messages

103

BIP5219E BIP5228E
parameter does not specify a valid message. User Response: Record the full details provided with this message and contact your IBM support center. BIP5219E Message Translation Interface error. Invalid tag name: message set &3; message &4; parent element &5; current element &6. Explanation: This error code is returned by the function MTIGetTagIdForTagText when the tag name parameter does not specify a valid tag. User Response: Check that the XML message contains the correct tags for the message type defined in the message set given above. BIP5220E Message Translation Interface error. Invalid message mode: message set &3; message &4; parent element &5; current element &6; function name &5; error code &1. Explanation: This error code is returned by the function MTIGetMessageIdent when the message mode parameter does not specify a valid mode. User Response: Record the full details provided with this message and contact your IBM support center. BIP5221E Message Translation Interface error. Invalid parameter: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error is returned from MTIGetPreDefinedTransactionDefinition when an invalid parameter is passed to this function. User Response: Record the full details provided with this message and contact your IBM support center. BIP5222E Message Translation Interface error. Invalid instance array: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned by MTIAddAtom and MTIGetAtom when the instanceArray parameter is NULL, or when the length of the instanceArray (instanceArrayLen) is incorrect. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5223E Message Translation Interface error. Invalid context tag: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned by MTIAddAtom and MTIGetAtom when an invalid context tag is passed to the context_tag parameter. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5224E Message Translation Interface error. Invalid transaction identifier: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned by MTIAddAtom and MTIGetAtom when the message header of the goldMsgHandle parameter contains an invalid requestType. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5225E Message Translation Interface. PDF write error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an Message Translation Interface PDF write operation fails. User Response: Record the full details provided with this message and contact your IBM support center. BIP5226E Message Translation Interface. PDF read error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an Message Translation Interface PDF read operation fails. User Response: Record the full details provided with this message and contact your IBM support center. BIP5227E Message Translation Interface error. PDF invalid length: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an Message Translation Interface PDF has an invalid length. User Response: Record the full details provided with this message and contact your IBM support center. BIP5228E Message Translation Interface error. PDF invalid operation: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an invalid operation is performed on an Message Translation Interface PDF. User Response: Record the full details provided with this message and contact your IBM support center.

104

MQSeries Integrator Messages

BIP5229E BIP5239E
BIP5229E Message Translation Interface error. PDF overflow: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an Message Translation Interface PDF operation causes an overflow. User Response: Record the full details provided with this message and contact your IBM support center. BIP5230E Message Translation Interface error. PDF not initialized: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when an Message Translation Interface PDF is not initialized. User Response: Record the full details provided with this message and contact your IBM support center. BIP5231E Message Translation Interface. PDF initializing error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error initializing an Message Translation Interface PDF. User Response: Record the full details provided with this message and contact your IBM support center. BIP5232E Message Translation Interface. PDF termination error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when there is an error terminating an Message Translation Interface PDF. User Response: Record the full details provided with this message and contact your IBM support center. BIP5233E Message Translation Interface. PDF read header error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when there is an error reading an Message Translation Interface PDF header. User Response: Record the full details provided with this message and contact your IBM support center. BIP5234E Message Translation Interface. PDF write header error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when there is an error writing an Message Translation Interface PDF header. User Response: Record the full details provided with this message and contact your IBM support center. BIP5235E Message Translation Interface error. PDF invalid CP: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This is returned when there is an invalid CP operation on an Message Translation Interface PDF. User Response: Check that you have a valid broker installation. If the problem persists contact your IBM support center. BIP5236E Message Translation Interface error. NLS file malformed: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Message Translation Interface returns this error if the NLS codepage file is found to contain data that does not conform to the NLS file specification. User Response: Record the full details provided with this message and contact your IBM support center. BIP5237E Message Translation Interface error. Invalid NLS string: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error is returned when the Message Translation Interface encounters invalid data in an NLS string. User Response: Check that you have a valid broker installation. If the problem persists contact, your IBM support center. BIP5238E Message Translation Interface error. Message header missing: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Message Translation Interface returned an error indicating that the message has no header attached. User Response: Record the full details provided with this message and contact your IBM support center. BIP5239E Message Translation Interface error. No transaction value: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: A message does not have a transaction value. User Response: Check the message and redeploy.

Chapter 2. Messages

105

BIP5240E BIP5249E
BIP5240E Message Translation Interface warning: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Error. The Message Translation Interface function encountered a compatibility problem. User Response: Record the full details provided with this message and contact your IBM support center. BIP5241E Message Translation Interface error. Missing mandatory element: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The Message Translation Interface has returned an error indicating that the mandatory element is missing from a message. User Response: Record the full details provided with this message and contact your IBM support center. BIP5242E Message Translation Interface error. Insufficient memory: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. This error is returned by any Message Translation Interface function that tries to allocate memory and fails. User Response: Record the full details provided with this message and contact your IBM support center. BIP5243E Message Translation Interface error. Buffer full: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. This error indicates that a memory buffer, used while putting a message to bitstream, has filled completely. User Response: Check that you have a valid broker installation. If the problem persists contact your IBM support center. BIP5244E Message Translation Interface error. Batch buffer full: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5245E Message Translation Interface error. Empty message: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5246E Message Translation Interface error. Field Definition mismatch: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5247E Message Translation Interface. Index error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. This error is returned when a function that uses an index as a reference to an instance of a element or structure has been given an index value that is invalid. User Response: Check that you have a valid broker installation. If the problem persists contact, your IBM support center. BIP5248E Message Translation Interface. Initialization error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. The Message Translation Interface failed to initialize correctly. User Response: Record the full details provided with this message and contact your IBM support center. BIP5249E Message Translation Interface. Message parsing error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal error. The Message Translation Interface function encountered a problem with the structure of a message stored in a bitstream. User Response: Record the full details provided with this message and contact your IBM support center.

106

MQSeries Integrator Messages

BIP5250E BIP5259E
BIP5250E Message Translation Interface error. Null pointer: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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. User Response: Record the full details provided with this message and contact your IBM support center. BIP5251E Message Translation Interface error. Structure Definition mismatch: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5252E Message Translation Interface. System error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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. User Response: Check that you have a valid broker installation. If the problem persists contact, your IBM support center. BIP5253E Message Translation Interface. Trace error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error code is returned when there is an error opening a trace file or stream. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5254E Message Translation Interface. Element is field: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Internal Message Translation Interface code. User Response: Record the full details provided with this message and contact your IBM support center. BIP5255E Message Translation Interface error. Duplicate Peer IDs: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error is returned when the MTIPutMessageToBitstream and MTIGetMessageFromBitstream functions find that two peer message elements have the same TAG. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5256E Message Translation Interface. Bitstream error: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error occurs when there is an file handling type error when opening, closing or manipulating a bitstream. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5257E Message Translation Interface error. Data out of bounds: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error occurs when encoding a predefined structure containing a character field with data that is too large for the character field. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5258E Message Translation Interface not initialized: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error occurs when a Message Translation Interface function is called before the Message Translation Interface function MTIInitialize has been successfully called. User Response: Record the full details provided with this message and contact your IBM support center. BIP5259E Message Translation Interface error. Options warning: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Message Translation Interface Options warning message. User Response: Record the full details provided with this message and contact your IBM support center.
Chapter 2. Messages

107

BIP5260E BIP5270E
BIP5260E Message Translation Interface error. Definition not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: The definition of a predefined field, structure, message or transaction was not found in the Standard Message Dictionary. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5261E Message Translation Interface error. Element not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: A search for a message element did not find the element. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5262E Message Translation Interface error. CStruct not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: This error is returned when a CStruct can not be found in the Standard Message Dictionary. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5263E Message Translation Interface error. Status information not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Message Translation Interface Status Information could not be found. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5264E Message Translation Interface error. NLS file not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: Returned by Message Translation Interface when NLS codepage file or DLL cannot be found or loaded. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5265E Message Translation Interface error. NLS incompatible version: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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 isnt using the correct version of the Message Translation Interface. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5266E Resource Manager error. Configuration File missing: message set &3; format identifier &4; function name &2; error code &1. Explanation: An Internal error occurred. The configuration file is missing for the Resource Manager. User Response: Record the full details provided with this message and contact your IBM support center. BIP5267E Resource Manager. Configuration file error: message set &3; format identifier &4; function name &2; error code &1. Explanation: Internal error. Configuration file is malformed for the Resource Manager. User Response: Record the full details provided with this message and contact your IBM support center. BIP5268E Resource Manager error. Mapping file missing: message set &3; format identifier &4; function name &2; error code &1. Explanation: Internal error. The mapping file is missing for the Resource Manager. User Response: Record the full details provided with this message and contact your IBM support center. BIP5269E Resource Manager error. Corrupt Mapping file: message set &3; format identifier &4; function name &2; error code &1. Explanation: An internal error occurred in the Resource Manager as the mapping file is corrupted. User Response: Record the full details provided with this message and contact your IBM support center. BIP5270E Resource Manager error. Buffer too small: message set &3; format identifier &4; function name &2; error code &1. Explanation: Buffer parameter is too small. User Response: Check that you have a valid broker

108

MQSeries Integrator Messages

BIP5271E BIP5282E
installation. If the problem persists, contact your IBM support center. BIP5271E Resource Manager. File error: message set &3; format identifier &4; function name &2; error code &1. Explanation: A general file I/O error occurred in the Resource Manager. User Response: Record the full details provided with this message and contact your IBM support center. BIP5272E Resource Manager error. Duplicate resource: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Resource Manager attempted to add a resource into the mapping file when it already exists. User Response: Record the full details provided with this message and contact your IBM support center. BIP5273E Resource Manager error. Resource not found: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Resource Manager requested a resource that was not found in the mapping file. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5274E Resource Manager error. Dependency exists: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Resource Manager tried to delete a resource on which a dependency exists. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5275E Resource Manager error. Resource in use: message set &3; format identifier &4; function name &2; error code &1. Explanation: The resource is not present in the mapping file, but is still in use by the Resource Manager. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5276E Resource Manager error. Plug-in module not found: message set &3; format identifier &4; function name &3; error code &1. Explanation: Plug-in module cannot be found/loaded. User Response: Check that you have a valid broker installation. If the problem persists contact your IBM support center. BIP5277E Resource Manager error. Plug-in entry point not found: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Plug-in module does not contain a mandatory entry point. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5278E Resource Manager not initialized: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Resource Manager has not been initialized. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5279E Resource Manager error. Invalid datasource: message set &3; format identifier &4; function name &2; error code &1. Explanation: The Resource Manager cannot find an ODBC datasource or a flat file. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5280E Message Translation Interface error. Unknown Error. Explanation: An unhandled internal error has occurred in the Message Translation Interface. User Response: Record the full details of the activity that was in progress and contact your IBM support center. BIP5281E Conversion from text to binary. Invalid buffer: message set &3; resource type &2; resource name &3. Explanation: An invalid buffer has been passed for conversion from text to binary data during the deployment process. Additional information: Message set = &1, Resource type = &2, Resource name = &3. User 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. BIP5282E Invalid child elements of structure element found. Explanation: A child element was found under a structure which is not a valid child for this structure. User Response: Check that you have packaged the message correctly and set the correct message
Chapter 2. Messages

109

BIP5283E BIP5902W
properties then resubmit the message. BIP5283E Invalid repeating field within structure element &1. Explanation: A repeating element was detected within a structure element, &1. 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. User Response: Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5284E Message Translation Interface error. Invalid element handle: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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 an message element. User Response: Check that you have a valid broker installation. If the problem persists, contact your IBM support center. BIP5285E Message Translation Interface Parsing Errors have occurred. Explanation: Errors have occurred during parsing. User Response: Review further error messages for an indication to the cause of the errors. BIP5286E Message Translation Interface Writing Errors have occurred. Explanation: Errors have occurred during writing. User Response: Review further error messages for an indication to the cause of the errors. BIP5287E Message Translation Interface error. Offset greater than message length: message set &1; message &2. Explanation: The message received is invalid because the offset of an element in the message is greater than Message length. User Response: Record the full details provided with this message and contact your IBM support center. BIP5288E Message Translation Interface error. Message bitstream larger than expected: message set &1; message &2. Explanation: The bitstream of the message being parsed by the MRM parser is larger than the size expected for a Custom Wire Format message of that message type. User Response: The message bitstream has been incorrectly constructed. Check that you have packaged the message correctly and set the correct message properties then resubmit the message. BIP5289E Message Translation Interface error. Message set identifier too large for buffer: message set &3 (size &2); buffer size &1. Explanation: The message set identifier &3 exceeds the length of the internal buffer used to store the identifier. Current buffer size is &1. The message set identifier size is &2. User 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. BIP5290E Invalid value for physical data type in Custom Wire Format: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. 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. User 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. BIP5291E The field &1 in message &2 has a repeat count defined in the dictionary of &3. The actual number of repeats is &4. 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 MRM. User 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. BIP5292E Custom Wire Format error: Expected element not found: message set &3; message &4; parent element &5; current element &6; function name &2; error code &1. Explanation: While mapping a physical data type to a logical type an expected element was not found. User Response: Check that the current element given above is in the incoming message. BIP5902W Error in parser &1 occurred whilst parsing the field named &2. Explanation: This message gives the name of the field in the parser that was being parsed at the time the error occurred. User Response: You should check for other messages issued with this one for the full context of the error.

110

MQSeries Integrator Messages

BIP5903W BIP6007E
BIP5903W Invalid configuration message: type &1 invalid for parser factory &2. Explanation: The message broker received a configuration message containing an instruction to create a message format detail of type &1 but this not a valid type for parser factory &2. User Response: No user action required. BIP5904W Invalid configuration message: type &1 invalid for parser factory &2. Explanation: The message broker received a configuration message containing an instruction to change a message format detail of type &1 but this not a valid type for parser factory &2. User Response: No user action required. BIP5905W Invalid configuration message: type &1 invalid for parser factory &2. Explanation: The message broker received a configuration message containing an instruction to delete a message format detail of type &1 but this not a valid type for parser factory &2. User Response: No user action required. BIP5906W Invalid configuration message: type &1 invalid for parser factory &2. Explanation: The message broker received a configuration message containing an instruction to report a message format detail of type &1 but this not a valid type for parser factory &2. User Response: No user action required. BIP5912W Error in parser &1 whilst writing the field named &2 to the bitstream. 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 &3 into this field. User Response: You should check for other messages issued with this one for the full context of the error.

BIP6000-BIP6999 (MQSeries and NEON Parsers)

BIP6001E Cannot find MQSI_PARAMETERS_FILE environment variable. Explanation: In order to parse messages using the NEON parser, the MQSI_PARAMETERS_FILE environment variable must give the location of the parameters file giving the connection information for the database containing the NEON format definitions. User 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. BIP6002E Cannot open NEON parameters file &1. Explanation: In order to parse messages using the NEON parser, the MQSI_PARAMETERS_FILE environment variable must give the location of the parameters file giving the connection information for the database containing the NEON format definitions. User Response: Correct the value of the MQSI_PARAMETERS_FILE environment variable to contain the full path to the NEON parameters file. On an NT system it will be necessary to reboot the machine in order for the change to have any effect BIP6003E Error &1 : &2 connecting to NEON format database with session &3. Explanation: A database session could not be created using the specified session name, &3. The specific error was &1 : &2. User Response: Check that the NN_CONFIG_FILE_PATH environment variable is set, and that the directory to which it points contains a neonreg.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. BIP6004E Unsupported NEON control message received. 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. User Response: The broker can be shut down using the normal MQSeries Integrator 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 mqsinrfreload command. See the MQSeries Integrator Administration Guide for more details on both of these operations. BIP6005E NEON parser failed to process message: input format &1; error code &2; error text &3. Explanation: When processing the message using input format &1, NEON reported an error. The NEON error code was &2. The NEON error text was &3. User Response: See the NEON manuals for further information. BIP6007E Error connecting to NEON format database using session name &1. Explanation: A database session could not be created using the specified session name, &1. There was no

Chapter 2. Messages

111

BIP6008E BIP6048E
further information regarding the cause of the connection failure. User Response: Check that the NN_CONFIG_FILE_PATH environment variable is set, and that the directory to which it points contains a neonreg.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. BIP6008E Error parsing NEON parameters file &1 at column &3 on line &2. Explanation: The configuration file giving the database connection information for the NEON rules and format database was of an invalid format. The error occurred at column &3 on line &2. User 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 MQSeries Integrator 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 NEON database. BIP6009E Illegal modification of a NEON message. Explanation: Generating messages which have a NEON body using a Compute node is not supported. If the message did not originate from a Compute node, this message indicates an internal error. User Response: Rewrite the message flow so that it does not attempt to generate NEON messages from a Compute node. BIP6021E The RFH option buffer length was &1, however no name/value data was present. Explanation: The buffer length was &1, however no name/value pairs were found in the option buffer. User Response: Consult the support team responsible for the application generating the RFH messages. BIP6022E Name &1 has no associated value. Explanation: A name was found in the name/value option buffer with no associated value. User Response: Check the application that generated the message. BIP6041E Bitstream cannot be aligned to a 4-byte boundary in codepage &1. Explanation: The bitstream for this parser should be aligned on a 4-byte boundary. However after conversion to the requested codepage it was not possible to do so. User Response: Either change the codepage to an SBCS codepage or change the content of the message. BIP6042E End of message reached unexpectedly at offset &1. Explanation: The end of the message was encountered before the message was syntactically complete. User Response: Correct the application (or compute expression) that generated the message. BIP6043E Invalid folder size of &1 detected within an MQSeries RFH2 header. Explanation: MQSeries 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. User Response: Correct the application (or compute expression) that generated the message. BIP6044E Folder size of &1 exceeds the size of the message. Explanation: The folder size as given in the message would extend beyond the end of the message bitstream. User Response: Correct the application (or compute expression) that generated the message. BIP6045E Value at offset &1 must start with single or double quote: data just before error is &2; data just after error is &3. 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. User Response: Correct the application (or compute expression) that generated the message. BIP6046E Mismatched start and end tags at offset &1: data just before error is &2; data just after error is &3. Explanation: The RFH2 parser encountered an end tag that did not match the currently open start tag in the option buffer. User Response: Correct the application (or compute expression) that generated the message. BIP6047E Syntax error in attribute specification at offset &1: data just before error is &2; data just after error is &3. Explanation: The RFH2 parser expected an = following the attribute name at the offset indicated. User Response: Correct the application (or compute expression) that generated the message. BIP6048E Error occurred at offset &1 in the RFH2 option buffer. Explanation: An error occurred in the option buffer this message gives the location of the error in the option buffer. User Response: Correct the application (or compute expression) that generated the message.

112

MQSeries Integrator Messages

BIP6049E BIP6107E
BIP6049E A folder was nested incompletely at offset &1. 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. User Response: Correct the application (or compute expression) that generated the message. BIP6050W A folder had an incorrect name specification at offset &1. Explanation: There is a syntax error in the a folder at offset &1. A tag name was terminated with an invalid character. User Response: Correct the application (or compute expression) that generated the message. BIP6060I Parser type &1 created on behalf of node &4 to handle portion of incoming message of length &3 bytes beginning at offset &2. Explanation: The message broker has created a parser of type &1 on behalf of node &4 to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset &2 and &3 bytes long. User Response: No user action required. BIP6061I Parser type &1 created on behalf of node &5 to handle portion of incoming message of length &3 bytes beginning at offset &2. Parser type selected based on value &4 from previous parser. Explanation: The message broker has created a parser of type &1 on behalf of node &5 to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset &2 and &3 bytes long. This parser type was selected as the best match given the value &4 from the previous parser. User Response: No user action required. BIP6062W Invalid message body/header sequence &2/&1 encountered by node &3. Explanation: The message broker has encountered a message body of type &2 followed by a message header of type &1. It is not valid to have message headers following message bodies. User Response: Identify the source of the invalid message. BIP6101E An error has occurred in the &1 parser when reading a message. Explanation: The parser has encountered an error whilst trying to read a part of the message or message header. User 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 organisation responsible for the parser that detected the error. If this is an IBM supplied parser, you should contact your IBM support center. BIP6102E An error has occurred in parser &1 when generating the message. 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. User Response: Correct the application or compute expression that generated the element tree. BIP6103E Parser &1 has encountered an 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. User Response: Analyze the information contained in the following messages and act accordingly. BIP6104E Lack of system resources, broker failed to allocate memory. Explanation: An attempt to allocate memory was denied by the operating system. You should allocate more paging space before the broker is restarted. User Response: This is a fatal error and the broker needs to be restarted. BIP6105E The remaining bitstream is too small to contain an &1 structure. Explanation: The bitream, as presented to the &2 parser, is too small to contain a structure of type &1. The message appears to have been truncated. User Response: Check with the support group responsible for the parser in question. BIP6106E Length of parser field name &1 was &2. It should be &3. Explanation: The length of the value does not match the required length for the field. User Response: Correct the application (or compute expression) that generated the message. BIP6107E The value of field name &1 must be a boolean, its value was &2. Explanation: The type of the element must be boolean for field name &1. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository.

Chapter 2. Messages

113

BIP6108E BIP6121E
BIP6108E The value of field name &1 must be a byte string, its value was &2. Explanation: The type of element for this field must be a byte string. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6109E The value of field name &1 must be a character string, its value was &2. Explanation: The type of this element must be a character string for this field. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6110E The value of field name &1 must be a date, its value was &2. Explanation: The type of element for this field must be a date. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6111E The value of field name &1 must be a timestamp, its value was &2. Explanation: The type of element for this field must be a timestamp. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6112E The value of field name &1 must be a time, its value was &2. Explanation: The type of element for this field must be a time. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6113E The value of field name &1 must be an integer, its value was &2. Explanation: The type of this element must be an integer for this field. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6114E The value of field name &1 must be an interval, its value was &2. Explanation: The type of this element must be an interval for this field. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6115E Unconvertible field value for &1. Explanation: The element for a field could not be converted to the required type. User Response: Check the application (or compute expression) generating the message, and verify that the message agrees with any definition held in the message repository. BIP6116E Message broker internal program error. Explanation: An attempt was made to parse a message but no parse buffer was supplied. This is an internal error in the parser. User Response: Contact your IBM support center. BIP6117E Internal parser error. Explanation: An internal parser error has been detected. User Response: You should report this problem to the support organisation responsible for the parser that detected the error. If this is an IBM supplied parser, you should contact your IBM support center. BIP6118E The remaining bitstream is too small to contain the indicated structure. Explanation: The bitstream, as presented to the &2 parser, is too small to contain the &1 structure. The length of this structure as given in the structure header is &3. The message appears to have been truncated. User Response: Check with the support group responsible for the parser in question. BIP6119E The bitstream for &1 contained an unrecognised entity. Explanation: An & was found in the bitream but did not introduce a valid, recognised entity for substitution. User Response: Check with the support group responsible for the parser in question. BIP6121E Command and Response not valid for Type field of a parameter. 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. User 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

114

MQSeries Integrator Messages

BIP6122E BIP7013S
the source of the erroneous message. BIP6122E Parameter type of &1 for PCF headers is not handled by the PCF parser. Explanation: The parameter type specified is not valid when used in the command header. User Response: The message flow processing the message must be modified to avoid referencing or setting the contents of the MQSeries PCF header containg the unsupported parameter type. BIP6220I Parser class &1 already exists. Explanation: A plug-in parser factory has attempted to define a parser class, but a parser class of that name already exists. The request is rejected. User Response: Ensure that the parser class names do not clash.

BIP7000-BIP7999 (Publish Subscribe)

BIP7001E ACL already exists for topic &1 and principal &2. Explanation: The broker received a request to create an ACL which already exists. User 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 dont 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. BIP7002E ACL update error on topic &1 and principal &2. Explanation: An internal error caused the update on the ACL for topic &1 and principal &2 to fail. User Response: Verify that the topic and principal are correct and retry the operation. If the operation continues to fail, contact your IBM support center. BIP7003E Syntax error in topic &1. Explanation: The topic contains a syntax error. For example; there may be invalid characters or an illegal combination of wildcards. User Response: Refer to the online help for more information on allowable topics, correct the syntax error and repeat the operation. BIP7005E ACL not found for topic &1 and principal &2. Explanation: The ACL operation failed because there is no ACL for topic &1 and principal &2. User 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. BIP7006E No such principal &1. Explanation: The operation failed because principal &1 does not exist. User 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. BIP7007E Syntax error in filter &1. Explanation: There is a syntax error in the filter expression. User Response: Refer to the online help for more information on allowable SQL expressions, correct the syntax error and repeat the operation. BIP7008S Security not enabled. Explanation: The operation failed because security was not enabled. User Response: This is an internal error and you should contact your IBM Support center. BIP7009E Security policy violation - &1 &2 &3. Explanation: There was a violation of security policy or authorization was denied. User Response: Ensure that the user has the required authority to complete the operation and retry. BIP7011S Duplicate broker (queue manager &1). Explanation: The attempt to add a neighboring broker was unnecessary because the neighbor with queue manager &1 is already known. This could indicate that the Configuration Manager is in an invalid state. User Response: This is an internal error and you should contact your IBM support center. BIP7012S Duplicate connection to broker (queue manager &1) with id &2. Explanation: A connection with id &2 to broker (queue manager &1) was not created because it already exists. This could indicate that the Configuration Manager is in an invalid state. User Response: This is an internal error and you should contact your IBM support center. BIP7013S Unknown broker (queue manager &1). Explanation: The operation failed because the broker (queue manager &1) is unknown. User Response: This is an internal error and you should contact your IBM support center.

Chapter 2. Messages

115

BIP7014S BIP7024E
BIP7014S Unknown connection with id &2 to broker (queue manager &1). Explanation: The operation failed because the connection with id &2 to broker (queue manager &1) is unknown. User Response: This is an internal error and you should contact your IBM support center. BIP7015E Permission conflict &1. Explanation: The operation failed because of an attempt to set incompatible permissions &1. User 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. BIP7016E Native security system error &1. Explanation: A call has been made to the operating system and there has been a error code returned. User Response: Look up the error code in your operating system documentation, and correct the problem. If the problem persists, contact your IBM support center. BIP7017W Unknown user &1. Explanation: The user &1 was not found in the security information. User 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. BIP7018E Client (id &1) not registered. Explanation: An attempt was made to deregister a subscription registered by the client with id &1, but this subscription was not found, or some other error prevented the subscription being deregistered. User 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. BIP7019E Problem accessing the broker database for publish/subscribe function. 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. User 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. BIP7020S Start up failure &1. Explanation: Initialization of the Publication node failed. User Response: Check the system log for possible errors and restart the broker. BIP7021E Internal error in the publish/subscribe Matching Engine &1. Explanation: An internal error has occurred in the Matching Engine, recoverable work will be rolled back and then processing will continue. User Response: This is an internal error and you should contact your IBM support center. BIP7022S Problem removing expired subscription. 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. User Response: Check the error messages which precede this error to determine why the failure occurred, and take action as described by those messages. BIP7023S Subscription to topic &2 was not found for client &1. Explanation: During processing of a RegisterSubscriber or a RequestUpdate request the subscription which client &1 had for topic &2 could not be found. The broker will be terminated. User Response: This is an internal error. Contact your IBM support center. BIP7024E Cannot create or modify ACLs without access to information on users and groups. 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. User 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.

116

MQSeries Integrator Messages

BIP7025W BIP7053S
BIP7025W User does not have permission to subscribe to a topic: &1. Explanation: Authorization to subscribe or request an update on a topic has been denied. User Response: Ensure that the user has the required authority to complete the operation and retry. BIP7026W User does not have publish permission on a topic: &1. Explanation: Authorization to publish or delete a publication on a topic has been denied. User Response: Ensure that the user has the required authority to complete the operation and retry. BIP7027I User cannot receive a message because they do not have subscribe permission on a topic: &1. Explanation: Authorization to deliver a publication on a topic to a subscriber has been denied. User Response: If you require that the user should receive such publications, revise the appropriate group or user ACLs and retry. BIP7028W A Type Exception occurred in the publish/subscribe Matching Engine when processing a publication against a filter: &1. Explanation: The publish/subscribe Matching Engine encountered a mismatch in data types when driving a publication against a filter. User Response: Check the types of the subscription filters fields against those supplied in the corresponding publications and retry the operation. BIP7029W A Parsing Exception occurred when processing a published message to see if it matched a subscribers filter. Explanation: The publish/subscribe Matching Engine requested that a message be parsed in order to determine whether it matched a subscribers filter. The parsing operation was unsuccessful. User Response: See related messages. BIP7030E Publish/subscribe state recovery failed. 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. User Response: Check that the database is started and accessible, by using your database management tools. Investigate any error codes given in the message above in your database documentation. BIP7031I Publish/subscribe state recovery started due to transaction rollback. 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 brokers database. The available information is given above in other messages. Refer to earlier messages for the original cause of the transaction failure. User 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. BIP7032I Publish/subscribe state recovery started due to incorrect sequence number. Explanation: An internal publish/subscribe message has been received with an incorrect sequence number. This indicates that the brokers publish/subscribe state is inconsistent, and will be recovered from the brokers database. User 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. BIP7033I Publish/subscribe state recovery completed. Explanation: Recovery of the publish/subscribe state from the brokers database is complete. User Response: This message is for information only. No user action required. BIP7050S Failed to locate Java class &1. Explanation: The Java class &1 could not be found. User Response: This is an internal error and you should contact your IBM support center. BIP7051S Failed to locate Java method &1 in class &2. Explanation: The Java method &1 in class &2 could not be found. User Response: This is an internal error and you should contact your IBM support center. BIP7052S Failed to create Java object &1. Explanation: The Java object &1 could not be created. User Response: This is an internal error and you should contact your IBM support center. BIP7053S Unexpected Java exception &1. Explanation: An unexpected exception was thrown from Java code. The detail shows the Java stack trace where the exception occurred. User Response: This is an internal error and you
Chapter 2. Messages

117

BIP7054S BIP7066S
should contact your IBM support center. BIP7054S Unexpected null pointer for instance of class &1. Explanation: An unexpected null pointer exception was thrown from Java code on an object of class &1. User Response: This is an internal error and you should contact your IBM support center. BIP7055E Invalid attribute value &1 &2. Explanation: The attribute &1 had a value &2 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. User Response: If this error has occurred as a result of an action from the Control Center, it is an internal error and you should contact your IBM support center. Otherwise, correct the invalid value, then retry the operation. BIP7056E Attribute value not found or invalid &1. Explanation: The attribute &1 had no value or the value could not be determined. User Response: If this error has occurred as a result of an action from the Control Center, it is an internal error and you should contact your IBM support center. Otherwise, check the attribute has a valid value, then retry the operation. BIP7057E Invalid neighbor with queue manager &1. Explanation: The queue manager &1 could not be contacted for the purpose of sending publications between brokers. The connection has not been made. User Response: Ensure that the appropriate MQSeries 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. BIP7058S Failed to create message element &1. Explanation: While attempting to build a message, a failure occurred on creating element &1. User Response: This is an internal error and you should contact your IBM support center. BIP7059S Failed to navigate to message element &1. Explanation: While attempting to explore the contents of a message, an error occurred because the element &1 was missing or unreachable. User Response: This is an internal error and you should contact your IBM support center. BIP7060E Unexpected filter in RFH message. Explanation: A filter was found in an RFH message, for which filters are not supported. User Response: Review the message and remove the filter, then retry the operation. BIP7061S Invalid client identifier &1. Explanation: The client identifier &1 is incomplete or invalid. User Response: This is an internal error and you should contact your IBM support center. BIP7062S An invalid PCF message has been detected: diagnostic data &1. Explanation: An invalid PCF message has been detected. User Response: This is an internal error and you should contact your IBM support center. BIP7063S Not an RFH message. Explanation: The message was found not to be an RFH message while performing an operation only supported for RFH format messages. User Response: Ensure that the message sent for this operation has an RFH header and retry. BIP7064S Failed to create Java VM &1. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7065S Failed to attach thread to JVM. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7066S Failed to get the Java Native Interface pointer. 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. User Response: This is an internal error and you should contact your IBM support center.

118

MQSeries Integrator Messages

BIP7067E BIP7080I
BIP7067E Caught exception while deleting message flow &1 &2. Explanation: There was a problem while attempting to delete the named message flow. User Response: This is an internal error and you should contact your IBM support center. BIP7069S Tried to create two instances of &1 where only one is allowed. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7071E Message (of type &2) on incorrect queue &1. Explanation: An application put a message of type &2 on queue &1. This queue is not intended for messages of that type and the message was not processed. User 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. BIP7072E Neighbor (queue manager &1) is already an MQSeries publish/subscribe neighbor. Explanation: An attempt has been made to join this broker with an MQSeries Integrator broker on queue manager &1. This request was unsuccessful because the broker is already joined as an MQSeries publish/subscribe neighbor. User Response: If queue manager &1 is an MQSeries Integrator broker then it can only be joined to this broker when the MQSeries publish/subscribe link has been removed. This can be achieved using the mqsiclearmqpubsub command. BIP7073S Invalid publisher event message received in subordinate process. 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. User 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. BIP7074E Exception &2 condition detected while recovering client &1 from the database. Explanation: An exception condition was detected in the message broker when trying to recover a client from the database. User Response: This is an internal error and you should contact your IBM support center. BIP7075E Unable to find client id &1 for subscription registered to topic &2. Explanation: While trying to recover the subscriptions a matching client id could not be found. User Response: This is an internal error and you should contact your IBM support center. BIP7076E Unable to find client id &1 for publisher registered to topic &2. Explanation: While trying to recover the publisher a matching client id could not be found. User Response: This is an internal error and you should contact your IBM support center. BIP7077S Unable to start DynamicSubscriptionEngine. Explanation: The message broker was unable to start the DynamicSubscriptionEngine. See the following messages for details of the error. User Response: If the error persists contact your IBM support center. BIP7078S Failed to detach thread from the JVM. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7079I Node &2: The publish/subscribe service has received a message of type &1. Explanation: The publish/subscribe service has started processing a control message. User Response: No user action required. BIP7080I Node &3: The Publication node with Subscription Point &2 has received a message of type &1. Explanation: The Publication node with Subscription Point &2 has started processing a message. User Response: No user action required.

Chapter 2. Messages

119

BIP7081I BIP7092E
BIP7081I The Publication node has matched &1 subscriptions to topic &2 for subscription point &3. Explanation: The Publication node has matched subscriptions for the current publication and topic. User Response: No user action required. BIP7082I Node &3: Publishing to destination &1 for user &2. Explanation: A publication destination is being added to the list of destinations to &1 for user &2. User Response: No user action required. BIP7083I Node &3: The Publication node with Subscription Point &2 has received an error code &1. Explanation: The Publication node with Subscription Point &2 has received an error with code &1. A response message has been sent to the originators reply queue. User Response: No user action required. BIP7084I Node &2: The publish/subscribe service has received an error code &1. Explanation: The publish/subscribe service has received an error with code &1. A response message has been sent to the originators reply queue. User Response: No user action required. BIP7085I Node &2: The Publication node has propagated a message to its Output terminal for subscription point &1. Explanation: The Publication node has propagated the current message to its Output terminal. User Response: No user action required. BIP7086I Node &3: The Publication node with Subscription Point &2 has received an error code &1. Explanation: The Publication node with Subscription Point &2 has received an error with code &1. No response message has been sent as one was not requested. User Response: No user action required. BIP7087I Node &2: The publish/subscribe service has received an error code &1. Explanation: The publish/subscribe service has received an error with code &1. No response message has been sent because one was not requested. User Response: No user action required. BIP7088W publish/subscribe configuration request &1 cannot be processed until after MQSeries publish/subscribe migration has completed. Explanation: The broker has been created as a replacement for an existing MQSeries publish/subscribe broker. Until all subscriptions and retained publications have been successfully migrated into the MQSeries Integrator broker it is not possible to deploy any new publish/subscribe configuration changes. User Response: Redeploy the configuration changes after migration has completed successfully. BIP7089S Publish/subscribe migration logic error. Explanation: The broker has been created as a replacement for an existing MQSeries publish/subscribe broker. A logic error has been detected which has caused the broker to terminate. User Response: This error should be reported to your IBM support center. Until the problem is corrected you can continue to use your existing MQSeries publish/subscribe broker. BIP7090I Configuration Managers subscription cannot be processed at this time. Explanation: The broker has been created as a replacement for an existing MQSeries 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. User 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. BIP7091E Caught exception &3 while deregistering subscriptions for client id &1: error code &2. Explanation: There was a problem while attempting to deregister all subscriptions for a client. User 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. BIP7092E Problem removing expired retained publication. 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. User Response: Check the error messages which

120

MQSeries Integrator Messages

BIP7093E BIP7104S
precede this error to determine why the failure occured, and take action as described by those messages. BIP7093E Attribute style properties not allowed in publish/subscribe message. 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 MQSeries Integrator Programming Guide, for more information and examples. User Response: Change the application which generated the message to use syntax as described above. BIP7094W Exception condition detected while sending deferred message of type &1. Failure count is &2. Explanation: The publish/subscribe service detected an error whilst sending a deferred message of type &1, 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 &2. 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. User Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. BIP7095E Requested response cannot be sent for non-RFH message. 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. User 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. BIP7101S Could not access MQConnectionManager resource. Explanation: The DynamicSubscriptionEngine, implemented in imbdfjps.lil, requires the presence of the MQSeries library, imbdfmqm.lil. This library is either missing or invalid. Other messages may indicate the reasons for the failure to load imbdfmqm.lil. User Response: Ensure that imbdfmqm.lil is valid and in the correct location. Check other messages for reasons why imbdfmqm.lil might not have loaded. BIP7102W Requesting broker &1 has inconsistent queue manager value &2. Explanation: A broker (identified by its UUID &1 and queue manager &2) 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. User 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. BIP7103W Requesting broker &1 (queue manager &2) is currently unknown. Explanation: A broker (identified by its UUID &1 and queue manager &2) 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. User 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. BIP7104S Interbroker message flow &1 not found. Explanation: The message flow &1 dedicated to serving interbroker function was not found. User 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.

Chapter 2. Messages

121

BIP7105S BIP7201S
BIP7105S Interbroker node not found in message flow &1. Explanation: An attempt was made to locate the Interbroker node within message flow &1. This message flow is internally created and managed by the broker. This is an internal error. User 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. BIP7106W Accepting broker &1 (queue manager &2) is currently unknown. Explanation: A broker (identified by its UUID &1 and queue manager &2) 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. User 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), re-establish the broker topology by redeploying. If the problem persists, contact your IBM support center. BIP7112W Requesting broker (UUID &1, queue manager &2) has an incorrect value &3 for this brokers UUID, which is &4. 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 brokers 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. User 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. BIP7113I Interbroker connection established with neighbor (queue manager &1). Explanation: A connection has been established with neighboring broker (queue manager &1) for the purposes of sending publications between the brokers. User Response: This message is for information only, to confirm that the interbroker connection has been made successfully. BIP7114I Interbroker connection ended with neighbor (queue manager &1). Explanation: An active connection has been ended with the neighboring broker (queue manager &1). Publications will not flow between the brokers until the connection is reestablished. User Response: This message is for information only, to confirm that the connection has been ended. BIP7115S Failure to create message flow for neighboring broker: error code &1. Explanation: An attempt to create a message flow to connect to a neighboring broker was unsuccessful. User Response: This is an internal error and you should contact your IBM support center. BIP7116S Failure to modify message flow for neighboring broker: error code &1. Explanation: An attempt to modify a message flow to connect to a neighboring broker was unsuccessful. User Response: This is an internal error and you should contact your IBM support center. BIP7150E Userid &3 not authorized to put to queue &2 on queue manager &1 using accounting token &4. Explanation: The user is not authorized to put a message on the named queue. User Response: Ensure the user is allowed to perform this operation. This may involve configuring the MQSeries settings for this queue, or using an alternative userid which is authorized. BIP7151S Tried to create two publish/subscribe user/group data stores. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7201S Tried to create two PubSubResources. 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. User Response: This is an internal error and you should contact your IBM support center.

122

MQSeries Integrator Messages

BIP7202S BIP7260W
BIP7202S Invalid tag &1. Explanation: A tag (&1) found in a configuration message was not understood. User Response: This is an internal error and you should contact your IBM support center. BIP7203S Missing tag &1. Explanation: A &1 tag in a configuration message was expected, but not found. User Response: This is an internal error and you should contact your IBM support center. BIP7204S Exception while creating &1 message flow &2. Explanation: A problem occurred while trying to create a &1 type of message flow. The exception detail was &2. User Response: This is an internal error and you should contact your IBM support center. BIP7205S Attribute &1 of tag &2 missing from the configuration message. Explanation: The configuration message is invalid. The attribute &1 is required for the &2 tag. User Response: This is an internal error and you should contact your IBM support center. BIP7250S Unexpected message received on MQSeries publish/subscribe interbroker communications queue &1: PutApplName &2; additional diagnostic data &3. Explanation: The broker has read a message from a queue used by the broker to receive messages from MQSeries 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. User 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 &1 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. BIP7251S Invalid state &2 detected for MQSeries publish/subscribe neighbor &1 whilst processing control message of type &3. Explanation: This is an internal error within the broker. User Response: Keep all diagnostic information contained within this message and contact your IBM support center. BIP7252S Failed to map &1 parameter/value &2. Explanation: This is an internal error within the broker. User Response: Keep all diagnostic information contained within this message and contact your IBM support center. BIP7255S MQSeries publish/subscribe broker &1 is already a neighbor. Explanation: An internal error has occurred while adding MQSeries publish/subscribe broker &1 as a neighbor. Broker &1 is already a neighbor. User Response: Contact your IBM support center. BIP7256S MQSeries publish/subscribe broker &1 is not a neighbor. Explanation: An internal error has occurred within the broker which has resulted in an attempt to remove an MQSeries publish/subscribe broker which is not a neighbor. User Response: Contact your IBM support center. BIP7257S MQSeries publish/subscribe neighbor &1 state &2 unsuitable to be made active. Explanation: An internal error has occurred within the broker which has resulted in an attempt to activate an MQSeries publish/subscribe broker which not in a valid state. User Response: Contact your IBM support center. BIP7258W A message has been received from unknown MQSeries publish/subscribe broker: link identifier &1. Explanation: A message was received from an MQSeries publish/subscribe broker which is not known to this broker. A failure response will be sent to the sending broker. User Response: No user action required. BIP7259E Message broker &1 has failed to import a migrated subscription: diagnostic information &2, &3. Explanation: The migmqbrk command has been issued to migrate an MQSeries publish/subscribe broker. The message broker has failed to import a subscription. The diagnostic information associated with this error is &2 and &3 User Response: Contact your IBM support center. BIP7260W Message broker &1 already has a parent MQSeries publish/subscribe broker &2. Explanation: The mqsijoinmqpubsub command has been used to join this message broker to a MQSeries publish/subscribe broker. This broker already has a parent broker so the command has been rejected.
Chapter 2. Messages

123

BIP7261E BIP7268W
User Response: Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with. BIP7261E An invalid control message from an MQSeries publish/subscribe neighbor has been detected: diagnostic information &1, &2. Explanation: This is an internal error. User Response: Contact your IBM support center. BIP7262E An MQSeries publish/subscribe control message intended for broker &2 has been detected: diagnostic information &1. Explanation: This is an internal error. User Response: Contact your IBM support center. BIP7263W Unexpected communication received from MQSeries publish/subscribe broker &1. Explanation: The broker has received an inter-broker communication from an MQSeries publish/subscribe broker that it did not expect. The message was sent by broker &1. 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. User 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 &1 from this broker, the clrmqbrk command should also be used at broker &1 to remove knowledge of this broker. BIP7264W Message broker could not send completion code &1 to a command line request. 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 non-zero completion code means that the request failed or was rejected by the message broker. User Response: Look for a previous error message, usually BIP2623, outlining the cause of the problem. If message BIP2623 reports an MQSeries 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 MQSeries Application Programming Reference manual. BIP7265E Bad data returned from MQSeries publish/subscribe database table: diagnostic information &1, &2. Explanation: This is an internal error within the broker. User Response: Keep all diagnostic information contained within this message and contact your IBM support center. BIP7266E Invalid MQSeries publish/subscribe migration message detected on queue &3: diagnostic information &1, &2. Explanation: The message broker has been processing migration messages arriving on a queue as a result of the migmqbrk command being issued against an MQSeries publish/subscribe broker. The message broker has detected an invalid message on this queue. User 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 MQSeries and MQSeries Integrator traces will help with problem resolution. BIP7267S Invalid MQSeries publish/subscribe control message detected on queue &3: diagnostic information &1, &2. Explanation: The message broker has been processing messages on a queue. Messages are sent to the queue by neighboring MQSeries 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 on to the dead letter queue. User 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 backout threshold for the queue which will cause the invalid message to be put on to the dead letter queue. From here the message can be captured by running the MQSeries 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. BIP7268W MQSeries publish/subscribe broker &1 is not known by this message broker. Explanation: The mqsiclearmqpubsub command has been used to remove MQSeries publish/subscribe broker &1. This broker is not known by this message broker so the command has been rejected.

124

MQSeries Integrator Messages

BIP7269W BIP7277E
User Response: Reissue the mqsiclearmqpubsub command specifying the correct broker to be removed. BIP7269W MQSeries publish/subscribe broker &1 is already known by this message broker. Explanation: The mqsijoinmqpubsub command has been used to join this message broker to MQSeries publish/subscribe broker &1. This broker is already known so the command has been rejected. User Response: Reissue the mqsijoinmqpubsub command specifying the correct broker to be joined with. BIP7270W Attempt to join with parent MQSeries publish/subscribe broker &1 failed because a parent &2 already exists. Explanation: The mqsijoinmqpubsub command has been used to join this message broker to MQSeries publish/subscribe broker. The attempt has been rejected because the message broker already has a parent broker. User Response: The message broker can only be joined to a single parent MQSeries 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 MQSeries publish/subscribe broker. BIP7271W Loop joining message broker &1 to MQSeries publish/subscribe broker &2. Explanation: The mqsijoinmqpubsub command has been used to join a message broker to a parent MQSeries publish/subscribe broker. The action has caused a loop to created in the MQSeries publish/subscribe hierarchy. User Response: Use the mqsiclearmqpubsub at the broker and clrmqbrk at the MQSeries publish/subscribe broker to remove the loop from the hierarchy. BIP7272I MQSeries publish/subscribe migration has started for message broker &1. Explanation: The migmqbrk command has been issued to start migration of a MQSeries publish/subscribe broker. User Response: No user action required. A further message will be issued when the migration has finished. BIP7273I MQSeries publish/subscribe migration has completed successfully for message broker &1. Explanation: The migration of the MQSeries publish/subscribe broker has been successful. User Response: All subscriptions, retained publications and local publisher registrations have been loaded into message broker &1. 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 MQSeries publish/subscribe broker. Guidance for this task can be found in the MQSeries Integrator Introduction and Planning guide. BIP7274E MQSeries publish/subscribe migration has failed for message broker &1 with reason code &2. Explanation: An attempt has been made to migrate an MQSeries publish/subscribe broker. This has failed with a reason code of &2. User Response: Investigate the reason for the failure. Look for previous messages issued by message broker &1 and also look for any MQSeries messages issued by the 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. BIP7275E Unexpected message of type &2 received from MQSeries publish/subscribe broker &1. Explanation: A unexpected message has been received from a neighboring MQSeries publish/subscribe broker. User Response: This is an internal error and you should contact your IBM support center. BIP7276E MQSeries Integrator broker has failed to join with MQSeries publish/subscribe broker &1 for reason &2. Explanation: The mqsijoinmqpubsub command has been issued to join with MQSeries publish/subscribe broker &1. The MQSeries Integrator broker attempted to register as a child of the MQSeries publish/subscribe broker but received an exception response indicating that this was not possible. User 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. BIP7277E MQSeries Integrator broker has failed to subscribe to MQSeries publish/subscribe broker &1. Reason codes &2 and &3. Explanation: The strmqbrk command has been issued at MQSeries publish/subscribe broker &1 nominating this MQSeries Integrator broker as its parent. While handling the resultant join request the MQSeries Integrator broker sent an internal subscription to the admininstration stream of broker &1. The subscription
Chapter 2. Messages

125

BIP7278E BIP7283I
failed and as a result the two brokers are not yet joined together. The broker will reissue the subscription immediately. User 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 &1, or a problem with the definition of route between this broker and broker &1. 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 &1 and the mqsiclearmqpubsub command at this broker. BIP7278E MQSeries Integrator broker has failed to propagate a subscription to MQSeries publish/subscribe broker &1. Reason codes &2 and &3. Explanation: An application has either registered or deregistered a global subscription. The broker has attempted to propagate the subscription change to MQSeries publish/subscribe broker &1 but the request has not been successful. The MQSeries Integrator broker will immediately attempt to refresh the state of all global subscriptions at broker &1. Until the subscription state has been successfully refreshed, messages published through broker &1 might not reach this broker. User 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 &1, or a problem with the definition of route between this broker and broker &1. When the problem has been rectified, this error message will no longer be issued. BIP7279W MQSeries Integrator broker failed to inform parent MQSeries publish/subscribe broker &1 of a new broker for reason &2. Explanation: When a new broker is added to an MQSeries 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 MQSeries Integrator broker has failed to notify its parent on queue manager &1 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. User 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. BIP7280E Message broker failed to propagate a delete publication command on topic &3 to MQSeries publish/subscribe broker &1 for reason &2. Explanation: When an application issues a delete publication command to delete a global publication, the command is propagated to all neighboring MQSeries publish/subscribe brokers. The delete publication command has failed to be forwarded from the broker, and as such the retained publication on the topic will not have been deleted. User 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. BIP7281W Request &1 from MQSeries publish/subscribe broker &3 contains an invalid topic &2. Explanation: The broker has received a request from neighboring a MQSeries publish/subscribe broker. The request contained an invalid topic and will be ignored. User Response: In a mixed network of MQSeries Integrator and MQSeries 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 MQSeries publish/subscribe network need to be modified to use topics which do not contain characters which are invalid to the MQSeries Integrator broker. BIP7282W mqsijoinmqpubsub command from broker &1 rejected because it named an MQSeries Integrator broker &2 instead of an MQSeries publish/subscribe broker as parent. Explanation: The command mqsijoinmqpubsub named an MQSeries publish/subscribe broker as its parent. This has been rejected because the named broker is an MQSeries Integrator broker. The two brokers have not been joined together. User Response: Use the Control Center to join the two MQSeries Integrator brokers together. BIP7283I Message broker is waiting for MQSeries publish/subscribe migration. Explanation: The broker has been created in migration mode. No publication message flows should be created until migration has completed successfully. User Response: Use the migmqbrk command to migrate the MQSeries publish/subscribe broker. If the broker has been created incorrectly, the broker will need to be deleted and recreated.

126

MQSeries Integrator Messages

BIP7284W BIP8007E
BIP7284W MQSeries publish/subscribe inter-broker queue &1 cannot be accessed. Explanation: The broker has MQSeries publish/subscribe neighbors. These neighbors communicate with this broker using queue &1. The queue cannot be accessed which will affect inter-operability with all MQSeries publish/subscribe neighbors. User Response: Check whether queue &1 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 MQSeries publish/subscribe neighbors. If the queue does not exist, consult the MQSeries Integrator 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. BIP7285W Subscription to topic &1 will not be propagated to MQSeries publish/subscribe neighbors. Explanation: A subscription to topic &1 has been received. This will not be propagated to any of the MQSeries publish/subscribe neighbors of this broker. User Response: You can ignore this message if the client making the subscription to topic &1 is not interested in any potential matching publications made within the MQSeries 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 MQSeries Integrator Introduction and Planning guide for more information about using wildcard subscriptions in a mixed broker network. BIP7350S Tried to create two data flow stores. 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. User Response: This is an internal error and you should contact your IBM support center. BIP7351W No data source supplied, so data flow configuration will not be persistent. Explanation: The start up parameters for the broker did not include a database name, so this configuration will not be saved anywhere. User Response: If persistence is required, ensure a database name is provided in the start up parameters for the broker. BIP7352W Some (but not all) tables exist, publish/subscribe state will not be persistent. Explanation: Some of the tables the broker requires in the database were missing so the broker state will not be saved anywhere. User Response: The database may need to be rebuilt. BIP7353S Tried to access a non-existent data flow store. Explanation: An attempt was made to read from or write to a database that has not been properly initialized. User Response: Examine the system log for indications of a start up failure.

BIP8000-BIP8199 (Commands)
BIP8001E Unknown flag selected. Explanation: When using this command interface the user should only select the supported flags. User Response: Correct and reissue the command. BIP8002E Selected flags incompatible. Explanation: When using this command interface the user should only select the supported flags. User Response: Correct and reissue the command. BIP8003E Duplicate flag detected. Explanation: A flag was selected more than once. User Response: Correct and reissue the command. BIP8004E Invalid flags and/or arguments selected. Explanation: When using this command interface the user should only select supported flags. User Response: Correct and reissue the command. BIP8005E Command flag or argument missing. Explanation: The command will result in no action being taken, a required flag or a flags argument is missing. User Response: Correct and reissue the command. BIP8006E Mandatory flag missing. Explanation: When using this command interface the user should select all mandatory flags. User Response: Correct and reissue the command. BIP8007E Mandatory argument missing. Explanation: When using this command interface the user should supply the mandatory argument. User Response: Correct and reissue the command.
Chapter 2. Messages

127

BIP8008E BIP8022E
BIP8008E Unable to create the Java environment. Explanation: The Java environment could not be created. User 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. BIP8009E Program name incorrect. Explanation: Ensure that the program name (executable) has not been modifed. User Response: Correct and reissue the command. BIP8010E No broker name supplied. Explanation: This command requires a broker name to be supplied. User Response: Correct and reissue the command. BIP8011E Unable to create the components configuration data. Explanation: The command is unable to store the components configuration data. User 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. BIP8012E Unable to connect to system components. Explanation: This command was unable to connect to required system services. User 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. BIP8013E Component does not exist. Explanation: A component may only be used if it has first been created. User Response: No user action required. BIP8014W Component could not be created. Explanation: Unable to create the component, the required resources were unavailable. User 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. BIP8015E The component cannot be started. Explanation: The command could not start the required component. User 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. BIP8016E Unable to stop component. Explanation: A request to stop this component was refused. User 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. BIP8017E The component could not be deleted. Explanation: Ensure that the component is in a valid state to be deleted. User 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. BIP8018E Component running. Explanation: This component is running, the command issued cannot be run against a running component. User Response: Stop the component and reissue the command. BIP8019E Component stopped. Explanation: A previous command was issued to stop this component or it has never been started. User Response: This component may be started, changed or deleted. BIP8020E Unable to access the brokers database tables. Explanation: This command interacts with the brokers database tables using the database userid selected for this component. User 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. BIP8021E Ensure that the userid and/or password supplied are correct. Explanation: Ensure that the password is valid and that the userid is defined. User Response: Correct and reissue the command. BIP8022E Invalid service userid and password combination supplied. Explanation: The userid/password pair are not correct. User Response: Correct and reissue the command.

128

MQSeries Integrator Messages

BIP8023E BIP8035E
BIP8023E A valid password must be supplied. 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. User Response: Correct and reissue the command. BIP8024E Unable to locate the components executable. Explanation: The components executable is not in the expected directory. User Response: Ensure that the product has not been moved from its installation directory. Check that executable bipservice is in the products \bin directory. BIP8025E Component disabled. Explanation: The component should not be in a disabled state. The component could not be started. User Response: Investigate why the component is disabled and correct the problem, on Windows NT this may be because the components service was disabled. BIP8026E Unable to start the component. Explanation: The component could not be started using the service userid that was supplied when the component was created. User 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). BIP8027E Unable to start MQSeries. Explanation: MQSeries Integrator requires that MQSeries is installed and its service is available. User Response: On NT the MQSeries service must be available before the MQSeries Integrator component can be started. The MQSeries service was unable to start, correct the problem and reissue this command. BIP8028E Required product unavailable. Explanation: MQSeries Integrator requires that MQSeries is installed and that its service MQSeriesServices is available. User Response: Ensure that MQSeries is installed. BIP8029E The brokers configuration is not yet deployed. 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 Control Center. User Response: Reissue the command after the brokers configuration has been deployed. BIP8030E Unable to modify userid privileges. Explanation: On NT this command modifies a userids privileges, (logon as service). User Response: Ensure that the userid issuing this command has sufficient privileges to modify the privileges of the userid supplied in the command. BIP8031E Invalid flag argument supplied. Explanation: Ensure that the correct flag arguments are selected. User Response: Correct and reissue the command. BIP8032E Unable to connect to an MQSeries queue. Explanation: An attempt was made to connect to the components MQSeries queue manager and queue, this attempt was unsuccessful. User Response: Ensure that the components MQSeries queue manager and queue are available, running and that the user has sufficient authority to access them. BIP8033E Unable to send an internal configuration message to the broker. Explanation: This command was unable to send an internal configuration message to the broker using MQSeries. User Response: Ensure that MQSeries is installed and that the broker and its queue manager are running. BIP8034E An internal configuration response message not received. Explanation: This command sends an internal configuration message to the broker, a internal configuration response message was not received from that broker. User Response: Ensure that the broker and its MQSeries queue manager are running. BIP8035E 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. 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. User Response: Investigate why the internal configuration response message was not received within this period. Check the system log messages and ensure that your MQSeries 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.

Chapter 2. Messages

129

BIP8036E BIP8049E
BIP8036E Negative response received. Explanation: This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful. User Response: Check that the MQSeries transport is available. Check the system log for further information. BIP8037E Unsupported flag selected. Explanation: When using this command interface the user should only select from the set of supported flags. User Response: Check the list of supported flags, correct and then reissue the command. BIP8038E An invalid combination of options was selected. Explanation: The command specified represents an invalid combination of options and parameters. User Response: Refer to the MQSeries Integrator Administration Guide for the list of valid options for this command. Correct and reissue the command. BIP8039E Execution group not available. Explanation: Execution groups may be deleted by the Control Center at any time. User Response: Check to see if the execution group selected exists. BIP8040E Unable to connect to the database. Explanation: The database cannot be accessed with the userid and password that were specified when the broker was created. User Response: Check that the database is running, that an ODBC connection has been created and that the userid and password pair specified for ODBC connect on the mqsicreate command are capable of being used to connect to the database using an ODBC connection. BIP8041E Unable to open the selected file &1. Explanation: The file selected could not be opened for read or write. User Response: Ensure that the file used for input exists, that the file specified as input is not also the file specified for output. Also ensure that the file is not locked by another user. BIP8042E Insufficient memory. Explanation: This command requires a significant amount of memory. User Response: Ensure that there is enough memory available to execute the command. BIP8043E File selected was not a broker trace file. Explanation: Broker trace files have an XML tag indicating that they are trace files. User Response: Repeat the trace extraction and reissue the command. BIP8044E Unable to get the message text for MQSI command response &1. 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. User Response: Contact your IBM support center. BIP8045E Message flow not available. Explanation: Message flows may be deleted by the Control Center at any time. User Response: Check to see if the message flow selected exists. BIP8046E Unable to initialize parser data, exception caught &1. Explanation: The command initializes parser functions prior to analysing 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. User Response: Contact your IBM support center. BIP8047E Unable to parse the data received, exception caught &1. Explanation: The command uses parser functions to analyse 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. User 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. BIP8048E Unable to start MQSeries queue manager &1. Explanation: This command attempts to start an MQSeries queue manager, the queue manager could not be started. User Response: Locate and resolve the problem and retry the command. BIP8049E Unable to stop MQSeries queue manager &1. Explanation: This command attempts to stop an MQSeries queue manager, the queue manager could not be stopped. User Response: Locate and resolve the problem and retry the command.

130

MQSeries Integrator Messages

BIP8050E BIP8060E
BIP8050E Unable to create MQSeries queue manager &1. Explanation: This command attempts to create an MQSeries queue manager, the queue manager could not be created. User Response: Locate and resolve the problem and retry the command. BIP8051E Unable to create MQSeries queue &1 on queue manager &2. Explanation: This command attempts to create an MQSeries queue but was unable to do so. User Response: Locate and resolve the problem and retry the command. BIP8052E Unable to delete MQSeries queue &1 from queue manager &2. Explanation: This command attempts to delete an MQSeries queue but was unable to do so. User Response: Locate and resolve the problem and retry the command. This could be because an MQSeries channel is still running. If this is the case, stop all MQSeries channels running on behalf of this queue manager. BIP8053E Unable to set the security attributes for MQSeries queue manager &1. Explanation: This command attempts to set the Group security attributes for an MQSeries queue manager. User Response: Ensure that the required Group (mqbrkrs) is available and that the user issuing this command is a member of the mqm group. BIP8054E Unable to set the security attributes for MQSeries queue &1 on queue manager &2. Explanation: This command attempts to set the group security attributes for an MQSeries queue. User Response: Ensure that the required group (mqbrkrs) is available and that the user issuing this command is a member of the mqm group. BIP8055E Unable to load a Java class or method &1. Explanation: This command attempts to use a Java class or method, but was unable to run the class or method. User Response: Ensure that the required Java archives (jar files) are in the brokers classes directory. BIP8056E The components MQSeries queue manager &1 does not exist. Explanation: The command cannot be executed because the queue manager associated with this component does not exist. User 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. BIP8057E The command has failed because of an unexpected queue manager error. Explanation: During execution of the command an unexpected response has been returned from an MQI call. User Response: A message containing further details of the failure will have been issued to your system log. Consult this message for problem resolution. BIP8058E A command has failed because of an unexpected MQSeries failure. A &1 request against object &2 has failed with reason code &3. Explanation: A command has been issued but during execution of the command an unexpected MQSeries failure was returned from MQI call &2. User Response: Using reason code &3, consult the MQSeries Application Programming Reference manual to establish the cause of the failure. Take appropriate action to correct the problem before reissuing the command. BIP8059E Command has failed because the brokers queue manager is not available. Explanation: The command has failed because the queue manager associated with the broker is currently unavailable. User Response: Reissue the command after the queue manager has been restarted. BIP8060E Command has failed because of problem with queue SYSTEM.BROKER.INTER.BROKER. COMMUNICATIONS. 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. User Response: First check whether the queue exists or not. If not, consult the MQSeries Integrator 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.

Chapter 2. Messages

131

BIP8061E BIP8074E
BIP8061E Broker has failed to reply to command. 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. User Response: Investigate why the broker failed to respond to the request. If the broker has terminated, restart it and reissue the command. BIP8062E Join request has failed because parent broker is already a neighbor. Explanation: The mqsijoinmqpubsub command has failed because the named parent broker is already a neighbor. User 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. BIP8063E Clear request has failed because specified broker is not a neighbor. Explanation: The mqsiclearmqpubsub command has failed because the named broker was not a neighbor. User Response: Reissue the command specifying a broker which is a neighbor. BIP8064E Command has failed because of an internal broker error Explanation: The command has failed because of an internal error at the broker. User Response: A message containing the further details of the failure will have been issued to the system log. Consult this message for problem resolution. BIP8065E Join request has failed because broker already has a parent. Explanation: The mqsijoinmqpubsub command has failed because the message broker already has a parent MQSeries publish/subscribe broker. User Response: Remove the existing parent broker before reissuing the command. BIP8066E Request has failed because an invalid broker name was specified. Explanation: The mqsijoinmqpubsub or mqsiclearmqpubsub command has failed because the MQSeries publish/subscribe broker name supplied was invalid. User Response: Reissue the command with a valid MQSeries publish/subscribe broker name. BIP8067E Request has failed because couldnt contact the parent MQSeries publish/subscribe broker. Explanation: The mqsijoinmqpubsub command has failed because the supplied MQSeries publish/subscribe broker could not be contacted. User 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 MQSeries Integrator broker. Correct the underlying problem with the MQSeries network and reissue the command. BIP8068E Argument &1 is not a valid integer value. Explanation: Ensure that the argument used is a valid integer and in the allowable range. User Response: Correct and reissue the command. BIP8069E Unable to find message &1 in message catalog &2. Explanation: A message could not be found in the message catalog specified. User Response: Ensure that the message is available in the message catalog and that the catalog is in the product message directory. BIP8070E Exception accessing database table executing SQL statement &1: SQL state &2; exception &3. Explanation: An SQL command has failed. User Response: Ensure that the brokers database is available. Examine the exception and SQL state code to determine and correct the cause of the error. BIP8071I Successful command completion. Explanation: User Response: BIP8072E Exception accessing a database table, executing SQL statement &1: exception &2. Explanation: An SQL command has failed. User Response: Ensure that the database is available, examine the exception to determine and correct the cause of the error. BIP8073E &1 is not a valid broker name. Explanation: The broker name selected is not allowed because it is reserved. User Response: Select a different broker name. BIP8074E Unable to create a JVM. Explanation: A Java Virtual Machine could not be created. User 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.

132

MQSeries Integrator Messages

BIP8075E BIP8086E
BIP8075E A Java exception was caught from class &1. The text is &2. Explanation: A Java exception was caught via the JNI. User Response: Check preceding messages for related errors and retry the operation. If the exception still occurs, contact your IBM support center. BIP8076E Current working directory could not be set to &1. Explanation: A problem was encountered while attempting to create/delete the Configuration Manager database tables. The current working directory could not be set. This action is necessary for the database operation to succeed and as a result the operation was not successful. User Response: Check messages in the system log for related errors and retry the operation. If the problem still occurs, contact your IBM support center. BIP8077E A problem was encountered while attempting to create/delete the Configuration Manager. Explanation: The operation was not completed successfully. An internal error generated an invalid return code of &1. User Response: Check messages in the system log for related errors and retry the operation. If the problem still occurs contact your IBM support center. BIP8078E A problem was encountered while attempting to create/delete the Configuration Manager. Explanation: The operation was not completed successfully. This error is symptomatic of a java CLASSPATH problem. User Response: Check messages in the system log for related errors. Check to see if a product has been installed recently that may have altered the CLASSPATH, if so, ensure that CLASSPATH is restored to at least its previous setting. This product relies on MQSeries JAR and ZIP files being available via the CLASSPATH, there may also be database specific JAR and ZIP files that are required. Retry the operation. If the problem still occurs, contact your IBM support center. BIP8079E Unable to find service user ID &1. Explanation: This user ID is not defined to the operating system, so it cannot be used as a broker service user ID. User Response: Create the user ID and reissue the mqsicreatebroker command, or reissue the mqsicreatebroker command specifying a user ID which does exist on this system. BIP8080E Unable to initialize a parser factory. Explanation: The command executable detected an error whilst initializing its parser factory. User Response: Contact your IBM support center. BIP8081E An exception &1, was caught while processing the command. Explanation: An unexpected exception occurred while the command was running. The command has cleaned up and terminated. User 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 :- Is your userid in the mqbrkrs group? Is the broker database working? Is any operating system limit set too low to allow the command to run? Is the environment correctly setup? Contact your IBM support center if you are unable to resolve the problem. BIP8082E Unable to delete MQSeries queue manager &1. Explanation: This command attempts to delete an MQSeries queue manager, but the queue manager could not be deleted. User Response: This could be because an MQSeries channel is still running. Stop all MQSeries channels running on behalf of this queue manager then retry the command. BIP8083E The component name supplied contains invalid characters. 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. User Response: Correct and reissue the command. BIP8084E Unable to create directory &1, return code &2. Explanation: The specified directory could not be created. Ensure that the characters used in the string are valid and that you have the required permissions to create the directory. User Response: Correct and reissue the command. BIP8085E The environment variable &1 could not be set. Explanation: An attempt to dynamically set an environment variable was unsuccessful. User Response: Contact your IBM support center. BIP8086E MQSeries queue manager &1 is already reserved for use by broker &2. Explanation: An attempt was made to use an MQSeries queue manager that was already reserved for use by another broker. User Response: It is acceptable for a broker, User
Chapter 2. Messages

133

BIP8087E BIP8101W
Name Server and Configuration Manager to all share a single MQSeries queue manager. It is not acceptable for multiple brokers to share a single MQSeries queue manager. Choose another MQSeries queue manager and reissue the command. BIP8087E &1 already exists and cannot be created. Explanation: An attempt was made to create a component that already exists. User Response: Ensure that the component name you have selected for creation is the correct one. Investigate the reasons why this component name already exists. BIP8088I There are no MQSeries publish/subscribe neighbors. BIP8095E MQSeries queue manager &1 is reserved for use by MQSeries Integrator component &2. Explanation: An attempt was made to delete an MQSeries queue manager that was being shared by another MQSeries Integrator component. User Response: It is acceptable for a broker, User Name Server and Configuration Manager to all share a single MQSeries queue manager. The MQSeries queue manager delete option provided by this command may only be selected if there are no other MQSeries Integrator components currently configured to share this MQSeries queue manager. BIP8096I Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

Explanation: User Response: BIP8089I MQSeries publish/subscribe neighbor &1 is inactive.

Explanation: User Response: BIP8090I MQSeries publish/subscribe neighbor &1 is active.

Explanation: User Response: BIP8097E Unable to instantiate Java object of class &1. Explanation: An instance of the Java class could not be instantiated. User 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. BIP8098I Trace level: &1, mode: &2, size: &3 KB. Explanation: User Response: BIP8099I &1 - &2 Explanation: User Response: BIP8101W Changes a brokers configuration. Syntax: mqsichangebroker BrokerName << -i ServiceUserId > -a ServicePassword > < -p DataSourcePassword > < -s UserNameServerQueueManagerName > < -t | -n > Explanation: Command Options i the userid that the broker should run under. a the password for the broker userid. p the password for the brokers database userid. s the MQSeries queue manager of the User Name Server. t indicates MQSeries fastpath is to be used for this broker. n indicates MQSeries fastpath is not to be used for this broker. User Response:

Explanation: User Response: BIP8091I Common stream &1. Explanation: User Response: BIP8092E Unable to locate MQSeries Integrator response &1 in message catalog &2. Explanation: The MQSeries Integrator response could not be found in the message catalog. User Response: Make sure that the message catalog is available and that the MQSeries Integrator response is in the message catalog. If the problem persists contact your IBM support center. BIP8093E Unable to access the MQSeries queue manager. Explanation: The MQSeries queue manager is currently being created by another user. User Response: Wait until the queue manager has been created, then reissue this command. BIP8094E Unable to access the MQSeries queue manager. Explanation: The MQSeries queue manager is currently being stopped by another user. User Response: Wait until the stop has completed and reissue this command.

134

MQSeries Integrator Messages

BIP8102W BIP8106W
BIP8102W Changes a Configuration Managers configuration. Syntax: mqsichangeconfigmgr << -i ServiceUserId > -a ServicePassword > < -d SecurityDomainName > < -s UserNameServerQueueManagerName > < -p DataBasePassword > < -r MRMDataSourcePassword > < -j MaxJVMHeapSize > Explanation: Command Options i the userid that the Configuration Manager should run under. a the password for the Configuration Manager userid. p the password for the configuration repository userid. r the password for the message repository userid. d the Security Domain that the Configuration Manager will use. s the MQSeries queue manager of the User Name Server. j the maximum Java virtual machine heap size, in megabytes (minimum 64). User Response: BIP8103W Changes a User Name Servers configuration. Syntax: mqsichangeusernameserver << -i ServiceUserId > -a ServicePassword > < -d SecurityDomainName > < -r RefreshInterval > Explanation: Command Options i the userid that the User Name Server should run under. a the password for the User Name Server userid. d the Security Domain that the User Name Server will use. r number of seconds between each refresh of the User Name Server internal cache. User Response: Changes a components trace options. Syntax (1): mqsichangetrace ComponentName ( -u | -t ) -e ExecutionGroupLabel < -f MessageFlow > ) < -l Level > < -m Mode > < -c Size > < -r > (2): mqsichangetrace ComponentName -t -b < -l Level > < -m Mode > < -c Size > Explanation: Command Options u indicates UserTrace. May only be used with flag e. t indicates Service Trace. b is for components other than execution groups. e execution group name. f message flow name. l specifies the trace level, none, normal or debug. m specifies the trace mode, safe or fast. c specifies the trace size in kilobytes. r specifies that the log should be reset. User Response: BIP8104W BIP8105W Creates a broker. Syntax: mqsicreatebroker BrokerName -i ServiceUserId -a ServicePassword -q QueueManagerName -n DataSourceName < -u DataSourceUserId > < -p DataSourcePassword > < -s UserNameServerQueueManagerName > < -w WorkPath > < -t > < -m > Explanation: Command Options i the userid that the broker should run under. a the password for the broker userid. q the MQSeries queue manager that the broker should use. This is created if it does not exist. n the brokers database name. u the userid that the broker uses to access its database. p the password for the brokers database userid. s the MQSeries queue manager of the User Name Server. w the directory into which trace logs are placed. t indicates MQSeries fastpath is to be used for this broker. m indicates that migration is required from an MQSeries publish/subscribe broker. User Response: BIP8106W Creates the Configuration Manager. Syntax: mqsicreateconfigmgr -i ServiceUserId -a ServicePassword -q QueueManagerName -n DataBaseName < -u DataBaseUserId > < -p DataBasePassword > -m MRMDataSourceName < -e MRMDataSourceUserId > < -r MRMDataSourcePassword > < -d SecurityDomainName > < -s UserNameServerQueueManagerName > < -w WorkPath > Explanation: Command Options i the userid that the Configuration Manager should run under. a the password for the Configuration Manager userid. q the MQSeries queue manager that the Configuration Manager should use. This is created if it does not exist. n the configuration repository name. u the userid that the Configuration Manager uses to access the configuration repository. p the password for the configuration repository userid. m the message repository name. e the userid that the Configuration Manager uses to access the message repository. r the password for the message repository userid. d the Security Domain that the Configuration Manager will use. s the MQSeries queue manager of the User Name Server. w the directory into which trace logs are placed. User Response:

Chapter 2. Messages

135

BIP8107W BIP8116W
BIP8107W Creates the User Name Server. Syntax: mqsicreateusernameserver -i ServiceUserId -a ServicePassword -q QueueManagerName < -d SecurityDomainName > < -r RefreshInterval > < -w WorkPath > Explanation: Command Options i the userid that the User Name Server should run under. a the password for the User Name Server userid. q the MQSeries queue manager that the User Name Server should use. This is created if it does not exist. d the Security Domain that the User Name Server will use. r number of seconds between each refresh of the User Name Server internal cache. w the directory into which trace logs are placed. User Response: BIP8108W Deletes a broker. Syntax: mqsideletebroker BrokerName < -q > < -w > Explanation: Command Options q deletes the brokers MQSeries queue manager. w deletes the brokers trace files from its work directory. User Response: BIP8109W Deletes the Configuration Manager. Syntax: mqsideleteconfigmgr < -q > < -w > < -n -m > Explanation: Command Options q deletes the Configuration Managers MQSeries queue manager. w deletes the Configuration Managers trace files from its work directory. n and m indicate that the Configuration Manager tables should be deleted; these should be used with EXTREME caution. User Response: Deletes the User Name Server. Syntax: mqsideleteusernameserver < -q > < -w > Explanation: Command Options q deletes the User Name Servers MQSeries queue manager. w deletes the User Name Servers trace files from its work directory. User Response: BIP8111W Formats the trace log retrieved using mqsireadlog. Syntax: mqsiformatlog -i InputFileName < -o OutputFileName > Explanation: Command Options i the file name containing a trace log that requires formatting. o a file name to receive the formated trace log. User Response: BIP8110W BIP8112W Joins with a neighboring MQSeries publish/subscribe broker. Syntax: mqsijoinmqpubsub BrokerName -p ParentQMgrName Explanation: Command Options p the MQSeries queue manager of the MQSeries publish/subscribe broker which is to be joined with. User Response: BIP8113W Lists the components that have been created and their MQSeries queue manager. Syntax: mqsilist < BrokerName < -e ExecutionGroupLabel >> Explanation: Command Options BrokerName requests a list of execution groups configured for a broker. e requests a list of message flows configured for an execution group. User Response: BIP8114W Retrieves the trace log. Syntax (1): mqsireadlog ComponentName ( -u | -t ) -e ExecutionGroupLabel < -f > < -o OutputFileName > (2): mqsireadlog ComponentName -t -b SubComponent < -f > < -o OutputFileName > Explanation: Command Options u indicates User Trace. May only be used with flag e. t indicates Service Trace. b is for sub-components other than execution groups: for a complete list of subcomponents refer, to the Administration Guide. e execution group name. f indicates a forced read; this option may result in partial trace records being read. o a file name to receive the trace log. User Response: BIP8115W Displays trace settings. Syntax (1): mqsireporttrace ComponentName ( -u | -t ) -e ExecutionGroupLabel < -f MessageFlow > (2): mqsireporttrace ComponentName -t -b Explanation: Command Options u indicates User Trace. May only be used with flag e. t indicates Service Trace. b is for components other than execution groups. e execution group name. f message flow name. User Response: BIP8116W Starts a component. Syntax: mqsistart ComponentName Explanation: Command Options ComponentName may be a broker name, ConfigMgr or UserNameServer. User Response:

136

MQSeries Integrator Messages

BIP8117W BIP8125W
Stops a component. Syntax: mqsistop ComponentName < -q > < -i > Explanation: Command Options ComponentName may be a broker name, ConfigMgr or UserNameServer. q stops the MQSeries queue manager used by ComponentName. i forces the broker to stop immediately; this option should be used with caution as there may be resource locks left that will need to be attended to. User Response: BIP8118W Removes knowledge of a neighboring MQSeries Publish/Subscribe broker. Syntax: mqsiclearmqpubsub BrokerName -n NeighbourQMgrName Explanation: Command Options n the queue manager name of the MQSeries Publish/Subscribe broker. User Response: BIP8119W Displays neighboring MQSeries publish/subscribe brokers. Syntax&colon; mqsilistqpubsub. BrokerName Explanation: User Response: BIP8120W Refreshes the Neon library. Syntax: mqsinrfreload -b BrokerName Explanation: Command Options b the broker that should be refreshed. User Response: BIP8121W Lists the contents of a components persistent store. Syntax: mqsibrowse componentName -t persistentStoreTable Explanation: Command Options t is the components persistent store table that will be listed. User Response: BIP8122W Displays broker property settings. Syntax: mqsireportproperties BrokerName -e ExecutionGroupLabel -o Object ( -n Name | -a | -r ) Explanation: Command Options e Execution Group name. o Object name. n Attribute name. a indicates that all attribute values should be displayed (non-recursive). r indicates that all attribute values should be displayed (recursive). User Response: BIP8117W BIP8123W Changes a broker property values. Syntax: mqsichangeproperties BrokerName -e ExecutionGroupLabel -o Object -n Name -v Value Explanation: Command Options e execution group name. o Object name. n Attribute name. v Attribute value. User Response: BIP8124W Changes and Reports a components details. Syntax: mqsiservice <componentName <-r label=value>> <-m messageNumber <-c messageCatalog>> Explanation: Reports the components product version and its locale. Allow a specific message from the message Catalog to be produced. Command Options componentName is the name of the component to query for its registry data. r (label=value) Sets the registry key label to value, (label=) Sets the registry key label to null, (label) deletes the registry key label. The r option flag is destructive; be sure to keep a backup. m is a message number to output. c is the name of the message catalog to use. User Response: BIP8125W Exports or Imports a message set from or into a repository. Syntax: mqsiimpexpmsgset -e -n MRMDataSourceName -u MRMDataSourceUserId -p MRMDataSourcePassword -s SourceMessageSetName -l SourceMessageSetLevel -f FileName mqsiimpexpmsgset -i -n MRMDataSourceName -u MRMDataSourceUserId -p MRMDataSourcePassword -f FileName Explanation: Command Options e Exports a message set. i Imports a message set. n the components database name. u the userid that the component uses to access the database. p the password that the component uses to access its database s the message set being exported or imported l the level of the message set f the file being imported, or the file being exported. User Response:

Chapter 2. Messages

137

BIP8126W BIP8140E
BIP8126W 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 Explanation: Command Options n the components database name. u the userid that the component uses to access the database. p the password that the component uses to access its database. s the message set being copied. l the level of the message set being copied. t the name of the target message set. k the target message set level. User Response: Example: mqsicopymsgset MRMDB MRMADMIN password My MessageSet 1 My MessageSet Copy 1 BIP8130I Execution Group: &1 - &2 Explanation: User Response: BIP8131I Message flow: &1 Explanation: User Response: BIP8132E &1 is not a valid sub-component name. Explanation: The name selected is not a valid sub-component. User Response: The name selected is not supported. Select a different sub-component name. BIP8133E Unable to write to the selected output file &1 Explanation: The file selected could not be written to. User Response: Ensure that the file selected is not in a protected directory, that it is not read-only and that it is not being used or locked by another user. Also check that the directory into which the file will be written has adequate free space. BIP8134E Unable to alter MQSeries queue manager &1. Explanation: This command attempts to alter an MQSeries queue manager, the queue manager could not be altered. User Response: Locate and resolve the problem and retry the command. BIP8135E Unable to create files: operating system return code {1}. Explanation: An error occurred creating files in response to a command. This may be because the user does not have the required authorisation. User Response: Check that the user has the required authority to create files and retry. BIP8136E Unable to change the ownership of files: operating system return code {1}. 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 authorisation. User Response: Check that the user has the required authority to create files and retry. BIP8137E Unable to change the attributes of files: operating system return code {1}. Explanation: An error occurred changing the attributes of files in response to a command. This may be because the user does not have the required authorisation. User Response: Check that the user has the required authority to create files and retry. BIP8138E Userid &1 cannot be used by this broker. Explanation: The userId selected cannot be used by the broker. This may be because the userid does not have the required authorization or that the userId is invalid for operations that the broker requires, for example, if a broker is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId mqm. User Response: Check that the user has the required authority to create files and retry. BIP8139E The user issuing this command does not have the required permissions to complete the command. Explanation: The userid that the command is being run under must have the authority to end broker processes. User Response: Check that the user has the required authority to end the brokers processes. BIP8140E Unable to find service userid &1 in broker &2. Explanation: Cannot authenticate service userid in broker. User Response: Use mqsichangebroker to alter the service userid and then retry the command.

138

MQSeries Integrator Messages

BIP8141E BIP8156E
BIP8141E Unauthorized userid &1 in broker &2. Explanation: The service userid is not authorized to run the broker. User Response: Use mqsichangebroker to alter the service userid and retry the command. BIP8142E Unable to set process userid. Explanation: UNIX setuid command had failed. User Response: Verify with your system adminstrator that file permissions for this command are set correctly. BIP8143E Unable to change group ownership of directory &2 to &3. (error &1) Explanation: Directory &2 is required to have &3 as group owner. User Response: Use a different -w value or consult system administrator for possible cause of this error. BIP8144E Unable to create directory &1. (error &2) Explanation: Directory &1 creation has failed due to directory permission setting. User Response: Use a different -w value or consult system administrator for possible cause of this error. BIP8145I Execution group process IDs &1 were forced to terminate. Explanation: The broker was shutdown forcibly, this caused execution group processes to be stopped. User Response: This action may leave system, database, MQSeries or application resources in a locked state. Some resource locks may need freeing manually, others will not need any action to be taken. BIP8146E An error occurred while opening registry file &2 to read it : &3. Explanation: The program cannot proceed, because it cannot read the value in the registry for this key. User Response: Contact your MQSeries Integrator administrator. BIP8147E An error occurred while reading registry file &1 : &2. Explanation: The broker cannot proceed, because it cannot read the value in the registry for this key. User Response: Contact your MQSeries Integrator administrator. BIP8148E An error occurred while opening registry file &1 to write it : &2. Explanation: The program cannot proceed, because it cannot record the value in the registry for this key. User Response: Contact your MQSeries Integrator administrator. BIP8149E An error occurred while writing registry file &1 : &2. Explanation: The program cannot proceed, because it cannot write the value in the registry for this key. User Response: Contact your MQSeries Integrator administrator. BIP8150E An error occurred while deleting files from registry directory &1 : &2. Explanation: Some of the files in the broker registry have not been deleted. User Response: Ask your MQSeries Integrator administrator to check why the files could not be deleted, then retry the mqsidelete command. BIP8151E An error occurred while deleting the registry directory &1 : &2. Explanation: The broker registry has not been deleted. User Response: Ask your MQSeries Integrator administrator to check why the registry directory could not be deleted, then retry the mqsidelete command. BIP8152E The registry is already locked. Explanation: The program cannot continue, because of an internal error. User Response: Contact your MQSeries Integrator administrator. BIP8153E An error occurred while opening the registry lock file &1 : &2. Explanation: You do not have sufficient UNIX file system permissions to administer the broker. User Response: Ask your MQSeries Integrator administrator to add you to the mqbrkrs group. After this has been done, log in again and reissue the command. BIP8154E An error occurred while locking the registry file &1 : &2. Explanation: The program cannot continue, because of an internal error. User Response: Contact your MQSeries Integrator administrator. BIP8155E An error occurred while writing to the registry lock file &1 : &2. Explanation: The program cannot continue, becuase of an internal error. User Response: Contact your MQSeries Integrator administrator. BIP8156E The registry was not locked. Explanation: The program cannot continue, because of an internal error. User Response: Contact your MQSeries Integrator administrator.

Chapter 2. Messages

139

BIP8157E BIP8179W
BIP8157E An error occurred while unlocking the registry lock file : &1. Explanation: The program cannot continue, because of an internal error. User Response: Contact your MQSeries Integrator administrator. BIP8165W An internal error has occurred while accessing the message repository. Explanation: There may insufficient memory to complete the operation. User Response: Increase the amount of virtual memory available on your system and retry the command. BIP8166E The message set to be imported has been finalized in this repository since the export file was created. 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. User Response: Delete all message sets based on this message set or import a finalized version of the message set. BIP8167E Unknown message repository database name &1. Explanation: The message repository database name &1 could not be located. User 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 datasource name &1 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 datasource that has been configured for the correct database. BIP8168E The userid and/or password are not authorized for connection to the message repository database &1. Explanation: The message repository database name &1 could not be opened because the userid and/or password is not authorized. User 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 message repository database access rights have been correctly configured. BIP8169W An internal error has occurred while accessing the message repository. Explanation: A SAX parser exception occurred. The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP8171W An internal error has occurred while accessing the message repository. Explanation: A DOM parser exception occurred. The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP8172W An unexpected exception has occurred while accessing the message repository. Explanation: The text of the exception is &1. User Response: If the error persists contact your IBM support center. BIP8173E An internal error has occurred while accessing the message repository. Explanation: The error was due to invalid content of an XML document. User Response: If the error persists contact your IBM support center. BIP8174E An internal error has occurred while accessing the message repository. Explanation: The error was due to invalid content of an XML document. User Response: If the error persists contact your IBM support center. BIP8175E Duplicate message set identifier. Explanation: The message set to be imported already exists in this repository. User Response: Delete the message set and retry the command. BIP8176E Failed to access export file &1. Explanation: The error code &2 was detected. User Response: Check that you have access rights to the export file. BIP8177E Failed to open import file &1. Explanation: There was a failure opening the import file &1. User Response: Check the filename and path entered and that you have access rights to the file. BIP8179W An internal inconsistency has been detected while accessing the message repository. Explanation: The MRM return code &1 was detected. User Response: This is an internal error. If the error

140

MQSeries Integrator Messages

BIP8180E BIP8207E
persists contact your IBM support center. BIP8180E The message repository database &1 has not been initialized correctly. Explanation: It is not possible to access the message repository because the database &1 has not been properly initialized. User Response: This error is most probably a result of a set-up inconsistency. You must delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then re-create your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options). BIP8181E An error has occurred while connecting to the message repository. 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. User 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 (&2) and SQL state (&3) were returned. Check your database manager documentation for further information on this error. BIP8182E Database manager not started. Explanation: The message repository database name, &1, could not be accessed. The database manager has either not been started, or has been stopped. User Response: Start the database manager and retry the command. BIP8183E The resource &1 does not exist in the message repository. Explanation: The resource &1 is referenced, but it does not exist in the message repository. User Response: Correct the problem and retry the command. BIP8185E Duplicate message set name. Explanation: A message set named &1 already exists in this repository. User Response: Delete the message set and retry the command. BIP8188E Invalid message set level. Explanation: The level &1 for message set &2 is invalid. User Response: Correct the message set level and retry the command. BIP8201I User Name Server starting with refresh interval &1. Explanation: The User Name Server is being started with a refresh interval that determines (in seconds) how frequently the native security subsystems user/group registry will be reread. User Response: No user action required. BIP8202I User Name Server UUID has been set to &1. Explanation: The User Name Server requires a UUID to identify it to the domain. User Response: No user action required. BIP8203S User Name Server UUID could not be established. Explanation: The User Name Server requires a UUID to identify it to the domain, a new UUID was not successfully generated. User Response: Restart the User Name Server. Contact your IBM support center if the problem persists. BIP8204I User Name Server is registering a client with UUID &1, and cache version &2. 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. User Response: No user action required. BIP8205E User Name Server failed to send a response/report to a configuration request. Explanation: The User Name Server could not deliver a response/report message. User Response: Check preceding system log entries for errors from the underlying messaging subsystem. BIP8206W User Name Server received an acknowledgement from an unregistered client with UUID &1. 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. User Response: Contact your IBM support center if the problem persists. BIP8207E User Name Server failed to send updated user/group information to client with UUID &1. Explanation: The User Name Server could not deliver user/group information to a registered client. User Response: Check preceding system log entries for errors from the underlying messaging subsystem.

Chapter 2. Messages

141

BIP8208I BIP8259W
BIP8208I User Name Server refresh interval has been reset to &1. Explanation: The User Name Servers refresh interval determines (in seconds) how frequently the native security subsystems user/group registry will be reread. User Response: No user action required. BIP8209W User Name Server could not retrieve user/group information from the native security subsystem. Explanation: The User Name Server will continue processing using its cached version of user/group information. User Response: Check preceding system log entries for errors from the underlying security subsystem. BIP8250W The Configuration Managers user/group cache is empty. 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. User 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. BIP8251W The Configuration Manager failed to send a registration/heartbeat message to the User Name Server. Explanation: The Configuration Manager could not deliver a registration/heartbeat message to the User Name Server. User Response: Check preceding system log entries for errors from the underlying messaging subsystem. Contact your IBM support center if the problem persists. BIP8252W The Configuration Manager failed to send an acknowledgement message to the User Name Server. Explanation: The Configuration Manager could not deliver an acknowledgement message to the User Name Server. User Response: Check preceding system log entries for errors from the underlying messaging subsystem. Contact your IBM support center if the problem persists. BIP8253E Error in parsing a message from the User Name Server, invalid tag &1. Explanation: The Configuration Manager has received a message from the User Name Server that it is unable to parse. User Response: Contact your IBM support center if the problem persists. BIP8254E Internal Error while parsing a message from the User Name Server. Explanation: The Configuration Manager has encountered an internal error while attempting to parse a message from the User Name Server. User Response: Contact your IBM support center if the problem persists. BIP8255I User Name Services are disabled. Explanation: The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. User 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. BIP8256E Failed to initialize the interface to the User Name Server. 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. User Response: Check preceding system log entries for related errors. BIP8257I The Configuration Manager has reconnected to MQSeries for User Name Services. 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 MQSeries transports but communication has been reestablished. User Response: Investigate the reasons for the failure of the MQSeries product. BIP8258I Successfully registered with the User Name Server using UUID &1. 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. User Response: No user action required. BIP8259W The Configuration Manager has not yet registered with the User Name Server. 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. User Response: Check that the User Name Server has

142

MQSeries Integrator Messages

BIP8260I BIP8302E
been started. Check preceding system log entries for related errors. BIP8260I Successfully initialized the interface to the User Name Server. 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. User Response: No user action required. BIP8261E The Configuration Manager is encountering problems in communicating with the User Name Server. 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. User Response: Check preceding system log entries for related errors. If the problem persists contact your IBM support center. BIP8280I Successfully initialized interface to the NT security domain, &1. Explanation: A component of MQSeries Integrator has successfully initialized the NT security domain. User Response: No user action required. BIP8281E Error in initializing the NT security domain: return code &1; subsystem error code &2. Explanation: A component of MQSeries Integrator 2 is attempting to initialize the NT security domain for use as a supplier of user and group information, without success. User Response: Check NT security subsystem documentation for the reported error. BIP8282E Error in call &1 to the NT security domain with return code &2. Explanation: A component of MQSeries Integrator is attempting to call the NT security domain. The security subsystem returned an error code. User Response: Check NT security subsystem documentation for the reported error. BIP8283E Error in determining the domain controller in the NT security domain, return code &1. Explanation: A component of MQSeries Integrator 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. User Response: Check NT security subsystem documentation for the reported error. BIP8284E Failed to find NT security domain, &1. Explanation: A component of MQSeries Integrator has failed to locate the specified NT security domain. User Response: Check that the domain name was correctly specified and that it is accessible from this machine. BIP8285E Insufficient authority to access NT security domain, &1. Explanation: A component of MQSeries Integrator 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. User 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. BIP8300W The brokers user/group cache is empty. 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. User 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. BIP8301E Failed to send initial registration to the User Name Server. 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 stopped. User Response: Check that the User Name Server is running. Check preceding system log entries for related errors. BIP8302E A problem occurred in registering with the User Name Server. 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 re-established. Registration is an asynchronous operation but severe delays and repetitions of this message require investigation. User Response: Check that the User Name Server has been started. Check preceding system log entries for related errors.

Chapter 2. Messages

143

BIP8380I BIP8418W
BIP8380I Successfully initialized the plug-in user/group registry. Explanation: A component of MQSeries Integrator 2 has successfully initialized the plug-in user/group registry. User Response: No user action required. BIP8381E Error in initializing the plug-in user/group registry. Explanation: A component of MQSeries Integrator is attempting to initialize the plug-in service for use as a supplier of user and group information. User Response: Check the plug-in services diagnostic report for initialization errors. BIP8382E Error in call &1 to the plug-in user/group registry with return code &2. Explanation: A component of MQSeries Integrator is attempting to call the plug-in user/group registry. The plug-in returned an error code. User Response: Check the plug-in services diagnostic report for the reported error. BIP8401E Invalid value for parameter &1. Explanation: The parameter &1 to a JMS interface method has been given an invalid value. User Response: Ensure all application calls to the JMS interface pass valid parameters. BIP8402S MessageConsumer.receive cannot be called when a listener is set. Explanation: An attempt has been made to call the JMS method MessageConsumer.receive() when a listener has already been set for the MessageConsumer method. A threading synchronization error has occurred. User Response: This is an internal error. Please contact your local IBM Support Center. BIP8403E The JMS functionality that you have requested is not available under this particular release. Explanation: Although the JMS specification suggests that this functionality is available, it has not been implemented for the particular version of the JMS specification that you are using. The function cannot be used. User Response: The functionality may be available in a more recent release. Alternatively modify your application so that it does not use the unsupported functionality. BIP8404E Invalid null value for JMS method parameter &1. Explanation: A null parameter has been passed to a JMS method, where a null value is not valid. User Response: Ensure your application does not pass a null value to the JMS method. BIP8405E JMS connection is not active. Explanation: A connection has been closed and a JMS client application is trying to perform an operation using the closed connection. User Response: The connection needs to be re-established before an attempt is made to use it again. Ensure the application has a valid connection before performing the operation. BIP8406W JMS client thread interrupted. Explanation: A Java thread has been interrupted while performing a JMS client operation. This interruption may have been caused by the process being terminated. User Response: Restart the client application if desired. BIP8407W JMS connection closed. Explanation: The connection has been closed because the broker at the other end of the connection has terminated, or ended the connection for some other reason. User Response: The connection needs to be reopened. Ensure the broker is running, then the application must either reopen the connection, or be restarted. BIP8408E JMS version of client (&2) different from that used by the broker (&1). Explanation: The JMS client version does not match the version that is being used at the broker. User Response: Ensure that the client is using the same version of JMS code as the broker. BIP8413W Network failure in JMS client. Explanation: A network failure has occurred, and detected by a JMS client. The connection to the broker has been terminated. User Response: Check that the network is operating correctly and that the broker is running. Restart the client application. If the problem persists, contact your IBM Support Center. BIP8414W The JMS client is not connected to the broker. Explanation: An attempt has been made to use a JMS operation which requires an active connection, when no connection has yet been made. User Response: Ensure that the application establishes a connection with the broker before using the operation. BIP8418W Topic not set in JMS message. Explanation: A JMS client operation was attempted which requires a topic to be set in a message, and the topic was not set. User Response: Ensure that the application sets the

144

MQSeries Integrator Messages

BIP8421W BIP8445W
topic before attempting the operation. BIP8421W The JMS connection is unusable. Explanation: An application attempted to use a JMS connection which is not currently usable. The connection is in the process of being terminated, and should not be used. User Response: Ensure JMS client applications do not use connections when they are being closed. BIP8422W The user is already connected via a JMS client connection. Explanation: Each user may only have a single active JMS client connection at a time. User Response: Ensure that only one application at a time connects with each user identifier. BIP8423W Unexpected javax.jms.JMSException of type &1; reason message is &2. Explanation: An unexpected exception was caught by the JMS client while calling an external method. User Response: Check JMS client applications to determine the reason for the exception being thrown. BIP8430E Unexpected end of JMS message. Explanation: The end of a JMS message was encountered unexpectedly. The message body is corrupt. User Response: This is an internal error. Contact you IBM Support Center. BIP8431E JMS message format exception. Explanation: The JMS message is not in a recognisable format. User Response: This is an internal error. Contact your IBM Service Center. BIP8432E JMS message not readable. Explanation: An operation which needs to read from the message failed because the message is not currently readable. User Response: This is an internal error. Contact your IBM Support Center. BIP8433E JMS message not writable. Explanation: An operation which needs to write to the message failed because the message is not currently writable. User Response: This is an internal error. Please contact your IBM Support Center. BIP8434E JMS resource allocation problem. Explanation: There has been an error while trying to allocate resources for a JMS operation. User Response: Retry the operation. If the problem persists, contact you IBM Support Center. BIP8436E JMS internal error. Explanation: An internal error has occurred. User Response: Retry the operation. If the problem persists, contact you IBM Support Center. BIP8437E JMS null element error. Explanation: An attempt has been made to retrieve a property that is not set. User Response: Ensure that the property being retrieved has been set. If the problem persists, contact your IBM Support Center. BIP8438E JMS null property name. Explanation: An attempt has been made to retrieve a property supplying a null name. User Response: Ensure that all JMS application calls to obtain property values specify a non-null value for the property name. BIP8439W JMS buffer too small. Explanation: A buffer passed on a JMS operation was not large enough for the operation. User Response: Retry the operation with a larger buffer. BIP8440S JMS unexpected error. Explanation: An unexpected error has occurred within the JMS client. User Response: Retry the operation. If the error persists, contact your IBM Support Center. BIP8441E JMS internal invalid hex string error. Explanation: An internal JMS operation encountered an invalid hexadecimal digit in a string. User Response: This is an internal error. Contact your IBM Support Center. BIP8443E JMS internal bad CCSID error. Explanation: An internal error supplied an invalid CCSID value. User Response: This is an internal error. Contact your IBM Support Center. BIP8444W JMS invalid map message. Explanation: An operation was attemped on a message using the map message type, but the message is of a different type. User Response: Ensure all JMS applications use the correct message types. If the problem persists, Contact your IBM Support Center. BIP8445W JMS invalid stream message. Explanation: An operation was attemped on a message using the stream message type, but the message is of a different type. User Response: Ensure all JMS applications use the
Chapter 2. Messages

145

BIP8446W BIP8460I
correct message types. If the problem persists, Contact your IBM Support Center. BIP8446W JMS byte to string error. Explanation: A message property was requested as a string value, but the property cannot be converted to a string. User Response: Ensure all JMS applications obtain message properties with the correct types. If the problem persists, contact your IBM Support Center. BIP8447E JMS bad RFH2 format error. Explanation: A message was recieved by a JMS client application with an unexpected format. The message cannot be processed. User Response: Ensure JMS clients are connect to brokers of the same version. If the problem persists, contact your IBM Support Center. BIP8448I com.ibm.broker.jms.JMSMessage Explanation: User Response: BIP8449E JMS bad message class error. Explanation: A message was recieved by a JMS client application with an unexpected format. The message cannot be processed. User Response: Ensure JMS clients are connect to brokers of the same version. If the problem persists, contact your IBM Support Center. BIP8450E JMS internal invalid surrogate error. Explanation: While converting a string to or from an internal XML representation, a conversion error ocurred while processing a UTF-16 surrogate. User Response: This is an internal error. Contact your IBM Support Center. BIP8451E JMS internal invalid escape sequence error. Explanation: While converting a string to or from an internal XML representation, a conversion error ocurred while processing an escape sequence. User Response: This is an internal error. Contact your IBM Support Center. BIP8452W JMS bad type exception. Explanation: An attempt has been tried to retrieve a value in a type to which the value cannot be converted. User Response: Ensure that all JMS applications obtain values using the correct types. If the problem persists, contact your IBM Support Center. BIP8453W JMS unsupported type. Explanation: An attempt has been made to set or retrieve an object of a type that is not supported. User Response: Ensure that all JMS client applications use types which are supported by this implementation of the JMS interface. BIP8454I JMS no session exception. Explanation: An attempt to acknowledge receipt of a message failed because the session is not available. User Response: Ensure that all JMS client applications have active sessions when they acknowledge receipt of messages. If the problem persists, contact your IBM Support Center. BIP8455E JMS property name &1 unacceptable. Explanation: A JMS application has tried to set a message property using an unacceptable name. User Response: Ensure that all JMS client applications are setting properties with acceptable names, according to the JMS interface specification. BIP8456E JMS element name &1 unacceptable. Explanation: A JMS application has tried to set a map message element using an unacceptable name. User Response: Ensure that all JMS client applications are setting map message elements with acceptable names, according to the JMS interface specification. BIP8457S JMS requires UTF8 support. Explanation: This implementation of the JMS client requires UTF8 support, which does not appear to be available with the level of the Java Virtual Machine on which the client is running. User Response: Ensure that the correct level of the Java Virtual Machine is being used. If the problem persists, contact your IBM Support Center. BIP8458E JMS object serialization failed. Explanation: A call to the serialize method failed on the Serializable object. User Response: This is an internal error. Contact your IBM Support Center. BIP8459E JMS object deserialization failed. Explanation: A call to the unserialize method failed on the Serializable object. User Response: This is an internal error. Contact your IBM Support Center. BIP8460I JMS exception &1 occurred converting message to string. Explanation: An exception ocurred converting a message to a string. User Response: The string representation of a message is not guaranteed to be available. If it cannot be generated, this is the result.

146

MQSeries Integrator Messages

BIP8461I BIP8614W
BIP8461I JMS characters omitted. Explanation: While converting a message to a string, a character string longer than 100 characters was encountered. Some characters have been omitted. User Response: No user action required. BIP8462I JMS encoding &1 &2. Explanation: A JMS message is being converted to a string, and this message indicates the encodings used for the conversion. User Response: No user action required. BIP8601E This program requires VGA or better resolution. Explanation: The installation of this product requires that you use a display with at least VGA resolution. User Response: Check your display/display settings. BIP8602E Setup requires Windows NT Server 4.0/SP5 or later. Explanation: The installation of this product requires that your system level is Windows NT Server 4.0/SP5 or later. User Response: Upgrade your NT system. BIP8603E MQSeries Integrator install or uninstall is already running. Explanation: The install has detected a conflicting install/uninstall process running on your machine. User Response: Exit this instance of the install/uninstall and terminate the conflicting process. BIP8604E The system has detected that you do not have administrator equivalent rights. You must log on as an administrator and run setup again. Explanation: To install MQSeries Integrator you need administrator authority. User Response: Terminate the installation, log off, log on as an administrator, and retry. BIP8605E UnInstaller setup failed to initialize. Explanation: There was an InstallShield error during setup. If the installation fails you may have to manually uninstall the product. User Response: Check the install log to determine the error then retry the uninstallation. To manually uninstall the product see the MQSeries Integrator Version 2.0.2 Installation Guide. If the problem persists contact your IBM Support Center. BIP8606W Before setup can display help, this computers help system needs upgrading to HTML Help 1.3. Would you like to upgrade now? You might need to restart the computer. Explanation: Help for install and uninstall requires that HTML Help 1.3 to be installed. User Response: If you want to see the install/uninstall help then you can allow MQSeries Integrator 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. BIP8610W Help cannot be displayed as Internet Explorer level is less than 4.01. Explanation: The install or uninstall cannot display help unless IE 4.01 or later is installed on your machine. User 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. BIP8611E Uninstall cannot continue, administrator authority is required. Explanation: You require administrator authority to uninstall MQSeries Integrator. User Response: Access the machine with the same user authority that the product was installed with. BIP8612I Select at least one component to proceed. Explanation: You need to select at least one component for installation/uninstallation. User Response: Select one or more components to proceed. BIP8613W MQSeries Integrator setup or uninstallation is already running. Explanation: MQSeries uninstall has detected that there is an instance of install or uninstall already running. User Response: Terminate this uninstall instance and restart (if necessary) when the already running install or uninstall has finished. BIP8614W One or more problems occurred during uninstallation.Review &1 for details. 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 &1 may contain additional information on the nature of the problem. User Response: Review the install/uninstall log &1 to aid resolution of the problem. If the problem persists, contact your IBM support center.

Chapter 2. Messages

147

BIP8615W BIP8622W
BIP8615W Problem encountered stopping broker &1. Return from mqsistop was &2. Abort, Retry, or Ignore? Explanation: The uninstall attempted to stop a broker named &1 using mqsistop but encountered an error. The return code from mqistop was &2. User Response: The command can be retried by choosing Retry, this is the suggested action. If you choose Abort then uninstall will end. Before relaunching the uninstall you should try to manually stop the broker identified. If you choose Ignore then uninstall will continue, but it is possible that the problem with mqsistop may cause additional errors to appear when the uninstall attempts to delete the broker. Additional help is available using the Help button. BIP8616W Unable to delete broker &1. Return Code from mqsideletebroker was &2. Abort, Retry, or Ignore? Explanation: The uninstall attempted to delete a broker (&1) but encountered an error. The return code from mqsideletebroker was &2. User 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 broker identified. If you choose Ignore then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button. BIP8617W Unable to stop Configuration Manager. Return Code from mqsistop was &1. Abort, Retry, or Ignore? Explanation: The uninstall attempted to stop the Configuration Manager using mqsistop but encountered a problem. The return code from mqsistop was &1. User Response: The command can be retried by choosing Retry. If you choose Abort then uninstall will end. Before relaunching the uninstall you should try to manually stop the Configuration Manager. If you choose Ignore then uninstall will continue, but it is possible that the problem with mqsistop may cause additional errors to appear when the uninstall attempts to delete the Configuration Manager. Additional help is available using the Help button. BIP8618W Unable to delete configuration manager. Return Code from mqsideleteconfigmgr was &1. Abort, Retry, or Ignore? Explanation: The uninstall attempted to delete the Configuration Manager but encountered an error. The return code from mqsideleteconfigmgr was &1. User 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 then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button. BIP8619W Unable to stop User Name Server. Return Code from mqsistop was &1. Abort, Retry, or Ignore? Explanation: The uninstall attempted to stop the User Name Server using mqsistop but encountered a problem. The return code from mqsistop was &1. User Response: The command can be retried by choosing Retry. If you choose Abort then uninstall will be terminated. Before relaunching the uninstall you should try to manually stop the User Name Server. If you choose Ignore then uninstall will continue, but it is possible that the problem with mqsistop may cause additional errors to appear when the uninstall attempts to delete the User Name Server. Additional help is available using the Help button. BIP8620W Unable to delete User Name Server. Return Code from mqsideleteusernameserver was &1. Abort, Retry, or Ignore? Explanation: The uninstall attempted to delete the User Name Server but encountered an error. The return code from mqsideleteusernameserver was &1. User 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 then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button. BIP8621I DB2 install completed successfully. Explanation: The silent install of DB2 was successful. User Response: As a result of installing DB2 you will be asked (at the end of install) to reboot the system in order for DB2 to be activated. You can choose to do this when asked or wait until a more convenient time. Until you reboot the DB2 functionality will not be fully available. BIP8622W DB2 install may have failed. Explanation: The silent install of DB2 may have failed. After completing the MQSeries Integrator V2 installation you should check the logs to identify the problem and reinstall DB2 as a seperate exercise. It is possible that the error will be minor and not require reinstallation. User Response: When installation of DB2 by MQSeries Integrator fails there should be two logs available for viewing in the directory into which you installed Windows NT ( WINNT is the default). The logs are called MQSI2DB2.ISS and MQSI2DB2.LOG. Check the contents of these files to determine why the installation of DB2 has failed. To correct the reason for the failure, first try to uninstall DB2 through the Control Panel-->Add/Remove Programs feature. If this

148

MQSeries Integrator Messages

BIP8623W BIP8632I
is possible (or not) then you should reboot your machine and reinstall DB2. To do this go into the DB2 directory on the CD and run the setup.exe file. This will give a panel based installation of DB2, you should select the Typical install option. If you cannot determine the cause of the failure contact your IBM support center for advice. BIP8623W Internet Explorer 4.01 or later required for online help. Explanation: The online help requires functionality that is only present in IE 4.01 or later. User Response: Check that IE 4.01 or later is installed on your system if you wish to view the online help. BIP8624W A root directory is not allowed for the top-level directory for MQSeries Integrator. Explanation: A root directory is not allowed for the top-level directory for MQSeries Integrator. User Response: Specify an alternative directory. BIP8625W The Windows NT system directory is not allowed for the top-level directory for MQSeries Integrator. Explanation: Windows NT system directory is not allowed for the top-level directory for MQSeries Integrator. User Response: Specify an alternative directory. BIP8626S Current service level is &1. You must reapply service after setup completes. Explanation: This warning message shows the current service level on the system. User Response: You must reapply service level, as shown on the screen, after setup completes. BIP8627W Install was unable to establish the MQSeries Integrator V1 base path. Explanation: As part of the install the MQSeries Integrator V1 function is replaced. This process involves removing the MQSeries Integrator V1 references in the PATH environment variable. The install was unable to determine the path where MQSeries Integrator V1 was installed to. User Response: You should check your PATH environment variable after install. If the MQSeries Integrator V1 paths are still there then you must remove them. BIP8628S Uninstall cannot determine the installation path from Registry. Explanation: The uninstall program failed when accessing the product Registry entry to determine the install path. User Response: It is possible that the registry entries for this product are damaged. Retry the uninstall and if the same failure occurs then you will need to manually uninstall the product. BIP8629S Uninstall cannot access Registry key (&1). Explanation: The uninstall program cannot establish ownership of the product Registry key. User Response: The userid you are using for uninstall does not seem to have authority to the registry entries for this product. You should obtain the correct authorisation to the Registry. BIP8630W OCX Registration using &1 failed (rc = &2). Explanation: In order to enable the MQSeries Integrator V1 Visual Tester NNMgr.ocx and NNObjs.ocx need to be registered. The regsvr32.exe program that does this has failed. User Response: You can run these commands manually following installation. One reason why you might encounter this error is because you have selected a type of MQSIV1.1 database that is not installed on your system. The OCX files that are installed, because of this selection, have inbuilt dependencies on dlls installed as part of the database package. BIP8631W Please confirm that you really want to cancel the uninstall? Continuation will leave a potentially non-working product. Explanation: You are trying to Cancel the uninstall while files are being deleted. If you continue, then you will have deleted some files from the product and left an incomplete set of files in place. MQSeries Integrator will be damaged. User Response: If you really mean to cancel then select Yes. In order to restore the product to a working state you will need to reinstall. You should still be able to run uninstall again if you wish. BIP8632I Verification of Userid/Password failed. Reason: &1. Select NO (default) to retry. Select YES to continue without retry. Explanation: The Userid/Password that you entered for use as a DB2 Administrator has failed verification. There are several reasons why this may have occurred and you should use the reason given in the message to attempt to correct the problem. The most common error will be that you gave an invalid password for the userid specified, but other errors may occur. User Response: You will normally select NO and retry, however you can select YES and bypass this failure. If you do select YES then the DB2 installation launched later in this installation may fail and you will then need to manually install DB2.

Chapter 2. Messages

149

BIP8633W BIP8640E
BIP8633W Password and Confirm Password fields are different. Explanation: You have entered different passwords in the Password and Confirm Password fields. User Response: You must enter the same password in the Password and Confirm Password fields. BIP8634I Setup of NT Security groups failed. Reason: &1 Explanation: There was an error encountered when the installation program attempted to set up local NT security groups, or (if you are installing on a primary or backup domain controller,) global NT security groups. The reason given in the message gives further information about the cause of the failure. User Response: The installation continues, however you may manually have to create the necessary groups using the Microsoft supplied User Manager Tool accessible through the NT toolbar. The installation manual gives more information on the names of the groups and how to do this. If the reason is Failure in adding global groups to local groups then this may reflect a valid situation where a decision has been made not to implement the security model using global groups. BIP8635I This CSD or a later one has already been installed. You must uninstall one or more CSDs before installation of this CSD can proceed. Explanation: The CSD you are trying to install has already been installed or there is a later CSD Installed. CSDs are cumulative, thus the CSD level currently installed will have all the problem fixes contained in this CSD. User Response: If, for some reason, you want to install this CSD level, rather than the one that the registry shows you currently have, then you will need to uninstall previous CSDs until the level of your installed code is below the level contained on the CSD you are trying to apply. If you believe there is a discrepancy in the level of service that the install program thinks you have applied, contact your IBM support center. BIP8636I Existing versions of Tool\\Workbook.ini and/or Tool\\working.cfg were found, and have been saved as .sav files. Explanation: A previous installation of MQSeries Integrator 2.0 existed and had created the Tool\\Workbook.ini and/or Tool\\working.cfgse files. These files are used by the Control Center and may have been modified to contain user configuration information. Installation may overwrite these files with newly initialized versions, the previous version of these files have been saved in case the values need to be restored. User Response: If you wish to restore the previous versions of Workbook.ini or working.cfg then you should use standard Windows mechanisms to replace them with the .sav versions. It is recommended that if you do this you save the versions of Workbook.ini and working.cfg that you are replacing. BIP8637W You must install all of the prerequisite software listed on this panel before or after this setup. MQSeries Integrator will not work without this prerequisite software. Explanation: The prerequisite software listed was not found in the users system. User Response: You need to install the prerequisite software before or after the setup, otherwise there may be problems running MQSeries Integrator. You are advised to cancel out of this installation and install the prerequisite software before continuing, however you may continue this installation without meeting the prerequisite software requirements. It is possible that, due to changes in the registry key structure of prerequisite products, you may have a valid prerquisite installed that this installation is not recognizing. For this reason you can bypass these prerequisites. BIP8638W The user name that you are installing under (&1) has more than 8 characters. If you continue and use this later to create DB2 databases then you can encounter problems. Explanation: You are using a userid to install that is longer than 8 characters. This may give problems if you later try and create DB2 databases whilst running under this userid. User Response: You can ignore this message and continue, particularly if you are only installing components that do not have a database dependency. If you are going to create databases following this installation, then we suggest that you cancel this installation and sign on with a userid that conforms to DB2 requirements. BIP8639W The account &1 was not found. Do you intend for DB2 Installation to create it? Explanation: You have chosen a User Name for DB2 database administration that does not currently exist on your system. If you continue, then the silent DB2 installation driven by this install will create the userid on your system. User Response: If you want to create a new user with the id specified then select Yes, otherwise select No. BIP8640E A problem was detected in the registry entries for DB2. Please check your registry. Explanation: The install code has detected inconsistencies in the registry structure that it was expecting for DB2. This may be due to a previous DB2 install failure or to corruption of the DB2 entries.

150

MQSeries Integrator Messages

BIP8641W BIP8650I
User Response: If you suspect that the inconsistencies are due to a previous DB2 install failure then you should attempt reinstall of DB2, otherwise you should contact IBM support. BIP8641W DB2 install may have failed to initialize. Explanation: Initialization of the DB2 install may have failed to launch. This may be due to a timeout limit expiring before the initailization file for DB2 was created, or to a corrupt DB2 setup. User Response: Please check your registry entries to confirm that DB2 has failed to install. If it has, please reinstall manually from the setup program on disk. OR The timeout limit may disadvantage slower systems, so please make sure all unnecessary applications are closed down before starting the main MQSeries Integrator installation process. BIP8642W Components installed in a previous version were not included in your choices. These will now be displayed as selected, along with any new selected components. Explanation: You have tried to deselect components during an upgrade install that are currently installed. This is not allowed. User Response: This message is informational - the deselection will be undone automatically. You will need to choose NEXT again. BIP8643E Base product has not been installed. CSD application not possible. Explanation: You are trying to install a CSD on a system where MQSeries Integrator V2 is not currently installed. This is not possible. User Response: Install the base product from its installation media and retry. BIP8644E Unable to create CSD backup directory. Explanation: The backup directory that you specified cannot be created. This may be due to having specified a location for which your userid does not have the correct level of permissions. User Response: You should investigate why this failure occurs by trying to manually create a directory at this location. BIP8645E Unable to update environment variable &1 because of its current size. Explanation: The identified environment variable has grown to a size where the operating system will not allow it to be updated with additional information. This means that there may be an operational failure running the product unless you manually modify the identifed environment variable. User Response: Use system tools to review the current entries in the identified environment variable and remove any that are not required and then add the entries required manually. For example, your PATH variable might contain entries for uninstalled products. BIP8646E Failed to add/include directory to environment. Explanation: As part of the install, the INCLUDE environment variable is updated with the path to the \include subdirectory in order that application developers may build extensions using defined interfaces. This update has failed. User Response: You should manually update the INCLUDE environment variable. If you are developing your application using an IDE then you may be able to access necessary include files by modifying a setting within the IDE. BIP8647E Failed to add include\plugin directory to enviroment variable. Explanation: As part of the install, the INCLUDE environment variable is updated with the path to the include\plugin subdirectory in order that application developers may build extensions using defined interfaces. This update has failed. User Response: You should manually update the INCLUDE environment variable. If you are developing your application using an IDE then you may be able to access necessary include files by modifying a setting within the IDE. BIP8648I This install is a different language to existing install. Explanation: You are installing or upgrading from a previous install and the language entries in the registry show that this install is in a different language to the previous one. User Response: This is for information only, and you should expect that (for example) menu labels change to reflect the new language setting. BIP8649I Please insert the appropriate DB2 support CD. Click Yes when inserted. Click No to bypass DB2 installation. Explanation: Your install is attempting to launch a silent install of the DB2 7.1 product from CD and requires the correct (supplied) CD to be inserted. User Response: If you get this message repeatedly then it is possible that the CD you inserted is either incorrect or is damaged. You can if you wish bypass the DB2 7.1 install and complete it later as a seperate exercise (see DB2 books). BIP8650I Unable to launch the silent DB2 7.1 install. Explanation: Your install is attempting to launch a silent install of the DB2 7.1 product. User Response: If you are installing from CD then check that you have inserted the DB2 CD appropriate to your national langauge. If you are installing from a
Chapter 2. Messages

151

BIP8651I BIP8657I
local hard disk or a remote device then it is likely that the transfer of materials from the CD-ROMs to the expected hard disk directory structure has not been done correctly. Refer to the Installation Manual for more information on this install. Installation will continue, however you may have to manually install DB2. BIP8651I Unable to create log file. Explanation: Install was unable to create a logfile under your Windows NT base directory (normally C:\WINNT). A typical reason for this might be lack of space on the drive. User Response: This is for information only. However you are recommended to cancel the install and investigate the space on your system disk. If it does occur, then it is likely that install will fail at a later point. BIP8652E Unable to create target directory. Explanation: The directory you chose to install the product in could not be created. The usual reason for this is that you have chosen a location to which you dont have the appropriate level of permission. User Response: Choose a different location or obtain the correct level of access. BIP8653E An unexpected error has occurred. Examine install log for more details. Explanation: An unexpected error has been detected by install that is not covered by a more detailed message. This is typically used to provide error coverage for errors that are never expected to happen in practice. Some of these errors will cause the install to fail. User Response: The install log will contain additional details on the error. BIP8654E Unable to create program folder: &1 Explanation: As part of the install, assorted shortcuts are created on the users system. There has been a failure in creating these shortcuts. User Response: You may need to manually add entries into the products program folder. BIP8655E Failed to add \lib directory to LIB environment variable. Explanation: As part of the install the LIB environment variable is updated with a path to the product \lib directory, in order that developers can create extensions to the product. This has failed. User Response: You may need to manually add an entry to the LIB environment variable. BIP8656E Failed to add \bin directory to PATH. Explanation: As part of install, the PATH environment variable is updated to include the path to the \bin directory. This update has failed. The consequence of this is that you will be unable to launch executables installed by this product unless your current or working directory is the \bin directory. User Response: Manually modify the PATH environment variable. BIP8657I Neon Support install failure. Explanation: MQSeries Integrator install launched an install for Neon functionality and this appears to have failed. User Response: You should investigate any messages that may have appeared during the launched Neon install. You can retry the Neon install by manually rerunning setup.exe from within the Neon52 subdirectory on the MQSeries Integrator install media. Examine the autorun.inf file in this directory for the exact location of the setup.exe you need (the Neon52 directory contains many seperate setup.exe files under different sub-directories).

152

MQSeries Integrator Messages

Appendix. Notices
This information was developed for products and services offered in the United States. IBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Copyright IBM Corp. 2000,2001

153

Notices
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM United Kingdom Laboratories, Mail Point 151, Hursley Park, Winchester, Hampshire, England SO21 2JN. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

154

MQSeries Integrator Messages

Notices

Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, or other countries, or both:
AIX FFST MQSeries AS/400 First Failure Support Technology SupportPac DB2 IBM

Lotus is a trademark of Lotus Development Corporation in the United States, or other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark in the United States and/or other countries licensed exclusively through The Open Group. Other company, product, or service names, may be the trademarks or service marks of others.

Appendix. Notices

155

156

MQSeries Integrator Messages

Bibliography
This section describes the documentation available for all current MQSeries Integrator products. MQSeries Integrator for HP-UX Installation Guide, GC34-5907 MQSeries Integrator for Sun Solaris Version 2.0.2 MQSeries Integrator for Sun Solaris Installation Guide, GC34-5842 MQSeries Integrator for Windows NT Version 2.0.2 MQSeries Integrator for Windows NT Installation Guide, GC34-5600 | | | | | | | | | | | | | | | | | | |

MQSeries Integrator Version 2.0.2 cross-platform publications

The MQSeries Integrator cross-platform publications are: v MQSeries Integrator Introduction and Planning, GC34-5599 v MQSeries Integrator Using the Control Center, GC34-5602 v MQSeries Integrator Messages, GC34-5601 v MQSeries Integrator Programming Guide, SC34-5603 v MQSeries Integrator Administration Guide, SC34-5792 v MQSeries Integrator ESQL Reference, SC34-5923 These books are all available in hardcopy. You can order publications from the IBMLink Web site at:
http://www.ibm.com/ibmlink

MQSeries Everyplace publications

If you intend to connect MQSeries Everyplace applications to message flows that include the MQSeries Everyplace message flow nodes, you will find the following publications useful: v MQSeries Everyplace for Multiplatforms Version 1.1 Introduction, GC34-5843 v MQSeries Everyplace for Multiplatforms Version 1.1 Programming Guide, SC34-5845 v MQSeries Everyplace for Multiplatforms Version 1.1 Programming Reference, SC34-5846 v MQSeries Everyplace for Multiplatforms Version 1.1 Native Client Information, SC34-5880 You can find these books on the MQSeries Web site (see MQSeries information available on the Internet on page 159). Translated versions of these books are also available in some languages from the same Web site.

In the United States, you can also order publications by dialing 1-800-879-2755. In Canada, you can order publications by dialing 1-800-IBM-4YOU (1-800-426-4968). For further information about ordering publications contact your IBM authorized dealer or marketing representative.

MQSeries Integrator Version 2.0.2 platform-specific publications

| Each MQSeries Integrator product provides one | platform-specific installation guide, which is | supplied in hardcopy. MQSeries Integrator for AIX Version 2.0.2 MQSeries Integrator for AIX Installation Guide, GC34-5841 MQSeries Integrator for HP-UX Version 2.0.2

NEONRules and NEONFormatter Support for MQSeries Integrator publications

| The following publications are supplied on the | product CD in PDF format, and are installed with | the Documentation component. v NEONRules and NEONFormatter Support for MQSeries Integrator Users Guide v NEONRules and NEONFormatter Support for MQSeries Integrator System Management Guide

Copyright IBM Corp. 2000,2001

157

Bibliography
v NEONRules and NEONFormatter Support for MQSeries Integrator Programming Reference for NEONRules v NEONRules and NEONFormatter Support for MQSeries Integrator Programming Reference for NEONFormatter v NEONRules and NEONFormatter Support for MQSeries Integrator Application Development Guide | These books are provided in US English only. | | | | | | | | | | | | | | | | | | | You can install the library as follows: v On AIX, invoke install d and select the documentation fileset. After installation, run the command mqsidocs. This launches Acrobat Reader and opens the PDF package. v On HP-UX, invoke swinstall d and select MQSI-DOCS from the menu. After installation, run the command mqsidocs. This launches Acrobat Reader and opens the PDF package. v On Sun Solaris, invoke pkgadd d and select mqsi-docs from the menu. After installation, run the command mqsidocs. This launches Acrobat Reader and opens the PDF package. v On Windows NT, select the Online Documentation component on a custom installation, or do a full installation. After installation, select Start>Programs>IBM MQSeries Integrator 2.0>Documentation. In addition, PDF files for books that have been translated are installed into the location mqsi_root/bin/book/pdf/<locale> (on UNIX) or mqsi_root\bin\book\pdf\<locale> (on Windows NT) where <locale> is one of the following: v de_DE for German v en_US for US English v es_ES for Spanish v fr_FR for French v it_IT for Italian v ja_JP for Japanese v ko_KR for Korean v pt_BR for Brazilian Portuguese | | | | | | | | | | | | | | | | | | | | | | | | | | | | | v zh_CN for Simplified Chinese v zh_TW for Traditional Chinese An index file (in HTML format) that provides a link to each book is supplied for each language. For example, the French index file is called indexfr.htm. The files are stored in the following directory: v On UNIX, <mqsi_root>/docs/ v On Windows NT, <mqsi_root>\bin\book Each index file has an entry for every book: if a particular book has not been translated into the appropriate language for that index file, a link to the English PDF is included. You can use any Web browser to view the index file. On Windows NT, you can also access the index file through the Start menu. The PDF file names for the English books are shown in Table 1.
Table 1. File names of MQSeries Integrator book PDFs
Book title MQSeries Integrator for AIX Installation Guide MQSeries Integrator for HP-UX Installation Guide MQSeries Integrator for Sun Solaris Installation Guide MQSeries Integrator for Windows NT Installation Guide MQSeries Integrator Introduction and Planning MQSeries Integrator Administration Guide File name bipaac04.pdf bipcac00.pdf bip7ac03.pdf bipyac03.pdf bipyab02.pdf bipyag04.pdf

Softcopy books
All the MQSeries Integrator books are available in softcopy formats.

Portable Document Format (PDF)

| | | All books in the MQSeries Integrator library are supplied in US English only in a searchable PDF library on the product CD.

| | | | | | | |

MQSeries Integrator Using the Control bipyar03.pdf Center MQSeries Integrator ESQL Reference MQSeries Integrator Programming Guide MQSeries Integrator Messages bipyae00.pdf bipyal02.pdf bipyao02.pdf

| | | | | | | | | | | | |

The fifth character of the file name indicates the language of the book (a indicates US English). You can deduce the file names of translated books by using the following substitutions for the fifth character: v g for German v s for Spanish v f for French v i for Italian

158

MQSeries Integrator Messages

Bibliography
| | | | | v v v v v j for Japanese k for Korean b for Brazilian Portuguese z for Simplified Chinese t for Traditional Chinese
http://www.ibm.com/software/mqseries/

MQSeries information available on the Internet

The MQSeries product family Web site is at:
http://www.ibm.com/software/mqseries/

PDF files can be viewed and printed using the Adobe Acrobat Reader. | | | | | If you cut and paste examples of commands from PDF files to a command line for execution, you must check that the content is correct before you press Enter. Some characters might be corrupted by local system and font settings. If you need to obtain the Adobe Acrobat Reader, or would like up-to-date information about the platforms on which the Acrobat Reader is supported, visit the Adobe Systems Inc. Web site at:
http://www.adobe.com/

By following links from this Web site you can: v Obtain latest information about the MQSeries product family. v Access the MQSeries books in HTML and PDF formats. | v Obtain information about complementary offerings by following these links: | IBM Business Partners | Partner Offerings (within Related links) | v Download an MQSeries SupportPac.

PDF versions of all current MQSeries Integrator books are also available from the MQSeries product family Web site at:

Bibliography

159

MQSeries on the Internet

160

MQSeries Integrator Messages

Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.

GC34-5601-02