BIP8000-8999: Runtime components - Commands

BIP8000
Failed to connect to the Integration Registry using the URI <insert_1>. Reason <insert_2>.
Severity
20 : Error
Explanation
The Integration Registry can not be connected to using the URI given.
Response
Review the reason given. Ensure that the Web Administration Interface is enabled and running correctly.

BIP8001
Unknown flag <insert_1> 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_1> 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_1> specified.
Severity
20 : Error
Explanation
Argument specified should be well formed.
Response
Correct and reissue the command.

BIP8005
Flag or argument <insert_1> 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_1>) 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 integration node name does not contain invalid characters or is too long.

BIP8012
It was not possible to connect to system components.
Severity
20 : Error
Explanation
The command issued 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 Windows services. Reissue the command when the problem has been resolved.

BIP8013
Integration node <insert_1> does not exist.
Severity
20 : Error
Explanation
An integration node can be used only if it has already 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 cannot start the required component.
Response
The possible causes of this error are: insufficient user ID permissions; lack of system resources (not enough memory); the WebSphere MQ environment is not configured correctly for the user who is running the command (for example, the mqm library is missing from the user's path).

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
Integration node <insert_1> running.
Severity
20 : Error
Explanation
This integration node is running; the command you issued cannot be processed when an integration node is running.
Response
Stop the integration node and reissue the command.

BIP8019
Integration node <insert_1> stopped.
Severity
20 : Error
Explanation
This integration node is stopped; the command you issued cannot be processed when an integration node is stopped.
A previous command has been issued to stop this integration node, or this integration node has never been started.
Response
This integration node can be started, changed, or deleted.

BIP8020
Unable to access the integration node's configuration.
Severity
20 : Error
Explanation
The command was unable to access the integration node's internal configuration store.
Response
Ensure that the integration node's service userid has permission to access the file system.

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
The component is 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 this may be because the component's service was 'disabled'.

BIP8026
It was not possible to start the component.
Severity
20 : Error
Explanation
The component could not be started using the service user ID that was supplied when the component was created.
Response
Ensure that the service user ID and password are still valid. Ensure that the service user ID has permission to access all of the product directories, specifically the 'bin' and 'log' directories. Check for system messages. (On Windows this would be the application event log).

BIP8027
It was not possible to start WebSphere MQ.
Severity
20 : Error
Explanation
IBM Integration Bus requires that WebSphere MQ is installed and its service 'IBM MQSeries' is available.
Response
On Windows the WebSphere MQ service must be available before the IBM Integration Bus component can be started. The WebSphere MQ service was unable to start. See the event log or syslog to determine the cause of the failure. Correct the problem and reissue the command.

BIP8028
The required product is unavailable.
Severity
20 : Error
Explanation
IBM Integration Bus requires that WebSphere MQ is installed and that its service 'IBM MQSeries' is available.
Response
Ensure that WebSphere MQ is installed, and that the service is started and running correctly.

BIP8029
The integration node's configuration is not yet deployed.
Severity
20 : Error
Explanation
This command results in an internal configuration message to the integration node, this message may only be sent after at least one deployment to the integration node from the Integration Toolkit.
Response
Reissue the command after the integration node's configuration has been deployed.

BIP8030
It was not possible to modify user ID privileges.
Severity
20 : Error
Explanation
On Windows the command issued modifies a user ID's privileges, ('logon as service').
Response
Ensure that the user ID issuing this command has sufficient privileges to modify the privileges of the user ID supplied in the command. Ensure that a Domain Controller, either Primary or Backup, is available. Re-execute the command. If the problem persists, 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 the integration node.
Severity
20 : Error
Explanation
An attempt was made to connect to the integration node, this attempt was unsuccessful.
Response
Ensure that the integration node is running.

BIP8033
Unable to send an internal configuration message to the integration node.
Severity
20 : Error
Explanation
This command was unable to send an internal configuration message to the integration node.
Response
Ensure that the integration node is running.

BIP8034
An internal configuration response message not received.
Severity
20 : Error
Explanation
This command sends an internal configuration message to the integration node, an internal configuration response message was not received from that integration node.
Response
Ensure that the integration node is running.

BIP8035
An internal configuration response message was expected from the integration node 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 integration node, 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 integration node 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 integration node. The response received indicated that the internal configuration message was unsuccessful.
Response
Check the system log for further information.

BIP8037
Unsupported flag. The flags listed in (<insert_1>) 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 IBM Integration Bus online documentation for the list of valid options for this command. Correct and reissue the command.

BIP8039
The integration server is not available.
Severity
20 : Error
Explanation
The integration server could not be found; it may have been deleted by the Integration Toolkit or a CMP application.
Response
Use the Integration Toolkit or a CMP application to see if the integration server exists.

BIP8040
Unable to connect to the database.
Severity
20 : Error
Explanation
The database cannot be accessed with the specified user Id and password pair.
Response
- Check that the database is running.
- Check that the database has an adequate number of database connections available for use.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.
- On z/OS check the BIPDSNAO member of the component's dataset, and check the DB2 64bit ODBC driver (DSNAO64C) is in the STEPLIB.
- Use mqsisetdbparms to set the password to the correct value and try again.

BIP8041
Unable to open the selected file <insert_1>.
Severity
20 : Error
Explanation
A product component cannot open the specified file for read or write, for example a log file.
Response
Ensure that:
1. The file path is valid.
2. If specified as input, the file exists and is not also specified as output.
3. 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 an integration node trace file.
Severity
20 : Error
Explanation
Integration node 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 IIB command response <insert_1>.
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 Integration Toolkit or a custom integration application.
Response
Use the Integration Toolkit or a custom integration application to see if the message flow exists.

BIP8046
Unable to initialize parser data, exception caught <insert_1>.
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_1>.
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.

BIP8049
Unable to stop WebSphere MQ Queue Manager <insert_1>.
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_1>.
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_1> on Queue Manager <insert_2>.
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_1> from queue manager <insert_2>.
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 any applications are connected to your integration node, you may need to stop these as well.

BIP8053
Unable to set the security attributes for WebSphere MQ Queue Manager <insert_1>, Group <insert_2>.
Severity
20 : Error
Explanation
This command attempts to set the Group security attributes for a WebSphere MQ 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 MQ Queue <insert_1> on Queue Manager <insert_2>, Group <insert_3>.
Severity
20 : Error
Explanation
This command attempts to set the Group security attributes for a WebSphere MQ 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_1>.
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 integration node's classes directory.

BIP8056
The component's WebSphere MQ queue manager <insert_1> 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 recreate the component.

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.

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
The mqsichangefileauth command changes the security permissions for a specified resource.
Severity
10 : Warning
Explanation
Syntax:
mqsichangefileauth <integrationNodeName> -r <role> [-o <resourceObject>] [-e <integrationServerName>] -p permissions

Command options:
'integrationNodeName' integration node name
'-r role' role or system user for the desired action
'-o resourceObject' resource object name for the desired action
'-e integrationServerName' integration server name
'-p permissions' the permissions that are added or removed from the sum of permissions applied to the resource for the specified role or system user. Specify the permissions as a comma-separated list of values. Possible values are: read[+/-], write[+/-], execute[+/-], all[+/-]. Each value for 'read', 'write', or 'execute' can be specified only once in the list of values. If 'all' is specified, it must be the only value.

BIP8061
Invalid resource <insert_1> supplied.
Severity
30 : Severe error
Explanation
The supplied resource is not valid as a resource specifier.
Response
Check that the value given to the '-o' argument is 'DataCapture'.

BIP8062
Join request has failed because parent integration node is already a neighbor.
Severity
20 : Error
Explanation
The mqsijoinmqpubsub command has failed because the named parent integration node is already a neighbor.
Response
If a previous attempt to join the two integration nodes 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 integration node is not a neighbor.
Severity
20 : Error
Explanation
The mqsiclearmqpubsub command has failed because the named integration node was not a neighbor.
Response
Reissue the command specifying an integration node 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 integration node already has a parent.
Severity
20 : Error
Explanation
The mqsijoinmqpubsub command has failed because the integration node already has a parent IBM Publish/Subscribe integration node.
Response
Remove the existing parent integration node before reissuing the command.

BIP8067
Request has failed because couldn't contact the parent IBM publish/subscribe integration node.
Severity
20 : Error
Explanation
The mqsijoinmqpubsub command has failed because the supplied IBM publish/subscribe integration node 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 integration node name not resolving to the name of a transmission queue at the queue manager which is hosting the IBM Integration Bus integration node. Correct the underlying problem with the IBM network and reissue the command.

BIP8068
Argument <insert_1> 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_1> in message catalog <insert_2>.
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_1>: SQL state <insert_2>; exception <insert_3>.
Severity
20 : Error
Explanation
An SQL command has failed.
Response
Ensure that the integration node'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_1>: exception <insert_2>.
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_1> 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_1>. The text is <insert_2>.
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_1>.
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_1> can't be accessed, correct the problem and retry the command. If the problem still occurs, contact your IBM support center.

BIP8079
Unable to find service user id <insert_1>.
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 occurred while the command was running; the command has cleaned up and ended.
Response
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.

BIP8082
Unable to delete WebSphere MQ Queue Manager <insert_1>.
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 integration node name that you specified, <insert_1>, contains characters that are not valid.
Severity
20 : Error
Explanation
The integration node name must only contain characters that are supported by the platform on which the command is being processed.
Response
Correct the integration node name and reissue the command.

BIP8084
Unable to create directory <insert_1>, return code <insert_2>.
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_1> 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_1> is already being used by integration node <insert_2>.
Severity
20 : Error
Explanation
An attempt was made to use a WebSphere MQ queue manager that was already in use by another integration node. It is not acceptable for multiple integration nodes to share a single WebSphere MQ queue manager.
Response
Choose another WebSphere MQ queue manager and reissue the command.

BIP8087
<insert_1> 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
The mqsichangeauthmode command specifies the mode of administration security that will be used for granting and revoking permissions, and enables or disables administration security for the integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsichangeauthmode <integrationNodeName> -s <adminSecurity> [-m <mode>]

Command options:
'integrationNodeName' integration node name
'-s adminSecurity' activates integration node administration security. Valid values that can be set are 'active' and 'inactive'.
'-m mode' authorization mode to be used, which must be set when administration security is active. Valid values that can be set are 'mq' and 'file'.

BIP8089
The mqsireportauthmode command is used to view the mode of administration security currently in effect for granting and revoking administration authority.
Severity
10 : Warning
Explanation
Syntax:
mqsireportauthmode <integrationNodeName>

Command options:
'integrationNodeName' integration node name

BIP8090
The mqsireportfileauth command reports the security permissions granted for a specified role or system user to access a specified resource.
Severity
10 : Warning
Explanation
Syntax:
mqsireportfileauth <integrationNodeName> [-o <resourceObject>] [-e <integrationServerName>] [-r <role>] [-l]

Command options:
'integrationNodeName' integration node name
'-o resourceObject' resource object name
'-e integrationServerName' integration server name
'-r role' role or system user
'-l' list all roles

BIP8091
Common stream <insert_1>.
Severity
0 : Information

BIP8092
Unable to locate IBM Integration Bus response <insert_1> in message catalog <insert_2>.
Severity
20 : Error
Explanation
The IBM Integration Bus response could not be found in the message catalog.
Response
Make sure that the message catalog is available and that the IBM Integration Bus 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
IBM queue manager <insert_1> is being used by IBM Integration Bus component <insert_2>.
Severity
20 : Error
Explanation
An attempt was made to delete a queue manager that in use by another IBM Integration Bus component. The queue manager delete option provided by this command can only be selected if there are no other IBM Integration Bus components using that queue manager.
Response
If it is no longer required, delete the component before deleting the 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_1>.
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_1>, mode: <insert_2>, size: <insert_3> KB.
Severity
0 : Information

BIP8099
<insert_1>: <insert_2> - <insert_3>3
Severity
0 : Information

BIP8100
Unable to detect an installation of WebSphere MQ
Severity
0 : Information

BIP8101
Changes the configuration of an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsichangebroker integrationNodeName [[-i generalDefaultUserId] -a generalDefaultPassword] [-q queueManagerName] [-t | -n] [-l userLilPath] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-c ICU converter path] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits] [-s adminSecurity] [-f function level] [-b cachePolicy] [-r cachePortRange]


Command options:
'integrationNodeName' the name of the integration node to change.
'-i generalDefaultUserId' the default user ID that the integration node will use to connect to external resources.
'-a generalDefaultPassword' the password to be used with the generalDefaultUserId.
'-C CCSID' the default coded character set ID for the integration node.
'-q queueManagerName' change the queue manager that is associated with the integration node.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-n' disables WebSphere MQ fastpath for this integration node.
'-l userLilPath' indicates where user-written LIL and JAR files are loaded from.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c ICU converter path' delimited ':' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a user exit name to this list changes its default state to active for this integration node. The default state can be overridden at the integration server or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the integration server starts, a BIP8860 message is written to the system log and the integration server fails to start. The separator character for the list is ':'.
'-s adminSecurity' activates integration node administration security. Valid values that can be set are 'active' and 'inactive'.
'-f function level' the effective function level of the integration node, such as '7.0.0.1', '7.0.0.2', or 'all'
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.

BIP8104
Changes a component's trace options.
Severity
10 : Warning
Explanation
Syntax (1):
mqsichangetrace componentName [-u | -t | [-n on | off]] -e integrationServerName [[-k application] [-y staticLibrary] -f messageFlow] [-l level] [-m mode] [-c size] [-r]
Syntax (2):
mqsichangetrace componentName -t -b [-l level] [-m mode] [-c size] [-r]


Command options:
'componentName' name of the component whose trace options are to be changed
'-u' indicates user trace (use only with '-e')
'-t' indicates service trace
'-n' indicates trace node settings (use only with '-e')
'-b' denotes tracing of a component other than an integration server
'-e integrationServerName' name of the integration server
'-k application' name of the application
'-y staticLibrary' name of the static library
'-f messageFlow' name of the message flow
'-l level' specifies the trace level: 'none', 'normal' or 'debug'
'-m mode' specifies the trace mode: 'safe', 'fast', 'temp' or 'temp=<a comma-separated list of BIP messages to disable trace on occurrence of any one of them. Specify up to 10 BIP messages.>'
'-c size' specifies the trace file size in kilobytes
'-r' specifies that the log should be reset
Certain conditions apply to these optional parameters. Check the online documentation for more information.

BIP8105
Creates an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsicreatebroker. integrationNodeName [-q queueManagerName] [-i generalDefaultUserId -a generalDefaultPassword] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-w workPath] [-e sharedWorkPath] [-l userLilPath] [-t] [-m] [-v statisticsMajorInterval] [-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath] [-o operationMode] [-s adminSecurity] [-d MQService] [-b cachePolicy] [-r cachePortRange]


Command Options:
'integrationNodeName' the name of the integration node.
'-q queueManagerName' the default WebSphere MQ queue manager that is used by the integration node. If -q is not specified, there is no default WebSphere MQ queue manager associated with the integration node.
'-i generalDefaultUserId' the default user ID that the integration node will use to connect to external resources.
'-a generalDefaultPassword' the password to be used with the generalDefaultUserId.
'-C CCSID' the default coded character set ID for the integration node.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-w workPath' the directory in which internal data, such as installation logs, component details, and trace output are written.
'-e sharedWorkPath' the directory in which registry and configuration data is shared between multiple instances of this integration node.
'-l userLilPath' the directory from which the integration node searches for user-supplied libraries.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-m' indicates that migration is required from an IBM publish/subscribe integration node.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c icuConverterPath' delimited ':' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-o operationMode' the integration node operation mode. Valid values that you can set are 'express', 'standard', 'adapter', 'advanced' and 'applicationIntegrationSuite'. The default mode is 'advanced' unless you have the Trial Edition, in which case the default mode is 'trial'.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'. The default is 'inactive'.
'-d MQService' start the broker as a WebSphere MQ Service when the queue manager starts. Valid values that you can set are 'defined' and 'undefined'. The default is 'undefined'.
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.

BIP8108
Deletes an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsideletebroker. integrationNodeName [-w] [-s]


Command Options:
'integrationNodeName' Name of the integration node to delete
'-w' deletes the integration node's trace files from its work directory.
'-s' delete the integration node and any current integration server administration security WebSphere MQ queues.

BIP8111
Formats the trace log retrieved using mqsireadlog.
Severity
10 : Warning
Explanation
Syntax:
mqsiformatlog -i inputFileName [-o outputFileName]


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).

BIP8113
Lists the components that have been created and their WebSphere MQ queue managers.
Severity
10 : Warning
Explanation
Syntax:
mqsilist [-a] [integrationNodeName [-e integrationServerName]]


Command Options:
'-a' lists all components on this machine.
'integrationNodeName' lists integration servers configured for an integration node
'-e integrationServerName' lists message flows configured for an integration server.

BIP8114
Retrieves the trace log.
Severity
10 : Warning
Explanation
Syntax (1):
mqsireadlog componentName (-u | -t) -e integrationServerName [-f] [-o outputFileName]
Syntax (2):
mqsireadlog componentName -t -b subcomponent -f [-o outputFileName]
Syntax (3):
mqsireadlog componentName -t -x integrationServerUuid -f [-o outputFileName]


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 integrationServerName' Name of the integration server
'-x integrationServerUuid' Universally Unique Identifier (UUID) of the integration server
'-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 | -n) -e integrationServerName [[-k application] [-y staticLibrary] -f messageFlow]
Syntax (2):
mqsireporttrace componentName -t -b

Syntax (3):
mqsireporttrace componentName [-u | -t]


Command options:
'-u' indicates user trace (use only with '-e')
'-t' indicates service trace
'-n' indicates trace node settings (use only with '-e')
'-b' denotes tracing of a component other than an integration server
'-e integrationServerName' integration server name
'-k application' application name
'-y staticLibrary' static library name
'-f messageFlow' message flow name

BIP8116
Starts an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsistart integrationNodeName

Command Options:
'integrationNodeName' name of the integration node to start

BIP8117
Stops an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsistop integrationNodeName [-i]

Command Options:
'integrationNodeName' name of the integration node to stop
'-i' forces the integration node to stop immediately (use with caution).

BIP8119
Lists the credentials of resources that are associated with an integration node.
Severity
10 : Warning
Explanation
Syntax (1):
mqsireportdbparms <integrationNodeName> -n <resource>
Syntax (2):
mqsireportdbparms <integrationNodeName> -n <resource> [-u <userId>] [-p <password>]
Syntax (3)
mqsireportdbparms <integrationNodeName> -n <resource> [-u <userId>] [-i <sshIdentity>] [-r <passPhrase>]

Command options, syntax (1)
<integrationNodeName >
The integration node name.
-n <resource>
The data source, resource name, or resource type of interest.
Lists the resources that are associated with the integration node and that have the specified resource name or type, together with their credentials.
If a non-SFTP data source is entered, the user ID is returned.
If an SFTP data source has been entered, the user ID and the SSH identity (if it is set) are returned.
If entering a specific resource, enter the resource name; for example, dsn&colon.&colon.odbc
If searching for a resource type, enter the first few letters of the resource type, such as ftp, followed by an asterisk.
See below for a list of available resource options
Command options, syntax (2):
<integrationNodeName>
The name of an integration node.
-n <resource>
The name or type of the resource that is associated with <userId> and <password>.
-u <userId>
The user identifier associated with <resource>.
-p <password>
The password that you are trying to verify is associated with <userId>.
Checks whether the password that you associate with a particular user ID and resource is correct.
When verifying a password, the -u and -p flags must be used together.

Command options, syntax (3):
<integrationNodeName>
The name of an integration node.
-n <resource>
The name of an SFTP resource that is associated with <SSHIdentity> and <passphrase>.
-u <userId>
The user identifier that is associated with <resource>.
-i <SSHIdentity>
The fully qualified path to the SSH identity that is associated with <resource>.
-r <passphrase>
The passphrase that is associated with <SSHIdentity>.
Validates an SSH identity and passphrase that are associated with <resource>
You must use the -u, -i, and -r flags together, and the resource must be an SFTP resource.

List of possible resources that can be entered with this command
The resource can be one of the following types. Each type is determined by the syntax of the <resource> parameter:

-n odbc::<Data Source Name>
The ODBC data source name

-n ftp::<security identity>
The FTP server security identity that is specified on File nodes.

-n jms::<JMS connection factory name>
The JMS ConnectionFactory that is used by a JMS node.

-n jndi::<JNDI administered object name>
The JNDI name that is associated with a JMS ConnectionFactory or Destination.

-n jdbc::<security identity>
The JDBC security identity.

-n <data source name>
The Data Source Name (DSN) that is used in Compute, Mapping, or Database nodes.

-n mq::<security identity>
The WebSphere MQ security identity used to connect to a secured queue manager from MQ nodes.

-n mqtt::<security identity>
The MQTT security identity used to connect to a secured MQTT server.

-n eis::<adapter name>
The adapter name that is used by the WebSphere Adapters nodes.

-n email::<security identity>
User identity for the EmailInput node or EmailServer configurable service.

-n ims::<security identity>
The IMS Connect security identity that is specified on an IMS node.

-n cics::<security_identity>
The CICS security identity that is specified on a CICSRequest node.

-n sftp::<security_identity>
The SFTP security identity that is used on a File node.

-n cd::<security_identity>
The Connect:Direct security identity that is used on the CD nodes. cd&colon.&colon.default is the default security identity used by the nodes.

-n wxs::<security_identity>
The WebSphere eXtreme Scale security identity that is used by the WebSphere eXtreme Scale configurable service.

-n salesforce::<security identity>
The Salesforce server security identity that is used on a Salesforce node.

-n loopback::<security identity>
The LoopBack connector security identity that is used on a LoopBackRequest node.

-n rest::<security identity>
The REST security identity specified on a REST request node.

-n kafka::KAFKA::<server name>
The Kafka security identity used for Kafka nodes deployed to an Integration server.

This command can be run when the integration node is running or when it is stopped.

BIP8120
Migrates integration node 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


Command Options:
'componentName' Name of the component to browse
'-t persistentStoreTable' the persistent store table to browse.

BIP8122
The mqsireportproperties command displays the values of integration node properties.
Severity
10 : Warning
Explanation
Syntax 1:
mqsireportproperties integrationNodeName -o ObjectName ( -b httplistener | -b securitycache | -b servicefederation | -b webadmin | -b cachemanager | -b eventpublisher | -e integrationServerName | -c ConfigurableService ) (-n PropertyName | -a | -r) [-p Path/Filename] [-f]
Syntax 2:
mqsireportproperties integrationNodeName (-o BrokerRegistry | -o SecurityCache) (-n PropertyName | -a | -r) [-p Path/Filename]

Command Options:
'integrationNodeName' The name of the integration node.
'-b httplistener' Report properties for the HTTP Listener component.
'-b securitycache' Report properties for the Security Cache component.
'-b servicefederation' Report properties for the Service Federation Management component.
'-b webadmin' Report properties for the Web Administration component.
'-b cachemanager' Report properties for the Cache Manager component.
'-b pubsub' Report properties for the Publish/Subscribe component.
'-e integrationServerName' The name of the integration server.
'-c ConfigurableService' The type of the configurable service, for example, JMSProviders. Specify a value of "AllTypes" to list all configurable service types.
'-o ObjectName' The name of the object to report on. Specify a value of "AllReportableEntityNames" to list all valid object names.
'-n AttributeName' Display the value of the named attribute.
'-a' Display all attribute values (non-recursive).
'-r' Display all attribute values (recursive).
'-p Path/Filename' The name of a file to write the integration node property settings to. If -n is specified, the attribute name is omitted from the output; only the value of the attribute is written to the file.
'-f' Allow the command to run when the integration server is stopped. This option can be used only along with the -e option.

BIP8123
The mqsichangeproperties command changes the values of integration node properties.
Severity
10 : Warning
Explanation
Syntax 1:
mqsichangeproperties integrationNodeName ( -b httplistener | -b securitycache | -b servicefederation | -b webadmin | -b cachemanager | -b eventpublisher | -e integrationServerName | -c ConfigurableService ) -o ObjectName -n PropertyName ( -v PropertyValue | -d | -p Path/Filename ) [-f]
Syntax 2:
mqsichangeproperties integrationNodeName ( -o BrokerRegistry | -o SecurityCache | -o ComIbmJvmManager ) -n PropertyName ( -v PropertyValue | -d | -p Path/Filename ) [-f]

