BIP1000-1999: Runtime components - Configuration

BIP1001
Message associated with number <insert_1> was not found: data supplied <insert_2>.
Severity
30 : Severe error
Explanation
A message number was used for which no associated message text could be found.
Response
This is an internal error. Contact your IBM support center.

BIP1014
You cannot view broker <insert_1>.
Severity
30 : Severe error
Explanation
Administrative security has been enabled on this broker, and you do not have read authority on it. This is required in order to view the broker's properties or to see its list of available execution groups.
Response
Contact your broker administrator.

BIP1017
A backup archive called <insert_1> was created successfully.
Severity
0 : Information

BIP1018
Unexpected exception in utility <insert_1>; method <insert_2>.
Severity
30 : Severe error
Explanation
An exception was caught by the <insert_1> utility in method <insert_2>. The exception text is: <insert_3>. The current operation will end.
Response
For XML parser errors check the XML is well-formed and the correct encoding is specified.
Retry the operation if possible. If the exception still occurs, contact your IBM support center.

BIP1019
Resource <insert_1> of type <insert_4> could not be found in <insert_2> of type <insert_5> in parent <insert_3> of type <insert_6>.
Severity
20 : Error
Explanation
The utility was asked to access the named resource <insert_1>, but this is not deployed in the specified location.
Response
Check that the (case-sensitive) message flow name has been entered correctly. Use the Message Broker Toolkit to ensure that the message flow has been deployed successfully.

