BIP0000-0999: Toolkit
- BIP0095
- SCRIBBLE subscriber has stopped receiving messages.
- BIP0110
- An Internal Error has occurred.
- Severity
- 20 : Error
- Explanation
- An Unknown Internal Error has occurred.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0111
- An error has occurred while saving <insert_0>.
- Severity
- 20 : Error
- Explanation
- Either the file has been edited with a Text Editor, or another application has corrupted the file.
- BIP0112
- An internal error occurred while deleting the resource.
- Severity
- 20 : Error
- Explanation
- The file could be read only, or is locked by another process.
- BIP0113
- An internal error occurred while applying your changes.
- Severity
- 20 : Error
- Explanation
- Either a value that was entered was incorrect or an unknown internal error was found.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0114
- Incorrect Parameters were supplied.
- Severity
- 20 : Error
- Explanation
- Incorrect parameters were supplied.
n This is an internal error.
The method was: <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0115
- An error occurred while trying to open the editor.
- Severity
- 20 : Error
- Explanation
- An error occured opening file <insert_0>.
Either the file is corrupted or has been modified by another application.
- BIP0116
- Error creating Message Definition File.
- Severity
- 20 : Error
- Explanation
- An error occured while creating <insert_0>.
Unable to write to the local file system: <insert_0>
- Response
- Refresh the workspace.
- BIP0117
- There was an error loading plugin <insert_0>.
- Severity
- 20 : Error
- Explanation
- Something went wrong while loading plugin <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0118
- Error creating Message Set Resource.
- Severity
- 20 : Error
- Explanation
- An error occured while creating <insert_0>.
Unable to write to the local file system: <insert_0>
- Response
- Refresh the workspace.
- BIP0119
- Error validating resource <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured while building resource <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0120
- Error loading XML Schema file <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured wrong while loading the XML Schema file <insert_0> Refresh the workspace.
- BIP0121
- Error generating WSDL File.
- Severity
- 20 : Error
- Explanation
- An error occured while generating WSDL file <insert_0>.
Unable to write to the local file system: <insert_0>
- Response
- Refresh the workspace.
- BIP0122
- Error updating Message Set Cache file for Message Set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured while updating the Message Set Cache file for Message Set <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0123
- Error saving Message Set Cache file <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured while saving the Message Set Cache file <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0124
- An error occurred while retrieving properties for <insert_0>.
- Severity
- 20 : Error
- Explanation
- An unexpected error occured while retrieving properties for <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0125
- Error creating Message Set Project.
- Severity
- 20 : Error
- Explanation
- An error occured while creating Message Set Project <insert_0>.
- Response
- Unable to write to the local file system: <insert_0>
nRefresh the workspace.
- BIP0126
- Error creating Message Category File.
- Severity
- 20 : Error
- Explanation
- An error occured while creating <insert_0>.
- Response
- Unable to write to the local file system: <insert_0>
nRefresh the workspace.
- BIP0127
- Error loading Message Set Cache file for Message Set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured while loading the Message Set Cache file.
- Response
- Perform a full build and if the problem persists turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0128
- Error renaming wire format <insert_0> in message set <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occured while renmaing wire format <insert_0>.
Unable to write to the local file system.
nReplace existing message set version with local history version and retry the operation and if the problem persists contact your IBM support center.
- BIP0129
- An Internal Message Set Compile Error has occurred.
- Severity
- 20 : Error
- Explanation
- An Unexpected Exception <insert_0>, the message was <insert_1>. Check the user log for details of the error. Retry the operation and contact your IBM support center.
- BIP0130
- Command completed.
- Severity
- 0 : Information
- Explanation
- Refer to report file for details of what was imported.
- BIP0131
- Command did not complete.
- Severity
- 20 : Error
- Explanation
- See earlier error messages for details of the problem.
- BIP0132
- Incorrect arguments supplied to mqsimigratemsgsets.
- Severity
- 20 : Error
- Explanation
- You must supply -d <directoryName>.
- BIP0133
- Error accessing directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- Please ensure the specified directory exists and that you have read access.
- BIP0134
- Empty directory <insert_0>.
- Severity
- 10 : Warning
- Explanation
- No files with extension "mrp" were found in the specified directory.
- BIP0135
- Error creating report file.
- Severity
- 20 : Error
- Explanation
- A problem was encountered creating the <insert_0> file. If the -log option was specified please ensure the filepath is correct. Otherwise if this problem persists please contact your IBM Support Center.
- BIP0136
- A project already exists for message set <insert_0>, ignoring message set.
- Severity
- 10 : Warning
- Explanation
- If you intend to replace this project, either delete it and retry the operation, or rerun the command with the -rm option.
- BIP0137
- An unexpected exception has occurred.
- Severity
- 20 : Error
- Explanation
- An exception was caught in method <insert_0>, details are: <insert_1>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0138
- Migrate message sets from a 2.1 export file format.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsimigratemsgsets
-data <workspace> Workspace location
-d <dirpath> Directory path (full or relative) containing .mrp export files
-rm Replace message set projects if they already exist (optional)
-v Produce verbose report (optional)
-g Create all elements and types as global (optional)
-part Partition a .mrp file into many message definition files (optional)
-log <filepath> Report file (optional)
-pl Elements with prefixed identifiers always created as local elements (optional)
- BIP0139
- A problem was encountered migrating export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. Refer to the report file for details of the problem.
- BIP0140
- Incorrect arguments supplied to mqsimigratemsgsets.
- Severity
- 20 : Error
- Explanation
- If you specify -log you must supply the name of a report file.
- BIP0141
- Parsing of export file terminated, SAX parsing error <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0142
- Validation failure: Missing value reference in Element <insert_0> MRValueMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0143
- Validation failure: Unresolved MRValueRef in Element <insert_0> MRValueMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0144
- Validation failure: Unresolved MRValidValueRef in Element <insert_0> MRValueMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0145
- Validation failure: Missing object reference in Compound Type <insert_0> MRTypeMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0146
- Validation failure: Unresolved MRElementRef in Compound Type <insert_0> MRTypeMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0147
- Validation failure: Unresolved MRMessageRef in Compound Type <insert_0> MRTypeMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0148
- Validation failure: Unresolved MRCompoundRef in Compound Type <insert_0> MRTypeMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0149
- Validation failure: Missing object reference in Category <insert_0> MRCategoryMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0150
- Validation failure: Unresolved MRTransactionRef in Category <insert_0> MRCategoryMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0151
- Validation failure: Unresolved MRMessageRef in Category <insert_0> MRCategoryMember
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0152
- Validation failure: Missing type reference in Element <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0153
- Validation failure: Unresolved MRCompoundRef in Element <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0154
- Validation failure: Missing MRCompoundRef reference in Message <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0155
- Validation failure: Unresolved MRCompoundRef in Message <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0156
- Validation failure: Missing MRSimpleRef in Element Value <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0157
- Validation failure: Unresolved MRLengthRef in Element <insert_0>
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is that the export file has been manually edited. Export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0158
- Unreferenced Element Length <insert_0> not imported
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0159
- Unreferenced Element Valid Value <insert_0> not imported
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0160
- Unreferenced Element Value <insert_0> not imported
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0161
- Compound Type <insert_0> has a base type, please refer to help for details of how this is migrated
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0162
- Member message <insert_0> min/max occurs set to 1
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0163
- Ignoring invalid value <insert_0> for property <insert_1>, object <insert_2>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0164
- Ignoring unknown or dropped property <insert_0>, object <insert_1>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0165
- Value Constraint role <insert_0> not migrated for Element <insert_1> of type <insert_2>
- Severity
- 10 : Warning
- Explanation
- <Spare>
- BIP0166
- Ignoring Element qualification in Message <insert_0>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0167
- Element Qualifiers encountered, not migrated
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0168
- Ignoring unresolved default wire format <insert_0>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0169
- Message Set state of frozen not supported, ignoring
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0170
- Message Set state of finalized not supported, ignoring
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0171
- Message Set level > 1 not supported, Message Set name is distinguished instead
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0172
- Message Set basing not supported, dependency information not migrated
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0173
- C Language Binding not supported, binding not migrated
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0174
- COBOL Language Binding not supported, binding not migrated
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0175
- The Date Template for Element <insert_0> does not match a Schema simple type, using xsd:datetime or xsd:time instead
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0176
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Namespace <insert_0> is used in this dictionary. Namespaces are not supported by brokers earlier than Version 5. The path to the object which uses the
amespace is <insert_1>.
- BIP0177
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- This message set has namespace support enabled. Namespaces are not supported by brokers earlier than Version 5.
- BIP0178
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> uses Daylight Savings Time (DST). DST is not supported by brokers earlier than Version 5.
- BIP0179
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Custom Wire Format <insert_0> uses Trailing Skip Count. Trailing Skip Count is not supported by brokers earlier than Version 5. The path to the object is <insert_1>.
- BIP0180
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- XML Wire Format <insert_0> uses NullXMLSchema to handle null values. NullXMLSchema is not supported by brokers earlier than Version 5.
- BIP0181
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- XML Wire Format <insert_0> uses Namespace <insert_1>. Namespaces are not supported by brokers earlier than Version 5. The path to the object which uses the
amespace is <insert_2>.
- BIP0182
- Message Set compile error.
- Severity
- 20 : Error
- Explanation
- A exception was thrown while compiling the Message Set. The cause of the error was an exception of type <insert_0>, with message <insert_1>. The stack trace at the time of the error was:
<insert_2>
nRetry the operation and contact your IBM support center.
- BIP0183
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> uses Strict Datetime Checking. This option is not supported by brokers earlier than Version 5.
- BIP0184
- Invalid Rendering option detected for Element <insert_0> in wire format <insert_1>
- Severity
- 20 : Error
- Explanation
- Elements or element references of complex types can only be rendered as XMLElement or XMLElementAttrID.
- Response
- Modify the rendering options and regenerate the schema.
- BIP0185
- Invalid Rendering option detected for Element reference <insert_0> in wire format <insert_1>
- Severity
- 20 : Error
- Explanation
- Elements or element references of complex types can only be rendered as XMLEleemnt or XMLElementAttrID.
- Response
- Modify the rendering options and regenerate the schema.
- BIP0186
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> has Suppress Absent Element Delimiters set to a value other than "End Of Type". This option is not supported by brokers earlier than Version 5. The path to the object is <insert_1>.
- BIP0187
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> has Suppress Absent Element Delimiters set to a value other than EndOfType at the message set level. This option is not supported by brokers earlier than Version 5.
- BIP0188
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Datetime Value <insert_0> is used in this dictionary. Datetimes with time zones set are not supported by brokers earlier than Version 5. The path to the object which uses the Datetime value is <insert_1>.
- BIP0189
- This dictionary requires a Version 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- This dictionary contains a facet or value constraint with an integer which is outside the 32-bit range.". Brokers earlier than Version 5 do not support 64-bit integer values in facets or value constraints. The name of the object which uses the 64-bit value is <insert_0>.
- BIP0190
- Ignoring SWIFT, EDIFACT or X12 "Delimiter" message set property value <insert_0>, it had no effect
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0191
- Replacing dropped composition "simple unordered set" with "all", Compound Type <insert_0>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0192
- Replacing dropped composition "simple unordered set" with "unorderedSet", Compound Type <insert_0>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0193
- Replacing dropped composition "empty" with an empty "sequence", Compound Type <insert_0>
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0194
- This is a large message set, you should consider using the -part option to create multiple message definition files
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0195
- Element <insert_0> is referenced more than once and so is global. This is a misuse of prefixed identifiers and could result in duplicate elements being created.
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0196
- Could not create physical format <insert_0>.
- Severity
- 20 : Error
- Explanation
- The export file for this message set can not be processed. The most likely reason for this is a duplicate physical format identifier. If so this will be indicated by preceding informational messages in the report. Correct the message set, export the message set again and retry the operation. If this error still occurs contact your IBM Support Center.
- BIP0197
- This dictionary requires a Version 5 Fix Pack 2 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Custom Wire Format <insert_0> uses 8 byte integers. This option is not supported by brokers earlier than Version 5 Fix Pack 2. The path to the object is <insert_1>.
- BIP0198
- This dictionary requires a Version 5 Fix Pack 2 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Custom Wire Format <insert_0> uses Packed Decimals with lengths greater than 6 bytes. This option is not supported by brokers earlier than Version 5 Fix Pack 2. The path to the object is <insert_1>.
- BIP0199
- This dictionary requires a Version 5 Fix Pack 2 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Custom Wire Format <insert_0> uses External Decimals with lengths greater than 11 bytes. This option is not supported by brokers earlier than Version 5 Fix Pack 2. The path to the object is <insert_1>.
- BIP0200
- This dictionary requires a Version 5 Fix Pack 2 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Element or attribute <insert_0> uses schema simple type "xsd:duration". This type is not supported by brokers earlier than Version 5 Fix Pack 2. The path to the object is <insert_1>.
- BIP0201
- This dictionary requires a Version 5 Fix Pack 3 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Custom Wire Format <insert_0> uses External Decimals with Sign EBCDIC Custom representation. This option is not supported by brokers earlier than Version 5 Fix Pack 3. The path to the object is <insert_1>.
- BIP0202
- This dictionary requires a Version 5 Fix Pack 3 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- TDS Format <insert_0> uses "Strict Numeric Checking". This option is not supported by brokers earlier than Version 5 Fix Pack 3.
- BIP0203
- This dictionary requires a Version 5 Fix Pack 4 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- TDS Format <insert_0> uses "Observe Element Length". This option is not supported by brokers earlier than Version 5 Fix Pack 4 The path to the object is <insert_1>.
- BIP0204
- This dictionary requires a Version 5 Fix Pack 4 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- TDS Format <insert_0> uses TLOG Message Standard. This option is not supported by brokers earlier than Version 5 Fix Pack 4.
- BIP0205
- This dictionary requires a Version 5 Fix Pack 4 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- CWF Format <insert_0> uses "Output Policy For Missing Elements" set to a value other than "Use Default Value". This option is not supported by brokers earlier than Version 5 Fix Pack 4.
- BIP0206
- This dictionary requires a Version 5 Fix Pack 4 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- CWF Format <insert_0> uses elements with the "Encoding Null" property set to "NullLiteralFill". This option is not supported by brokers earlier than Version 5 Fix Pack 4. The path to the object is <insert_1>
- BIP0207
- This dictionary requires a Version 5 Fix Pack 5 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- TDS Format <insert_0> uses HL7 Messaging Standard. This option is not supported by brokers earlier than Version 5 Fix Pack 5.
- BIP0208
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- CWF Format <insert_0> uses elements/groups with an unbounded number of repeats. This option is not supported by brokers earlier than Version 6. The path to the object is <insert_1>
- BIP0209
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Message <insert_0> has a Message Alias specified. This option is not supported by brokers earlier than Version 6.
- BIP0210
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- You must supply -d <sourceFilesDirectory>.
- BIP0211
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- No source directory specified after -d.
- BIP0212
- Error accessing source files directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- Please ensure the specified directory exists and that you have read access.
- BIP0213
- Empty directory <insert_0>.
- Severity
- 10 : Warning
- Explanation
- No C/COBOL/DTD/XSD files found in the specified directory.
- BIP0214
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- You must supply -p <messageSetProjectName>.
- BIP0215
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- No message set project name specified after -p.
- BIP0216
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- -log specified but no report file name supplied.
- BIP0217
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- -opt specified but no options file supplied.
- BIP0218
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- Invalid options file pathname <insert_0>.
- BIP0219
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- -base specified but no base message set name supplied.
- BIP0220
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- Invalid base message set name <insert_0>.
- BIP0221
- Import C/COBOL/DTD/XSD files to generate message definitions.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsicreatemsgdefs
-data <workspace> Workspace location
-p <messageSetProjectName>, will be created if it does not exist
-base <baseMessageSetProjectName&bsl;baseMessageSetName> (optional)
-d <sourceFilesDirectory> (absolute/relative) containing C/COBOL/DTD/XSD files
-rmp Replace message set project if it already exists (optional)
-rmd Replace message definitions if they already exist (optional)
-ns Namespace aware if creating new message set (optional)
-msg Create messages from complex global elements (optional)
-v Produce verbose report (optional)
-opt <importPropertiesFilePath> (absolute/relative) (optional)
-log <reportFileName> (optional)
- BIP0222
- Message definition with the same name already exists, ignoring source file <insert_0>.
- Severity
- 10 : Warning
- Explanation
- If you intend to replace this message definition, either delete it and retry the operation, or rerun the command with the -rmd option.
- BIP0223
- The message set has no Custom Wire Format layer defined. Only the logical information will appear in the model.
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0224
- The message set has no XML Wire Format layer defined. Only the logical information will appear in the model.
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0225
- Command completed.
n Refer to file <insert_0> for details of what was imported.
- Severity
- 0 : Information
- Explanation
- <Not used>
- BIP0226
- Command did not complete.
- Severity
- 20 : Error
- Explanation
- See earlier error messages for details of the problem.
- BIP0227
- Error loading import options file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Please make sure the specified options file a valid XML file.
- BIP0228
- Error loading import options file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Missing or invalid option for <insert_0>: <insert_1>.
- BIP0229
- Empty message set project <insert_0>.
- Severity
- 20 : Error
- Explanation
- Please make sure the specified message set project has a message set in it.
- BIP0230
- Message set project <insert_0> already exists.
- Severity
- 20 : Error
- Explanation
- Please make sure the message set project specified for -p does not exist when -base <baseMsetProjbaseMsetName> is specified, or use the -rmp option to
eplace the existing project.
- BIP0231
- A problem was encountered importing file <insert_0>.
- Severity
- 20 : Error
- Explanation
- No message definition can be generated for this source file. Refer to the report file for details of the problem.
- BIP0232
- Error occurred while creating message defintiion.
- Severity
- 20 : Error
- Explanation
- An internal error has occured while importing <insert_0>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0233
- Error occurred while creating message set <insert_0>.
- Severity
- 20 : Error
- Explanation
- An exception was caught in method <insert_0>, details are: <insert_1>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0234
- Error occurred while importing file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The source file contains errors, details are: <insert_1> Please correct the error and try importing the file again.
- BIP0235
- The message set has no namespace support. The imported XML Schema will be modified to remove namespaces.
- Severity
- 10 : Warning
- Explanation
- <Not used>
- BIP0236
- Error occured while creating message definition.
- Severity
- 20 : Error
- Explanation
- <insert_0> cannot be imported since it contains unsupported features.
<insert_1>
- BIP0237
- Error loading import options file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Missing uri and/or prefix attributes in URI_PREFIX_PAIRS.
- BIP0238
- Error occured while importing file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The file cannot be renamed to form a valid message artifact file name.
- BIP0239
- Byte alignment for elements referenced in the complex type <insert_0> may not be correct.
- Severity
- 10 : Warning
- Explanation
- Byte alignment should be fixed by editing the file through the message definition editor.
Probable cause: Element in the COBOL copy book has OCCURS DEPENDING ON clause.REA239 = <Not used>
- BIP0240
- An unexpected exception has occurred while importing a COBOL file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check the COBOL copybook is valid by ensuring it compiles on the system from which it was obtained. Correct any errors and try importing the file again. If this problem persists, contact your IBM Support Center.
- BIP0241
- An unexpected exception has occurred while importing a C file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Check the C file is valid by ensuring it compiles on the system from which it was obtained. Correct any errors and try importing the file again. If this problem persists, contact your IBM Support Center.
- BIP0242
- The source C file name is invalid: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Rename the C file so that it does not contain any of the following characters <insert_', '%', ''', '#', '>. Correct any errors and try importing the file again.
- BIP0243
- The source COBOL file name is invalid: <insert_0>.
- Severity
- 20 : Error
- Explanation
- Rename the COBOL file so that it does not contain any of the following characters <insert_', '%', ''', '#', '>. Correct any errors and try importing the file again.
- BIP0250
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- An element/attribute has the "Interpret Value As" property set to a value other than "None". This option is not supported by brokers earlier than Version 6. The path to the object is <insert_0>
- BIP0251
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> sets XML version to <insert_1>. Only XML version 1.0 is supported by brokers earlier than Version 6.
- BIP0252
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> sets Suppress XML Encoding to false. Generation of the XML declaration "encoding" attribute is not supported by brokers earlier than Version 6.
- BIP0253
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical format <insert_0> has XML "Output policy for xsi:type attributes" set to a value other than "When Present". This option is not supported by brokers earlier than Version 6.
- BIP0254
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Physical Format <insert_0> has the "Use Input UTC Format on Output" property set to true. This option is not supported by brokers earlier than Version 6.
- BIP0255
- This dictionary requires a Version 6 (or later) broker.
- Severity
- 10 : Warning
- Explanation
- Message <insert_0> has XML "Output policy for xsi:type attributes" set to a value other than "When Present". This option is not supported by brokers earlier than Version 6.
- BIP0256
- Error details are
<insert_0>
- Severity
- 20 : Error
- Explanation
- <Not used>
- BIP0257
- Within a message set, a message name <insert_0> and a message alias must be unique.
- Severity
- 20 : Error
- Explanation
- A message alias or message name cannot have the same value as any other message name or message alias within the message set.
- BIP0258
- Incorrect arguments supplied to mqsicreatemsgdefs.
- Severity
- 20 : Error
- Explanation
- You must supply -data <workspaceDirectory>.
- BIP0259
- Incorrect arguments supplied to mqsimigratemsgsets.
- Severity
- 20 : Error
- Explanation
- You must supply -data <workspaceDirectory>.
- BIP0310
- Error occurred while generating XML schema.
- Severity
- 20 : Error
- Explanation
- An internal error occured while creating <insert_0>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0311
- Error occurred while generating XML schema.
- Severity
- 20 : Error
- Explanation
- An internal error occured while trying to locate attribute <insert_0> in namespace <insert_1>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0312
- Error occurred while generating XML schema.
- Severity
- 20 : Error
- Explanation
- An internal error occured while trying to locate element <insert_0> in namespace <insert_1>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0313
- Error loading MXSD file <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occured wrong while loading the MXSD file <insert_0> Refresh the workspace.
- BIP0320
- Error occurred while generating HTML documentation.
- Severity
- 20 : Error
- Explanation
- An internal error occured while documentation. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0330
- Error creating WSDL definitions.
- Severity
- 20 : Error
- Explanation
- An internal error occured while generating WSDL definitions for message set <insert_0>. If this problem persists, turn on tracing to capture details of the error. Retry the operation and contact your IBM Support Center.
- BIP0331
- Error importing WSDL File.
- Severity
- 20 : Error
- Explanation
- An error occured while creating <insert_0> for the following reason: <insert_1>
- Response
- See report log for more details.
- BIP0610
- Import a WSDL file to generate a message definition.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsicreatemsgdefsfromwsdl
-data <workspace> Workspace location
-p <messageSetProjectName>, will be created if it does not exist
-base <baseMessageSetProjectName&bsl;baseMessageSetName> (optional)
-d <sourceFilesDirectory> (absolute/relative) containing WSDL files
-f <wsdlFile> (absolute/relative to -d) The wsdl file to import
-binding <bindingName> (optional if wsdl contains only one binding)
-rmp Replace message set project if it already exists (optional)
-rmd Replace message definitions if they already exist (optional)
-v Produce verbose report (optional)
-log <reportFileName> (optional)
-vfa <wsi-validation-action>, where the action is one of "ignore", "warn", or "fail" (optional)
- BIP0611
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- You must supply -d <sourceFilesDirectory>.
- BIP0612
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- No source directory specified after -d.
- BIP0613
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- You must supply -p <messageSetProjectName>.
- BIP0614
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- No message set project name specified after -p.
- BIP0615
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- You must supply -f <wsdlFile>.
- BIP0616
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- No wsdl file specified after -f.
- BIP0617
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- -log specified but no report file name supplied.
- BIP0618
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- -base specified but no base message set name supplied.
- BIP0619
- Invalid arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- The provided WSDL <insert_0> contains no bindings. The WSDL to import must contain at least one binding.
- BIP0620
- Invalid arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- -binding was not specified however the wsdl being imported has multiple bindings. Specify the binding to import and re-run the tool.
- BIP0621
- Invalid arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- The binding name <insert_0> does not exist in the WSDL definition
- BIP0622
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- Invalid base message set name <insert_0>.
- BIP0623
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- -binding specified but no binding name supplied.
- BIP0624
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- -vfa specified but no WSI validation action supplied.
- BIP0625
- Incorrect arguments supplied to mqsicreatemsgdefsfromwsdl.
- Severity
- 20 : Error
- Explanation
- You must supply -data <workspaceDirectory>.
- BIP0800
- An unexpected exception occurred: <insert_0>
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0801
- An unexpected exception occurred: <insert_0>
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred but provided no additional information.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0810
- An error occurred while saving file <insert_0>.
- Severity
- 20 : Error
- Explanation
- An exception occurred and the file is not saved.
- Response
- Resolve the reason of error and try again.
- BIP0811
- The file <insert_0> refers some inaccessible resources.
- Severity
- 20 : Error
- Explanation
- Unloadable resources and mappings associated with them will be removed from this file at next save.REA811 =
Some of the referenced resources cannot be loaded.
- Response
- Refer to task list for more information.
- BIP0812
- The file <insert_0> cannot be loaded.
- Severity
- 20 : Error
- Explanation
- Some error occurred while loading this file.
- Response
- Refer to task list for more information.
- BIP0813
- The resource <insert_0> cannot be created.
- Severity
- 20 : Error
- Explanation
- Unable to write to the local file system: <insert_0>
- Response
- Refresh the workspace.
- BIP0814
- The resource <insert_0> cannot be created.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>.
- Response
- Resolve the reason of error and try again.
- BIP0815
- The container at <insert_0> cannot be accessed.
- Severity
- 20 : Error
- Explanation
- Either the resource does not exist or it is a closed project.
- Response
- If the resource is a closed project, open it. Otherwise, refresh your workspace and try again.
- BIP0816
- The resource <insert_0> could not be <insert_1>.
- Severity
- 20 : Error
- Explanation
- The workspace is out of synch with the local file system.
- Response
- Refresh your workspace and try again.
- BIP0817
- The resource <insert_0> could not be <insert_1>.
- Severity
- 20 : Error
- Explanation
- Unable to read the resource from the local file system. Another application might be preventing this resource from being accessed.
- Response
- Close other applications that are accessing the resource and try again.
- BIP0818
- The resource <insert_0> could not be <insert_1>.
- Severity
- 20 : Error
- Explanation
- Unable to write the resource to the destination in the local file system. This resource may already exist in the file system.
- Response
- Refresh your workspace and try again.
- BIP0819
- The resource <insert_0> could not be <insert_1>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0820
- Unable to delete resources.
- Severity
- 20 : Error
- Explanation
- The workspace is out of synch with the file system.
- Response
- Refresh your workspace and try again.
- BIP0821
- Unable to delete resources.
- Severity
- 20 : Error
- Explanation
- Unable to access one of the selected resources. Another application might be preventing this resource from being accessed.
- Response
- Close other applications that are accessing the resources being deleted and try again.
- BIP0822
- Unable to delete resources.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0823
- An error occurred while saving file <insert_0>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0824
- The resource <insert_0> could not be loaded.
- Severity
- 20 : Error
- Explanation
- The resource no longer exists on the file system.
- Response
- Refresh your workspace and then recreate the resource or re-add it from the repository.
- BIP0825
- The resource <insert_0> could not be loaded.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0826
- The resource <insert_0> could not be loaded.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Recreate the resource or replace it with a saved version from the
epository.
- BIP0827
- The palette could not be generated.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Retry the operation and contact your IBM support center.
- BIP0828
- The class <insert_0> could not be loaded.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Close and then reopen the workbench and try again.
- BIP0829
- Unable to load the selected wizard.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Ensure the wizard's plugin is installed correctly, restart the workbench and try again.
- BIP0830
- Unable to locate the selected marker.
- Severity
- 20 : Error
- Explanation
- Marker <insert_0> does not exist.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0831
- The resource <insert_0> could not be accessed.
- Severity
- 20 : Error
- Explanation
- The workspace is out of synch with the local file system.
- Response
- Refresh your workspace and try again.
- BIP0832
- The resource <insert_0> could not be accessed.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0833
- The resource <insert_0> could not be accessed.
- Severity
- 20 : Error
- Explanation
- Unable to access the resource on the local file system. Another application might be preventing this resource from being accessed.
- Response
- Close other applications that are accessing the resource and try again.
- BIP0834
- The resource <insert_0> could not be closed.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- Resolve the reason of error and try again.
- BIP0835
- Unable to alter schema paths.
- Severity
- 20 : Error
- Explanation
- The current ESQL source code cannot be parsed correctly.
- Response
- Resolve the syntax error and try again.
- BIP0836
- The action could not be performed on the resources.
- Severity
- 20 : Error
- Explanation
- Exceptions occurred and provided the following information.
- Response
- Resolve the reason of error and try again.
- BIP0837
- Migrate message flows from a 2.1 export file format.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsimigratemsgflows
-data <workspace> Workspace location
-p <projectName> The name of the project to use or create
-d <dirpath> Directory path (full or relative) containing the flow export files
-rm Replace message flow projects if they already exist (optional)
-log <filepath> Report file (optional)
- BIP0838
- Unable to start message flows migration.
- Severity
- 20 : Error
- Explanation
- No parameters were supplied to the mqsimigratemsgflows command.
Correct and reissue the command.
- BIP0839
- Incorrect arguments supplied to mqsimigratemsgflows.
- Severity
- 20 : Error
- Explanation
- You must supply -p <projectName>.
- BIP0840
- Incorrect arguments supplied to mqsimigratemsgflows.
- Severity
- 20 : Error
- Explanation
- You must supply -d <dirPath>.
- BIP0841
- The resource <insert_0> could not be added to broker archive file <insert_1>.
- Severity
- 20 : Error
- Explanation
- Compile errors occurred in the following resource: <insert_0>
Rebuild your project and try again.
- BIP0842
- The message flow application <insert_0> could not be added to broker archive file <insert_1>.
- Severity
- 20 : Error
- Explanation
- Internal exceptions occurred in the <insert_0> plugin
Resolve the reason of error and try again.
- BIP0843
- Unable to use exported flows directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified directory does not exist.
Specify an existing exported message flows directory.
- BIP0844
- Unable to use exported flows directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified directory is in fact a file.
Specify an existing exported message flows directory.
- BIP0845
- Unable to use exported flows directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified directory is not readable.
Ensure the directory has sufficient read permissions.
- BIP0846
- Unable to find exported flows in directory <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified directory does not contain any file.
Specify an existing exported message flows directory.
- BIP0847
- Unable to create the migration report file.
- Severity
- 20 : Error
- Explanation
- The mqsimigratemsgflows command was unable to create the report file
in the current working directory.
Verify you can create any text file in the current working directory.
- BIP0848
- Unable to parse message flow export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message:
<insert_1>.
The export file must be a well formed XML file.
- BIP0849
- Unable to migrate message flow export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message:
<insert_1>.
- BIP0850
- Unable to migrate message flow export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message:
<insert_1>.
Ensure the file has read permission and no other application is accessing it.
- BIP0851
- Unable to create project <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified project does not exist and cannot be created.
Specify an existing project or a project with a valid name.
- BIP0852
- Unable to use existing project <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified project is not a message flow project.
Specify an existing message flow project
or a non-existing project with a valid name.
- BIP0853
- The resource <insert_0> could not be added to broker archive file <insert_1>.
- Severity
- 20 : Error
- Explanation
- Internal errors occurred while compiling the following resource: <insert_0>
Resolve the reason of error and try again.
- BIP0854
- An unexpected exception occurred: <insert_0>.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred while processing the following resource: <insert_1>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0855
- Unable to migrate message flow export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message flow export file is empty.
Ensure the file is not damaged and has appropriate read permissions.
- BIP0856
- Unable to migrate message flow export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message flow export file is not readable.
Ensure the file has appropriate read permissions.
- BIP0857
- Selected Execution Group(s) associated to broker <insert_0> cannot be deleted.
- Severity
- 20 : Error
- Explanation
- A Broker must contain at least one Execution Group.
Unselect one or more execution groups or create another execution group and retry the operation.
- BIP0858
- Unable to create message flow <insert_0> in workspace.
- Severity
- 20 : Error
- Explanation
- The migrate command could not write the new message flow.
The following error message was issued by the workspace:
<insert_0>.
Verify you are able to create files in the project.
- BIP0859
- The message flow name <insert_0> is invalid.
- Severity
- 10 : Warning
- Explanation
- The migrate command cannot use the flow name as the file name.
The flow name has been changed to <insert_0>.
You may later rename the flow from the Message Brokers Toolkit.
- BIP0860
- Numeric conversion from string <insert_0> to type double failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
- BIP0861
- Numeric conversion from string <insert_0> to type long failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
- BIP0862
- Numeric conversion from string <insert_0> to type float failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
- BIP0863
- Numeric conversion from string <insert_0> to type integer failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
- BIP0864
- The plugin [<insert_0>] failed to complete its configuration tasks.
- Severity
- 20 : Error
- Explanation
- A unexpected runtime exception [<insert_0>] occurred whilst performing task [<insert_1>].
- Response
- <insert_2>
Resolve the reason of error and try again.
Be aware your runtime may now be in an incomplete state.
- BIP0865
- The plugin [<insert_0>] failed to complete a configuration task.
- Severity
- 20 : Error
- Explanation
- An attempt to perform task [<insert_0>], resulted in an error.
- Response
- <insert_1>
<insert_2>
Resolve the reason of error and try again.
Be aware your runtime may now be in an incomplete state.
- BIP0866
- The plugin [<insert_0>] failed to complete its configuration tasks.
- Severity
- 10 : Warning
- Explanation
- The wizards configuration processing was halted by the user.
Processing was halted after the successful completion of task [<insert_0>]
- Response
- <insert_1>
Be aware your runtime may now be in an incomplete state.
- BIP0867
- A dependent subflow or primitive is missing.
- Severity
- 10 : Warning
- Explanation
- The migration command cannot evaluate if a missing flow is a subflow
with terminals or a user defined node. The migration made the assumption
that it was a subflow.
If the subflow was indeed a user defined node, change the extension to .msgnode,
open the message node in the editor, make some changes and save. The message node
will be regenerated correctly.
A flow may not be able to resolve this subflow, if it has been renamed.
In that case, re-export the flows and subflows in the same export file.
Message flow name being migrated: <insert_0>
Missing flow name: <insert_1>
Missing flow uuid: <insert_2>
- BIP0868
- Unable to correctly migrate a promoted property.
- Severity
- 20 : Error
- Explanation
- The migration command cannot locate the node hosting an overridden property.
A placeholder property was substituted to preserve the flow integrity.
Message flow name being migrated: <insert_0>
Promoted property name: <insert_1>
Overridden property name: <insert_2>
After migration, from the Message Brokers Toolkit, promote the property again.
ESQL code reuse has been enhanced significantly and is no longer promotable.
Refer to the ESQL programming guide for further information.
- BIP0869
- Conversion from string <insert_0> to Time failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
The format for an ESQL Time property is: hh:mm:ss.ffffff
- BIP0870
- Conversion from string <insert_0> to Timestamp failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
The format for an ESQL Timestamp property is: yyyy-mm-dd hh:mm:ss.ffffff
- BIP0871
- Conversion from string <insert_0> to Date failed.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
Use Message Brokers Toolkit to open the flow and assign a valid value.
The format for an ESQL Date property is: yyyy-mm-dd
- BIP0872
- Unable to assign a property value.
- Severity
- 20 : Error
- Explanation
- Cannot assign a value for the property <insert_0> from the flow <insert_1>.
The given value is not in the list of the enumeration type.
Property value from the migrated flow: <insert_2>
Property type enumerated choices: <insert_3>
After migration, from the Message Brokers Toolkit, assign a value to the property.
- BIP0873
- An unexpected error occurred while trying to open an editor.
- Severity
- 20 : Error
- Explanation
- An internal error occurred which reported the following message: <insert_0>.
- Response
- Turn on tracing to capture details of the error. Retry the operation and contact your IBM support center.
- BIP0874
- A failure response has been received from Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- A failure response has been received which provided the message(s) detailed below.
- Response
- Editor/Viewer has been refreshed with Configuration Manager content.
- BIP0875
- An unknown type response has been received from Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- An unknown type response has been received which provided the message(s) detailed below.
- Response
- Editor/Viewer has been refreshed with Configuration Manager content.
- BIP0876
- Changes you initiated may conflict with Configuration Manager actual content.
- Severity
- 10 : Warning
- Explanation
- Configuration Manager sent a change notification while you are editing its content.
- Response
- To avoid any potential conflict, close editor without saving.
- BIP0877
- Initiated changes cannot be processed for now.
- Severity
- 10 : Warning
- Explanation
- Configuration Manager did not send yet all expected responses to previous actions.
- Response
- Click OK to stop waiting for these responses and to refresh editor content.
You will then be able to initiate changes.
Click Cancel to go on waiting for Configuration Manager responses to be processed.
- BIP0878
- Paste operation cannot performed as the copied object has been deleted.
- Severity
- 20 : Error
- Explanation
- A previously copied domain object cannot be pasted as it does no longer exist
on the Configuration Manager.
- Response
- Copy a new object before retrying the paste operation.
- BIP0879
- Unable to write an ESQL Module
- Severity
- 20 : Error
- Explanation
- The migrate command could not write an ESQL Module.
Error message from the Message Brokers Toolkit workspace:
<insert_0>
Message flow name being migrated: <insert_1>
Message flow ESQL filename: <insert_2>
Message flow node hosting the ESQL module: <insert_3>
ESQL Module content: <insert_4>
- BIP0880
- Unable to create a connection between two nodes.
- Severity
- 20 : Error
- Explanation
- The migration command cannot connect the node <insert_0>
to the node <insert_1>.
Message flow name being migrated: <insert_2>
After migration, from the Message Brokers Toolkit, edit the flow and connect the two nodes.
- BIP0881
- Unable to restore a connection bend point.
- Severity
- 0 : Information
- Explanation
- The migration command cannot restore a bend point on a connection between
two nodes.
Message flow name being migrated: <insert_0>
After migration, from the Message Brokers Toolkit, edit the flow and reroute the connection.
- BIP0882
- Unable to locate the source node of a connection.
- Severity
- 20 : Error
- Explanation
- The migration command cannot locate the node initiating a connection.
Message flow name being migrated: <insert_0>
Message processing source node UUID: <insert_1>
After migration, from the Message Brokers Toolkit, edit the flow,
locate the source node and reconnect it.
- BIP0883
- Unable to locate the target node of a connection.
- Severity
- 20 : Error
- Explanation
- The migration command cannot locate the node ending a connection.
Message flow name being migrated: <insert_0>
Message processing target node UUID: <insert_1>
After migration, from the Message Brokers Toolkit, edit the flow,
locate the source node and reconnect it.
- BIP0884
- A RETURN statement has been detected in the Filter ESQL expression.
- Severity
- 0 : Information
- Explanation
- The migrate command has not added a RETURN statement as one was detected.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
After migration, from the Message Brokers Toolkit, verify that a RETURN statement exists.
- BIP0885
- A RETURN statement has not been detected in the Filter ESQL expression.
- Severity
- 0 : Information
- Explanation
- The migrate command has added a RETURN statement as one was not detected.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
After migration, from the Message Brokers Toolkit, verify the RETURN statement is correct.
- BIP0886
- An unexpected exception occurred: <insert_0>
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>.
- Response
- The migration command may have terminated prematurely.
If so, remove the export file being migrated, and resume migration.
Consult the report.txt file for migration progress.
- BIP0887
- The <insert_0> is not properly set in enqueue file <insert_1>.
- Severity
- 20 : Error
- Explanation
- Check the enqueue file <insert_0> for errors and try again.
- BIP0888
- The resource <insert_0> could not be added to broker archive file <insert_1>.
- Severity
- 20 : Error
- Explanation
- <insert_1>.
- BIP0889
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Message Brokers Toolkit is experiencing problems communicating with the Configuration Manager on <insert_0>.
- Response
- Ensure that the Configuration Manager is available.
If so, do the following:
1) Select the Window > Preferences menu.
2) Select the Broker Administration > Configuration Manager Proxy preferences.
3) Increase the Maximum retry attempts, Initial and/or Increase time between attempts values.
4) Apply the changes.
5) Retry the operation.
- BIP0890
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Message Brokers Toolkit is experiencing problems communicating with the Configuration Manager on <insert_0>.
- Response
- Resolve the reason of error and try again.
- BIP0891
- An empty file cannot be added to a message flow as a subflow.
- Severity
- 20 : Error
- Explanation
- Empty files are not valid as message subflows.
- Response
- Add content to the subflow and try the operation again.
- BIP0892
- A successful response has been received from Configuration Manager on <insert_0>.
- Severity
- 0 : Information
- Explanation
- A successful response has been received which provided the message(s) detailed below.
- BIP0893
- Cannot communicate with queue manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- An unexpected exception occurred while attempting to communicate with the queue manager.
- Response
- Check the name/status of the queue manager and try again.
- BIP0894
- Topology cannot be saved because some brokers are missing Queue Manager Name definition.
- Severity
- 20 : Error
- Explanation
- Mandatory "Queue Manager Name" property is not filled for following brokers:
<insert_0>
Modify this property for each listed broker and try the operation again.
- BIP0895
- Cannot dequeue message from queue <insert_0> using queue manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- Check the enqueue file <insert_0> for errors and try again.
- BIP0896
- Cannot enqueue message into queue <insert_0> using queue manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- Check the enqueue file <insert_0> for errors and try again.
- BIP0897
- Cannot delete Configuration Manager's subscription.
- Severity
- 10 : Warning
- Explanation
- Subscriptions starting with $SYS or $ISYS are used internally
by the Configuration Manager and cannot be deleted.
- BIP0898
- Cannot add subflow <insert_0>
- Severity
- 20 : Error
- Explanation
- The reference to file <insert_0> is ambiguous.
A file with the same name may exist in the same schema in a referenced project.
- Response
- Rename one of the files and try the operation again.
- BIP0899
- Cannot add subflow <insert_0>
- Severity
- 20 : Error
- Explanation
- The file <insert_0> cannot be found.
The file may exist in a project that is not referenced.
- Response
- Add the project containing the subflow as a referenced project and try the operation again.
- BIP0900
- An exception occurred when trying to update Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- An exception has been received which provided additional information detailed below.
- Response
- Editor/Viewer has been refreshed with Configuration Manager content.
- BIP0901
- <insert_0> Editor cannot be opened.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager has sent an ACL restriction on <insert_0>
Verify the ACL and retry the operation.
- BIP0902
- ESQL breakpoint marker in file <insert_0> cannot be updated.
- Severity
- 20 : Error
- Explanation
- The breakpoint location or breakpoint attributes cannot be set.
Errors could be happened in <insert_0>.
- BIP0903
- A Compute node has been substituted for an Extract node.
- Severity
- 0 : Information
- Explanation
- The Extract node is now developed using the mapping editor.
It no longer hosts hand coded ESQL statements.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
- BIP0904
- A Database node has been substituted for a Warehouse node.
- Severity
- 0 : Information
- Explanation
- The Warehouse node is now developed using the mapping editor.
It no longer hosts hand coded ESQL statements.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
- BIP0905
- Not enough memory to display image with given scale factor.
- Severity
- 20 : Error
- Explanation
- Selected image <insert_0>
cannot be displayed with a <insert_1> scale factor.
- Response
- Select another image or decrease scale factor and retry the operation.
- BIP0906
- Cannot load a platform dependency.
- Severity
- 20 : Error
- Explanation
- A suitable extension for point <insert_0> cannot be loaded.
- BIP0907
- The file provided cannot be used.
- Severity
- 20 : Error
- Explanation
- The file <insert_0> is not writable.
Modify Read-only attribute or choose another file.
- BIP0908
- An attempt was made to create a new file but a failure return code was returned
- Severity
- 20 : Error
- Explanation
- The file <insert_0> could not be created.
The user should amend the filename and try again.
- BIP0909
- An attempt was made to create a new file but an exception was thrown.
- Severity
- 20 : Error
- Explanation
- The file <insert_0> could not be created (after <insert_1>).
- BIP0910
- The file provided cannot be opened.
- Severity
- 20 : Error
- Explanation
- The file <insert_0> doesn't exist.
nChoose another file and try again.
- BIP0911
- Would you like to override an existing file?
- Severity
- 10 : Warning
- Explanation
- The file <insert_0> already exists.
nDo you want to replace it?
- BIP0912
- The file provided cannot be parsed.
- Severity
- 20 : Error
- Explanation
- The file <insert_0> is not a valid topics export file.
nChoose a valid topics file and try again.
- BIP0913
- Configuration Manager is not at the required software product level.
- Severity
- 20 : Error
- Explanation
- The version of the Configuration Manager is not compatible with current version of Message Brokers Toolkit.
Reply to the sent request indicates that Configuration Manager is not at a sufficient level.
Try to connect to a same product level Configuration Manager and retry the operation.
- BIP0914
- Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- Network connection may be dropped and / or WebSphere MQ queue manager <insert_0> is not running and / or listener on port <insert_1> is not started.
- Response
- First, check the Queue Manager is available by doing the following:
1) Ensure network connection is enabled.
2) Start WebSphere MQ queue manager <insert_0> if necessary.
3) Ensure listener on port <insert_1> is running.
Then, do the following:
4) Disconnect from the Domain if already connected.
5) Connect to the Domain.
6) Retry the operation.
- BIP0915
- Message Brokers Toolkit is unable to communicate with the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ queue manager <insert_0> cannot be reached.
- Response
- Ensure first the Queue Manager is available.
If so, then do the following:
1) Disconnect from the Domain if already connected.
2) Connect to the Domain.
3) Retry the operation.
- BIP0916
- Unable to dequeue message.
- Severity
- 20 : Error
- Explanation
- Cannot get message from queue <insert_0> under queue manager <insert_1>.
- Response
- Check names of the queue and the queue manager and try again.
- BIP0917
- No messages found to dequeue.
- Severity
- 20 : Error
- Explanation
- No messages were found on queue <insert_0> under queue manager <insert_1>.
- Response
- Check the names and status of the queue and the queue manager and try again.
- BIP0918
- The resource <insert_0> could not be refactored.
- Severity
- 20 : Error
- Explanation
- An error occurred while trying to read the file from disk.
- Response
- The file may be internally inconsistent. Modify the file in its editor and save it to correct the error.
- BIP0919
- An exception occurred while sending a message to Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- Text Messenger is experiencing problems sending a message.
nRestart the application.
- BIP0920
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Text Messengers connection on Queue Manager <insert_0> has been broken or is not available.
nEnsure your Queue Manager is available and your listener is running.
- BIP0921
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Text Messenger is experiencing problems communicating with the Configuration Manager on <insert_0>.
nEnsure you have run the create queue wizard for the Getting Started Samples.
- BIP0922
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Text Messenger is experiencing problems sending a message.
- BIP0923
- An exception occurred while subscribing messages on Queue Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Surf subscriber is experiencing problems sending subscriptions.
nRestart the application.
- BIP0924
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Surf Subscribers connection on Queue Manager <insert_0> has been broken or is not available.
nEnsure your Queue Manager is available and your listener is running.
- BIP0925
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Surf Subscriber is experiencing problems communicating with the Configuration Manager on <insert_0>.
nEnsure you have run the create queue wizard for the Getting Started Samples.
- BIP0926
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Surf Subscriber is experiencing problems subscribing topics.
- BIP0927
- An exception occurred while publishing messages on Queue Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Publisher is experiencing problems publishing messages.
nRestart the application.
- BIP0928
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Publishers connection on Queue Manager <insert_0> has been broken or is not available.
nEnsure your Queue Manager is available and your listener is running.
- BIP0929
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Publisher is experiencing problems communicating with the Configuration Manager on <insert_0>.
nEnsure you have run the create queue wizard for the Getting Started Samples.
- BIP0930
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Publisher is experiencing problems publishing messages.
- BIP0931
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Pagers connection on Queue Manager <insert_0> has been broken or is not available.
nEnsure your Queue Manager is available and your listener is running.
- BIP0932
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Pager is experiencing problems communicating with the Configuration Manager on <insert_0>.
nEnsure you have run the create queue wizard for the Getting Started Samples.
- BIP0933
- An exception occurred while communicating with the Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- Pager is experiencing problems receiving messages.
- BIP0934
- An exception occurred while getting messages from Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- Pager is experiencing problems getting messages.
nRestart the application.
- BIP0935
- Several domain connection files exist for the domain.
- Severity
- 20 : Error
- Explanation
- Domain connection editor cannot be opened because several domain connection files exist for the domain <insert_0>.
- Response
- Select the domain connection file you want to edit and open it.
- BIP0936
- Topology Configuration cannot be deployed for now.
- Severity
- 10 : Warning
- Explanation
- Topology Configuration on <insert_0> cannot be deployed because a previous Broker Configuration is deployed.
- Response
- Retry later the deploy operation on Broker Topology.
- BIP0937
- Problem on connecting to broker.
- Severity
- 20 : Error
- BIP0938
- There was a problem trying to create a subscriber.
- Severity
- 20 : Error
- BIP0939
- There was a problem trying to start the subscriber listening on the subscribe queue.
- Severity
- 20 : Error
- BIP0940
- There was a problem trying to stop the subscriber.
- Severity
- 20 : Error
- BIP0941
- The message received was incorrectly formed.
- Severity
- 20 : Error
- BIP0942
- The connection to the QueueManager was closed.
- Severity
- 20 : Error
- BIP0943
- Error creating the connection to WebSphere MQ.
- Severity
- 20 : Error
- BIP0944
- Failed to create Coordinate publisher.
- Severity
- 20 : Error
- BIP0945
- Failed to create Clear screen publisher.
- Severity
- 20 : Error
- BIP0946
- Exception when closing connection to broker.
- Severity
- 20 : Error
- BIP0947
- Error on publishing clear message.
- Severity
- 20 : Error
- BIP0948
- Error on publishing coordinate message.
- Severity
- 20 : Error
- BIP0949
- WebSphere MQ error getting message from Queue.
- Severity
- 20 : Error
- BIP0950
- SCRIBBLE has a WebSphere MQ connection message.
- Severity
- 0 : Information
- BIP0951
- SCRIBBLE has got a subscribe message.
- Severity
- 0 : Information
- BIP0952
- SCRIBBLE subscriber has started receiving messages.
- Severity
- 0 : Information
- BIP0954
- Cannot create image with specified file name.
- Severity
- 20 : Error
- Explanation
- An image cannot be created from specified image file <insert_0>.
The file may not exist or has not a valid JPG or GIF format.
- Response
- Verify that file exists and is valid, then retry the operation.
- BIP0955
- Compile a broker archive file from source.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsicreatebar -data workspace -b barName [-version id] [-esql21]
t[-p projectName [...]] -o filePath1 [filePath2 [...]]
Command Options:
'-data workspace' workspace location (Mandatory)
'-b barName' bar file name to create or replace
'-version id' appends '_' and id to compiled names in the archive (optional)
'-esql21' compile ESQL for brokers version 2.1 (optional)
'-p projectName' specify projects containing files to link (optional, multiple
tprojects can be specified)
'-o filePath1' workspace relative path (including the project) of deployable
tfiles to add to the broker archive. Multiple deployable files can be compiled
tin a single mqsicreatebar command.
- BIP0956
- Unable to start mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- No parameters were supplied to the mqsicreatebar command.
- BIP0957
- Incorrect arguments supplied to mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- You must supply the "-b <barName>" parameter.
- BIP0958
- Nothing to do in mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- You must supply the workspace-relative path of the msgflow or messagset.mset
to compile using the -o parameter.
- BIP0959
- Incorrect arguments supplied to mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- Project name is not valid.
- BIP0960
- Incorrect "-p" or "-o" argument supplied to mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- Project directory <insert_0> does not exist.
- BIP0961
- Error opening workspace in mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- Project could not be created for directory <insert_0>."
The reason given was:
<insert_1>
- BIP0962
- Error opening workspace in mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- Project <insert_0> could not be opened. The reason given was:
<insert_1>
- BIP0963
- Error saving file in mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- The file <insert_0> could not be saved to disk.
The reason given was:
<insert_1>
- BIP0964
- Incorrect "-o or -p" argument supplied to mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- File <insert_0> does not exist.
- BIP0965
- Error compiling files in mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- The message is:
<insert_0>
- BIP0967
- No more handles available to display image.
- Severity
- 20 : Error
- Explanation
- The Operating System cannot allocate new graphical objects
because it has reached its maximum number of handles.
Close then reopen the workbench and try again.
- BIP0968
- A Database node has been substituted for a DataInsert node.
- Severity
- 0 : Information
- Explanation
- The DataInsert node is now developed using the mapping editor.
It no longer hosts hand coded ESQL statements.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
- BIP0969
- A Database node has been substituted for a DataUpdate node.
- Severity
- 0 : Information
- Explanation
- The DataUpdate node is now developed using the mapping editor.
It no longer hosts hand coded ESQL statements.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
- BIP0970
- A Database node has been substituted for a DataDelete node.
- Severity
- 0 : Information
- Explanation
- The DataDelete node is now developed using the mapping editor.
It no longer hosts hand coded ESQL statements.
Message flow name being migrated: <insert_0>
Message processing node name: <insert_1>
- BIP0971
- Cannot open ESQL module <insert_0>
- Severity
- 20 : Error
- Explanation
- The reference to module <insert_0> is ambiguous.
A module with the same name may exist in the same schema in a referenced project.
- Response
- Rename one of the modules and try the operation again.
- BIP0972
- Incorrect arguments supplied to mqsimigratemsgflows.
- Severity
- 20 : Error
- Explanation
- If you specify -log you must supply the name of a report file.
- BIP0973
- Unable to delete existing project <insert_0>.
- Severity
- 20 : Error
- Explanation
- The specified project could not be deleted.
Specify a non-existing project with a valid name.
- BIP0974
- Invalid 'esql' protocol URL parsed
- Severity
- 20 : Error
- Explanation
- The invalid 'esql' protocol URL is <insert_0>.
- BIP0975
- A resource could not be found.
- Severity
- 20 : Error
- Explanation
- A <insert_0> exception occurred which reported the following message: <insert_1>
- Response
- The ESQL or Mapping file path length may exceed 256 characters which may not be supported by the file system.
To overcome this situation, keep install path, project names, broker schema names, and message flow names reasonably short.
- BIP0976
- Property name collision has been detected.
- Severity
- 20 : Error
- Explanation
- A property with the name <insert_0> appears more than once in the flow <insert_1>.
The flow has not been corrected by the migration tool.
You must later correct the flow manually.
- BIP0977
- The WebSphere MQ classes for Java could not be found.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ classes for Java must be installed to use the enqueue editor to send messages.
- Response
- If this package is installed check and see if the following environment variable is set:
Windows: PATH=<install directory>&bsl;lib
Linux: LD_LIBRARY_PATH=/opt/mqm/java/lib
- BIP0978
- The WebSphere MQ classes for Java could not be found.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ classes for Java must be installed to get messages using the dequeue dialog.
- Response
- If this package is installed check and see if the following environment variable is set:
Windows: PATH=<install directory>&bsl;lib
Linux: LD_LIBRARY_PATH=/opt/mqm/java/lib
- BIP0979
- Read a broker archive file.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsireadbar -b <full path to bar file>
- BIP0980
- Unable to read broker archive file.
- Severity
- 20 : Error
- Explanation
- File <insert_0> does not exist.
- BIP0981
- Incorrect arguments supplied to mqsireadbar.
- Severity
- 20 : Error
- Explanation
- You must supply the "-b <full path to bar file>" parameter.
- BIP0982
- Unable to start mqsireadbar.
- Severity
- 20 : Error
- Explanation
- No parameters were supplied to the mqsireadbar command.
- BIP0983
- Unable to read broker archive file.
- Severity
- 20 : Error
- Explanation
- The message is:
<insert_0>
- BIP0985
- Error storing incrementally compiled ESQL.
- Severity
- 20 : Error
- Explanation
- The ESQL content associated with <insert_0> could not
be saved.
- BIP0986
- Command completed successfully.
- Severity
- 0 : Information
- BIP0987
- A failure response has been received from Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- A failure response has been received which provided the message(s) detailed below.
- BIP0988
- Error occurred while completing mqsicreatebar command.
- Severity
- 10 : Warning
- BIP0989
- Incorrect "-o" argument supplied to mqsicreatebar.
- Severity
- 20 : Error
- Explanation
- File <insert_0> cannot be added because it does not contain a valid file extension.
- BIP0990
- Incorrect arguments supplied to mqsimigratemsgflows.
- Severity
- 20 : Error
- Explanation
- You must supply -data <workspace>.
- BIP0991
- A failure response has been received from Configuration Manager on <insert_0>.
- Severity
- 20 : Error
- Explanation
- A failure response has been received which provided the message(s) detailed below.
- Response
- Resolve the reason of error and try again.
- BIP0992
- Cannot add drag and drop resource <insert_0>
- Severity
- 20 : Error
- Explanation
- The file <insert_0> cannot be found.
The file may exist in a project that is not referenced.
- Response
- Add the project containing the resource as a referenced project and try the operation again.
- BIP0993
- Cannot add drag and drop resource <insert_0>
- Severity
- 20 : Error
- Explanation
- The reference to file <insert_0> is ambiguous.
A file with the same name may exist in the same schema in a referenced project.
- Response
- Rename one of the files and try the operation again.
- BIP0994
- Cannot update flow node <insert_0>
- Severity
- 20 : Error
- Explanation
- The file <insert_0> cannot be found.
The file may exist in a project that is not referenced.
- Response
- Add the project containing the resource as a referenced project and try the operation again.