Command options:
integrationNodeName: The name of the integration node to modify.
'-b httplistener': Change properties for the HTTP Listener component.
'-b securitycache': Change properties for the Security Cache component.
'-b servicefederation' Change properties for the Service Federation Management component.
'-b webadmin' Change properties for the Web Administration component.
'-b cachemanager' Change properties for the Cache Manager component.
'-b pubsub' Report properties for the Publish/Subscribe component.
'-e integrationServerName' Change properties for the integration server.
'-c ConfigurableService' Change properties for a configurable service used by the integration node, such as JMSProviders.
'-o ObjectName' The name of the object for which you want to change the properties.
'-n PropertyName' The name of the property to be changed.
'-v PropertyValue' The value that is assigned to the property specified by the -n parameter. Specify more than one property name and corresponding value by using commas as separators; for example, -n Name1, Name2 -v Value1, Value2.
'-d' If the property that you specify on the -n parameter exists, it is deleted. This parameter is valid only if you specify a configurable service of type UserDefined.
'-p Path/Filename' The name of a file to read the integration node property settings from.
'-f' Allow the command to run when the integration server stopped. Use this option only for recovering from integration server startup failures and only with the -e option.

BIP8124
Changes and reports a component's details.
Severity
10 : Warning
Explanation
Syntax:
mqsiservice. [-v] [componentName [-r label=value]] [-m messageNumber [-c messageCatalog]] [-t]


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 time zone.

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


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


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 an integration node's subscriptions table looking for CBR filters that include string literals with escape characters.
Severity
10 : Warning
Explanation
Syntax:
mqsicbrreport integrationNodeName


Command Options
'integrationNodeName' Name of the integration node.

BIP8128
Reloads an integration node's integration servers.
Severity
0 : Information
Explanation
Syntax:
mqsireload integrationNodeName [-e integrationServerName]


Command Options:
'integrationNodeName' The name of the integration node.
'-e integrationServerName' The name of the integration server to reload.

BIP8129
Sets the credentials of resources that are associated with an integration node.
Severity
10 : Warning
Explanation
Syntax (1):
mqsisetdbparms <integrationNodeName> -n <resource> [-u <userId>] [-p <password>] [-f]
Syntax (2):
mqsisetdbparms <integrationNodeName> -n <resource> -d [-f]
Syntax (3):
mqsisetdbparms <integrationNodeName> -n <resource> [-u <userId>] [-i <ssh_identiy>] [-r <passphrase>] [-f]
Syntax (4):
mqsisetdbparms <integrationNodeName> -n <resource> [-u <userId>] [-p <password>] [-c <client identity>] [-s <client secret>] [-f]
Syntax (5):
mqsisetdbparms <integrationNodeName> -n <resource> [-u <userId>] [-p <password>] [-k <API key>] [-f]


Command options, syntax (1):
<integrationNodeName>
The integration node name.
-n <resource>
The type and name of the resource with which the <userId> and <password> are associated.
-u <userId>
The user identifier associated with <resource>.
If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter.
If the resource does not already exist, you must set this parameter.
-p <password>
The password associated with <resource>.
You must set the <userId> and <password>.

Command options, syntax (2)
<integrationNodeName>
The integration node name.
-n <resource>
The type and name of the resource with which the <userId> and <password> are associated.
-d
Deletes the <resource>, <userId>, and <password> information.

Command options, syntax (3):
<integrationNodeName>
The integration node name.
-n <resource>
The type and name of the resource with which the <userId> and <ssh_identity> are associated.
-u <userId>
The user identifier associated with <resource>.
If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter.
If the resource does not already exist, you must set this parameter.
-i <ssh_identity>
The fully qualified path to the SSH identity associated with <resource>.
You must set the <userId> and <ssh_identity>.
-r <passphrase>
The passphrase associated with <ssh_identity>.
The passphrase is optional.

Command options, syntax (4):
<integrationNodeName>
The integration node name.
-n <resource>
The type and name of the resource with which the <userId> and <password> are associated.
-u <userId>
The user identifier associated with <resource>.
If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter.
If the resource does not already exist, you must set this parameter.
-p <password>
The password associated with <resource>.
You must set the <userId> and <password>.
-c <client identity>
The client identity associated with <resource>.
-s <client secret>
The client secret associated with <resource>.

Command options, syntax (5):
<integrationNodeName>
The integration node name.
-n <resource>
The type and name of the resource with which the <userId>, <password>, and <API key> are associated.
You must specify a user ID, an API key, or a user ID and an API key.
If you specify a user ID, you must also specify a password.
You can specify a password without a user ID if the resource already exists and a user ID is already associated with the resource.
-u <userId>
The user identifier associated with <resource>.
-p <password>
The password associated with <resource>.
-k <API key>
The API key associated with <resource>.

The resource can be one of the following types. Each type is determined by the syntax of the <resource> parameter:

-n odbc::<Data Source Name>[::<integration server name>]
The ODBC Data Source Name, with optional integration server name

-n ftp::<security identity>
The FTP server security identity specified on File nodes.

-n jms::<JMS connection factory name>
The JMS ConnectionFactory used by a JMS node.

-n jndi::<JNDI administered object name>
The JNDI name associated with a JMS ConnectionFactory or Destination.

-n jdbc::<security identity>
The JDBC security identity.

-n <data source name>
The Data Source Name (DNS) that is used in Compute, Mapping, or Database nodes.

-n mq::<security identity>
The WebSphere MQ security identity used to connect to a secured queue manager from MQ nodes.

-n mqtt::<security identity>
The MQTT security identity used to connect to a secured MQTT server.

-n eis::<adapter name>
The adapter name used by the WebSphere Adapters nodes.

-n email::<security identity>
User identity for the EmailInput node or EmailServer configurable service.

-n ims::<security identity>
The IMS Connect security identity specified on an IMS node.

-n cics::<security_identity>
The CICS security identity specified on a CICSRequest node.

-n sftp::<security_identity>
The SFTP security identity used on a File node.

-n cd::<security_identity>
The Connect:Direct security identity used on the CD nodes. cd&colon.&colon.default is the default security identity used by the nodes.

-n wxs::<security_identity>
The WebSphere eXtreme Scale security identity used by the WebSphere eXtreme Scale configurable service.

-n brokerKeystore&colon.&colon.password
The keystore password used by the integration node.

-n brokerTruststore&colon.&colon.password
The truststore password used by the integration node.

-n brokerTruststore&colon.&colon.keypass&colon.&colon.encKey
The private key password used by the integration node.

-n httpproxy::HTTPPROXY or -n httpproxy::<proxy server>
The HTTP proxy security credentials used for request nodes, connectors and services in the integration node.

-n salesforce::<security identity>
The Salesforce server security identity specified on a Salesforce node.

-n loopback::<security identity>
The LoopBack connector security identity specified on a LoopBackRequest node.

-n rest::<security identity>
The REST security identity specified on a REST request node.

-n kafka::KAFKA::<server name>
The Kafka security identity used for Kafka nodes deployed to an Integration server.

By default, this command processes with the integration node running, but the operational changes do not take effect until the integration server, or servers, using the <resource> are restarted.
Use the -f option to force a check that the integration node <integrationNodeName> is stopped before this command is allowed to run, thereby ensuring that the changes take effect for all integration servers as soon as the integration node is next started. However, using this option means that the integration node has to be stopped before this command can be run.

BIP8130
Integration server: <insert_1> - <insert_2>2
Severity
0 : Information

BIP8131
MessageFlow: <insert_1>1
Severity
0 : Information

BIP8132
<insert_1> 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_1>
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_1>.
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_1>.
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_1>.
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_1> : operating system return code <insert_2>.
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_1> 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 execute the command.
Severity
20 : Error
Explanation
The userId that the command is being run under must have the required authority execute the command.
Response
Check that the user has the required authority to execute the command.

BIP8140
Unable to find service userid <insert_1> in component <insert_2>.
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_1> in component <insert_2>.
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_2> to <insert_3>. (error <insert_1>)
Severity
20 : Error
Explanation
Directory <insert_2> is required to have <insert_3> 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_1>. (error <insert_2>)
Severity
20 : Error
Explanation
Directory <insert_1> 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
Integration server process IDs <insert_1> were forced to terminate.
Severity
0 : Information
Explanation
The integration node was shutdown forcibly, this caused integration server 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 the configuration of an integration node. Syntax: changebroker [l=userLilPath] [g=configurationChangeTimeout] [k=internalConfigurationTimeout] [x=userExitPath] [e=activeUserExits] [s=adminSecurity] [d=MQService] [f=functionLevel] [b=cachePolicy] [r=cachePortRange]
Severity
10 : Warning
Explanation
Command options:
'l=userLilPath' the directory from which the integration node searches for user-supplied libraries.
'g=configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'k=internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'C=CCSID' the default coded character set ID for the integration node.
'x=userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server 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 integration node. The default state can be overridden at the integration server or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified, and no library is found to provide that user exit when the integration server starts, a BIP8860 message is written to the system log and the integration server fails to start. The separator character for the list is ':'.
's=adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'.
'f=functionLevel' the effective function level of the integration node, such as '7.0.0.1', '7.0.0.2', or 'all'
'b=cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'r=cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.

BIP8149
This command changes a component's trace options. Syntax (1): changetrace (u=yes | t=yes | (n=on | n=off)) ,e=executionGroupName [[,k=application] [,y=library] ,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 that user trace options are to be modified (use only with the e parameter)
't=yes' indicates that service trace options are to be modified
'n=on' indicates that trace node is active (use only with the e parameter)
'n=off' indicates that trace node is inactive (use only with the e parameter)
'b=yes' indicates that service trace options for the agent subcomponent of the specified component are to be modified
'e=executionGroupName' specifies the integration server name
'k=application' specifies the application name
'y=library' specifies the library name
'f=messageFlow' specifies the message flow name
'l=level' specifies the trace level: 'none', 'normal' or 'debug'
'm=mode' specifies the trace mode: 'safe', 'fast' or 'temp'
'c=size' specifies the trace size in kilobytes
'r=yes' specifies that the log is reset
Certain conditions apply to these optional parameters. Check the online documentation for more information.

BIP8150
Displays trace settings. Syntax (1): reporttrace (u=yes | t=yes | n=yes) ,e=executionGroupName [[,k=application] [,y=library] ,f=messageFlow] Syntax (2): reporttrace t=yes ,b=yes
Severity
10 : Warning
Explanation
Command options:
'u=yes' indicates user trace (use only with flag 'e')
't=yes' indicates service trace
'n=yes' indicates trace node settings (use only with flag 'e')
'b=yes' denotes components other than integration servers
'e=executionGroupName' integration server name
'k=application' specifies the application name
'y=library' specifies the library name
'f=messageFlow' message flow name.

BIP8151
Lists the properties of an integration node. Syntax: list [e=egName [k=applicationName] [y=libraryName]] [r=recursive] [d=detailLevel]
Severity
10 : Warning
Explanation
Command Options
'e=egName' list deployed objects configured for an integration server.
'k=applicationName' list deployed objects configured for an application.
'y=libraryName' list deployed objects configured for a library.
'r=recursive' display information on subcomponents.
'd=detailLevel' control how much information to display. Valid values are: 0 = display minimal information 1 = display one-line summary per object (default) 2 = display detailed information

BIP8152
Stops a component. Syntax: stopcomponent [i=yes]
Severity
10 : Warning
Explanation
Command Options:
'i=yes' Stop the component immediately

BIP8153
Migrated database tables for integration node <insert_1>1
Severity
0 : Information

BIP8154
An error occurred while locking the registry file <insert_1> : <insert_2>.
Severity
20 : Error
Explanation
The program cannot continue, because of an internal error.
Response
Contact your IBM Integration Bus administrator.

BIP8155
Migrates database tables for an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsimigratetables integrationNodeName [-i serviceUserId] [-a servicePassword]


Command options
'integrationNodeName' name of the integration node whose tables are to be migrated
'-i' the userid that the integration node service should run under
'-a' the password for the integration node service userid.

BIP8156
Integration node database being migrated is in an inconsistent state
Severity
20 : Error
Explanation
The integration node database being migrated is in an inconsistent state. ClientId's referenced in tables can not be found in the BCLIENTUSER table.
Response
Restore your integration node database tables to a known good state, then try migrating the tables again.

BIP8157
Unable to create WebSphere MQ channel <insert_1> on queue manager <insert_2>.
Severity
20 : Error
Explanation
This command attempted to create a WebSphere MQ channel, but was unable to do so.
Response
Locate and resolve the problem, and retry the command.

BIP8158
Invalid format for command.
Severity
20 : Error
Explanation
The string <insert_1> contained no valid formatted command.
Response
Consult the user manual and correct your errors.

BIP8159
Unknown parameter <insert_1>.
Severity
20 : Error
Explanation
The parameter <insert_1> 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_1> is unknown.
Severity
20 : Error
Explanation
The verb <insert_1> 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_1>.
Severity
20 : Error
Explanation
You opened a quoted text at <insert_1>, 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_1>.
Severity
20 : Error
Explanation
The message repository database name <insert_1> 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_1> was not set up correctly, or has been deleted. Check that the message repository database name has been correctly set up as an ODBC system data source that has been configured for the correct database.

BIP8168
The userid and/or password are not authorized for connection to the message repository database <insert_1>.
Severity
20 : Error
Explanation
The message repository database name <insert_1> 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_1>.
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_1>.
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_1>.
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_1>.
Severity
20 : Error
Explanation
The error code <insert_2> was detected.
Response
Check that you have access rights to the export file.

BIP8177
Failed to open import file <insert_1>.
Severity
20 : Error
Explanation
There was a failure opening the import file <insert_1>.
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_1> 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 resource name <insert_1> has userID <insert_2>.
Severity
0 : Information

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_2>) and SQL state (<insert_3>) 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_1>, 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_1> already exists in this repository.
Response
Delete the message set and retry the command.

BIP8186
The message set <insert_1> with level <insert_2> does not exist in the message repository.
Severity
20 : Error
Explanation
The message set <insert_1> with level <insert_2> is referenced, but it does not exist in the message repository.
Response
Correct the problem and retry the command.

BIP8187
Statistics <insert_1> collection for flow <insert_2> in integration server <insert_3> is <insert_4>. Settings: ThreadDataLevel: <insert_5>, NodeDataLevel: <insert_6>, OutputFormat: <insert_7>, AccountingOrigin: <insert_8>.
Severity
0 : Information

BIP8188
Invalid message set level.
Severity
20 : Error
Explanation
The level <insert_1> for message set <insert_2> is invalid.
Response
Correct the message set level and retry the command.

BIP8189
Changes an integration node's statistics options.
Severity
10 : Warning
Explanation
Syntax:
mqsichangeflowstats integrationNodeName (-a | -s) (-e integrationServerName | -g) ([-k application] [-y staticLibrary] -f messageFlow | -j) [-c control] [-t threadData] [-n nodeData] [-r] [-o outputFormat] [-b accountingOrigin]

Command Options:
'integrationNodeName' name of the integration node.
'-a' indicates archival of statistics.
'-s' indicates snapshot publishing.
'-e integrationServerName' integration server name.
'-g' indicates all integration servers.
'-k application' application name
'-y staticLibrary' static library name
'-f messageFlow' message flow name.
'-j' indicates all message flows.
'-c control' starts or 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, that is, deletes all previous records currently held.
'-o outputFormat' specifies the output format: values allowed are 'usertrace', 'xml', 'json' or (on z/OS only) 'smf'. The default is 'usertrace'.
'-b accountingOrigin' indicates using accounting origin to segregate the statistics.

BIP8190
Displays statistics settings.
Severity
10 : Warning
Explanation
Syntax:
mqsireportflowstats integrationNodeName ( -a | -s | -a -s ) ( -e integrationServerName | -g ) ([-k application] [-y staticLibrary] -f messageFlow | -j )

Command Options
'integrationNodeName' name of the integration node
'-a' indicates archival of statistics
'-s' indicates snapshot publishing
'-e integrationServerName' integration server name
'-g' indicates all integration servers
'-k application' application name
'-y staticLibrary' static library name
'-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=integration_server_name | ,g=yes ) ([,k=Application] [,y=Library] ,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, that is, deletes all previous records currently held.
's' indicates Snapshot publishing.
'e' Integration server name.
'g' indicates all integration servers.
'k' Application name.
'y' Library name.
'f' Message Flow name.
'j' indicates all Message Flows.
'c' starts or 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=integration_server_name | ,g=yes ) ([,k=Application] [,y=Library] ,f=MessageFlow | ,j=yes )
Severity
10 : Warning
Explanation
Command Options
'a' indicates Archival of statistics.
's' indicates Snapshot publishing.
'e' Integration server name.
'g' indicates all integration servers.
'k' Application name.
'y' Library name.
'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 integrationNodeName | -e integrationServerName | -s | -t | -r) ) )


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 integrationNodeName' The operation references the specified integration node.
'-e integrationServerName' The operation references the specified integration server.
'-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 integrationNodeName | -e integrationServerName | -s | -t | -r) )


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 integrationNodeName' The operation references the specified integration node
'-e integrationServerName' The operation references the specified integration server
'-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 integrationNodeName | -e integrationServerName | -s | -t | -r]


Command Options:
'-g groupName' ACLs referencing the specified group
'-u userName' ACLs referencing the specified user
'-b integrationNodeName' ACLs referencing the specified integration node
'-e integrationServerName' ACLs referencing the specified integration server
'-s' ACLs referencing the subscriptions table
'-t' ACLs referencing the publish/subscribe topology
'-r' ACLs referencing the root topic.

BIP8196
Statistics <insert_1> settings for flow <insert_2> in integration server <insert_3> - On?: <insert_4>, ThreadDataLevel: <insert_5>, NodeDataLevel: <insert_6>, OutputFormat: <insert_7>.
Severity
0 : Information

BIP8197
Unable to set the security attributes for WebSphere MQ Queue <insert_2> on Queue Manager <insert_1>.
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_3> 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_1> was unsuccessful and returned WebSphere MQ code <insert_2>.
Severity
20 : Error
Explanation
This command attempts to start the required WebSphere MQ Queue Manager.
Response
Ensure that the required Queue Manager, <insert_1> 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_1>.
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_2> is available and that the user issuing this command is a member of the mqm group.

BIP8200
Resource <insert_1> does not exist.
Severity
20 : Error
Explanation
An attempt was made to delete a resource called <insert_1> that does not exist.
Response
Update the command with the correct name for the resource to be deleted, and reissue the command. If the resource name is correct, the resource has already been deleted and no other action is required.

BIP8201
The password you entered, <insert_1> for resource <insert_2> and userId <insert_3> is correct.
Severity
0 : Information

BIP8202
The Resource name <insert_1> has SSHIdentity <insert_2>
Severity
0 : Information

BIP8203
The passPhrase you entered, <insert_1> for resource <insert_2> with userId <insert_3> and SSHIdentity <insert_4> is correct
Severity
0 : Information

BIP8204
The password you entered, <insert_1> for resource <insert_2> and userId <insert_3> is incorrect
Severity
10 : Warning

BIP8205
The passPhrase you entered, <insert_1> for resource <insert_2> with userId <insert_3> and SSHIdentity <insert_4> is incorrect
Severity
10 : Warning

BIP8206
The Integration node is not running and may not have been restarted since the last change made by the mqsisetdbparms command.
Severity
0 : Information

BIP8207
The Integration node has not been restarted since the last change made to this datasource by the mqsisetdbparms command.
Severity
0 : Information

BIP8208
No resources found with resource name <insert_1>.
Severity
10 : Warning

BIP8209
The resource name <insert_1> has client identity <insert_2>.
Severity
0 : Information

BIP8210
The resource name <insert_1> has client secret <insert_2>.
Severity
0 : Information

BIP8211
User Name Server failed to retrieve <insert_2> <insert_1> entries from the native security subsystem.
Severity
0 : Information
Explanation
The User Name Server failed to read a number (<insert_2>) of user or group (<insert_1>) entries, and will continue processing using an incomplete cache of user/group information.
Response
Check trace entries for an indication of which <insert_1> entries could not be read.

BIP8212
User Name Server failed to retrieve more than <insert_2> <insert_1> entries from the native security subsystem.
Severity
10 : Warning
Explanation
The User Name Server failed to read more than a given number (<insert_2>) of user or group (<insert_1>) entries, and will not attempt to read any further <insert_1> entries. Processing will continue using an incomplete cache of user/group information.
Response
Check trace entries for an indication of which <insert_1> entries could not be read.

BIP8213
User Name Server failed to retrieve any <insert_1> entries from the native security subsystem.
Severity
20 : Error
Explanation
The User Name Server did not read any user or group (<insert_1>) entries, and will not continue processing.
Response
Check trace entries for an indication of why no <insert_1> entries were found.

BIP8214
The resource name <insert_1> has API key <insert_2>.
Severity
0 : Information

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_1> is not readable by this version of the product. The file was written by version <insert_2>, while this product is version <insert_3>.
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_1> 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_1> from queue manager <insert_2>.
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 an integration node or a component from a previous version of the product is still running. Stop all processes associated with the queue manager, and retry the command.

BIP8219
Service binary path for component <insert_1> changed to <insert_2>; previous value was <insert_3>.
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_1> could not be changed to <insert_2>: error <insert_4>. Current value remains <insert_3>.
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_1>: <insert_2> (Version <insert_4>) - <insert_3>3
Severity
0 : Information

BIP8222
Unable to find ODBCINI file <insert_1>.
Severity
20 : Error
Explanation
Could not find the ODBCINI file <insert_1>, which is specified by the ODBCINI environment variable.
Response
Ensure that the ODBCINI environment variable points to an existing ODBCINI file.

BIP8223
User <insert_2> is not a member of group <insert_1>.
Severity
20 : Error
Explanation
User <insert_2> is not a member of group <insert_1> and therefore does not have the privilege to use this command.
Response
Talk to your system administrator to obtain the membership of group <insert_1> or login as a user who does have the membership.

BIP8224
Internal error while trying to load library <insert_1>.
Severity
20 : Error
Explanation
Could not load an internal library <insert_1>.
Response
Ensure that the library is correctly installed.

BIP8225
<insert_1> 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_1>.
Severity
0 : Information

BIP8227
Force data in the integration node's security cache to be reloaded.
mqsireloadsecurity integrationNodeSpec [-u useridList] [-w timeoutSecs]
Severity
0 : Information
Explanation
Command Options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-u useridList' A colon-separated list of user IDs that are to have their security cache entries reloaded. If no list is supplied, all entries in the cache are reloaded.
'-w timeoutSecs' maximum number of seconds to wait for message flows to start (default is 60)
Response
No action.

BIP8228
Force data in the integration node's security cache to be reloaded. Syntax: reloadsecurity [u=userid list] [w=timeoutValue]
Severity
0 : Information
Explanation
Command Options:
'u=userid list' A colon-separated list of user IDs that are to have their security cache entries reloaded. If no list is supplied, all entries in the cache are reloaded.
'w=timeoutValue' Value in seconds to wait for the integration node to reply to the deploy request.
Response
No action.

BIP8229
The command completed with the following number of warnings: <insert_1>.
Severity
0 : Information

BIP8230
mqsisetdbparms cannot be used to set a user name and password for the integration node data source.
Severity
10 : Warning
Explanation
An attempt was made to set a user name and password for the integration node ODBC data source name. This is not allowed. You may set user names and passwords only for ODBC data sources other than the integration node data source.

BIP8231
Argument <insert_2> is not a valid integer value for flag <insert_1>.
Severity
20 : Error
Explanation
Ensure that the argument used is a valid integer, and in the permitted range (from <insert_3> to <insert_4>) or the special value <insert_5>.
Response
Correct the value and reissue the command.

BIP8232
The operation cannot be performed for multi-instance integration node <insert_1>, or an instance of that integration node, because of directory permission settings for the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The integration node instance needs to reference the shared workpath, but the directory permissions do not allow this action.
Response
Use a different -e value, or consult your system administrator for possible causes of this error.

BIP8233
Multi-instance integration node <insert_1>, or an instance of that integration node, cannot be created because the shared workpath <insert_2> does not exist.
Severity
20 : Error
Explanation
The integration node instance needs to reference the shared workpath that cannot be accessed, or cannot be located.
Response
Check that the server hosting the shared workpath is accessible.
If the shared workpath does not exist, use the mqsicreatebroker command to create the integration node and the shared workpath.

