5000-5999 - Installable services
See Reading a message for an explanation of how to interpret these messages.
AMQ5005
Unexpected error
Severity:
20 : Error
Explanation:
An unexpected error occurred in an internal function of the product.
Response:
Save the generated output files and contact your IBM support center.
AMQ5006
Unexpected error: rc = <insert_1>
Severity:
20 : Error
Explanation:
An unexpected error occurred in an internal function of the product.
Response:
Save the generated output files and contact your IBM support center.
AMQ5008
An essential WebSphere MQ process <insert_1> (<insert_3>) cannot be found and is assumed to be terminated.
Severity:
40 : Stop Error
Explanation:
1) A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible it has terminated the process so that a new process can be created.
Response:
WebSphere MQ will stop all MQ processes. Inform your systems administrator. When the problem is rectified WebSphere MQ can be restarted.
AMQ5009
WebSphere MQ agent process <insert_1> has terminated unexpectedly.
Severity:
40 : Stop Error
Explanation:
WebSphere MQ has detected that an agent process has terminated unexpectedly. The queue manager connection(s) that this process is responsible for will be broken.
Response:
Use any previous FFSTs to determine the reason for the failure. Try to eliminate the following reasons before contacting your IBM support center.
1) A user has inadvertently terminated the process.
2) The system is low on resources. Some operating systems terminate processes to free resources. If your system is low on resources, it is possible that the operating system has terminated the process so that a new process can be created.AMQ5010
The system is restarting the WorkLoad Management Server process.
Severity:
10 : Warning
Explanation:
The system has detected that the WorkLoad Management server process (amqzlwa0, pid:<insert_1>) has stopped and is restarting it.
Response:
Save the generated output files which may indicate the reason why the WorkLoad Management process stopped. If the reason the WorkLoad Management Server process stopped is a problem in a WorkLoad Management user exit, correct the problem, otherwise contact your IBM support center.
AMQ5011
The Queue Manager ended for reason <insert_1> <insert_3>
Severity:
10 : Warning
Explanation:
The Queue Manager ended because of a previous error <insert_1> or <insert_3>
Response:
This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information.
AMQ5019
Unable to access program <insert_3>.
Severity:
40 : Stop Error
Explanation:
A request was made to execute the program <insert_3>, however the operation was unsuccessful because the program could not be found in the specified location.
Response:
Check the definition of the service specifies the correct and full path to the program to run. If the path is correct then verify that the program exists in the specified location and that WebSphere MQ userid has permission to access it.
AMQ5020
Permission denied attempting to execute program <insert_3>.
Severity:
40 : Stop Error
Explanation:
A request was made to execute the program <insert_3>, however the operation was unsuccessful because the WebSphere MQ operating environment has insufficient permissions to access the program file.
Response:
Check the access permissions of the of the program to be executed and if necessary alter them to include execute permission for the WebSphere MQ userId. Also check that the WebSphere MQ userId has search access on all directories which compose the path to the program file.
AMQ5021
Unable to start program <insert_3>.
Severity:
40 : Stop Error
Explanation:
A request was made to execute the program <insert_3> however the operation was unsuccessful. Reasons for the failure may include
a shortage of available system resources
a problem with the program to be started
Response:
If the problem persists then the WebSphere MQ error logs should be consulted for further information related to this error. The Operating System error recording facilities should also be consutled for information relating to shortage of system resources.
AMQ5022
The Channel Initiator has started. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Channel Initiator process has started.
Response:
None.
AMQ5023
The Channel Initiator has ended. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Channel Initiator process has ended.
Response:
None.
AMQ5024
The Command Server has started. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Command Server process has started.
Response:
None.
AMQ5025
The Command Server has ended. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Command Server process has ended.
Response:
None.
AMQ5026
The Listener <insert_3> has started. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Listener process has started.
Response:
None.
AMQ5027
The Listener <insert_3> has ended. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Listener process has ended.
Response:
None.
AMQ5028
The Server <insert_3> has started. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Server process has started.
Response:
None.
AMQ5029
The Server <insert_3> has ended. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Server process has ended.
Response:
None.
AMQ5030
The Command <insert_3> has started. ProcessId(<insert_1>).
Severity:
0 : Information
Explanation:
The Command has started.
Response:
None.
AMQ5032
Error (<insert_4>) accessing file <insert_3>.
Severity:
40 : Stop Error
Explanation:
While attempting to access the file <insert_3> the error <insert_4> occurred.
Response:
Use the information contained in the error to locate and correct the cause of the failure.
AMQ5036
Error detected processing line <insert_1>, position <insert_2> in service environment file.
Severity:
40 : Stop Error
Explanation:
While processing the environment file <insert_3> an error was detected on line <insert_1> at position <insert_2>. Possible causes are
Variable name too long
Variable value too long
Incorrectly formed line. Lines must be in the format <name>=<value>. There should be no blank characters in name field. All characters following the '=' are part of the value field.
Response:
This error will not stop the command from executing but any data on the invalid line is not processed.
AMQ5037
The Queue Manager task <insert_3> has started.
Severity:
0 : Information
Explanation:
The Utility Task Manager, processId(<insert_1>) type(<insert_2>), has started the <insert_3> task.
Response:
None.
AMQ5038
The Queue Manager task <insert_3> failed to start with error-code <insert_1>.
Severity:
40 : Stop Error
Explanation:
The Utility Task Manager, attempted to start the task <insert_3> but the start request failed with error code <insert_1>.
Response:
The failure to start the identified task may not be critical to queue-manager operation however all of the queue manager functionality may not be available. Further details of the failure are available in WebSphere MQ error logs.
AMQ5041
The Queue Manager task <insert_3> has ended.
Severity:
0 : Information
Explanation:
The Queue Manager task <insert_3> has ended.
Response:
None.
AMQ5042
Request to start <insert_3> failed.
Severity:
40 : Stop Error
Explanation:
The request to start the process <insert_3> failed.
Response:
Consult the Queue Manager error logs for further details on the cause of the failure.
AMQ5043
Statistics recording is unavailable due to error code <insert_1>.
Severity:
40 : Stop Error
Explanation:
The statistics collection task was unable to start due the error code <insert_1>. Statistics collection will be unavailable until the problem is rectified and the Queue Manager is restarted.
Response:
Consult the Queue Manager error logs for further details on the cause of the failure.
AMQ5044
<insert_3> task operation restricted due to Reason Code <insert_1>.
Severity:
10 : Warning
Explanation:
The <insert_3> task encountered a non-fatal error which may effect the operation of the task.
Response:
Using the Reason Code <insert_1> and any previous messages recorded in the Error Logs correct the error. It may be necessary to restart the Queue Manager in order remove the restriction caused by the failure.
AMQ5045
System reconfiguration event received
Severity:
0 : Information
Explanation:
The Queue Manager received a system re-configuration event. This is likely to have been caused by an administrative change in the configuration of the machine (for example dynamically adding or removing resources such as memory or processors).
Response:
No action is required unless this notification was unexpected.
AMQ5203
An error occurred calling the XA interface.
Severity:
0 : Information
Explanation:
The error number is <insert_2> where a value of
1 indicates the supplied flags value of <insert_1> was invalid,
2 indicates that there was an attempt to use threaded and non-threaded libraries in the same process,
3 indicates that there was an error with the supplied queue manager name <insert_3>,
4 indicates that the resource manager id of <insert_1> was invalid,
5 indicates that an attempt was made to use a second queue manager called <insert_3> when another queue manager was already connected,
6 indicates that the Transaction Manager has been called when the application isn't connected to a queue manager,
7 indicates that the XA call was made while another call was in progress,
8 indicates that the xa_info string <insert_3> in the xa_open call contained an invalid parameter value for parameter name <insert_4>,
9 indicates that the xa_info string <insert_3> in the xa_open call is missing a required parameter, parameter name <insert_4>, and
10 indicates that MQ was called in dynamic registration mode but cannot find the ax_reg and ax_unreg functions ! Either call MQ in non-dynamic registration mode or supply the correct library name via the AXLIB parameter in the xa_open string.
Response:
Correct the error and try the operation again.
AMQ5204
A non-threaded application tried to run as a Trusted application.
Severity:
10 : Warning
Explanation:
Only applications linked with the threaded MQ libraries can run as Trusted applications.
Response:
Make sure that the application is relinked with the threaded MQ libraries, or set the the environment variable MQ_CONNECT_TYPE to STANDARD.
AMQ5205
File or directory <insert_3> not owned by user <insert_4>.
Severity:
40 : Stop Error
Explanation:
WebSphere MQ has detected that the file or directory <insert_3> is not owned by the user <insert_4>. This is not necessarily an error but you should investigate further if this is unexpected.
Response:
If this is unexpected then you should alter the ownership of the file or directory back to the user <insert_4>.
If this is expected, then WebSphere MQ will continue however WebSphere MQ will be unable to verify the security of this file or directory. If the access permissions are too strict then you may encounter problems if WebSphere MQ cannot access the contents of the file or directory. If the access permissions are too relaxed then there may be an increased risk to the security of the WebSphere MQ system.AMQ5206
Duplicate parameters detected.
Severity:
10 : Warning
Explanation:
WebSphere MQ has detected that the activity about to be displayed contains two or more parameters in the same group with the same parameter identifier. The activity may be displayed incorrectly.
Response:
Inform the author of the activity that there may be an error in it.
AMQ5358
WebSphere MQ could not load AX support module <insert_3>.
Severity:
20 : Error
Explanation:
An error has occurred loading the AX support module <insert_3>. This module needs to be loaded so that dynamically-registering resource managers, such as DB2, can participate in global units of work.
Response:
Look for a previous message outlining the reason for the load failure. Message AMQ6175 should have been issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the AX support module and the mqmax library have been correctly installed on your system.
AMQ5501
There was not enough storage to satisfy the request
Severity:
20 : Error
Explanation:
An internal function of the product attempted to obtain storage, but there was none available.
Response:
Stop the product and restart it. If this does not resolve the problem, save the generated output files and contact your IBM support center.
AMQ5502
The CDS directory name <insert_3> is not in the correct format.
Severity:
20 : Error
Explanation:
An internal function of the DCE Naming service found a CDS directory name in the wrong format. The name was expected to start with either '/...' for a fully qualified name (from global root), or '/.:' for a partially qualified name (from local cell root).
Response:
Save the generated output files and contact your IBM support center.
AMQ5503
The name of the local DCE cell cannot be determined, status = <insert_1>
Severity:
20 : Error
Explanation:
The DCE Naming Service attempted to determine the name of the local DCE cell by calling 'dce_cf_get_cell_name()', which returned a nonzero return code.
Response:
Save the generated output files and contact your IBM support center.
AMQ5504
DCE error. No value for the XDS attribute found.
Severity:
20 : Error
Explanation:
The DCE Naming service called om_get() to get the entry from the object returned by ds_read(). Although the status was correct, no objects were returned.
Response:
Save the generated output files and contact your IBM support center.
AMQ5505
DCE error. No value for the XDS attribute number <insert_1> found.
Severity:
20 : Error
Explanation:
The DCE Naming service called om_get() to get the entry from the object returned by ds_read(). Although the status was correct, no objects were returned.
Response:
Save the generated output files and contact your IBM support center.
AMQ5506
DCE error. <insert_3> returned <insert_1> for attribute number <insert_2>.
Severity:
20 : Error
Explanation:
The DCE Naming service queried an object by calling <insert_3> which returned a nonzero return code.
Response:
Save the generated output files and contact your IBM support center.
AMQ5507
DCE error. <insert_3> failed for an unknown reason.
Severity:
20 : Error
Explanation:
An unexpected error occurred in an internal function of the DCE Naming service.
Response:
Save the generated output files and contact your IBM support center.
AMQ5508
DCE error. The requested attribute is not present.
Severity:
20 : Error
Explanation:
The DCE Naming service was attempting to extract the value from an attribute, but the attribute cannot be found in the XDS object.
Response:
Save the generated output files and contact your IBM support center.
AMQ5509
DCE error. The XDS workspace cannot be initialized.
Severity:
20 : Error
Explanation:
The DCE Naming service called 'ds_initialize()' to initialize the XDS workspace, but 'ds_initialize()' returned a nonzero return code.
Response:
Save the generated output files and contact your IBM support center.
AMQ5510
DCE error. <insert_3> returned with problem <insert_1>.
Severity:
20 : Error
Explanation:
The DCE Naming service found an unexpected XDS error.
Response:
Save the generated output files and contact your IBM support center.
AMQ5511
Installable service component <insert_3> returned <insert_4>.
Severity:
20 : Error
Explanation:
The internal function, that adds a component to a service, called the component initialization process. This process returned an error.
Response:
Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component.
AMQ5511 (iSeries)
An installable service component returned an error.
Severity:
20 : Error
Explanation:
Installable service component <insert_3> returned <insert_4>. The internal function, that adds a component to a service, called the component initialization process. This process returned an error.
Response:
Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component.
AMQ5512
Installable service component <insert_3> returned <insert_4> for queue manager name = <insert_5>.
Severity:
20 : Error
Explanation:
An installable service component returned an unexpected return code.
Response:
Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component.
AMQ5512 (iSeries)
An installable service component returned an unexpected return code.
Severity:
20 : Error
Explanation:
Installable service component <insert_3> returned <insert_4> for queue manager name = <insert_5>.
Response:
Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component.
AMQ5513
<insert_3> returned <insert_1>.
Severity:
20 : Error
Explanation:
An unexpected error occurred.
Response:
Save the generated output files and contact your IBM support center.
AMQ5519
Bad DCE identity. Status = <insert_1>, auth = <insert_2>, keytab file = <insert_3>, principal = <insert_4>.
Severity:
20 : Error
Explanation:
The keytab file was not installed correctly, or the WebSphere MQ user ID has a different password from that used to create the keytab file.
Response:
Make sure that the MQ user ID defined when the product was installed has the same password as that defined by the keytab file, and that the keytab file has been installed correctly.
AMQ5519 (iSeries)
Bad DCE identity.
Severity:
20 : Error
Explanation:
Status = <insert_1>, auth = <insert_2>, keytab file = <insert_3>, principal = <insert_4>. The keytab file was not installed correctly, or the WebSphere MQ user ID has a different password from that used to create the keytab file.
Response:
Make sure that the MQ user ID defined when the product was installed has the same password as that defined by the keytab file, and that the keytab file has been installed correctly.
AMQ5520
The system could not load the module <insert_5> for the installable service <insert_3> component <insert_4>. The system return code was <insert_1>. The Queue Manager is continuing without this component.
Severity:
10 : Warning
Explanation:
The queue manager configuration data included a stanza for the installable service <insert_3> component <insert_4> with the module <insert_5>. The system returned <insert_1> when it tried to load this module. The Queue Manager is continuing without this component.
Response:
Make sure that the module can be loaded. Put the module into a directory where the system can load it, and specify its full path and name in the configuration data . Then stop and restart the queue manager.
AMQ5520 (iSeries)
The system could not load a module. The Queue Manager is continuing without this component.
Severity:
10 : Warning
Explanation:
The queue manager configuration data included a stanza for the installable service <insert_3> component <insert_4> with the module <insert_5>. The system returned <insert_1> when it tried to load this module. The Queue Manager is continuing without this component.
Response:
Make sure that the module can be loaded. Put the module into a directory where the system can load it, and specify its full path and name in the configuration data . Then stop and restart the queue manager.
AMQ5521
The system could not open "<insert_3>".
Severity:
10 : Warning
Explanation:
The system failed to open the default object "<insert_3>" at connect time for reason <insert_4>. This may be because "<insert_3>" has been deleted or changed.
Response:
Recreate the default objects by running "strmqm -c <qmgr>" (where <qmgr> is the name of the queue manager) and retry the application.
AMQ5522
A WebSphere MQ installable service component could not be initialized.
Severity:
20 : Error
Explanation:
An installable service component returned an unexpected return code.
Response:
Check the queue manager error logs for messages explaining which installable service could not be initialized and why that service could not be initialized. Check the component was installed correctly. If it was, and the component was supplied by IBM, then save the generated output files and contact your IBM support center. If the component was not supplied by IBM, save the generated output files and follow the support procedure for that component.
AMQ5524
The WebSphere MQ Object Authority Manager has failed to migrate authority data.
Severity:
20 : Error
Explanation:
The Object Authority Manager has attempted to migrate existing queue manager authority data from a previous version of an Object Authority Manager and failed.
Response:
Check this log for any previous related messages, follow their recommendations then restart the queue manager.
AMQ5525
The WebSphere MQ Object Authority Manager has failed.
Severity:
20 : Error
Explanation:
The Object Authority Manager has failed to complete an MQ request.
Response:
Check the queue manager error logs for messages explaining the failure and try to correct the problem accordingly.
AMQ5526
The WebSphere MQ Object Authority Manager has failed with reason <insert_1>
Severity:
20 : Error
Explanation:
The Object Authority Manager has failed an operation on the Object Authority Manager's data queue <insert_3> with reason <insert_1>.
Response:
Investigate why the error has occured and correct the problem.
AMQ5527
The WebSphere MQ Object Authority Manager has failed to locate an essential authority file
Severity:
20 : Error
Explanation:
The Object Authority Manager has failed to locate the authority file <insert_3>. The migration of authority data cannot continue until the file has been restored. The queue manager will shutdown.
Response:
Restore the authority file mentioned above and restart the queue manager.
AMQ5528
The WebSphere MQ Object Authority Manager has failed to locate an object's authority file
Severity:
20 : Error
Explanation:
The Object Authority Manager has failed to locate the authority file for the object <insert_3> of type (<insert_1>). The authority access to this object will initially be limited to members of the mqm group. Where type is one of the following:
1) Queue
2) Namelist
3) Process
5) Queue Manager
Response:
To extend access to this object use the setmqaut command, see the WebSphere MQ System Administration documentation for details.
AMQ5529
The Remote OAM Service is not available.
Severity:
20 : Error
Explanation:
The Remote OAM service is not available. The <insert_1> call returned <insert_1>, errno <insert_2> : <insert_3>. The context string is <insert_4>
Response:
To extend access to this object use the setmqaut command, see the WebSphere MQ System Administration documentation for details.
AMQ5600
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-g ApplicationGroup]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5601
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]
Severity:
0 : Information
Response:
None.
AMQ5602
[-lc | -ll] [-lf LogFileSize] [-ld LogPath] QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5602 (iSeries)
[-ll] [-lf LogFileSize] [-ld LogPath] [-lz ASPNum] QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5603
Usage: dltmqm [-z] QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5604
Usage: dspmqaut [-m QMgrName] [-n ObjName] -t ObjType (-p Principal | -g Group) [-s ServiceComponent]
Severity:
0 : Information
Response:
None.
AMQ5605
Usage: endmqm [-z] [-c | -w | -i | -p] QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5606
Usage: setmqaut [-m QMgrName] [-n ObjName] -t ObjType (-p Principal | -g Group) [-s ServiceComponent] Authorizations
Severity:
0 : Information
Response:
None.
AMQ5607
Usage: strmqm [-a|-c|-r][-d none|minimal|all][-z][-ns] [QMgrName]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5608
Usage: dspmqtrn [-m QMgrName] [-e] [-i]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5609
Usage: rsvmqtrn -m QMgrName (-a | ((-b | -c | -r RMId) Transaction,Number))
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5610 (iSeries)
Usage: strmqtrc [-m QMgrName] [-e] [-t TraceType] [-o mqm|pex|all] [-x TraceType] [-l MaxFileSize] [-d UserDataSize]
Severity:
0 : Information
Explanation:
None.
Response:
None.
AMQ5610 (Unix)
Usage: strmqtrc [-m QMgrName] [-e] [-t TraceType] [-x TraceType]
[-l MaxFileSize] [-d UserDataSize]
Severity:
0 : Information
Explanation:
This applies to UNIX systems. MaxFileSize is the maximum size of a trace file in millions of bytes. UserDataSize is the size of user data to be traced in bytes.
Response:
None.
AMQ5610 (Windows)
Usage: strmqtrc [-t TraceType] [-x TraceType] [-l MaxFileSize] [-d UserDataSize]
Severity:
0 : Information
Explanation:
This applies to Windows NT and Windows 2000 systems only. MaxFileSize is the maximum size of a trace file in millions of bytes. UserDataSize is the size of user data to be traced in bytes.
Response:
None.
AMQ5611 (Unix)
Usage: endmqtrc [-m QMgrName] [-e] [-a]
Severity:
0 : Information
Explanation:
This applies to UNIX systems.
Response:
None.
AMQ5611 (Windows)
Usage: endmqtrc
Severity:
0 : Information
Explanation:
This applies to Windows NT and Windows 2000 systems only.
Response:
None.
AMQ5612
Usage: dspmqtrc [-t TemplateFile] [-hs] [-o OutputFileName] [-C InputFileCCSID] InputFileName(s)
Severity:
0 : Information
Explanation:
Options: -t Template file for formatting trace data -h Skip the trace file header -s Summary (format only the trace header) -o Save trace output to file -C Specifies the CCSID value for the input file
Response:
None.
AMQ5613
Usage: dspmq [-m QMgrName] [-o status | -s] [-o default]
Severity:
0 : Information
AMQ5614
Usage: setmqtry
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5615
Default objects cannot be created: CompCode = <insert_1> Reason = <insert_2>.
Severity:
20 : Error
Explanation:
During the creation of a queue manager, using the crtmqm command, the default objects could not be created. Possible reasons for this include another command, issued elsewhere, quiescing or stopping the queue manager, or insufficient storage being available.
Response:
Use the Completion and Reason codes shown in the message to determine the cause of the failure, then re-try the command.
AMQ5616
Usage: setmqprd LicenseFile
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5617
Default objects cannot be created.
Severity:
20 : Error
Explanation:
During the creation of a queue manager using the crtmqm command, the default objects could not be created. The most likely reason for this error is that the queue manager was started before the crtmqm command had completed.
Response:
Ensure that the queue manager being created is not started before the create request completes. Stop the queue manager if it is already running. Restart the queue manager using the strmqm command with the '-c' option to request that the default objects are created.
AMQ5618
integer
Severity:
0 : Information
AMQ5619
string
Severity:
0 : Information
AMQ5620
channel_name
Severity:
0 : Information
AMQ5621
process_name
Severity:
0 : Information
AMQ5622
q_name
Severity:
0 : Information
AMQ5623
connection_name
Severity:
0 : Information
AMQ5624
generic_channel_name
Severity:
0 : Information
AMQ5625
generic_process_name
Severity:
0 : Information
AMQ5626
generic_q_name
Severity:
0 : Information
AMQ5627
qalias_name
Severity:
0 : Information
AMQ5628
qmodel_name
Severity:
0 : Information
AMQ5629
qlocal_name
Severity:
0 : Information
AMQ5630
qremote_name
Severity:
0 : Information
AMQ5631
namelist_name
Severity:
0 : Information
AMQ5632
generic_namelist_name
Severity:
0 : Information
AMQ5633
generic_Q_Mgr_name
Severity:
0 : Information
AMQ5634
generic_cluster_name
Severity:
0 : Information
AMQ5635
The argument supplied with the -l flag is not valid.
Severity:
20 : Error
Explanation:
The argument supplied with the -l flag must be in the range 1 - 4293.
Response:
Submit the command again with a valid argument.
AMQ5636
cluster_name
Severity:
0 : Information
AMQ5637 (AIX)
The environment variable EXTSHM is set to "ON". This is incompatable with the way WebSphere MQ uses shared memory. Reset the environment variable EXTSHM and retry the command.
Severity:
20 : Error
Explanation:
On AIX the environment variable EXTSHM causes shared memory segments to be fixed size. WebSphere MQ expects to be able to extend shared memory segments.
Response:
Reset the environment variable EXTSHM and retry the command.
AMQ5646
Usage: setmqcap Processors
Severity:
0 : Information
AMQ5647
Usage: dspmqcap
Severity:
0 : Information
AMQ5648
Usage: dmpmqaut [-m QMgrName] [-n Profile | -l] [-t ObjType] [-p Principal | -g Group] [-s ServiceComponent] [-e | -x]
Severity:
0 : Information
Response:
None.
AMQ5649
generic_authinfo_name
Severity:
0 : Information
AMQ5650
authinfo_name
Severity:
0 : Information
AMQ5651
qmname
Severity:
0 : Information
AMQ5652
The Deferred Message process failed to connect to the WebSphere MQ queue manager for reason <insert_1>.
Severity:
30 : Severe error
Explanation:
The WebSphere MQ queue manager <insert_3> might have generated earlier messages or FFST information explaining why the deferred message process (amqzdmaa) could not connect.
Response:
Correct any configuration errors. Configuration errors that can cause this problem include badly configured CLWL Exit modules. If the problem persists contact your IBM service representative.
AMQ5653
The mqm user is not defined.
Severity:
30 : Severe error
Explanation:
The system call getpwnam("mqm") failed with errno <insert_1>. The program was running as <insert_3>.
Response:
Create the mqm user as a member of the mqm group and retry the operation.
AMQ5654
Usage: dspmqrte [-c] [-n] [-l Persistence] [-m QMgrName] [-o] [-p Priority]
Severity:
0 : Information
Explanation:
This shows the correct usage of the DSPMQRTE command.
Response:
None.
AMQ5655
[-rq ReplyQName [-rqm ReplyQMgrName]] [-ro ReportOptions]
Severity:
0 : Information
Explanation:
This shows the correct usage of the DSPMQRTE command.
Response:
None.
AMQ5656
[-xs Expiry] [-xp Pass] [-qm TargetQMgrName] [-ac [-ar]]
Severity:
0 : Information
Explanation:
This shows the correct usage of the DSPMQRTE command.
Response:
None.
AMQ5657
[-d Delivery] [-f Forwarding] [-s Activities] [-t Detail]
Severity:
0 : Information
Explanation:
This shows the correct usage of the DSPMQRTE command.
Response:
None.
AMQ5658
[-i CorrelId] [-b] [-v Verbosity] [-w WaitTime] -q TargetQName
Severity:
0 : Information
Explanation:
This shows the correct usage of the DSPMQRTE command.
Response:
None.
AMQ5700
listener_name
Severity:
0 : Information
AMQ5701
service_name
Severity:
0 : Information
AMQ5749
display_cmd
Severity:
0 : Information
AMQ5750
filter_keyword
Severity:
0 : Information
AMQ5751
operator
Severity:
0 : Information
AMQ5752
filter_value
Severity:
0 : Information
AMQ5805
WebSphere MQ Publish/Subscribe broker currently running for queue manager.
Severity:
10 : Warning
Explanation:
The command was unsuccessful because queue manager <insert_3> currently has an WebSphere MQ Publish/Subscribe broker running.
Response:
None.
AMQ5806
WebSphere MQ Publish/Subscribe broker started for queue manager <insert_3>.
Severity:
0 : Information
Explanation:
WebSphere MQ Publish/Subscribe broker started for queue manager <insert_3>.
Response:
None.
AMQ5807
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> ended.
Severity:
0 : Information
Explanation:
The WebSphere MQ Publish/Subscribe broker on queue manager <insert_3> has ended.
Response:
None.
AMQ5808
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> is already quiescing.
Severity:
10 : Warning
Explanation:
The endmqbrk command was unsuccessful because an orderly shutdown of the WebSphere MQ Publish/Subscribe broker running on queue manager <insert_3> is already in progress.
Response:
None.
AMQ5808 (iSeries)
WebSphere MQ Publish/Subscribe broker is already quiescing.
Severity:
10 : Warning
Explanation:
The endmqbrk command was unsuccessful because an orderly shutdown of the broker, running on queue manager <insert_3>, is already in progress.
Response:
None.
AMQ5809
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> starting.
Severity:
0 : Information
Explanation:
The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently initializing.
Response:
None.
AMQ5810
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> running.
Severity:
0 : Information
Explanation:
The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently running.
Response:
None.
AMQ5811
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> quiescing.
Severity:
0 : Information
Explanation:
The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker is currently performing a controlled shutdown.
Response:
None.
AMQ5812
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> stopping.
Severity:
0 : Information
Explanation:
Either the dspmqbrk command or the endmqbrk command has been issued. The WebSphere MQ Publish/Subscribe broker is currently performing an immediate shutdown. If the endmqbrk command has been issued to request that the broker terminate, the command is unsuccessful because the broker is already performing an immediate shutdown.
Response:
None.
AMQ5813
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> not active.
Severity:
0 : Information
Explanation:
An WebSphere MQ Publish/Subscribe broker administration command has been issued to query or change the state of the broker. The WebSphere MQ Publish/Subscribe broker is not currently running.
Response:
None.
AMQ5814
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> ended abnormally.
Severity:
0 : Information
Explanation:
The dspmqbrk command has been issued to query the state of the WebSphere MQ Publish/Subscribe broker. The WebSphere MQ Publish/Subscribe broker has ended abnormally.
Response:
Refer to the queue manager error logs to determine why the broker ended abnormally.
AMQ5815
Invalid WebSphere MQ Publish/Subscribe broker initialization file stanza for queue manager (<insert_3>).
Severity:
20 : Error
Explanation:
The broker was started using the strmqbrk command. The broker stanza in the queue manager initialization file is not valid. The broker will terminate immediately. The invalid attribute is <insert_5>.
Response:
Correct the broker stanza in the queue manager initialization file.
AMQ5815 (iSeries)
Invalid WebSphere MQ Publish/Subscribe broker initialization file stanza.
Severity:
20 : Error
Explanation:
The broker was started using the strmqbrk command. The Broker stanza in the queue manager(<insert_3>) initialization file is not valid. The broker will terminate immediately. The invalid attribute is <insert_5>.
Response:
Correct the Broker stanza in the queue manager initialization file.
AMQ5815 (Windows)
The WebSphere MQ Publish/Subscribe broker configuration for queue manager (<insert_3>) is not valid.
Severity:
20 : Error
Explanation:
The broker was started using the strmqbrk command. The broker configuration information is not valid. The broker will terminate immediately. The invalid attribute is <insert_5>.
Response:
Correct the broker attribute using the cfgmqbrk configuration tool.
AMQ5816
Unable to open WebSphere MQ Publish/Subscribe broker control queue for reason <insert_1>,<insert_2>.
Severity:
20 : Error
Explanation:
The broker has failed to open the broker control queue (<insert_3>). The attempt to open the queue failed with completion code <insert_1> and reason <insert_2>. The most likely reasons for this error are that an application program has opened the broker control queue for exclusive access, or that the broker control queue has been defined incorrectly. The broker will terminate immediately.
Response:
Correct the problem and restart the broker.
AMQ5817
An invalid stream queue has been detected by the broker.
Severity:
10 : Warning
Explanation:
WebSphere MQ has detected an attempt to use a queue (<insert_3>) as a stream queue, but the attributes of the queue make it unsuitable for use as a stream queue. The most likely reason for this error is that the queue is: (1) Not a local queue; (2) A shareable queue; (3) A temporary dynamic queue. If the queue was created using implicit stream creation, the model stream might have been defined incorrectly. The message that caused the stream to be created will be rejected or put to the dead-letter queue, depending upon the message report options and broker configuration.
Response:
Correct the problem and resubmit the request.
AMQ5818
Unable to open WebSphere MQ Publish/Subscribe broker stream queue.
Severity:
10 : Warning
Explanation:
The broker has failed to open a stream queue (<insert_3>). The attempt to open the queue failed with completion code <insert_1> and reason <insert_2>. The most likely reason for this error is that an application has the queue open for exclusive access. The stream will be temporarily shut down and an attempt will be made to restart the stream after a short interval.
Response:
Correct the problem.
AMQ5819
An WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
Severity:
10 : Warning
Explanation:
The broker stream (<insert_3>) has ended abnormally for reason <insert_1>. The broker will attempt to restart the stream. If the stream should repeatedly fail then the broker will progressively increase the time between attempts to restart the stream.
Response:
Investigate why the problem occurred and take appropriate action to correct the problem. If the problem persists, contact your IBM service representative.
AMQ5820
WebSphere MQ Publish/Subscribe broker stream (<insert_3>) restarted.
Severity:
0 : Information
Explanation:
The broker has restarted a stream that ended abnormally. This message will frequently be preceded by message AMQ5867 or AMQ5819 indicating why the stream ended.
Response:
Correct the problem.
AMQ5821
WebSphere MQ Publish/Subscribe broker unable to contact parent broker.
Severity:
10 : Warning
Explanation:
The broker has been started specifying a parent broker. The broker has been unable to send a message to the parent broker (<insert_3>) for reason <insert_1>. The broker will terminate immediately.
Response:
Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent broker name not resolving to the name of a transmission queue on the local broker.
AMQ5822
WebSphere MQ Publish/Subscribe broker failed to register with parent broker.
Severity:
10 : Warning
Explanation:
The broker has been started specifying a parent broker (<insert_3>). The broker attempted to register as a child of the parent broker, but received an exception response (<insert_1>) indicating that this was not possible. The broker will attempt to reregister as a child of the parent periodically. The child might not be able to process global publications or subscriptions correctly until this registration process has completed normally.
Response:
Investigate why the problem occurred and take appropriate action to correct the problem. The problem is likely to be caused by the parent broker not yet existing, or a problem with the SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS queue at the parent broker.
AMQ5823
Exit path attribute invalid in WebSphere MQ Publish/Subscribe broker stanza.
Severity:
10 : Warning
Explanation:
The broker exit path attribute <insert_3> is not valid. The attribute should be specified as: <path><module name>(<function name>). The broker will terminate immediately.
Response:
Correct the problem with the attribute and restart the broker.
AMQ5824
WebSphere MQ Publish/Subscribe broker exit module could not be loaded.
Severity:
10 : Warning
Explanation:
The broker exit module <insert_3> could not be loaded for reason <insert_1>:<insert_4>. The broker will terminate immediately.
Response:
Correct the problem with the broker exit module <insert_3> and restart the broker.
AMQ5825
The address of the WebSphere MQ Publish/Subscribe broker exit function could not be found.
Severity:
10 : Warning
Explanation:
The address of the broker exit function <insert_4> could not be found in module <insert_3> for reason <insert_1>:<insert_5>. The broker will terminate immediately.
Response:
Correct the problem with the broker exit function <insert_4> in module <insert_3>, and restart the broker.
AMQ5826
The WebSphere MQ Publish/Subscribe broker has failed to propagate a subscription to another broker.
Severity:
10 : Warning
Explanation:
The broker failed to propagate subscription to stream (<insert_4>) at broker (<insert_3>). Reason codes <insert_1> and <insert_2>. An application has either registered or deregistered a global subscription to stream (<insert_4>). The broker has attempted to propagate the subscription change to broker (<insert_3>) but the request has not been successful. The message broker will immediately attempt to refresh the state of the global subscriptions for stream (<insert_4>) at broker (<insert_3>). Until the subscription state has been successfully refreshed, messages published on stream (<insert_4>) through broker (<insert_3>) might not reach this broker.
Response:
Use the reason codes to investigate why the problem occurred and take appropriate action to correct the problem.
AMQ5827
An WebSphere MQ Publish/Subscribe broker internal subscription has failed.
Severity:
10 : Warning
Explanation:
The broker failed to subscribe to stream (<insert_4>) at broker (<insert_3>) with reason codes <insert_1> and <insert_2>. Related brokers learn about each others configuration by subscribing to information published by each other. A broker has discovered that one of these internal subscriptions has failed. The broker will reissue the subscription immediately. The broker cannot function correctly without knowing some information about neighboring brokers. The information that this broker has about broker (<insert_3>) is not complete and this could lead to subscriptions and publications not being propagated around the network correctly.
Response:
Investigate why the problem occurred and take appropriate action to correct the problem. The most likely cause of this failure is a problem with the SYSTEM.BROKER.CONTROL.QUEUE at broker (<insert_3>), or a problem with the definition of the route between this broker and broker (<insert_3>).
AMQ5828
WebSphere MQ Publish/Subscribe broker exit returned an ExitResponse that is not valid.
Severity:
10 : Warning
Explanation:
The broker exit returned an ExitResponse <insert_1> that is not valid. The message has been allowed to continue and an FFST has been generated that contains the entire exit parameter structure.
Response:
Correct the problem with the broker exit.
AMQ5829
Usage: <insert_3> [-m QMgrName] [-p ParentQMgrName]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5830
Usage: endmqbrk [-c | -i] [-m QMgrName]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5831
Usage: dspmqbrk [-m QMgrName]
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5832
WebSphere MQ Publish/Subscribe broker failed to publish configuration information on SYSTEM.BROKER.ADMIN.STREAM.
Severity:
10 : Warning
Explanation:
Related brokers learn about each others configuration by subscribing to information published by each other. A broker has discovered that one of these internal publications has failed. The broker will republish the information immediately. Brokers cannot function correctly without knowing some information about neighboring brokers. The information that neighboring brokers have of this broker might not be complete and this could lead to some subscriptions and publications not being propagated around the network.
Response:
Investigate why the problem occurred and take appropriate action to correct the problem.
AMQ5833
A loop has been detected in the WebSphere MQ Publish/Subscribe broker hierarchy.
Severity:
20 : Error
Explanation:
The broker, on queue manager (<insert_3>), introduced a loop in the broker hierarchy. This broker will terminate immediately.
Response:
Remove broker (<insert_3>) from the hierarchy, either by deleting the broker, or by removing knowledge of the broker's parent, using the clrmqbrk command.
AMQ5834
Conflicting queue manager names in the WebSphere MQ Publish/Subscribe broker hierarchy.
Severity:
10 : Warning
Explanation:
The names of the queue managers (<insert_3>) and (<insert_4>) in the broker hierarchy both start with the same 12 characters. The first 12 characters of a broker's queue manager name should be unique to ensure that no confusion arises within the broker hierarchy, and to guarantee unique message ID allocation.
Response:
Use a queue manager naming convention that guarantees uniqueness of the first 12 characters of the queue manager name.
AMQ5835
WebSphere MQ Publish/Subscribe broker failed to inform its parent of a relation for reason <insert_1>.
Severity:
0 : Information
Explanation:
The failed to notify its parent on queue manager (<insert_3>) of the relation (<insert_4>) in the broker hierarchy. The notification message will be put to the parent's dead-letter queue. A failure to notify a broker of a new relation will mean that no loop detection can be performed for the new relation.
Response:
Diagnose and correct the problem on the parent queue manager. One possible reason for this is that the parent broker does not yet exist.
AMQ5836
Duplicate queue manager name located in the WebSphere MQ Publish/Subscribe hierarchy.
Severity:
0 : Information
Explanation:
Multiple instances of the queue manager name (<insert_3>) have been located. This could either be the result of a previously resolved loop in the broker hierarchy, or multiple queue managers in the broker hierarchy having the same name.
Response:
If this broker introduced a loop in the hierarchy (typically identified by message AMQ5833), this message can be ignored. It is strongly recommended that every queue manager in a broker hierarchy has a unique name. It is not recommended that multiple queue managers use the same name.
AMQ5837
WebSphere MQ Publish/Subscribe broker failed to quiesce queue (<insert_3>) for reason <insert_1>.
Severity:
10 : Warning
Explanation:
When a broker is deleted, the broker's input queues are quiesced by making the queue get inhibited, and writing the contents of the queue to the dead-letter queue (depending upon the report options of the message). The broker was unable to quiesce the named queue for the reason shown. The attempt to delete the broker will fail.
Response:
Investigate why the problem occurred, take appropriate action to correct the problem, and reissue the dltmqbrk command. Likely reasons include the queue being open for input by another process, there being no dead-letter queue defined at this queue manager, or the operator setting the queue to get inhibited while the dltmqbrk command is running. If there is no dead-letter queue defined, the reason will be reported as MQRC_UNKNOWN_OBJECT_NAME. If the problem occurs because there is no dead-letter queue defined at this broker, the operator can either define a dead-letter queue, or manually empty the queue causing the problem.
AMQ5837 (iSeries)
WebSphere MQ Publish/Subscribe broker failed to quiesce queue.
Severity:
10 : Warning
Explanation:
When a broker is deleted, the broker's input queues are quiesced by making the queue get inhibited, and writing the contents of the queue to the dead-letter queue (depending upon the report options of the message). The broker was unable to quiesce the queue (<insert_3>) for reason <insert_1>. The attempt to delete the broker will fail.
Response:
Investigate why the problem occurred, take appropriate action to correct the problem, and reissue the dltmqbrk command. Likely reasons include the queue being open for input by another process, there being no dead-letter queue defined at this queue manager, or the operator setting the queue to get inhibited while the dltmqbrk command is running. If there is no dead-letter queue defined, the reason will be reported as MQRC_UNKNOWN_OBJECT_NAME. If the problem occurs because there is no dead-letter queue defined at this broker, the operator can either define a dead-letter queue, or manually empty the queue causing the problem.
AMQ5838
WebSphere MQ Publish/Subscribe broker cannot be deleted.
Severity:
10 : Warning
Explanation:
The broker cannot be deleted as child (<insert_3>) is still registered. A broker cannot be deleted until all other brokers that have registered as children of that broker, have deregistered as its children.
Response:
Use the clrmqbrk and dltmqbrk commands to change the broker topology so that broker (<insert_3>) is not registered as a child of the broker being deleted.
AMQ5839
WebSphere MQ Publish/Subscribe broker received an unexpected inter-broker communication.
Severity:
10 : Warning
Explanation:
A broker has received an inter-broker communication that it did not expect. The message was sent by broker (<insert_3>). The message will be processed according to the report options in that message. The most likely reason for this message is that the broker topology has been changed while inter-broker communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous broker topology has arrived at a broker in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication.
Response:
If the broker topology has changed and the broker named in the message is no longer related to the broker issuing this message, this message can be ignored. If the clrmqbrk command was issued to unilaterally remove knowledge of broker (<insert_3>) from this broker, the clrmqbrk command should also be used to remove knowledge of this broker from broker (<insert_3>). If the clrmqbrk command was issued to unilaterally remove knowledge of this broker from broker (<insert_3>), the clrmqbrk command should also be used to remove knowledge of broker (<insert_3>) at this broker.
AMQ5840
WebSphere MQ Publish/Subscribe broker unable to delete queue.
Severity:
10 : Warning
Explanation:
The broker has failed to delete the queue (<insert_3>) for reason <insert_2>. The broker typically attempts to delete queues during dltmqbrk processing, in which case the dltmqbrk command will fail.
Response:
The most likely reason for this error is that some other process has the queue open. Determine why the queue cannot be deleted, remove the inhibitor, and retry the failed operation. In a multi-broker environment, it is likely that a message channel agent might have queues open, which the broker needs to delete for a dltmqbrk command to complete.
AMQ5841
WebSphere MQ Publish/Subscribe broker (<insert_3>) deleted.
Severity:
0 : Information
Explanation:
The broker (<insert_3>) has been deleted using the dltmqbrk command.
Response:
None.
AMQ5842
WebSphere MQ Publish/Subscribe broker (<insert_3>) cannot be deleted for reason <insert_1>:<insert_5>.
Severity:
20 : Error
Explanation:
An attempt has been made to delete the broker (<insert_3>) but the request has failed for reason <insert_1>:<insert_5>.
Response:
Determine why the dltmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and reissue the dltmqbrk command.
AMQ5842 (iSeries)
WebSphere MQ Publish/Subscribe broker cannot be deleted.
Severity:
20 : Error
Explanation:
An attempt has been made to delete the WebSphere MQ Publish/Subscribe broker (<insert_3>) but the request has failed for reason <insert_1>:<insert_5>.
Response:
Determine why the dltmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and reissue the dltmqbrk command.
AMQ5843
WebSphere MQ Publish/Subscribe broker (<insert_3>) cannot be started as it is partially deleted.
Severity:
10 : Warning
Explanation:
An attempt has been made to start a broker that is in a partially deleted state. An earlier attempt to delete the broker has failed. The broker deletion must be completed before the broker will be allowed to restart. When broker deletion is successful, message AMQ5841 is issued, indicating that the broker has been deleted. If this message is not received on completion of a dltmqbrk command, the broker deletion has not been completed and the command will have to be reissued.
Response:
Investigate why the earlier attempt to delete the broker failed. Resolve the problem and reissue the dltmqbrk command.
AMQ5843 (iSeries)
WebSphere MQ Publish/Subscribe broker cannot be started as it is partially deleted.
Severity:
10 : Warning
Explanation:
An attempt has been made to start the broker <insert_3> that is in a partially deleted state. An earlier attempt to delete the broker has failed. The broker deletion must be completed before the broker will be allowed to restart. When broker deletion is successful, message AMQ5841 is issued, indicating that the broker has been deleted. If this message is not received on completion of a dltmqbrk command, the broker deletion has not been completed and the command will have to be reissued.
Response:
Investigate why the earlier attempt to delete the broker failed. Resolve the problem and reissue the dltmqbrk command.
AMQ5844
The relation between two WebSphere MQ Publish/Subscribe brokers is unknown.
Severity:
10 : Warning
Explanation:
The clrmqbrk command has been issued in an attempt to remove a brokers knowledge of a relation of that broker. The relative (<insert_4>) is unknown at broker (<insert_3>). If the "-p" flag was specified, the broker does not currently have a parent. If the "-c" flag was specified, the broker does not recognize the named child.
Response:
Investigate why the broker is unknown.
AMQ5845
Usage: dltmqbrk -m QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5846
Usage: clrmqbrk -p | -c ChildQMgrName -m QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5847
WebSphere MQ Publish/Subscribe broker (<insert_3>) has removed knowledge of relation (<insert_4>).
Severity:
0 : Information
Explanation:
The clrmqbrk command has been used to remove knowledge of broker (<insert_4>) from broker (<insert_3>).
Response:
None.
AMQ5847 (iSeries)
WebSphere MQ Publish/Subscribe broker relation removed.
Severity:
0 : Information
Explanation:
The clrmqbrk command has been used to remove knowledge of broker (<insert_4>) from broker (<insert_3>).
Response:
None.
AMQ5848
WebSphere MQ Publish/Subscribe broker (<insert_3>) has failed to remove references to relation (<insert_4>) for reason <insert_1>:<insert_5>.
Severity:
20 : Error
Explanation:
An attempt has been made to remove references to broker (<insert_4>) from broker (<insert_3>) using the clrmqbrk command, but the request has been unsuccessful.
Response:
Determine why the clrmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and then reissue the clrmqbrk command.
AMQ5848 (iSeries)
WebSphere MQ Publish/Subscribe broker has failed to remove references to a related broker.
Severity:
20 : Error
Explanation:
An attempt has been made to remove references to broker (<insert_4>) from broker (<insert_3>) using the clrmqbrk command, but the request has been unsuccessful for reason <insert_1>:<insert_5>.
Response:
Determine why the clrmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information on why the broker cannot be deleted. Resolve the problem that is preventing the command from completing and then reissue the clrmqbrk command.
AMQ5849
WebSphere MQ Publish/Subscribe broker may not change parent.
Severity:
10 : Warning
Explanation:
An attempt has been made to start broker (<insert_3>), nominating broker (<insert_4>) as its parent. The broker (<insert_3>) has previously been started, nominating broker (<insert_5>) as its parent. The strmqbrk command cannot be used to change an existing relationship.
Response:
Do not attempt to change the broker topology by using the strmqbrk command. The dltmqbrk and clrmqbrk commands are the only supported means of changing the broker topology. Refer to the documentation of those commands for guidance on changing the broker topology.
AMQ5850
WebSphere MQ Publish/Subscribe broker interrupted while creating queue.
Severity:
10 : Warning
Explanation:
The broker was interrupted while creating queue (<insert_3>) for user ID (<insert_4>). When the broker creates a queue, it first creates the queue with default security attributes and it then sets the appropriate security attributes for the queue. If the broker should be interrupted during this operation (for example the queue manager is shut down), the broker cannot reliably detect that the security attributes have not been set correctly. The broker was creating a queue, but was interrupted before it could complete creation of the queue and setting the initial authority. If the interrupt occurred before the initial authority of the queue could be set, it might be necessary for the operator to set the appropriate authorities using the setmqaut command.
Response:
Confirm that the named queue has the appropriate security attributes and modify them as necessary.
AMQ5851
WebSphere MQ Publish/Subscribe broker interrupted while creating internal queue.
Severity:
10 : Warning
Explanation:
The broker was interrupted while creating internal queue (<insert_3>) for user ID (<insert_4>). When the broker creates an internal queue, it first creates the queue with default security attributes and it then sets the appropriate security attributes for the queue. If the broker should be interrupted during this operation (for example the queue manager is shut down), the broker attempts to delete and redefine the queue. If the internal queue is available to users (for example, the default stream or the administration stream), it is possible that a user will put a message on the queue while it is in this invalid state, or that a user application has the queue open. In this situation the broker does not automatically redefine the queue and cannot be restarted until the queue has been emptied or closed.
Response:
Examine any messages on the named queue and take appropriate action to remove them from the queue. Ensure that no applications have the queue open.
AMQ5852
WebSphere MQ Publish/Subscribe broker failed to propagate delete publication command.
Severity:
0 : Information
Explanation:
The broker failed to propagate delete publication command for stream (<insert_3>) to related broker (<insert_4>) for reason <insert_1>. When an application issues a delete publication command to delete a global publication, the command has to be propagated to all brokers in the sub-hierarchy supporting the stream. The broker reporting the error has failed to forward a delete publication command to a related broker (<insert_4>) who supports stream (<insert_3>). Delete publication commands are propagated without MQRO_DISCARD_MSG and the command message might have been written to a dead-letter queue. The topic for which the delete publication has failed is (<insert_5>).
Response:
If the delete publication has failed because the stream has been deleted at the related broker, this message can be ignored. Investigate why the delete publication has failed and take the appropriate action to recover the failed command.
AMQ5853
WebSphere MQ Publish/Subscribe failed to propagate a delete publication command.
Severity:
0 : Information
Explanation:
The broker failed to propagate a delete publication command for stream (<insert_3>) to a previously related broker. When an application issues a delete publication command to delete a global publication, the command is propagated to all brokers in the sub-hierarchy supporting the stream. The broker topology was changed after deleting the publication, but before a broker removed by the topology change processed the propagated delete publication message. The topic for which the delete publication has failed is (<insert_5>).
Response:
It is the user's responsibility to quiesce broker activity before changing the broker topology using the clrmqbrk command. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at the broker that was removed from the topology. In this case, further action might be necessary to propagate the delete publication command that was not quiesced before the clrmqbrk command was issued. If this message occurs as a result of the dltmqbrk command, the publication will have been deleted as a result of the dltmqbrk command, and the delete publication message will have been written to the dead-letter queue at the queue manager where the broker was deleted. In this case the delete publication message on the dead-letter queue can be discarded.
AMQ5854
WebSphere MQ Publish/Subscribe broker failed to propagate a delete publication command.
Severity:
0 : Information
Explanation:
When an application issues a delete publication command to delete a global publication, the command has to be propagated to all brokers in the sub-hierarchy supporting the stream. At the time the delete publication was propagated, broker (<insert_4>) was a known relation of this message broker supporting stream (<insert_3>). Before the delete publication command arrived at the related broker, the broker topology was changed so that broker (<insert_4>) no longer supported stream (<insert_3>). The topic for which the delete publication has failed is (<insert_5>).
Response:
It is the user's responsibility to quiesce broker activity before changing the stream topology of the broker. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at broker (<insert_4>).
AMQ5855
WebSphere MQ Publish/Subscribe broker ended.
Severity:
10 : Warning
Explanation:
An attempt has been made to run the broker (<insert_3>) but the broker has ended for reason <insert_1>:<insert_5>.
Response:
Determine why the broker ended. The message logs for the queue manager might contain more detailed information on why the broker cannot be started. Resolve the problem that is preventing the command from completing and reissue the strmqbrk command.
AMQ5856
Broker publish command message cannot be processed. Reason code <insert_1>.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker failed to process a publish message for stream (<insert_3>). The broker was unable to write the publication to the dead-letter queue and was not permitted to discard the publication. The broker will temporarily stop the stream and will restart the stream and consequently retry the publication after a short interval.
Response:
Investigate why the error has occurred and why the publication cannot be written to the dead-letter queue. Either manually remove the publication from the stream queue, or correct the problem that is preventing the broker from writing the publication to the dead-letter queue.
AMQ5857
Broker control command message cannot be processed. Reason code <insert_1>.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker failed to process a command message on the SYSTEM.BROKER.CONTROL.QUEUE. The broker was unable to write the command message to the dead-letter queue and was not permitted to discard the command message. The broker will temporarily stop the stream and will restart the stream and consequently retry the command message after a short interval. Other broker control commands cannot be processed until this command message has been processed successfully or removed from the control queue.
Response:
Investigate why the error has occurred and why the command message cannot be written to the dead-letter queue. Either, manually remove the command message from the stream queue, or correct the problem that is preventing the broker from writing the command message to the dead-letter queue.
AMQ5858
Broker could not send publication to subscriber queue.
Severity:
10 : Warning
Explanation:
A failure has occurred sending a publication to subscriber queue (<insert_4>) at queue manager (<insert_3>) for reason <insert_1>. The broker configuration options prevent it from recovering from this failure by discarding the publication or by sending it to the dead-letter queue. Instead the broker will back out the unit of work under which the publication is being sent and retry the failing command message a fixed number of times. If the problem still persists, the broker will then attempt to recover by failing the command message with a negative reply message. If the issuer of the command did not request negative replies, the broker will either discard or send to the dead-letter queue the failing command message. If the broker configuration options prevent this, the broker will restart the affected stream, which will reprocess the failing command message again. This behavior will be repeated until such time as the failure is resolved. During this time the stream will be unable to process further publications or subscriptions.
Response:
Usually the failure will be due to a transient resource problem, for example, the subscriber queue, or an intermediate transmission queue, becoming full. Use reason code <insert_1> to determine what remedial action is required. If the problem persists for a long time, you will notice the stream being continually restarted by the broker. Evidence of this occurring will be a large number of AMQ5820 messages, indicating stream restart, being written to the error logs. In such circumstances, manual intervention will be required to allow the broker to dispose of the failing publication. To do this, you will need to end the broker using the endmqbrk command and restart it with appropriate disposition options. This will allow the publication to be sent to the rest of the subscribers, while allowing the broker to discard or send to the dead-letter queue the publication that could not be sent.
AMQ5859
WebSphere MQ Publish/Subscribe broker stream is terminating due to an internal resource problem.
Severity:
10 : Warning
Explanation:
The broker stream (<insert_3>) has run out of internal resources and will terminate with reason code <insert_1>. If the command in progress was being processed under syncpoint control, it will be backed out and retried when the stream is restarted by the broker. If the command was being processed out of syncpoint control, it will not be able to be retried when the stream is restarted.
Response:
This message should only be issued in very unusual circumstances. If this message is issued repeatedly for the same stream, and the stream is not especially large in terms of subscriptions, topics, and retained publications, save all generated diagnostic information and contact your IBM Support Center for problem resolution.
AMQ5862
WebSphere MQ Publish/Subscribe broker for queue manager <insert_3> migrating.
Severity:
0 : Information
Explanation:
The dspmqbrk command has been issued to query the state of the broker. The broker is currently being migrated.
Response:
None.
AMQ5863
WebSphere MQ Integrator broker not ready for migration. See message logs for guidance.
Severity:
10 : Warning
Explanation:
The migmqbrk command was unsuccessful because the WebSphere MQ Integrator broker was not ready to accept messages. The state of the WebSphere MQ Publish/Subscribe message broker is exported to the WebSphere MQ Integrator broker in a series of messages sent to queue SYSTEM.BROKER.INTERBROKER.QUEUE. Before migration commences the WebSphere MQ Publish/Subscribe broker checks whether the WebSphere MQ Integrator broker is ready to accept messages on this queue. This check has failed for reason <insert_1> so migration has been abandoned.
Response:
Reason code <insert_1> should be used to determine the nature of the problem. A value of 1 means that queue SYSTEM.BROKER.INTERBROKER.QUEUE does not exist. This is probably because no WebSphere MQ Integrator broker has been defined yet on this queue manager. A value of 2 means that the WebSphere MQ Integrator broker does not have the queue open probably because it hasn't been started or the first message flow has yet to be deployed for it. If both of these steps have been taken then the WebSphere MQ Integrator broker may have been created incorrectly. In particular, it should have been created in migration mode. If the broker was not created with the migration flag set then it will need to be deleted and recreated before migration can commence. Any other value in the reason code will need to be reported to your IBM Support Center for problem resolution. Note that until the problem has been resolved the WebSphere MQ Publish/Subscribe broker can still be restarted with the the strmqbrk command.
AMQ5864
Broker reply message could not be sent. The command will be retried.
Severity:
10 : Warning
Explanation:
While processing a publish/subscribe command, the WebSphere MQ Publish/Subscribe broker could not send a reply message to queue (<insert_4>) at queue manager (<insert_3>) for reason <insert_1>. The broker was also unable to write the message to the dead-letter queue. Since the command is being processed under syncpoint control, the broker will attempt to retry the command in the hope that the problem is only of a transient nature. If, after a set number of retries, the reply message still could not be sent, the command message will be discarded if the report options allow it. If the command message is not discardable, the stream will be restarted, and processing of the command message recommenced.
Response:
Use reason code <insert_1> to determine what remedial action is required. If the failure is due to a resource problem (for example, a queue being full), you might find that the problem has already cleared itself. If not, this message will be issued repeatedly each time the command is retried. In this case you are strongly advised to define a dead-letter queue to receive the reply message so that the broker can process other commands while the problem is being investigated. Check the application from which the command originated and ensure that it is specifying its reply-to queue correctly.
AMQ5865
Broker reply message could not be sent.
Severity:
10 : Warning
Explanation:
While processing a publish/subscribe command, the WebSphere MQ Publish/Subscribe broker could not send a reply message to queue (<insert_4>) at queue manager (<insert_3>) for reason <insert_1>. The broker was also unable to write the message to the dead-letter queue. As the command is not being processed under syncpoint control, the broker is not able to retry the command.
Response:
Use reason code <insert_1> to determine what remedial action is required. If the failure is due to a resource problem (for example, a queue being full), you might find that the problem has already cleared itself. If not, check the application from which the command originated and ensure that it is specifying its reply-to queue correctly. You might find that defining a dead-letter queue to capture the reply message on a subsequent failure will help you with this task.
AMQ5866
Broker command message has been discarded. Reason code <insert_1>.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker failed to process a publish/subscribe command message, which has now been discarded. The broker will begin to process new command messages again.
Response:
Look for previous error messages to indicate the problem with the command message. Correct the problem to prevent the failure from happening again.
AMQ5867
WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
Severity:
10 : Warning
Explanation:
The broker stream (<insert_3>) has ended abnormally for reason <insert_1>. The broker will attempt to restart the stream. If the stream should repeatedly fail, the broker will progressively increase the time between attempts to restart the stream.
Response:
Use the reason code <insert_1> to investigate why the problem occurred. A reason code of 1 indicates that the stream ended because a command message could not be processed successfully. Look in the error logs for earlier messages to determine the reason why the command message failed. A reason code of 2 indicates that the stream ended because the broker exit could not be loaded. Until the problem with the broker exit has been resolved, the stream will continue to fail.
AMQ5868
User is no longer authorized to subscribe to stream.
Severity:
0 : Information
Explanation:
The broker has attempted to publish a publication to a subscriber, but the subscriber no longer has browse authority to stream queue (<insert_4>). The publication is not sent to the subscriber and his subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While user ID (<insert_3>) remains unauthorized, the broker will continue to deregister subscriptions associated with that user ID.
Response:
If the authority of user ID (<insert_3>) was intentionally removed, consider removing all of that user IDs subscriptions immediately by issuing an MQCMD_DEREGISTER_SUBSCRIBER command, specifying the MQREGO_DEREGISTER_ALL option on the subscriber's behalf. If the authority was revoked accidentally, reinstate it, but be aware that some, if not all, of the subscriber's subscriptions will have been deregistered by the broker.
AMQ5869
WebSphere MQ Publish/Subscribe broker is checkpointing registrations.
Severity:
0 : Information
Explanation:
A large number of changes have been made to the publisher and subscriber registrations of stream (<insert_3>). These changes are being checkpointed, in order to minimize both stream restart time and the amount of internal queue space being used.
Response:
None.
AMQ5870
(Unexpected Error)
Severity:
0 : Information
Explanation:
N/A
Response:
N/A
AMQ5871
(Resource Problem)
Severity:
0 : Information
Explanation:
N/A
Response:
N/A
AMQ5872
(WebSphere MQ Publish/Subscribe broker has a known child)
Severity:
0 : Information
Explanation:
N/A
Response:
N/A
AMQ5873
(WebSphere MQ Publish/Subscribe broker active)
Severity:
0 : Information
Explanation:
N/A
Response:
N/A
AMQ5874
(One or more queues could not be quiesced)
Severity:
0 : Information
Explanation:
N/A
Response:
N/A
AMQ5875
WebSphere MQ Publish/Subscribe broker cannot write a message to the dead-letter queue.
Severity:
10 : Warning
Explanation:
The broker attempted to put a message to the dead-letter queue (<insert_3>) but the message could not be written to the dead-letter queue for reason <insert_1>:<insert_4>. The message was being written to the dead-letter queue with a reason of <insert_2>:<insert_5>.
Response:
Determine why the message cannot be written to the dead-letter queue. Also, if the message was not deliberately written to the dead-letter queue, for example by a message broker exit, determine why the message was written to the dead-letter queue and resolve the problem that is preventing the message from being sent to its destination.
AMQ5876
A parent conflict has been detected in the WebSphere MQ Publish/Subscribe broker hierarchy.
Severity:
20 : Error
Explanation:
The broker (<insert_3>) has been started, naming this broker as its parent. This broker was started naming broker (<insert_3>) as its parent. The broker will send an exception message to broker (<insert_3>) indicating that a conflict has been detected. The most likely reason for this message is that the broker topology has been changed while inter-broker communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous broker topology has arrived at a broker in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication.
Response:
If the broker topology has changed and the broker named in the message no longer identifies this broker as its parent, this message can be ignored - for example, if the command "clrmqbrk -m <insert_3> -p" was issued. If broker (<insert_3>) has been defined as this broker's parent, and this broker has been defined as broker (<insert_3>)'s parent, the clrmqbrk or the dltmqbrk commands should be used to resolve the conflict.
AMQ5877
WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
Severity:
10 : Warning
Explanation:
A broker stream (<insert_3>) has ended abnormally for reason <insert_1>. The broker recovery routines failed to reset the stream state and the stream cannot be restarted automatically.
Response:
Investigate why the stream failed and why the broker's recovery routine could not recover following the failure. Take appropriate action to correct the problem. Depending upon the broker configuration and the nature of the problem it will be necessary to restart either the broker,or both the queue manager and the broker, to make the stream available. If the problem persists contact your IBM service representative.
AMQ5878
WebSphere MQ Publish/Subscribe broker recovery failure detected.
Severity:
10 : Warning
Explanation:
An earlier problem has occurred with the broker, and either a stream has been restarted or the broker has been restarted. The restarted stream or broker has detected that the previous instance of the stream or broker did not clean up successfully and the restart will fail.
Response:
Investigate the cause of the failure that caused a stream or broker restart to be necessary, and why the broker or stream was unable to clean up its resources following the failure. When the broker processes with a non trusted routing exit (RoutingExitConnectType=STANDARD), the broker runs in a mode where it is more tolerant of unexpected failures and it is likely that the restart will succeed after a short delay. In the case of a stream restart, the broker will normally periodically retry the failing restart. In the case of a broker restart, it will be necessary to manually retry the broker restart after a short delay. When the broker processes without a routing exit, or with a trusted routine exit (RoutingExitConnectType=FASTPATH), the broker runs in a mode where it is less tolerant of unexpected failures and a queue manager restart will be necessary to resolve this problem. When the broker is running in this mode, it is important that the broker processes are not subjected to unnecessary asynchronous interrupts, for example, kill. If the problem persists, contact your IBM service representative.
AMQ5879
WebSphere MQ Publish/Subscribe broker has been migrated.
Severity:
10 : Warning
Explanation:
The command was unsuccessful because the MQ Pub/Sub broker at queue manager <insert_3> has been migrated. After migration the only command which can be issued against the migrated broker is the dltmqbrk command.
Response:
Issue the dltmqbrk command to delete the migrated broker.
AMQ5880
User is no longer authorized to subscribe to stream.
Severity:
0 : Information
Explanation:
The broker has attempted to publish a publication to a subscriber but the subscriber no longer has altusr authority to stream queue (<insert_4>). The publication is not sent to the subscriber and that user IDs subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While user ID (<insert_3>) remains unauthorized, the broker will continue to deregister subscriptions associated with that user ID.
Response:
If the authority of user ID (<insert_3>) was intentionally removed, consider removing subscriptions immediately by issuing an MQCMD_DEREGISTER_SUBSCRIBER command for the appropriate topics on the subscriber's behalf. If the authority was revoked accidentally, reinstate it, but be aware that some, if not all, of the subscriber's subscriptions will have been deregistered by the broker.
AMQ5881
The WebSphere MQ Publish/Subscribe broker configuration parameter combination <insert_1> is not valid.
Severity:
20 : Error
Explanation:
A combination of Broker stanzas in the queue manager initialization file is not valid. The broker will not operate until this has been corrected.
An combination of (1) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentInputMsg has been set to FALSE. DiscardNonPersistentInputMsg must be set to TRUE when SyncPointIfPersistent is set to TRUE.
An combination of (2) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentResponse has been set to FALSE. DiscardNonPersistentResponse must be set to TRUE when SyncPointIfPersistent is set to TRUE.
An combination of (3) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentPublication has been set to FALSE. DiscardNonPersistentPublication must be set to TRUE when SyncPointIfPersistent is set to TRUE.
Response:
Alter the message broker stanzas to comply with the above rules and retry the command.
AMQ5881 (Windows)
The WebSphere MQ Publish/Subscribe broker configuration parameter combination <insert_1> is not valid.
Severity:
20 : Error
Explanation:
A combination of Broker parameters in the broker configuration information is not valid. The broker will not operate until this has been corrected.
An combination of (1) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentInputMsg has been set to FALSE. DiscardNonPersistentInputMsg must be set to TRUE when SyncPointIfPersistent is set to TRUE.
An combination of (2) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentResponse has been set to FALSE. DiscardNonPersistentResponse must be set to TRUE when SyncPointIfPersistent is set to TRUE.
An combination of (3) indicates that SyncPointIfPersistent has been set to TRUE and DiscardNonPersistentPublication has been set to FALSE. DiscardNonPersistentPublication must be set to TRUE when SyncPointIfPersistent is set to TRUE.
Response:
Alter the message broker configuration information using the cfgmqbrk tool to comply with the above rules and retry the command.
AMQ5882
WebSphere MQ Publish/Subscribe broker has written a message to the dead-letter queue.
Severity:
10 : Warning
Explanation:
The broker has written a message to the dead-letter queue (<insert_3>) for reason <insert_1>:<insert_5>. Note. To save log space, after the first occurrence of this message for stream (<insert_4>), it will only be written periodically.
Response:
If the message was not deliberately written to the dead-letter queue, for example by a message broker exit, determine why the message was written to the dead-letter queue, and resolve the problem that is preventing the message from being sent to its destination.
AMQ5883
WebSphere MQ Publish/Subscribe broker state not recorded.
Severity:
10 : Warning
Explanation:
The broker state on stream (<insert_3>) not recorded while processing a publication outside of syncpoint. A nonpersistent publication has requested a change to either a retained message or a publisher registration. This publication is being processed outside of syncpoint because the broker has been configured with the SyncPointIfPersistent option set. A failure has occurred hardening either the publisher registration or the retained publication to the broker's internal queue. All state changes attempted as a result of this publication will be backed-out. Processing of the publication will continue and the broker will attempt to deliver it to all subscribers.
Response:
Investigate why the failure occurred. It is probably due to a resource problem occurring on the broker. The most likely cause is 'queue full' on a broker queue. If your publications also carry state changes, you are advised to send them either as persistent publications or turn off the SyncPointIfPersistent option. In this way, they will be carried out under syncpoint and the broker can retry them in the event of a failure such as this.
AMQ5884
WebSphere MQ Publish/Subscribe broker control queue is not a local queue.
Severity:
10 : Warning
Explanation:
WebSphere MQ Publish/Subscribe has detected that the queue 'SYSTEM.BROKER.CONTROL.QUEUE' exists and is not a local queue. This makes the queue unsuitable for use as the control queue of the broker. The broker will terminate immediately.
Response:
Delete the definition of the existing queue and, if required, re-create the queue to be of type MQQT_LOCAL. If you do not re-create the queue the broker will automatically create one of the correct type when started.
AMQ5885
Usage: migmqbrk -m QMgrName
Severity:
0 : Information
Explanation:
This shows the correct usage.
Response:
None.
AMQ5886
WebSphere MQ Publish/Subscribe broker is being migrated.
Severity:
10 : Warning
Explanation:
The command cannot be issued at this time because the MQ Pub/Sub broker at queue manager <insert_3> is being migrated.
Response:
Once migration has commenced then the only command which can be issued against the MQ Pub/Sub broker is the endmqbrk command to cancel the migration. Once the broker has ended if migration did not complete then it can be reattempted using the migmqbrk command again. Alternatively it can be cancelled by restarting the broker using the strmqbrk command.
AMQ5887
Migration started for stream <insert_3>
Severity:
0 : Information
Explanation:
Migration of stream <insert_3> has started.
Response:
None.
AMQ5888
Migration complete for stream <insert_3>
Severity:
0 : Information
Explanation:
All of the state of stream <insert_3> has been exported to the WebSphere MQ Integrator broker.
Response:
None.
AMQ5889
WebSphere MQ Publish/Subscribe broker has been successfully migrated. It will now be deleted.
Severity:
0 : Information
Explanation:
Migration of the broker has completed successfully. The broker will now be deleted.
Response:
The broker is no longer startable. If deletion fails then the dltmqbrk command will need to be re-issued to complete its deletion.
AMQ5890
The migration of the WebSphere MQ Publish/Subscribe broker has failed.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker is being migrated. During this migration all persistent state, for example subscriptions, are exported to the WebSphere MQ Integrator broker as a series of messages sent to queue <insert_3>. A migration message could not be written to this queue for reason <insert_1>.
Response:
Use the MQPUT failure code <insert_1> to determine why the message cannot be written to the queue. The reason code could indicate that the queue manager is terminating in which case the migmqbrk command will need to be re-issued after the queue manager has restarted. Alternatively there may be a problem with the queue which may need to be rectified before migration can be attempted again.
AMQ5891
WebSphere MQ Publish/Subscribe broker has failed to receive a reply while exporting its state to WebSphere MQ Integrator.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker is being migrated. During this migration all persistent state, for example subscriptions, are exported to the WebSphere MQ Integrator broker as a series of messages. A reply message for one of the migration messages could not be retrieved from queue <insert_3> for reason <insert_1>. The migration of the WebSphere MQ Publish/Subscribe broker has failed.
Response:
Use the MQGET failure code <insert_3> to determine why the reply message could not be received from the reply queue. The reason code could indicate that the queue manager is terminating in which the migmqbrk command will need to be re-issued after the queue manager has restarted. A reason code of 2033 indicates that no reply message was received within a 30 second wait interval. In this case the problem is more likely to have occurred at the WebSphere MQ Integrator broker. Check for error messages issued at the WebSphere MQ Integrator broker.
AMQ5892
Migration of stream <insert_3> has failed for reason <insert_1>:<insert_4>.
Severity:
0 : Information
Explanation:
Migration of stream <insert_3> has failed.
Response:
Use reason code <insert_1> to investigate the reason for the failure. Once the problem has been resolved, re-issue the migmqbrk command to retry migration.
AMQ5892 (iSeries)
Migration of stream <insert_3> has failed.
Severity:
0 : Information
Explanation:
Migration of stream <insert_3> has failed for reason <insert_1>:<insert_4>.
Response:
Use reason code <insert_1> to investigate the reason for the failure. Once the problem has been resolved, re-issue the migmqbrk command to retry migration.
AMQ5893
WebSphere MQ Publish/Subscribe broker (<insert_3>) cannot be migrated for reason <insert_1>:<insert_5>.
Severity:
20 : Error
Explanation:
An attempt has been made to migrate the WebSphere MQ Publish/Subscribe broker (<insert_3>) but the request has failed for reason <insert_1>:<insert_5>.
Response:
Determine why the migmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information outlining why the broker cannot be migrated. Resolve the problem that is preventing the command from completing and reissue the migmqbrk command.
AMQ5893 (iSeries)
WebSphere MQ Publish/Subscribe broker cannot be migrated.
Severity:
20 : Error
Explanation:
An attempt has been made to migrate the broker (<insert_3>) but the request has failed for reason <insert_1>:<insert_5>.
Response:
Determine why the migmqbrk command cannot complete successfully. The message logs for the queue manager might contain more detailed information outlining why the broker cannot be migrated. Resolve the problem that is preventing the command from completing and reissue the migmqbrk command.
AMQ5894
WebSphere MQ Publish/Subscribe broker cannot be migrated.
Severity:
10 : Warning
Explanation:
The WebSphere MQ Publish/Subscribe broker cannot be migrated yet because the state of stream <insert_3> is not consistent with respect to related broker <insert_4>. While an WebSphere MQ Publish/Subscribe broker is being migrated a check is made to ensure that the state of each stream is consistent with respect to all of the broker's relations. This check has failed because an inconsistency has been detected in the state of stream <insert_3> with respect to broker <insert_4>. The problem will most likely be of a transient nature, caused because the WebSphere MQ Publish/Subscribe broker has yet to complete processing a recent change to the topology of the broker network. For example, the stream in question may have recently been created or deleted at related broker <insert_4> and this broker has yet to complete its processing for this change. Another cause maybe that either this broker, or broker <insert_4>, have just been added into the broker network and subscriptions have yet to be exchanged the two brokers. If this is the case then the brokers will be inconsistent with respect to all streams. If no recent topology changes have been made then there maybe a current failure with the propagation of subscriptions to broker <insert_4>.
Response:
In all cases migration of the WebSphere MQ Publish/Subscribe broker will need to be suspended until the inconsistency has been resolved. You will need to restart the broker using the strmqbrk command so that it can resolve the problem. After a short while, the broker can be ended and migration reattempted. If repeated attempts to migrate the broker all fail with this message then try to resolve the underlying problem. Look for earlier occurrences of message AMQ5826 and follow the guidance given there. In all cases ensure that the channels between the two brokers are running.
AMQ5895
WebSphere MQ Publish/Subscribe broker cannot be migrated.
Severity:
10 : Warning
Explanation:
A topic has been detected which cannot be exported to the WebSphere MQ Integrator broker. The topic <insert_3> cannot be migrated because it contains wildcard characters recognised by the WebSphere MQ Integrator broker. The wildcard characters used by WebSphere MQ Integrator are the '+' and the '#' characters. The state associated with the topic isn't migrated and migration of the WebSphere MQ Publish/Subscribe broker fails.
Response:
The WebSphere MQ Publish/Subscribe broker cannot be migrated while topic <insert_3> is in use. All applications using topics which contain either the '+' or '#' characters will need to be redesigned to use different topic strings. Note that the amqspsd sample can be used to dump the state of the WebSphere MQ Publish/Subscribe broker. Within the dump produced by this program locate topic <insert_3> to determine information about the publishing or subscribing applications concerned. Until the problem has been resolved the WebSphere MQ Publish/Subscribe broker can be restarted as normal using the strmqbrk command.
AMQ5896
Unknown attribute for WebSphere MQ Publish/Subscribe broker configuration parameter GroupId.
Severity:
20 : Error
Explanation:
The broker has attempted to create stream <insert_4> belonging to group <insert_3>, this group is unknown.
Response:
Modify the attribute for broker configuration parameter GroupId, to a group that exists, or create the group <insert_3>.