BIP1024
Starts message flows.
Severity
0 : Information
Explanation
Syntax:
mqsistartmsgflow brokerSpec (-g | -e egName) [[(-k applicationName | -z)] [-y libraryName] (-m flowName | -j)] [-w timeoutSecs] [-v traceFileName]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-g' all execution groups.
'-e egName' name of the execution group on which to start message flows. If this is not specified, all execution group processes are started.
'-z' starts all applications on the specified broker or execution group
'-k applicationName' name of the application to start or name of the application in which a message flow is in.
'-y libraryName' name of the library in which a message flow is in.
'-m flowName' name of the message flow to start
'-j' starts all message flows on the specified broker or execution group
'-w timeoutSecs' maximum number of seconds to wait for each object to start (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

Note: If -e or -g is specified without -m or -j then the start will only apply to execution groups. The saved run state of the message flow will be honoured on restart. Those that were in stopped state will remain in stopped state. Those that were in running state will be restarted.
Note: If -e is specified with -m or -j the execution group needs to be in running state. If the named execution group is in stopped state, the command will be rejected.
Note: Similar behavior will be observed with -g combined with -m or -j, in that if a stopped execution group is encountered then the start message flow request will not be processed. However, processing will continue until the command has been attempted on each execution group.
Note: When an execution group is in stopped state it is not possible to start or stop the message flows within it. An execution group needs to be in running state to process the start or stop message flow request, and so the only command a stopped execution group will accept is the request to start the execution group itself.

BIP1025
Stops message flows.
Severity
0 : Information
Explanation
Syntax:
mqsistopmsgflow brokerSpec (-g | -e egName) [[(-k applicationName | -z)] [-y libraryName] (-m flowName | -j)] [-w timeoutSecs] [-v traceFileName]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-g' all execution groups.
'-e egName' name of the execution group on which to stop message flows. If this is not specified, all execution groups on the broker are stopped.
'-z' stops all applications on the specified broker or execution group
'-k applicationName' name of the application to stop or name of the application in which a message flow is in.
'-y libraryName' name of the library in which a message flow is in.
'-m flowName' name of the message flow to stop
'-j' stops all message flows on the specified broker or execution group but leaves execution group processes running
'-w timeoutSecs' maximum number of seconds to wait for message flows to stop (default is 60)
'-v traceFileName' send verbose internal trace to the specified file

Note: If -e or -g is specified without -m or -j then the stop will only apply to execution groups. The current run state of the message flow will be saved ready for restart.
Note: When an execution group is in stopped state it is not possible to start or stop the message flows within it. An execution group needs to be in running state to process the start or stop message flow request, and so the only command a stopped execution group will accept is the request to start the execution group itself.

BIP1026
Modifying the security cache of broker <insert_1> execution group <insert_2>...
Severity
0 : Information

BIP1027
Starting message flow <insert_1> on execution group <insert_2> (Application <insert_3>, Library <insert_4>)...
Severity
0 : Information

BIP1028
Stopping message flow <insert_1> on execution group <insert_2> (Application <insert_3>, Library <insert_4>)...
Severity
0 : Information

BIP1030
Message flow <insert_1> on execution group <insert_2> is reported as started. (Application <insert_3>, Library <insert_4>)
Severity
0 : Information

BIP1031
Message flow <insert_1> on execution group <insert_2> is reported as stopped. (Application <insert_3>, Library <insert_4>)
Severity
0 : Information

BIP1033
Invalid parameters.
Severity
20 : Error
Explanation
The following flag(s) are invalid, missing, or cannot be used together: <insert_1>.
Response
Reissue the command specifying valid options and flags.

BIP1034
Properties file could not be read
Severity
20 : Error
Explanation
A utility was asked to read connection parameters from the properties file <insert_1> but this could not be found or was found to be invalid.
Response
Reissue the command specifying a valid path and file name. If such a file is not available, Use the Message Broker Toolkit to generate one, or supply the connection parameters individually.

BIP1035
Property missing from properties file.
Severity
30 : Severe error
Explanation
Property <insert_1> was not found in the properties file <insert_2>.
Response
Reissue the command with a valid properties file.

BIP1036
Broker port is not a number (<insert_1>).
Severity
30 : Severe error
Explanation
The supplied port value (<insert_1>) is not valid port number. This must be an integer value.
Response
Retry the command specifying a valid port number in the configuration or properties file.

BIP1038
The execution group <insert_1> does not exist in broker <insert_2>.
Severity
30 : Severe error
Response
Reissue the command specifying a valid execution group name.

BIP1039
Deploying BAR file <insert_3> to broker <insert_1> (execution group <insert_2>) ...
Severity
0 : Information

BIP1041
Broker connection parameters could not be found
Severity
20 : Error
Explanation
A CMP application could not connect to a broker because no connection parameters were provided. Furthermore, no default connection parameters could be determined.
Response
Reissue the command, specifying a valid set of broker connection parameters.

BIP1044
Connecting to the queue manager...
Severity
0 : Information

BIP1046
Unable to connect with the queue manager (<insert_1>).
Severity
20 : Error
Explanation
The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue.
Response
Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate.

BIP1047
The operation timed out waiting for a response.
Severity
20 : Error
Explanation
The utility did not receive an expected response from the broker within a designated amount of time. The operation might have completed successfully, even though the response was not received.
Response
Ensure that the broker is running and that the correct connection parameters have been supplied to the utility. Use the -w flag to increase the amount of time to wait for responses.

BIP1048
This command displays information about a broker archive (BAR) file.
Severity
0 : Information
Explanation
Syntax:
mqsireadbar -b barFileName [-r] [-v traceFileName] Command options:
'-b barFileName' The name of the BAR file to display.
'-r' Recursively display the contents of applications and libraries.
'-v traceFileName' Verbose internal trace is sent to the specified file.

BIP1049
The broker archive (bar) file does not exist.
Severity
20 : Error
Explanation
The bar file <insert_1> could not be found on the file system.
Response
Reissue the command specifying the location of a valid bar file.

BIP1050
The broker archive (bar) file could not be read from the file system.
Severity
20 : Error
Explanation
While the file was being read, the following error occurred: <insert_1>1
Response
Ensure that the file can be read by the current user, and that it is a valid broker archive. Correct the problem and reissue the command.

BIP1051
Reading Bar file using toolkit mqsireadbar...
Severity
0 : Information

BIP1052
Reading Bar file using runtime mqsireadbar...
Severity
0 : Information

BIP1053
The operation could not be completed by the broker: <insert_1>
Severity
20 : Error
Response
Ensure that the correct parameters are supplied to the broker and that the user is authorized to complete the operation. If the problem persists, contact your IBM support center.

BIP1054
The broker <insert_1> is not running.
Severity
20 : Error
Explanation
In order for the commandline utility to work, the broker needs to be running.
Response
Ensure that the broker is running and that the correct connection parameters have been supplied to the utility.

BIP1055
The broker archive (bar) file did not contain a top-level deployment descriptor.
Severity
10 : Warning
Explanation
The broker archive (bar) file did not contain a top-level deployment descriptor. The command-line options that were supplied to the command were not set to search for application or library level deployment descriptors. Any overrides have not been applied.
Response
Ensure the bar file contains a top-level deployment descriptor or repeat the command with either the -k, -y, or -r flags set.

BIP1058
The broker supplied the following message(s):
Severity
0 : Information

BIP1060
Connecting to the broker...
Severity
0 : Information

BIP1062
Removing the following objects from execution group <insert_2> (application <insert_3>, library <insert_4>):
<insert_1>1
Severity
0 : Information

BIP1063
Objects with the following name(s) could not be found on execution group <insert_2> (application <insert_3>, library <insert_4>):
<insert_1>1
Severity
10 : Warning

BIP1064
Removing message set <insert_1> from execution group <insert_2> ...
Severity
0 : Information

BIP1065
The CLASSPATH is incorrectly configured
Severity
30 : Severe error
Explanation
The utility was unable to start because a required set of Java classes could not be loaded from the CLASSPATH (<insert_1>).
Response
Add <insert_2> (from the installed product's classes directory) to the CLASSPATH environment variable and reissue the command.

BIP1071
The specified archive <insert_1> already exists.
Severity
30 : Severe error
Response
Reissue the command specifying a different archive name for the backup.

BIP1089
Ignoring the following name(s) as they are ambiguous on execution group <insert_2> (application <insert_3>, library <insert_4>):
<insert_1>1
Severity
10 : Warning

BIP1092
The broker successfully processed the deployment request.
Severity
0 : Information

BIP1093
The broker rejected the deployment request and reported the following error(s):
Severity
20 : Error

BIP1095
The broker has not yet responded to the deployment request.
Severity
10 : Warning
Explanation
The broker did not respond to the deployment request within a reasonable amount of time. The request is queued for processing and will be completed when the broker is able to do so.
Response
It is not usually necessary to repeat the deployment action. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time before this message is displayed.

BIP1113
The utility could not open file <insert_1> for writing trace output.
Severity
10 : Warning
Explanation
An attempt was made to open the file <insert_1> so that internal utility trace could be written there, but this was not successful.
Response
If the file already exists, ensure that it is not locked or in use by another application, and that the current user can write to it. If the file does not exist, ensure that the current user has the authority to write to the specified directory. Try specifying a different filename. If the problem persists, please contact your IBM support center.

BIP1115
Connected to the broker <insert_1>.
Severity
0 : Information

BIP1117
The execution group was created successfully.
Severity
0 : Information
Explanation
The broker has initialized the execution group.

BIP1121
Creates an execution group.
Severity
0 : Information
Explanation
Syntax:
mqsicreateexecutiongroup brokerSpec -e egName [-w timeoutSecs] [-v traceFileName]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-e egName' name of the new execution group
'-w timeoutSecs' maximum number of seconds to wait for the execution group to be created (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP1122
Deletes an execution group and all resources that are deployed to it.
Severity
0 : Information
Explanation
Syntax:
mqsideleteexecutiongroup brokerSpec -e executionGroupName [-w timeoutSecs] [-v traceFileName]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-e executionGroupName' name of the execution group to delete
'-w timeoutSecs' maximum number of seconds to wait for the execution group to be deleted (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP1123
The execution group already exists.
Severity
20 : Error
Explanation
The utility was asked to create execution group <insert_2> on broker <insert_1>, but it already exists.
Response
Check that the names of the execution group and broker are correct and reissue the command.

BIP1124
Creating execution group <insert_2> on broker <insert_1>...
Severity
0 : Information

BIP1125
The execution group could not be created.
Severity
20 : Error
Explanation
The utility was asked to create execution group <insert_2> on broker <insert_1>, but it was not completed successfully by the broker.
Response
Determine the cause of the problem by reviewing the following error messages. If the problem persists, contact your IBM support representative.

BIP1127
This command will implicitly remove the following resource(s): <insert_1>1
Severity
0 : Information

BIP1129
The execution group could not be deleted.
Severity
20 : Error
Explanation
The utility was asked to delete execution group <insert_2> on broker <insert_1>, but it was not completed successfully.
Response
Determine the cause of the problem by reviewing the following error messages. If the problem persists, contact your IBM support representative.

BIP1130
Deleting the execution group from broker <insert_1>...
Severity
0 : Information

BIP1134
The overrides file does not exist.
Severity
20 : Error
Explanation
The overrides file <insert_1> could not be found on the file system.
Response
Reissue the command specifying the location of a valid overrides file.

BIP1135
The overrides file could not be read from the file system.
Severity
20 : Error
Explanation
While the file was being read, the following error occurred: <insert_1>1
Response
Ensure that the file can be read by the current user, and that it is a valid overrides file. Correct the problem and reissue the command.

BIP1136
This command overrides properties in a broker archive file.
Severity
0 : Information
Explanation
Syntax:
mqsiapplybaroverride -b barFileName [-p overridesFile] [-m manualOverrides] [-k applicationName] [-y libraryName] [-r] [-o outputFile] [-v traceFileName] Command options:
'-b barFileName' The file name of the broker archive file (in zip format) to be overridden.
'-p overridesFile' The file name of the plain text file that contains one of these items: the broker properties to be overwritten, the entire new deployment descriptor, or a broker archive that contains the entire new deployment descriptor.
'-m manualOverrides' A comma separated list of key=value pairs that describe the overrides to apply. On Windows systems, the list must be enclosed in quotation marks (""). If used in conjunction with -p, the overrides that are specified with the -m parameter are performed after all overrides that are specified by the -p parameter have been made.
'-k applicationName' The name of the application to which the overrides will be applied.
'-y libraryName' The name of the library to which the overrides will be applied.
'-r' requests that overrides are applied recursively through applications and libraries.
'-o outputFile' The name of the output bar file to which the bar file changes are to be made. If this name is not specified, the input file is overwritten.
'-v traceFileName' Verbose internal trace is sent to the specified file.
Note: Overrides must be supplied either in the form FLOW#NODE.PROPERTY=NEWVALUE or in the form OLDVALUE=NEWVALUE. If the latter form is used, OLDVALUE must already be an overridden value in the deployment descriptor. Specify FLOW#NODE.PROPERTY on its own to remove an override.

BIP1137
Applying overrides using toolkit mqsiapplybaroverride...
Severity
0 : Information

BIP1138
Applying overrides using runtime mqsiapplybaroverride...
Severity
0 : Information

BIP1139
Replacing <insert_2> with <insert_1>...
Severity
0 : Information

BIP1140
Overriding property <insert_1> with <insert_2> in <insert_3> ...
Severity
0 : Information

BIP1141
Replacing <insert_3> occurrence(s) of value <insert_1> with <insert_2> in <insert_4> ...
Severity
0 : Information

BIP1142
Removing override for property <insert_1> in <insert_2> ...
Severity
0 : Information

BIP1143
Saving Bar file <insert_1>...
Severity
0 : Information

BIP1144
Ignoring property override <insert_1> in <insert_2>
Severity
10 : Warning
Explanation
The property override <insert_1> was ignored because it does not correspond to an existing property value that can be replaced, nor is it in the correct format for a property identifier.
Response
If the override was intended to be a property identifier, ensure that the format of the identifier is 'flow#node.property' or 'flow#property'. Use the mqsireadbar command to list the property names that can be overridden in a specific broker archive file. . If the override was intended to be a an existing property value, ensure that the property value is currently set in the deployment descriptor. If the value exists in the deployment descriptor, it may not have been found because it had already been set to something else earlier in the override processing. For example, if using mqsiapplybaroverride with both the -p and -m flags set, note that overrides specified through -p are made before overrides specified through -m. This means that the manual overrides will be made to a deployment descriptor that has already had any substitutions from the overrides file made. . If you are seeing this error message on the z/OS platform and are using an XML-based overrides file, ensure that the correct encoding is specified in the XML header.

BIP1145
The file <insert_1> could not be found in <insert_2>.
Severity
20 : Error
Explanation
A request was made to access the file <insert_1> in <insert_2> and this file could not be found.
Response
Check that the file is available in the target resource.

BIP1147
The broker archive (bar) file <insert_1> could not be written.
Severity
20 : Error
Explanation
The system tried to update the broker archive, but could not write to the bar file. This might be because the file, if it already exists, is read-only, or because the file system is write-protected.
Response
Ensure that the bar file can be written to, and reissue the command.

BIP1148
The broker archive (bar) file <insert_1> could not be read.
Severity
20 : Error
Response
Ensure that the bar file can be read, and reissue the command.

BIP1181
Starting all message flows on execution group <insert_1> (Application <insert_2>, Library <insert_3>)...
Severity
0 : Information

BIP1182
All message flows on execution group <insert_1> started successfully. (Application <insert_2>, Library <insert_3>)
Severity
0 : Information

BIP1183
Stopping all message flows on execution group <insert_1> (Application <insert_2>, Library <insert_3>)...
Severity
0 : Information

BIP1184
All message flows on execution group <insert_1> stopped successfully. (Application <insert_2>, Library <insert_3>)
Severity
0 : Information

BIP1185
You cannot view execution group <insert_2> on broker <insert_1>.
Severity
30 : Severe error
Explanation
Administrative security has been enabled on this broker, and you do not have read authority to the execution group <insert_2>. This is required in order to view the execution group's properties or to see its list of available message flows.
Response
Contact your broker administrator.

BIP1186
Starting the execution group <insert_1>...
Severity
0 : Information

BIP1187
The execution group <insert_1> is reported as started.
Severity
0 : Information

BIP1188
Stopping the execution group <insert_1>...
Severity
0 : Information

BIP1189
The execution group <insert_1> is reported as stopped.
Severity
0 : Information

BIP1190
The file <insert_1> is not a valid broker archive.
Severity
20 : Error
Explanation
The utility was asked to deploy <insert_1> but the file is not in the correct format. The file was not deployed.
Response
Use the Message Broker Toolkit or mqsicreatebar command to generate a Bar file and try the command again.

BIP1191
The file <insert_1> could not be read.
Severity
20 : Error
Explanation
The utility was asked to deploy <insert_1> but the file could not be read. The file was not deployed.
Response
Ensure that the file exists and that the current user has authority to read it.

BIP1192
Starting application <insert_1> on execution group <insert_2>...
Severity
0 : Information

BIP1193
Stopping application <insert_1> on execution group <insert_2>...
Severity
0 : Information

BIP1194
Application <insert_1> on execution group <insert_2> is reported as started.
Severity
0 : Information

BIP1195
Application <insert_1> on execution group <insert_2> is reported as stopped.
Severity
0 : Information

BIP1196
Starting all applications on execution group <insert_1>...
Severity
0 : Information

BIP1197
All applications on execution group <insert_1> started successfully.
Severity
0 : Information

BIP1198
Stopping all applications on execution group <insert_1>...
Severity
0 : Information

BIP1199
All applications on execution group <insert_1> stopped successfully.
Severity
0 : Information

BIP1251
Creates a backup file for the specified broker.
Severity
0 : Information
Explanation
Syntax:
mqsibackupbroker brokerName -d directory [-a archiveName] [-f] [-v traceFileName]

Command Options:
'brokerName' name of broker to backup.
'-d directory' name of the directory the backup file will be written to.
'-a archiveName' name of the file (defaults to 'brokerName_yyMMdd_HHmmss.zip')
'-f' force incomplete backup files to be created if any part of the broker's configuration cannot be read
'-v traceFileName' send verbose internal trace to the specified file.

BIP1252
Creating backup file <insert_2> for broker <insert_1>.
Severity
0 : Information

BIP1253
Failed to backup the broker <insert_1> (error <insert_2>)
Severity
30 : Severe error
Explanation
At least one file in the broker's configuration could not be backed up.
Response
Check user access to the backup or restore directory and reissue the command. If this problem persists contact your IBM support center.

BIP1254
The broker <insert_1> cannot be found.
Severity
30 : Severe error
Explanation
In order to backup or restore a broker's configuration, a broker of that name must first exist on the machine on which the command is run.
Response
Check that the name of the broker has been entered correctly and that the broker has been created successfully.

BIP1255
The directory <insert_1> cannot be written to.
Severity
30 : Severe error
Response
Reissue the command specifying a valid directory for the backup file.

BIP1256
A backup of the broker's configuration could not be created because the broker is using an external system database (FADLevel=<insert_1>)
Severity
20 : Error
Explanation
A backup of the broker's configuration cannot be taken because the broker is not of the required version. The command was run against a version of the broker that requires a system database, which cannot be backed up using this command.
Response
Consult the documentation for the existing version of the broker for information on how to back it up.

BIP1257
Could not back up the file <insert_1>. (Error: <insert_2>)
Severity
10 : Warning

BIP1258
The backup file that was created for broker <insert_1> is incomplete; the following number of files are missing: <insert_2>
Severity
10 : Warning
Explanation
A backup file was created but it might not contain sufficient information to allow it to be successfully restored.
Response
Previous messages show which files could not be backed up. If you are sure that these files are not a necessary part of the broker's configuration, this error can be ignored. If any of the missing files are required, or if you are unsure as to whether they are required, determine why the file cannot be read and retry the command. If possible, stop the broker before retrying the command.

BIP1259
A backup for broker <insert_1> could not be created because the following number of files could not be backed up: <insert_2>
Severity
20 : Error
Explanation
A backup file was not created because it might not contain sufficient information to allow it to be successfully restored.
Response
Previous messages show which files could not be backed up. Investigate why these files could not be backed up, fix the problem and try again. If you are sure that the failed files are not a necessary part of the broker's configuration, rerun the command using the -f flag to force the creation of an incomplete backup. If possible, stop the broker before retrying the command.

BIP1260
Restoring from an incomplete backup.
Severity
10 : Warning
Explanation
When the backup file was created, the following files were not backed up: <insert_1>1 The broker might not work as expected.

BIP1261
Restores a broker's configuration from a backup file.
Severity
0 : Information
Explanation
Syntax:
mqsirestorebroker brokerName -d directory -a archiveName [-c] [-v traceFileName]

Command Options:
'brokerName' name of the broker that will be overwritten
'-d directory' name of the directory the backup file will be read from
'-a archiveName' name of the backup file to restore
'-c' restores common configuration. If this flag is specified, the command will additionally restore configuration from the backup file which might be shared with other brokers on the same machine (for instance, profiles)
'-v traceFileName' send verbose internal trace to the specified file.

BIP1262
Could not delete the existing configuration of broker <insert_1>.
Severity
30 : Severe error
Explanation
In order to restore the broker's configuration, it is first necessary to delete any existing configuration files for the broker. At least one file from this configuration could not be deleted. Previous message(s) describe which file(s) could not be deleted.
Response
Check that the broker is not running. Check that the current user has authority to read the file and write to the directory described by the environment variable MQSI_REGISTRY and try the command again. If the problem persists contact your IBM support center.

BIP1263
Failed to restore the broker <insert_1>. (Error = <insert_2>)
Severity
30 : Severe error
Explanation
At least one file in the broker's configuration could not be restored. The broker might be in an inconsistent state.
Response
Check that the broker is not running. Check that the current user has authority to read the file and write to the directory described by the environment variable MQSI_REGISTRY and try the command again. If the problem persists contact your IBM support center.

BIP1264
The file <insert_1> cannot be found or is not a valid broker backup file.
Severity
30 : Severe error
Response
Reissue the command specifying a valid path and file name for the backup file.

BIP1265
An error occurred while restoring the file <insert_1>: <insert_2>
Severity
30 : Severe error
Explanation
It was not possible to restore the broker's configuration. The broker might be in an inconsistent state.
Response
Ensure that the broker is not running. Check that the current user has the necessary permissions to write to the filesystem and that there is sufficient disk space available. Correct the problem and run the command again.

BIP1266
Deleting the existing configuration of broker <insert_1> ...
Severity
0 : Information

BIP1267
Restoring all configuration information from backup archive <insert_1>...
Severity
0 : Information

BIP1268
Restoring broker configuration information from backup archive <insert_1>...
Severity
0 : Information

BIP1269
Could not delete <insert_1>.
Severity
30 : Severe error

BIP1274
Library <insert_1> is deployed to execution group <insert_2>. (Application <insert_8>)
Severity
0 : Information
Explanation
Deployed: <insert_3> in BAR file <insert_4>
Last edited: <insert_5>
Long description: <insert_6>
Keywords: <insert_7>7

BIP1275
Application <insert_1> on execution group <insert_2> is running.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Long description: <insert_6>
Keywords: <insert_7>7

BIP1276
Application <insert_1> on execution group <insert_2> is stopped.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Long description: <insert_6>
Keywords: <insert_7>7

BIP1277
Message flow <insert_1> on execution group <insert_2> is running. (Application <insert_10>, Library <insert_11>)
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
Start mode: <insert_13>
UUID: <insert_12>
Long description: <insert_9>
User-defined property names: <insert_7>7
Keywords: <insert_8>8

BIP1278
Message flow <insert_1> on execution group <insert_2> is stopped. (Application <insert_10>, Library <insert_11>)
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
Start mode: <insert_13>
UUID: <insert_12>
Long description: <insert_9>
User-defined property names: <insert_7>7
Keywords: <insert_8>8

BIP1280
The number of WebSphere Message Broker runtime installations on this machine is <insert_1>.
Severity
0 : Information
Explanation
<insert_2>2

BIP1281
No brokers have been defined on this machine.
Severity
0 : Information

BIP1282
No execution groups have been defined on broker <insert_1>.
Severity
0 : Information

BIP1283
There is nothing deployed to execution group <insert_1>.
Severity
0 : Information

BIP1284
Broker <insert_1> on queue manager <insert_2> is running.
Severity
0 : Information
Explanation
Broker version: <insert_3> (build <insert_4>)
Platform: <insert_5>, <insert_6>, <insert_7>
Process ID: <insert_8>
Short description: <insert_9>
Long description: <insert_10>

BIP1285
Broker <insert_1> on queue manager <insert_2> is stopped.
Severity
0 : Information
Response
Start the broker for more information.

BIP1286
Execution group <insert_2> on broker <insert_1> is running.
Severity
0 : Information
Explanation
Number of message flows that are enabled to run: <insert_3>.
Number of applications that are enabled to run: <insert_8>.
Process ID: <insert_4>
UUID: <insert_5>
Short description: <insert_6>
Long description: <insert_7>

BIP1287
Execution group <insert_2> on broker <insert_1> is stopped.
Severity
0 : Information
Explanation
Number of message flows that will start with the execution group: <insert_3>.
Number of applications that will start with the execution group: <insert_8>.
UUID: <insert_5>
Short description: <insert_6>
Long description: <insert_7>

BIP1288
Message flow <insert_1> on execution group <insert_2> is running.
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
UUID: <insert_10>
Start mode: <insert_11>
Long description: <insert_9>
User-defined property names: <insert_7>7
Keywords: <insert_8>8

BIP1289
Message flow <insert_1> on execution group <insert_2> is stopped.
Severity
0 : Information
Explanation
Additional thread instances: <insert_3>
Deployed: <insert_4> in Bar file <insert_5>
Last edited: <insert_6>
UUID: <insert_10>
Start mode: <insert_11>
Long description: <insert_9>
User-defined property names: <insert_7>7
Keywords: <insert_8>8

BIP1290
File <insert_1> is deployed to execution group <insert_2>.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
Keywords: <insert_6>6

BIP1291
Lists brokers and their properties.
Severity
0 : Information
Explanation
Syntax:
mqsilist ([-a] | brokerSpec [-e egName [-k applicationName] [-y libraryName]]) [-r] [-d detailLevel] [-w timeoutSecs] [-v traceFileName]

Command Options:
'-a' list brokers of all versions on this machine (not applicable on z/OS)
'brokerSpec' list execution groups configured for a broker; is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-e egName' list deployed objects configured for an execution group.
'-k applicationName' list deployed objects configured for an application.
'-y libraryName' list deployed objects configured for a library.
'-r' recursive (display information on subcomponents, ignored for -d 0)
'-d detailLevel' control how much information to display. Valid values are:
0 = display minimal information (identical to older versions of mqsilist)
1 = display one-line summary per object (default)
2 = display detailed information
'-w timeoutSecs' maximum number of seconds to wait for any broker to respond (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.

BIP1292
The multi-instance or High Availability Broker <insert_1> on queue manager <insert_2> has stopped.
Severity
0 : Information
Response
Start the broker for more information.

BIP1293
Broker <insert_1> is a multi-instance broker running in standby mode on queue manager <insert_2>.
Severity
0 : Information

BIP1294
Broker <insert_1> is a multi-instance broker running in standby mode on queue manager <insert_2>.
More information will be available when the broker instance is active.
Severity
0 : Information
Explanation
Broker version: <insert_3> (build <insert_4>)
Platform: <insert_5>, <insert_6>, <insert_7>
Process ID: <insert_8>
Short description: <insert_9>
Long description: <insert_10>

BIP1295
Broker <insert_1> is an active multi-instance or High Availability broker running on queue manager <insert_2>.
Severity
0 : Information
Explanation
Broker version: <insert_3> (build <insert_4>)
Platform: <insert_5>, <insert_6>, <insert_7>
Process ID: <insert_8>
Short description: <insert_9>
Long description: <insert_10>

BIP1296
Broker <insert_1> is stopped. It is a multi-instance broker and will be started as a WebSphere MQ service by queue manager <insert_2>.
Severity
0 : Information

BIP1297
Broker <insert_1> is a multi-instance broker running in standby mode on queue manager <insert_2>.
Severity
0 : Information

BIP1298
Broker <insert_1> is stopped. It will be started as a WebSphere MQ service by queue manager <insert_2>.
Severity
0 : Information

BIP1299
File <insert_1> is deployed to execution group <insert_2>. (Application <insert_7>, Library <insert_8>)
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
Keywords: <insert_6>6

BIP1801
Views or changes modes of operation
Severity
0 : Information
Explanation
Syntax:
mqsimode brokerSpec [-o operationMode] [-w timeoutSecs] [-v traceFileName] [-x modeExtensions]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-o operationMode' new operation mode to set, from the list below. If -o is not supplied, the command displays mode information for the broker.
'-x modeExtensions' comma-separated list of mode extensions
'-w timeoutSecs' maximum number of seconds to wait for the broker to respond (default is 60)
'-v traceFileName' send verbose internal trace to the specified file.
Available modes of operation: <insert_1>1

BIP1802
Broker <insert_1> is in <insert_2> mode.
Severity
0 : Information

BIP1803
The trial period for broker <insert_1> expires on <insert_2>.
Severity
0 : Information

BIP1804
Broker <insert_1> does not have mode information set (assuming <insert_2>).
Severity
0 : Information

BIP1805
The mode for broker <insert_1> has been changed to <insert_2>.
Severity
0 : Information

BIP1808
Broker <insert_1> is not at the required software level to change the mode.
Severity
10 : Warning
Explanation
Brokers created before V6.1.0.2 must be upgraded before the mode can be changed.
Response
Upgrade broker <insert_1> to at least V6.1.0.2 and reissue the command.

BIP1809
Changing the mode of broker <insert_1> to <insert_2>...
Severity
0 : Information

BIP1810
The mode of the broker has not yet changed; the mode is currently being reported as <insert_1>.
Severity
10 : Warning
Explanation
The broker was was not able to process the request to change the mode within a reasonable amount of time. The request is queued for processing and will be completed when the broker is able to do so.
Response
It is not usually necessary to repeat the command. Increasing the value of the timeout period (-w) will allow the utility to wait for a longer period of time before this message is displayed.

BIP1815
Broker <insert_1> is set to mode of operation <insert_2>, which is not valid. Correct the mode of operation.
Severity
20 : Error

BIP1821
WARNING: Broker <insert_1> is in <insert_2> mode but has <insert_3> execution groups, which exceeds the allowed maximum for this mode.
Severity
10 : Warning

BIP1822
WARNING: Broker <insert_1> is in <insert_2> mode but has <insert_3> message flows deployed, which exceeds the allowed maximum for this mode.
Severity
10 : Warning

BIP1823
WARNING: Broker <insert_1> has a message flow called <insert_4> (Application <insert_6>, Library <insert_7>) in execution group <insert_5> , which contains one or more nodes that are not valid in this mode: <insert_3>.
Severity
10 : Warning

BIP1824
WARNING: The trial period for broker <insert_1> expired on <insert_2>.
Severity
10 : Warning

BIP1825
Cannot create execution group <insert_2> on broker <insert_1> because the broker is running in <insert_3> mode, which supports a maximum of <insert_4> execution groups.
Severity
20 : Error
Explanation
The execution group cannot be created because the maximum number of execution groups for the mode of the target broker has been reached, and creating the execution group causes this limit to be exceeded.
Response
Reuse an existing execution group, or delete an existing execution group and try the command again. Alternatively, contact your IBM representative to upgrade your license.

BIP1826
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but the broker is running in <insert_3> mode which limits the number of message flows that can exist at any one time. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it causes the broker to run more message flows than are valid for the current mode of the target broker.
Response
Delete message flows from the broker and try the command again. Alternatively, contact your IBM representative to upgrade your license.

BIP1827
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but the broker is running in <insert_3> mode which has a restriction on the types of node that can be deployed. The bar file cannot be deployed. The set of node types found in the bar file that are not valid are: <insert_4>.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains nodes that are not valid for the current mode of the target broker.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.

BIP1828
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but the trial period for the broker has expired. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The target broker is running in a trial mode that has expired.
Response
Contact your IBM representative. If you have already purchased a valid license for the target broker, change the broker to the correct mode by using the mqsimode command.

BIP1829
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but the broker is running in <insert_3> mode which limits the number of execution groups that can exist at any one time. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because the maximum number of execution groups for the mode of the target broker has been reached.
Response
Delete an existing execution group and try the command again. Alternatively, contact your IBM representative to upgrade your license.

BIP1830
Changing the mode extensions of broker <insert_1> to <insert_2>...
Severity
0 : Information

BIP1831
Broker <insert_1> has mode extensions <insert_2>.
Severity
0 : Information

BIP1832
WARNING: Broker <insert_1> has a message flow called <insert_3> (Application <insert_5>, Library <insert_6>) in execution group <insert_4> which requires broker extension <insert_2> to be enabled.
Severity
10 : Warning

BIP1833
WARNING: Broker <insert_1> has a message flow called <insert_4> (Application <insert_6>, Library <insert_7>) in execution group <insert_5>, which contains one or more nodes that are not valid with broker extensions <insert_2>: <insert_3>.
Severity
10 : Warning

BIP1834
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but a flow (name <insert_4>) within the bar file requires extension <insert_3> to be enabled in the broker. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains a flow that is not valid for the current mode of the target broker.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.

BIP1835
You attempted to deploy a broker archive (bar) file to execution group <insert_2> on broker <insert_1>, but a flow within the bar file contains a node of type <insert_4> that requires extension <insert_3> to be enabled in the broker. The bar file cannot be deployed.
Severity
20 : Error
Explanation
The bar file cannot be deployed because it contains a flow that is not valid for the target broker.
Response
Rework your message flow to use nodes that are valid in the current mode. Alternatively, contact your IBM representative to upgrade your license.

BIP1836
You attempted to deploy a broker archive (BAR) file to the execution group named <insert_2> on the broker named <insert_1>. The broker is running in <insert_3> mode, which restricts the types of file that can be deployed to it. The BAR file could not be deployed because it contains the following restricted file types: <insert_4>.
Severity
20 : Error
Explanation
The BAR file could not be deployed because it contains one or more file types that are not valid for the current mode of the target broker.
Response
If the restricted file type is 'ESQL', and you are using an ESQL node that can be deployed to the current mode of the target broker, select "In-line ESQL into the compiled flow" in the BAR file that you want to deploy. Alternatively, contact your IBM representative to upgrade your license.

BIP1837
WARNING: The execution group <insert_3> on broker <insert_1> contains the resource <insert_2> (Application <insert_5>, Library <insert_6>). This resource is not valid in the current operation mode of the broker. The operation mode of the broker is currently set to <insert_4>.
Severity
10 : Warning

BIP1838
Package a broker archive file from source.
Severity
0 : Information
Explanation
Syntax:
mqsipackagebar -a barName [-w rootLocation]
[-o filePath1 [filePath2 [...]]]
[-k applicationName [...]] [-y libraryName [...]] [-n appDomainName [...]]
[-u|-d] [-i] [-v traceFileName]
Command options:
'-a barName' bar file name to create or replace (Mandatory).
'-w rootLocation' root location. If not specified, the default working directory is used.
'-o filePath1' relative path (including the project) of deployable files to add to the broker archive. Multiple deployable files can be packaged in a single mqsipackagebar command (optional).
'-k applicationName' specify application projects containing files to link (optional, multiple projects can be specified).
'-y libraryName' specify library projects containing files to link (optional, multiple projects can be specified).
'-n appDomainName' specify .NET application domain projects containing files to link (optional, multiple projects can be specified).
'-u' update an existing bar file. If the bar file does not exist, a new one is created. Use with -o, -k, -y, or -n options.
'-d' delete elements from an existing bar file. Use the -k, -y, and -n options to specify the elements to delete.
'-i' include all supported and unsupported element types.
'-v traceFileName' specify the trace file name or path where the tracing data is written to. If only file name or relative path is specified then the file is written to the current working directory.

BIP1839
<insert_1> not specified.
Severity
30 : Severe error

BIP1840
No valid resources found to add to the BAR file. Check that rootLocation is correct and specify at least one resource by using one or more of the -k, -y, -n, or -o options.
Severity
30 : Severe error

BIP1841
<insert_1> is not a valid traceFilePath.
Severity
30 : Severe error

BIP1842
Cannot open trace file <insert_1>. Error: <insert_2>.
Severity
30 : Severe error

BIP1843
The trace file <insert_1> is read-only.
Severity
30 : Severe error

BIP1844
Unexpected end of argument reached.
Severity
30 : Severe error

BIP1845
Command completed successfully.
Severity
0 : Information

BIP1846
The update option (-u) and the delete option (-d) cannot be used simultaneously.
Severity
30 : Severe error

BIP1847
The broker archive file <insert_1> does not exist.
Severity
30 : Severe error

BIP1848
The <insert_1> file contains an unsupported node: <insert_2>.
Severity
30 : Severe error
Explanation
The node type is not supported in a message flow.
Response
Remove the node from the message flow and try again.

BIP1849
The application <insert_1> references project <insert_2> which does not exist.
Severity
10 : Warning

BIP1850
Running command: mqsipackagebar
Severity
0 : Information

BIP1851
Command arguments: <insert_1>
Severity
0 : Information

BIP1852
Processing file <insert_1>.
Severity
0 : Information

BIP1853
Application file <insert_1> successfully added to the broker archive.
Severity
0 : Information

BIP1854
Application contents:
Severity
0 : Information

BIP1855
Library file <insert_1> successfully added to the broker archive.
Severity
0 : Information

BIP1856
Library contents:
Severity
0 : Information

BIP1857
Application domain file <insert_1> successfully added to the broker archive.
Severity
0 : Information

BIP1858
Application domain contents:
Severity
0 : Information

BIP1859
Successfully added file <insert_1> to the broker archive.
Severity
0 : Information

BIP1860
Successfully deleted file <insert_1> from the broker archive.
Severity
0 : Information

BIP1861
Elapsed time: <insert_1> second(s).
Severity
0 : Information

BIP1862
Ignoring invalid or missing resource: <insert_1>
Severity
10 : Warning

BIP1863
Command completed with warnings.
Severity
10 : Warning

BIP1864
The generated broker archive file does not contain any Message Broker deployable files.
Severity
10 : Warning

BIP1865
<insert_1> is not added to the BAR file because it contains no deployable resources. To create deployable resources for Java code or message sets, use theámqsicreatebar -compileOnly command.
Severity
10 : Warning

BIP1866
The referenced project <insert_1> contains no deployable resources. To create deployable resources for Java code or message sets, use theámqsicreatebar -compileOnly command.
Severity
10 : Warning

BIP1867
Cannot add <insert_1> to the BAR file, because this flow is already in the BAR file as a compiled (.cmf) file. Delete <insert_2> from the BAR file by using the -d option and try again.
Severity
10 : Warning

BIP1868
Ignoring <insert_1>, which is in application <insert_2>. Use the -k option to include the application.
Severity
10 : Warning

BIP1869
Ignoring <insert_1>, which is in library <insert_2>. Use the -y option to include the library.
Severity
10 : Warning

BIP1870
Ignoring <insert_1>, which is in .NET application domain project <insert_2>. Use the -n option to include the application domain project.
Severity
10 : Warning

BIP1875
Service <insert_1> on execution group <insert_2> is running.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Long description: <insert_6>
Keywords: <insert_7>7

BIP1876
Service <insert_1> on execution group <insert_2> is stopped.
Severity
0 : Information
Explanation
Deployed: <insert_3> in Bar file <insert_4>
Last edited: <insert_5>
UUID <insert_8>
Start mode: <insert_9>
Long description: <insert_6>
Keywords: <insert_7>7