BIP8234
Unable to add integration node instance <insert_1>, because the integration node has not yet been created using the mqsicreatebroker command.
Severity
20 : Error
Explanation
An integration node instance cannot be added if the integration node has not yet been created.
Response
Create the integration node using the mqsicreatebroker command, then rerun the mqsiaddbrokerinstance command.

BIP8235
The multi-instance integration node <insert_1> cannot be deleted because its associated queue manager <insert_2> is in standby mode.
The multi-instance queue manager is running elsewhere, and there might also be an active integration node instance.
Severity
0 : Information
Explanation
The multi-instance integration node needs to connect to the active multi-instance queue manager, in order to delete any WebSphere MQ resources owned by the integration node.
An active integration node instance might also be running elsewhere and this integration node instance must also be stopped before the multi-instance integration node can be successully deleted.
Response
Stop the active multi-instance queue manager that is running elsewhere before reissuing this command.
You should delete all integration node instances, by using the mqsiremovebrokerinstance command, before deleting the multi-instance integration node.

BIP8236
A standby instance of integration node <insert_1> has been started against the standby queue manager <insert_2>. The active integration node instance and active queue manager instance are running elsewhere.
Severity
0 : Information
Explanation
The multi-instance integration node has started in standby mode. The integration node will not become active until the current active integration node instance and active queue manager instance end, or are stopped.
Response
No action required.

BIP8237
The multi-instance integration node <insert_1> detected that another integration node instance is active, when it attempted to obtain access to the <insert_2> integration node table. The DataFlowEngine process stops and restarts to maintain integrity of the integration node data.
Severity
20 : Error
Explanation
Only one instance of a multi-instance integration node can be active at any time. This integration node instance has detected a problem, because another instance appears to be active at the same time.
This error might have been caused by a network problem connecting to the server where the shared data for the integration node is stored.
Response
The integration node instance should stop and restart automatically and the problem be resolved without the need for manual intervention.
If the problem persists, investigate the network shared server and all connections to it.
Ensure that all the mount points are still valid from client servers that host the integration node instances.
Investigate any problems with the WebSphere MQ multi-instance queue managers associated with this integration node.

BIP8238
The multi-instance integration node <insert_1> has detected that another integration node instance is active. This integration node instance stops and restarts to maintain integrity of the integration node data.
Severity
20 : Error
Explanation
Only one instance of a multi-instance integration node can be active at any time. This integration node instance has detected a problem because another instance appears to be active at the same time.
This error might have been caused by a network problem connecting to the server where the shared data for the integration node is stored.
Response
The integration node instance should stop and restart automatically and the problem be resolved without the need for manual intervention.
If the problem persists, investigate the network shared server and all connections to it.
Ensure that all the mount points are still valid from client servers that host the integration node instances.
Investigate any problems with the WebSphere MQ multi-instance queue managers associated with this integration node.

BIP8239
Integration Bus has detected that the WebSphere MQ multi-instance Queue Manager <insert_1> is in Standby mode.
Severity
20 : Error
Explanation
The WebSphere MQ multi-instance queue manager must be active when creating or starting an integration node.
Response
Stop the active WebSphere MQ multi-instance queue manager where it is currently running, to allow the local instance of the queue manager to become active, and rerun this command.

BIP8240
Integration node <insert_1> was configured as multi-instance, but cannot be deleted because it does not exist in the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The command has attempted to delete a multi-instance integration node from the shared workpath, which has been already been deleted.
Response
Check that the server hosting the shared workpath is accessible, or
Retry the operation, using the mqsiremovebrokerinstance command to remove the local multi-instance integration node defintion.

BIP8241
A multi-instance integration node <insert_1> cannot be deleted because it does not exist in the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The multi-instance integration node cannot be found in the shared workpath, or it has not yet been created using the mqsicreatebroker command.
Response
Check that the server hosting the shared workpath is accessible.

BIP8242
An integration node instance <insert_1> cannot be deleted because it does not exist in the local workpath <insert_2>.
Severity
20 : Error
Explanation
The integration node instance has already been removed, or was never created originally.
Response
No user action required.

BIP8243
The integration node <insert_1> cannot be deleted with the removebrokerinstance command because it is not a multi-instance integration node.
Severity
20 : Error
Explanation
The integration node was not created as multi-instance using the mqsiaddbrokerinstance command.
The integration node can only be deleted with the mqsideletebroker command.
Response
Check that the server hosting the shared workpath is accessible.

BIP8244
An integration node instance <insert_1> cannot be started because it does not exist in the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The integration node instance cannot be started because a multi-instance integration node has been deleted from the shared workpath.
Response
Recreate the multi-instance integration node on another server using the same shared work path.

BIP8245
A multi-instance integration node <insert_1> cannot be started because the shared workpath <insert_2> does not exist.
Severity
20 : Error
Explanation
The integration node instance needs to reference the shared workpath that cannot be found, or has not yet been created using the mqsicreatebroker command.
Response
Check that the server hosting the shared workpath is accessible.
If the shared workpath does not exist, use the mqsicreatebroker command to create the integration node and the shared workpath.

BIP8246
Cannot create the WebSphere MQ service for integration node <insert_1> and queue manager <insert_2>.
The WebSphere MQ return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when creating the WebSphere MQ service to stop and start an integration node.
Response
Check the reason for the WebSphere MQ error and take any suggested corrective action.

BIP8247
Cannot alter the WebSphere MQ service for integration node <insert_1> and queue manager <insert_2>.
The WebSphere MQ return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when altering the WebSphere MQ service to stop and start an integration node.
Response
Check the reason for the WebSphere MQ error and take any suggested corrective action.

BIP8248
Cannot delete the WebSphere MQ service for integration node <insert_1> and queue manager <insert_2>.
The WebSphere MQ return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when deleting the WebSphere MQ services to stop and start an integration node.
Response
Check the reason for the WebSphere MQ error and take any suggested corrective action.

BIP8249
Cannot start the WebSphere MQ service for integration node <insert_1> and queue manager <insert_2>.
The WebSphere MQ return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when starting the WebSphere MQ service for an integration node.
Response
Check the reason for the WebSphere MQ error and take any suggested corrective action.

BIP8250
Cannot stop the MQSeries services for integration node <insert_1> and queue manager <insert_2>.
The MQSeries return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when stopping the MQSeries service for an integration node.
Response
Check the reason for the MQSeries error and take any suggested corrective action.

BIP8251
Service dependencies for component <insert_1> changed to <insert_2>; the previous value was <insert_3>.
Severity
10 : Warning
Explanation
The service dependencies for this component were incorrect for this installation. The dependencies have been updated to the correct value.
Response
None.

BIP8252
Service dependencies for component <insert_1> cannot be changed to <insert_2>: error <insert_4>. The current value remains at <insert_3>.
Severity
20 : Error
Explanation
The service dependencies for this component are incorrect for this installation. The command attempted to change these dependencies, but was unsuccessful.
Response
Determine why the change was unsuccessful, correct the problem, and re-run the command.

BIP8253
The service <insert_1> is not running and is required in order to create Integration Nodes. Start the service and retry this command.
Severity
20 : Error
Explanation
The service <insert_1> is not running and is required in order to create Integration Nodes.
Response
Start the service and retry this command.

BIP8254
The Java API framework could not create an instance of <insert_1>.
Severity
20 : Error
Explanation
An internal JNI error has occurred during object instantiation due to NumberFormatException.
Response
Ensure that the field causing this error is correct. Contact your IBM support center if the issue persists.

BIP8255
The multi-instance integration node <insert_1> is in standby mode on queue manager <insert_2>.
Severity
20 : Error
Explanation
This integration node is in standby mode; the command you issued cannot be processed when an integration node is in standby mode.
Response
The command should be issued on the active multi-instance integration node <insert_1>.

BIP8256
The multi-instance integration node <insert_1> on queue manager <insert_2> is stopped.
Severity
20 : Error
Explanation
This multi-instance integration node is stopped; the command you issued cannot be processed when an integration node is stopped.
Response
The command should be issued on the active multi-instance integration node <insert_1>.

BIP8257
The multi-instance integration node <insert_1> is stopped. It will be started as a WebSphere MQ service by queue manager <insert_2>.
Severity
20 : Error
Explanation
This multi-instance integration node is stopped; the command you issued cannot be processed when an integration node is stopped.
Response
The command should be issued on the active multi-instance integration node <insert_1>.

BIP8258
The integration node <insert_1> is stopped. It will be started as a WebSphere MQ service by queue manager <insert_2>.
Severity
20 : Error
Explanation
This integration node is stopped; the command you issued cannot be processed when an integration node is stopped.
A previous command has been issued to stop this integration node, or this integration node has never been started.
Response
This integration node can be changed, or deleted.

BIP8259
The JMS provider <insert_1> does not support delivery delay.
Severity
20 : Error
Explanation
The JMS provider <insert_1> does not support delivery delay but an attempt was made to set a delivery delay. The failure message from the JMS Provider was <insert_2>.
Response
Do not attempt to set a delivery delay for this JMS provider.

BIP8260
The userId you entered, <insert_1> for resource <insert_2> with userId <insert_3> is incorrect
Severity
10 : Warning

BIP8261
The SSHIdentity you entered, <insert_1> for resource <insert_2> with userId <insert_3> and SSHIdentity <insert_4> is incorrect
Severity
10 : Warning

BIP8264
Integration node <insert_1> is a local integration node instance. The associated multi-instance integration node does not exist in the shared workpath <insert_2>. The multi-instance integration node has been deleted from the shared workpath.
Severity
20 : Error
Explanation
The multi-instance integration node no longer exists because it has already been deleted from the shared workpath.
An integration node instance exists only locally. You cannot delete an integration node instance with the mqsideletebroker command.
Response
You must use the mqsiremovebrokerinstance command to remove the local integration node instance.

BIP8265
Cannot stop the MQSeries services for integration node <insert_1> and queue manager <insert_2>.
The MQSeries return code is <insert_3>.
Severity
20 : Error
Explanation
There was an error when stopping the MQSeries service for an integration node.
Response
Check the reason for the MQSeries error and take any suggested corrective action.

BIP8266
The data for multi-instance integration node <insert_1>, or an instance of that integration node, cannot be found in the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The shared workpath exists, but the command cannot find the integration node data in the expected subdirectories.
Response
If the integration node is missing, run the mqsicreatebroker or mqsiaddbrokerinstance command as appropriate.

BIP8267
Warning, there might be problems with datasource <insert_1>. See the preceding messages for more information.
Severity
10 : Warning
Explanation
The mqsicvp command has completed, but some potential problems have been identified with the datasource provided.

BIP8268
Datasource <insert_1> is compatible with datasource <insert_2>.
Severity
0 : Information
Explanation
The capability offered by these two datasources is basically the same.
Response
These datasources can be used together within message processing nodes that support interaction with multiple discrete datasources through ESQL; for example, Database, Compute and Filter nodes.

BIP8269
Datasource <insert_1> is not compatible with datasource <insert_2>.
Severity
10 : Warning
Explanation
The capability offered by these two datasources is not the same. These datasources cannot be used together within message processing nodes that support interaction with multiple discrete datasources through ESQL; for example, Database, Compute and Filter nodes.

BIP8270
Connected to Datasource <insert_1> as user <insert_2>. The datasource platform is <insert_4>, version <insert_5>.
Severity
0 : Information

BIP8271
Connected to secondary datasource <insert_1> as user <insert_2>. The datasource platform is <insert_4>, version <insert_5>. This datasource can now be compared to the primary datasource.
Severity
0 : Information

BIP8272
Datasource <insert_1> has not been associated with integration node <insert_2>.
Severity
20 : Error
Explanation
This invocation of the mqsicvp command requires that the datasource name has been associated with the integration node, using the mqsisetdbparms command.
Response
Check that this datasource has been associated with the integration node.

BIP8273
The following datatypes and functions are not natively supported by datasource <insert_1> using this ODBC driver: Unsupported datatypes: <insert_2> Unsupported functions: <insert_3>
Severity
0 : Information
Response
Examine the specific datatypes and functions not supported natively by this datasource using this ODBC driver.
When using these datatypes and functions within ESQL, the associated data processing is done within IBM Integration Bus rather than being processed by the database provider.

Note that "functions" within this message can refer to functions or predicates.

BIP8274
Warning. The following datatypes and functions are not natively supported by datasource <insert_1> using this ODBC driver: Unsupported datatypes: <insert_2> Unsupported functions: <insert_3>
Severity
10 : Warning
Explanation
Some problems have been identified with the datasource provided.
Response
Examine the specific datatypes and functions not supported natively by this datasource using this ODBC driver.
Use of these datatypes and functions within ESQL can cause problems, and should be avoided.

Note that "functions" within this message can refer to functions or predicates.

BIP8275
Verification passed for User Datasource <insert_1>.
Severity
0 : Information

BIP8276
One or more problems have been detected with User Datasource <insert_1>. Use the mqsicvp command against this datasource (by running: mqsicvp integrationNodeName -n <insert_1>) to obtain further information on these problems, together with any limitations that these problems could cause.
Severity
10 : Warning

BIP8277
The configurable service name that you specified, <insert_1>, starts with a digit or contains characters that are not valid.
Severity
20 : Error
Explanation
The configurable service name must not start with a digit and must only contain characters that are supported by the platform on which the command is being processed.
Response
Correct the configurable service name and reissue the command.

BIP8278
The static library is not available.
Severity
20 : Error
Explanation
The static library cannot be found. The static library might have been deleted by the Integration Toolkit or a custom integration application.
If the specified library is a shared library, this command cannot be used with the shared library.
Response
Use the Integration Toolkit or a custom integration application to check that the static library exists.

BIP8279
The application is not available.
Severity
20 : Error
Explanation
The application could not be found; it may have been deleted by the Integration Toolkit or a custom integration application.
Response
Use the Integration Toolkit or a custom integration application to see if the application exists.

BIP8280
Successfully initialized interface to the NT security domain, <insert_1>.
Severity
0 : Information
Explanation
A component of IBM Integration Bus has successfully initialized the NT security domain.
Response
No user action required.

BIP8281
Error in initializing the NT security domain&colon. return code <insert_1>; subsystem error code <insert_2>.
Severity
20 : Error
Explanation
A component of IBM Integration Bus 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_1> to the NT security domain with return code <insert_2>.
Severity
20 : Error
Explanation
A component of IBM Integration Bus 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 integration node. 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_1>.
Severity
20 : Error
Explanation
A component of IBM Integration Bus 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_1>.
Severity
20 : Error
Explanation
A component of IBM Integration Bus 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_1>.
Severity
20 : Error
Explanation
A component of IBM Integration Bus 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.

BIP8287
This command displays the content of response messages.
Severity
10 : Warning
Explanation
Syntax:
mqsiexplain [messageNumber]

Command Options:
'messageNumber' is the message for which the command will show the details. This value can be the number itself, or it can be preceded by BIP.

BIP8288
Unable to read ODBCINI file <insert_1>. Check that this file exists, and that the integration node user ID has permission to read and write the file.
Severity
10 : Warning
Explanation
The integration node cannot read the file <insert_1>, which is specified by the ODBCINI environment variable.
Response
Ensure that the ODBCINI environment variable points to an existing file, and that the integration node user ID has permission to read and write the file.

BIP8289
Unable to read ODBCSYSINI file in specified directory <insert_1>. Check that this file exists, and that the integration node user ID has permission to read the file.
Severity
10 : Warning
Explanation
The integration node cannot read the odbcinst.ini file in directory <insert_1>, which is specified by the ODBCSYSINI environment variable.
Response
Ensure that the ODBCSYSINI environment variable, if specified, points to a directory that contains the odbcinst.ini file, and that the integration node user ID has permission to read the file.

BIP8290
Verification passed for the ODBC environment.
Severity
0 : Information

BIP8291
The IE02_PATH environment variable is not set.
Severity
10 : Warning
Explanation
The integration node cannot find the IE02_PATH environment variable, which is required by the IBM Integration Bus ODBC Database Extender.
Response
Ensure that the IE02_PATH environment variable is set, and reissue the command.

BIP8292
<insert_1> User data sources were not verified, because they do not have mqsisetdbparms credentials.
Severity
0 : Information
Explanation
<insert_1> User data source stanzas are listed in the ODBCINI file, but were not verified by this command, because they have not been associated with the integration node.
Response
Associate the data sources with the integration node explicitly by using the mqsisetdbparms command, then reissue this command.

BIP8293
Unable to read ODBCUOINI file <insert_1>. Check that this file exists, and that the integration node user ID has permission to read and write the file.
Severity
10 : Warning
Explanation
The integration node cannot read the file <insert_1>, which is specified by the ODBCUOINI environment variable.
Response
Ensure that the ODBCUOINI environment variable points to an existing file, and that the integration node user ID has permission to read and write the file. This file is required by the IBM Integration Bus ODBC Database Extender.

BIP8294
ODBC environment verification was skipped because the ODBCINI environment variable is not set.
Severity
0 : Information
Response
Check that the ODBCINI environment variable is set.

BIP8295
ODBC environment variables have not been set, or are invalid.
Severity
20 : Error
Explanation
The integration node cannot verify user data sources because the ODBCINI, ODBCSYSINI, or IE02_PATH environment variables are not set, or because the ODBCINI environment variable is set incorrectly.
Response
Ensure that the ODBCINI environment variable is set, and see earlier warning messages for further details.

BIP8296
The ODBCSYSINI environment variable is not set.
Severity
10 : Warning
Explanation
The integration node cannot find the ODBCSYSINI environment variable, which is required by the IBM Integration Bus ODBC Database Extender.
Response
Ensure that the ODBCSYSINI environment variable is set, and reissue the command.

BIP8297
<insert_1> file <insert_2> is empty.
Severity
10 : Warning
Explanation
The integration node has detected that the file <insert_2>, which is specified by the <insert_1> environment variable, has zero size.
Response
Ensure that the <insert_1> environment variable points to a valid and complete file.

BIP8299
User <insert_1> from security resource name <insert_2> will be used for the connection to datasource <insert_3>.
Severity
0 : Information
Explanation
The user ID and password to be used for the ODBC connection to datasource <insert_3> have been obtained from the security resource <insert_2>. This association was created using the mqsisetdbparms command.

BIP8300
The configuration checks have finished, but one or more checks encountered a warning.
Severity
10 : Warning
Response
Review the command output for preceding warning messages.

If you are not able to understand the warning message then try running mqsicvp with the verbose (-v) option to find out where any invalid property was loaded from.
You can also use the mqsiexplain command to find out more details about the message.

BIP8301
The configuration checks have finished successfully, but one or more checks encountered an error.
Severity
20 : Error
Response
Review the command output for preceding error and warning messages.

If you are not able to understand the error or warning message then try running mqsicvp with the verbose (-v) option to find out where any invalid property was loaded from.
You can also use the mqsiexplain command to find out more details about the message.

BIP8302
Performing <insert_1> configuration checks for integration node <insert_2>.
Severity
0 : Information

BIP8303
Checking configuration for integration server <insert_1>:
Severity
0 : Information

BIP8304
Checking configuration for component <insert_1>:
Severity
0 : Information

BIP8305
HTTPSConnector for integration server <insert_1>:
Severity
0 : Information

BIP8310
No keystore file configured at the <insert_1> level.
Severity
0 : Information
Explanation
There is no keystore file configured at the indicated configuration level.
Response
If you expect there to be a keystore configured then check the configured value using mqsireportproperties and if no value is set then configure one using mqsichangeproperties.

BIP8311
KeyStore <insert_1> of type <insert_2> with password <insert_3> configured.
Severity
0 : Information
Explanation
There is a keystore file that is configured for this component, with the indicated name and type. The keystore will be opened using the specified password. The password might be a resource name to lookup a password set using mqsisetdbparms.
Response
If the configuration is not as expected then review the configured values using mqsireportproperties and change them using mqsichangeproperties.

BIP8312
No truststore file configured at the <insert_1> level.
Severity
0 : Information
Explanation
There is no truststore file configured at the indicated configuration level.
Response
If you expect there to be a truststore configured then check the configured value using mqsireportproperties and if no value is set then configure one using mqsichangeproperties.

BIP8313
TrustStore <insert_1> of type <insert_2> with password <insert_3> configured.
Severity
0 : Information
Explanation
There is a truststore file that is configured for this component, with the indicated name and type. The truststore will be opened using the specified password. The password might be a resource name to lookup a password set using mqsisetdbparms.
Response
If the configuration is not as expected then review the configured values using mqsireportproperties and change them using mqsichangeproperties.

BIP8314
Unable to find mqsisetdbparms entry for <insert_1>.
Severity
20 : Error
Explanation
The mqsicvp command was unable to find the indicated resource name in the values set using mqsisetdbparms.
Response
If the resource name is supposed to refer to an mqsisetdbparms entry then review the configuration using mqsireportdbparms and set it using mqsisetdbparms.

BIP8315
Found password in mqsisetdbparms for entry <insert_1>.
Severity
0 : Information
Explanation
The mqsicvp command was able to find the indicated resource name in the values set using mqsisetdbparms.
Response
No user action required.

BIP8316
Unsupported store type <insert_1>.
Severity
20 : Error
Explanation
A keystore or truststore type was configured which is not recognized by mqsicvp. This might still be a valid JSSE store type, but mqsicvp is unable to verify the configuration and contents of the store.
Response
If the store type is valid then review the configuration manually and ensure the appropriate settings are configured.

BIP8317
Store file <insert_1> does not exist.
Severity
20 : Error
Explanation
The mqsicvp command was unable to find the configured keystore or truststore.
Response
Review the configuration and ensure that the keystore or truststore exists and is readable by mqsicvp.

BIP8318
Unable to read store file <insert_1>.
Severity
20 : Error
Explanation
The mqsicvp command was unable to read the configured keystore or truststore.
Response
Review the configuration and ensure that the keystore or truststore exists and is readable by mqsicvp.

BIP8319
KeyStore configured which contains 0 keys.
Severity
20 : Error
Explanation
The configured keystore was found and opened, but contained 0 keys.
Having 0 keys makes the keystore unusable for opening a server socket with the HTTPSConnector.
Response
Review the mqsicvp command output and check that the configured keystore is correct and it contains the expected keys and certificates.

BIP8320
Unable to open store file <insert_1> with unsupported store provider <insert_2>.
Severity
20 : Error
Explanation
The mqsicvp command was unable to open the keystore or truststore file using the configured provider because the provider name was not recognized.
Response
Review the configured provider using mqsireportproperties to report on the configured value and then use mqsichangeproperties to update the value.

BIP8321
Unable to open store file <insert_1> with error message <insert_2>.
Severity
20 : Error
Explanation
The mqsicvp command was unable to open the keystore or truststore file because of the error message.
Response
Review the error message and take any corrective action.
If the error message points at a configuration problem then review the configured properties using mqsireportproperties to report on the configured values and then use mqsichangeproperties to update the values.

BIP8322
TrustStore <insert_1> contains <insert_2> certificates.
Severity
0 : Information
Explanation
The mqsicvp command was able to open the configured truststore and found that it contains <insert_2> certificates.
Response
If the number of certificates is not as expected then review the truststore file and manually check that it contains the required certificates.
Running mqsicvp with the -v option will list the certificates in the truststore

BIP8323
KeyStore <insert_1> contains <insert_2> keys and <insert_3> certificates.
Severity
0 : Information
Explanation
The mqsicvp command was able to open the configured keystore and it contained <insert_2> keys and <insert_3> certificates.
Response
If the number of keys or certificates is not as expected then review the keystore file and manually check that it contains the required keys and certificates.
Running mqsicvp with the -v option will list the keys in the keystore.

BIP8324
KeyStore configured which contains 0 keys.
Severity
10 : Warning
Explanation
The configured keystore was found and opened, but contained 0 keys.
This might not be an error if the keystore is used exclusively for trust purposes, e.g. for use by the CICSRequest node when client auth is disabled on the CICS region.
Having 0 keys will make the keystore unusable for opening a server socket, e.g. with the TCPIPServerInput node, or if the keystore is used by a client which connects to a server which has client authentication enabled, eg. with the HTTPRequest node.
Response
Review the mqsicvp command output and check that the configured keystore is correct and that it contains the expected keys and certificates.

