BIP8000-8999: Runtime components - Commands
- BIP8001
- Unknown flag <insert_0> selected.
- Severity
- 20 : Error
- Explanation
- When using this command interface the user should only select the supported flags.
- Response
- Correct and reissue the command.
- BIP8002
- Selected flag <insert_0> badly formed.
- Severity
- 20 : Error
- Explanation
- Command flag should be properly specified.
- Response
- Correct and reissue the command.
- BIP8003
- Duplicate flag detected.
- Severity
- 20 : Error
- Explanation
- A flag was selected more than once.
- Response
- Correct and reissue the command.
- BIP8004
- Invalid argument <insert_0> specified.
- Severity
- 20 : Error
- Explanation
- Argument specified should be well formed.
- Response
- Correct and reissue the command.
- BIP8005
- Flag or argument <insert_0> missing.
- Severity
- 20 : Error
- Explanation
- The command will result in no action being taken, a required flag or a flag's argument is missing.
- Response
- Correct and reissue the command.
- BIP8006
- Flag missing. One of the flags in list (<insert_0>) must be specified.
- Severity
- 20 : Error
- Explanation
- When using this command interface the user should select all required flags.
- Response
- Correct and reissue the command.
- BIP8007
- Mandatory argument missing.
- Severity
- 20 : Error
- Explanation
- When using this command interface the user should supply the mandatory argument.
- Response
- Correct and reissue the command.
- BIP8008
- Unable to create the Java environment.
- Severity
- 20 : Error
- Explanation
- The Java environment could not be created.
- Response
- Ensure that the Java CLASSPATH variable is correct and ensure that the Java runtime executable (JRE) shipped with the product is in its correct directory.
- BIP8009
- Program name incorrect.
- Severity
- 20 : Error
- Explanation
- Ensure that the program name (executable) has not been modified.
- Response
- Correct and reissue the command.
- BIP8010
- No component name supplied.
- Severity
- 20 : Error
- Explanation
- This command requires a component name to be supplied.
- Response
- Correct and reissue the command.
- BIP8011
- Unable to create the components configuration data.
- Severity
- 20 : Error
- Explanation
- The command is unable to store the component's configuration data.
- Response
- Ensure that the userid that is running this command has adequate authority to update the configuration or registry files. Without this authority the registry or configuration files cannot be updated. Also check that the broker name does not contain invalid characters or is too long.
- BIP8012
- Unable to connect to system components.
- Severity
- 20 : Error
- Explanation
- This command was unable to connect to required system services.
- Response
- Check your system log for failure information. Ensure that the user name used to issue this command has the required permissions to modify NT services. Reissue the command when this has been resolved.
- BIP8013
- Component does not exist.
- Severity
- 20 : Error
- Explanation
- A component may only be used if it has first been created.
- Response
- No user action required.
- BIP8014
- Component could not be created.
- Severity
- 10 : Warning
- Explanation
- Unable to create the component, the required resources were unavailable.
- Response
- Investigate the reasons for the failure, ensure that the userid permissions are correct and that there are sufficient system resources available. Contact your IBM support center if you are unable to resolve the problem.
- BIP8015
- The component cannot be started.
- Severity
- 20 : Error
- Explanation
- The command could not start the required component.
- Response
- Trace the command and investigate the reasons for this failure, insufficient userid permissions or lack of system resources may cause this problem. If you are unable to resolve the problem, contact your IBM support center.
- BIP8016
- Unable to stop component.
- Severity
- 20 : Error
- Explanation
- A request to stop this component was refused.
- Response
- Investigate the reason for this failure and reissue the command. The problem may be that the component was in the process of being stopped or started, in this case just reissue the command. It may be that the command could not be issued because of insufficient userid permissions. If you are unable to resolve the problem, contact your IBM support center.
- BIP8017
- The component could not be deleted.
- Severity
- 20 : Error
- Explanation
- Ensure that the component is in a valid state to be deleted.
- Response
- Make sure that the component is stopped and reissue the command. Check your system log for failures. If you are unable to resolve the problem contact your IBM support center.
- BIP8018
- Component running.
- Severity
- 20 : Error
- Explanation
- This component is running, the command issued cannot be run against a running component.
- Response
- Stop the component and reissue the command.
- BIP8019
- Component stopped.
- Severity
- 20 : Error
- Explanation
- A previous command was issued to stop this component or it has never been started.
- Response
- This component may be started, changed or deleted.
- BIP8020
- Unable to access the broker's database tables.
- Severity
- 20 : Error
- Explanation
- This command interacts with the broker's database tables using the database userid selected for this component.
- Response
- Ensure that the database is running, that all broker tables are available and that the database userid provided for this broker or Configuration Manager still has the permissions to modify the database tables.
- BIP8021
- Ensure that the userid and/or password supplied are correct.
- Severity
- 20 : Error
- Explanation
- Ensure that the password is valid and that the userid is defined. Ensure that the service does not interact with the desktop.
- Response
- Correct and reissue the command.
- BIP8022
- Invalid service userid and password combination supplied.
- Severity
- 20 : Error
- Explanation
- The userid/password pair are not correct.
- Response
- Correct and reissue the command.
- BIP8023
- A valid password must be supplied.
- Severity
- 20 : Error
- Explanation
- When a userid is altered, a valid password must also be supplied. If you supply a password it must contain at least two characters.
- Response
- Correct and reissue the command.
- BIP8024
- Unable to locate the component's executable.
- Severity
- 20 : Error
- Explanation
- The component's executable is not in the expected directory.
- Response
- Ensure that the product has not been moved from its installation directory. Check that executable 'bipservice' is in the product's 'bin' directory.
- BIP8025
- Component disabled.
- Severity
- 20 : Error
- Explanation
- The component should not be in a disabled state. The component could not be started.
- Response
- Investigate why the component is disabled and correct the problem, on Windows NT this may be because the component's service was 'disabled'.
- BIP8026
- Unable to start the component.
- Severity
- 20 : Error
- Explanation
- The component could not be started using the service userid that was supplied when the component was created.
- Response
- Ensure that the service userid and password are still valid. Ensure that the service userid has permission to access all of the products directories, specifically the 'bin' and 'log' directories. Check for system messages (on Windows NT this would be the application event log).
- BIP8027
- Unable to start WebSphere.
- Severity
- 20 : Error
- Explanation
- WebSphere Message Brokers requires that WebSphere is installed and its service is available.
- Response
- On NT the WebSphere service must be available before the WebSphere Message Brokers component can be started. The WebSphere service was unable to start, correct the problem and reissue this command.
- BIP8028
- Required product unavailable.
- Severity
- 20 : Error
- Explanation
- WebSphere Message Brokers requires that WebSphere is installed and that its service 'WebSphereServices' is available.
- Response
- Ensure that WebSphere is installed.
- BIP8029
- The broker's configuration is not yet deployed.
- Severity
- 20 : Error
- Explanation
- This command results in an internal configuration message to the broker, this message may only be sent after at least one deployment to the broker from the Message Brokers Toolkit.
- Response
- Reissue the command after the broker's configuration has been deployed.
- BIP8030
- Unable to modify userid privileges.
- Severity
- 20 : Error
- Explanation
- On NT this command modifies a userid's privileges, ('logon as service').
- Response
- Ensure that the userid issuing this command has sufficient privileges to modify the privileges of the userid supplied in the command. Ensure that a Domain Controller, either Primary or Backup, is available. Re-execute the command. If the problem persists then please contact your IBM support center.
- BIP8031
- Invalid flag argument supplied.
- Severity
- 20 : Error
- Explanation
- Ensure that the correct flag arguments are selected.
- Response
- Correct and reissue the command.
- BIP8032
- Unable to connect to a WebSphere MQ queue.
- Severity
- 20 : Error
- Explanation
- An attempt was made to connect to the component's WebSphere MQ Queue Manager and queue, this attempt was unsuccessful.
- Response
- Ensure that the components WebSphere MQ Queue Manager and queue are available, running and that the user has sufficient authority to access them.
- BIP8033
- Unable to send an internal configuration message to the broker.
- Severity
- 20 : Error
- Explanation
- This command was unable to send an internal configuration message to the broker using WebSphere MQ.
- Response
- Ensure that WebSphere MQ is installed and that the broker and its Queue Manager are running.
- BIP8034
- An internal configuration response message not received.
- Severity
- 20 : Error
- Explanation
- This command sends an internal configuration message to the broker, a internal configuration response message was not received from that broker.
- Response
- Ensure that the broker and its WebSphere MQ Queue Manager are running.
- BIP8035
- An internal configuration response message was expected from the broker but was not received within its 1 hour timeout or the internal configuration message was rejected as an invalid message.
- Severity
- 20 : Error
- Explanation
- This command sends an internal configuration message to the broker, it has a predefined 1 hour timeout, if a request exceeds this time then the command is terminated. The internal configuration messages may also be rejected if their format is incorrect.
- Response
- Investigate why the internal configuration response message was not received within this period. Check the system log messages and ensure that your WebSphere MQ channels and listeners are active and that the broker or User Name Server is active. Contact your IBM support center if you are unable to resolve this problem.
- BIP8036
- Negative response received.
- Severity
- 20 : Error
- Explanation
- This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
- Response
- Check that the WebSphere MQ transport is available. Check the system log for further information.
- BIP8037
- Unsupported flag. The flags listed in (<insert_0>) are not supported.
- Severity
- 20 : Error
- Explanation
- When using this command interface the user should only select from the set of supported flags.
- Response
- Check the list of supported flags, correct and then reissue the command.
- BIP8038
- An invalid combination of options was selected.
- Severity
- 20 : Error
- Explanation
- The command specified represents an invalid combination of options and parameters.
- Response
- Refer to the WebSphere Message Brokers online documentation for the list of valid options for this command. Correct and reissue the command.
- BIP8039
- The execution group is not available.
- Severity
- 20 : Error
- Explanation
- The execution group could not be found; it may have been deleted by the Message Brokers Toolkit or Config Manager Proxy application.
- Response
- Use the Message Brokers Toolkit or Config Manager Proxy to see if the execution group exists.
- BIP8040
- Unable to connect to the database.
- Severity
- 20 : Error
- Explanation
- The database cannot be accessed with the userid and password that were specified with the broker.
- Response
- - Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqsicreate or mqsichangebroker command are capable of being used to connect to the database using an ODBC connection.
- Check that the database has a adequate number of database connections available for use.
- BIP8041
- Unable to open the selected file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The file selected could not be opened for read or write.
- Response
- Ensure that, if specified as input, the file exists and not also for output; and that the file path is valid in any cases. Also ensure that the file is not locked by another user.
- BIP8042
- Insufficient memory.
- Severity
- 20 : Error
- Explanation
- This command requires a significant amount of memory.
- Response
- Ensure that there is enough memory available to execute the command.
- BIP8043
- File selected was not a broker trace file.
- Severity
- 20 : Error
- Explanation
- Broker trace files have an XML tag indicating that they are trace files.
- Response
- Repeat the trace extraction and reissue the command.
- BIP8044
- Unable to get the message text for WBIMB command response <insert_0>.
- Severity
- 20 : Error
- Explanation
- A response was generated for which there is no message available. This is an internal error and should be reported to IBM together with a trace of the command that caused this message to be issued.
- Response
- Contact your IBM support center.
- BIP8045
- The message flow is not available.
- Severity
- 20 : Error
- Explanation
- The message flow could not be found; it may have been deleted by the Message Brokers Toolkit or a Config Manager Proxy application.
- Response
- Use the Message Brokers Toolkit or Config Manager Proxy to see if the message flow exists.
- BIP8046
- Unable to initialize parser data, exception caught <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command initializes parser functions prior to analyzing XML data, this parser cannot be initialized. Use the line number and column number (inserts 2 and 3 in the exception), to locate the XML causing the problem.
- Response
- Contact your IBM support center.
- BIP8047
- Unable to parse the data received, exception caught <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command uses parser functions to analyze XML data, the parser has detected an error in the format of the XML data being parsed. Use the line number and column number to locate the XML causing the problem.
- Response
- Check that the data being parsed is correctly formatted. The command may produce partial output. It may also be possible to modify the XML data that the command is parsing so that the error does not occur.
- BIP8048
- Unable to start WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to start a WebSphere MQ Queue Manager. The Queue Manager could not be started.
- Response
- Check your system log for failure information. Ensure that the user name used to issue this command has the required permissions to start the WebSphere MQ Queue Manager. Check that you have an appropriate installation of WebSphere MQ to support a WebSphere Message Broker component. Please see the "Diagnosing errors" section in the Information Center for more information.
- BIP8049
- Unable to stop WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to stop a WebSphere MQ Queue Manager. The Queue Manager could not be stopped.
- Response
- Locate and resolve the problem and retry the command.
- BIP8050
- Unable to create WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to create a WebSphere MQ Queue Manager. The Queue Manager could not be created.
- Response
- Locate and resolve the problem and retry the command.
- BIP8051
- Unable to create WebSphere MQ Queue <insert_0> on Queue Manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- This command attempts to create a WebSphere MQ Queue but was unable to do so.
- Response
- Locate and resolve the problem and retry the command.
- BIP8052
- Unable to delete WebSphere MQ Object <insert_0> from Queue Manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- This command attempts to delete a WebSphere MQ Object but was unable to do so.
- Response
- Locate and resolve the problem and retry the command. This could be because a WebSphere MQ channel is still running. If this is the case, stop all WebSphere MQ channels running on behalf of this Queue Manager. If your Message Brokers Toolkit is connected to your configuration manager, you may need to disconnect it as well.
- BIP8053
- Unable to set the security attributes for WebSphere Queue Manager <insert_0>, Group <insert_1>.
- Severity
- 20 : Error
- Explanation
- This command attempts to set the Group security attributes for a WebSphere Queue Manager.
- Response
- Ensure that the required Group is available and that the user issuing this command is a member of the mqm group.
- BIP8054
- Unable to set the security attributes for WebSphere Queue <insert_0> on Queue Manager <insert_1>, Group <insert_2>.
- Severity
- 20 : Error
- Explanation
- This command attempts to set the Group security attributes for a WebSphere Queue.
- Response
- Ensure that the required Group is available and that the user issuing this command is a member of the mqm group.
- BIP8055
- Unable to load a Java class or method <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to use a Java class or method, but was unable to run the class or method.
- Response
- Ensure that the required Java archives (jar files) are in the broker's classes directory.
- BIP8056
- The component's WebSphere MQ Queue Manager <insert_0> does not exist.
- Severity
- 20 : Error
- Explanation
- The command cannot be executed because the Queue Manager associated with this component does not exist.
- Response
- Recover the queue manager or delete and then recreate the component. If the component is a Configuration Manager, you should be careful NOT to delete its database tables.
- BIP8057
- The command has failed because of an unexpected Queue Manager error.
- Severity
- 20 : Error
- Explanation
- During execution of the command an unexpected response has been returned from an MQI call.
- Response
- A message containing further details of the failure will have been issued to your system log. Consult this message for problem resolution.
- BIP8058
- A command has failed because of an unexpected WebSphere MQ failure. A <insert_0> request against object <insert_1> has failed with reason code <insert_2>.
- Severity
- 20 : Error
- Explanation
- A command has been issued but during execution of the command an unexpected WebSphere MQ failure was returned from MQI call <insert_1>.
- Response
- Using reason code <insert_2>, consult the WebSphere MQ Application Programming Reference manual to establish the cause of the failure. Take appropriate action to correct the problem before reissuing the command.
- BIP8059
- Command has failed because the component's Queue Manager is not available.
- Severity
- 20 : Error
- Explanation
- The command has failed because the Queue Manager associated with the component is currently unavailable.
- Response
- Reissue the command after the queue manager has been restarted.
- BIP8060
- Command has failed because of problem with queue SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub and mqsiclearmqpubsub commands send their requests to the broker on queue SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS. The request has not been sent because a problem has been detected with the queue.
- Response
- First check whether the queue exists or not. If not, consult the WebSphere Message Brokers Introduction and Planning guide for more information about how the queue needs to be defined. After the queue has been defined you will need to stop and restart the broker before it will start to receive messages on this queue. If the queue already existed then stop and restart the broker before reissuing the command. If the command still fails with this error, check that the broker is not waiting for migration to complete. If this is the case, message BIP7283 will have been issued when the broker was last started.
- BIP8061
- Broker has failed to reply to command.
- Severity
- 20 : Error
- Explanation
- The request has been sent to the broker but no reply message has been received. The command may or may not have been successful.
- Response
- Investigate why the broker failed to respond to the request. If the broker has terminated, restart it and reissue the command.
- BIP8062
- Join request has failed because parent broker is already a neighbor.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub command has failed because the named parent broker is already a neighbor.
- Response
- If a previous attempt to join the two brokers using the mqsijoinmqpubsub command has failed then it may be necessary to use mqsiclearmqpubsub first before reissuing the command.
- BIP8063
- Clear request has failed because specified broker is not a neighbor.
- Severity
- 20 : Error
- Explanation
- The mqsiclearmqpubsub command has failed because the named broker was not a neighbor.
- Response
- Reissue the command specifying a broker which is a neighbor.
- BIP8064
- Command has failed because of an internal component error
- Severity
- 20 : Error
- Explanation
- The command has failed because of an internal error at the component.
- Response
- A message containing the further details of the failure will have been issued to the system log. Consult this message for problem resolution.
- BIP8065
- Join request has failed because broker already has a parent.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub command has failed because the message broker already has a parent WebSphere Publish/Subscribe broker.
- Response
- Remove the existing parent broker before reissuing the command.
- BIP8066
- Request has failed because an invalid broker name was specified.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub or mqsiclearmqpubsub command has failed because the WebSphere Publish/Subscribe broker name supplied was invalid.
- Response
- Reissue the command with a valid WebSphere Publish/Subscribe broker name.
- BIP8067
- Request has failed because couldn't contact the parent WebSphere publish/subscribe broker.
- Severity
- 20 : Error
- Explanation
- The mqsijoinmqpubsub command has failed because the supplied WebSphere publish/subscribe broker could not be contacted.
- Response
- A message containing further details of the failure will have been issued to the system log. The problem is likely to be caused by the parent broker name not resolving to the name of a transmission queue at the queue manager which is hosting the WebSphere Message Brokers broker. Correct the underlying problem with the WebSphere network and reissue the command.
- BIP8068
- Argument <insert_0> is not a valid integer value for this flag.
- Severity
- 20 : Error
- Explanation
- Ensure that the argument used is a valid integer and in the allowable range.
- Response
- Correct and reissue the command.
- BIP8069
- Unable to find message <insert_0> in message catalog <insert_1>.
- Severity
- 20 : Error
- Explanation
- A message could not be found in the message catalog specified.
- Response
- Ensure that the message is available in the message catalog and that the catalog is in the product message directory.
- BIP8070
- Exception accessing database table executing SQL statement <insert_0>: SQL state <insert_1>; exception <insert_2>.
- Severity
- 20 : Error
- Explanation
- An SQL command has failed.
- Response
- Ensure that the broker's database is available. Examine the exception and SQL state code to determine and correct the cause of the error.
- BIP8071
- Successful command completion.
- Severity
- 0 : Information
- BIP8072
- Exception accessing a database table, executing SQL statement <insert_0>: exception <insert_1>.
- Severity
- 20 : Error
- Explanation
- An SQL command has failed.
- Response
- Ensure that the database is available, examine the exception to determine and correct the cause of the error.
- BIP8073
- <insert_0> is not a valid component.
- Severity
- 20 : Error
- Explanation
- The name selected is not a valid component.
- Response
- Select a different component.
- BIP8074
- Unable to create a JVM.
- Severity
- 20 : Error
- Explanation
- A Java Virtual Machine could not be created.
- Response
- Ensure that the Java CLASSPATH variable is correct and that it is not too large, ensure that the Java runtime executable (JRE) shipped with the product is in its correct directory.
- BIP8075
- A Java exception was caught from class <insert_0>. The text is <insert_1>.
- Severity
- 20 : Error
- Explanation
- A Java exception was caught via the JNI.
- Response
- Check preceding messages for related errors and retry the operation. If the exception still occurs, contact your IBM support center.
- BIP8076
- Current working directory could not be set to <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error has occurred while the command was running. The command has cleaned up and terminated.
- Response
- Investigate why the directory <insert_0> can't be accessed, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.
- BIP8077
- A problem was encountered while attempting to create/delete the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- The operation was not completed successfully. An internal error generated an invalid return code of <insert_0>.
- Response
- Check messages in the system log for related errors and retry the operation. If the problem still occurs contact your IBM support center.
- BIP8078
- A problem was encountered while attempting to create/delete the Configuration Manager.
- Severity
- 20 : Error
- Explanation
- The operation was not completed successfully.
- Response
- Check messages in the system log for related errors and retry the operation. If the problem still occurs, contact your IBM support center.
- BIP8079
- Unable to find service user id <insert_0>.
- Severity
- 20 : Error
- Explanation
- This user ID is not defined to the operating system, so it cannot be used as a component service user ID.
- Response
- Create the user ID and reissue the command, or specify a user ID which exists on this system.
- BIP8080
- Unable to initialize a parser factory.
- Severity
- 20 : Error
- Explanation
- The command executable detected an error whilst initializing its parser factory.
- Response
- Contact your IBM support center.
- BIP8081
- An error occurred while processing the command.
- Severity
- 20 : Error
- Explanation
- An error has occurred while the command was running. The command has cleaned up and terminated.
- Response
- Use messages prior to this one to determine the cause of the error. Correct the problem and retry the command. Check for some common problems :- Does the user id have the correct authorities (for example a member of the mqbrkrs group)? Is the broker database started and operating correctly? Is any operating system limit set too low to allow the command to run? Is the environment correctly set up? Contact your IBM support center if you are unable to resolve the problem.
- BIP8082
- Unable to delete WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to delete an WebSphere MQ Queue Manager, but the Queue Manager could not be deleted.
- Response
- This could be because an WebSphere MQ channel or WebSphere MQ Listener is still running. Stop all WebSphere MQ channels and WebSphere MQ Listeners running for this Queue Manager and retry the command.
- BIP8083
- The component name supplied contains invalid characters.
- Severity
- 20 : Error
- Explanation
- This command requires that the component name is made up of a set of characters supported by the platform on which the command is being executed.
- Response
- Correct and reissue the command.
- BIP8084
- Unable to create directory <insert_0>, return code <insert_1>.
- Severity
- 20 : Error
- Explanation
- The specified directory could not be created. Ensure that the characters are valid, that you have the required permissions and that the parent directory exists.
- Response
- Correct and reissue the command.
- BIP8085
- The environment variable <insert_0> is not defined.
- Severity
- 20 : Error
- Explanation
- An attempt to read an environment variable was unsuccessful.
- Response
- Ensure the environment variable is defined.
- BIP8086
- WebSphere MQ Queue Manager <insert_0> is already reserved for use by component <insert_1>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to use a WebSphere MQ Queue Manager that was already reserved for use by another component. It is acceptable for a broker, User Name Server and Configuration Manager to all share a single WebSphere MQ Queue Manager. It is not acceptable for multiple components of the same type (brokers, User Name Servers, or Configuration Managers) to share a single WebSphere MQ Queue Manager.
- Response
- Choose another WebSphere MQ Queue Manager and reissue the command.
- BIP8087
- <insert_0> already exists and cannot be created.
- Severity
- 20 : Error
- Explanation
- An attempt was made to create a component that already exists.
- Response
- Ensure that the component name you have selected for creation is the correct one, and investigate the reasons why this component name already exists. Additionally, if you are running on a Windows platform and mqsilist does not report the existence of the component the component's service may still be running. This may be because of a previous delete failed to complete and left the component's service running (this can be caused by an open Administrative Tools - Services window, which prevents the deletion being completed.) If the component's service still exists try deleting the component after resolving any relevant issues and retry this create command.
- BIP8088
- There are no WebSphere Publish/Subscribe neighbors.
- Severity
- 0 : Information
- BIP8089
- WebSphere Publish/Subscribe neighbor <insert_0> is inactive.
- Severity
- 0 : Information
- BIP8090
- WebSphere Publish/Subscribe neighbor <insert_0> is active.
- Severity
- 0 : Information
- BIP8091
- Common stream <insert_0>.
- Severity
- 0 : Information
- BIP8092
- Unable to locate WebSphere Message Brokers response <insert_0> in message catalog <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere Message Brokers response could not be found in the message catalog.
- Response
- Make sure that the message catalog is available and that the WebSphere Message Brokers response is in the message catalog. If the problem persists contact your IBM support center.
- BIP8093
- Unable to access the WebSphere MQ Queue Manager.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ Queue Manager is currently being created by another user.
- Response
- Wait until the Queue Manager has been created, then reissue this command.
- BIP8094
- Unable to access the WebSphere MQ Queue Manager.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ Queue Manager is currently being stopped by another user.
- Response
- Wait until the stop has completed and reissue this command.
- BIP8095
- WebSphere queue manager <insert_0> is reserved for use by WebSphere Message Brokers component <insert_1>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to delete an WebSphere queue manager that was being shared by another WebSphere Message Brokers component.
- Response
- It is acceptable for a broker, User Name Server and Configuration Manager to all share a single WebSphere queue manager. The 'WebSphere queue manager delete' option provided by this command may only be selected if there are no other WebSphere Message Brokers components currently configured to share this WebSphere queue manager.
- BIP8096
- Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
- Severity
- 0 : Information
- BIP8097
- Unable to instantiate Java object of class <insert_0>.
- Severity
- 20 : Error
- Explanation
- An instance of the Java class could not be instantiated.
- Response
- This is an internal error, possibly due to a faulty installation. Check messages in the system log for related errors and retry the operation. If the problem persists, contact your IBM support center.
- BIP8098
- Trace level: <insert_0>, mode: <insert_1>, size: <insert_2> KB.
- Severity
- 0 : Information
- BIP8099
- <insert_0>: <insert_1> - <insert_2>
- Severity
- 0 : Information
- BIP8101
- Changes a broker's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangebroker brokerName [[-i serviceUserId] -a servicePassword] [-p dataSourcePassword] [-s unsQMgrName] [-j | -d] [-t | -n] [-l userLilPath] [-g configurationTimeout] [-k configurationDelayTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-c ICU converter path] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits]
- Response
- Command Options:
'brokerName' name of the broker to change
'-i serviceUserId' the userid that the broker should run under
'-a servicePassword' the password for the broker userid
'-p dataSourcePassword' the password for the broker's database userid
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j' indicates that publish/subscribe access control is to be enabled for this broker
'-d' indicates that publish/subscribe access control is to be disabled for this broker
'-t' indicates WebSphere MQ fastpath is to be used for this broker (not supported on all platforms)
'-n' indicates WebSphere MQ fastpath is not to be used for this broker
'-l userLilPath' indicates where user-written 'lil' and 'jar' files are loaded from
'-g configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message
'-k configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records
'-P httpListenerPort' the port that the broker's HTTP listener will use
'-c ICU converter path' delimited list (';' in windows, ':' on unix) of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (userId)
'-z ldapCredentials' the LDAP Credentials (password)
'-x userExitPath' the directory from which the broker searches for all user exits. This path will be added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a userExit name to this list, changes its default state to active for this broker. The default state can be overridden at the execution group or message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and the execution group will fail to start.
- BIP8102
- Changes a Configuration Manager's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeconfigmgr configMgrName [[-i serviceUserId] -a servicePassword] [-s unsQMgrName] [-p dataBasePassword] [-j maxJVMHeapSize]
- Response
- Command Options:
'configMgrName' name of the Configuration Manager (may be omitted on Windows)
'-i serviceUserId' the userid that the Configuration Manager should run under
'-a servicePassword' the password for the Configuration Manager userid
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-p dataBasePassword' the password for the DB2 database being migrated
'-j maxJVMHeapSize' the maximum Java virtual machine heap size, in megabytes (default 256) (minimum 64).
Note: On Windows platforms, if the Configuration Manager name is omitted 'ConfigMgr' will be used.
- BIP8103
- Changes a User Name Server's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeusernameserver [[-i serviceUserId] -a servicePassword] [-d securityDomainName] [-r refreshInterval] [-g authProtocolDataSource] [-j | -o]
- Response
- Command Options:
'-i serviceUserId' the userid that the User Name Server should run under
'-a servicePassword' the password for the User Name Server userid
'-d securityDomainName' the security domain that the User Name Server will use
'-r refreshInterval' number of seconds between each refresh of the User Name Server internal cache
'-g authProtocolDataSource' the name of the data source required by the authentication protocol
'-j' indicates that groups and group memberships will be defined in the data source for the authentication protocol (rather than drawn from the Operating System)
'-o' indicates that groups and group memberships will be drawn from the Operating System (rather than defined in the data source for the authentication protocol).
- BIP8104
- Changes a component's trace options.
- Severity
- 10 : Warning
- Explanation
- Syntax (1):
mqsichangetrace componentName [-u | -t] -e egName [-f messageFlow] [-l level] [-m mode] [-c size] [-r]
Syntax (2):
mqsichangetrace componentName -t -b [-l level] [-m mode] [-c size]
- Response
- Command Options:
'componentName' Name of the component whose trace options are to be changed
'-u' indicates user trace (may only be used with '-e')
'-t' indicates service trace.
'-b' denotes tracing of a component other than an execution group
'-e egName' Name of the execution group
'-f messageFlow' Name of the message flow
'-l level' specifies the trace level, 'none', 'normal' or 'debug'
'-m mode' specifies the trace mode, 'safe' or 'fast'
'-c size' specifies the trace file size in kilobytes
'-r' specifies that the log should be reset.
Certain conditions apply to these optional parameters. Please check the online documentation for more information.
- BIP8105
- Creates a broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreatebroker brokerName -i serviceUserId -a servicePassword -q queueManagerName -n dataSourceName [-u dataSourceUserId] [-p dataSourcePassword] [-s unsQMgrName [-j]] [-g configurationTimeout] [-k configurationDelayTimeout] [-w workPath] [-l userLilPath] [-t] [-m] [-v statisticsMajorInterval] [-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath]
- Response
- Command Options:
'brokerName' name of the broker
'-i serviceUserId' the userid that the broker will run under
'-a servicePassword' the password for the broker userid
'-q queueManagerName' the WebSphere MQ queue manager that the broker will use. This is created if it does not exist
'-n dataSourceName' the broker's database name
'-u dataSourceUserId' the userid that the broker uses to access its database
'-p dataSourcePassword' the password for the broker's database userid
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j' enables publish/subscribe access control for the broker
'-g configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message
'-k configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message
'-w workPath' the directory into which trace logs are placed
'-l userLilPath' the directory from which the broker searches for user-supplied libraries
'-t' enables WebSphere MQ fastpath for this broker
'-m' indicates that migration is required from an WebSphere publish/subscribe broker
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records
'-P httpListenerPort' the port that the broker HTTP listener will use
'-c icuConverterPath' delimited list (';' in windows, ':' on unix) of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (userId)
'-z ldapCredentials' the LDAP Credentials (password)
'-x userExitPath' the directory from which the broker searches for all user exits. This path will be added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
- BIP8106
- Creates a Configuration Manager.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateconfigmgr configMgrName -i serviceUserId -a servicePassword -q queueManagerName [-n db2DatabaseToMigrate -u migrationDatabaseUserId -p migrationDatabasePassword] [-s unsQMgrName] [-w workPath]
- Response
- Command Options
'configMgrName' name of the Configuration Manager (may be omitted on Windows)
'-i serviceUserId' the userid that the Configuration Manager will run under
'-a servicePassword' the password for the Configuration Manager userid
'-q queueManagerName' the WebSphere MQ queue manager that the Configuration Manager will use (this is created if it does not exist)
'-n db2DatabaseToMigrate' the name of the DB2 database that contains existing domain data to migrate
'-u migrationDatabaseUserId' the userid of the DB2 database being migrated
'-p migrationDatabasePassword' the password of the DB2 database being migrated
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-w workPath' the directory into which trace logs and the Configuration Manager repository will be placed.
- BIP8107
- Creates a User Name Server.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateusernameserver -i serviceUserId -a servicePassword -q queueManagerName [-d securityDomainName] [-r refreshInterval] [-w workPath] [-g authProtocolDataSource] [-j]
- Response
- Command Options:
'-i serviceUserId' the userid that the User Name Server will run under
'-a servicePassword' the password for the User Name Server userid
'-q queueManagerName' the WebSphere MQ queue manager that the User Name Server will use (it will be created if it does not exist)
'-d securityDomainName' the Security Domain that the User Name Server will use
'-r refreshInterval' number of seconds between each refresh of the User Name Server internal cache
'-w workPath' the directory into which trace logs will be placed
'-g authProtocolDataSource' the name of the data source required by the authentication protocol
'-j' indicates that groups and group memberships will be defined in the data source for the authentication protocol rather than drawn from the Operating System.
- BIP8108
- Deletes a broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideletebroker brokerName [-q] [-w]
- Response
- Command Options:
'brokerName' Name of the component to delete
'-q' deletes the broker's WebSphere MQ queue manager
'-w' deletes the broker's trace files from its work directory.
- BIP8109
- Deletes a Configuration Manager.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteconfigmgr configMgrName [-q] [-w] [-n]
- Response
- Command Options
'configMgrName' name of the Configuration Manager to delete (may be omitted on Windows)
'-q' deletes the Configuration Manager's WebSphere MQ queue manager
'-w' deletes the Configuration Manager's trace files from its work directory
'-n' deletes the Configuration Manager's repository (use with caution).
Note: On Windows platforms, if the Configuration Manager name is omitted 'ConfigMgr' will be used.
- BIP8110
- Deletes the User Name Server.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteusernameserver [-q] [-w]
- Response
- Command Options:
'-q' deletes the User Name Server's WebSphere MQ queue manager.
'-w' deletes the User Name Server's trace files from its work directory.
- BIP8111
- Formats the trace log retrieved using mqsireadlog.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsiformatlog -i inputFileName [-o outputFileName]
- Response
- Command Options:
'-i inputFileName' the file name of a trace log that requires formatting
'-o outputFileName' the file name to write the formatted trace log (default=stdout).
- BIP8112
- Joins a broker with a neighboring WebSphere publish/subscribe broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsijoinmqpubsub brokerName -p qMgrName
- Response
- Command Options:
'brokerName' name of the broker to modify
'-p qMgrName' the WebSphere MQ queue manager of the broker to be joined with.
- BIP8113
- Lists the components that have been created and their WebSphere MQ queue managers.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsilist [-a] [brokerName [-e egName]]
- Response
- Command Options:
'-a' lists all components on this machine.
'brokerName' lists execution groups configured for a broker
'-e egName' lists message flows configured for an execution group.
- BIP8114
- Retrieves the trace log.
- Severity
- 10 : Warning
- Explanation
- Syntax (1):
mqsireadlog componentName (-u | -t) -e executionGroupName [-f] [-o outputFileName]
Syntax (2):
mqsireadlog componentName -t -b subcomponent -f [-o outputFileName]
- Response
- Command Options:
'-u' indicates user trace (may only be used with '-e')
'-t' indicates service trace
'-b subcomponent' name of the command or subcomponent (for example, 'agent')
'-e executionGroupName' Name of the execution group
'-f' specifies that the log file is to be read directly from the file system (this flag is mandatory for service trace)
'-o outputFileName' file name to write the trace log.
- BIP8115
- Displays trace settings.
- Severity
- 10 : Warning
- Explanation
- Syntax (1):
mqsireporttrace componentName (-u | -t) -e executionGroupName [-f messageFlow]
Syntax (2):
mqsireporttrace componentName -t -b
- Response
- Command Options
'-u' indicates user trace (may only be used with '-e')
'-t' indicates service trace
'-b' used for components other than execution groups
'-e executionGroupName' execution group name
'-f messageFlow' message flow name.
- BIP8116
- Starts a component.
- Severity
- 10 : Warning
- Explanation
- Syntax:
v componentName
- Response
- Command Options:
'componentName' broker name, Configuration Manager name or 'UserNameServer'.
- BIP8117
- Stops a component.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsistop componentName [-q] [-i]
- Response
- Command Options:
'componentName' broker name, Configuration Manager name or 'UserNameServer'
'-q' stops the WebSphere MQ queue manager used by the component
'-i' forces the broker to stop immediately (use with caution).
- BIP8118
- Removes knowledge of a neighboring WebSphere publish/subscribe broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsiclearmqpubsub brokerName -n neighboringQMgrName
- Response
- Command Options:
'brokerName' Broker to modify
'-n neighboringQMgrName' the queue manager name of the WebSphere publish/subscribe broker.
- BIP8119
- Displays neighboring WebSphere Publish/Subscribe brokers.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsilistmqpubsub brokerName
- Response
- Command options:
'brokerName' Name of the broker whose neighbors are to be displayed.
- BIP8120
- Migrates broker database tables.
- Severity
- 10 : Warning
- Explanation
- Syntax:
migratetables
- BIP8121
- Lists the contents of a components persistent store.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsibrowse componentName -t persistentStoreTable
- Response
- Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.
- BIP8122
- Displays broker property settings.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsireportproperties brokerName ( -e executionGroupName | -b httplistener | -c externalResource ) -o object [-n attribute | -a | -r]
- Response
- Command Options:
'brokerName' name of the broker
'-e executionGroupName' name of the execution group
'-b httplistener' report properties for the HTTP Listener component
'-c externalResource' report properties for an external resource used by the Broker. Use AllTypes for a list of all resource types
'-o object' object name to report on. Use AllReportableEntityNames for a list of allowable object names
'-n attribute' display the value of the attribute with this name
'-a' display all attribute values (non-recursive)
'-r' display all attribute values (recursive).
- BIP8123
- This command changes broker property values.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeproperties brokerName ( -e executionGroupName | -b httplistener | -c configurableService ) -o object -n name -v value
- Response
- Command options:
'brokerName': name of the broker
'-e executionGroupName': execution group name
'-b httplistener': change properties for the HTTP Listener component
'-c configurableService': change properties for a configurable service used by the broker
'-o object': object name
'-n name': attribute name
'-v value': attribute value
- BIP8124
- Changes and reports a component's details.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsiservice [-v] [componentName [-r label=value]] [-m messageNumber [-c messageCatalog]] [-t]
- Response
- Command Options:
'-v' is the product version information
'componentName' is the name of the component to query for its registry data
'-r label=value' sets the registry key 'label' to 'value'. Use with caution.
'-r label=' sets the registry key 'label' to null. Use with caution.
'-r label' deletes the registry key 'label'. Use with caution.
'-m messageNumber' is a message number to output.
'-c messageCatalog' is the name of the message catalog to use.
'-t' Output information about current time and timezone
- BIP8125
- Exports or Imports a message set from or into a repository.
- Severity
- 10 : Warning
- Explanation
- Syntax (1):
mqsiimpexpmsgset -e -n mrmDataSourceName -u mrmDataSourceUserId -p mrmDataSourcePassword -s sourceMessageSetName -l sourceMessageSetLevel -f fileName
Syntax (2):
mqsiimpexpmsgset -i -n mrmDataSourceName -u mrmDataSourceUserId -p mrmDataSourcePassword -f fileName
- Response
- Command Options
'-e' exports a message set.
'-i' imports a message set.
'-n mrmDataSourceName' the component's database name.
'-u mrmDataSourceUserId' the userid that the component uses to access the database.
'-p mrmDataSourcePassword' the password that the component uses to access its database
'-s sourceMessageSetName' the message set being exported or imported
'-l sourceMessageSetLevel' the level of the message set
'-f fileName' the file being imported, or the file being exported.
- BIP8126
- Creates a new message set as a copy of an existing message set within a repository.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicopymsgset -n mrmDataSourceName -u mrmDataSourceUserId -p mrmDataSourcePassword -s sourceMessageSetName -l sourceMessageSetLevel -t targetMessageSetName -k targetMessageSetLevel
- Response
- Command Options
'-n mrmDataSourceName' the component's database name
'-u mrmDataSourceUserId' the userid that the component uses to access the database
'-p mrmDataSourcePassword' the password that the component uses to access its database
'-s sourceMessageSetName' the message set being copied
'-l sourceMessageSetLevel' the level of the message set being copied
'-t targetMessageSetName' the name of the target message set
'-k targetMessageSetLevel' the target message set level.
- BIP8127
- Checks the contents of a broker's subscriptions table looking for CBR filters that include string literals with escape characters.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicbrreport brokerName
- Response
- Command Options
'brokerName' Name of the broker.
- BIP8128
- Reloads a broker's execution groups.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsireload brokerName [-e egName]
- Response
- Command Options:
'brokerName' Broker name
'-e egName' Execution group name to reload.
- BIP8129
- Sets the username and password to be used in a compute node in the broker.
- Severity
- 10 : Warning
- Explanation
- Syntax (1):
mqsisetdbparms brokerName -n dataSourceName [-u dataSourceUserId] -p dataSourcePassword
Syntax (2):
mqsisetdbparms brokerName -n dataSourceName -d
- Response
- Command Options
'brokerName' the broker name
'-n dataSourceName' the database name
'-u dataSourceUserId' the userid used to access the database
'-p dataSourcePassword' the password used to access its database
'-d' delete the database userid and password information.
- BIP8130
- Execution Group: <insert_0> - <insert_1>
- Severity
- 0 : Information
- BIP8131
- MessageFlow: <insert_0>
- Severity
- 0 : Information
- BIP8132
- <insert_0> is not a valid subcomponent name.
- Severity
- 20 : Error
- Explanation
- The name selected is not a valid subcomponent.
- Response
- The name selected is not supported. Select a different subcomponent name.
- BIP8133
- Unable to write to the selected output file <insert_0>
- Severity
- 20 : Error
- Explanation
- The file selected could not be written to.
- Response
- Ensure that the file selected is not in a protected directory, that it is not read-only and that it is not being used or locked by another user. Also check that the directory into which the file will be written has adequate free space.
- BIP8134
- Unable to alter WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be altered.
- Response
- Locate and resolve the problem and retry the command.
- BIP8135
- Unable to create files: operating system return code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occurred creating files in response to a command. This may be because the user does not have the required authorization.
- Response
- Check that the user has the required authority to create files and retry.
- BIP8136
- Unable to change the ownership of files: operating system return code <insert_0>.
- Severity
- 20 : Error
- Explanation
- An error occurred changing the ownership of files in response to a command. This may be because the user does not have the required authorization.
- Response
- Check that the user has the required authority to create files and retry.
- BIP8137
- Unable to change the access permission mode of file <insert_0> : operating system return code <insert_1>.
- Severity
- 20 : Error
- Explanation
- An error occurred while changing the access permissions for the specified file. This may be because the user does not have the required authorization to carry out this action.
- Response
- Check that the user has the required authority to create and modify files. Retry the operation.
- BIP8138
- Userid <insert_0> cannot be used by this component.
- Severity
- 20 : Error
- Explanation
- The userId selected cannot be used by the component. This may be because the userId does not have the required authorization or that the userId is invalid for operations that the component requires, for example, if a component is to use fastbind (-t) on UNIX platforms it must use the ServiceUserId 'mqm'.
- Response
- Check that the user has the required authority to create files and retry.
- BIP8139
- The user issuing this command does not have the required permissions to complete the command.
- Severity
- 20 : Error
- Explanation
- The userId that the command is being run under must have the authority to end broker processes.
- Response
- Check that the user has the required authority to end the broker's processes.
- BIP8140
- Unable to find service userid <insert_0> in component <insert_1>.
- Severity
- 20 : Error
- Explanation
- Cannot authenticate service userid in component.
- Response
- Use mqsichangebroker to alter the service userid and then retry the command.
- BIP8141
- Unauthorized userid <insert_0> in component <insert_1>.
- Severity
- 20 : Error
- Explanation
- The service userid is not authorized to run the component.
- Response
- Use mqsichangebroker to alter the service userid and retry the command.
- BIP8142
- Unable to set process userid.
- Severity
- 20 : Error
- Explanation
- UNIX setuid command had failed.
- Response
- Verify with your system administrator that file permissions for this command are set correctly.
- BIP8143
- Unable to change group ownership of directory <insert_1> to <insert_2>. (error <insert_0>)
- Severity
- 20 : Error
- Explanation
- Directory <insert_1> is required to have <insert_2> as group owner.
- Response
- Use a different -w value or consult system administrator for possible causes of this error.
- BIP8144
- Unable to create directory <insert_0>. (error <insert_1>)
- Severity
- 20 : Error
- Explanation
- Directory <insert_0> creation has failed due to directory permission setting.
- Response
- Use a different -w value or consult system administrator for possible causes of this error.
- BIP8145
- Execution Group process IDs <insert_0> were forced to terminate.
- Severity
- 0 : Information
- Explanation
- The Broker was shutdown forcibly, this caused Execution Group processes to be killed.
- Response
- This action may leave system, database, WebSphere MQ or Application resources in a locked state. Some resource locks may need freeing manually, others will not need any action to be taken.
- BIP8146
- Unable to retrieve the SQL primitives supported by the Database.
- Severity
- 20 : Error
- Explanation
- The command attempted to retrieve the SQL primitives that the Database supports, however the primitives retrieved indicate that the Database could not be contacted successfully. Refer to the Administration Guide for information about Database setup, ensure that the Database libraries are available in the library path and that the ODBC ini file is correct.
- Response
- Correct the problem and retry the command.
- BIP8147
- Changes a broker's configuration. Syntax: changebroker [s=unsQMgrName] [l=userLilPath] [g=configurationTimeout] [k=configurationDelayTimeout] [x=userExitPath] [e=activeUserExits]
- Severity
- 10 : Warning
- Explanation
- Command Options:
's=unsQMgrName' the WebSphere MQ queue manager of the User Name Server.
'l=userLilPath' indicates where 'lil' files are loaded from.
'g=configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message.
'k=configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message.
'x=userExitPath' the directory from which the broker searches for all user exits. This path will be added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
'e=activeUserExits' the active user exits. By default, user exits are inactive. Adding a userExit name to this list, changes its default state to active for this broker. The default state can be overridden at the execution group or message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and the execution group will fail to start.
- BIP8148
- Changes a User Name Server's configuration. Syntax: changeusernameserver [r=refreshInterval] [-g authProtocolDataSource] [-j | -o]
- Severity
- 10 : Warning
- Explanation
- Command Options
'r=refreshInterval' number of seconds between each refresh of the User Name Server internal cache
'g=authProtocolDataSource' the name of the data source required by the authentication protocol
'j=yes' indicates that groups and group memberships will be defined in the data source for the authentication protocol (rather than drawn from the Operating System)
'o=yes' indicates that groups and group memberships will be drawn from the Operating System (rather than defined in the data source for the authentication protocol)
- BIP8149
- Changes a component's trace options. Syntax (1): changetrace (u=yes | t=yes) ,e=executionGroupName [,f=messageFlow] [,l=level] [,m=mode] [,c=size] [,r=yes] Syntax (2): changetrace t=yes ,b=yes [,l=level] [,m=mode] [,c=size]
- Severity
- 10 : Warning
- Explanation
- Command Options
'u=yes' indicates user trace (only with flag 'e')
't=yes' indicates service trace
'b=yes' is for components other than execution groups
'e=executionGroupName' execution group name
'f=messageFlow' message flow name
'l=level' specifies the trace level, 'none', 'normal' or 'debug'
'm=mode' specifies the trace mode, 'safe' or 'fast'
'c=size' specifies the trace size in kilobytes
'r=yes' specifies that the log should be reset
Certain conditions apply to these optional parameters. Please check the online documentation for more information.
- BIP8150
- Displays trace settings. Syntax (1): reporttrace (u=yes | t=yes) ,e=executionGroupName [,f=messageFlow] Syntax (2): reporttrace t=yes ,b=yes
- Severity
- 10 : Warning
- Explanation
- Command Options
'u=yes' indicates user trace (only with flag 'e')
't=yes' indicates service trace
'b=yes' is for components other than execution groups
'e=executionGroupName' execution group name
'f=messageFlow' message flow name.
- BIP8151
- Lists the components that have been created and their WebSphere MQ queue managers. Syntax: list [e=executionGroupName]
- Severity
- 10 : Warning
- Explanation
- Command Options
'e=executionGroupName' requests a list of message flows configured for an execution group.
If the execution group is not specified, this command requests a list of execution groups configured for the broker.
- BIP8152
- Stops a component. Syntax: stopcomponent
- Severity
- 10 : Warning
- BIP8153
- Migrated database tables for broker <insert_0>
- Severity
- 0 : Information
- BIP8154
- An error occurred while locking the registry file <insert_0> : <insert_1>.
- Severity
- 20 : Error
- Explanation
- The program cannot continue, because of an internal error.
- Response
- Contact your WebSphere Message Brokers administrator.
- BIP8155
- Migrates database tables for a broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
v brokerName [-i serviceUserId] [-a servicePassword]
- Response
- Command options
'brokerName' name of the broker whose tables are to be migrated
'-i' the userid that the broker service should run under
'-a' the password for the broker service userid.
- BIP8156
- Broker database being migrated is in an inconsistent state
- Severity
- 20 : Error
- Explanation
- The Broker database being migrated is in an inconsistent state. ClientId's referenced in tables can not be found in the BCLIENTUSER table.
- Response
- Restore your Broker database tables to a known good state, then try migrating the tables again.
- BIP8158
- Invalid format for command.
- Severity
- 20 : Error
- Explanation
- The string <insert_0> contained no valid formatted command.
- Response
- Consult the user manual and correct your errors.
- BIP8159
- Unknown parameter <insert_0>.
- Severity
- 20 : Error
- Explanation
- The parameter <insert_0> is not valid for this command.
- Response
- Check the spelling of the parameter and check if it is valid for this command.
- BIP8160
- The verb <insert_0> is unknown.
- Severity
- 20 : Error
- Explanation
- The verb <insert_0> is not a valid verb.
- Response
- Consult the user manual and correct your errors.
- BIP8161
- Start was issued.
- Severity
- 0 : Information
- Explanation
- Start was issued and recognized.
- Response
- Everything was OK.
- BIP8162
- MVS stop was issued.
- Severity
- 0 : Information
- Explanation
- MVS stop was issued and recognized.
- Response
- Everything was OK.
- BIP8163
- Missing closing single quote. Opened at <insert_0>.
- Severity
- 20 : Error
- Explanation
- You opened a quoted text at <insert_0>, but never closed it.
- Response
- Check where you intended to end the quoted text and issue the corrected command.
- BIP8164
- A problem was encountered while attempting to create/delete/list security ACL information.
- Severity
- 20 : Error
- Explanation
- The operation was not completed successfully.
- Response
- Check messages in the system log for related errors and retry the operation. If the problem still occurs, contact your IBM support center.
- BIP8165
- An internal error has occurred while accessing the message repository.
- Severity
- 20 : Error
- Explanation
- This is an internal error. There may be insufficient memory to complete the operation.
- Response
- Increase the amount of virtual memory available on your system and retry the command. If the problem persists turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry the operation and contact your IBM support center.
- BIP8166
- The message set to be imported has been finalized in this repository since the export file was created.
- Severity
- 20 : Error
- Explanation
- A record of this message set, indicating that it was finalized, exists in this repository because another message set was based on it before it was deleted.
- Response
- Delete all message sets based on this message set or import a finalized version of the message set.
- BIP8167
- Unknown message repository database name <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message repository database name <insert_0> could not be located.
- Response
- This error is most probably a result of either, an incorrect name that was provided for the MRMDataSourceName on the mqsiimpexpmsgset command, or the ODBC data source name <insert_0> was not set up correctly, or has been deleted. Check that the message repository database name has been correctly set up as an ODBC system data source that has been configured for the correct database.
- BIP8168
- The userid and/or password are not authorized for connection to the message repository database <insert_0>.
- Severity
- 20 : Error
- Explanation
- The message repository database name <insert_0> could not be opened because the userid and/or password is not authorized.
- Response
- This error is most probably a result of either, incorrect userid and password that were provided for the MRMDataSourceUserId and MRMDataSourcePassword on the mqsiimpexpmsgset command, or the userid has not been assigned access rights to the message repository database by the database management system. Check that the message repository database access rights have been correctly configured.
- BIP8169
- An internal error has occurred while accessing the message repository.
- Severity
- 10 : Warning
- Explanation
- A SAX parser exception occurred. The text of the exception is <insert_0>.
- Response
- If the error persists contact your IBM support center.
- BIP8170
- Failed to import as all plug-ins registered for the message set have not been installed.
- Severity
- 20 : Error
- Explanation
- The import file refers to plug-ins which have not been installed.
- Response
- Install all plug-ins registered for the message set and retry the command.
- BIP8171
- An internal error has occurred while accessing the message repository.
- Severity
- 10 : Warning
- Explanation
- A DOM parser exception occurred. The text of the exception is <insert_0>.
- Response
- If the error persists contact your IBM support center.
- BIP8172
- An unexpected exception has occurred while accessing the message repository.
- Severity
- 10 : Warning
- Explanation
- The text of the exception is <insert_0>.
- Response
- If the error persists contact your IBM support center.
- BIP8173
- An internal error has occurred while accessing the message repository.
- Severity
- 20 : Error
- Explanation
- The error was due to invalid content of an XML document.
- Response
- If the error persists contact your IBM support center.
- BIP8174
- An internal error has occurred while accessing the message repository.
- Severity
- 20 : Error
- Explanation
- The error was due to invalid content of an XML document.
- Response
- If the error persists contact your IBM support center.
- BIP8175
- Duplicate message set identifier.
- Severity
- 20 : Error
- Explanation
- The message set to be imported already exists in this repository.
- Response
- Delete the message set and retry the command.
- BIP8176
- Failed to access export file <insert_0>.
- Severity
- 20 : Error
- Explanation
- The error code <insert_1> was detected.
- Response
- Check that you have access rights to the export file.
- BIP8177
- Failed to open import file <insert_0>.
- Severity
- 20 : Error
- Explanation
- There was a failure opening the import file <insert_0>.
- Response
- Check the filename and path entered and that you have access rights to the file.
- BIP8178
- The database transaction log size has been exceeded.
- Severity
- 20 : Error
- Explanation
- You have exceeded the transaction log size of the database.
- Response
- Increase the size of the database transaction log size on your system and retry the command.
- BIP8179
- Internal error while accessing message repository.
- Severity
- 10 : Warning
- Explanation
- An internal inconsistency has been detected while accessing the message repository. The MRM return code <insert_0> was detected.
- Response
- This is an internal error. Turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry the operation and contact your IBM support center.
- BIP8180
- The message repository database <insert_0> has not been initialized correctly.
- Severity
- 20 : Error
- Explanation
- It is not possible to access the message repository because the database <insert_0> has not been properly initialized.
- Response
- This error is most probably a result of a setup inconsistency. You must delete your Configuration Manager (using the mqsideleteconfigmgr command with the -n and -m options) and then recreate your Configuration Manager (using the mqsicreateconfigmgr command with the -n and -m options).
- BIP8181
- An error has occurred while connecting to the message repository.
- Severity
- 20 : Error
- Explanation
- This error is most probably a result of an incorrect userid that was provided for the MRMDataSourceUserId on the mqsiimpexpmsgset command, or the userid has not been assigned access rights to the message repository database by the database management system.
- Response
- Check that the message repository database access rights have been correctly configured. Alternatively, if the userid is correct, then this is an internal error. The SQL code (<insert_1>) and SQL state (<insert_2>) were returned. Check your database manager documentation for further information on this error.
- BIP8182
- Database manager not started.
- Severity
- 20 : Error
- Explanation
- The message repository database name, <insert_0>, could not be accessed. The database manager has either not been started, or has been stopped.
- Response
- Start the database manager and retry the command.
- BIP8183
- A referenced resource does not exist in the message repository.
- Severity
- 20 : Error
- Explanation
- A resource was referenced, but it does not exist in the message repository.
- Response
- This is an internal error. Turn on mqsiimpexpmsgset utility tracing to capture details of the error, retry the operation and contact your IBM support center.
- BIP8184
- Message set is not complete.
- Severity
- 20 : Error
- Explanation
- A message set must be complete before performing an export. A message set is incomplete if it contains any incomplete messages. A message is incomplete if its type is incomplete. An empty type is incomplete if the type composition is not empty except for type composition message where the type content is not closed. A type is also incomplete if it has incomplete plug-in layer information or if it has an incomplete child. Similarly, a child is incomplete if its type is incomplete.
- Response
- Complete the message set and retry the command.
- BIP8185
- Duplicate message set name.
- Severity
- 20 : Error
- Explanation
- A message set named <insert_0> already exists in this repository.
- Response
- Delete the message set and retry the command.
- BIP8186
- The message set <insert_0> with level <insert_1> does not exist in the message repository.
- Severity
- 20 : Error
- Explanation
- The message set <insert_0> with level <insert_1> is referenced, but it does not exist in the message repository.
- Response
- Correct the problem and retry the command.
- BIP8187
- Statistics <insert_0> settings for flow <insert_1> in execution group <insert_2> - On?: <insert_3>, ThreadDataLevel: <insert_4>, NodeDataLevel: <insert_5>, OutputFormat: <insert_6> , AccountingOrigin <insert_7>.
- Severity
- 0 : Information
- BIP8188
- Invalid message set level.
- Severity
- 20 : Error
- Explanation
- The level <insert_0> for message set <insert_1> is invalid.
- Response
- Correct the message set level and retry the command.
- BIP8189
- Changes a broker's statistics options.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeflowstats brokerName (-a | -s) (-e executionGroupName | -g) (-f messageFlow | -j) [-c control] [-t threadData] [-n nodeData] [-r] [-o outputFormat] [-b accountingOrigin]
- Response
- Command Options:
'brokerName' name of the broker
'-a' indicates archival of statistics
'-s' indicates snapshot publishing
'-e executionGroupName' execution group name
'-g' indicates all execution groups
'-f messageFlow' message flow name
'-j' indicates all message flows
'-c control' starts/stops collection: values allowed are 'active' or 'inactive'
'-t threadData' specifies the thread statistics level: values allowed are 'none' or 'basic'
'-n nodeData' specifies the node statistics level: values allowed are 'none', 'basic' or 'advanced'
'-r' resets the archival, i.e. deletes all previous records currently held
'-o outputFormat' specifies the output format: values allowed are 'usertrace', 'xml' or (on zOS only) 'smf'
'-b accountingOrigin' indicates using accounting origin to segregate the statistics.
- BIP8190
- Displays statistics settings.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsireportflowstats BrokerName ( -a | -s | -a -s ) ( -e executionGroupName | -g ) ( -f messageFlow | -j )
- Response
- Command Options
'brokerName' name of the broker
'-a' indicates archival of statistics
'-s' indicates snapshot publishing
'-e executionGroupName' execution group name
'-g' indicates all execution groups
'-f messageFlow' message flow name
'-j' indicates all message flows.
- BIP8191
- Changes a component's statistics options. Syntax : changeflowstats ( a=yes [,r=yes] | s=yes ) ( ,e=ExecutionGroupLabel | ,g=yes ) ( ,f=MessageFlow | ,j=yes ) [ ,l=Level ] [ ,t=ThreadData ] [ ,n=NodeData ] [,o=OutputFormat] [,b=AccountingOrigin]
- Severity
- 10 : Warning
- Explanation
- Command Options
'a' indicates Archival of statistics. 'r' resets the Archival, i.e. deletes all previous records currently held. 's' indicates Snapshot publishing. 'e' Execution Group name. 'g' indicates all Execution Groups. 'f' Message Flow name. 'j' indicates all Message Flows. 'c' starts/stops collection: values allowed are 'active' or 'inactive'. 't' specifies the thread statistics level: ThreadData values allowed are 'none' or 'basic'. 'n' specifies the node statistics level: NodeData values allowed are 'none', 'basic' or 'advanced'. 'o' specifies the output format: values allowed are 'usertrace', 'xml' or 'smf'. 'b' indicates using Accounting Origin to segregate the statistics.
- BIP8192
- Displays statistics settings. Syntax : reportflowstats ( a=yes, | s=yes, | a=yes,s=yes, ) ( ,e=ExecutionGroupLabel | ,g=yes ) ( ,f=MessageFlow | ,j=yes )
- Severity
- 10 : Warning
- Explanation
- Command Options
'a' indicates Archival of statistics. 's' indicates Snapshot publishing. 'e' Execution Group name. 'g' indicates all Execution Groups. 'f' Message Flow name. 'j' indicates all Message Flows.
- BIP8193
- Creates a security ACL group entry.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateaclgroup (-f fileName | ( (-g groupName | -u userName) -x accessLevel (-b broker | -e executionGroup | -s | -t | -r) ) )
- Response
- Command Options:
'-f fileName' Imported ACL list file name.
'-g groupName' Windows group name for the desired action.
'-u userName' Windows user name for the desired action.
'-x accessLevel' Desired security access level for specified object (F, E, D, V).
'-b broker' The operation references the specified broker.
'-e executionGroup' The operation references the specified execution group.
'-s' The operation references the subscriptions.
'-t' The operation references the topology.
'-r' The operation references the root topic.
- BIP8194
- Deletes a security ACL group entry.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteaclgroup (-f fileName | (-g groupName | -u userName) (-b broker | -e executionGroup | -s | -t | -r) )
- Response
- Command Options:
'-f fileName' Imported ACL list file name
'-g groupName' Group name for the desired action
'-u userName' User name for the desired action
'-b broker' The operation references the specified broker
'-e executionGroup' The operation references the specified execution group
'-s' The operation references the subscriptions
'-t' The operation references the topology
'-r' The operation references the root topic
- BIP8195
- Lists the current security ACL group(s).
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsilistaclgroup [-g groupName | -u userName | -b broker | -e executionGroup | -s | -t | -r]
- Response
- Command Options:
'-g groupName' ACLs referencing the specified group
'-u userName' ACLs referencing the specified user
'-b broker' ACLs referencing the specified broker
'-e executionGroup' ACLs referencing the specified execution group
'-s' ACLs referencing the subscriptions table
'-t' ACLs referencing the publish/subscribe topology
'-r' ACLs referencing the root topic.
- BIP8196
- Statistics <insert_0> settings for flow <insert_1> in execution group <insert_2> - On?: <insert_3>, ThreadDataLevel: <insert_4>, NodeDataLevel: <insert_5>, OutputFormat: <insert_6>.
- Severity
- 0 : Information
- BIP8197
- Unable to set the security attributes for WebSphere MQ Queue <insert_1> on Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to set the Group or Principal security attributes for a WebSphere MQ Queue for the related Queue Manager.
- Response
- Ensure that the required Group or Principal, <insert_2> is available and that the user issuing this command is a member of the mqm group.
- BIP8198
- An attempt to start the Queue Manager for WebSphere MQ Queue Manager <insert_0> was unsuccessful and returned WebSphere MQ code <insert_1>.
- Severity
- 20 : Error
- Explanation
- This command attempts to start the required WebSphere MQ Queue Manager.
- Response
- Ensure that the required Queue Manager, <insert_0> is available and that the user issuing this command is a member of the mqm group.
- BIP8199
- Unable to set the security attributes for WebSphere MQ Queue Manager <insert_0>.
- Severity
- 20 : Error
- Explanation
- This command attempts to set the Group or Principal security attributes for a WebSphere MQ Queue Manager.
- Response
- Ensure that the required Group or Principal, <insert_1> is available and that the user issuing this command is a member of the mqm group.
- BIP8201
- User Name Server starting with refresh interval <insert_0>.
- Severity
- 0 : Information
- Explanation
- The User Name Server is being started with a refresh interval that determines (in seconds) how frequently the native security subsystem's user/group registry will be reread.
- Response
- No user action required.
- BIP8202
- User Name Server UUID has been set to <insert_0>.
- Severity
- 0 : Information
- Explanation
- The User Name Server requires a UUID to identify it to the domain.
- Response
- No user action required.
- BIP8203
- User Name Server UUID could not be established.
- Severity
- 30 : Severe error
- Explanation
- The User Name Server requires a UUID to identify it to the domain, a new UUID was not successfully generated.
- Response
- Restart the User Name Server. Contact your IBM support center if the problem persists.
- BIP8204
- User Name Server is registering a client with UUID <insert_0>, and cache version <insert_1>.
- Severity
- 0 : Information
- Explanation
- The User Name Server maintains a registry of clients, uniquely identified by their UUID, and uses the cache version to determine whether a client that is re-registering has an up-to-date version of user and group information.
- Response
- No user action required.
- BIP8205
- User Name Server failed to send a response/report to a configuration request,
- Severity
- 20 : Error
- Explanation
- The User Name Server could not deliver a response/report message.
- Response
- Check preceding system log entries for errors from the underlying messaging subsystem.
- BIP8206
- User Name Server received an acknowledgement from an unregistered client with UUID <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The User Name Server maintains a registry of clients, uniquely identified by their UUID, an acknowledgement has been received from a client whose UUID is not in the registry.
- Response
- Contact your IBM support center if the problem persists.
- BIP8207
- User Name Server failed to send updated user/group information to client with UUID <insert_0>.
- Severity
- 20 : Error
- Explanation
- The User Name Server could not deliver user/group information to a registered client.
- Response
- Check preceding system log entries for errors from the underlying messaging subsystem.
- BIP8208
- User Name Server refresh interval has been reset to <insert_0>.
- Severity
- 0 : Information
- Explanation
- The User Name Server's refresh interval determines (in seconds) how frequently the native security subsystem's user/group registry will be reread.
- Response
- No user action required.
- BIP8209
- User Name Server could not retrieve user/group information from the native security subsystem.
- Severity
- 10 : Warning
- Explanation
- The User Name Server will continue processing using its cached version of user/group information.
- Response
- Check preceding system log entries for errors from the underlying security subsystem.
- BIP8210
- User Name Server has processed <insert_0> of <insert_1> usernames.
- Severity
- 0 : Information
- Explanation
- The User Name Server retrieves user/group information from the native security subsystem's user/group registry.
- Response
- No user action required.
- BIP8211
- User Name Server failed to retrieve <insert_1> <insert_0> entries from the native security subsystem.
- Severity
- 0 : Information
- Explanation
- The User Name Server failed to read a number (<insert_1>) of user or group (<insert_0>) entries, and will continue processing using an incomplete cache of user/group information.
- Response
- Check trace entries for an indication of which <insert_0> entries could not be read.
- BIP8212
- User Name Server failed to retrieve more than <insert_1> <insert_0> entries from the native security subsystem.
- Severity
- 10 : Warning
- Explanation
- The User Name Server failed to read more than a given number (<insert_1>) of user or group (<insert_0>) entries, and will not attempt to read any further <insert_0> entries. Processing will continue using an incomplete cache of user/group information.
- Response
- Check trace entries for an indication of which <insert_0> entries could not be read.
- BIP8213
- User Name Server failed to retrieve any <insert_0> entries from the native security subsystem.
- Severity
- 20 : Error
- Explanation
- The User Name Server did not read any user or group (<insert_0>) entries, and will not continue processing.
- Response
- Check trace entries for an indication of why no <insert_0> entries were found.
- BIP8214
- Object not found
- Severity
- 20 : Error
- Explanation
- The Configuration Manager repository object <insert_0> of type <insert_1> does not exist.
- Response
- Ensure that you have specified the correct object name, type and that the object has been defined to the Configuration Manager.
- BIP8215
- The ACL command resulted in no change.
- Severity
- 10 : Warning
- Explanation
- The ACL command resulted in no change.
- Response
- The most likely cause of this return code is attempting to delete an Access Control Entry which does not exist or create one which already exists.
- BIP8216
- Trace file <insert_0> is not readable by this version of the product. The file was written by version <insert_1>, while this product is version <insert_2>.
- Severity
- 20 : Error
- Explanation
- The trace file contains data that cannot be understood by this product, and the trace reader command was not able to process the file.
- Response
- Ensure that the correct version of the product is used to read the trace files.
- BIP8217
- Trace file <insert_0> is corrupt, and has not been fully read.
- Severity
- 30 : Severe error
- Explanation
- The trace file contains data other than complete trace records for the current product version, and the trace reader command was not able to process the file.
- Response
- Ensure that the correct product version is used to read trace files. If the correct version is being used and this error still occurs, ensure that enough disk space is available to store trace data, and that none of the files are limited by other means (e.g., ulimit on UNIX platforms).
- BIP8218
- Unable to clear messages for WebSphere MQ Queue <insert_0> from Queue Manager <insert_1>.
- Severity
- 20 : Error
- Explanation
- This command attempts to clear a WebSphere MQ queue but was unable to do so.
- Response
- Locate and resolve the problem and retry the command. This could be because a whole broker, an Execution Group, a Config Manager, or a User Name Server is still running. Stop all processes associated with the queue manager, and retry the command.
- BIP8219
- Service binary path for component <insert_0> changed to <insert_1>; previous value was <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The service location for this component was incorrect for this installation. The location has been updated to the correct value.
- Response
- None.
- BIP8220
- Service binary path for component <insert_0> could not be changed to <insert_1>: error <insert_3>. Current value remains <insert_2>.
- Severity
- 20 : Error
- Explanation
- The service location for this component is incorrect for this installation. The command attempted to change this location, but was unsuccessful.
- Response
- Determine why the change was unsuccessful, correct the problem, and re-run the command.
- BIP8221
- <insert_0>: <insert_1> (Version <insert_3>) - <insert_2>
- Severity
- 0 : Information
- BIP8222
- Unable to find ODBCINI file <insert_0>.
- Severity
- 20 : Error
- Explanation
- Could not find the ODBCINI file <insert_0>, which is specified by the ODBCINI environment variable.
- Response
- Ensure that the ODBCINI environment variable points to an existing ODBCINI file.
- BIP8223
- User <insert_1> is not a member of group <insert_0>.
- Severity
- 20 : Error
- Explanation
- User <insert_1> is not a member of group <insert_0> and therefore does not have the privilege to use this command.
- Response
- Talk to your system administrator to obtain the membership of group <insert_0> or login as a user who does have the membership.
- BIP8224
- Internal error while trying trying to load library <insert_0>.
- Severity
- 20 : Error
- Explanation
- Could not load an internal library <insert_0>.
- Response
- Ensure that the library is correctly installed.
- BIP8225
- <insert_0> is not a known component.
- Severity
- 20 : Error
- Explanation
- The name provided is not a known component.
- Response
- Provide a different component name.
- BIP8226
- Executing system command <insert_0>.
- Severity
- 0 : Information
- BIP8250
- The Configuration Manager's user/group cache is empty.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager receives user and group information from the User Name Server. The cache will be empty if the Configuration Manager has not yet successfully registered with the User Name Server.
- Response
- Check preceding system log entries for related errors. Check that the User Name Server has been started. Contact your IBM support center if the problem persists.
- BIP8251
- The Configuration Manager failed to send a registration/heartbeat message to the User Name Server.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager could not deliver a registration/heartbeat message to the User Name Server.
- Response
- Check preceding system log entries for errors from the underlying messaging subsystem. Contact your IBM support center if the problem persists.
- BIP8252
- The Configuration Manager failed to send an acknowledgement message to the User Name Server.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager could not deliver an acknowledgement message to the User Name Server.
- Response
- Check preceding system log entries for errors from the underlying messaging subsystem. Contact your IBM support center if the problem persists.
- BIP8253
- Error in parsing a message from the User Name Server, invalid tag <insert_0>.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager has received a message from the User Name Server that it is unable to parse.
- Response
- Contact your IBM support center if the problem persists.
- BIP8254
- Internal Error while parsing a message from the User Name Server.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager has encountered an internal error while attempting to parse a message from the User Name Server.
- Response
- Contact your IBM support center if the problem persists.
- BIP8255
- User Name Services are disabled.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs.
- Response
- No action unless you want to manage topic ACLs. If you want to manage topic ACLs you must reconfigure the Configuration Manager by providing a queue manager name for the User Name Server.
- BIP8256
- Failed to initialize the interface to the User Name Server.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. Initialization failures occur when the underlying transport encounters problems.
- Response
- Check preceding system log entries for related errors.
- BIP8257
- The Configuration Manager has reconnected to WebSphere MQ for User Name Services.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. The Configuration Manager was unable to communicate via WebSphere MQ transports but communication has been reestablished.
- Response
- Investigate the reasons for the failure of the WebSphere MQ product.
- BIP8258
- Successfully registered with the User Name Server using UUID <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. The initial registration with the User Name Server succeeded.
- Response
- No user action required.
- BIP8259
- The Configuration Manager has not yet registered with the User Name Server.
- Severity
- 10 : Warning
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. Registration is an asynchronous operation but severe delays require investigation.
- Response
- Check that the User Name Server has been started. Check preceding system log entries for related errors.
- BIP8260
- Successfully initialized the interface to the User Name Server.
- Severity
- 0 : Information
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. The Configuration Manager will now asynchronously register with the User Name Server.
- Response
- No user action required.
- BIP8261
- The Configuration Manager is encountering problems in communicating with the User Name Server.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. Messaging failures are occurring.
- Response
- Check preceding system log entries for related errors. If the problem persists contact your IBM support center.
- BIP8262
- Failed to initialize the interface to the User Name Server, a UUID could not be established.
- Severity
- 20 : Error
- Explanation
- The Configuration Manager communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. The Configuration Manager requires a UUID to identify it to the User Name Server, a new UUID was not successfully generated.
- Response
- Restart the Configuration Manager. Contact your IBM support center if the problem persists.
- BIP8263
- User Name Server has found a user <insert_0> that is not a member of any groups. This user will be ignored.
- Severity
- 10 : Warning
- Explanation
- Each user must be a member of at least one group.
- Response
- Use the OS tools to assign the user <insert_0> to at least one group.
- BIP8280
- Successfully initialized interface to the NT security domain, <insert_0>.
- Severity
- 0 : Information
- Explanation
- A component of WebSphere Message Brokers has successfully initialized the NT security domain.
- Response
- No user action required.
- BIP8281
- Error in initializing the NT security domain: return code <insert_0>; subsystem error code <insert_1>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use as a supplier of user and group information, without success.
- Response
- Check NT security subsystem documentation for the reported error.
- BIP8282
- Error in call <insert_0> to the NT security domain with return code <insert_1>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to call the NT security domain. The security subsystem returned an error code.
- Response
- Check NT security subsystem documentation for the reported error. Restart the relevant service component (UserNameServer, or Configuration Manager). Ensure that a Domain Controller, either Primary or Backup, is available.
- BIP8283
- Error in determining the domain controller in the NT security domain, return code <insert_0>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use as a supplier of user and group information. The security subsystem returned an error code.
- Response
- Check NT security subsystem documentation for the reported error.
- BIP8284
- Failed to find NT security domain, <insert_0>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers has failed to locate the specified NT security domain.
- Response
- Check that the domain name was correctly specified and that it is accessible from this machine.
- BIP8285
- Insufficient authority to access NT security domain, <insert_0>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize the NT security domain for use as a supplier of user and group information. The userid under which the component is running does not have the authority to access this information in the specified domain.
- Response
- Check that the correct domain name was specified in the configuration command that created this component and check that its service id has administrative or account operator privilege in that domain.
- BIP8286
- Error in Operating System call <insert_0>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to call the Operating System. The security subsystem returned an error code.
- Response
- Check Operating system documentation and environment.
- BIP8301
- Failed to send initial registration to the User Name Server.
- Severity
- 20 : Error
- Explanation
- The Broker communicates with the User Name Server in order to procure user and group information for configuring topic ACLs. This broker has never established communication with the User Name Server and has no cached user and group information. The process will be terminated.
- Response
- Check that the User Name Server is running. Check preceding system log entries for related errors.
- BIP8302
- A problem occurred in registering with the User Name Server.
- Severity
- 20 : Error
- Explanation
- The Broker communicates with the User Name Server in order to procure user and group information for processing topic ACLs. The Broker will use the user and group information that it last successfully retrieved from the User Name Server until communications are reestablished. Registration is an asynchronous operation but severe delays and repetitions of this message require investigation.
- Response
- Check that the User Name Server has been started. Check preceding system log entries for related errors.
- BIP8303
- The Broker's user/group cache is empty.
- Severity
- 10 : Warning
- Explanation
- The Broker maintains a persistent copy of user and group information which it initially receives from the User Name Server. The cache will be empty if the Broker has never successfully registered with the User Name Server.
- Response
- Check preceding system log entries for related errors. Check that the User Name Server has been started. Contact your IBM support center if the problem persists.
- BIP8304
- Starting deferred JMS/IP Input Node with authentication enabled.
- Severity
- 0 : Information
- Explanation
- The broker has received authentication information from the User Name Server and JMS/IP Input nodes with authentication enabled will now be started.
- Response
- No user action required.
- BIP8305
- Cannot start a JMS/IP Input Node with authentication support.
- Severity
- 10 : Warning
- Explanation
- Authentication has been enabled for a JMS/IP Input Node but the broker has received either no authentication information or invalid authentication information from the User Name Server.
- Response
- Check preceding system log entries for related errors. Check the authentication parameters specified during User Name Server configuration. Contact your IBM support center if the problem persists.
- BIP8306
- Starting deferred JMS/IP Input Node with authorization enabled.
- Severity
- 0 : Information
- Explanation
- The broker has received authorization information from the User Name Server and JMS/IP Input nodes will now be started.
- Response
- No user action required.
- BIP8307
- The start of a JMS/IP Input Node has been deferred.
- Severity
- 10 : Warning
- Explanation
- Authorization has been enabled but the broker has yet to receive authorization information from the User Name Server. The JMS/IP node will be started when this information has been received.
- Response
- Check preceding system log entries for related errors. Check that the User Name Server has been started. Contact your IBM support center if the problem persists.
- BIP8308
- The start of a JMS/IP Input Node has been deferred.
- Severity
- 10 : Warning
- Explanation
- Authentication has been enabled for a JMS/IP Input Node but the broker has yet to receive authentication information from the User Name Server. The node will be started when this information has been received.
- Response
- Check preceding system log entries for related errors. Check that the User Name Server has been started. Contact your IBM support center if the problem persists.
- BIP8309
- The broker has successfully processed the initial message from the User Name Server.
- Severity
- 0 : Information
- Explanation
- The broker has received the latest authentication and/or authorization information from the User Name Server. If this is the first time that the broker and User Name Server have ever communicated, then the broker will now be ready to support pubsub security services.
- Response
- No user action required.
- BIP8310
- User Name Server has completed processing a command request.
- Severity
- 0 : Information
- Explanation
- This message is issued when the User Name Server has finished processing a command request from a broker or Configuration Manager.
- Response
- No user action required.
- BIP8311
- User Name Server received command message <insert_0>.
- Severity
- 0 : Information
- Explanation
- This message is issued when the User Name Server receives a command request from a broker or Configuration Manager.
- Response
- No user action required.
- BIP8380
- Successfully initialized the plug-in user/group registry.
- Severity
- 0 : Information
- Explanation
- A component of WebSphere Message Brokers has successfully initialized the plug-in user/group registry.
- Response
- No user action required.
- BIP8381
- Error in initializing the plug-in user/group registry.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize the plug-in service for use as a supplier of user and group information.
- Response
- Check the plug-in service's diagnostic report for initialization errors.
- BIP8382
- Error in call <insert_0> to the plug-in user/group registry with return code <insert_1>.
- Severity
- 20 : Error
- Explanation
- A component of WebSphere Message Brokers is attempting to call the plug-in user/group registry. The plug-in returned an error code.
- Response
- Check the plug-in service's diagnostic report for the reported error.
- BIP8390
- Successfully initialized support for authentication.
- Severity
- 0 : Information
- Explanation
- A component of WebSphere Message Brokers has successfully loaded and initialized the authentication support module.
- Response
- No user action required.
- BIP8391
- Error in initializing support for authentication.
- Severity
- 10 : Warning
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize support for authentication
- Response
- Check preceding system log entries for related errors. Check the authentication service's diagnostic report for initialization errors.
- BIP8392
- Authentication Protocol Type not recognised, <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The User Name Server component of WebSphere Message Brokers is attempting to initialize support for authentication but does not recognise the specified authentication type. Authentication support will be disabled.
- Response
- Check that a valid authentication protocol type string was specified in the configuration command that created the User Name Server. Processing will continue but authentication support will be disabled.
- BIP8393
- Authentication support is disabled.
- Severity
- 10 : Warning
- Explanation
- A component of WebSphere Message Brokers is attempting to initialize support for authentication but authentication services have been disabled.
- Response
- Check preceding system log entries for related errors. Check that a valid authentication protocol type string was specified in the configuration command that created the User Name Server. Check the authentication service's diagnostic report for initialization errors.
- BIP8394
- Error in initialising Data Source for Authentication Service.
- Severity
- 10 : Warning
- Explanation
- The User Name Server component of WebSphere Message Brokers is attempting to initialize support for authentication but has encountered a problem in initialising its Data Source. Authentication support will be disabled.
- Response
- Check that a valid file was specified as Data Source in the configuration command that created the User Name Server. The User Name Server may not have successfully read the file. In order to check for errors, you should enable service trace and restart the User Name Server. When service trace is enabled the User Name Server produces a log file named auth<pid>.out (where pid is a process id) in the product log directory that records any errors encountered in reading the Data Source. Processing will continue but authentication support will be disabled.
- BIP8401
- Message associated with internal message number <insert_0> was not found: data supplied <insert_1>
- Severity
- 20 : Error
- Explanation
- An internal message number was used for which no associated message text could be found.
- Response
- This is an internal error. Contact your IBM support center.
- BIP8403
- MAX_CLIENT_READ_THREADS was < 0, it must be >= 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Respecify the MAX_CLIENT_READ_THREADS value to be greater or equal to 0 and restart the broker. Note that MAX_CLIENT_READ_THREADS is 0 by default and should not be specified as non-zero in normal operation. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxClientReadThreads -v value
- BIP8404
- PING_TIMEOUT_MULTIPLE was <= 0, it must be > 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Respecify the PING_TIMEOUT_MULTIPLE value to be greater than 0 and restart the broker. Note that PING_TIMEOUT_MULTIPLE=3 is the default and usually does not require overriding. To change the value, use the following mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n pingTimeoutMultiple -v value
- BIP8405
- PING_MIN was <= 0, it must be > 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Respecify the PING_MIN value to be greater than 0 and restart the broker. Note that PING_MIN is 100 by default and usually does not require overriding. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n pingMin -v value
- BIP8406
- EXPECTED_MESSAGE_SIZE was <= 0, it must be > 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Respecify the EXPECTED_MESSAGE_SIZE value to be greater than 0 and restart the broker. Note that EXPECTED_MESSAGE_SIZE=200 by default. While setting this value to something more like the true expected size can improve performance slightly, this parameter does not affect correctness, and the default is normally satisfactory. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n expectedMessageSize -v value
- BIP8407
- MAX_MESSAGE_SIZE was <= 0, it must be > 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value. The MAX_MESSAGE_SIZE value is used for the Real Time transport to declare the maximum size for messages to be delivered to client applications
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. This can be set by using : mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxMessageSize -v value A broker restart is required to activate the change.
- BIP8408
- MESSAGE_SIZE_EXTRA_ALLOWANCE was < 0, it must be >= 0.
- Severity
- 20 : Error
- Explanation
- A configuration request was received which specified an invalid value. The MESSAGE_SIZE_EXTRA_ALLOWANCE value is used for the Real Time transport to declare the extra allowance size for messages to be delivered to client applications
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. This can be set by using : mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n messageSizeExtraAllowance -v value A broker restart is required to activate the changes.
- BIP8410
- An exception occured while attempting to specify a "strong" crypto library for use by MinCrypto. MinCrypto will default to the standard exportable library instead. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8411
- An attempt to specify the default "exportable" crypto library in MinCrypto failed with an exception. The exception is <insert_0>.
- Severity
- 20 : Error
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8412
- A failure has occured when attempting to log an event. The type of event is <insert_0>, the severity of the event is <insert_1>, and the exception is <insert_2>.
- Severity
- 10 : Warning
- Explanation
- An event recording error has occurred. The error is described in the message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8413
- The broker received an invalid or unexpected control message. The type of the message is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8414
- Authentication on a broker-broker connection failed. This is non-fatal but must be repaired in order to allow multibroker routing. The name of the attempted broker-broker connection is <insert_0>, and the InauthenticBrokerException that was caught is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- Correct the error and retry the operation.
- BIP8415
- Authentication on a broker-broker connection timed out after too many unsuccessful attempts. This is non-fatal but must be repaired in order to allow multibroker routing. The name of the attempted broker-broker connection is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- Correct the error and retry the operation.
- BIP8416
- The broker caught an exception while attempting to update its broker-broker connection status using a local SemaphoreClient. The attempted update is <insert_0> and the exception is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8417
- A VMX message received on a broker-broker connection had a bad MDT. The associated connection will be closed. The MsgDistException which triggered the event is <insert_0>, and the name of the broker-broker connection is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8418
- An error was encountered while parsing the BROKERS_THRU_SOCKS parameter. This is non-fatal but will disable any socksified broker-broker connections. The caught exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8419
- An error occurred while attempting to instantiate the non-blocking IO library. The regular blocking IO library will be used instead. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8420
- A request was made to add an initial state processor to a topic which was alread assigned a processor. The requested processor will be ignored. The full name of the requested topic is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8421
- A SecurityGeneralException was encountered while processing a message received on a connection. The caught exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8422
- A client attempted to publish on a topic for which it was not authorized. The message was dropped. The client connection is <insert_0>, and the topic is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- Correct the error and retry the operation.
- BIP8423
- A client connection failed on authentication and will be disconnected. The hostname and port of the failed connection is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- Correct the error and retry the operation.
- BIP8424
- A client connection was closed because it failed to finish authentication within a preset time limit. The hostname and port of the failed connection is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A security error has occurred. The error is described in the message.
- Response
- Correct the error and retry the operation by attempting to reconnect the client
- BIP8425
- The broker configuration of MAX_BROKER_QUEUE_SIZE is between 0 and 500 bytes. This is rather small and may cause many broker-broker messages to be discarded. The value of MAX_BROKER_QUEUE_SIZE is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A configuration request was received which specified an unexpected value.
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. The MAX_BROKER_QUEUE_SIZE is used for queueing Real Time transport broker to broker messages. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxBrokerQueueSize -v value
- BIP8426
- The broker configuration of MAX_CLIENT_QUEUE_SIZE is between 0 and 500 bytes. This is rather small and may cause many client-broker messages to be discarded. The value of MAX_CLIENT_QUEUE_SIZE is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. This can be done using mqsichangeproperties: mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxClientQueueSize -v value A broker restart is required to activate the change
- BIP8427
- ENABLE_SOCKS is true but BROKERS_THRU_SOCKS is zero-length. Processing will continue but no broker-broker connections will be socksified. This may not be the intended behavior.
- Severity
- 10 : Warning
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n enableThruSocks -v value
- BIP8428
- ENABLE_SOCKS is true but SOCKS_HOST is zero-length. Processing will continue but no broker-broker connections will be socksified. This may not be the intended behavior.
- Severity
- 10 : Warning
- Explanation
- A configuration request was received which specified an invalid value.
- Response
- Modify the configuration request to specify a valid value for the attribute, and retry the request. mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n socksHost -v value
- BIP8429
- An exception was caught in the run loop of the StatsEPImpl thread. Processing continues. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8430
- An exception occurred while closing the segment reader portion of a non-blocking threaded socket segment. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8431
- An exception occurred while closing the segment writer portion of a non-blocking threaded socket segment. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8432
- An exception occurred while deregistering the client associated with a non-blocking threaded socket segment. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8433
- An exception occurred while closing the socket associated with a non-blocking threaded socket segment. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8437
- A broker connection on socket <insert_0> established with name <insert_1> received a topology message from broker <insert_2>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8438
- An attempt to establish a broker connection on socket <insert_0> failed with exception <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error may be caused by an application attempting to use the port that has been configured for broker connections.
- Response
- Investigate whether an application is incorrectly using the socket that has been configured for broker connections.
- BIP8439
- An alpha services reload was requested but the wrong directory is in use.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8440
- An error occurred during locking. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8441
- An exception occurred during reset after a lock error. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8442
- A service failure was reported to BrokerControl. The service reference is <insert_0>, the reason for the failure is <insert_1>, and the exception is <insert_2>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8443
- The LogRecorder generated an exception while recording a log entry. The log mask is <insert_0> and the exception is <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8444
- An exception was caught while changing the state of an internal ControlHandler. Processing continues. The exception is <insert_0>.
- Severity
- 10 : Warning
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8445
- An exception was caught at the end of the scheduling loop of StatsEPImpl. As a result, the statistics entry point is now disabled. Processing continues, but statistics are no longer be available from this broker. The exception is <insert_0>.
- Severity
- 20 : Error
- Explanation
- An unexpected error occurred. The error is described in the error message.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8446
- Message queue exceeded limit. Discarded <insert_0> bytes in <insert_1> messages.
- Severity
- 10 : Warning
- Explanation
- The message queue exceeded its configured limit for the Real Time transport.
- Response
- Consider increasing the value of MAX_CLIENT_QUEUE_SIZE and MAX_BROKER_QUEUE_SIZE. These can be set using mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxClientQueueSize -v value or mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxBrokerQueueSize -v value MAX_CLIENT_QUEUE_SIZE is used for Broker to Client messages. MAX_BROKER_QUEUE_SIZE is used for Broker to Broker messages.
- BIP8447
- Client <<insert_0>> tried to publish a <insert_1> byte message, exceeding the limit <insert_2>.
- Severity
- 10 : Warning
- Explanation
- A client connection was closed (culled) because it tried to publish a message that exceeded the configured limit, MAX_MESSAGE_SIZE. A string giving the hostname and port of the failed connection is included as the first parameter of this event. The size of the message is the second parameter. And the configured maximum is the third parameter.
- Response
- If the failing client was publishing a message within the expected size range, consider increasing the value of the MAX_MESSAGE_SIZE This can be set using : mqsichangeproperties BrokerName -e ExecutionGroupLabel -o DynamicSubscriptionEngine -n maxMessageSize -v value A broker restart is required to activate the change parameter.
- BIP8448
- A broker-broker connection with <insert_0> has been disconnected due to failure to respond to a ping
- Severity
- 10 : Warning
- Explanation
- A connection did not respond to pings to it is about to be reaped. A string representing the host and port of the remote broker is the sole parameter of this event.
- Response
- This message is for information only, to indicate disconnection of a broker due to its inactivity. Reconnection will be attempted automatically.
- BIP8449
- A broker-broker connection with <insert_0> has been disconnected due to Exception <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An exception occurred while processing messages on a broker-broker connection. The exception may have occurred either due to a message processing error or a dropped connection.
- Response
- This message is for information only, to indicate disconnection of a broker due to an exception. Reconnection will be attempted automatically.
- BIP8450
- Server-to-server authentication failed because id of other broker <insert_0> was not in the server principals directory.
- Severity
- 10 : Warning
- Explanation
- The would-be partner broker authenticated with an id that was not known to this broker.
- Response
- Ensure that the id <insert_0> is known to the broker
- BIP8451
- Client-to-server authentication failed because id of the client <insert_0> was not in the client principals directory.
- Severity
- 20 : Error
- Explanation
- The would-be client authenticated with an id that was not known to this broker.
- Response
- Ensure that the client <insert_0> is known to the broker
- BIP8452
- <insert_0> is not allowed in BROKER_AUTH_PROTOCOLS.
- Severity
- 20 : Error
- Explanation
- We don't allow the use of protocol <insert_0> for broker to broker authentication.
- Response
- This is an internal error and you should contact your IBM support center.
- BIP8453
- Broker-Broker connection on socket <insert_0> with broker <insert_1> has been established
- Severity
- 0 : Information
- Explanation
- Broker-Broker connection on socket <insert_0> with broker <insert_1> has been established and authenticated with id=<insert_1> and protocol=<insert_2>.
- Response
- This message is for information only
- BIP8454
- The authentication timeout thread for an instance of Security caught an exception
- Severity
- 20 : Error
- Explanation
- The authentication timeout thread for an instance of Security caught the exception <insert_0>
- Response
- This is a warning message, client authentication may be affected.
- BIP8460
- Could not create internal non-blocking socket on the loopback address 127.0.0.1. Using the address of the adapter associated with the host name of the machine.
- Severity
- 0 : Information
- Explanation
- An exception occurred while creating an internal communication socket bound to the loopback address 127.0.0.1. The operaton will be retried using the address of the adapter bound to the hostname of the computer.
- Response
- This message is for information only.
- BIP8461
- Broker <insert_0> has an incorrectly configured Broker Topology: <insert_1> with <insert_2> neighbours: <insert_3>.
- Severity
- 10 : Warning
- Explanation
- A Broker Topology has been incorrectly configured.
- Response
- Correct the topology configuration using either the Message Brokers Toolkit or the Config Manager Proxy.
- BIP8462
- Disthub caught a fatal exception [<insert_0>].
- Severity
- 30 : Severe error
- Explanation
- A fatal exception occurred within the Broker <insert_0>. The behavior of the Broker is now undefined and further use will produce unpredictable results
- Response
- Restart the broker, if the problem persists you should contact your IBM support center
- BIP8463
- Broker <insert_0> detected a cycle in its own topology configuration.
- Severity
- 20 : Error
- Explanation
- The broker found a cycle in the topology. This will result in publications looping around brokers in the topology.
- Response
- Correct and redeploy the topology in the Message Brokers Toolkit, or programmatically using the Config Manager Proxy.
- BIP8464
- Error while trying to open Interbroker Port <insert_0>.
- Severity
- 20 : Error
- Explanation
- While trying to open port <insert_0> for Real-time Communications from a Neighbor, a java.net.BindException occurred.
- Response
- This normally occurs because another application is holding the socket open. If required, change the InterbrokerPort Broker property in the Message Brokers Toolkit to a port that isn't in use. This can also be done programmatically using the Config Manager Proxy.
- BIP8465
- A connection from client at <insert_0> has been disconnected due to inactivity.
- Severity
- 10 : Warning
- Explanation
- A connection did not respond to pings so it is about to be reaped. A string representing the host and port of the reaped connection is the sole parameter of this event.
- Response
- This message is for information only, to indicate disconnection of a client due to its inactivity.
- BIP8601
- This program requires VGA or better resolution.
- Severity
- 20 : Error
- Explanation
- The installation of this product requires that you use a display with at least VGA resolution.
- Response
- Check your display/display settings.
- BIP8602
- Setup requires Windows NT Server 4.0/SP5 or later.
- Severity
- 20 : Error
- Explanation
- The installation of this product requires that your system level is Windows NT Server 4.0/SP5 or later.
- Response
- Upgrade your NT system.
- BIP8603
- WebSphere Message Brokers install or uninstall is already running.
- Severity
- 20 : Error
- Explanation
- The install has detected a conflicting install/uninstall process running on your machine.
- Response
- Exit this instance of the install/uninstall and terminate the conflicting process.
- BIP8604
- The system has detected that you do not have administrator equivalent rights. You must log on as an administrator and run setup again.
- Severity
- 20 : Error
- Explanation
- To install WebSphere Message Brokers you need administrator authority.
- Response
- Terminate the installation, log off, log on as an administrator, and retry.
- BIP8606
- Before setup can display help, this computer's help system needs upgrading to HTML Help 1.3. Would you like to upgrade now? You might need to restart the computer.
- Severity
- 10 : Warning
- Explanation
- Help for install and uninstall requires that HTML Help 1.3 to be installed.
- Response
- If you want to see the install/uninstall help then you can allow WebSphere Message Brokers to upgrade your system. Note that in order to activate this help you might need to terminate this install, reboot and then start install again.
- BIP8610
- Help cannot be displayed as Internet Explorer level is less than 4.01.
- Severity
- 10 : Warning
- Explanation
- The install or uninstall cannot display help unless IE 4.01 or later is installed on your machine.
- Response
- If you wish to see the help for install/uninstall then you must exit this instance of the installation or uninstallation and upgrade your system.
- BIP8611
- Uninstall cannot continue, administrator authority is required.
- Severity
- 20 : Error
- Explanation
- You require administrator authority to uninstall WebSphere Message Brokers.
- Response
- Access the machine with the same user authority that the product was installed with.
- BIP8612
- Select at least one component to proceed.
- Severity
- 0 : Information
- Explanation
- You need to select at least one component for installation/uninstallation.
- Response
- Select one or more components to proceed.
- BIP8613
- WebSphere Message Brokers setup or uninstallation is already running.
- Severity
- 10 : Warning
- Explanation
- WebSphere Message Brokers uninstall has detected that there is an instance of install or uninstall already running.
- Response
- Terminate this uninstall instance and restart (if necessary) when the already running install or uninstall has finished.
- BIP8614
- One or more problems occurred during uninstallation. Review <insert_0> for details.
- Severity
- 10 : Warning
- Explanation
- One (or more) problems were encountered during uninstallation of the product. You may have seen a previous message(s) indicating the nature of the problem. The install/uninstall log <insert_0> may contain additional information on the nature of the problem.
- Response
- Review the install/uninstall log <insert_0> to aid resolution of the problem. If the problem persists, contact your IBM support center.
- BIP8615
- Problem encountered stopping broker <insert_0>. Return from v was <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to stop a broker named <insert_0> using v but encountered an error. The return code from this command was <insert_1>.
- Response
- The command can be retried by choosing Retry, this is the suggested action. If you choose Abort or Cancel then uninstall will end. Before relaunching the uninstall you should try to manually stop the broker identified. If you choose Ignore (if available) then uninstall will continue, but it is possible that the problem with v may cause additional errors to appear when the uninstall attempts to delete the broker. Additional help is available using the Help button.
- BIP8616
- Unable to delete broker <insert_0>. Return Code from v was <insert_1>. Abort, Retry, or Ignore?
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to delete a broker (<insert_0>) but encountered an error. The return code from v was <insert_1>.
- Response
- The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will terminate. Before relaunching the uninstall you should try to manually delete the broker identified. If you choose Ignore (if available) then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button.
- BIP8617
- Unable to stop Configuration Manager. Return Code from v was <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to stop the Configuration Manager using v but encountered a problem. The return code from v was <insert_0>.
- Response
- The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will end. Before relaunching the uninstall you should try to manually stop the Configuration Manager. If you choose Ignore (if available) then uninstall will continue, but it is possible that the problem with v may cause additional errors to appear when the uninstall attempts to delete the Configuration Manager. Additional help is available using the Help button.
- BIP8618
- Unable to delete configuration manager. Return Code from v was <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to delete the Configuration Manager but encountered an error. The return code from v was <insert_0>.
- Response
- The command can be retried by choosing Retry. If you choose Abort then uninstall will terminate. Before relaunching the uninstall you should try to manually delete the Configuration Manager. If you choose Ignore (if available) then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button.
- BIP8619
- Unable to stop User Name Server. Return Code from v was <insert_0>. See message
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to stop the User Name Server using v but encountered a problem. The return code from v was <insert_0>.
- Response
- The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will be terminated. Before relaunching the uninstall you should try to manually stop the User Name Server. If you choose Ignore (if available) then uninstall will continue, but it is possible that the problem with v may cause additional errors to appear when the uninstall attempts to delete the User Name Server. Additional help is available using the Help button.
- BIP8620
- Unable to delete User Name Server. Return Code from v was <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The uninstall attempted to delete the User Name Server but encountered an error. The return code from v was <insert_0>.
- Response
- The command can be retried by choosing Retry. If you choose Abort or Cancel then uninstall will terminate. Before relaunching the uninstall you should try to manually delete the User name Server. If you choose Ignore (if available) then uninstall will continue, but it is possible that additional errors will be encountered later. Additional help is available using the Help button.
- BIP8621
- Install of <insert_0> has started
- Severity
- 0 : Information
- Explanation
- The install of product <insert_0> has started. The end of the install will be signaled by BIP8622.
- Response
- No user action required
- BIP8622
- Install of <insert_0> has finished successfully
- Severity
- 0 : Information
- Explanation
- Install of product <insert_0> has finished without any errors.
- Response
- No user action required
- BIP8623
- Uninstall of <insert_0> has started
- Severity
- 0 : Information
- Explanation
- The uninstall of product <insert_0> has started. The end of the uninstall will be signaled by BIP8624.
- Response
- No user action required
- BIP8624
- Uninstall of <insert_0> has finished successfully
- Severity
- 0 : Information
- Explanation
- Uninstall of product <insert_0> has finished without any errors.
- Response
- No user action required
- BIP8640
- symlink returned EACCES when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Write access to the directory containing <insert_1> is denied, or one of the directories in the path prefix of <insert_1> did not allow search permission.
- BIP8641
- symlink returned EEXIST when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- <insert_1> already exists.
- BIP8642
- symlink returned EFAULT when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- This is an internal error, please contact your IBM support center.
- BIP8643
- symlink returned EIO when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- And I/O error occurred, please check the state of the filesystems and retry the command. If the problem persists please contact your IBM support center.
- BIP8644
- symlink returned ELOOP when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Too many symbolic links were encountered in resolving <insert_1>.
- BIP8645
- symlink returned ENAMETOOLONG when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- <insert_0> or <insert_1> was too long for the filesystem to handle.
- BIP8646
- symlink returned ENOENT when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A directory component in <insert_1> does not exist or is a dangling symbolic link, or <insert_0> is the empty string.
- BIP8647
- symlink returned ENOMEM when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Insufficient kernel memory was available.
- BIP8648
- File rename operation returned ENOSPC when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The device containing <insert_1> path prefix has no room for the <insert_1> directory entry.
- BIP8649
- symlink returned ENOTDIR when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- A component used as a directory in <insert_1> is not, in fact, a directory.
- BIP8650
- symlink returned EPERM when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The filesystem containing <insert_1> does not support the creation of symbolic links.
- BIP8651
- symlink returned EROFS when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- <insert_1> is on a read-only filesystem.
- BIP8652
- symlink operation failed when attempting to create a symbolic link with target <insert_0> and link name <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The operation failed for an unknown reason, please attempt to create the symbolic manually and resolve the errors before re-running the command.
- BIP8653
- Creating a symbolic link with target <insert_0> and link name <insert_1>
- Severity
- 0 : Information
- BIP8654
- Moving filesystem artefacts from <insert_0> to <insert_1>
- Severity
- 0 : Information
- BIP8655
- Removing <insert_0>.
- Severity
- 0 : Information
- BIP8656
- Cannot remove non-empty directory <insert_0> due to unhandled file <insert_1>
- Severity
- 10 : Warning
- BIP8657
- Creating directory <insert_0>
- Severity
- 0 : Information
- BIP8658
- Unable to determine necessary information for migrating broker <insert_0>, does it really exist?
- Severity
- 20 : Error
- BIP8659
- Could not determine the Data Source Name for broker <insert_0>, could be wrong version?
- Severity
- 20 : Error
- BIP8660
- Could not determine the Queue Manager for broker <insert_0>, could be wrong version?
- Severity
- 20 : Error
- BIP8661
- Detected source version <insert_0>.<insert_1>.<insert_2>.<insert_3>
- Severity
- 0 : Information
- BIP8662
- Detected target version <insert_0>.<insert_1>.<insert_2>.<insert_3>
- Severity
- 0 : Information
- BIP8663
- Creating temporary new tables
- Severity
- 0 : Information
- BIP8664
- Migrating from existing tables to temporary new tables
- Severity
- 0 : Information
- BIP8665
- Dropping existing tables
- Severity
- 0 : Information
- BIP8666
- Creating new tables
- Severity
- 0 : Information
- BIP8667
- Copying all rows from temporary new tables to new tables
- Severity
- 0 : Information
- BIP8668
- Dropping temporary new tables
- Severity
- 0 : Information
- BIP8669
- Database migration successful
- Severity
- 0 : Information
- BIP8670
- Database migration started
- Severity
- 0 : Information
- BIP8671
- Database migration failed
- Severity
- 20 : Error
- BIP8672
- Rolling back database changes
- Severity
- 10 : Warning
- BIP8673
- Migration of broker <insert_0> from version <insert_1>.<insert_2>.<insert_3>.<insert_4> to version <insert_5>.<insert_6>.<insert_7>.<insert_8> failed, see previous messages for reasons.
- Severity
- 20 : Error
- BIP8674
- Configuration Manager <insert_0> (Version <insert_1>.<insert_2>) specified for migration.
- Severity
- 0 : Information
- BIP8675
- UserNameServer <insert_0> (Version <insert_1>.<insert_2>) specified for migration.
- Severity
- 0 : Information
- BIP8676
- Component <insert_0> is of a type which cannot be migrated. Only Brokers, Configuration Managers and UserNameServers may be migrated.
- Severity
- 30 : Severe error
- BIP8677
- Component <insert_0> was specified with a source version of <insert_1>.<insert_2>.<insert_3>.<insert_4>, whilst version <insert_5>.<insert_6>.<insert_7>.<insert_8> was detected.
- Severity
- 10 : Warning
- BIP8678
- Component <insert_0> is sharing a database schema with component <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Migrate one component first and then migrate just the registry (using the '-1' flag) and MQ (using the '-2' flag) components of the others.
- BIP8679
- Found a 64 bit execution group: <insert_0>. Brokers with 64 bit execution groups cannot be migrated to versions prior to 6.
- Severity
- 10 : Warning
- BIP8680
- Pre-migration check succeeded.
- Severity
- 0 : Information
- BIP8681
- Pre-migration check failed.
- Severity
- 10 : Warning
- BIP8682
- Unable to open root registry key <insert_0> for query.
- Severity
- 10 : Warning
- BIP8683
- Unable to query values under key <insert_0>.
- Severity
- 10 : Warning
- BIP8684
- Rolling back WebSphere MQ changes
- Severity
- 10 : Warning
- BIP8685
- Rolling back Registry changes
- Severity
- 10 : Warning
- BIP8686
- Finished Rolling back WebSphere MQ changes
- Severity
- 10 : Warning
- BIP8687
- Finished Rolling back Registry changes
- Severity
- 10 : Warning
- BIP8688
- Following migration, Message Set <insert_0>(<insert_1>) should be redeployed to Execution Group <insert_2>(<insert_3>).
- Severity
- 10 : Warning
- BIP8689
- The source and target version are compatible, no migration is necessary.
- Severity
- 0 : Information
- BIP8700
- Post-migration check started.
- Severity
- 0 : Information
- Explanation
- The migration utility is checking the component configuration to ensure that migration was successful.
- Response
- None.
- BIP8701
- Post-migration check succeded
- Severity
- 0 : Information
- Explanation
- The migration utility did not find any configuration errors for the component.
- Response
- None.
- BIP8702
- Post-migration check failed; see previous messages for possible causes.
- Severity
- 10 : Warning
- Explanation
- The migration utility found configuration errors for the component. This means that the component configuration is not correct in some way; previous messages should provide the exact errors.
- Response
- Examine previous messages, and errors reported during migration steps, to determine the cause of the failure. The migration may need to be reversed, or completed manually.
- BIP8703
- Column <insert_0> is missing from database table <insert_1>
- Severity
- 30 : Severe error
- Explanation
- Table <insert_1> must have the correct set of columns for this component to function correctly, and column <insert_0> is missing. This could be because a migration step has not been performed, or because the table itself has become damaged.
- Response
- If this broker is being started after a migration, ensure all migration steps have completed successfully. If this broker is newly created, and the database tables were created manually by a database administrator, ensure all columns specified are correct.
- BIP8704
- Column <insert_0> should not be present in database table <insert_1>
- Severity
- 30 : Severe error
- Explanation
- Table <insert_1> must have the correct set of columns for this component to function correctly, and an extra column <insert_0> is present. This could be because a migration step has not been performed, or because the table itself has become damaged.
- Response
- If this broker is being started after a migration, ensure all migration steps have completed successfully. If this broker is newly created, and the database tables were created manually by a database administrator, ensure all columns specified are correct.
- BIP8705
- WebSphere MQ queue <insert_0> is missing.
- Severity
- 30 : Severe error
- Explanation
- The WebSphere MQ queue manager must have the correct set of queues for this component to function correctly, and queue <insert_0> is missing. This could be because a migration step has not been performed, or because the queue manager itself has become damaged.
- Response
- If this broker is being started after a migration, ensure all migration steps have completed successfully. If this broker is newly created, and the WebSphere MQ queues were created manually by a WebSphere MQ administrator, ensure all queues specified are correct.
- BIP8706
- WebSphere MQ queue <insert_0> exists, but is not accessible; reason code <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ queue manager must have the correct set of queues for this component to function correctly, and queue <insert_0> is not accessible. This could be because the permissions have been changed, or because the queue manager itself has become damaged.
- Response
- If this broker is being started after a migration, ensure all migration steps have completed successfully. If this broker is newly created, and the WebSphere MQ queues were created manually by a WebSphere MQ administrator, ensure all queues specified are correct, and the correct permissions. Examine the reason code, and correct any faults that might lead to this code.
- BIP8750
- Starting registry migration for component <insert_0>.
- Severity
- 0 : Information
- Explanation
- Registry data is being migrated for component <insert_0>.
- Response
- None.
- BIP8751
- Created top-level 'CurrentVersion' key.
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the 'CurrentVersion' key has been created.
- Response
- None.
- BIP8752
- Created <insert_0> subkey
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the <insert_0> key has been created.
- Response
- None.
- BIP8753
- Created value named <insert_0>; value data is <insert_1>
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the <insert_0> value has been created and set to <insert_1>
- Response
- None.
- BIP8754
- Moving registry data into 'CurrentVersion'
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the legacy data is being moved into the new location.
- Response
- None.
- BIP8755
- Copied value <insert_0> into the new location
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the legacy data element <insert_0> is being copied into the new location.
- Response
- None.
- BIP8756
- Finished moving registry data into 'CurrentVersion'
- Severity
- 0 : Information
- Explanation
- The registry portion of the migration process has completed.
- Response
- None.
- BIP8757
- Error moving registry value <insert_0>: <insert_1>
- Severity
- 20 : Error
- Explanation
- An error has occured when moving registry value <insert_0>. The registry migration will now be reversed.
- Response
- None.
- BIP8758
- Reversing registry migration for component <insert_0>.
- Severity
- 10 : Warning
- Explanation
- Registry data is being unmigrated for component <insert_0>.
- Response
- None.
- BIP8759
- Found registry subkey <insert_0> that is not valid in either source or target; left unchanged.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry subkey <insert_0> that is not valid in either source or target version; this value will be left unchanged.
- Response
- None.
- BIP8760
- Found registry value <insert_0> that is not valid in either source or target; left unchanged.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry value <insert_0> that is not valid in either source or target version; this value will be left unchanged.
- Response
- None.
- BIP8761
- Found registry value <insert_0> for DSN <insert_1> that is not valid in either source or target; left unchanged.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry value <insert_0> in DSN-specific subkey <insert_1> that is not valid in either source or target version; this value will be left unchanged.
- Response
- None.
- BIP8762
- Copied registry value from <insert_0> to HTTP value <insert_1>; set to <insert_2>
- Severity
- 0 : Information
- Explanation
- During migration, the command found a registry value <insert_0> whose name must be changed for the new version into <insert_1>. The value data is still <insert_2>.
- Response
- None.
- BIP8763
- Deleted value <insert_0> from the old location
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the legacy data element <insert_0> is being copied into the new location.
- Response
- None.
- BIP8764
- Found registry subkey <insert_0> that is not valid in the source version; left unchanged.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry subkey <insert_0> that is not valid in the source version; this value will be left unchanged.
- Response
- None.
- BIP8765
- Found registry value <insert_0> that is not valid in the source version; left unchanged.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry value <insert_0> that is not valid in the source version; this value will be left unchanged.
- Response
- None.
- BIP8766
- Copied value <insert_0> for DSN <insert_1> into the new location
- Severity
- 0 : Information
- Explanation
- As part of the registry migration, the legacy data element <insert_0> is being copied into the new location for DSN <insert_1>.
- Response
- None.
- BIP8767
- Found registry value <insert_0> that is not valid in the target version; not copied.
- Severity
- 10 : Warning
- Explanation
- During migration, the command found a registry value <insert_0> that is not valid in the target version; this value will not be copied, though no functionality will be lost.
- Response
- None.
- BIP8768
- Finished registry migration for component <insert_0>.
- Severity
- 0 : Information
- Explanation
- Registry data has been sucessfully migrated for component <insert_0>.
- Response
- None.
- BIP8785
- Starting WebSphere MQ queue migration for component <insert_0>.
- Severity
- 0 : Information
- Explanation
- Queue data is being migrated for component <insert_0>.
- Response
- None.
- BIP8786
- Created WebSphere MQ queue <insert_0>
- Severity
- 0 : Information
- Explanation
- As part of the WebSphere MQ queue migration, the queue <insert_0> has been created.
- Response
- None.
- BIP8787
- Cleared WebSphere MQ queue <insert_0>
- Severity
- 0 : Information
- Explanation
- As part of the WebSphere MQ queue migration, the queue <insert_0> has been cleared of messages.
- Response
- None.
- BIP8788
- Deleted WebSphere MQ queue <insert_0>
- Severity
- 0 : Information
- Explanation
- As part of the WebSphere MQ queue migration, the queue <insert_0> has been deleted.
- Response
- None.
- BIP8789
- Finished WebSphere MQ queue migration for component <insert_0>.
- Severity
- 0 : Information
- Explanation
- Queue data has been sucessfully migrated for component <insert_0>.
- Response
- None.
- BIP8790
- Duplicate rows were detected in table <insert_0>. This will prevent migration from succeeding.
- Severity
- 30 : Severe error
- Explanation
- Duplicate rows were detected in table <insert_0>. The destination product requires unique indexes to be added to the table for correct operation, and duplicate rows will prevent the index add from succeding.
- Response
- Contact IBM service for more assistance; do not attempt to correct the problem.
- BIP8791
- Duplicate rows check started.
- Severity
- 0 : Information
- Explanation
- The migration utility is checking the broker database for entries that could cause migration to fail.
- Response
- None.
- BIP8792
- Duplicate rows check passed.
- Severity
- 0 : Information
- Explanation
- No duplicate rows were detected in the broker database.
- Response
- None.
- BIP8793
- Duplicate rows check failed.
- Severity
- 30 : Severe error
- Explanation
- Duplicate rows were detected in the broker database. See previous errors for more information.
- Response
- Contact IBM service for more assistance; do not attempt to correct the problem.
- BIP8794
- Table <insert_0> has no duplicated rows.
- Severity
- 0 : Information
- Explanation
- The destination product requires unique indexes to be added to the table for correct operation, and duplicate rows will prevent the index add from succeding.
- Response
- None.
- BIP8795
- A previously migrated Configuration Manager repository found at <insert_0>
- Severity
- 0 : Information
- Explanation
- A previously migrated repository will be used by the Configuration Manager being migrated. No previous configuration data from the DB2 database will be migrated to the Configuration Manager repository when starting the new Configuration Manager. If you want to fully migrate all existing configuration data from the DB2 database then you must delete the directory <insert_0> before starting the new Configuration Manager.
- Response
- None.
- BIP8796
- All configuration data from the DB2 database will be migrated to the new Configuration Manager repository when the Configuration Manager is first started.
- Severity
- 0 : Information
- Explanation
- None.
- BIP8797
- Topic syntax check succeded
- Severity
- 0 : Information
- Explanation
- No topic syntax errors where found in the broker database.
- Response
- None.
- BIP8798
- Topic syntax check failed; see previous messages for possible causes.
- Severity
- 10 : Warning
- Explanation
- An invalid topic has been found in the Broker Database.
- Response
- Examine previous messages, and errors reported during migration steps, to determine the cause of the failure. The migration may need to be reversed, or completed manually.
- BIP8799
- Invalid topic syntax was detected in table <insert_0>. Topic is <insert_1>. This will prevent migration from succeeding.
- Severity
- 20 : Error
- Explanation
- Invalid topic syntax was detected in table <insert_0>. Topic is <insert_1>. The destination product requires a new topic syntax and any invalid topic will cause the Broker to be unable to start.
- Response
- Contact IBM service for more assistance; do not attempt to correct the problem.
- BIP8800
- No invalid topic syntax was detected in table <insert_0>.
- Severity
- 0 : Information
- BIP8801
- Unable to migrate the registry for broker <insert_0>
- Severity
- 10 : Warning
- Explanation
- The broker database for the given broker has been migrated successfully, however while attempting to migrate its registry to the current location a failure occurred.
- Response
- Migrate this broker's registry to the current location manually.
- BIP8802
- Sets the license processor count.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsisetcapacity -c processorCount
- Response
- Command Options:
'-c processorCount' is the number of processors on this machine for which WebSphere Message Brokers is licensed.
- BIP8803
- Displays the license processor count. Syntax : mqsidisplaycapacity
- Severity
- 0 : Information
- Explanation
- Shows the processor count entered via the mqsisetcapacity command.
- BIP8804
- This copy of WebSphere Message Brokers is now running in Production mode.
- Severity
- 0 : Information
- Explanation
- A Production license has been installed for this copy of WebSphere Message Brokers.
- BIP8805
- No license installed for this copy of WebSphere Message Brokers.
- Severity
- 20 : Error
- Explanation
- No Production license has been installed for this copy of WebSphere Message Brokers.
- Response
- A valid Production license must be installed before the WebSphere Message Brokers product can be run, ensure that the product installation completed successfully.
- BIP8806
- A license could not be installed for this copy of WebSphere Message Brokers.
- Severity
- 20 : Error
- Explanation
- A Production license could not be installed for this copy of WebSphere Message Brokers. This is because the 'nodelock' file in the '/bin' directory could not be created or updated.
- Response
- Check the ownership and permissions for the '/bin' directory.
- BIP8807
- The Production license for this copy of WebSphere Message Brokers has expired.
- Severity
- 20 : Error
- Explanation
- The production license for this copy of WebSphere Message Brokers has an expiry date. This date has been passed.
- Response
- Contact your IBM support center.
- BIP8808
- License file <insert_0> not found or not valid. For more information refer to the WebSphere Message Brokers online help.
- Severity
- 20 : Error
- Explanation
- WebSphere Message Brokers requires that the file <insert_0> is present and available and is a valid license file. For more information refer to the online help.
- Response
- Check that the specified file exists.
- BIP8809
- This copy of WebSphere Message Brokers is already running in Production mode.
- Severity
- 0 : Information
- Explanation
- A Production license has previously been installed for this copy of WebSphere Message Brokers.
- BIP8810
- Insufficient license units.
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance (<insert_0>) is less than the number of processors (<insert_1>) in this machine.
- Response
- Ensure sufficient license units have been purchased and use the WebSphere Message Brokers mqsisetcapacity command to set the purchased processor allowance for this installation. For more information refer to the online help.
- BIP8811
- The purchased processor allowance is set to <insert_0>.
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance for this installation of WebSphere Message Brokers has been set to <insert_0> using the mqsisetcapacity command.
- BIP8812
- The purchased processor allowance is <insert_0>
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance is currently set to <insert_0>
- Response
- Ensure sufficient license units have been purchased and, if necessary, use the WebSphere Message Brokers mqsisetcapacity command to change the purchased processor allowance for this installation. For more information refer to the online help.
- BIP8813
- The number of processors in this machine is <insert_0>
- Severity
- 0 : Information
- Explanation
- The operating system reports that the number of processors in this machine is <insert_0>.
- BIP8814
- The number of license units is sufficient for all future possible upgrades to this machine.
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance for this installation of WebSphere Message Brokers has been set to -1, which allows any permitted processor configuration.
- BIP8815
- Purchased processor allowance not set (use the mqsisetcapacity command).
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance for this installation has not been set.
- Response
- Ensure sufficient license units have been purchased for WebSphere Message Brokers and use the mqsisetcapacity command to set the purchased processor allowance for this installation. For more information refer to the online help.
- BIP8816
- QueueManagerName does not exist for component <insert_0>.
- Severity
- 20 : Error
- Explanation
- No queues were deleted because QueueManagerName does not exist in the component registry.
- Response
- Ensure the component registry is correct and has not been deleted. Recreate the component registry if necessary.
- BIP8817
- DataSourceName does not exist for component <insert_0>.
- Severity
- 20 : Error
- Explanation
- No database rows were deleted because DataSourceName does not exist in the component registry.
- Response
- Ensure the component registry is correct and has not been deleted. Recreate the component registry if necessary.
- BIP8818
- Creates queues on a WebSphere MQ queue manager for use with a migrated broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
v brokerName
- Response
- Command options
'brokerName' the name of broker whose queues are to be migrated.
- BIP8819
- Migrates WebSphere MQ queues for brokers. Syntax: v
- Severity
- 10 : Warning
- Explanation
- Creates queues on a WebSphere MQ queue manager for use with a migrated broker.
- BIP8820
- Enter password for userid
- Severity
- 10 : Warning
- Explanation
- This is used to prompt for a password for service userid on the console.
- Response
- Enter password for userid
- BIP8821
- Enter password for database userid
- Severity
- 10 : Warning
- Explanation
- This is used to prompt for a password for service userid on the console.
- Response
- Enter password for database userid
- BIP8822
- The supplied password is invalid. Ensure that the password is within the range of 2 - 255 characters in length.
- Severity
- 10 : Warning
- Explanation
- Re-enter the password.
- BIP8823
- Retype password for userid
- Severity
- 10 : Warning
- Explanation
- This is used to prompt for a password for service userid on the console.
- Response
- Retype password for userid
- BIP8824
- Retype password for database userid
- Severity
- 10 : Warning
- Explanation
- This is used to prompt for a password for service userid on the console.
- Response
- Retype password for database userid
- BIP8825
- Passwords do not match.
- Severity
- 10 : Warning
- Explanation
- Passwords do not match.
- Response
- Passwords do not match.
- BIP8827
- Creates a broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreatebroker brokerName -q queueManagerName -n dataSourceName -u dataSourceUserId [-l userLilPath] [-1 | -2 | -3] [-s unsQMgrName [-j]] [-g configurationTimeout] [-k configurationDelayTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath]
- Response
- Command Options
'brokerName' name of the broker to create
'-q queueManagerName' the WebSphere MQ Queue Manager that the broker should use
'-1' creates only the broker's registry
'-2' creates only the broker's WebSphere MQ resources
'-3' creates only the broker's database resources
'-n dataSourceName' the broker's database name
'-u dataSourceUserId' the userid that the broker uses to access its database
'-l userLilPath' the directory from which the broker searches for user-supplied libraries
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j' indicates that Publish/Subscribe access control is to be enabled for this broker
'-g configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message
'-k configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records
'-P httpListenerPort' the port that the broker HTTP listener will use.
'-y ldapPrincipal' the LDAP Principal (userId)
'-z ldapCredentials' the LDAP Credentials (password)
'-x userExitPath' the directory from which the broker searches for all user exits. This path will be added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
- BIP8828
- Deletes a broker.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideletebroker brokerName [-1 | -2 | -3]
- Response
- Command Options:
'brokerName' name of the broker to delete
'-1' deletes only the broker's registry.
'-2' deletes only the broker's WebSphere MQ queues.
'-3' deletes only the broker's database resources.
- BIP8829
- Creates the User Name Server.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateusernameserver -q queueManagerName [-1 | -2] [-r refreshInterval] [-g authProtocolDataSource] [-j]
- Response
- Command Options:
'-q queueManagerName' the WebSphere MQ queue manager that the User Name Server should use.
'-1' only creates the User Name Server's registry.
'-2' only creates the User Name Server's WebSphere MQ resources.
'-r refreshInterval' number of seconds between each refresh of the User Name Server internal cache.
'-g authProtocolDataSource' the name of the data source required by the authentication protocol
'-j' indicates that groups and group memberships will be defined in the data source for the authentication protocol rather than drawn from the Operating System.
- BIP8830
- Deletes the User Name Server.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteusernameserver [-1 | -2]
- Response
- Command Options
'-1' deletes only the User Name Server's registry.
'-2' deletes only the User Name Server's WebSphere MQ queues.
- BIP8831
- Creates the Configuration Manager.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateconfigmgr configMgrName -q queueManagerName [-1 | -2] [-n db2DatabaseToMigrate -u migrationDataBaseUserId -p migrationDataBasePassword] [-s unsQMgrName]
- Response
- Command Options
'configMgrName' name of the Configuration Manager
'-q queueManagerName' the Configuration Manager's WebSphere MQ queue manager
'-1' creates only the Configuration Manager's registry.
'-2' creates only the Configuration Manager's WebSphere MQ resources.
'-n db2DatabaseToMigrate' the DB2 database name, used only for migration from earlier versions.
'-u migrationDataBaseUserId' the userid that the Configuration Manager uses to access the DB2 database.
'-p migrationDataBasePassword' the password for the DB2 database userid.
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server.
- BIP8832
- Deletes the Configuration Manager.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteconfigmgr (-1 | -2) [-n]
- Response
- Command Options
'-1' deletes only the Configuration Manager's registry
'-2' deletes only the Configuration Manager's WebSphere MQ queues
'-n' indicates that the Configuration Manager table should be deleted; use with caution.
- BIP8833
- Changes a broker's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangebroker brokerName [-s unsQMgrName] [-j | -d] [-l userLilPath] [-g configurationTimeout] [-k configurationDelayTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits]
- Response
- Command Options:
'brokerName' name of the broker
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j' indicates that Publish/Subscribe access control is to be enabled for this broker
'-d' indicates that Publish/Subscribe access control is to be disabled for this broker
'-l userLilPath' indicates where 'lil' files are loaded from
'-g configurationTimeout' the maximum time (in seconds) to allow a broker to process a deployed message
'-k configurationDelayTimeout' the maximum time (in seconds) to allow a broker to process a minimum size deployed message
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records
'-P httpListenerPort' the port that the broker HTTP listener will use.
'-y ldapPrincipal' the LDAP Principal (userId)
'-z ldapCredentials' the LDAP Credentials (password)
'-x userExitPath' the directory from which the broker searches for all user exits. This path will be added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the execution group process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a userExit name to this list, changes its default state to active for this broker. The default state can be overridden at the execution group or message flow level using mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the Execution Group starts, then a BIP8860 message will be written to system log and the execution group will fail to start.
- BIP8834
- Changes a User Name Server's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeusernameserver -r refreshInterval [-g authProtocolDataSource] [-j | -o]
- Response
- Command Options:
'-r refreshInterval' number of seconds between each refresh of the User Name Server internal cache.
'-g authProtocolDataSource' the name of the data source required by the authentication protocol
'-j' indicates that groups and group memberships will be defined in the data source for the authentication protocol (rather than drawn from the Operating System)
'-o' indicates that groups and group memberships will be drawn from the Operating System (rather than defined in the data source for the authentication protocol).
- BIP8835
- Changes a Configuration Manager's configuration.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeconfigmgr configMgrName [-s unsQMgrName] [-j MaxJVMHeapSize]
- Response
- Command Options:
'configMgrName' Name of the Configuration Manager
'-s unsQMgrName' the WebSphere MQ queue manager of the User Name Server
'-j MaxJVMHeapSize' the maximum Java virtual machine heap size, in megabytes (default=256) (minimum=64).
- BIP8836
- Changes a Configuration Manager's configuration. Syntax: changeconfigmgr [s=unsQMgrName] [j=MaxJVMHeapSize]
- Severity
- 10 : Warning
- Explanation
- Command Options:
's=unsQMgrName' the WebSphere MQ queue manager of the User Name Server.
'j=MaxJVMHeapSize' the maximum Java virtual machine heap size, in megabytes (default=256) (minimum=64).
- BIP8837
- Creates a security Access Control Entry in the Configuration Manager repository. Syntax: createaclentry (f=fileName | ((g=groupName | (u=userName (m=machineName | a=yes))) x=accessLevel ((b=broker [e=executionGroup]) | s=yes | r=yes | t=yes | p=yes))) [w=timeoutValue]
- Severity
- 10 : Warning
- Explanation
- Command Options:
'f=fileName' File containing list of Access Control Entries to create
'g=groupName' Add Access Control Entry for the specified group
'u=userName' Add Access Control Entry for the specified user (must be accompanied by either a=yes or m=machineName)
'm=machineName' Add the Access Control Entry for the user for this specific machine/domain name only
'a=yes' Add an Access Control Entry for this user for all machines/domains
'p=yes' Add access to the ConfigManagerProxy. Also known as the "All resources" Access Control Entry
'x=accessLevel' desired security access level for specified object (D, E, V, F)
'b=broker' Add access to the specified broker
'e=executionGroup' Add access to the specified execution group (must be accompanied by b=broker)
's=yes' Add access to the subscriptions table
'r=yes' Add access to the root topic
't=yes' Add access to the pub/sub topology
'w=timeoutValue' value in seconds to wait for responses.
- BIP8838
- Deletes a security Access Control Entry in the Configuration Manager repository. Syntax: deleteaclentry (f=fileName | ((g=groupName | (u=userName (m=machineName | a=yes))) ((b=broker [e=executionGroup]) | s=yes | r=yes | t=yes | p=yes))) [w=timeoutValue]
- Severity
- 10 : Warning
- Explanation
- Command Options:
'f=fileName' File containing list of Access Control Entries to delete.
'g=groupName' Delete Access Control Entry for the specified group
'u=userName' Delete Access Control Entry for the specified user (must be accompanied by either a=yes or m=machineName)
'm=machineName' Delete the Access Control Entry for the specified user which applies to this specific machine/domain name only
'a=yes' Delete the "All machines/domains" Access Control Entry for the specified user
'p=yes' Delete access to the ConfigManagerProxy. Also known as the "All resources" Access Control Entry.
'b=broker' Delete Access Control Entry for the specified broker
'e=executionGroup' Delete Access Control Entry for the specified execution group (must be accompanied by b=broker)
's=yes' Delete subscriptions Access Control Entry
'r=yes' Delete root topic Access Control Entry
't=yes' Delete pub/sub topology Access Control Entry
'w=timeoutValue' value in seconds to wait for responses.
- BIP8839
- Lists the security Access Control Entries in the Configuration Manager repository. Syntax: listaclentry [g=groupName | (u=userName (m=machineName | a=yes))] [(b=broker [e=executionGroup]) | s=yes | r=yes | t=yes | p=yes] [f=fileName] [w=timeoutValue]
- Severity
- 10 : Warning
- Explanation
- Command Options:
'f=fileName' Output list of Access Control Entries to given filename
'g=groupName' Display Access Control Entries for the specified group
'u=userName' Display Access Control Entries for the specified user (must be accompanied by either a=yes or m=machine)
'm=machineName' Display Access Control Entries for the specified user which apply to this specific machine/domain name only
'a=yes' Display only those Access Control Entries for the specified user which apply to ALL machines/domain names
'p=yes' Display Access Control Entries for the ConfigManagerProxy. Also known as the "All resources" Access Control Entries
'b=broker' Display Access Control Entries for the specified broker
'e=executionGroup' Display Access Control Entries for the specified execution group (must be accompanied by b=broker)
's=yes' Display Access Control Entries for the subscriptions table
'r=yes' Display Access Control Entries for the root topic
't=yes' Display Access Control Entries for the pub/sub topology
'w=timeoutValue' value in seconds to wait for responses.
- BIP8840
- Deploys pub/sub topology, topics or BAR file configuration data to the specified broker(s). Syntax: deploy ((b=brokerName [e=executionGroupName [a=BARFileName | d=deployedObjects]]) | l=yes | t=yes | c=yes | m=yes) [w=timeoutValue] [v=traceFile]
- Severity
- 10 : Warning
- Explanation
- Command Options:
'b=brokerName' name of broker to deploy to
'e=executionGroupName' name of execution group to deploy to
'a=BARFileName' deploy the specified Broker Archive file
'd=deployedObjects' colon separated list of deployed objects to remove
'l=yes' deploy Topology configuration to all brokers
't=yes' deploy Topics configuration to all brokers
'c=yes' cancel all outstanding deploy requests
'm=yes' deploy complete information (default is to perform incremental deploy; changes to the deployed state)
'w=timeoutValue' value in seconds to wait for the broker to reply to the deploy request
'v=traceFile' send verbose internal trace to the specified file.
- BIP8841
- Deploys pub/sub neighbors, topics or BAR file configuration data to the specified broker(s).
- Severity
- 0 : Information
- Explanation
- Syntax 1 (deploy pub/sub neighbors):
mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -l [-m] [-w timeoutValue] [-v traceFileName]
- Response
- Syntax 2 (deploy topics hierarchy):
mqsideploy (-n cfgParameterFileName | (-i ipAddress -p port -q qMgr)) -t [-m] [-w timeoutValue] [-v traceFileName]
- BIP8842
- Invalid options for ConfigMgr ignored.
- Severity
- 10 : Warning
- Explanation
- From version 6.0 of Message Brokers, the -l and -d options are no longer valid for mqsicreateconfigmgr and mqsichangeconfigmgr. For most purposes in which non-default values were used on these commands, an equivalent effect can be achieved in V6.0 onwards by appropriate use of the -a and/or -m options on the mqsicreateaclentry command.
- Response
- No action is required, the command will safely ignore the -d or -l parameter.
- BIP8843
- Creates a security Access Control Entry in the Configuration Manager repository.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsicreateaclentry configMgrName (-f fileName | ((-g groupName | (-u userName (-m machineName | -a))) -x accessLevel ((-b broker (-e executionGroup)) | -s | -t | -r | -p))) [-n connectionFile] [-w timeoutValue]
- Response
- Command Options:
'configMgrName' name of the Configuration Manager (may be omitted on Windows)
'-f fileName' File containing list of Access Control Entries to create.
'-g groupName' Add Access Control Entry for the specified group
'-u userName' Add Access Control Entry for the specified user (must be accompanied by either -a or -m)
'-m machineName' Add the Access Control Entry for the user for this specific machine/domain name only
'-a' Add an Access Control Entry for the user for all machines/domains
'-x accessLevel' Level of authority to grant (F, E, D, V)
'-b broker' Add access to the specified broker
'-e executionGroup' Add access to the specified execution group (must be accompanied by -b)
'-s' Add access to the subscriptions table
'-t' Add access to the pub/sub topology
'-r' Add access to the root topic
'-p' Add access to the ConfigManagerProxy. Also known as the "All resources" Access Control Entry.
'-w timeoutValue' value in seconds to wait for responses.
'-n connectionFile' Optional "connection file" to allow the command to communicate with a remote ConfigMgr.
Note: On Windows platforms, if the Configuration Manager name is omitted 'ConfigMgr' will be used.
- BIP8844
- Deletes a security Access Control Entry in the Configuration Manager repository.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsideleteaclentry configMgrName (-f fileName | ((-g groupName | -u userName (-m machineName | -a)) ((-b broker [-e executionGroup]) | -s | -t | -r | -p))) [-n connectionFile] [-w timeoutValue]
- Response
- Command Options:
'configMgrName' name of the Configuration Manager (may be omitted on Windows)
'-f fileName' File containing list of Access Control Entries to delete.
'-g groupName' Delete Access Control Entry for the specified group
'-u userName' Delete Access Control Entry for the specified user (must be accompanied by either -a or -m)
'-m machineName' Delete the Access Control Entry for the specified user which applies to this specific machine/domain name only
'-a' Delete the "ALL machines/domains" Access Control Entry for the specified user
'-b broker' Delete Access Control Entry for the specified broker
'-e executionGroup' Delete Access Control Entry for the specified execution group (must be accompanied by -b)
'-s' Delete subscriptions Access Control Entry
'-t' Delete pub/sub topology Access Control Entry
'-r' Delete root topic Access Control Entry
'-p' Delete Access Control Entry for the ConfigManagerProxy. Also known as the "All resources" Access Control Entry.
'-w timeoutValue' value in seconds to wait for responses.
'-n connectionFile' Optional "connection file" to allow the command to communicate with a remote ConfigMgr.
Note: On Windows platforms, if the Configuration Manager is omitted 'ConfigMgr' will be used.
- BIP8845
- Lists the security Access Control Entries in the Configuration Manager repository.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsilistaclentry configMgrName [-g groupName | (-u userName (-m machineName | -a))] [(-b broker [-e executionGroup]) | -s | -t | -r | -p] [-f filename] [-n connectionFile] [-w timeoutValue]
- Response
- Command Options:
'configMgrName' name of the Configuration Manager (may be omitted on Windows)
'-g groupName' Display Access Control Entries for the specified group
'-u userName' Display Access Control Entries for the specified user (must be accompanied by either -a or -m)
'-m machineName' Display Access Control Entries for the specified user which apply to this specific machine/domain name only
'-a' Display only those Access Control Entries for the specified user which apply to ALL machines/domain names
'-b broker' Display Access Control Entries for the specified broker
'-e executionGroup' Display Access Control Entries for the specified execution group (must be accompanied by -b)
'-s' Display Access Control Entries for the subscriptions table
'-t' Display Access Control Entries for the pub/sub topology
'-r' Display Access Control Entries for the root topic.
'-p' Display Access Control Entries for the ConfigManagerProxy. Also known as the "All resources" Access Control Entries.
'-f filename' Output list of Access Control Entries to given filename rather than to the screen.
'-w timeoutValue' value in seconds to wait for responses.
'-n connectionFile' Optional "connection file" to allow the command to communicate with a remote ConfigMgr.
Note: On Windows platforms, if the Configuration Manager name is omitted 'ConfigMgr' will be used.
- BIP8846
- Configuration data for component <insert_0> is not usable by this product version (level <insert_1>; should be <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- Each component has configuration data associated with it, and this data is versioned to ensure that the component can only be run under a product version that supports this level. The component level is <insert_1> and the current code level only supports <insert_2>.
- BIP8847
- migrates a components queues, registry, database and file-system information between different versions.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsimigratecomponents componentName [ -s sourceVersion ] [ -t targetVersion ] [ -c ] [ -1 ] [ -2 ] [ -3 ] [ -v ] [ -q ] [ -u ]
- Response
- Command Options:
'componentName' is the name of the component to query for its registry data
'-s sourceVersion' The current version of the component.
'-t targetVersion' The version of the component to migrate to.
'-c' Do a pre-migration check of the specified component. This will attempt to determine whether the current state of the component is such that it can be safely migrated.
'-1' Do only registry and file-system related migration work. Use this when security restrictions prevent the command from migrating WebSphere MQ, registry and file-system and database in one step.
'-2' Do only WebSphere MQ related migration work. Use this when security restrictions prevent the command from migrating WebSphere MQ, registry and file-system and database in one step.
'-3' Do only database related migration work. Use this when security restrictions prevent the command from migrating WebSphere MQ queues, registry and file-system and database in one step.
'-v' Do a post-migration check of the specified component. This will double-check whether the migration has completed successfully.
'-q' reduce the verbosity of the progress of the command.
'-u' Undo a failed migration step. At least one of -1, -2 or -3 must also be specified. This should only be used when migration has failed, and also failed to auto-recover.
- BIP8848
- Invalid version <insert_0>.<insert_1>.<insert_2>.<insert_3> supplied.
- Severity
- 30 : Severe error
- Explanation
- The supplied version is not compatible to migrate to or from with this component.
- Response
- Check that the string given to the '-s' or '-t' argument is of the form <version>.<release>.<modification>.<fix>.
The minimum supported versions for migration to or from WebSphere Message Brokers Version 6.0 are:
- WebSphere MQ Event Broker or WebSphere MQ Integrator Broker or WebSphere MQ Integrator, Version 2.1 with fix pack 02 or later
- WebSphere Business Integration Event Broker or WebSphere Business Integration Message Broker or WebSphere Business Integration Message Broker with Rules and Formatter Extension, Version 5.0 with fix pack 04 or later
Version 2.1 fix pack 02 is identified by the four digit version number 2.1.0.3
Version 5.0 fix pack 04 is identified by the four digit version number 5.0.0.4
If the version has already been specified correctly the component cannot be automatically migrated.
- BIP8849
- Broker <insert_0> (Version <insert_3>.<insert_4>) with Queue Manager <insert_1> and Data Source <insert_2> specified for migration.
- Severity
- 0 : Information
- BIP8850
- Displays broker property settings.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsireportodbcconnectioninfo -q dsn1 -u userName1 -p password1 [-c dsn2 -i userName2 -a password2] [-v]
- Response
- Command Options:
'-q dsn1' First DataSource to query
'-u userName1' Username to use when connecting to DSN1
'-p password1' Password to use when connecting to DSN1
'-c dsn2' Second DataSource to compare to DSN1
'-i userName2' Username to use when connecting to DSN2
'-a password2' Password to use when connecting to DSN2
'-v' verbose output
Specifing only -q provides ODBC information about DSN1. If -c is also specified then DSN2 is compared to DSN1 for equality of functionality.
- BIP8851
- Migration Failed
- Severity
- 30 : Severe error
- Explanation
- One of the migration steps failed, please see messages above for more details.
- BIP8852
- sets list of active or inaction user exits.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsichangeflowuserexits brokerName -e egName [-f messageFlowName] (-a activeUserExitList |-i inactiveUserExitList)
- Response
- Command Options:
'brokerName' name of the broker
'-e egName' name of the execution group
'-f messageFlowName' name of message flow
'-a activeUserExitList' colon separated list of names of user exits to be set to active state
'-i inactiveUserExitList' colon separated list of names of user exits to be set to inactive state
The command will not alter the existing vlaue of a user exit list, if the corresponding name/value pair is not specified. To clear a user exit list, use an empty string (""), e.g., '-i ""'.
- BIP8853
- queries the lists of active and inactive user exits.
- Severity
- 10 : Warning
- Explanation
- Syntax:
mqsireportflowuserexits brokerName [-e egName [-f messageFlowName]]
- Response
- Command Options:
'brokerName' name of the broker
'-e egName' name of the execution group
'-f messageFlowName' name of message flow
- BIP8854
- User Exits active for Execution Group <insert_0>: <insert_1>.
- Severity
- 0 : Information
- BIP8855
- User Exits inactive for Execution Group <insert_0>: <insert_1>.
- Severity
- 0 : Information
- BIP8856
- User Exits active for Message Flow <insert_0>: <insert_1>.
- Severity
- 0 : Information
- BIP8857
- User Exits inactive for Message Flow <insert_0>: <insert_1>.
- Severity
- 0 : Information
- BIP8858
- Invalid user exit name <insert_0> specified
- Severity
- 20 : Error
- Explanation
- User exit name <insert_0> specified on the <insert_1> flag does not correspond to any user exit available to the target execution group.
- Response
- Review the name provided. If the name is incorrect, reissue the command with the correct name. If the name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes the directory containing the user exit library. Check system log when execution group starts for errors loading the user exit library.
- BIP8859
- User Exits active for broker <insert_0>: <insert_1>.
- Severity
- 0 : Information
- BIP8860
- User Exit <insert_0> not found
- Severity
- 20 : Error
- Explanation
- A User Exit name <insert_0> has been specified as active or inactive but that user exit was not provided by any library loaded by this execution group. No user message flows will be started until this is resolved.
- Response
- Review the name provided. If the name is incorrect, reissue the relevant command with the correct name. If the user exit was set at the broker level, then run mqsichangebroker to correct it. If it was set at the execution group level, then run mqsichangeflowuserexit to correct it. Issue mqsireportflowuserexit to help determine where the invalid user exit name was set. If the name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes the directory containing the user exit library. Check system log when execution group starts for errors loading the user exit library.
- BIP8861
- User Exit <insert_0> not found for flow <insert_1>
- Severity
- 20 : Error
- Explanation
- A User Exit name <insert_0> has been specified as active or inactive for message flow <insert_1> but that user exit was not provided by any library loaded by this execution group. This message flow will be not started until this is resolved.
- Response
- Review the name provided. If the name is incorrect, reissue the mqsichangeflowuserexit command with the correct name. If the name is correct, ensure that the user exit library is being loaded by the execution group. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath broker property to ensure one of them includes the directory containing the user exit library. Check system log when execution group starts for errors loading the user exit library.
- BIP8862
- sets list of active or inaction user exits.
- Severity
- 10 : Warning
- Explanation
- Syntax:
changeflowuserexits brokerName e=egName [f=messageFlowName] (a=activeUserExitList |i=inactiveUserExitList)
- Response
- Command Options:
'brokerName' name of the broker
'e=egName' name of the execution group
'f=messageFlowName' name of message flow
'a=activeUserExitList' colon separated list of names of user exits to be set to active state
'i=inactiveUserExitList' colon separated list of names of user exits to be set to inactive state
- BIP8863
- queries the lists of active and inactive user exits.
- Severity
- 10 : Warning
- Explanation
- Syntax:
reportflowuserexits brokerName [e=egName [f=messageFlowName]]
- Response
- Command Options:
'brokerName' name of the broker
'e=egName' name of the execution group
'f=messageFlowName' name of message flow
- BIP8864
- Internal Error: Unable to set RC and inserts (RC is <insert_0>).
- Severity
- 20 : Error
- Explanation
- Unable to set RC and inserts as RC, <insert_0>, is unknown.
- Response
- Contact your IBM support center to report this error.
- BIP8865
- Bad flag combination. The flags in list (<insert_0>) can't be specified together.
- Severity
- 20 : Error
- Explanation
- None.
- Response
- Correct and reissue the command.
- BIP8866
- Registry is not in the right state for this step-by-step migration (by using the '-2'/'-3' flags) from Version (<insert_0>.<insert_1>.<insert_2>.<insert_3>) to Version (<insert_4>.<insert_5>.<insert_6>.<insert_7>).
- Severity
- 20 : Error
- Explanation
- For a forward migration, the right order for step-by-step migration is to migrate the registy (by using the '-1' flag) before migrating anything else. For a backward migration, the right order for step-by-step migration is to migrate the registy last.
- Response
- Correct the migration order.
- BIP8867
- Migration from Version <insert_0>.<insert_1>.<insert_2>.<insert_3> to Version <insert_4>.<insert_5>.<insert_6>.<insert_7> is not supported.
- Severity
- 20 : Error
- Explanation
- Direct migrations between two previous versions are not supported, i.e. either the source version or the target version must be the current product version.
- Response
- Correct migration strategy.
- BIP8868
- <insert_0> is not a known component. However, an attempt will be made to delete resources associated with this component name. Make sure that you spelt the component name correctly, and that you ran the command on the right computer. Also make sure that the component was created by, or was migrated to, the current version of WebSphere Message Brokers.
- Severity
- 10 : Warning
- BIP8901
- Table <insert_0> is not empty. This table will be dropped after a migration to the target version is performed.
- Severity
- 10 : Warning
- Explanation
- Manually backup the table, if required, before performing the migration.
- BIP8902
- Table <insert_0> is empty.
- Severity
- 0 : Information
- BIP8981
- This command creates an object associated with a type of configurable service.
- Severity
- 10 : Warning
- Explanation
- Syntax:
v brokerName -c configurableService -o object ( -n name -v value )
- Response
- Command options:
'brokerName': name of the broker
'-c configurableService': configurable service type used by the broker
'-o object': object name belonging to the configurable service type
'-n name': attribute name
'-v value': attribute value.
- BIP8982
- This command deletes an object name associated with a type of external resource that was previously created using the mqsicreateconfigurableservice command.
- Severity
- 10 : Warning
- Explanation
- Syntax:
v brokerName -c configurableService -o object
- Response
- Command options:
'brokerName': name of the broker
'-c configurableService': a type of configurable service used by the broker
'-o object': object name belonging to the type of configurable service
- BIP8983
- Configurable service object name <insert_0> already exists.
- Severity
- 10 : Warning
- Explanation
- The user has tried to create a configurable service object name that already exists.
- Response
- Check the names of the existing configurable services using the mqsireportproperties command. Then modify the external resource object name and reissue the command.
- BIP8984
- Configurable service object name <insert_0> was not found.
- Severity
- 10 : Warning
- Explanation
- The user has tried to delete or modify a configurable service object name that does not exist.
- Response
- Check the names of the existing configurable services using the mqsireportproperties command. Then modify the external resource object name and reissue the command.
- BIP8995
- Please ensure that you have applied CSD 1 for this product prior to using the v command.
- Severity
- 0 : Information
- Explanation
- CSD 1 must be applied to this installation of WebSphere Message Brokers. Brokers cannot be migrated until the CSD is applied. Configuration Managers can be migrated before the CSD is applied.
- Response
- Contact your IBM support center for details about CSD availability.
- BIP8996
- Version: <insert_0>
- Severity
- 0 : Information
- BIP8997
- Product: <insert_0>
- Severity
- 0 : Information
- BIP8998
- CMVC Level: <insert_0>
- Severity
- 0 : Information
- BIP8999
- Build Type: <insert_0>
- Severity
- 0 : Information