BIP8325
[<insert_5>] Certificate entry: Alias <insert_1>; Subject <insert_2>; Expires <insert_3>; Chain length <insert_4>.
Severity
0 : Information
Explanation
A certificate was found in the truststore which has the indicated details.
Response
Review the certificate details to ensure the certificate is an expected one.

BIP8326
[<insert_3>] Unknown store entry: Alias <insert_1>; Type <insert_2>.
Severity
10 : Warning
Explanation
An entry with the indicated alias was found in the store file which was of a type unrecognized by mqsicvp. The only recongized type is an X509 certificate.
Response
Manually review the store file contents and ensure that the certificate entry is valid and suitable for its intended purpose.

BIP8327
[<insert_4>] Key entry: Alias <insert_1>; Subject <insert_2>; Expires <insert_3>.
Severity
0 : Information
Explanation
A private key was found in the keystore which had a linked certificate with the indicated details.
Response
Review the certificate details for the private key to ensure the key is an expected one.

BIP8328
[<insert_2>] Unable to read key with alias <insert_1> using the keystore password. Error message <insert_3>.
Severity
10 : Warning
Explanation
The mqsicvp command was unable to read the private key with the indicated alias using the password which was used to open the keystore.
This might not be an error if the keystore is not used for inbound HTTPS connections or if all of the keys are protected by the same key password.
An error will be reported if the keystore is configured for use by an HTTPSConnector, but mqsicvp is unable to tell if the keystore is used by a flow during runtime and either specifies a key password or does not use the key.
Response
Manually review the keystore uses and ensure they are suitable
.If an 'UnrecoverableKeyException' exception is seen during runtime then this could be an indication that the password for this key needs to be the same as the other keys in the keystore or a key password needs to be configured.

BIP8329
Store file location <insert_1> is not absolute. Successful resolution of relative paths might be unreliable.
Severity
10 : Warning
Explanation
The configured keystore or truststore file location is not an absolute path. This relies on the correct workpath for resolution.
The user might find that this file location is resolved by the mqsicvp command and not by the running integration node, or vice versa, so inconsistent errors might be reported.
Response
Correct the path configuration so that it is an absolute path.

BIP8330
Configured password is not an mqsisetdbparms key. Unable to use it.
Severity
20 : Error
Explanation
The mqsicvp command was unable to use the value configured for the password property as a resource name to lookup the values set using mqsisetdbparms as it does not conform to the relevant naming convention.
Response
Correct the value configured for the password to be a valid resource name and then set a password for the resource name using mqsisetdbparms.

BIP8331
Unable to find mqsisetdbparms entry for <insert_1>. Attempting to use the value directly.
Severity
10 : Warning
Explanation
The mqsicvp command was unable to find the indicated resource name in the values set using mqsisetdbparms.
It will now try and use the value as the password directly.
Response
If the resource name is supposed to refer to an mqsisetdbparms entry then review the configuration using mqsireportdbparms and set it using mqsisetdbparms.
It is not recommended to use a plain password which is not a resource name and is not supported in all configurations. mqsicvp will raise an error if the use of a plain password is not supported.

BIP8332
Configured password is not an mqsisetdbparms key. Attempting to use the value directly.
Severity
10 : Warning
Explanation
The mqsicvp command was unable to use the value configured for the password property as a resource name to lookup the values set using mqsisetdbparms as it does not conform to the relevant naming convention.
It will now try and use the value as the password directly.
Response
If the value configured is supposed to refer to an mqsisetdbparms entry then review the configuration using mqsireportdbparms and set it using mqsisetdbparms.
It is not recommended to use a plain password which is not a resource name and is not supported in all configurations. mqsicvp will raise an error if the use of a plain password is not supported.

BIP8333
Property <insert_1> loaded from location <insert_2> with value <insert_3>.
Severity
0 : Information
Explanation
The named configuration property was loaded from the indicated location and it contained the reported value.
Response
If the configuration value is not the expected one, then review the configured values and the precedence order with which the property is loaded.

BIP8334
Property <insert_1> loaded with default value <insert_2>.
Severity
0 : Information
Explanation
The named configuration property was loaded with its default value as this was not overridden by any of the locations from which it could be loaded.
Response
If the configuration value is not the expected one, then review the configured values and the precedence order with which the property is loaded.

BIP8335
Algorithm <insert_1> configured for the HTTPSConnector. Using default <insert_2>.
Severity
0 : Information
Explanation
The named key algorithm is configured for the HTTPSConnector. If this is the default value and has not been overridden then this is indicated.
Response
If this is not the expected configuration value then review the configured value using mqsireportproperties and change it using mqsichangeproperties.

BIP8336
SSL Protocol <insert_1> configured for the HTTPSConnector. Using default <insert_2>.
Severity
0 : Information
Explanation
The named SSL protocol is configured for the HTTPSConnector. If this is the default value and has not been overridden then this is indicated.
Response
If this is not the expected configuration value then review the configured value using mqsireportproperties and change it using mqsichangeproperties.

BIP8337
SSL Protocol <insert_1> is not recognized. Error message <insert_2>.
Severity
20 : Error
Explanation
The value configured for the SSL protocol is not recognized as a valid value. The error message shows the error returned when validating this value.
Response
Correct the configuration value to be a supported SSL protocol using mqsichangeproperties.

BIP8338
Algorithm <insert_1> is not recognized. Error message <insert_2>.
Severity
20 : Error
Explanation
The value configured for the key algorithm is not recognized as a valid value. The error message shows the error returned when validating this value.
Response
Correct the configuration value to be a supported key algorithm using mqsichangeproperties.

BIP8339
ClientAuth is enabled for the HTTPSConnector through value <insert_1>. Using default <insert_2>.
Severity
0 : Information
Explanation
Client authentication (clientAuth) is enabled for the HTTPSConnector through the configuration value. This requires all clients to present a valid key which is validated using the truststore configured for the HTTPSConnector. This configuration is not the default setting.
Response
Ensure that the truststore contains the required certificates to validate any keys presented by valid clients.

BIP8340
ClientAuth is enabled, but not required, for the HTTPSConnector through value <insert_1>. Using default <insert_2>.
Severity
0 : Information
Explanation
Client authentication (clientAuth) is requested for the HTTPSConnector through the configuration value. All clients will be asked to provide a valid key, and if a key is supplied it has to be valid, but presentation of a key is not required for a successful connection.
Any key which is presented will be validated using the truststore configured for the HTTPSConnector. This configuration is not the default setting.
Response
Ensure that the truststore contains the required certificates to validate any keys which are presented.
Be aware that this setting allows clients to connect whose identity cannot be verified, as well as those where the identity can be verified. Ensure that this behavior is required.

BIP8341
ClientAuth is disabled for the HTTPSConnector through value <insert_1>. Using default <insert_2>.
Severity
0 : Information
Explanation
Client authentication (clientAuth) is disabled for the HTTPSConnector through the configuration value. Clients will not be asked to provide a valid key. If clientAuth is disabled through the default value and has not been overridden then this is indicated.
Response
Be aware that this setting allows all clients to connect without any identity verification taking place. Ensure that this behavior is required.

BIP8342
Configuration value <insert_1> for property <insert_2> is not recognized.
Severity
10 : Warning
Explanation
The value configured for the named property is not a recognized value. This normally means that the default value will be applied instead and further messages will indicate what value is applied.
Response
Review the configured value using mqsireportproperties and correct it using mqsichangeproperties.

BIP8343
No restricted cipher suite list is configured for the HTTPSConnector through value <insert_1>. All available ciphers enabled. Using default <insert_2>.
Severity
0 : Information
Explanation
The HTTPSConnector configuration setting 'ciphers' is set to <insert_1>, where an empty value is the default. This configuration means that all available cipher suites are available for use, which includes some suites that are potentially vulnerable to attacks.
Response
Ensure that this configuration is the required one, and that a restricted cipher suite (or list of cipher suites) is not required. You can review the configuration using mqsireportproperties and correct it using mqsichangeproperties.

BIP8344
Restricted cipher suite list <insert_1> configured and enabled for HTTPSConnector through value <insert_2>. Using default <insert_3>.
Severity
0 : Information
Explanation
A restricted cipher suite list has been enabled for the HTTPSConnector. Only ciphers named in the enabled list are available for clients to use. This configuration is not the default setting.
The enabled list may be a subset of the configured value if some of the ciphers in the configured value are not recognized. An additional error message will be logged if a cipher suite is not a valid name.
Response
Ensure that this is the desired configuration and that all required cipher suites are in the enabled list.

BIP8345
Cipher suite <insert_1> is not valid.
Severity
20 : Error
Explanation
The named cipher suite is not a valid cipher suite available to the integration node.
Response
Review the value configured for the cipher suite and correct its name if necessary or examine why the named cipher is not available.
The list of available ciphers can be reported by running mqsicvp with the -v option.

BIP8346
<insert_1> Cipher suites available.
Severity
0 : Information
Explanation
The are <insert_1> ciphers suites available to the integration node using the configured JSSE security files.
Response
No user action required.

BIP8347
[<insert_2>] Available cipher suite: <insert_1>.
Severity
0 : Information
Explanation
The named cipher suite is available for use.
Response
No user action required.

BIP8348
Propagate client certificate is enabled through value <insert_1>. Using default <insert_2>.
Severity
0 : Information
Explanation
The HTTPSConnector is enabled to propagate any client certificates which are presented to the message flow if a suitable security profile is configured. If client certificate propagation is enabled through the default value and has not been overridden then this is indicated.
Response
Ensure that a suitable security profile is configured to propagate the client certificate to the message flow if this is required.

BIP8349
Propagate client certificate is disabled through value <insert_1>. Using default <insert_2>.
Severity
0 : Information
Explanation
The HTTPSConnector will not propagate any client certificates which are presented to the message flow. If client certificate propagation is disabled through the default value and has not been overridden then this is indicated.
Response
If client certificates are required in the message flow for further validation or filtering then this property will need to be enabled and a suitable security profile configured on the flow.

BIP8350
No keyAlias configured for the HTTPSConnector.
Severity
0 : Information
Explanation
The HTTPSConnector has not been configured with a key alias to point at the required key in the keystore. The HTTPSConnector will retrieve one of the keys in the keystore and use that for any incoming connections.
Response
This configuration is the default setting and is suitable if there is only one key in the keystore. If there is more than one key in the keystore then it is indeterminate which key the HTTPSConnector will choose to use.

BIP8351
KeyAlias <insert_1> configured for the HTTPSConnector with keyPass <insert_2>.
Severity
0 : Information
Explanation
The HTTPSConnector has been configured with a key alias to point at the required key in the keystore.
Response
Review the key alias to ensure it is the correct one.

BIP8352
Unable to find alias <insert_1> in keystore <insert_2>.
Severity
20 : Error
Explanation
The HTTPSConnector was unable to find the configured alias in the configured keystore.
Response
Review the alias and keystore configuration and ensure the correct alias is specified and corresponds to a key in the keystore.

BIP8353
Unable to read key with alias <insert_1> using keyPass <insert_2>. Error message <insert_3>.
Severity
20 : Error
Explanation
The HTTPSConnector was unable to read the key for the configured alias using the specified keyPass because of the displayed error message.
Response
Review the error message and take any corrective action.
If the error message points at a configuration problem then review the configured properties using mqsireportproperties to report on the configured values and then use mqsichangeproperties to update the values.

BIP8354
Unable to read key with alias <insert_1> using keystore password. Error message <insert_2>.
Severity
20 : Error
Explanation
The HTTPSConnector was unable to read the key for the configured alias using the keystore password because of the displayed error message.
Response
Review the error message and take any corrective action.
If the error message points at a configuration problem then review the configured properties using mqsireportproperties to report on the configured values and then use mqsichangeproperties to update the values.

BIP8355
No keyPass configured for the HTTPSConnector so using keystore password.
Severity
0 : Information
Explanation
The HTTPSConnector is configured to load a specific key via the keyAlias property and there is no keyPass value configured. The integration node will use the keystore password to load the key from the keystore.
This configuration is not an error unless the key is protected by a key password which is different from the keystore password. Further mqsicvp output messages will indicate if the key can be loaded successfully.
Response
Review the mqsicvp output for warning or error messages.

BIP8356
Key alias <insert_1> found. Details: Subject <insert_2>; Expires <insert_3>.
Severity
0 : Information
Explanation
The HTTPSConnector is configured to load a specific key via the keyAlias property and this was loaded successfully from the keystore.
The private key which was loaded has a linked certificate with the indicated details.
Response
Review the key details and ensure that this is the desired key.

BIP8357
Key alias <insert_1> found, but unknown type <insert_2>.
Severity
10 : Warning
Explanation
The HTTPSConnector is configured to load a specific key via the keyAlias property and this was found but its linked certificate is of a type unrecognized by mqsicvp. The only recognized type is an X509 certificate.
Response
Manually review the keystore contents and ensure that the linked certificate entry is valid and suitable for its intended purpose.

BIP8358
No keystore configured for the HTTPSConnector. A default '.keystore' file in the user's home directory will be used.
Severity
10 : Warning
Explanation
The HTTPSConnector is available but there is no keystore file configured. The HTTPSConnector will default at runtime to use a file called '.keystore' in the user's home directory.
This configuration is not a problem if the HTTPSConnector is not going to be used because there are no flows deployed with HTTPInput, SOAPInput, or SCAInput nodes accepting HTTPS connections.
If there are nodes using the HTTPSConnector deployed there should be a keystore file configured and the default '.keystore' file should not be relied upon.
Response
Review the deployed message flows to see if any HTTPInput, SOAPInput, or SCAInput nodes are configured to accept HTTPS connections.

BIP8359
The <insert_1> is enabled through property <insert_2> with value <insert_3>. Using default <insert_4>.
Severity
0 : Information
Explanation
The named component is enabled through the specified configuration property due to the indicated configuration value. If this component is enabled through the default value and has not been overridden then this is indicated.
Response
Review the component and ensure that enabled is the desired status.

BIP8360
The <insert_1> is disabled through property <insert_2> with value <insert_3>. Using default <insert_4>.
Severity
0 : Information
Explanation
The named component is disabled through the specified configuration property due to the indicated configuration value. If this component is disabled through the default value and has not been overridden then this is indicated.
Response
Review the component and ensure that disabled is the desired status.
If the httplistener HTTPSConnector is disabled and input nodes are deployed and configured to accept HTTPS connections and to use the integration node wide listener then this represents an error.

BIP8361
SSL session cache is configured with size <insert_1> and timeout <insert_2> seconds. Using defaults <insert_3>.
Severity
0 : Information
Explanation
The SSL session cache is configured with the noted size and timeout. If the SSL session cache is configured through the default values and they have not been overridden then this is indicated.
Response
Review the session cache size and timeout. It is not normally necessary to alter these values.
Note that the timeout is not an active timeout and entries are not expired automatically but are only expired when next used.

BIP8362
No keystore password configured at the <insert_1> level(s).
Severity
0 : Information
Explanation
There is no keystore password configured at the indicated configuration levels.
This might be an error if there is a configured keystore file and it cannot be opened using any default password which is applied, and a message flow node is configured to use the keystore.
mqsicvp will issue further messages if it detects any of the following: 1) The default password is to be used. 2) A configured keystore file cannot be opened using the default password. 3) A runtime situation where the absence of the password will lead to an error can be detected.
Response
Review the mqsicvp output for warning or error messages.

BIP8363
No truststore password configured at the <insert_1> level(s).
Severity
0 : Information
Explanation
There is no truststore password configured at the indicated configuration levels.
This may be an error if there is a configured truststore file and it cannot be opened using any default password which is applied, and a message flow node is configured to use the truststore.
mqsicvp will issue further messages if it detects any of the following: 1) The default password is to be used. 2) A configured truststore file cannot be opened using the default password. 3) A runtime situation where the absence of the password will lead to an error can be detected.
Response
Review the mqsicvp output for warning or error messages.

BIP8364
Setting JVM system property <insert_1> with value <insert_2>.
Severity
0 : Information
Explanation
The named JVM system property will be set during integration server startup to the reported value.
Response
No user action required.

BIP8365
The following nodes, node types and functionality can use the SSL keystore and truststore defined below:
Severity
0 : Information
Explanation
HTTP(Async)Request, SOAP(Async)Request, SCARequest, CICSRequest,
IMSRequest, JavaCompute, JMS Nodes, TCPIP Nodes, WSRR Nodes.
JDBC, external WXS grids.

BIP8366
Incomplete keystore or truststore configuration. Store file or password missing.
Severity
10 : Warning
Explanation
There is an incomplete configuration of either a keystore or truststore file and matching password.
This configuration is only an error if the keystore or truststore is used during message flow runtime through a node configured to use SSL connections.
Response
Review the deployed message flows to see if any nodes are configured for SSL connections.

BIP8367
The <insert_1> nodes will use the embedded listener HTTPSConnector keystore and truststore defined below.
Severity
0 : Information
Explanation
The indicated node types are configured to use the integration server embedded listener and will use the keystore and truststore defined for the integration server level HTTPSConnector if instances of these nodes are configured to accept HTTPS connections.
Response
Review the node types and ensure that, if you wish any nodes of this type to accept HTTPS connections, that you want them to use the integration server embedded listener.

BIP8368
Unable to find mqsisetdbparms entry for <insert_1> in default configuration.
Severity
0 : Information
Explanation
The mqsicvp command was unable to find the indicated resource name in the values set using mqsisetdbparms. This configuration is not an error because a matching store file is not defined and the resource-name matches that of the default configuration.
This message is output if the configuration matches the default configuration where a known resource name is configured for a keystore or truststore password property which has not been set using mqsisetdbparms and the appropriate keystore or truststore file has not been defined.
If a keystore or truststore file had been defined and the resource name could not be found then this would represent an error and mqsicvp will output a different message.
Response
No user action required.

BIP8369
The <insert_1> nodes will use the integration node wide listener.
Severity
0 : Information
Explanation
The indicated node types are configured to use the integration node wide listener and will use the keystore and truststore defined for the httplistener HTTPSConnector if instances of these nodes are configured to accept HTTPS connections.
Response
Review the node types and ensure that, if you wish any nodes of this type to accept HTTPS connections, that you want them to use the integration node wide listener.

BIP8370
Unable to recover all keys in the keystore using the keystore password. Error message <insert_1>.
Severity
20 : Error
Explanation
The mqsicvp command was unable to recover all of the keys in the keystore using the keystore password because of the displayed error message.
Parts of the product require that all of the keys in a keystore can be recovered using the keystore password and this error message is output when this situation can be detected.
Response
Correct the keystore so that all keys are protected by the keystore password.

BIP8371
This command can not be run against an instance of an integration node which is in stopped or standby state with an active instance running elsewhere.
Severity
20 : Error
Explanation
The command is prohibited from running to protect the configuration and state of the active instance of the integration node.
Response
Reissue this command for the active instance of this integration node, or wait until no other instance is active elsewhere.

BIP8372
The mqsichangebluemixreporting command changes the state and configuration for Bluemix startup, usage, and logging services.
Severity
10 : Warning
Explanation
Syntax:
mqsichangebluemixreporting integrationNodeName [-e integrationServerName | -g]
([-c usage state] [-j apihost] [-k apikey] [-m mins] [-n groupname] [-y proxy])
([-l logging state] [-s secs] [-r region -o organization -a space -u user -p pwd [-d]]
[-x host[:_port] -i tenantSpaceID -t tenantLoggingID])

Command options:
'integrationNodeName' specifies the integration node name.
'-e integrationServerName' specifies the name of the integration server to be changed.
'-g' indicates that all existing integration servers will be changed.
' ' if neither '-e' nor '-g' are specified, the default for integration servers that have never been set using -e or -g will be changed.
Following flags for startup and usage reporting services:
'-c' enables or disables reporting. Valid values are 'active' or 'inactive'.
'-j' sets the apihost.
'-k' sets the apikey.
'-m intMinutes' optionally sets the interval in minutes, with a minimum value of 10 and a maximum value of 1440. The default value is 15.
'-n' optionally sets the group name.
'-y' optionally sets a proxy location, in the form hostname':'port.
Following flags for logging services:
'-l' enables or disables logging. Valid values are 'active' or 'inactive'.
'-s intSeconds' sets the logging interval in seconds, with a minimum value of 1 and a maximum value of 300. The default value is 60.
'-r' sets the Bluemix region. Valid values are 'us-south', 'eu-gb', or Bluemix API endpoint, eg, https://api.ng.bluemix.net.
'-o' sets the Bluemix organization.
'-a' sets the Bluemix space.
'-u' sets the Bluemix username.
'-p' sets the Bluemix password.
'-d' indicates publish current IIB Kibana dashboard for Bluemix logging services.
Following flags are alternatives to r,o,a,u,p flags, to manually set up logging services:
'-x' sets the host name and optionally ':' port number for logging services.
'-i' sets the Bluemix space identifier for logging services.
'-t' sets the Bluemix logging token for logging services.
Example 1
Set startup and usage reporting service active for all servers
'mqsichangebluemixreporting TESTNODE -g -c active -j https://hybridconnect-api.ng.bluemix.net -k 9ec2e5c5-c2d1-3257-b2cd-c271ec26d427'
Example 2
Set logging service active and publish the IIB Kibana 4 dashboard for all servers
'mqsichangebluemixreporting TESTNODE -g -l active -r eu-gb -o a.user@comp.com -a dev -u a.user@comp.com -p pass -d'

BIP8373
The mqsireportbluemixreporting command reports the current configuration for the Bluemix startup, usage and logging services.
Severity
10 : Warning
Explanation
Syntax:
mqsireportbluemixreporting integrationNodeName [-e integrationServerName | -g]

Command options:
'integrationNodeName' specifies the integration node name.
'-e integrationServerName' indicates that only the named integration server will be reported.
'-g' indicates that all integration servers will be reported.
' ' if neither '-e' nor '-g' are specified, all integration servers are reported.

BIP8374
Server = <insert_1>, Bluemix startup and usage reporting mode = <insert_2>, apihost = <insert_3>, apikey = <insert_4>, report interval minutes = <insert_5>, group name = <insert_6>, proxy = <insert_7>
Severity
0 : Information

BIP8375
Server = <insert_1>, Bluemix logging mode = <insert_2>, host = <insert_3>, port = <insert_4>, report interval seconds = <insert_5>, tenantSpaceId = <insert_6>, tenantLogToken = <insert_7>
Severity
0 : Information

BIP8376
Dashboard files are prepared for manual import into Kibana from <insert_1>.
Severity
0 : Information

BIP8377
Current dashboard has been loaded into Kibana for Bluemix logging space <insert_1>. Dashboard files are also prepared for manual import into Kibana from <insert_2>.
Severity
0 : Information

BIP8378
Server = <insert_1>, Bluemix tenant SpaceId and LogToken obtained for region = <insert_2>, organization = <insert_3>, space = <insert_4>, user = <insert_5>
Severity
0 : Information

BIP8401
Message associated with internal message number <insert_1> was not found: data supplied <insert_2>
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 integration node. Note that MAX_CLIENT_READ_THREADS is 0 by default and should not be specified as non-zero in normal operation. mqsichangeproperties integrationNodename -e integrationServerName -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 integration node. Note that PING_TIMEOUT_MULTIPLE=3 is the default and usually does not require overriding. To change the value, use the following mqsichangeproperties integrationNodename -e integrationServerName -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 integration node. Note that PING_MIN is 100 by default and usually does not require overriding. mqsichangeproperties integrationNodename -e integrationServerName -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 integration node. 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 integrationNodename -e integrationServerName -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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxMessageSize -v value An integration node 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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n messageSizeExtraAllowance -v value An integration node restart is required to activate the changes.

BIP8410
An exception occurred 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_1>.
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_1>.
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 occurred when attempting to log an event. The type of event is <insert_1>, the severity of the event is <insert_2>, and the exception is <insert_3>.
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 integration node received an invalid or unexpected control message. The type of the message 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.

BIP8414
Authentication on a connection between integration nodes failed. This is non-fatal but must be repaired in order to allow routing between integration nodes. The name of the attempted connection between integration nodes is <insert_1>, and the InauthenticBrokerException that was caught is <insert_2>.
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 connection between integration nodes timed out after too many unsuccessful attempts. This is non-fatal but must be repaired in order to allow routing between integration nodes. The name of the attempted connection between integration nodes 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.

BIP8416
The integration node caught an exception while attempting to update its connection status between integration nodes using a local SemaphoreClient. The attempted update 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.

BIP8417
A VMX message received on a connection between integration nodes had a bad MDT. The associated connection will be closed. The MsgDistException which triggered the event is <insert_1>, and the name of the connection between integration nodes 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.

BIP8418
An error was encountered while parsing the BROKERS_THRU_SOCKS parameter. This is non-fatal but will disable any socksified connections between integration nodes. The caught 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.

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_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.

BIP8420
A request was made to add an initial state processor to a topic which was already assigned a processor. The requested processor is ignored. The full name of the requested topic 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; contact your IBM support center.

BIP8421
A SecurityGeneralException was encountered while processing a message received on a connection. The caught 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.

BIP8422
A client attempted to publish on a topic for which it was not authorized. The message was dropped. The client connection is <insert_1>, and the topic is <insert_2>.
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_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.

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_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 by attempting to reconnect the client

BIP8425
The integration node configuration of MAX_BROKER_QUEUE_SIZE is between 0 and 500 bytes. This size is rather small and might cause many integration node to integration node messages to be discarded. The value of MAX_BROKER_QUEUE_SIZE is <insert_1>.
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 object, and retry the request. The MAX_BROKER_QUEUE_SIZE is used for queuing Real-time transport integration node to integration node messages. mqsichangeproperties integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxBrokerQueueSize -v value

BIP8426
The integration node configuration of MAX_CLIENT_QUEUE_SIZE is between 0 and 500 bytes. This is rather small and may cause many client-integration node messages to be discarded. The value of MAX_CLIENT_QUEUE_SIZE is <insert_1>.
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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxClientQueueSize -v value An integration node restart is required to activate the change

BIP8427
ENABLE_SOCKS is true but BROKERS_THRU_SOCKS is zero-length. Processing will continue but no integration node-integration node 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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n enableThruSocks -v value

BIP8428
ENABLE_SOCKS is true but SOCKS_HOST is zero-length. Processing will continue but connections between integration nodes will not be SOCKS-enabled. 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 integrationNodename -e integrationServerName -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_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.

BIP8430
An exception occurred while closing the segment reader portion of a non-blocking threaded socket segment. 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.

BIP8431
An exception occurred while closing the segment writer portion of a non-blocking threaded socket segment. 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.

BIP8432
An exception occurred while deregistering the client associated with a non-blocking threaded socket segment. 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.

BIP8433
An exception occurred while closing the socket associated with a non-blocking threaded socket segment. 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.

BIP8437
An integration node connection on socket <insert_1> established with name <insert_2> received a topology message from integration node <insert_3>.
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 an integration node connection on socket <insert_1> failed with exception <insert_2>.
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 integration node connections.
Response
Investigate whether an application is incorrectly using the socket that has been configured for integration node 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_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.

BIP8441
An exception occurred during reset after a lock error. 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.

BIP8442
A service failure was reported to BrokerControl. The service reference is <insert_1>, the reason for the failure is <insert_2>, and the exception is <insert_3>.
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_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.

BIP8444
An exception was caught while changing the state of an internal ControlHandler. Processing continues. 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.

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 integration node. The exception is <insert_1>.
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_1> bytes in <insert_2> 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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxClientQueueSize -v value or mqsichangeproperties integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxBrokerQueueSize -v value MAX_CLIENT_QUEUE_SIZE is used for integration node to Client messages. MAX_BROKER_QUEUE_SIZE is used for integration node to integration node messages.

BIP8447
Client <<insert_1>> tried to publish a <insert_2> byte message, exceeding the limit <insert_3>.
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 integrationNodename -e integrationServerName -o DynamicSubscriptionEngine -n maxMessageSize -v value An integration node restart is required to activate the change parameter.

BIP8448
A connection between integration nodes with <insert_1> 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 integration node is the sole parameter of this event.
Response
This message is for information only, to indicate disconnection of an integration node due to its inactivity. Reconnection will be attempted automatically.

BIP8449
A connection between integration nodes with <insert_1> has been disconnected due to Exception <insert_2>.
Severity
10 : Warning
Explanation
An exception occurred while processing messages on a connection between integration nodes. 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 an integration node due to an exception. Reconnection will be attempted automatically.

BIP8450
Server-to-server authentication failed because id of other integration node <insert_1> was not in the server principals directory.
Severity
10 : Warning
Explanation
The would-be partner integration node authenticated with an id that was not known to this integration node.
Response
Ensure that the id <insert_1> is known to the integration node

BIP8451
Client-to-server authentication failed because id of the client <insert_1> 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 integration node.
Response
Ensure that the client <insert_1> is known to the integration node

BIP8452
<insert_1> is not allowed in BROKER_AUTH_PROTOCOLS.
Severity
20 : Error
Explanation
We don't allow the use of protocol <insert_1> for integration node to integration node authentication.
Response
This is an internal error and you should contact your IBM support center.

BIP8453
A connection on socket <insert_1> with integration node <insert_2> has been established
Severity
0 : Information
Explanation
A connection on socket <insert_1> with integration node <insert_2> has been established and authenticated with id=<insert_2> and protocol=<insert_3>.
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_1>1
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 operation will be retried using the address of the adapter bound to the hostname of the computer.
Response
This message is for information only.

BIP8461
Integration node <insert_1> has an incorrectly configured integration node topology: <insert_2> with <insert_3> neighbors: <insert_4>.
Severity
10 : Warning
Explanation
An integration node topology has been incorrectly configured.
Response
This is an internal error. Contact your IBM support center.

BIP8462
Disthub caught a fatal exception [<insert_1>].
Severity
30 : Severe error
Explanation
A fatal exception occurred within integration node <insert_1>. The behavior of the integration node is now undefined and further use will produce unpredictable results
Response
Restart the integration node, if the problem persists you should contact your IBM support center

BIP8463
Integration node <insert_1> detected a cycle in its own topology configuration.
Severity
20 : Error
Explanation
The integration node found a cycle in the topology. This will result in publications looping around integration nodes in the topology.
Response
This is an internal error. Contact your IBM support center.

BIP8464
Error while trying to open the <insert_1> port between integration nodes.
Severity
20 : Error
Explanation
While trying to open port <insert_1> 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 integration node property in the Integration Toolkit to a port that isn't in use. This can also be done programmatically using a custom integration application.

BIP8465
A connection from client at <insert_1> 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.

BIP8466
Successful command completion. Created a high availability or multi-instance integration node (with a queue manager).
Severity
0 : Information

BIP8467
Successful command completion. Created a high availability or multi-instance integration node (without a queue manager).
Severity
0 : Information

BIP8500
The value supplied for parameter <insert_1> contains an invalid value <insert_2>. Allowed values for <insert_1> are: <insert_3>.
Severity
10 : Warning
Explanation
An invalid value was specified for the supplied parameter. Valid values for this parameter are: <insert_3>.
Response
Ensure that the value specified for parameter <insert_1> is valid.

BIP8501
The supplied HTTP request body is missing the following required fields: <insert_1>.
Severity
10 : Warning
Explanation
The supplied HTTP request body is missing the following required fields: <insert_1>.
Response
Ensure that the request body contains the fields <insert_1>.

BIP8502
The value supplied for parameter <insert_1> contains an invalid value <insert_2>. The value must be a non-negative integer.
Severity
10 : Warning
Explanation
An invalid value was specified for the supplied parameter. The value must be greater than or equal to 0.
Response
Ensure that the value specified for parameter <insert_1> is valid.

BIP8503
The user name associated with role <insert_1> does not have permission to view the integration server <insert_2>.
Severity
10 : Warning
Explanation
The user with role <insert_1> does not have the required permissions to view integration server <insert_2>.
Response
Check that the user's role <insert_1> has the required permissions to access integration server <insert_2>.

BIP8504
The user name associated with role <insert_1> does not have the permission on the integration server <insert_2> that is required to view the data capture store <insert_3>
Severity
10 : Warning
Explanation
The user with role <insert_1> does not have the required permissions on integration server <insert_2> to view data capture store <insert_3>.
Response
Check that the user's role <insert_1> has the required permissions to access integration server <insert_2>.

BIP8505
Changing the password of the default user is not allowed.
Severity
10 : Warning
Explanation
Administration security is disabled, and an attempt was made to change the password of the default user. Changing the password or role of the default user is not permitted.
Response
None.

BIP8506
User does not have permission to view object <insert_1>.
Severity
10 : Warning
Explanation
The user does not have the required permissions to view object <insert_1>.
Response
Check that the user's role has the required permissions to access object <insert_1>.

BIP8507
The value supplied in the http body for field <insert_1> contains an invalid value <insert_2>. Allowed values for <insert_1> are: <insert_3>.
Severity
10 : Warning
Explanation
An invalid value was specified for the supplied field. Valid values for this field are: <insert_3>.
Response
Ensure that the value specified for field <insert_1> is valid.

BIP8508
The parameters <insert_1> supplied in the HTTP body is not allowed. Allowed parameters are: <insert_2>.
Severity
10 : Warning
Explanation
Invalid parameters specified. Valid parameters are: <insert_2>.
Response
Ensure that the specified parameters are valid.

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
IBM Integration Bus 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 IBM Integration Bus 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 IBM Integration Bus 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.

BIP8608
Unable to create WebSphere MQ Topic <insert_1> on Queue Manager <insert_2>. Return code: <insert_3>.
Severity
20 : Error
Explanation
This command attempts to create a WebSphere MQ Topic but was unable to do so.
Response
Locate and resolve the problem and retry the command.

BIP8609
Unable to delete WebSphere MQ object <insert_1> from queue manager <insert_2>.
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 any applications are connected to your integration node, you may need to stop these as well.

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 IBM Integration Bus.
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
IBM Integration Bus setup or uninstallation is already running.
Severity
10 : Warning
Explanation
IBM Integration Bus 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_1> 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_1> may contain additional information on the nature of the problem.
Response
Review the install/uninstall log <insert_1> to aid resolution of the problem. If the problem persists, contact your IBM support center.

BIP8615
Problem encountered stopping integration node <insert_1>. Return from wmqpsstop was <insert_2>.
Severity
10 : Warning
Explanation
The uninstall process attempted to stop an integration node named <insert_1> using wmqpsstop but encountered an error. The return code from this command was <insert_2>.
Response
Choose Retry to run the command again; this is the suggested action. If you choose Abort or Cancel the uninstall process ends. Before relaunching the uninstall process try to stop the integration node identified manually. If Ignore is available, and you choose this option, the uninstall process continues, but it is possible that the problem with wmqpsstop might cause additional errors to appear when the uninstall process attempts to delete the integration node. Additional help is available using the Help button.

BIP8616
Unable to delete integration node <insert_1>. Return Code from wmqpsdeletebroker was <insert_2>. Abort, Retry, or Ignore?
Severity
10 : Warning
Explanation
The uninstall process attempted to delete an integration node (<insert_1>) but encountered an error. The return code from wmqpsdeletebroker was <insert_2>.
Response
Choose Retry to run the command again. If you choose Abort or Cancel the uninstall process ends. Before relaunching the uninstall process try to delete the integration node identified manually. If Ignore is available, and you choose this option, the uninstall process continues, but it is possible that you will encounter additional errors later. Additional help is available using the Help button.

BIP8619
Unable to stop User Name Server. Return Code from wmqpsstop was <insert_1>. See message
Severity
10 : Warning
Explanation
The uninstall process attempted to stop the User Name Server using wmqpsstop but encountered a problem. The return code from wmqpsstop was <insert_1>.
Response
Choose Retry to run the command again. If you choose Abort or Cancel the uninstall process ends. Before relaunching the uninstall process try to stop the User Name Server manually. If Ignore is available, and you choose this option, the uninstall process continues, but it is possible that the problem with wmqpsstop might cause additional errors to appear when the uninstall process attempts to delete the User Name Server. Additional help is available using the Help button.

BIP8621
Install of <insert_1> has started
Severity
0 : Information
Explanation
The install of product <insert_1> has started. The end of the install will be signaled by BIP8622.
Response
No user action required

BIP8622
Install of <insert_1> has finished successfully
Severity
0 : Information
Explanation
Install of product <insert_1> has finished without any errors.
Response
No user action required

BIP8623
Uninstall of <insert_1> has started
Severity
0 : Information
Explanation
The uninstall of product <insert_1> has started. The end of the uninstall will be signaled by BIP8624.
Response
No user action required

BIP8624
Uninstall of <insert_1> has finished successfully
Severity
0 : Information
Explanation
Uninstall of product <insert_1> has finished without any errors.
Response
No user action required

BIP8640
symlink returned EACCES when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
Write access to the directory containing <insert_2> is denied, or one of the directories in the path prefix of <insert_2> did not allow search permission.

BIP8641
symlink returned EEXIST when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
<insert_2> already exists.

BIP8642
symlink returned EFAULT when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
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_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
An I/O error has occurred. Check the state of the file systems and retry the command. If the problem persists, contact your IBM support center.

BIP8644
symlink returned ELOOP when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
Too many symbolic links were encountered in resolving <insert_2>.

BIP8645
symlink returned ENAMETOOLONG when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
<insert_1> or <insert_2> was too long for the file system to handle.

BIP8646
symlink returned ENOENT when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
A directory component in <insert_2> does not exist or is a dangling symbolic link, or <insert_1> is the empty string.

BIP8647
symlink returned ENOMEM when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
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_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
The device containing <insert_2> path prefix has no room for the <insert_2> directory entry.

BIP8649
symlink returned ENOTDIR when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
A component used as a directory in <insert_2> is not, in fact, a directory.

BIP8650
symlink returned EPERM when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
The file system containing <insert_2> does not support the creation of symbolic links.

BIP8651
symlink returned EROFS when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
Severity
30 : Severe error
Explanation
<insert_2> is on a read-only file system.

BIP8652
symlink operation failed when attempting to create a symbolic link with target <insert_1> and link name <insert_2>.
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_1> and link name <insert_2>
Severity
0 : Information

BIP8654
Moving file system artifacts from <insert_1> to <insert_2>.
Severity
0 : Information

BIP8655
Removing <insert_1>.
Severity
0 : Information

BIP8656
Cannot remove non-empty directory <insert_1> due to unhandled file <insert_2>
Severity
10 : Warning

BIP8657
Creating directory <insert_1>
Severity
0 : Information

BIP8658
Unable to determine necessary information for migrating integration node <insert_1>, does it really exist?
Severity
20 : Error

BIP8659
Could not determine the Data Source Name for integration node <insert_1>, could be wrong version or -1 option missing with -c option.
Severity
20 : Error

BIP8660
Could not determine the Queue Manager for integration node <insert_1>, could be wrong version or -1 option missing with -c option.
Severity
20 : Error

BIP8661
Detected source version <insert_1>.<insert_2>.<insert_3>.<insert_4>4
Severity
0 : Information

BIP8662
Detected target version <insert_1>.<insert_2>.<insert_3>.<insert_4>4
Severity
0 : Information

BIP8663
The integration server <insert_1> is being migrated from 32-bit to 64-bit mode. You might need to re-compile your user defined extensions, parsers, and exits before it can be re-started.
Severity
10 : Warning
Explanation
This version of the product no longer supports 32-bit integration servers.
Response
Make sure that your user defined extensions, parsers, and exits are re-compiled in 64-bit mode, if not already available. Check that they are in a location that the integration node can access.

BIP8669
Database migration successful
Severity
0 : Information

BIP8670
Database migration started
Severity
0 : Information

BIP8671
Database migration failed
Severity
20 : Error

BIP8673
Migration of integration node <insert_1> from version <insert_2>.<insert_3>.<insert_4>.<insert_5> to version <insert_6>.<insert_7>.<insert_8>.<insert_9> failed, see previous messages for reasons.
Severity
20 : Error

BIP8676
Component <insert_1> of type <insert_2> cannot be migrated; only components of type 'Broker' can be migrated.
Severity
20 : Error
Explanation
Only integration node components can be migrated to this version of the product. Other component types that existed in previous versions are no longer used and cannot be migrated.
Response
Refer to the migration documentation.

BIP8677
Component <insert_1> was specified with a source version of <insert_2>.<insert_3>.<insert_4>.<insert_5>, whilst version <insert_6>.<insert_7>.<insert_8>.<insert_9> was detected.
Severity
10 : Warning

BIP8679
Found a 64 bit integration server: <insert_1>. Integration nodes with 64 bit integration servers 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_1> for query.
Severity
10 : Warning

BIP8683
Unable to query values under key <insert_1>.
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_1>(<insert_2>) must be redeployed to integration server <insert_3>(<insert_4>).
Severity
10 : Warning

BIP8689
The source and target version are compatible, no migration is necessary.
Severity
0 : Information

BIP8690
The registry information for the integration node <insert_1> could not be retrieved from the location specified in the environment variable $MQSI_REGISTRY. The environment variable $MQSI_REGISTRY is set to <insert_2>.
Severity
20 : Error
Explanation
$MQSI_REGISTRY is used to locate the directory that contains the definitions files for the integration node.
Response
Update the variable to point to the correct location.

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 succeeded.
Severity
0 : Information
Explanation
The migration utility did not find any configuration errors for the component.
Response
None.

BIP8702
The post-migration check failed. See previous messages for possible causes.
Severity
10 : Warning
Explanation
Configuration errors for the component were found, signifying that the component configuration is not correct. The previous messages provide details of the errors.
Response
Examine the previous messages to determine the cause of the failure. If you are migrating, you might need to undo the migration by using the different options of the mqsimigratecomponents command. If you are creating an integration node, check that the persistent store of the integration node does not contain tables from a different integration node version.

BIP8703
Column <insert_1> is missing from database table <insert_2>
Severity
30 : Severe error
Explanation
Table <insert_2> must have the correct set of columns for this component to function correctly, and column <insert_1> is missing. This could be because a migration step has not been performed, or because the table itself has become damaged.
Response
If this integration node is being started after a migration, ensure all migration steps have completed successfully. If this integration node is newly created, and the database tables were created manually by a database administrator, ensure all columns specified are correct.

BIP8704
Column <insert_1> should not be present in database table <insert_2>
Severity
30 : Severe error
Explanation
Table <insert_2> must have the correct set of columns for this component to function correctly, and an extra column <insert_1> is present. This could be because a migration step has not been performed, or because the table itself has become damaged.
Response
If this integration node is being started after a migration, ensure all migration steps have completed successfully. If this integration node 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_1> 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_1> 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 integration node is being started after a migration, ensure all migration steps have completed successfully. If this integration node 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_1> exists, but is not accessible; reason code <insert_2>.
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_1> is not accessible. This could be because the permissions have been changed, or because the queue manager itself has become damaged.
Response
If this integration node is being started after a migration, ensure all migration steps have completed successfully. If this integration node 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.

BIP8710
Starting configuration data migration for integration server <insert_1>.
Severity
0 : Information
Explanation
The configuration data is being migrated for integration server <insert_1>.
Response
None.

BIP8711
Starting configuration data migration for application <insert_1>.
Severity
0 : Information
Explanation
The configuration data is being migrated for application <insert_1>.
Response
None.

BIP8712
Starting configuration data migration for library <insert_1>.
Severity
0 : Information
Explanation
The configuration data is being migrated for library <insert_1>.
Response
None.

BIP8713
Starting configuration data migration for library <insert_1> in application <insert_2>.
Severity
0 : Information
Explanation
The configuration data is being migrated for library <insert_1> in application <insert_2>.
Response
None.

BIP8714
Migrating the contents of configuration data table <insert_1>.
Severity
0 : Information
Explanation
The contents of configuration data table <insert_1> are being migrated.
Response
None.

BIP8715
The contents of configuration data table <insert_1> have been migrated.
Severity
0 : Information
Explanation
None.
Response
None.

BIP8716
The integration node <insert_1> will now use the configuration data table(s) <insert_2>
Severity
0 : Information
Explanation
None.
Response
None.

BIP8717
The integration node <insert_1> will no longer use the configuration data table(s) <insert_2>
Severity
0 : Information
Explanation
None.
Response
None.

BIP8718
The data <insert_1> with identifier <insert_2> has been migrated from the configuration data table <insert_3> to configuration data table <insert_4>.
Severity
0 : Information
Explanation
None.
Response
None.

BIP8719
The data <insert_1> with identifier <insert_2> has been migrated from the configuration data table <insert_3> to <insert_4>.
Severity
0 : Information
Explanation
None.
Response
None.

BIP8720
The resource <insert_1> of type <insert_2> has been migrated from the configuration data table <insert_3> to <insert_4>.
Severity
0 : Information
Explanation
None.
Response
None.

BIP8721
Failed to migrate the contents of configuration data table <insert_1>.
Severity
20 : Error
Explanation
An error occurred whilst migrating the contents of configuration data table <insert_1>. See previous errors for more information.
Response
None.

BIP8722
Failed to migrate the data <insert_1> with identifier <insert_2> from the configuration data table <insert_3> to configuration data table <insert_4>.
Severity
20 : Error
Explanation
An error occurred whilst migrating the data <insert_1> with identifier <insert_2>from configuration data table <insert_3>. See previous errors for more information.
Response
None.

BIP8723
Failed to migrate the data <insert_1> with identifier <insert_2> from the configuration data table <insert_3> to <insert_4>.
Severity
20 : Error
Explanation
An error occurred whilst migrating the data <insert_1> with identifier <insert_2> from configuration data table <insert_3>. See previous errors for more information.
Response
None.

BIP8724
Failed to migrate the resource <insert_1> of type <insert_2> from the configuration data table <insert_3> to <insert_4>
Severity
20 : Error
Explanation
An error occurred whilst migrating the data <insert_1> with identifier <insert_2> from configuration data table <insert_3>. See previous errors for more information.
Response
None.

BIP8725
Rolling back configuration data table changes.
Severity
10 : Warning

BIP8726
Finished Rolling back configuration data table changes.
Severity
10 : Warning

BIP8727
The message flow <insert_1> (Application <insert_2>, Library <insert_3>) may have user-defined property (UDP) or monitoring overrides that were applied after deployment. The message flow will be migrated however these user-defined property (UDP) or monitoring overrides may not be maintained.
Severity
10 : Warning
Explanation
The message flow <insert_1> contains subflow nodes that reference deployable subflows. When the subflow nodes were resolved the resultant message flow contains monitoring events and/or user-defined properties (UDPs). Monitoring event source(s) may have had their state changed after deployment using the mqsichangeflowmonitoring command with the -s parameter. User-defined properties (UDPs) may have been changed after deployment using the Integration Toolkit or Integration API. If such changes were made after deployment these settings may be discarded on migration.
Response
The message flow will be migrated. Any monitoring event source(s) that were changed after deployment will need to be changed again after migration. Any User-defined properties (UDPs) that were changed after deployment will need to be changed again after migration.

BIP8728
The message flow <insert_1> (Application <insert_2>, Library <insert_3>) contains message flow node(s) of type <insert_4> that are no longer supported in IBM Integration Bus. The message flow will be migrated in stopped state.
Severity
10 : Warning
Explanation
The message flow node type <insert_4> is no longer supported in IBM Integration Bus. The message flow cannot run and so will be migrated in stopped state.
Response
After migration remove all of the message flow nodes of type <insert_4> and redeploy the message flow.

BIP8729
The subflow <insert_1> (Application <insert_2>, Library <insert_3>) contains message flow node(s) of type <insert_4> that are no longer supported in IBM Integration Bus. The subflow will be migrated however it cannot be used by message flows.
Severity
10 : Warning
Explanation
The message flow node type <insert_4> is no longer supported in IBM Integration Bus.
Response
After migration remove all of the message flow nodes of type <insert_4> and redeploy the subflow.

BIP8730
Please contact your IBM support center for further information.
Severity
0 : Information

BIP8731
The configuration data for message flow <insert_1> (Application <insert_2>, Library <insert_3>) cannot be read. The message flow cannot be migrated.
Resource label <insert_4>.
Resource identifier <insert_5>.
Resource file name <insert_6>.
Resource location <insert_7>.
Resource directory <insert_8>.
Severity
10 : Warning
Explanation
An error occurred when reading the configuration data for message flow <insert_1>. The information required to migrate the message flow cannot be determined. The message flow cannot be migrated.
Response
If this warning occurred on a pre-migration check then redeploy the message flow or its application before migrating. If this warning occurred during migration then redeploy the message flow or its application after migration.

BIP8750
Starting registry migration for component <insert_1>.
Severity
0 : Information
Explanation
Registry data is being migrated for component <insert_1>.
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_1> subkey
Severity
0 : Information
Explanation
As part of the registry migration, the <insert_1> key has been created.
Response
None.

BIP8753
Created value named <insert_1>; value data is <insert_2>
Severity
0 : Information
Explanation
As part of the registry migration, the <insert_1> value has been created and set to <insert_2>
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_1> into the new location
Severity
0 : Information
Explanation
As part of the registry migration, the legacy data element <insert_1> 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_1>: <insert_2>.
Severity
20 : Error
Explanation
An error has occurred when moving registry value <insert_1>. The registry migration will now be reversed.
Response
None.

BIP8758
Reversing registry migration for component <insert_1>.
Severity
10 : Warning
Explanation
Registry data is being un-migrated for component <insert_1>.
Response
None.

BIP8759
Found registry subkey <insert_1> that is not valid in either source or target; left unchanged.
Severity
10 : Warning
Explanation
During migration, the command found a registry subkey <insert_1> that is not valid in either source or target version; this value will be left unchanged.
Response
None.

BIP8760
Found registry value <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_1> that is not valid in either source or target version; this value will be left unchanged.
Response
None.

BIP8761
Found registry value <insert_1> for DSN <insert_2> that is not valid in either source or target; left unchanged.
Severity
10 : Warning
Explanation
During migration, the command found a registry value <insert_1> in DSN-specific subkey <insert_2> that is not valid in either source or target version; this value will be left unchanged.
Response
None.

BIP8762
Copied registry value from <insert_1> to HTTP value <insert_2>; set to <insert_3>
Severity
0 : Information
Explanation
During migration, the command found a registry value <insert_1> whose name must be changed for the new version into <insert_2>. The value data is still <insert_3>.
Response
None.

BIP8763
Deleted value <insert_1> from the old location
Severity
0 : Information
Explanation
As part of the registry migration, the legacy data element <insert_1> is being copied into the new location.
Response
None.

BIP8764
Found registry subkey <insert_1> that is not valid in the source version; left unchanged.
Severity
10 : Warning
Explanation
During migration, the command found a registry subkey <insert_1> that is not valid in the source version; this value will be left unchanged.
Response
None.

BIP8765
Found registry value <insert_1> that is not valid in the source version; left unchanged.
Severity
10 : Warning
Explanation
During migration, the command found a registry value <insert_1> that is not valid in the source version; this value will be left unchanged.
Response
None.

BIP8766
Copied value <insert_1> for DSN <insert_2> into the new location
Severity
0 : Information
Explanation
As part of the registry migration, the legacy data element <insert_1> is being copied into the new location for DSN <insert_2>.
Response
None.

BIP8767
Found registry value <insert_1> that is not valid in the target version; not copied.
Severity
10 : Warning
Explanation
During migration, the command found a registry value <insert_1> 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_1>.
Severity
0 : Information
Explanation
Registry data has been successfully migrated for component <insert_1>.
Response
None.

BIP8769
An error occurred when migrating integration node <insert_1> to a previous version. You cannot remove the source version (<insert_2>) of the integration node registry after migration.
Severity
10 : Warning
Explanation
An error occurred removing the source version (<insert_2>) of the integration node registry when migrating integration node <insert_1> to a previous version (<insert_3>). This error can occur if one or more of the files or folders in the registry are in use, are open in an application, or a folder is the current working directory in a Command Prompt.
Response
Ensure that none of the files or folders are in use and try again.

BIP8770
An error occurred when creating primary registry folders for integration node <insert_1> in the filesystem, at location <insert_2>. Ensure that the user running the command has full access to this location.
Severity
10 : Warning
Explanation
The primary folders for integration node <insert_1> could not be created in the filesystem at location <insert_2>.
Response
Ensure that the user running the command has the correct permissions.

BIP8771
An error occurred changing the location of the integration node service for integration node <insert_1>.
Severity
10 : Warning
Explanation
The location of the service for integration node <insert_1> could not be updated to the new location.
Response
Ensure that the user running the command has the correct permissions.

BIP8772
An error occurred changing the permissions of the integration node service for the integration node <insert_1>.
Severity
10 : Warning
Explanation
The permissions for the integration node service for the integration node <insert_1> could not be updated.
Response
Ensure that the user running the command has the correct permissions.

BIP8773
An error occurred when migrating the registry for integration node <insert_1>.
Severity
10 : Warning
Explanation
An error occurred when migrating the registry for integration node <insert_1> from the old version to the new.
Response
See previous error messages for further details.

BIP8774
Warning: Unable to set the correct access permissions on a file or folder in the explicit workpath (-w) located at <insert_2> for integration node <insert_1>. Migration will continue, but the permissions on the file(s) at this location have not been changed.
Severity
10 : Warning
Explanation
The permissions a file or folder in the explicit workpath (-w) at location <insert_2> for the integration node <insert_1> could not be updated.
Response
Ensure that the user running the command has the correct permissions.

BIP8775
An error occurred when opening a required registry key <insert_2> for integration node <insert_1>.
Severity
10 : Warning
Explanation
Could not access required registry key <insert_2>. Error code <insert_3>, last error <insert_4>.
Response
Ensure that the user running the command has the correct permissions.

BIP8776
An error occurred when creating a required registry folder at location <insert_2> for integration node <insert_1>.
Severity
10 : Warning
Explanation
Could not create registry folder <insert_2>. Error code <insert_3>, last error <insert_4>.
Response
Ensure that the user running the command has the correct permissions.

BIP8777
An error occurred when opening registry file <insert_2> for migration under integration node <insert_1>.
Severity
10 : Warning
Explanation
Could not open registry file <insert_2>. Error code <insert_3>.
Response
Ensure that the user running the command has the correct permissions.

BIP8778
An error occurred when opening registry file <insert_2> for migration under integration node <insert_1>, the file does not exist.
Severity
10 : Warning
Explanation
Could not open a required file <insert_2> as it does not exist. Error code <insert_3>.
Response
Ensure that the user running the command has the correct permissions and that the file exists and is accessible.

BIP8779
An error occurred when reading from registry file <insert_2> during migration under integration node <insert_1>, the file seems invalid or corrupt.
Severity
10 : Warning
Explanation
Could not read from the required file <insert_2> as it is not valid. Error code <insert_3>.
Response
Ensure that the user running the command has the correct permissions and that the file exists and that it is accessible.

BIP8780
An error occurred when writing to the registry file <insert_2> when migrating integration node <insert_1>.
Severity
10 : Warning
Explanation
Could not write to the required file <insert_2>. Error code <insert_3>.
Response
Ensure that the user running the command has the correct permissions and that the file location is accessible.

BIP8781
A user defined Configurable Service with an invalid character in its name was encountered when migrating the Configurable Services under integration node <insert_1>. The Configurable Service was called <insert_2> and is of type <insert_3>. This Configurable Service must be renamed before migration can take place.
Severity
10 : Warning
Explanation
The user defined Configurable Service <insert_2> of type <insert_3> has at least one invalid character in its name starting at position <insert_4>.
Response
Rename the Configurable Service and re-run the migration command.

BIP8782
A DataSource Name (DSN) called <insert_2> with invalid characters in its name was encountered when migrating the DSNs under integration node <insert_1>. This DSN must be renamed before migration can take place.
Severity
10 : Warning
Explanation
The DSN <insert_2> has at least one invalid character in its name starting at position <insert_3>.
Response
Rename the DSN and re-run the migration command.

BIP8783
The integration node <insert_1> does not exist at a previous level, and so cannot be migrated backwards.
Severity
10 : Warning
Explanation
The integration node <insert_1> cannot be migrated backwards as it does not exist at the previous level.
Response
For an integration node to be migrated backwards, it must exist at the previous level.

BIP8784
The integration node <insert_1> cannot be migrated to the target version <insert_2> because it is incompatible.
Severity
20 : Error
Explanation
The integration node <insert_1> has used functionality that is not compatible with the target version of <insert_1>. The possible causes of this error are:
The integration node was created in the current version of the IBM Integration Bus.
The integration node does not have a default queue manager.
The integration node has administration security with File authorization mode set.
The integration node has shared libraries deployed to it.
Response
For an integration node to be migrated to the target version it needs to compatible.
The integration node must have a default queue manager.
If the integration node has administration security enabled then MQ authorization mode needs to be set.
Any shared libraries and dependent applications need to be removed.

BIP8785
Starting WebSphere MQ queue migration for component <insert_1>.
Severity
0 : Information
Explanation
Queue data is being migrated for component <insert_1>.
Response
None.

BIP8786
Created WebSphere MQ queue <insert_1>
Severity
0 : Information
Explanation
As part of the WebSphere MQ queue migration, the queue <insert_1> has been created.
Response
None.

BIP8787
Cleared WebSphere MQ queue <insert_1>
Severity
0 : Information
Explanation
As part of the WebSphere MQ queue migration, the queue <insert_1> has been cleared of messages.
Response
None.

BIP8788
Deleted WebSphere MQ queue <insert_1>
Severity
0 : Information
Explanation
As part of the WebSphere MQ queue migration, the queue <insert_1> has been deleted.
Response
None.

BIP8789
Finished WebSphere MQ queue migration for component <insert_1>.
Severity
0 : Information
Explanation
Queue data has been successfully migrated for component <insert_1>.
Response
None.

BIP8790
Duplicate rows were detected in table <insert_1>. Migration cannot complete successfully.
Severity
30 : Severe error
Explanation
Duplicate rows were detected in table <insert_1>. The destination product requires unique indexes to be added to the table for correct operation, and duplicate rows prevent the index add from succeeding.
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 integration node 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 integration node database.
Response
None.

BIP8793
Duplicate rows check failed.
Severity
30 : Severe error
Explanation
Duplicate rows were detected in the integration node database. See previous errors for more information.
Response
Contact IBM service for more assistance; do not attempt to correct the problem.

BIP8794
Table <insert_1> 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 prevent the index add from succeeding.
Response
None.

BIP8797
Topic syntax check succeeded.
Severity
0 : Information
Explanation
No topic syntax errors where found in the integration node 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 integration node 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_1>. Topic is <insert_2>. This will prevent migration from succeeding.
Severity
20 : Error
Explanation
Invalid topic syntax was detected in table <insert_1>. Topic is <insert_2>. The destination product requires a new topic syntax and any invalid topic will cause the integration node 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_1>.
Severity
0 : Information

BIP8801
Unable to migrate the registry for integration node <insert_1>1
Severity
10 : Warning
Explanation
The integration node database for the given integration node has been migrated successfully, however while attempting to migrate its registry to the current location a failure occurred.
Response
Migrate this integration node's registry to the current location manually.

BIP8802
Sets the license processor count.
Severity
0 : Information
Explanation
Syntax:
mqsisetcapacity -c processorCount


Command Options:
'-c processorCount' is the number of processors on this machine for which IBM Integration Bus 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 IBM Integration Bus is now running in Production mode.
Severity
0 : Information
Explanation
A Production license has been installed for this copy of IBM Integration Bus.

BIP8805
No license installed for this copy of IBM Integration Bus.
Severity
20 : Error
Explanation
No Production license has been installed for this copy of IBM Integration Bus.
Response
A valid Production license must be installed before the IBM Integration Bus product can be run, ensure that the product installation completed successfully.

BIP8806
A license could not be installed for this copy of IBM Integration Bus.
Severity
20 : Error
Explanation
A Production license could not be installed for this copy of IBM Integration Bus. 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 IBM Integration Bus has expired.
Severity
20 : Error
Explanation
The production license for this copy of IBM Integration Bus has an expiry date. This date has been passed.
Response
Contact your IBM support center.

BIP8808
License file <insert_1> not found or not valid. For more information refer to the IBM Integration Bus online help.
Severity
20 : Error
Explanation
IBM Integration Bus requires that the file <insert_1> 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 IBM Integration Bus is already running in Production mode.
Severity
0 : Information
Explanation
A Production license has previously been installed for this copy of IBM Integration Bus.

BIP8810
Insufficient license units.
Severity
10 : Warning
Explanation
The purchased processor allowance (<insert_1>) is less than the number of processors (<insert_2>) in this machine.
Response
Ensure sufficient license units have been purchased and use the IBM Integration Bus 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_1>.
Severity
0 : Information
Explanation
The purchased processor allowance for this installation of IBM Integration Bus has been set to <insert_1> using the mqsisetcapacity command.

BIP8812
The purchased processor allowance is <insert_1>1
Severity
0 : Information
Explanation
The purchased processor allowance is currently set to <insert_1>1
Response
Ensure sufficient license units have been purchased and, if necessary, use the IBM Integration Bus 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_1>1
Severity
0 : Information
Explanation
The operating system reports that the number of processors in this machine is <insert_1>.

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 IBM Integration Bus 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 IBM Integration Bus 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_1>.
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_1>.
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 integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsimigratequeues integrationNodeName


Command options
'integrationNodeName' the name of integration node whose queues are to be migrated.

BIP8819
Migrates WebSphere MQ queues for integration nodes. Syntax: mqsimigratequeues
Severity
10 : Warning
Explanation
Creates queues on a WebSphere MQ queue manager for use with a migrated integration node.

BIP8820
Enter password for user ID
Severity
10 : Warning
Explanation
This is used to prompt for a password for service user ID on the console.
Response
Enter password for user ID

BIP8821
Enter password for user ID
Severity
10 : Warning
Explanation
This is used to prompt for a password for service user ID on the console.
Response
Enter password for user ID

BIP8822
The supplied password is invalid. Ensure that the password is within the range of 2 - 255 characters in length.
Severity
10 : Warning
Response
Re-enter the password.

BIP8823
Retype password for user ID
Severity
10 : Warning
Explanation
This is used to prompt for a password for service user ID on the console.
Response
Retype password for user ID

BIP8824
Retype password for user ID.
Severity
10 : Warning
Explanation
This prompts you for a password for the service user ID on the console.
Response
Retype the password for your user ID.

BIP8825
Passwords do not match.
Severity
10 : Warning
Explanation
Passwords do not match.
Response
Passwords do not match.

BIP8826
Invalid version identifier <insert_1> supplied.
Severity
30 : Severe error
Explanation
The supplied version is not valid as a function-level specifier
Response
Check that the string given to the '-f' argument is 'all', blank, or of the form <version>.<release>.<modification>.<fix>

BIP8827
Creates an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsicreatebroker. integrationNodeName -q queueManagerName [-l userLilPath] [-1 | -2] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath] [-s adminSecurity] [-b cachePolicy] [-r cachePortRange]


Command Options
'integrationNodeName' the name of the integration node to create.
'-q queueManagerName' the default WebSphere MQ queue manager that is used by the integration node.
'-1' creates only the integration node's registry.
'-2' creates only the integration node's WebSphere MQ resources.
'-l userLilPath' the directory from which the integration node searches for user-supplied libraries.
'-C CCSID' the default coded character set ID for the integration node.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'. The default is 'inactive'.
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.

BIP8828
Deletes an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsideletebroker. integrationNodeName [-1 | -2] [-s]


Command Options:
'integrationNodeName' name of the integration node to delete
'-1' deletes only the integration node's registry.
'-2' deletes only the integration node's WebSphere MQ queues.
'-s' delete the integration node and any current integration server administration security WebSphere MQ queues.

BIP8829
Invalid property name <insert_1> specified.
Severity
20 : Error
Explanation
Property names must be valid XML element or XML attribute names.
Response
Correct and reissue the command.

BIP8830
The default queue manager for the integration node has been changed while administration security is active. Resource access permissions need to be applied.
Severity
10 : Warning
Explanation
The mqsichangebroker command has changed the default queue manager for the integration node. Resource access authorizations for administration need to be applied again to the MQ objects located on the new queue manager.
Response
Use the setmqaut command to set authorizations on the SYSTEM.BROKER.AUTH queue, and any other authorization queues located on the new queue manager.

BIP8831
The default queue manager for the integration node has been removed while administration security using MQ authorization mode is active. File authorization mode needs to be configured on the integration node.
Severity
10 : Warning
Explanation
The mqsichangebroker command has removed the default queue manager for the integration node. The integration node is configured with security active using MQ authorization mode. File authorization mode needs to be configured on the integration node, and the required authorizations applied.
Response
Use the mqsichangeauthmode command to set file authorization mode, and use the mqsichangefileauth command to set each user authorization for administration.

BIP8832
Invalid number of property values specified.
Severity
20 : Error
Explanation
<insert_1> property values have been specified, but only <insert_2> property names have been specified.
The number of property values specified must be less than or equal to the number of property names specified.
If you are attempting to specify commas in a property value, then that value must be enclosed with escaped double quotation marks (\\\" and \\\").
For example, -n Name1,Name2 -v Value1,\"Value21,Value22\".
Response
Correct and reissue the command.

BIP8833
Changes the configuration of an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsichangebroker integrationNodeName [-l userLilPath] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits] [-s adminSecurity] [-f function level] [-b cachePolicy] [-r cachePortRange]


Command options:
'integrationNodeName' the name of the integration node.
'-l userLilPath' the directory from which the integration node searches for user-supplied libraries.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-C CCSID' the default coded character set ID for the integration node.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node HTTP listener uses.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server 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 integration node. The default state can be overridden at the integration server or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified, and no library is found to provide that user exit when the integration server starts, a BIP8860 message is written to the system log and the integration server fails to start. The separator character for the list is ':'.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'.
'-f function level' the effective function level of the integration node, such as '7.0.0.1', '7.0.0.2', or 'all'
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.

BIP8834
Invalid number of property names specified.
Severity
20 : Error
Explanation
A property value has been specified with the '-p' flag, but <insert_1> property names have been specified.
Only one property name must be specified when a property value is specified with the '-p' flag.
Response
Correct and reissue the command.

BIP8840
Deploys a BAR file or deletes resources from an integration server. Syntax: deploy e=egName ((a=BARFileName [m=yes]) | d=resourcesToDelete) [w=timeoutSecs]
Severity
10 : Warning
Explanation
Command Options:
'e=egName' name of integration server to deploy to.
'a=BARFileName' deploy the specified BAR file.
'm=yes' empties the integration server before deployment.
'd=resourcesToDelete' deletes a colon-separated list of resources from the integration server.
'w=timeoutSecs' maximum number of seconds to wait for the integration node to respond (default is 60).

BIP8841
Deploys a BAR file or deletes resources from an integration server.
Severity
0 : Information
Explanation
Syntax:
mqsideploy integrationNodeSpec -e integrationServerName ((-a BARFileName [-m]) | -d resourcesToDelete) [-w timeoutSecs] [-v traceFileName]

Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-e integrationServerName' name of integration server
'-a BARFileName' deploy the specified BAR file
'-m' empties the integration server before deployment
'-d resourcesToDelete' deletes a colon-separated list of resources from the integration server
'-w timeoutSecs' maximum number of seconds to wait for the integration node to respond (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP8846
Configuration data for component <insert_1> is not usable by this product version (level <insert_2>; should be <insert_3>).
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_2> and the current code level only supports <insert_3>.

BIP8847
migrates a components registry and file-system information between different versions.
Severity
10 : Warning
Explanation
Syntax:
mqsimigratecomponents componentName [ -s sourceVersion ] [ -t targetVersion ] [ -c ] [ -v ] [ -q ] [ -u ]


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.
'-v' Do a post-migration check of the specified component for the new version of the component.
'-q' Reduce the verbosity of the progress of the command.
'-u' Undo a failed migration step. This should only be used when migration has failed, and also failed to auto-recover.

BIP8848
Invalid version <insert_1>.<insert_2>.<insert_3>.<insert_4> 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 version for migration to or from IBM Integration Bus <insert_5>.<insert_6>.<insert_7>.<insert_8> is version 7.0.0.5.
If the version has already been specified correctly the component cannot be automatically migrated.

BIP8849
Integration node <insert_1> (Version <insert_4>.<insert_5>) with queue manager <insert_2> and data source <insert_3> specified for migration.
Severity
0 : Information

BIP8850
Displays integration node property settings.
Severity
10 : Warning
Explanation
Syntax:
mqsireportodbcconnectioninfo -q dsn1 -u userName1 -p password1 [-c dsn2 -i userName2 -a password2] [-v]


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 inactive user exits.
Severity
10 : Warning
Explanation
Syntax:
mqsichangeflowuserexits integrationNodeName -e integrationServerName [[-k applicationName] [-y staticLibraryName] -f messageFlowName] (-a activeUserExitList |-i inactiveUserExitList)
Command Options:
'integrationNodeName' name of the integration node.
'-e integrationServerName' name of the integration server.
'-f messageFlowName' name of message flow.
'-k applicationName' name of application.
'-y staticLibraryName' name of static library.
'-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 does not alter the existing value of a user exit list, if the corresponding name/value pair is not specified. To clear a user exit list, use an empty string (""), for example, '-i ""'.

BIP8853
queries the lists of active and inactive user exits.
Severity
10 : Warning
Explanation
Syntax:
mqsireportflowuserexits integrationNodeName [-e integrationServerName [[-k applicationName] [-y staticLibraryName] -f messageFlowName]]


Command Options:
'integrationNodeName' name of the integration node
'-e integrationServerName' name of the integration server
'-f messageFlowName' name of message flow
'-k applicationName' name of application
'-y staticLibraryName' name of static library

BIP8854
User Exits active for integration server <insert_1>: <insert_2>.
Severity
0 : Information

BIP8855
User Exits inactive for integration server <insert_1>: <insert_2>.
Severity
0 : Information

BIP8856
User Exits active for Message Flow <insert_1>: <insert_2>.
Severity
0 : Information

BIP8857
User Exits inactive for Message Flow <insert_1>: <insert_2>.
Severity
0 : Information

BIP8858
Invalid user exit name <insert_1> specified
Severity
20 : Error
Explanation
User exit name <insert_1> specified on the <insert_2> flag does not correspond to any user exit available to the target integration server.
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 integration server. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath integration node property to ensure one of them includes the directory containing the user exit library. Check system log when integration server starts for errors loading the user exit library.

BIP8859
User Exits active for integration node <insert_1>: <insert_2>.
Severity
0 : Information

BIP8860
User Exit <insert_1> not found
Severity
20 : Error
Explanation
A User Exit name <insert_1> has been specified as active or inactive but that user exit was not provided by any library loaded by this integration server. 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 integration node level, then run mqsichangebroker to correct it. If it was set at the integration server 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 integration server. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath integration node property to ensure one of them includes the directory containing the user exit library. Check system log when integration server starts for errors loading the user exit library.

BIP8861
User Exit <insert_1> not found for flow <insert_2>
Severity
20 : Error
Explanation
A User Exit name <insert_1> has been specified as active or inactive for message flow <insert_2> but that user exit was not provided by any library loaded by this integration server. 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 integration server. Check settings for MQSI_USER_EXIT_PATH environment variable and/or userExitPath integration node property to ensure one of them includes the directory containing the user exit library. Check system log when integration server starts for errors loading the user exit library.

BIP8862
Sets the list of active or inactive user exits. Syntax: changeflowuserexits integrationNodeName e=egName [[k=applicationName] [y=libraryName] f=messageFlowName] (a=activeUserExitList |i=inactiveUserExitList)
Severity
10 : Warning
Explanation
Command Options:
'integrationNodeName' name of the integration node.
'e=egName' name of the integration server.
'k=applicationName' name of application.
'y=libraryName' name of library.
'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. Syntax: reportflowuserexits integrationNodeName [e=egName [[k=applicationName] [y=libraryName] f=messageFlowName]]
Severity
10 : Warning
Explanation
Command Options:
'integrationNodeName' name of the integration node.
'e=egName' name of the integration server.
'f=messageFlowName' name of message flow.
'k=applicationName' name of application.
'y=libraryName' name of library.

BIP8864
Internal Error: Unable to set RC and inserts (RC is <insert_1>).
Severity
20 : Error
Explanation
Unable to set RC and inserts as RC, <insert_1>, is unknown.
Response
Contact your IBM support center to report this error.

BIP8865
Bad flag combination. The flags in list (<insert_1>) can't be specified together.
Severity
20 : Error
Explanation
None.
Response
Correct and reissue the command.

BIP8866
The registry is not in the correct state for this step-by-step migration (using the '-2' or '-3' flags) from Version (<insert_1>.<insert_2>.<insert_3>.<insert_4>) to Version (<insert_5>.<insert_6>.<insert_7>.<insert_8>).
Severity
20 : Error
Explanation
For a forward migration, the correct order for step-by-step migration is to migrate the registry (by using the '-1' flag) before migrating any other components.
Response
Correct the migration order.

BIP8867
Migration from Version <insert_1>.<insert_2>.<insert_3>.<insert_4> to Version <insert_5>.<insert_6>.<insert_7>.<insert_8> 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_1> 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 IBM Integration Bus.
Severity
10 : Warning

BIP8869
The registry is not in the correct state for this step-by-step reverse migration (using the '-1' flag) from Version (<insert_1>.<insert_2>.<insert_3>.<insert_4>) to Version (<insert_5>.<insert_6>.<insert_7>.<insert_8>).
Severity
20 : Error
Explanation
For a reverse migration, the correct order for step-by-step migration is to reverse migrate the registry (by using the '-1' flag) only after reverse migration of all other components (using the '-2' or '-3' flags, or both) is complete.
Response
Correct the migration order.

BIP8870
Trace nodes are: <insert_1> for integration server: <insert_2>, message flow: <insert_3>.
Severity
0 : Information
Explanation
Trace nodes are either 'on' or 'off' for each message flow. These settings take effect only if the integration server setting is 'on'.

BIP8871
Integration server: <insert_2> has trace nodes: <insert_1> for its message flows.
Severity
0 : Information
Explanation
When the integration server has trace nodes set to 'on' the individual settings on the message flows take effect.

BIP8872
Verifies an integration node. Verifies a user datasource to be used within the integration node, or compares primary and secondary datasources for equivalence.
Severity
10 : Warning
Explanation
Syntax (1):
mqsicvp integrationNodeName
Syntax (2):
mqsicvp integrationNodeName -n primaryDatasource [-c secondaryDatasource] [-v]
Syntax (3):
mqsicvp -n primaryDatasource -u primaryDatasourceUserId -p primaryDatasourcePassword [-c secondaryDatasource -i secondaryDatasourceUserId -a secondaryDatasourcePassword] [-v]


Command options, syntax (1):
'integrationNodeName'
The integration node name.

Command options, syntax (2):
'integrationNodeName'
The integration node name.
'-n primaryDatasource'
The name of the datasource to verify.
This datasource must have been previously associated with the integration node using mqsisetdbparms.
'-c secondaryDatasource'
The name of the second datasource.
If specified, the function of this datasource is compared with that of primaryDatasource.
This datasource must have been previously associated with the integration node using mqsisetdbparms.
'-v'
Causes extra, untranslated, diagnostics related to supported CASTS to be output by the command.

Command options, syntax (3):
'-n primaryDatasource'
The name of the datasource to verify.
'-u primaryDatasourceUserId'
The user identifier to be used to connect to primaryDatasource.
'-p primaryDatasourcePassword'
The password associated with primaryDatasourceUserId
'-c secondaryDatasource'
The name of the second datasource.
If specified, the function of this datasource is compared with that of primaryDatasource.
'-i secondaryDatasourceUserId'
The user identifier to be used to connect to secondaryDatasource.
'-a secondaryDatasourcePassword'
The password associated with secondaryDatasourceUserId
'-v'
Causes extra, untranslated, diagnostics related to supported CASTS to be output by the command.

BIP8873
Starting the component verification for component <insert_1>.
Severity
0 : Information

BIP8874
The component verification for <insert_1> has finished successfully.
Severity
0 : Information

BIP8875
The component verification for <insert_1> has finished, but one or more checks failed.
Severity
10 : Warning
Explanation
One or more of the component verification checks failed.
Response
Check the error log for preceding error messages.

BIP8876
Starting the environment verification for component <insert_1>.
Severity
0 : Information

BIP8877
The environment verification for component <insert_1> has finished, but one or more checks failed.
Severity
10 : Warning
Explanation
One or more of the environment verification checks failed.
Response
Check the error log for preceding error messages.

BIP8878
The environment verification for component <insert_1> has finished successfully.
Severity
0 : Information

BIP8879
Starting the database verification for component <insert_1>.
Severity
0 : Information

BIP8880
The database verification for component <insert_1> has finished, but one or more checks failed.
Severity
10 : Warning
Explanation
One or more of the database verification checks failed.
Response
Check the error log for preceding error messages.

BIP8881
The database verification for component <insert_1> has finished successfully.
Severity
0 : Information

BIP8882
Starting the WebSphere MQ verification for component <insert_1>.
Severity
0 : Information

BIP8883
The WebSphere MQ verification for component <insert_1> has finished, but one or more checks failed.
Severity
10 : Warning
Explanation
One or more of the WebSphere MQ verification checks failed.
Response
Check the error log for preceding error messages.

BIP8884
The WebSphere MQ verification for component <insert_1> has finished successfully.
Severity
0 : Information

BIP8885
Verification failed. Failed to connect to queue manager <insert_1>. MQRC: <insert_2> MQCC: <insert_3>3
Severity
20 : Error
Explanation
While attempting to connect to queue manager <insert_1>, a WebSphere MQ error generated return code <insert_2> and completion code <insert_3>.
Response
Check the WebSphere MQ completion and reason codes in the Application Programming Reference section of the WebSphere MQ information center to establish the cause of the error, and take any appropriate action.

BIP8886
Verification passed for queue <insert_1> on queue manager <insert_2>.
Severity
0 : Information

BIP8887
Verification failed for queue <insert_1> on queue manager <insert_2> while issuing <insert_3>. MQRC: <insert_4> MQCC: <insert_5>5
Severity
20 : Error
Explanation
The operation <insert_3> on the specified queue returned with the indicated WebSphere MQ completion and reason codes.
Typical causes of failures during queue verification are that the queue does not exist, or that the integration node is unable to put or get a message.
Response
Check the WebSphere MQ completion and reason codes in the Application Programming Reference section of the WebSphere MQ information center to establish the cause of the error, and take any appropriate action.

BIP8888
Verification failed. Failed to disconnect from queue manager <insert_1>. MQRC: <insert_2> MQCC: <insert_3>3
Severity
20 : Error
Explanation
While attempting to disconnect from queue manager <insert_1>, a WebSphere MQ error generated return code <insert_2> and completion code <insert_3>.
Response
Check the WebSphere MQ completion and reason codes in the Application Programming Reference section of the WebSphere MQ information center to establish the cause of the error, and take any appropriate action.

BIP8889
Verification failed for table <insert_1> in integration node datasource <insert_2>. Preceding messages contain further information.
Severity
20 : Error
Explanation
An operation on table <insert_1> in datasource <insert_2> has failed.
Response
See preceding messages, for example BIP2322, for further information about the cause of this failure and the actions that you can take to resolve it.

BIP8890
Verification passed for table <insert_1> in datasource <insert_2>.
Severity
0 : Information

BIP8891
Verification failed. Failed to connect to datasource <insert_1> with user ID <insert_2>. Preceding messages contain further information.
Severity
20 : Error
Explanation
While attempting to connect to datasource <insert_1> with user ID <insert_2>, an error occurred.
Typical causes of this error are incorrect user ID or password, or incorrect user ID permissions.
On z/OS, the user ID is blank because SQLConnect is performed by using the primary authorization ID, which resolves to the user ID of the started task.
Response
See preceding messages for further information about the cause of this failure, and the actions that you can take to resolve it.

BIP8892
Verification failed. The installed Java level <insert_1> does not meet the required Java level <insert_2>.
Severity
20 : Error
Explanation
The installed level of Java does not match the required level of Java.
Response
On z/OS, install the correct level of Java, and correct the component profile BIPBPROF or BIPCPROF. Submit BIPGEN to create the component's ENVFILE.
On distributed platforms, you must use the JVM that is supplied and installed with the integration node. In mqsiprofile, correct the MQSI_JREPATH and PATH environment variables, and the appropriate library path environment variables for your operating system.

BIP8893
Unable to access file <insert_1> with user ID <insert_2> due to error <insert_3>. Additional information for IBM support: <insert_4> <insert_5>.
Severity
20 : Error
Explanation
The component has encountered an error trying to access file <insert_1>.
This error is typically caused by incorrect file permissions, insufficient storage or in the case of NULL because the directory doesn't exist. This is typically found when checking the integration node's home directory, which is not correctly defined.
Response
Ensure that user ID <insert_2> has the correct permissions to access file <insert_1>, and that sufficient storage exists on the file system.
If this problem persists, contact your IBM support center.

BIP8894
Verification passed for <insert_1>.
Severity
0 : Information

BIP8895
Verification failed. Environment variable <insert_1> is incorrect or missing.
Severity
20 : Error
Explanation
The component requires environment variable <insert_1>.
Response
On z/OS, correct the integration node's profile BIPBPROF and submit BIPGEN to recreate the ENVFILE.
On distributed platforms, check that you have run mqsiprofile, and that the environment variable <insert_1> exists and is set to the correct value.
Preceding messages might contain further information about the cause of this failure, and the actions that you can take to resolve it.

BIP8896
Verification failed. Unable to access the registry with user ID <insert_1>. Additional information for IBM support: <insert_2> <insert_3>.
Severity
20 : Error
Explanation
The component has encountered an error trying to access the registry.
Typical causes of this failure are incorrect file permissions or insufficient storage.
On Linux, UNIX, and z/OS systems, the location of the registry is defined by the MQSI_REGISTRY environment variable.
Response
Ensure that user ID <insert_1> has the correct permissions to access the registry, and that sufficient storage exists on the file system.
If this problem persists, contact your IBM support center.

BIP8897
Verification failed. Environment variable <insert_1> does not match the component name <insert_2>.
Severity
20 : Error
Explanation
The value of the environment variable must match the component name.
Response
Correct the environment variable <insert_1> in the component profile BIPBPROF or BIPCPROF. Submit BIPGEN to create the component's ENVFILE.

BIP8898
Verification failed. Table <insert_1> in datasource <insert_2> contains no columns.
Severity
20 : Error
Explanation
Table <insert_1> does not contain the set of columns that this component requires to function correctly. The table might have been damaged, or, if you have recently migrated the component, you might not have completed all the required steps successfully.
Response
If you have recently migrated the integration node, check that you have completed all migration steps, and that they were all succeessful. If you have just created this integration node as a new integration node, and the datasource tables were created manually by a datasource administrator, ensure that all required columns are defined.

BIP8899
Verification failed. Table <insert_1> in datasource <insert_2> contains <insert_3> rows, but must contain exactly 1 row.
Severity
20 : Error
Explanation
Table <insert_1> does not contain the correct number of rows that this component requires to function correctly. The table might have been damaged, or the DB2 installation jobs might not have completed succesfully.
Response
Check that the DB2 installation jobs have completed succesfully, correct any errors that have been reported, and retry the operation.

BIP8900
Verification passed for APF Authorization of file <insert_1>.
Severity
0 : Information

BIP8901
Table <insert_1> is not empty. This table will be dropped after a migration to the target version is performed.
Severity
10 : Warning
Response
Manually backup the table, if required, before performing the migration.

BIP8902
Table <insert_1> is empty.
Severity
0 : Information

BIP8903
Verification failed. The APF Authorization check failed for file <insert_1>.
Severity
20 : Error
Explanation
IBM Integration Bus requires that only bipimain is APF Authorized for successful operation. File <insert_1> fails that requirement.
Response
If the file indicated in the message is bipimain, use the USS command extattr to ensure that it is APF Authorized. If the file indicated in the message is not bipimain, use the USS command extattr to ensure that it is not APF Authorized. For more information, search the information center for "APF attributes".

BIP8904
Verification failed. Failed to stat file <insert_1> with return code <insert_2> and errno <insert_3>.
Severity
20 : Error
Explanation
The component has encountered an error trying to stat file <insert_1>. Typical reasons for this error are that the file does not exist, or the file name is a symbolic link that is either not valid or results in a pathname that is longer than the maximum path length.
Response
Ensure that the file exists and is available, and that any symbolic links can be resolved in less than 1024 characters, and then retry the operation. If the file location is incorrect, ensure that MQSI_FILEPATH points to the root directory of your IBM Integration Bus installation. If the problem persists, contact your IBM support center.

BIP8905
Changes the monitoring options of a message flow.
Severity
10 : Warning
Explanation
Syntax:
mqsichangeflowmonitoring integrationNodeName (-e integrationServerName | -g) ([-k application] [-y staticLibrary] -f messageFlow | -j) [-c control] [-m monitoringProfileName] [-i eventState -s eventSources]

Command Options:
'integrationNodeName' name of the integration node
'-e integrationServerName' integration server name
'-g' indicates all integration servers
'-k application' application name
'-y staticLibrary' static library name
'-f messageFlow' message flow name
'-j' indicates all message flows
'-c control' starts or stops monitoring: values allowed are 'active' or 'inactive'
'-m monitoringProfileName' specifies the name of the monitoring profile to be used
'-i eventState' changes the state of events for event sources specified by the -s option: values allowed are 'enable' or 'disable' Applicable only with options -e and -f
'-s eventSources' specifies the event sources that are to have their event state changed by the -i option. Specify the event sources as a comma-separated list, where each event source is of the form <nodeLabel>.terminal.<terminalName> or <nodeLabel>.transaction.<Start, End or Rollback>. The latter form is applicable only to input nodes. Applicable only with options -e and -f.

BIP8906
Changes the monitoring options of a message flow. Syntax : changeflowmonitoring ( ,e=integration_server_name | ,g=yes ) ( [,k=Application] [,y=Library] ,f=MessageFlow | ,j=yes ) [ ,c=Control ] [ ,m=monitoringProfileName ] [,i=eventState,s=eventSources]
Severity
10 : Warning
Explanation
Command Options
'e' Integration server name.
'g' indicates all integration servers.
'f' Message Flow name.
'k' Application name.
'y' Library name.
'j' indicates all Message Flows.
'c' starts or stops monitoring: values allowed are 'active' or 'inactive'.
'm' specifies the monitoring profile name to be used
'i' changes the state of events for event sources specified by the s option: values allowed are 'enable' or 'disable' Applicable only with options e and f
's' specifies the event sources that are to have their event state changed by the i option. Specify the event sources as a comma-separated list, where each event source is of the form <nodeLabel>.terminal.<terminalName> or <nodeLabel>.transaction.<Start, End or Rollback>. The latter form is applicable only to input nodes. Applicable only with options e and f.

BIP8907
Verification failed. Unable to verify Java level.
Severity
20 : Error
Explanation
Unable to verify the installed Java level. This error is typically caused by Java not being installed, or a file permissions error.
Response
Ensure Java has been correctly installed, by running the command java -version.
If Java has been correctly installed, see the preceding messages for further information about the cause of this failure, and the actions that you can take to resolve it.

BIP8908
Verification failed for <insert_1>. Preceding messages contain further information.
Severity
20 : Error
Response
See preceding messages for further information about the cause of this failure, and the actions that you can take to resolve it.

BIP8909
Displays monitoring settings.
Severity
10 : Warning
Explanation
Syntax:
mqsireportflowmonitoring integrationNodeName ( -e integrationServerName | -g ) ([-k application] [-y staticLibrary] -f messageFlow | -j ) [-a | -n | -s eventSource | -x -p pathToFile]

Command Options
'integrationNodeName' name of the integration node
'-e integrationServerName' integration server name
'-g' indicates all integration servers
'-k application' application name
'-y staticLibrary' static library name
'-f messageFlow' message flow name
'-j' indicates all message flows.
'-a' indicates that the command should report the monitoring properties for all event sources in the message flow, whether they have been configured or not. Applicable only with options -e and -f.
'-n' indicates that the command should report the monitoring properties for all event sources in the message flow where monitoring is configured. Applicable only with options -e and -f.
'-s' indicates that the command should report the monitoring properties for the specified event sources in the message flow. The event sources should be specified as a comma-separated list, where each event source is of the form <nodeLabel>.terminal.<terminalName> or <nodeLabel>.transaction.<Start, End or Rollback>. The latter form is applicable only to input nodes. Applicable only with options -e and -f.
'-x' indicates that the command should report the monitoring properties for all configured nodes in the message flow, in XML form. Applicable only with options -e, -f and -p.
'-p' indicates the file to which the output from the -x option should be written. Its argument is the path to the file. Applicable only with options -e, -f and -x.

BIP8910
Displays monitoring settings.
Syntax: mqsireportflowmonitoring ( e=integrationServerName | g=yes ) ([,k=Application] [,y=Library] ,f=MessageFlow | ,j=yes ) [,a=yes | ,n=yes | ,s=eventSource | ,x=yes,p=pathToFile]
Severity
10 : Warning
Explanation
Command Options
'e' The name of the integration server.
'g' indicates all integration servers.
'k' Application name.
'y' Library name.
'f' Message Flow name.
'j' indicates all Message Flows.
'a' indicates that the command reports the monitoring properties for all nodes in the message flow, whether they have been configured or not. Applicable only with options e and f.
'n' indicates that the command reports the monitoring properties for all nodes in the message flow where monitoring is configured. Applicable only with options e and f.
's' indicates that the command reports the monitoring properties for the specified event sources in the message flow. The event sources must be specified as a comma separated list, where each event source is of the form <nodeLabel>.terminal.<terminalName> or <nodeLabel>.transaction.<Start, End or Rollback>. The latter form is applicable only to input nodes. Applicable only with options e and f.
'x' indicates that the command reports the monitoring properties for all configured nodes in the message flow, in XML form. Applicable only with options e, f, and p.
'p' indicates the file to which the output from the x option will be written. Its argument is the path to the file. Applicable only with options e, f, and x.

BIP8911
Monitoring settings for flow <insert_1> in integration server <insert_2> - State?: <insert_3>, ProfileName: <insert_4>.
Severity
0 : Information

BIP8912
Event: <insert_1>, Event name: <insert_2>, Configured?: <insert_3>, State?: <insert_4>.
Severity
0 : Information

BIP8913
Event: <insert_1> not found in message flow <insert_2>
Severity
0 : Information
Explanation
The event with the name that you specified, using the -s parameter, was not found in the message flow.

BIP8914
Changes the configuration of an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsichangebroker integrationNodeName [[-i generalDefaultUserId] -a generalDefaultPassword] [-t | -n] [-l userLilPath] [-r userLilPath64] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-c ICU converter path] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-b userExitPath64] [-e activeUserExits] [-o operationMode] [-s adminSecurity]


Command options:
'integrationNodeName' the name of the integration node to change.
'-i generalDefaultUserId' the default user ID that the integration node will use to connect to external resources.
'-a generalDefaultPassword' the password to be used with the generalDefaultUserId.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-n' WebSphere MQ fastpath for this integration node not enabled.
'-l userLilPath' indicates from where user-written 32-bit LIL and JAR files are loaded.
'-r userLilPath64' indicates from where user-written 64-bit LIL and JAR files are loaded.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c ICU converter path' delimited ':' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all 32-bit user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-b userExitPath64' the directory from which the integration node searches for all 64-bit user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a user exit name to this list changes its default state to active for this integration node. The default state can be overridden at the integration server or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the integration server starts, a BIP8860 message is written to the system log and the integration server fails to start. The separator character for the list is ':'.
'-o operationMode' the integration node operation mode. Valid values are 'express', 'standard', 'adapter', and 'advanced'.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'.

BIP8915
Creates an integration node.
Severity
10 : Warning
Explanation
Syntax:
mqsicreatebroker. integrationNodeName [-q queueManagerName] [-i generalDefaultUserId -a generalDefaultPassword] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-w workPath] [-l userLilPath] [-r userLilPath64] [-t] [-m] [-v statisticsMajorInterval] [-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath] [-b userExitPath64] [-o operationMode] [-s adminSecurity]


Command Options:
'integrationNodeName' the name of the integration node.
'-q queueManagerName' the default WebSphere MQ queue manager that is used by the integration node. If -q is not specified, there is no default WebSphere MQ queue manager associated with the integration node.
'-i generalDefaultUserId' the default user ID that the integration node will use to connect to external resources.
'-a generalDefaultPassword' the password to be used with the generalDefaultUserId.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-w workPath' the directory in which internal data, such as installation logs, component details, and trace output are written.
'-l userLilPath' the directory from which the integration node searches for user-supplied 32-bit libraries.
'-r userLilPath64' the directory from which the integration node searches for user-supplied 64-bit libraries.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-m' indicates that migration is required from an IBM publish/subscribe integration node.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c icuConverterPath' delimited ':' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all 32-bit user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-b userExitPath64' the directory from which the integration node searches for all 64-bit user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-o operationMode' the integration node operation mode. Valid values that you can set are 'express', 'standard', 'adapter', 'advanced' and 'applicationIntegrationSuite'. The default mode is 'advanced' unless you have the Trial Edition, in which case the default mode is 'trial'.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'. The default is 'inactive'.

BIP8916
Update monitoring profile configurable service <insert_1> to change monitoring properties for flow <insert_2>
Severity
0 : Information
Explanation
Message flow <insert_2> uses monitoring profile configurable service <insert_1> to set its monitoring properties. You cannot use the mqsichangeflowmonitoring command to update a configurable service.
Response
Use the mqsichangeproperties command to update the monitoring profile configurable service.

BIP8917
Event: <insert_1> not found in monitoring profile configurable service <insert_2>
Severity
0 : Information
Explanation
The event was specified in the -s parameter but no event with that name was found in the monitoring profile configurable service.
Response
Correct the name and then reissue the command.

BIP8918
The monitoring profile configurable service has not been updated
Severity
0 : Information
Explanation
The errors reported for this command have prevented the monitoring profile configurable service being updated.
Response
Correct and then reissue the command.

BIP8919
mqsireportproperties did not find any configured event sources. If this is not expected it could be because your profile failed to load correctly. Check for errors and correct if necessary.
Severity
10 : Warning
Explanation
mqsireportflowmonitoring did not find any configured event sources. The monitoring properties were loaded from a configurable service monitoring profile, which might contain errors.
Response
Check the monitoring profile source and messages and correct the profile as necessary.

BIP8920
Creates an integration node.
Severity
10 : Warning
Explanation
Syntax (for Microsoft Windows platforms):
mqsicreatebroker. integrationNodeName [-i serviceUserID | -i LocalSystem ] -a servicePassword [-q queueManagerName] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-w workPath] [-e sharedWorkpath] [-l userLilPath] [-t] [-m] [-v statisticsMajorInterval] [-P httpListenerPort] [-c icuConverterPath] [-y ldapPrincipal -z ldapCredentials] [-x userExitPath] [-o operationMode] [-s adminSecurity] [-d MQService] [-b cachePolicy] [-r cachePortRange] [-S autoStart]


Command Options:
'integrationNodeName' the name of the integration node.
'-i serviceUserID' the user ID that the integration node runs under and is used to connect to external resources. If -i is not specified, LocalSystem is the default that is used for this parameter.
'-a servicePassword' the password for the integration node user ID. If 'LocalSystem' was specified for the user ID, the password value is ignored.
'-C CCSID' the default coded character set ID for the integration node.
'-q queueManagerName' the default WebSphere MQ queue manager that is used by the integration node. If -q is not specified, there is no default WebSphere MQ queue manager associated with the integration node.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-w workPath' the directory in which internal data, such as installation logs, component details, and trace output are written.
'-e sharedWorkPath' the directory in which registry and configuration data is shared between multiple instances of this integration node.
'-l userLilPath' the directory from which the integration node searches for user-supplied libraries.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-m' indicates that migration is required from an IBM publish/subscribe integration node.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c icuConverterPath' delimited ';' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-o operationMode' the integration node operation mode. Valid values that you can set are 'express', 'standard', 'scale', 'adapter', 'advanced' and 'applicationIntegrationSuite'. The default mode is 'advanced' unless you have the Developer Edition, in which case the default mode is 'developer'.
'-s adminSecurity' activates integration node administration security. Valid values that you can set are 'active' and 'inactive'. The default is 'inactive'.
'-d MQService' start the broker as a WebSphere MQ Service when the queue manager starts. Valid values that you can set are 'defined' and 'undefined'. The default is 'undefined'.
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.
'-B integrationNodeDomainGroup' the Windows Domain Group that is used to secure files in the sharedWorkPath of a multi instance integration node. Only used in conjunction with -e.
'-Q queueManagerDomainGroup' the Windows Domain Group that is used to secure the WebSphere MQ Queue Manager files in the sharedWorkPath of a multi instance integration node. Only used in conjunction with -e and if the queue manager does not exist and is to be created.
'-S autoStart' activates automatic startup of the integration node on system startup. Valid values that you can set are 'yes' and 'no'. The default is 'no'.

BIP8921
Changes the configuration of an integration node.
Severity
10 : Warning
Explanation
Syntax (for Microsoft Windows platforms):
mqsichangebroker integrationNodeName [[-i serviceUserId] -a servicePassword] [-q defaultQueueManager] [-t | -n] [-l userLilPath] [-g configurationChangeTimeout] [-k internalConfigurationTimeout] [-v statisticsMajorInterval] [-P httpListenerPort] [-c ICU converter path] [-y ldapPrincipal] [-z ldapCredentials] [-x userExitPath] [-e activeUserExits] [-s adminSecurity] [-f function level] [-b cachePolicy] [-r cachePortRange] [-S autoStart]


Command options:
'integrationNodeName' the name of the integration node to change.
'-i serviceUserId' the user ID that the integration node runs under and, by default, will be used to connect to external resources.
'-C CCSID' the default coded character set ID for the integration node.
'-a servicePassword' the password for the integration node user ID.
'-q defaultQueueManager' change the default queue manager for the integration node.
'-t' enables WebSphere MQ fastpath for this integration node (not supported on all platforms).
'-n' disables WebSphere MQ fastpath for this integration node.
'-l userLilPath' indicates where user-written LIL and JAR files are loaded from.
'-g configurationChangeTimeout' the maximum time (in seconds) allowed for a user configuration request to be processed.
'-k internalConfigurationTimeout' the maximum time (in seconds) allowed for an internal configuration change to be processed.
'-v statisticsMajorInterval' the time (in minutes) for the duration of the interval for collecting statistics archive records.
'-P httpListenerPort' the port that the integration node's HTTP listener uses.
'-c ICU converter path' delimited ';' list of paths to search for ICU converters or converter packages.
'-y ldapPrincipal' the LDAP Principal (user ID).
'-z ldapCredentials' the LDAP Credentials (password).
'-x userExitPath' the directory from which the integration node searches for all user exits. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.
'-e activeUserExits' the active user exits. By default, user exits are inactive. Adding a user exit name to this list changes its default state to active for this integration node. The default state can be overridden at the integration server or message flow level using the mqsichangeflowuserexits command. If a user exit name is specified and no library is found to provide that user exit when the integration server starts, a BIP8860 message is written to the system log and the integration server fails to start. The separator character for the list is ':'.
'-s adminSecurity' activates integration node administration security. Valid values that can be set are 'active' and 'inactive'.
'-f function level' the effective function level of the integration node, such as '7.0.0.1', '7.0.0.2', or 'all'
'-b cachePolicy' selects a policy to use for the cache manager. Built-in values that you can set are 'default', 'disabled' and 'none'. Alternatively, specify the absolute path to a cache policy file. The default value is 'disabled'.
'-r cachePortRange' selects a range of ports to be used by the cache manager. The value must be of the form 'startport-endport'. A valid range is generated by default.
'-S autoStart' activates automatic startup of the integration node on system startup. Valid values that you can set are 'yes' and 'no'. The default is 'no'.

BIP8922
Event source address <insert_1> was not found or is not configured.
Severity
20 : Error
Explanation
The event source address was specified in the -s parameter of the mqsichangeflowmonitoring command, but the event source was not found or is not configured.
Response
Issue the mqsireportflowmonitoring command with the -n and -a options to see details of event sources in the flow. Take corrective action and then reissue the mqsichangeflowmonitoring command.

BIP8923
The monitoring properties for the deployed message flow have not been updated.
Severity
20 : Error
Explanation
The deployed message flow cannot be updated because of errors that have already been reported.
Response
Correct the errors and then reissue the command.

BIP8924
The mqsireportbroker command displays integration node registry entries.
Severity
10 : Warning
Explanation
Syntax:
mqsireportbroker integrationNodeName


Command Options:
'integrationNodeName' the name of the integration node.

BIP8926
Integration node name <insert_1>
Severity
0 : Information
Explanation
Install path = <insert_2>
Work path = <insert_3>
Integration node UUID = <insert_4>
Process id = <insert_5>
Queue Manager = <insert_6>
User lil path = <insert_7>
User lil path64 = <insert_8>
User exit path = <insert_9>
User exit path64 = <insert_10>
Active user exits = <insert_11>
LDAP principal = <insert_12>
LDAP credentials = <insert_13>
ICU converter path = <insert_14>
Trusted (fastpath) Queue Manager application = <insert_15>
Configuration change timeout = <insert_16> seconds
Internal configuration timeout = <insert_17> seconds
Statistics major interval = <insert_18> minutes
Operation mode = <insert_19>
Fixpack capability level = <insert_20> (effective level <insert_21>)
Integration node registry format = <insert_22>
Administration security = <insert_23>

BIP8927
Integration node name <insert_1>
Severity
0 : Information
Explanation
Last mqsistart path = <insert_28>
mqsiprofile install path = <insert_2>
Work path = <insert_3>
Integration node UUID = <insert_4>
Process id = <insert_5>
Queue Manager = <insert_6>
User lil path = <insert_7>
User exit path = <insert_8>
Active user exits = <insert_9>
LDAP principal = <insert_10>
LDAP credentials = <insert_11>
ICU converter path = <insert_12>
Trusted (fastpath) Queue Manager application = <insert_13>
Configuration change timeout = <insert_14> seconds
Internal configuration timeout = <insert_15> seconds
Statistics major interval = <insert_16> minutes
Operation mode = <insert_17>
Fixpack capability level = <insert_18> (effective level <insert_19>)
Integration node registry format = <insert_20>
Administration security = <insert_21>
Multi-instance integration node = <insert_22>
Shared Work Path = <insert_23>
Start as WebSphere MQ Service = <insert_24>
HTTP listener port = <insert_25>
Cache manager policy = <insert_26>
Cache manager port range = <insert_27>
Integration registry hostname = <insert_29>
Default integration node CCSID = <insert_30>

BIP8928
Integration node name <insert_1>
Severity
0 : Information
Explanation
Last mqsistart path = <insert_25>
mqsiprofile install path = <insert_2>
Work path = <insert_3>
Integration node UUID = <insert_4>
Process id = <insert_5>
Queue Manager = <insert_6>
User lil path = <insert_7>
User lil path64 = <insert_8>
User exit path = <insert_9>
User exit path64 = <insert_10>
Active user exits = <insert_11>
LDAP principal = <insert_12>
LDAP credentials = <insert_13>
ICU converter path = <insert_14>
Configuration change timeout = <insert_15> seconds
Internal configuration timeout = <insert_16> seconds
Statistics major interval = <insert_17> minutes
Fixpack capability level = <insert_18> (effective level <insert_19>)
Integration node registry format = <insert_20>
Administration security = <insert_21>
HTTP listener port = <insert_22>
Cache manager policy = <insert_23>
Cache manager port range = <insert_24>
Integration registry hostname = <insert_26>

BIP8929
Integration node name <insert_1>
Severity
0 : Information
Explanation
IBM Support override trace = <insert_2>
IBM Support override trace size = <insert_3> bytes
IBM Support override integration server trace = <insert_4>
IBM Support override integration server trace size = <insert_5> bytes
IBM Support override integration server trace label = <insert_7>
IBM Support override integration server user trace level = <insert_6>

BIP8930
Integration node name <insert_1>
Severity
0 : Information
Explanation
Administration security = <insert_2>
Authorization mode = <insert_3>

BIP8931
Role = <insert_1>, Resource = <insert_2>, Permissions = <insert_3>
Severity
0 : Information

BIP8934
Verification failed. The installed Java level is 31-bit.
Severity
20 : Error
Explanation
The level of Java installed does not meet the minimum requirement; a 64-bit Java assembly is necessary.
Response
On z/OS, install the correct level of Java, and correct the BIPBPROF component profile. Submit BIPGEN to create the ENVFILE for the integration node.
On all other platforms, you must use the Java Virtual Machine that is supplied and installed with the integration node. In the mqsiprofile command, correct the MQSI_JREPATH and PATH environment variables, and the appropriate library path environment variables for your operating system.

BIP8935
Adds an integration node instance.
Severity
10 : Warning
Explanation
Syntax (for Linux and UNIX platforms):
&mqsiaddbrokerinstance. integrationNodeName [-w workPath] -e sharedWorkPath


Command Options:
'integrationNodeName' the name of the multi-instance integration node.
'-w workPath' the directory in which internal data, such as installation logs, component details, and trace output are written.
'-e sharedWorkPath' the directory in which registry and configuration data is shared between multiple instances of this integration node.

BIP8936
Adds an integration node instance.
Severity
10 : Warning
Explanation
Syntax (for Microsoft Windows platforms):
&mqsiaddbrokerinstance. integrationNodeName -i serviceUserId -a servicePassword [-w workPath] -e sharedWorkPath


Command Options:
'integrationNodeName' the name of the multi-instance integration node.
'-i serviceUserId' the user ID that the integration node runs under and that by default will be use to connect to external resources.
'-a servicePassword' the password for the integration node user ID.
'-w workPath' the directory in which internal data, such as installation logs, component details, and trace output are written.
'-e sharedWorkPath' the directory in which registry and configuration data is shared between multiple instances of this integration node.

BIP8937
Removes an integration node instance.
Severity
10 : Warning
Explanation
Syntax:
&mqsiremovebrokerinstance. integrationNodeName


Command Options:
'integrationNodeName' the name of the multi-instance integration node.

BIP8938
Changes an integration node's resource statistics options.
Severity
10 : Warning
Explanation
Syntax:
mqsichangeresourcestats integrationNodeSpec [-e integrationServerName] -c control [-w timeoutSecs] [-v traceFileName]
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.

Command Options:
'-e integrationServerName' integration server name. If not specified, the command acts upon all integration servers.
'-c control' starts or stops collection: values allowed are 'active' or 'inactive'.
'-w timeoutSecs' maximum number of seconds to wait for the integration node to respond (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP8939
Displays statistics settings.
Severity
10 : Warning
Explanation
Syntax:
mqsireportresourcestats integrationNodeSpec [-e integrationServerName] [-d detailLevel] [-w timeoutSecs] [-v traceFileName]

Command Options
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.
'-e integrationServerName' integration server name. If not specified, the command acts upon all integration servers.
'-d detailLevel' control how much information to display. Valid values are:
0 = display combined information (identical to previous versions of mqsireportresourcestats)
1 = display summary of configurable settings per integration server (default)
2 = display detailed information including non-configurable settings
'-w timeoutSecs' maximum number of seconds to wait for the integration node to respond (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP8940
Statistics collection for resource type <insert_1> in integration server <insert_2> is <insert_3>. Measurements: <insert_4>.
Severity
0 : Information

BIP8941
Statistics collection for resource type <insert_1> in integration server <insert_2> is <insert_3>.
Severity
0 : Information

BIP8942
Statistics resource measurements for <insert_1>: <insert_2>.
Severity
0 : Information

BIP8943
The -m flag was specified, but the original integration node was not created with the -w "workPath" option. Remove the -m flag and run the command again.
Severity
10 : Warning
Explanation
The -m flag is not allowed in this scenario.
Response
Remove the -m flag and run the command again.

BIP8944
Service trace is enabled for the integration node agent and HTTPListener - level: <insert_1>, mode: <insert_2>, size: <insert_3> KB.
Severity
0 : Information

BIP8945
Service trace settings for integration server <insert_1> - mode: <insert_2>, size: <insert_3> KB
Severity
0 : Information

BIP8946
Service trace is enabled for integration server <insert_1> with level <insert_2>.
Severity
0 : Information

BIP8947
Service trace is enabled for message flow <insert_1> with level <insert_2>.
Severity
0 : Information

BIP8948
User trace settings for integration server <insert_1> - mode: <insert_2>, size: <insert_3> KB
Severity
0 : Information

BIP8949
User trace is enabled for integration server <insert_1> with level <insert_2>.
Severity
0 : Information

BIP8950
User trace is enabled for message flow <insert_1> with level <insert_2>.
Severity
0 : Information

BIP8951
The following environment variable is set, which might affect current trace settings for the integration node - <insert_1> = <insert_2>.
Severity
0 : Information

BIP8952
Service trace is not enabled for integration node <insert_1>.
Severity
0 : Information

BIP8953
User trace is not enabled for integration node <insert_1>.
Severity
0 : Information

BIP8954
Service trace is enabled for the HTTPListener - level: <insert_1>, size: <insert_2>.
Severity
0 : Information

BIP8955
A multi-instance integration node <insert_1> cannot be created because it already exists in the shared workpath <insert_2>.
Severity
20 : Error
Explanation
The multi-instance integration node cannot be created because it already exists in the shared workpath.
Response
Either run the mqsiaddbrokerinstance command or delete the integration node.

BIP8960
Installs, uninstalls or lists Assemblies in Global Assembly Cache (GAC)
Severity
10 : Warning
Explanation
Syntax (1):
mqsiAssemblyInstall -i AssemblyName
Syntax (2):
mqsiAssemblyInstall -u AssemblyName
Syntax (3):
mqsiAssemblyInstall -l AssemblyName

Command Options:
'-i' installs an Assembly into the GAC
'-u' uninstalls an Assembly from the GAC
'-l' lists Assemblies that are installed in the GAC

BIP8961
The full .NET 4 framework in not installed or is not installed correctly.
Severity
30 : Severe error
Explanation
The full .NET 4 framework must be installed correctly before this command can be run.

BIP8962
The installation of the assembly into the Global Assembly Cache failed.
Severity
30 : Severe error
Explanation
The assembly could not be installed into the Global Assembly Cache.

BIP8963
The assembly could not be uninstalled from the the Global Assembly Cache.
Severity
30 : Severe error
Explanation
The uninstallation of the assembly from the Global Assembly Cache failed.

BIP8964
The listing of the assembly in the Global Assembly Cache failed.
Severity
30 : Severe error
Explanation
The assembly in the Global Assembly Cache failed could not be listed.

BIP8965
Use the mqsiwebuseradmin command to administer user accounts for the web user and RESTful interfaces.
Severity
10 : Warning
Explanation
Syntax:
mqsiwebuseradmin integrationNodeSpec [-c | -m | -d | -l] [-u username] [-a password | -x] [-r role] [-w timeout] [-v traceFileName]

Command options:
'integrationNodeSpec' is one of:
(a) 'integrationNodeName' : Name of a locally defined integration node
(b) '-n integrationNodeFileName' : File containing remote integration node connection parameters (*.broker)
(c) '[integrationNodeName] -i ipAddress -p port' : hostname and port of a remote integration node. 'integrationNodeName' optional for validation.
(d) '[integrationNodeName] -i uri' : URI for the remote integration node in the form tcp://[<user>[:<password>]@]<host>:<port>
If a user name and password are supplied, any URI Reserved characters in the password must be percent-encoded.

Also specify one of the following values:
'-c' : create web user account
'-m' : modify web user account
'-d' : delete web user account
'-l' : list web users

Specify the following options if required:
'-u username' : username to create/modify/delete
'-x' : No local password is to be stored. Use this option when the user is to be authenticated against an external password database.
'-a password' : local password for create/modify
'-r role' : role for create/modify
'-w timeoutSecs' : maximum number of seconds to wait for the integration node to respond (default is 60)
'-v traceFileName' : send verbose internal trace to the specified file.

BIP8966
Use the mqsifindmqpath command to find the path for a Websphere MQ install.
Severity
10 : Warning
Explanation
Syntax:
mqsifindmqpath integrationNodeName

Command options:

'integrationNodeName' : Name of the integration node to source the WebSphere MQ path for. Ommit to find the latest available install on the machine.

BIP8967
Failed to access the queue manager <insert_1> because the WebSphere MQ environment has not been set up.
Severity
20 : Error
Explanation
The WebSphere MQ environment must be set up for the command mqsicreatebroker to be able to use a queue manager. Run the setmqenv command from the install of the version of WebSphere MQ you want to use to use the queue manager.

BIP8968
Failed to create the queue manager <insert_1> because the WebSphere MQ environment is not supported. The WebSphere MQ environment is set to <insert_2>, but the integration node requires a minimum of WebSphere MQ version <insert_3>.
Severity
20 : Error
Explanation
The WebSphere MQ environment must be set up for the command mqsicreatebroker to be able to create a queue manager. Run the setmqenv command from the install of the version of WebSphere MQ you want to use to create the queue manager.

BIP8969
The version of WebSphere MQ that is installed for queue manager <insert_1> is not supported. The queue manager <insert_1> uses WebSphere MQ version <insert_2>, but the integration node requires a minimum of WebSphere MQ version <insert_3>.
Severity
20 : Error
Explanation
Migrate the WebSphere MQ queue manager to a supported version.

BIP8970
Starting WebSphere MQ service migration for component <insert_1>.
Severity
0 : Information
Explanation
The component is defined to run as a WebSphere MQ service. The WebSphere MQ service definition is being migrated for component <insert_1>.
Response
None.

BIP8971
Finished WebSphere MQ service migration for component <insert_1>.
Severity
0 : Information
Explanation
The WebSphere MQ service definition has been successfully migrated for component <insert_1>.
Response
None.

BIP8972
Removing the WebSphere MQ service definition for component <insert_1>.
Severity
0 : Information
Explanation
The integration node has been defined to run as a WebSphere MQ service but it is not possible to migrate the WebSphere MQ service definition to an earlier version. The definition will be removed, but you can redefine the integration node to run as a WebSphere MQ service using the mqsichangebroker command.
Response
To modify the migrated integration node to start as a WebSphere MQ service, use the mqsichangebroker command with the -d parameter. For example, 'mqsichangebroker MyIbnode -d defined'.

BIP8973
Finished removing the WebSphere MQ service definition for component <insert_1>. Use the mqsichangebroker command after migration to redefine the integration node to run as a WebSphere MQ service.
Severity
0 : Information
Explanation
The integration node has been defined to run as a WebSphere MQ service but it is not possible to migrate the WebSphere MQ service definition to an earlier version. The definition has been removed, but you can redefine the integration node to run as a WebSphere MQ service using the mqsichangebroker command.
Response
To modify the migrated integration node to start as a WebSphere MQ service, use the mqsichangebroker command with the -d parameter. For example, 'mqsichangebroker IBNODE -d defined'.

BIP8974
Component: <insert_1>, <insert_2>2
Severity
0 : Information

BIP8975
The value provided for the '-n' parameter is invalid.
Severity
20 : Error
Explanation
The resource name provided is invalid. For resources associated with the Kafka Consumer or Kafka Producer nodes the format of the resource name must be
kafka::KAFKA::<server_name>
Response
Correct and reissue the command.

BIP8980
Fix ID: <insert_1>1
Severity
0 : Information

BIP8981
This command creates an object associated with a type of configurable service.
Severity
10 : Warning
Explanation
Syntax:
mqsicreateconfigurableservice integrationNodeName -c configurableService -o object ( -n name -v value )
Command options:
'integrationNodeName': name of the integration node
'-c configurableService': configurable service type used by the integration node
'-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:
mqsideleteconfigurableservice integrationNodeName -c configurableService -o object
Command options:
'integrationNodeName': name of the integration node
'-c configurableService': a type of configurable service used by the integration node
'-o object': object name belonging to the type of configurable service

BIP8983
Configurable service object name <insert_1> 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_1> was not found.
Severity
10 : Warning
Explanation
The user has tried to delete or modify a configurable service object name that does not exist, or is not valid for UserDefined types.
Response
Check the names of the existing configurable services using the mqsireportproperties command. Then modify the external resource object name and reissue the command.

BIP8985
The integration node cannot detect the PSMODE for WebSphere MQ queue manager <insert_1>. Return code: <insert_2>.
Severity
0 : Information
Explanation
A failure occurred when the integration node queried the Publish Subscribe Mode for WebSphere MQ queue manager <insert_1>.
Response
Ensure that the queue manager is running. Review any other errors that are reported to identify the cause of the problem, then retry the operation.

BIP8986
A failure occurred when the integration node tried to update the PSMODE for WebSphere MQ queue manager <insert_1>. Return code: <insert_2>.
Severity
0 : Information
Explanation
The Publish Subscribe Interface (PSMODE) within WebSphere MQ for queue manager <insert_1> is currently set to ENABLED. This setting is incompatible with IBM Integration Bus in its default configuration. The integration node tried to change the PSMODE to COMPATIBILITY but the request failed.
Response
Ensure that the WebSphere MQ command server is running and is able to process PCF requests.

BIP8987
The command server for WebSphere MQ queue manager <insert_1> is not running. Return code: <insert_2>.
Severity
0 : Information
Explanation
The WebSphere MQ command server must be running on the queue manager that hosts an integration node. It is currently disabled.
Response
Check the status of the command server and start it if necessary.

BIP8988
The integration node cannot detect the version of WebSphere MQ that is installed for queue manager <insert_1>. Return code: <insert_2>.
Severity
0 : Information
Explanation
A failure occurred when the integration node queried the version of WebSphere MQ. The queue manager name that hosts the integration node is <insert_1>.
Response
Ensure that the queue manager is running. Review any other errors that are reported to identify the cause of the problem, then retry the operation.

BIP8989
The command completed with warnings.
Severity
0 : Information
Explanation
The command completed successfully but generated warnings.
Response
Check the warning messages previously issued by this command.

BIP8990
The integration node has detected that WebSphere MQ queue manager <insert_1> uses version <insert_2> which is not supported.
One of the following versions of WebSphere MQ must be used as the required minimum: <insert_3>.
Severity
20 : Error
Explanation
The integration node will not function using queue manager <insert_1> because the queue manager is using a version of WebSphere MQ that is not one of the supported versions.
Response
Check the product documentation for supported versions of WebSphere MQ, and compare this against the version of WebSphere MQ that is installed for queue manager <insert_1>. Migrate the WebSphere MQ queue manager to a supported version.

BIP8991
The integration node has detected that the PSMODE for WebSphere MQ queue manager <insert_1> is set to DISABLED. The PSMODE will be updated to COMPAT.
Severity
10 : Warning
Explanation
The Publish Subscribe Interface (PSMODE) within WebSphere MQ for the specified queue manager is currently set to DISABLED. This setting is incompatible with IBM Integration Bus. The integration node will change the PSMODE to COMPAT.
Response
If this message occurs more than once, identify what is causing the PSMODE to be set to DISABLED and correct the problem.

BIP8992
A failure occurred when the integration node tried to update the PSMODE for WebSphere MQ queue manager <insert_1>. Return code: <insert_2>.
Severity
20 : Error
Explanation
The Publish Subscribe Interface (PSMODE) within WebSphere MQ for the specified queue manager is currently set to DISABLED. This setting is incompatible with IBM Integration Bus. The integration node tried to change the PSMODE to COMPAT but the request failed.
Response
Ensure that the WebSphere MQ command server is running and is able to process PCF requests.

BIP8993
A component integrity check has failed.
Severity
20 : Error
Explanation
The command ran an integrity check on the component's configuration, and found errors. Previous messages indicate the errors found.
Response
Examine previous messages to determine the cause of the failure. Correct the errors, and rerun the command.

BIP8994
Access Denied. Administrator permissions are needed to use the selected options. Use an administrator command prompt to complete these tasks.
Severity
20 : Error
Response
Run the mqsicommandconsole command to get an elevated administrator command prompt, from which you can run this command.

BIP8995
The integration node could not determine the version of WebSphere MQ that is installed for queue manager <insert_1>.
One of the following versions of WebSphere MQ must be installed as the required minimum: <insert_2>.
Severity
20 : Error
Explanation
The integration node will not function using queue manager <insert_1> because the integration node cannot determine what version of WebSphere MQ the queue manager is using.
Response
Check the product documentation for supported versions of WebSphere MQ, and compare this against the version of WebSphere MQ that is installed for queue manager <insert_1>. Migrate the WebSphere MQ queue manager to a supported version.

BIP8996
Version: <insert_1>1
Severity
0 : Information

BIP8997
Product: <insert_1>1
Severity
0 : Information

BIP8998
Code Level: <insert_1>1
Severity
0 : Information

BIP8999
Build Type: <insert_1>, <insert_2> bit, <insert_3>3
Severity
0 : Information