An essential IBM MQ process <insert_1> (<insert_3>) cannot be found and is assumed to be terminated.
Severity
40 : Severe
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
IBM MQ will stop all MQ processes. Inform your systems administrator. When the problem is rectified IBM MQ can be restarted.
AMQ5009
IBM MQ agent process <insert_1> has terminated unexpectedly.
Severity
40 : Severe
Explanation
IBM 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
Try to eliminate the following reasons before taking any further action:
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. If you believe the problem is not a result of the above reasons, save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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 : Severe
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 IBM MQ userid has permission to access it.
AMQ5020
Permission denied attempting to execute program <insert_3>.
Severity
40 : Severe
Explanation
A request was made to execute the program <insert_3>, however the operation was unsuccessful because the IBM 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 IBM MQ userId. Also check that the IBM 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 : Severe
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 IBM 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 : Informational
Explanation
The channel initiator process has started.
Response
None.
AMQ5023
The channel initiator has ended. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The channel initiator process has ended.
Response
None.
AMQ5024
The command server has started. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The command server process has started.
Response
None.
AMQ5025
The command server has ended. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The command server process has ended.
Response
None.
AMQ5026
The listener <insert_3> has started. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The listener process has started.
Response
None.
AMQ5027
The listener <insert_3> has ended. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The listener process has ended.
Response
None.
AMQ5028
The Server <insert_3> has started. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The Server process has started.
Response
None.
AMQ5029
The Server <insert_3> has ended. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The Server process has ended.
Response
None.
AMQ5030
The Command <insert_3> has started. ProcessId(<insert_1>).
Severity
0 : Informational
Explanation
The Command has started.
Response
None.
AMQ5032
Error (<insert_4>) accessing file <insert_3>.
Severity
40 : Severe
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 : Severe
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 : Informational
Explanation
The restartable utility task manager has started the <insert_3> task. This task has now started <insert_2> times.
Response
None.
AMQ5038
The queue manager task <insert_3> failed to start with error code <insert_1>.
Severity
40 : Severe
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, some of the queue manager functionality may not be available. Further details of the failure are available in IBM MQ error logs.
AMQ5041
The queue manager task <insert_3> has ended.
Severity
0 : Informational
Explanation
The queue manager task <insert_3> has ended.
Response
None.
AMQ5042
Request to start <insert_3> failed.
Severity
40 : Severe
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 : Severe
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 : Informational
Explanation
The queue manager received a system reconfiguration 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.
AMQ5046
Automatic unmarking of messages is unavailable due to error code <insert_1>.
Severity
40 : Severe
Explanation
An error was encountered by the task that unmarks messages which have been marked for cooperative browse but have not been destructively got within the timeout period. The error code was <insert_1>. Automatic unmarking of messages 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.
AMQ5049
The queued pub/sub interface cannot be started/stopped due to error code <insert_1>.
Severity
40 : Severe
Explanation
An error was encountered by the task that starts and stops the queued pub/sub interface. The error code was <insert_1>. The interface will be unable to be started or stopped 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.
AMQ5050
An essential IBM MQ process <insert_1> (<insert_3>) cannot be found and is assumed to be terminated.
Severity
40 : Severe
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. 3) MQ has encountered an unexpected error. Check for possible errors reported in the MQ error logs and for any FFSTs that have been generated.
Response
IBM MQ will attempt to restart the terminated process.
AMQ5051
The queue manager task <insert_3> has started.
Severity
0 : Informational
Explanation
The critical utility task manager has started the <insert_3> task. This task has now started <insert_2> times.
Response
None.
AMQ5052
The queue manager task <insert_3> has started.
Severity
0 : Informational
Explanation
The publish/subscribe utility task manager has started the <insert_3> task. This task has now started <insert_2> times.
Response
None.
AMQ5053
IBM MQ process <insert_1> (<insert_3>) cannot be found and is assumed to be terminated.
Severity
10 : Warning
Explanation
A queue manager process has terminated, the queue manager will continue to run but the functionality of the queue manager may be limited until the problem is resolved. Possible reasons for the termination are: 1) A user has inadvertently terminated the process. 2) The system is low on resources. Some operating systems terminate processes to free resources. 3) The process encountered an error.
Response
Check for earlier messages in the queue manager and system error logs that may indicate the problem. When the problem is rectified the queue manager will need to be restarted to restore the lost functionality.
AMQ5054
Start or Stop service <insert_3> failed as the <insert_4> path is too long.
Severity
40 : Severe
Explanation
A request was made to start or stop the MQ Service <insert_3>, however the operation was unsuccessful because the length of the <insert_4> path, after the replaceable inserts were expanded, exceeded the maximum path length of <insert_2>.
Response
Modify the path or the values of the replaceable inserts such that the path string is within the maximum allowable length of <insert_2> characters.
AMQ5055
<insert_4> service <insert_3> failed as the <insert_5> program arguments are too long.
Severity
40 : Severe
Explanation
A request was made to start or stop the MQ Service <insert_3>, however the operation was unsuccessful because the length of the argument string, once the replaceable inserts were expanded, exceeded the maximum argument string length.
Response
Modify the argument string or the values of the replaceable inserts such that the argument string is within the maximum allowable length of <insert_2> characters.
AMQ5056 (IBM MQ Appliance)
Argument <insert_3> supplied to command <insert_4> is not permitted on this platform.
Severity
20 : Error
Explanation
You supplied at least one forbidden argument (<insert_3>) to a valid MQ command (<insert_4>).
Response
Correct the command and submit it again. Additional information on the platform specific forbidden arguments causing the error may be found in the relevant section on the IBM info/knowledge centre.
AMQ5057
Unable to reserve <insert_1>MB of file-system storage.
Severity
20 : Error
Explanation
IBM MQ attempted to reserve <insert_1>MB' of file-system storage but the request failed with system error code <insert_2>.
IBM MQ will continue but this may be an indication that there is only a small amount of file-sytem storage available which may effect the operation of the Queue Manager.
Response
The operator should ensure that sufficient free space is available for the Queue Manager to operate correctly.
AMQ5101
Message unexpectedly not found on SYSTEM.DDELAY.LOCAL.QUEUE.
Severity
0 : Informational
Explanation
The queue manager delayed delivery processor expected to find a message on the SYSTEM.DDELAY.LOCAL.QUEUE, but when attempting to retrieve this message found the message was not available. Messages on the SYSTEM.DDELAY.LOCAL.QUEUE should only be processed by the queue managers delayed delivery processor. The MsgId of the message resulting in the message on the SYSTEM.DDELAY.LOCAL.QUEUE was "<insert_3>". By default the SYSTEM.DDELAY.LOCAL.QUEUE is defined with NOSHARE to avoid problems of this nature. The delayed delivery processor will continue without delivering this message.
Response
Check that the queue SYSTEM.DDELAY.LOCAL.QUEUE is defined with NOSHARE. Check if any other user action has resulted in direct processing of messages on SYSTEM.DDELAY.LOCAL.QUEUE. If this is not the case then contact MQ support.
AMQ5203
An error occurred calling the XA interface.
Severity
0 : Informational
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
10 : Warning
Explanation
IBM 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 IBM MQ will continue however IBM 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 IBM 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 IBM MQ system.
AMQ5206
Duplicate parameters detected.
Severity
10 : Warning
Explanation
IBM 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.
AMQ5208
File <insert_3> missing.
Severity
20 : Error
Explanation
IBM MQ has detected that the file <insert_3> is missing.
Response
If this is expected then this is not an error condition.
If this is unexpected then investigate why the error has occurred.
AMQ5211
Maximum property name length exceeded.
Severity
10 : Warning
Explanation
IBM MQ was in the process of parsing an MQRFH2 folder that is known to contain message properties. However, one of the elements in folder <insert_3> has a name which is longer than MQ_MAX_PROPERTY_NAME_LENGTH. The element name begins <insert_4>. The name of the parsed message property will be limited to the maximum number of characters which may cause inquiry of that property or selection of the message to fail.
Response
Reduce the size of the MQRFH2 element name or move the element into a folder which does not contain properties.
AMQ5212
Resource required for asynchronous consume constrained.
Severity
10 : Warning
Explanation
The application has issued an MQCTL(SUSPEND) or MQCTL(STOP) request but the number of concurrent requests for this action exceeds the current capacity of the queue manager. IBM MQ will wait for the capacity to become available, but the application may experience a delay in completing the operation.
This message will only be issued once for the lifetime of the application.
Response
In order to avoid this problem consider reducing the workload on the queue manager.
AMQ5358
IBM 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.
AMQ5370 (HP NSS)
IBM MQ client for HP Integrity NonStop Server (<insert_1>) enlisting with wrong TMF/Gateway
Severity
10 : Warning
Explanation
An IBM MQ client for HP Integrity NonStop Server, process (<insert_1>), connected to <insert_4> has incorrectly attempted to enlist with TMF/Gateway connected to <insert_3>.
Response
The configuration for the IBM MQ client for HP Integrity NonStop Server is incorrect. Ensure the mqclient.ini TMF and TMFGateway stanza have been correctly configured to match the correct TMF/Gateway instances for the queue managers being used.
AMQ5371 (HP NSS)
TMF/Gateway shutting down due to TMF operator closing RM file <insert_3>
Severity
20 : Error
Explanation
The TMF/Gateway is shutting down due to the TMF operator closing RM file <insert_3>.
Response
Contact the TMF administrator to determine why the RM file has been closed.
AMQ5372 (HP NSS)
TMF has shutdown
Severity
10 : Warning
Explanation
TMF has shutdown. The TMF/Gateway for queue manager <insert_3> will reset and wait for TMF to become available before restarting operation.
Response
Contact the TMF administrator to determine why TMF has been shutdown.
AMQ5373 (HP NSS)
TMF not configured
Severity
20 : Error
Explanation
The TMF/Gateway for queue manager <insert_3> is unable to start due to the TMF subsystem not being configured.
Response
Contact the TMF administrator to ensure the TMF subsystem is configured.
AMQ5374 (HP NSS)
TMF/Gateway not authorized to access RM file
Severity
20 : Error
Explanation
The TMF/Gateway for queue manager <insert_3> is not authorized to access TMF RM file <insert_4>.
Response
There is an existing RM file <insert_4> within TMF, associated with a different owner from that specified for the TMF/Gateway server class for queue manager <insert_3> within PathWay. Ensure the TMF/Gateway server class within PathWay is configured with the same owner as the existing TMF RM file.
AMQ5375 (HP NSS)
TMF/Gateway for queue manager <insert_3> has encountered a TMF resource error (<insert_1>)
Severity
20 : Error
Explanation
The TMF/Gateway for queue manager <insert_3> has encountered a TMF resource error (<insert_1>)
Response
These errors are typically as a result of reaching configured resource limits within the TMF subsystem. Refer to the HP Integrity NonStop Guardian Procedure Errors and Messages Manual for the appropriate corrective action based on the error (<insert_1>).
AMQ5376 (HP NSS)
Queue manager <insert_3> unavailable
Severity
0 : Informational
Explanation
Queue manager <insert_3> is unavailable for communication with the TMF/Gateway.
Response
Ensure that the queue manager has been started. The TMF/Gateway uses a client channel connection so additional channel definition and channel status checks might be required. The TMF/Gateway will periodically attempt to reestablish communication with the queue manager. If the queue manager continues to remain unavailable this message will be reissued at regular intervals.
AMQ5377 (HP NSS)
The TMF/Gateway is not authorized to connect to queue manager <insert_3>
Severity
20 : Error
Explanation
The TMF/Gateway is not authorized to connect to queue manager <insert_3>.
Response
Ensure the TMF/Gateway has been configured to use the correct queue manager and that the queue manager has granted appropriate authority for the owner of the TMF/Gateway.
AMQ5378 (HP NSS)
Participation in TMF transactions is not supported by queue manager <insert_3>
Severity
20 : Error
Explanation
TMF/Gateway has detected IBM MQ for z/OS queue manager <insert_3> does not support participation in TMF transactions.
Response
The version of z/OS queue manager that you are connecting to does not support the TMF Gateway, please upgrade to a supported release.
AMQ5379 (HP NSS)
TMF/Gateway started with missing or invalid parameters
Severity
0 : Informational
Explanation
Usage: runmqtmf -m QMgrName [-c ChannelName] [-h HostName] [-p Port] [-n MaxThreads]
-m is the name of the queue manager for this Gateway process. If you are using a queue sharing group (or other port distribution technology), this parameter must be targeted to a specific queue manager. This parameter is mandatory.
-c is the name of the server channel on the queue manager to be used by this Gateway process. This parameter is optional.
-p is the TCP/IP port for the queue manager. This parameter is optional.
-h is the host name of the queue manager. This parameter is optional.
-n is the maximum number of worker threads that are created by the Gateway process. This parameter can be a value of 10 or greater. This parameter is optional. If no value is provided, the Gateway process creates up to a maximum of 50 threads.
If you specify one or more, but not all of the -c, -p, and -h attributes, then those attributes that you do not specify default to the following values:
ChannelName defaults to SYSTEM.DEF.SVRCONN
HostName defaults to localhost
Port defaults to 1414
Response
Ensure the TMF/Gateway is started with only valid parameters.
AMQ5380 (HP NSS)
TMF/Gateway already running for queue manager <insert_3> using TMF RM-file <insert_4>
Severity
20 : Error
Explanation
A single TMF/Gateway process must be configured with TMF for each queue manager that is to participate in TMF coordinated units of work.
Response
Use the TMFCOM STATUS RESOURCEMANAGER command to identify the process that is already using RM-file <insert_4>.
If you are using multiple installations, you must nominate a single Gateway process from one of these installations to coordinate queue manager <insert_3>. The interface to the Gateway process supports any client at the same version or earlier.
Ensure the TMF/Gateway server class definition within Pathway for queue manager <insert_3> has been configured with MAXSERVER set to 1.
AMQ5389 (HP NSS)
Usage: setmqtmf -m QMgrName (-r | -d | -t [-i | -w])
-m Name of the queue manager to which the TMF/Gateway is coordinating TMF transactions.
-r Request recovery of in-doubt transactions immediately.
-d Request the TMF/Gateway to produce debug output.
-t Request the TMF/Gateway to terminate.
-i Terminate the TMF/Gateway immediately. Use in combination with the -t option.
-w Terminate the TMF/Gateway after outstanding work has been completed. Use in combination with the -t option.
Severity
0 : Informational
Explanation
This shows the correct usage.
AMQ5390 (HP NSS)
Invalid process name <insert_3> provided in the MQTMF_GATEWAY_NAME environment variable for the TMF/Gateway for queue manager <insert_4>.
Severity
20 : Error
AMQ5391 (HP NSS)
No PATHMON process name provided in the mqclient.ini for the TMF/Gateway for queue manager <insert_3>.
Severity
20 : Error
AMQ5392 (HP NSS)
No server class name provided in the mqclient.ini for the TMF/Gateway for queue manager <insert_3>.
Severity
20 : Error
AMQ5393 (HP NSS)
The TMF/Gateway for queue manager <insert_3> is unable to process the request, return code (<insert_1>:<insert_3>)
Severity
20 : Error
AMQ5394 (HP NSS)
The TMF/Gateway for queue manager <insert_3> has successfully processed the request.
Severity
0 : Informational
AMQ5395 (HP NSS)
Unable to locate server class <insert_4> hosted by PATHMON process <insert_3>.
Severity
20 : Error
AMQ5396 (HP NSS)
Unable to locate PATHMON process <insert_3>
Severity
20 : Error
AMQ5397 (HP NSS)
Not authorized to use server class <insert_4> hosted by PATHMON process <insert_3>
Severity
20 : Error
AMQ5398 (HP NSS)
Error encountered while establishing contact with the TMF/Gateway server class <insert_4> hosted by PATHMON process <insert_3>. Pathsend error (<insert_1>), file system error (<insert_2>).
Severity
20 : Error
AMQ5399 (HP NSS)
The TMF/Gateway server class <insert_4> hosted by PATHMON process <insert_3> has not been configured appropriately
Severity
20 : Error
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 any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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).
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.
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.
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.
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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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 (IBM i)
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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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 (IBM i)
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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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.
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 IBM 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 (IBM i)
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 IBM 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 (IBM i)
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
An IBM 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 any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, 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 IBM 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 IBM 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 IBM 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 IBM 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 IBM 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 IBM 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 IBM MQ System Administration documentation for details.
AMQ5530
Error from LDAP authentication and authorization service
Severity
20 : Error
Explanation
The LDAP authentication and authorization service has failed. The <insert_3> call returned error <insert_1> : <insert_4>. The context string is <insert_5>. Additional code is <insert_2>.
Response
Correct the LDAP configuration. Look at the LDAP server logs for additional error information.
AMQ5531
Error locating user or group in LDAP
Severity
20 : Error
Explanation
The LDAP authentication and authorization service has failed in the <insert_3> call while trying to find user or group <insert_4>. Returned count is <insert_1>. Additional context is <insert_5>.
Response
Specify the correct name, or fix the directory configuration. There may be additional information in the LDAP server error logs.
AMQ5532
Error authorizing entity in LDAP
Severity
20 : Error
Explanation
The LDAP authorization service has failed in the <insert_3> call while trying to find user or group <insert_4>. Returned count is <insert_1>. Additional context is <insert_5>.
Response
Specify the correct name, or fix the directory configuration. There may be additional information in the LDAP server error logs.
AMQ5533
The object <insert_3> specified by the CONNAUTH parameter is invalid
Severity
20 : Error
Explanation
The object <insert_3> specified by the queue manager CONNAUTH parameter either does not exist, or is of invalid type.
Response
Investigate why the error has occured and correct the problem.
AMQ5534
User ID <insert_3> authentication failed
Severity
20 : Error
Explanation
The user ID and password supplied by the <insert_4> program could not be authenticated.
Additional information: <insert_5>.
Response
Ensure that the correct user ID and password are provided by the application. Ensure that the authentication repository is correctly configured. Look at previous error messages for any additional information.
AMQ5535
runmqccred failed with error <insert_1> while processing file <insert_3>
Severity
20 : Error
Explanation
The runmqccred program failed with error <insert_1> while processing file <insert_3>
Response
Correct the error
AMQ5536
Cannot open configuration file <insert_3>
Severity
20 : Error
Explanation
The runmqccred program could not open a file called <insert_3>.
Response
The default location of the configuration file is at
<user's home directory>/.mqs/mqccred.ini
Set the MQCCRED environment variable to override this. Do not specify a directory as the configuration file.
Ensure the user running the program has permission to read and update the file.
AMQ5537
Configuration file <insert_3> is not secure.
Other users may be able to read it. No changes have been made to the file.
Use the -p option for runmqccred to bypass this error.
Severity
10 : Warning
Explanation
Permissions on configuration file <insert_3> permit other users to read it. Use the -p option for runmqccred to bypass this error.
Response
The permissions on the configuration file allow other users to read it. It is recommended that the file be restricted to only the owner. Use the -p option for runmqccred to bypass this error.
The runmqccred program protected <insert_1> password(s) in file <insert_3>
Response
Nothing
AMQ5539
Usage: runmqccred [-f file] [-p]
-f Configuration file to be processed.
-p Ignore error when configuration file is insufficiently protected.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
Nothing
AMQ5540
Application <insert_3> did not supply a user ID and password
Severity
20 : Error
Explanation
The queue manager is configured to require a user ID and password, but none was supplied.
Response
Ensure that the application provides a valid user ID and password, or change the queue manager configuration to OPTIONAL to allow applications to connect which have not supplied a user ID and password.
AMQ5541
The failed authentication check was caused by the queue manager CONNAUTH <insert_5> configuration.
Severity
0 : Informational
Explanation
The user ID <insert_3> and its password were checked because the user ID is privileged and the queue manager connection authority (CONNAUTH) configuration refers to an authentication information (AUTHINFO) object named <insert_4> with <insert_5>.
This message accompanies a previous error to clarify the reason for the user ID and password check.
Response
Refer to the previous error for more information.
Ensure that a password is specified by the client application and that the password is correct for the user ID. The authentication configuration of the queue manager connection determines the user ID repository. For example, the local operating system user database or an LDAP server.
To avoid the authentication check, you can either use an unprivileged user ID or amend the authentication configuration of the queue manager. You can amend the CHCKCLNT attribute in the CHLAUTH record, but you should generally not allow unauthenticated remote access.
AMQ5542
The failed authentication check was caused by the queue manager CONNAUTH <insert_5> configuration.
Severity
0 : Informational
Explanation
The user ID <insert_3> and its password were checked because the queue manager connection authority (CONNAUTH) configuration refers to an authentication information (AUTHINFO) object named <insert_4> with <insert_5>.
This message accompanies a previous error to clarify the reason for the user ID and password check.
Response
Refer to the previous error for more information.
Ensure that a password is specified by the client application and that the password is correct for the user ID. The authentication configuration of the queue manager connection determines the user ID repository. For example, the local operating system user database or an LDAP server.
If the CHCKCLNT setting is OPTIONAL, the authentication check can be avoided by not passing a user ID across the channel. For example, by omitting the MQCSP structure from the client MQCONNX API call.
To avoid the authentication check, you can amend the authentication configuration of the queue manager connection, but you should generally not allow unauthenticated remote access.
AMQ5543
The distinguished name is too long
Severity
20 : Error
Explanation
The distinguished name <insert_3> was found in the LDAP directory when looking for <insert_4>, but is longer than the maximum <insert_1> characters.
Response
Associate the entity with a shorter distinguished name.
AMQ5600
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-md DataPath] [-g ApplicationGroup]
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]
[-lc | -ll] [-lf LogFileSize] [-ld LogPath] [-p Port] QMgrName
-c Descriptive text.
-d Default transmission queue name.
-g Restrict use of the queue manager to this group.
-h Maximum number of handles per connection handle.
-lc Use circular logging.
-ld Directory used to hold the log files for the queue manager.
-lf Log file size, specified in units of 4 KB pages.
-ll Use linear logging.
-lp Primary log files allocated when the queue manager is created.
-ls Secondary log files allocated when the primary files are exhausted.
-md Directory used to hold the data files for the queue manager.
-p Create listener configured for TCP/IP on the specified port.
-q Make this queue manager the default queue manager.
-t Trigger interval in milliseconds.
-u Dead-letter queue name.
-x Maximum number of uncommitted messages under any one syncpoint.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5600 (IBM MQ Appliance)
Usage: crtmqm [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-p Port] [-t TrigInt] [-u DeadQ] [-x MaxUMsgs]
[-lp LogPri] [-ls LogSec] [-lf LogFileSize]
[-fs FileSystemSize] [-sx] QMgrName
-c Descriptive text.
-d Default transmission queue name.
-fs File system size in gigabytes (GB).
-h Maximum number of handles per connection handle.
-lf Log file size, specified in units of 4 KB pages.
-lp Primary log files allocated when the queue manager is created.
-ls Secondary log files allocated when the primary files are exhausted.
-p Port number for the managed TCP listener.
-sx Make this queue manager a high availability (HA) queue manager.
-t Trigger interval in milliseconds.
-u Dead-letter queue name.
-x Maximum number of uncommitted messages under any one syncpoint.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5600 (IBM i)
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-md DataPath] [-g ApplicationGroup]
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs]
[-lb BufferSize] [-lf JrnRcvThreshold]
[-ld Library] [-lz ASPNum|ASPDev] [-p Port] QMgrName
-c Descriptive text.
-d The name of the local default transmission queue.
-g Restrict use of the queue manager to this group.
-h The maximum number of handles per connection handle.
-lb The journal buffer size in bytes.
-ld The name of the queue manager's library.
-lf The journal receiver threshold in KB.
-lz The auxiliary storage pool containing the library.
-md The directory used to hold the data files for the queue manager.
-p Create listener configured for TCP/IP on the specified port.
-q Make this queue manager the default queue manager.
-t The trigger interval in milliseconds.
-u The name of the dead-letter queue.
-x The maximum number of uncommitted messages under any one syncpoint.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5600 (UNIX and Linux)
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-md DataPath] [-g ApplicationGroup] [-oa user|group]
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]
[-lc | -ll] [-lf LogFileSize] [-ld LogPath] [-p Port] QMgrName
-c Descriptive text.
-d Default transmission queue name.
-g Restrict use of the queue manager to this group.
-h Maximum number of handles per connection handle.
-lc Use circular logging.
-ld Directory used to hold the log files for the queue manager.
-lf Log file size, specified in units of 4 KB pages.
-ll Use linear logging.
-lp Primary log files allocated when the queue manager is created.
-ls Secondary log files allocated when the primary files are exhausted.
-md Directory used to hold the data files for the queue manager.
-oa Authorization policy for the queue manager.
-p Create listener configured for TCP/IP on the specified port.
-q Make this queue manager the default queue manager.
-t Trigger interval in milliseconds.
-u Dead-letter queue name.
-x Maximum number of uncommitted messages under any one syncpoint.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5600 (Windows)
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-md DataPath] [-g ApplicationGroup] [-ss | -sa | -sax | -si]
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]
[-lc | -ll] [-lf LogFileSize] [-ld LogPath] [-p Port ] QMgrName
-a Allow this group access to queue manager files.
-c Descriptive text.
-d Default transmission queue name.
-g Restrict use of the queue manager to this group.
-h Maximum number of handles per connection handle.
-lc Use circular logging.
-ld Directory used to hold the log files for the queue manager.
-lf Log file size, specified in units of 4 KB pages.
-ll Use linear logging.
-lp Primary log files allocated when the queue manager is created.
-ls Secondary log files allocated when the primary files are exhausted.
-md Directory used to hold the data files for the queue manager.
-p Create listener configured for TCP/IP on the specified port.
-q Make this queue manager the default queue manager.
-sa Automatic queue manager startup.
-sax Automatic queue manager startup, permitting multiple instances.
-si Interactive (manual) queue manager startup.
-ss Service (manual) queue manager startup.
-t Trigger interval in milliseconds.
-u Dead-letter queue name.
-x Maximum number of uncommitted messages under any one syncpoint.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5602
Configuration information for the queue manager <insert_3> has been added without access to one or more queue manager configuration files.
Severity
10 : Warning
Explanation
The configuration information for the queue manager <insert_3> has been added without validating the queue manager configuration because of failure in accessing one or more queue manager configuration files.
Response
Look at previous error messages for <insert_4> in this error log to determine the cause for the failure in accessing one or more files in the queue manager directory.
If the command was executed on a system where the queue manager data file system is not available (for example, the secondary node in a high availability configuration), then this is not an error condition.
If the command was executed on a system where the queue manager data file system is expected to be available(for example, the primary node in a high availability configuration), then ensure that the file system is available.
Usage: dspmqaut [-m QMgrName] [-n ObjName] -t ObjType
(-p Principal | -g Group) [-s ServiceComponent]
-g User group name.
-m Queue manager name.
-n Profile name, either an object name or a generic profile name.
-t Object type:
authinfo, channel, clntconn, comminfo, listener,
namelist, process, queue, qmgr, rqmname, service,
topic.
-p Principal name.
-s Name of the authorization service.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5605
Usage: endmqm [-z] [([-c | -w | -i | -p] [-r] [-s]) | -x] QMgrName
-c Controlled (or quiesced) shutdown.
-i Immediate shutdown.
-p Preemptive shutdown. Use only in exceptional circumstances.
-r Start trying to reconnect reconnectable clients.
-s Switch over to a standby queue manager instance after shutting down.
-w Wait shutdown. Waits until controlled shutdown is complete.
-x End standby queue manager instance, without ending the active instance.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5605 (IBM MQ Appliance)
Usage: endmqm [-c | -w | -i | -p] [-r] QMgrName
-c Controlled (or quiesced) shutdown.
-i Immediate shutdown.
-p Preemptive shutdown. Use only in exceptional circumstances.
-r Start trying to reconnect reconnectable clients.
-w Wait shutdown. Waits until controlled shutdown is complete.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5606
Usage: setmqaut [-m QMgrName] [-n Profile] -t ObjType
(-p Principal | -g Group)
[-s ServiceComponent] Authorizations
-g User group name.
-m Queue manager name.
-n Profile name, either an object name or a generic profile name.
-t Object type:
authinfo, channel, clntconn, comminfo, listener,
namelist, process, queue, qmgr, rqmname, service,
topic.
-p Principal name.
-s Name of the authorization service.
Authorizations: use + to grant and - to revoke.
MQI authorizations:
+altusr, -altusr, +browse, -browse, +connect, -connect,
+get, -get, +inq, -inq, +pub, -pub, +put, -put,
+resume, -resume, +set, -set, +sub, -sub
Context authorizations:
+passall, -passall, +passid, -passid,
+setall, -setall, +setid, -setid
Administration authorizations:
+chg, -chg, +clr, -clr, +crt, -crt, +dlt, -dlt,
+dsp, -dsp, +ctrl, -ctrl, +ctrlx, -ctrlx
Generic authorizations:
+all, -all, +alladm, -alladm, +allmqi, -allmqi,
+none, +system, -system
Remove authorizations using +remove or -remove.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5607
Usage: strmqm [-z] [-a | -c | -r | -x] [-d none|minimal|all] [-f]
[-ns] [-e CMDLEVEL=Level] [QMgrName]
-a Activate the backup queue manager.
-c Redefine the default and system objects, then stop the queue manager.
-d Detail level for informational messages.
-e Enable a command level's new functions, then stop the queue manager.
-f Fix corrupt or missing data directories.
-ns Do not start channel initiator, command server, services or listeners.
All connection authentication configuration is suppressed.
-r Update the backup queue manager, but do not start it.
-x Start an instance of a multi-instance queue manager.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5607 (IBM MQ Appliance)
Usage: strmqm [-c] [-d none|minimal|all] [-f]
[-ns] [-e CMDLEVEL=Level] QMgrName
-c Redefine the default and system objects, then stop the queue manager.
-d Detail level for informational messages.
-e Enable a command level's new functions, then stop the queue manager.
-f Fix corrupt or missing data directories.
-ns Do not start channel initiator, command server, services or listeners.
All connection authentication configuration is suppressed.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5607 (Windows)
Usage: strmqm [-z] [-a | -c | -r | -x] [-d none|minimal|all] [-f]
[-ns] [-ss | -si] [-e CMDLEVEL=Level] [QMgrName]
-a Activate the backup queue manager.
-c Redefine the default and system objects, then stop the queue manager.
-d Detail level for informational messages.
-e Enable a command level's new functions, then stop the queue manager.
-f Fix corrupt or missing data directories.
-ns Do not start channel initiator, command server, services or listeners.
All connection authentication configuration is suppressed.
-r Update the backup queue manager, but do not start it.
-si Start the queue manager under the logged on (interactive) user.
-ss Start the queue manager under the control of a service.
-x Start an instance of a multi-instance queue manager.
-z Suppress error messages.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5608
Usage: dspmqtrn [-m QMgrName] [-e] [-i] [-h] [-a [-q]]
-a Display details of all current transactions.
-e Display details of externally coordinated, in-doubt transactions.
-h Display details of heuristically completed transactions.
-i Display details of internally coordinated, in-doubt transactions.
-m Queue manager name.
-q Include a list of objects updated in current transactions
If none of -a, -e, -i, or -h is specified, details of all in-doubt transactions are displayed.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5609
Usage: rsvmqtrn -m QMgrName (-a | ((-b | -c | -f | -r RMId) Tran,Number))
-a Resolve all internally-coordinated, in-doubt transactions.
-b Back out the externally-coordinated, in-doubt transaction.
-c Commit the externally-coordinated, in-doubt transaction.
-f Forget the heuristically completed transaction.
-m Queue manager name.
-r Resource manager which can be ignored in the in-doubt transaction.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5610 (HP NSS)
Usage: strmqtrc [-t TraceType] [-x TraceType] [-s] [-l MaxFileSize]
[-e] [-p ProgramName] [-i Pid.Tid] [-d UserDataSize]
[-b StartTrigger] [-c StopTrigger]
-b Start trigger as a list of FDC probe IDs.
-c Stop trigger as a list of FDC probe IDs or interval.
-d The amount of user data to trace in bytes.
-e Start early tracing of all processes.
-i Start tracing for the specified process and thread.
-l The maximum size of a trace file in MB.
-p Start tracing for the supplied list of programs.
-s Report the tracing options currently in effect.
-t The points to trace and the amount of trace detail to record:
all, api, commentary, comms, csdata, csflows, detail, Explorer,
java, lqmdata, lqmflows, otherdata, otherflows, parms,
remotedata, remoteflows, servicedata, serviceflows,
splflows, spldata, soap, ssl, versiondata, mqxr or mqlight.
-x The points to exclude from the trace.
Usage: strmqtrc [-m QMgrName] [-t TraceType] [-x TraceType] [-s]
[-l MaxFileSize] [-e] [-p ProgramName] [-i Pid.Tid]
[-d UserDataSize] [-b StartTrigger] [-c StopTrigger]
[-w]
-b Start trigger as a list of FDC probe IDs.
-c Stop trigger as a list of FDC probe IDs or interval.
-d The amount of user data to trace in bytes.
-e Start early tracing of all processes.
-i Start tracing for the specified process and thread.
-l The maximum size of a trace file in MB.
-m Queue manager name.
-p Start tracing for the supplied list of programs.
-s Report the tracing options currently in effect.
-t The points to trace and the amount of trace detail to record:
all, api, commentary, comms, csdata, csflows, detail, Explorer,
java, lqmdata, lqmflows, otherdata, otherflows, parms,
remotedata, remoteflows, servicedata, serviceflows,
splflows, spldata, soap, ssl, versiondata, mqxr or mqlight.
-w Allow any application to trigger trace.
-x The points to exclude from the trace.
Severity
0 : Informational
Explanation
This applies to UNIX and Windows systems.
Response
None.
AMQ5611 (HP NSS)
Usage: endmqtrc [-p ProgramName] [-i Pid.Tid] [-a] [-e]
-a End all tracing.
-e End early tracing of all processes.
-i End tracing for the specified process and thread.
-p End tracing for the supplied list of programs.
This applies to AS/400 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.
AMQ5611 (Windows)
Usage: endmqtrc [-p ProgramName] [-i Pid.Tid] [-m QMgrName] [-a] [-e] [-w]
-a End all tracing.
-e End early tracing of all processes.
-i End tracing for the specified process and thread.
-m Queue manager name.
-p End tracing for the supplied list of programs.
-w Restrict triggering of trace to applications run by an
IBM MQ administrator.
Severity
0 : Informational
Explanation
This applies to UNIX and Windows systems.
Response
None.
AMQ5612
Usage: dspmqtrc [-t TemplateFile] [-hs] [-o OutputFileName]
[-C InputFileCCSID] InputFileName(s)
-C Specifies the CCSID value for the input file.
-h Skip the trace file header.
-o Save trace output to file.
-s Summary (format only the trace header).
-t Template file for formatting trace data.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5613
Usage: dspmq [-m QMgrName] [-o status | -s] [-o default]
[-o standby] [-o installation] [-x] [-n] [-a]
-a Display information about the active queue managers only. &M -m Queue manager name.
-n Suppress translation of output strings.
-o all
Display all status information for the queue managers.
-o status
Display the operational status of the queue managers.
-o default
Display whether any of the queue managers are the default.
-o standby
Display whether a queue manager currently permits a standby instance.
-o installation
Display the installation details of the queue managers.
-s Display the operational status of the queue managers.
-x Display information about instances of queue managers.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5613 (IBM MQ Appliance)
Usage: dspmq [-m QMgrName] [-o status | -s] [-o default] [-o ha] [-n] [-a]
-a Display information about the active queue managers only.
-m Queue manager name.
-n Suppress translation of output strings.
-o all
Display all status information for the queue managers.
-o status
Display the operational status of the queue managers.
-o default
Display whether any of the queue managers are the default.
-o ha
Display the high availability information for the queue managers.
-o dr
Display the disaster recovery information for the queue managers.
-s Display the operational status of the queue managers.
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 : Informational
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 : Informational
AMQ5619
string
Severity
0 : Informational
AMQ5620
channel_name
Severity
0 : Informational
AMQ5621
process_name
Severity
0 : Informational
AMQ5622
q_name
Severity
0 : Informational
AMQ5623
connection_name
Severity
0 : Informational
AMQ5624
generic_channel_name
Severity
0 : Informational
AMQ5625
generic_process_name
Severity
0 : Informational
AMQ5626
generic_q_name
Severity
0 : Informational
AMQ5627
qalias_name
Severity
0 : Informational
AMQ5628
qmodel_name
Severity
0 : Informational
AMQ5629
qlocal_name
Severity
0 : Informational
AMQ5630
qremote_name
Severity
0 : Informational
AMQ5631
namelist_name
Severity
0 : Informational
AMQ5632
generic_namelist_name
Severity
0 : Informational
AMQ5633
generic_Q_Mgr_name
Severity
0 : Informational
AMQ5634
generic_cluster_name
Severity
0 : Informational
AMQ5635
The argument supplied with the <insert_3> flag is not valid.
Severity
20 : Error
Explanation
The argument supplied with the -l parameter must be in the range 1 - 4293. The argument supplied with the -d parameter must be -1, 0 or greater than 15.
Response
Submit the command again with a valid argument.
AMQ5636
cluster_name
Severity
0 : Informational
AMQ5637
Test file format incorrect. Delete the test file and format it again making sure to allow formatting to complete.
Severity
20 : Error
Explanation
The test program does not recognise the format of the test file. This occurs if the formatting of the file was not allowed to run to completion.
Response
None.
AMQ5638
Usage: endmqsde -m QMgrName -n ServiceName [-t ServiceType]
End an existing IBM MQ service definition that is running.
-m Queue manager name.
-n Service name.
-t Service type.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5646
Usage: setmqcap Processors
Severity
0 : Informational
AMQ5647
Usage: dspmqcap
Severity
0 : Informational
AMQ5648
Usage: dmpmqaut [-m QMgrName] [-n Profile | -l] [-t ObjType]
[-p Principal | -g Group] [-s ServiceComponent] [-e | -x]
-e Dump all profiles used to calculate the entity's authorizations.
-g User group name.
-m Queue manager name.
-n Profile name, either an object name or a generic profile name.
-l Dump only the profile name and type.
-t Object type:
authinfo, channel, clntconn, comminfo, listener,
namelist, process, queue, qmgr, rqmname, service,
topic.
-p Principal name.
-s Name of the authorization service.
-x Dump all profiles which exactly match the profile name.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5649
generic_authinfo_name
Severity
0 : Informational
AMQ5650
authinfo_name
Severity
0 : Informational
AMQ5651
qmname
Severity
0 : Informational
AMQ5652
A task in the queue managers restartable utility process failed to connect to the IBM MQ queue manager for reason <insert_1>.
Severity
30 : Error
Explanation
The IBM MQ queue manager <insert_3> might have generated earlier messages or FFST information explaining why the task 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 save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ5653
The user <insert_3> is not defined.
Severity
30 : Error
Explanation
The system call getpwnam("<insert_3>") failed with errno <insert_1>.
Response
If you are trying to use user <insert_3> on this system, create the user and retry the operation. If you are trying to map from user <insert_3> to another user using CHLAUTH USERMAP rules, check that CHLAUTH is enabled on the queue manager and ensure the case is correct in your CHLAUTH rule. If you are trying to flow through the client side user <insert_3> remember that on UNIX, Linux and Windows the user ID received from the client is changed to lowercase.
AMQ5654
The test file is full of data, but it was filled by a single copy of the test program. Delete the test file and repeat the test. Once you have formatted the test file, make sure that you use two copies of the test program to append data to the test file, interrupting the first one while it is writing data.
Severity
20 : Error
Explanation
The test checks whether data integrity is maintained even when an outage occurs while data is being written. Interrupting the writing makes it more challenging to maintain data integrity. The test is successful only when the data read was written by more than one copy of the test program.
Response
None.
AMQ5655
<insert_1>-bit environments are not supported on this machine.
Severity
20 : Error
Explanation
The <insert_3> command was issued specifying that a <insert_1>-bit environment should be configured. However, this machine does not support <insert_1>-bit environments.
Response
Reissue the command specifiying a valid environment mode.
AMQ5656
IBM MQ cannot be used with filesystems that use mandatory file locking.
Severity
20 : Error
Explanation
IBM MQ is not compatible with mandatory file locking. This is normally only relevant on some network-attached storage devices which use mandatory file locking. IBM MQ was designed to use advisory file locking which is less restrictive.
Response
Use a filesystem which enforces less restrictive file locking behavior.
AMQ5657 (UNIX and Linux)
The system resource <insert_3> is set at an unusually low level for IBM MQ.
Severity
0 : Informational
Explanation
The system resource <insert_3> is currently set to <insert_1> which is below the usual minimum level of <insert_2>, recommended for IBM MQ.
Response
If possible, increase the current setting to at least <insert_2>.
AMQ5658
Installation name <insert_4> for the queue manager <insert_3> has been set without access to one or more queue manager configuration files.
Severity
20 : Error
Explanation
The installation name <insert_4> has been updated for the queue manager <insert_3> without validating the queue manager configuration because of failure in accessing one or more queue manager configuration files.
Response
Look at previous error messages for <insert_5> in this error log to determine the cause for the failure in accessing one or more files in the queue manager directory.
If the command was executed on a system where the queue manager data file system is not available (for example, the secondary node in a high availability configuration), then this is not an error condition.
If the command was executed on a system where the queue manager data file system is expected to be available(for example, the primary node in a high availability configuration), then ensure that the file system is available.
AMQ5659 (IBM i)
Unable to access trace control shared memory (<insert_1>)
Severity
0 : Informational
Explanation
An unexpected error accessing trace control memory has occured whilst attempting to start or stop trace. The attempt to access trace control failed with a return code of <insert_1>.
Response
Please contact your IBM representative.
AMQ5659 (UNIX and Linux)
Unable to access trace shared memory: <insert_1>
Severity
0 : Informational
Explanation
This applies to UNIX systems.
Response
Refer to IBM Service Personnel
AMQ5659 (Windows)
Unable to access trace control shared memory (<insert_1>)
Severity
20 : Error
Explanation
An unexpected error accessing trace control memory has occured whilst attempting to start or stop trace. The attempt to access trace control failed with a return code of <insert_1>.
Response
Please contact your IBM representative.
AMQ5660
Usage: dspmqrte [-c] [-n] [-l Persistence] [-m QMgrName] [-o] [-p Priority]
[-rq ReplyQName [-rqm ReplyQMgrName]] [-ro ReportOptions]
[-xs Expiry] [-xp Pass] [-qm TargetQMgrName] [-ac [-ar]]
[-d Delivery] [-f Forwarding] [-s Activities] [-t Detail]
[-i CorrelId] [-b] [-v Verbosity] [-w WaitTime] [-u UserId]
-q TargetQName | -ts TargetTopicString
-ac Accumulate activity information within the trace-route message.
-ar Request a trace-route reply message.
-b Browse activity reports and replies.
-c Connect to the queue manager as a client.
-d Whether to deliver the trace-route message on the target queue.
-f Forward trace-route message to queue managers:
all, supported.
-i Correlation identifier of activity information to display.
-l Persistence of the trace-route message:
yes, no, q.
-m Queue manager name.
-n Do not display activity information returned.
-o Do not bind the target queue to a specific destination in a cluster.
-p Priority of the trace-route message.
-q Target queue name.
-qm Target queue's queue manager name.
-rq Reply-to queue name.
-rqm Reply-to queue manager name.
-ro Report options:
none, activity, coa, cod, exception, expiration, discard.
-s Maximum number of activities resulting from this trace-route.
-t Detail of activities recorded:
low, medium, high.
-ts Target topic string for publishing the trace-route message.
-u UserId for connection to queue manager.
-v Display option:
summary, all, none, outline.
-w Time in seconds to wait for activity reports or replies.
-xp Whether to use MQRO_PASS_DISCARD_AND_EXPIRY:
yes, no.
-xs Expiry time for the trace-route message, in seconds.
Severity
0 : Informational
Explanation
This shows the correct usage of the DSPMQRTE command.
Usage: amqmfsck [-a | -c | -f [-p FileSize] | -i | -w | -x] [-v] DirectoryName
-a Append data to a test file for data integrity testing.
-c Test writing concurrently to a file.
-f Format a test file for data integrity testing.
-i Inspect the test file for data integrity testing.
-p Size of the data integrity test file in 4 KB pages.
-v Verbose output.
-w Test waiting for and releasing file locks.
-x Delete files created by tests in the directory.
If no option is specified, the program tests the basic behavior of the filesystem for use by IBM MQ for queue manager data and logs.
If either -a, -c or -w is specified, the program should be started concurrently on two servers with the same command line options. The directory should be on networked storage mounted at the same location on both servers.
The data integrity test has three phases. First, format a test file with the -f option. Second, append data to the test file with the -a option on two servers, introducing a failure on the first server while it is appending data. Third, when the test file is full, inspect the contents of the test file with the -i option to check whether data integrity was preserved.
The amqmfsck program was executed with '-?' or an incorrect parameter.
Response
Call the amqmfsck program with the following parameters:
a Append data to a test file for data integrity testing.
c Test writing concurrently to a file.
f Format a test file for data integrity testing.
i Inspect the test file for data integrity testing.
p Size of the data integrity test file in 4 KB pages.
v Verbose output.
w Test waiting for and releasing file locks.
x Delete files created by tests in the directory.
If no option is specified, the program tests the basic behavior of the filesystem for use by IBM MQ for queue manager data and logs.
If either -a, -c or -w is specified, the program should be started concurrently on two servers with the same command line options. The directory should be on networked storage mounted at the same location on both servers.
The data integrity test has three phases. First, format a test file with the -f option. Second, append data to the test file with the -a option on two servers, introducing a failure on the first server while it is appending data. Third, when the test file is full, inspect the contents of the test file with the -i option to check whether data integrity was preserved.
AMQ5665
Test files deleted.
Severity
0 : Informational
Explanation
The test program has deleted any test files found in the directory.
Response
None.
AMQ5666
System call: <insert_3>
Severity
0 : Informational
Explanation
This shows the information about an operating system call issued by amqmfsck.
Response
This information may be useful trying to diagnose a filesystem problem reported by amqmfsck. The sequence of system calls together with the failing error code indicate the cause of the failure.
AMQ5667
Error executing system call <insert_3> on file <insert_4>, errno <insert_1> (<insert_5>).
Severity
20 : Error
Explanation
This shows the information about an operating system call issued by amqmfsck.
Response
This information may be useful trying to diagnose a filesystem problem reported by amqmfsck. The sequence of system calls together with the failing error code indicate the cause of the failure.
AMQ5668
Start a second copy of this program with the same parameters on another server.
Severity
0 : Informational
Explanation
This test is intended to be run on two servers at the same time.
Response
Start another copy of the test program with the same command line parameters on another server.
AMQ5669
File lock acquired.
Severity
0 : Informational
Explanation
The test program acquired the file lock.
Response
None.
AMQ5670
Press Enter or terminate this process to release the lock.
Severity
0 : Informational
Explanation
The test program holds the file lock. The test is waiting.
Response
To release the lock explicitly in the test program, press Enter. To release it implicitly as part of process termination, terminate the process from the terminal or by sending it a signal. If the lock is on a network filesystem, the lock can be released by removing network connectivity or turning off the power.
AMQ5671
Waiting for the file lock.
Severity
0 : Informational
Explanation
The test program is waiting for the file lock.
Response
If the file lock is held by another instance of the test program, release the lock. It can take several seconds for the lock to be released if the lock holder lost network connectivity.
AMQ5672
File lock released.
Severity
0 : Informational
Explanation
The test program has released the file lock.
Response
None.
AMQ5673
Writing to test file. This will normally complete within about <insert_1> seconds.
Severity
0 : Informational
Explanation
The test program is starting a test of concurrent writing behavior.
Response
None.
AMQ5674
Trace file <insert_3> was produced by IBM MQ V<insert_4>.
Severity
20 : Error
Explanation
The dspmqtrc command attempted to format trace file <insert_3>. The trace file was produced by IBM MQ V<insert_4>, which is different from the version of dspmqtrc. Although dspmqtrc will have continued to try to format the trace file, the output may be incorrect.
Response
Format the trace files using the dspmqtrc command from the same installation that produced the files.
AMQ5675
Inconsistent use of installations detected.
Severity
20 : Error
Explanation
When executing program <insert_3> from IBM MQ installation <insert_4>, MQ detected that, due to the configuration of the environment, resources were loaded from MQ installation <insert_5>. The program cannot complete successfully while the program is executing using inconsistent installations. Incorrect use of the LD_LIBRARY_PATH environment variable can cause this error.
Response
If applicable, run program <insert_3> from MQ installation <insert_5> or configure the environment so that all resources required by program <insert_3> are loaded from MQ installation <insert_4>.
AMQ5675 (AIX)
Inconsistent use of installations detected.
Severity
20 : Error
Explanation
When executing program <insert_3> from IBM MQ installation <insert_4>, MQ detected that, due to the configuration of the environment, resources were loaded from MQ installation <insert_5>. The program cannot complete successfully while the program is executing using inconsistent installations. Incorrect use of the LIBPATH environment variable can cause this error.
Response
If applicable, run program <insert_3> from MQ installation <insert_5> or configure the environment so that all resources required by program <insert_3> are loaded from MQ installation <insert_4>.
AMQ5675 (HP-UX)
Inconsistent use of installations detected.
Severity
20 : Error
Explanation
When executing program <insert_3> from IBM MQ installation <insert_4>, MQ detected that, due to the configuration of the environment, resources were loaded from MQ installation <insert_5>. The program cannot complete successfully while the program is executing using inconsistent installations. Incorrect use of the SHLIB_PATH or LD_LIBRARY_PATH environment variable can cause this error.
Response
If applicable, run program <insert_3> from MQ installation <insert_5> or configure the environment so that all resources required by program <insert_3> are loaded from MQ installation <insert_4>.
AMQ5675 (Windows)
Inconsistent use of installations detected.
Severity
20 : Error
Explanation
When executing program <insert_3> from IBM MQ installation <insert_4>, MQ detected that, due to the configuration of the environment, resources were loaded from MQ installation <insert_5>. The program cannot complete successfully while the program is executing using inconsistent installations. Incorrect use of the PATH environment variable can cause this error.
Response
If applicable, run program <insert_3> from MQ installation <insert_5> or configure the environment so that all resources required by program <insert_3> are loaded from MQ installation <insert_4>.
AMQ5676
The filesystem being used is <insert_3>.
Severity
0 : Informational
Explanation
This message shows the name of the filesystem being tested with amqmfsck.
Response
None.
AMQ5677
Formatting test file for data integrity test.
Severity
0 : Informational
Explanation
The test program is formatting a test file to be used to test data integrity.
Response
None.
AMQ5678
Inconsistent data read at page <insert_1>, offset <insert_2>. The expected data was <insert_3>, but the actual data read was <insert_4>.
Severity
20 : Error
Explanation
The test program has read data which appears inconsistent. This could indicate a problem with data integrity on the filesystem being tested.
Response
None.
AMQ5679
Reading test file checking the integrity of the data read.
Severity
0 : Informational
Explanation
The test program is reading the data in the test file, checking for integrity.
Response
None.
AMQ5680
Writing data into test file. Once the other copy of the program has begun waiting on the file lock, interrupt this program by ending the process, temporarily breaking the network connection to the networked storage, rebooting the server or turning off the power.
Severity
0 : Informational
Explanation
The test program is writing data into the test file. The test checks whether data integrity is maintained even when an outage occurs as data is being written. Interrupting the writing makes it more challenging to maintain data integrity.
Response
None.
AMQ5681
Appending data into the test file after data already found.
Severity
0 : Informational
Explanation
The test program has read some existing data in the test file and is now appending its own data.
Response
None.
AMQ5682
The data read was consistent.
Severity
0 : Informational
Explanation
The test program has completed reading the data in the test file. No inconsistencies were found in the data.
Response
None.
AMQ5683
The test file is full of data. It is ready to be inspected for data integrity.
Severity
0 : Informational
Explanation
The test program has filled the test file with data. It is ready to be inspected for data integrity.
Response
None.
AMQ5684
The test file is not yet full of data. Run the test program again to continue writing data into the test file.
Severity
0 : Informational
Explanation
The test program has not yet filled the test file with data. The test file must be filled before it can be inspected for data integrity.
The installation name is either not valid or not known.
Severity
20 : Error
Explanation
Either the specified installation name does not conform to the rules required by IBM MQ or the installation does not exist. The rules for naming MQ objects are detailed in the IBM MQ Command Reference. This message can also occur when specifying an option to a command that contains a path. To ensure that the installation name is correctly passed to MQ by the Microsoft Windows command interpreter escape all directory separators in the path ("\\") or do not surround the path in quotation marks.
Response
Correct the name and submit the command again.
AMQ5687
<insert_3> is not executing from installation <insert_4>.
Severity
20 : Error
Explanation
The command <insert_3> was issued specifying installation name <insert_4>, but the command is executing from installation <insert_5>. The command must be executing from installation <insert_4> if that installation name is specified.
Response
Correct the command and submit it again.
AMQ5688
Unable to associate queue manager <insert_3> with installation <insert_4>.
Severity
20 : Error
Explanation
The request to associate queue manager <insert_3> with installation <insert_4> failed. This could be caused by the MQ version with which the queue manager was previously running being greater than the version of installation <insert_4>.
Response
Check that the installation specified is as intended and reissue the command.
AMQ5689
A queue manager name is required but you did not specify one.
Severity
20 : Error
Explanation
The command needs a queue manager name, but you did not specify one.
Response
Correct the command and submit it again.
AMQ5690
An installation name is required but you did not specify one.
Severity
20 : Error
Explanation
The command needs an installation name, but you did not specify one.
Response
Correct the command and submit it again.
AMQ5691
Queue manager <insert_4> is associated with a different installation (<insert_5>).
Severity
20 : Error
Explanation
The command <insert_3> was issued against queue manager <insert_4>, but the queue manager is associated with a different installation than the one currently in use, <insert_5>. In order for the command to succeed, the installation that the command is executing from must match the installation that the queue manager is associated with.
Response
Either change the installation the command is being executed from using the setmqenv command or associate the queue manager with the current installation using the setmqm command.
AMQ5692
The queue manager is associated with installation <insert_3>.
Severity
0 : Informational
Explanation
This is an informational message indicating which installation the queue manager is associated with.
Response
None.
AMQ5693
Test file already exists.
Severity
20 : Error
Explanation
The test file for the data integrity test already exists in this directory.
Response
To format another test file, first delete the existing file.
AMQ5694
Test file does not exist.
Severity
20 : Error
Explanation
The test file for the data integrity test does not exist in this directory.
Response
Use the test program to create and format the test file in order to begin the data integrity test in this directory.
AMQ5695
Test file formatted with <insert_1> pages of data.
Severity
0 : Informational
Explanation
The test file for the data integrity test has been formatted with <insert_1> pages of 4 kilobytes. The test file can now be used for the data integrity test.
Response
None.
AMQ5696
Queue manager <insert_3> is already associated with installation <insert_4>.
Severity
20 : Error
Explanation
An attempt was made to associate queue manager <insert_3> with installation <insert_4>. However, the queue manager is already associated with that installation.
Response
Ensure that the queue manager name is correct. If you did intend to associate this queue manager with a different installation, use the setmqm command from the installation you wish to associate the queue manager with.
AMQ5697 (UNIX and Linux)
Usage: crtmqenv (-m QMgrName | -n InstallationName | -p Path | -r | -s)
[-i] [-k | -l] [-x 32|64] [-z]
Create an environment that can be applied to the current shell using setmqenv.
-i Create an environment that can be used within a profile.
-k Add IBM MQ to start of the library path in the environment created.
-l Add IBM MQ to end of the library path in the environment created.
-m Create an environment for the specified queue manager.
-n Create an environment for the specified installation.
-p Create an environment for the installation located in the specified path.
-r Remove IBM MQ from the environment.
-s Create an environment for the installation that this command comes from.
-x Create a 32-bit or 64-bit environment.
-z Indicate the command is being called by setmqenv.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5697 (Windows)
Usage: crtmqenv (-m QMgrName| -n InstallationName | -p Path | -r | -s)
[-i] [-x 32|64] [-z]
Create an environment that can be applied to the current shell using setmqenv.
-i Create an environment that can be used within a profile.
-m Create an environment for the specified queue manager.
-n Create an environment for the specified installation.
-p Create an environment for the installation located in the specified path.
-r Remove IBM MQ from the environment.
-s Create an environment for the installation that this command comes from.
-x Create a 32-bit or 64-bit environment.
-z Indicate the command is being called by setmqenv.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5698 (UNIX and Linux)
Usage: setmqenv (-m QMgrName | -n InstallationName | -p Path | -r | -s)
[-x 32|64] [-k | -l]
Set up the environment for use with IBM MQ.
-k Set the library path, adding to the start of the current value.
-l Set the library path, adding to the end of the current value.
-m Set the environment for the specified queue manager.
-n Set the environment for the specified installation.
-p Set the environment for the installation located in the specified path.
-r Remove IBM MQ from the environment.
-s Set the environment for the installation that this command comes from.
-x Set a 32-bit or 64-bit environment.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5698 (Windows)
Usage: setmqenv (-m QMgrName| -n InstallationName | -p Path | -r | -s)
[-x 32|64]
Set up the environment for use with IBM MQ.
-m Set the environment for the specified queue manager.
-n Set the environment for the specified installation.
-p Set the environment for the installation located in the specified path.
-r Remove IBM MQ from the environment.
-s Set the environment for the installation that this command comes from.
-x Set a 32-bit or 64-bit environment.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5699
The installation path is either not valid or not known.
Severity
20 : Error
Explanation
Either the specified installation path does not conform to the rules required by IBM MQ or an installation at that path does not exist. The rules for installation paths can be found in the IBM MQ documentation.
This message can also occur when specifying an option to a command that contains a path. To ensure that the installation name is correctly passed to MQ by the Microsoft Windows command interpreter escape all directory separators in the path ("\\") or do not surround the path in quotation marks.
Response
Correct the path and submit the command again.
AMQ5700
listener_name
Severity
0 : Informational
AMQ5701
service_name
Severity
0 : Informational
AMQ5703
Usage: dmpmqcfg [-m QMgrName] [-n ObjName] [-t ObjType]
[-x ExportType] [-o Format] [-a] [-z]
[-s MsgSeqNo] [-q ReplyQName] [-r RemoteQMgrName]
[-u UserId] [-w NumSecs]
[-c default|-c DEFINE CHANNEL..]
-a Dump all attributes.
-c Client connection:
default, DEFINE CHANNEL(chlname) CHLTYPE(CLNTCONN) ...
-m Queue manager name.
-n Object name or a generic object name.
-o Format: mqsc, 1line, 2line, setmqaut, grtmqmaut, setmqspl.
-q Reply-to queue name, default SYSTEM.DEFAULT.MODEL.QUEUE.
-r Remote queue manager name (queued mode).
-s Reset channel message sequence number.
-t Object type:
all, authinfo, channel, clntconn, comminfo, listener,
mqttchl, namelist, process, queue, qmgr, service, topic.
-u UserId. If specified, a password is requested.
-w Timeout number of seconds
-x Export type:
all, authrec, chlauth, object, policy, sub.
-z Suppress warnings.
IBM MQ queue manager <insert_3> is running under a newer release of IBM MQ at command level <insert_1>.
Severity
20 : Error
Explanation
The queue manager has been started by a newer release of IBM MQ at command level <insert_1>, this command only supports queue managers running up to and including command level <insert_2>.
Response
Use a newer version of this command that supports command level <insert_1>.
AMQ5705
IBM MQ queue manager <insert_3> does not support <insert_4>.
Severity
20 : Error
Explanation
The queue manager does not support the PCF inquiry required by <insert_4>.
Response
Use command defaults or specify -z to suppress this warning.
AMQ5706
One or more MQSC parameter values were masked.
Severity
20 : Error
Explanation
The queue manager configuration dump included one or more masked values which if replayed would not correctly recreate the objects configuration. The values were masked to prevent sensitive data, such as passwords from being included in cleartext in the configuration dump.
Response
If replaying the dump configuration with MQSC, first check the dump output for masked parameters such as SSLCRYP, PASSWORD or LDAPPWD that have been commented and issue additional commands to substitute valid values.
AMQ5749
display_cmd
Severity
0 : Informational
AMQ5750
filter_keyword
Severity
0 : Informational
AMQ5751
operator
Severity
0 : Informational
AMQ5752
filter_value
Severity
0 : Informational
AMQ5753
topic_name
Severity
0 : Informational
AMQ5754
obj_name
Severity
0 : Informational
AMQ5755
generic_topic_name
Severity
0 : Informational
AMQ5756
subscription_name
Severity
0 : Informational
AMQ5757
subscription_id
Severity
0 : Informational
AMQ5758
generic_topic_string
Severity
0 : Informational
AMQ5759
comminfo_name
Severity
0 : Informational
AMQ5760
principal_name
Severity
0 : Informational
AMQ5761
group_name
Severity
0 : Informational
AMQ5762
service_component_name
Severity
0 : Informational
AMQ5763
profile_name
Severity
0 : Informational
AMQ5764
authority_list
Severity
0 : Informational
AMQ5765
channel_profile
Severity
0 : Informational
AMQ5805
Queued Publish/Subscribe Daemon currently running for queue manager.
Severity
10 : Warning
Explanation
The command was unsuccessful because queue manager <insert_3> currently has a Queued Publish/Subscribe Daemon running.
Response
None.
AMQ5806
Queued Publish/Subscribe Daemon started for queue manager <insert_3>.
Severity
0 : Informational
Explanation
Queued Publish/Subscribe Daemon started for queue manager <insert_3>.
Response
None.
AMQ5807
Queued Publish/Subscribe Daemon for queue manager <insert_3> ended.
Severity
0 : Informational
Explanation
The Queued Publish/Subscribe Daemon on queue manager <insert_3> has ended.
Response
None.
AMQ5808
Queued Publish/Subscribe Daemon for queue manager <insert_3> is already quiescing.
Severity
10 : Warning
Explanation
The endmqbrk command was unsuccessful because an orderly shutdown of the Queued Publish/Subcribe Daemon running on queue manager <insert_3> is already in progress.
Response
None.
AMQ5808 (IBM i)
IBM 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
Unable to process publication messages due to get disabled stream queue.
Severity
10 : Warning
Explanation
The stream queue (<insert_3>) has been get disabled, preventing the queued publish/suscribe daemon from processing publication messages. The queued publish/subscribe daemon will continue to process publication messages on other stream queues and subscriptions on all streams.
Response
To resume processing publication messages get enable the stream queue. To quiesce the stream remove name from SYSTEM.QPUBSUB.QUEUE.NAMELIST. To quiesce the queued publish/subscribe daemon alter the queue manager attribute PSMODE to COMPAT.
AMQ5810
Queued publish/subscribe unable to process subscription requests.
Severity
10 : Warning
Explanation
The queued publish/subscribe control queue (SYSTEM.BROKER.CONTROL.QUEUE) has been get disabled, preventing the queued publish/suscribe daemon from processing subscription requests. The queued publish/subscribe daemon will continue to process publication messages on stream queues.
Response
To resume processing subscription request get enable SYSTEM.BROKER.CONTROL.QUEUE. To quiesce the queued publish/subscribe daemon alter the queue manager attribute PSMODE to COMPAT.
AMQ5812
Queued Publish/Subscribe Daemon for queue manager <insert_3> stopping.
Severity
0 : Informational
Explanation
The Queued Publish/Subscribe Daemon is currently performing an immediate shutdown. Another attempt has been issued to request that the Queued Publish/Subscribe Daemon terminate, the attempt is unsuccessful because the Queued Publish/Subscribe Daemon is already performing an immediate shutdown.
Response
None.
AMQ5813
Queued Publish/Subscribe Daemon for queue manager <insert_3> not active.
Severity
0 : Informational
Explanation
A queue manager administration command has been issued to query or change the state of the Queued Publish/Subscribe Daemon. The Queued Publish/Subscribe Daemon is not currently running.
Response
None.
AMQ5814
Queued publish/subscribe daemon unable to resolve parent queue manager.
Severity
10 : Warning
Explanation
In establishing a publish/subscribe hierarchy, the queued publish/subscribe daemon is unable to resolve the parent queue manager (<insert_3>). The status of the publish/subscribe parent connection will be set to error.
Response
Check that the parent queue manager is correctly specified. Ensure the queue manager is able to resolve the queue manager name of the parent. To resolve the queue manager name, at least one of the following resources must be configured: - A transmission queue with the same name as the parent queue manager name. - A queue manager alias definition with the same name as the parent queue manager name. - A cluster with the parent queue manager as a member of the same cluster as this queue manager. - A cluster queue manager alias definition with the same name as the parent queue manager name. - A default transmission queue. After you have set up the configuration correctly, modify the parent queue manager name to blank. Then set the parent queue manager name.
AMQ5815
Invalid Queued Publish/Subscribe initialization file stanza for queue manager (<insert_3>).
Severity
20 : Error
Explanation
The broker stanza in the queue manager initialization file is not valid. The Queued Publish/Subscribe Daemon will terminate immediately. The invalid attribute is <insert_5>.
Response
Correct the broker stanza in the queue manager initialization file.
AMQ5816
Unable to open Queued Publish/Subscribe control queue for reason <insert_1>,<insert_2>.
Severity
20 : Error
Explanation
The queue manager 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 control queue for exclusive access, or that the control queue has been defined incorrectly. The Queued Publish/Subscribe Daemon will terminate immediately.
Response
Correct the problem and restart the queued publish/subscribe interface.
AMQ5817
An invalid stream queue has been detected by the broker.
Severity
10 : Warning
Explanation
IBM 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. 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 Queued Publish/Subscribe stream queue.
Severity
10 : Warning
Explanation
The queue manager 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 reasons for this error are:
(1) a new stream name has been added to SYSTEM.QPUBSUB.QUEUE.NAMELIST but the stream queue does not exist.
(2) an application has the queue open for exclusive access.
Response
Correct the problem. Then remove and re-add the stream queue to the SYSTEM.QPUBSUB.QUEUE.NAMELIST.
AMQ5819
Queued Publish/Subscribe stream has ended abnormally.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon stream (<insert_3>) has ended abnormally for reason <insert_1>. The queue manager will attempt to restart the stream. If the stream should repeatedly fail then the Queued Publish/Subscribe Daemon 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, save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
The queue manager 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
Queued publish/subscribe daemon unable to contact parent queue manager.
Severity
10 : Warning
Explanation
In establishing a publish/subscribe hierarchy, the queued pub/sub daemon is unable to send a message to the parent queue manager (<insert_3>) for reason <insert_1>. The status of the publish/subscribe parent connection will be set to error.
Response
Investigate why the problem occurred and take appropriate action to correct the problem. After the problem has been corrected, modify the parent queue manager name to blank. Then set the parent queue manager name.
AMQ5822
Failed to register with parent.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon has been started and the PARENT queue manager was set to <insert_3> in a queue manager attribute. The queue manager attempted to register as a child of the parent broker, but received an exception response (<insert_1>) indicating that it was not possible. The queue manager 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 queue manager not yet existing, or a problem with the SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS queue at the parent queue manager.
AMQ5824
Inconsistent use of publish/subscribe hierarchy streams and PROXYSUB FORCE attribute detected
Severity
10 : Warning
Explanation
Topic object <insert_3> is a publish/subscribe hierarchy stream. <insert_4> is a higher topic object in the topic tree that has set PROXYSUB to be FORCE, this results in a single wildcarded proxy subscription being sent to the neighboring queue managers in the publish/subscribe hierarchy that support the higher topic's stream. No further individual proxy subscriptions will be sent for any subscriptions made below this higher point in the topic tree, including below topic object <insert_3>. If a neighboring queue manager supports the <insert_3> stream but not the higher stream, publications will not be sent to subscriptions to topic <insert_3> on this queue manager from that neighbor.
Response
If this is the intended behaviour or this queue manager is not a member of a publish/subscribe hierarchy then this warning can be ignored. However, it is not recommended to use nested streams in the topic tree. If possible reorganise the streams to remove the nesting. Alternatively, object <insert_3> should also set PROXYSUB to be FORCE or the FORCE setting should be removed from topic object <insert_4>.
AMQ5826
Failed to propagate a subscription to another queue manager.
Severity
10 : Warning
Explanation
The queue manager failed to propagate subscription to stream (<insert_4>) at queue manager (<insert_3>). Reason codes <insert_1> and <insert_2>. An application has either registered or deregistered a subscription to stream (<insert_4>). The queue manager has attempted to propagate the subscription change to queue manager (<insert_3>) but the request has not been successful. Messages published on stream (<insert_4>) through queue manager (<insert_3>) might not reach this queue manager.
Response
Use the reason codes to investigate why the problem occurred and take appropriate action to correct the problem. Use the command
REFRESH QMGR TYPE(PROXYSUB)
to refresh proxy subscriptions.
The queue manager failed to subscribe to stream (<insert_4>) at queue manager (<insert_3>) with reason codes <insert_1> and <insert_2>. Related queue managers learn about each others configuration by subscribing to information published by each other. A queue manager discovered that one of these internal subscriptions has failed. The queue manager will reissue the subscription immediately. The publish/subscribe hierarchy cannot function correctly without knowing this information from neighboring queue managers, this will 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 causes of this failure are: a problem with the SYSTEM.BROKER.CONTROL.QUEUE at the other queue manager; a problem with the definition of the route between this queue manager and the other queue manager or the other queue manager has forcibly reset its relationship with this queue manager.
AMQ5829
Usage: amqfqpub [-m QMgrName] Note: Users should not manually run this command!
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5830
The endmqbrk command can no longer be used. The queued publish/subscribe interface is enabled/disabled by altering the queue manager's PSMODE attribute. Setting PSMODE to "COMPAT" disables the queued publish/subscribe interface.
Severity
0 : Informational
Explanation
The endmqbrk command (shipped with earlier versions of MQ) is no longer used to enable/disable the queued publish/subscribe interface. Instead of issuing the endmqbrk command the PSMODE attribute of the queue manager should be set to COMPAT.
Response
None.
AMQ5831
Unable to make subscription.
Severity
20 : Error
Explanation
A failure occured while attempting to create a subscription to topic string <insert_4>. The associated reason code is <insert_1>.
Response
Use the reason code shown in the message to determine the cause of the failure and take appropriate action to rectify the problem.
AMQ5832
Queued Publish/Subscribe Daemon failed to publish configuration information on SYSTEM.BROKER.ADMIN.STREAM.
Severity
10 : Warning
Explanation
Related queue managers learn about each others configuration by subscribing to information published by each other. A queue manager has discovered that one of these internal publications has failed. The queue manager will republish the information immediately. Queue managers cannot function correctly without knowing some information about neighboring queue manager The information that neighboring queue managers have of this queue manager 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
Queue manager (<insert_3>) introduced a loop into the Publish/Subscribe hierarchy.
Severity
20 : Error
Explanation
The queue manager (<insert_3>), introduced a loop in the Publish/Subscribe hierarchy. The Queued Publish/Subscribe Daemon on this queue manager will terminate immediately.
Response
Remove queue manager (<insert_3>) from the hierarchy, by removing knowledge of the queue manager's parent, using the "ALTER QMGR PARENT(' ')" MQSC command, or in exceptional circumstances, "RESET QMGR TYPE(PUBSUB) PARENT(<insert_3>)".
AMQ5834
Conflicting queue manager names in the Publish/Subscribe 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 queue manager name should be unique to ensure that no confusion arises within the 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
Unable inform parent (<insert_3>) of new relation (<insert_4>) for reason <insert_1>.
Severity
0 : Informational
Explanation
The queue manager failed to notify its parent queue manager (<insert_3>) of the relation (<insert_4>) in the Publish/Subscribe hierarchy. The notification message will be put to the parent's dead-letter queue. A failure to notify a queue manager 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 queue manager does not yet exist.
AMQ5836
Duplicate queue manager name located in the Publish/Subscribe hierarchy.
Severity
0 : Informational
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 Publish/Subscribe hierarchy, or multiple queue managers in the Publish/Subscribe hierarchy having the same name.
Response
If this queue manager 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 Publish/Subscribe hierarchy has a unique name. It is not recommended that multiple queue managers use the same name.
AMQ5837
IBM 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 (IBM i)
IBM 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
IBM 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
Unexpected topology information received from queue manager (<insert_3>).
Severity
10 : Warning
Explanation
A queue manager has received an distributed publish/subscribe communication that it did not expect. The message was sent by queue manager (<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 queue manager topology has been changed while distributed publish/subscribe communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous queue manager topology has arrived at a queue manager in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication.
Response
If the queue manager topology has changed and the queue manager named in the message is no longer related to the queue manager issuing this message, this message can be ignored. If the "RESET QMGR TYPE(PUBSUB)" MQSC command was issued to unilaterally remove knowledge of queue manager (<insert_3>) from this queue manager, the "RESET QMGR TYPE(PUBSUB)" MQSC command should also be used to remove knowledge of this queue manager from queue manager (<insert_3>) .
AMQ5840
Queued Publish/Subscribe Daemon unable to delete queue.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon has failed to delete the queue (<insert_3>) for reason <insert_2>.
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 queue manager environment, it is likely that a message channel agent might have queues open, which the Queued Publish/Subscribe Daemon is trying to delete.
AMQ5841
IBM MQ Publish/Subscribe broker (<insert_3>) deleted.
Severity
0 : Informational
Explanation
The broker (<insert_3>) has been deleted using the dltmqbrk command.
Response
None.
AMQ5842
IBM 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 (IBM i)
IBM MQ Publish/Subscribe broker cannot be deleted.
Severity
20 : Error
Explanation
An attempt has been made to delete the IBM 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
IBM 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 (IBM i)
IBM 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 <insert_4> is unknown.
Severity
10 : Warning
Explanation
The "reset qmgr type(pubsub)" MQSC command (or its PCF equivalent) has been issued in an attempt to remove a queue manager's knowledge of a relation of that queue manager. The relative (<insert_4>) is unknown at broker (<insert_3>). If the "parent" attribute was specified, the broker does not currently have a parent. If the "child" attribute was specified, the broker does not recognize the named child.
Response
Investigate why the broker is unknown.
AMQ5845
Usage: dltmqbrk -m QMgrName
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ5847
A publish exit has caused an error in the Queued Publish/Subscribe Daemon.
Severity
20 : Error
Explanation
The Queued Publish/Subscribe Daemon uses publications for internal state and these publications are processed by publish exits configured for the queue manager. An MQRC_PUBLISH_EXIT_ERROR reason returned by a publish exit will result in the Queued Publish/Subscribe Daemon failing to function correctly.
Response
Publish exits must not modify the internal state publications and must not fail when processing then. The publish exit must be modified or removed from the queue manager to enable the Queued Publish/Subscribe Daemon to function correctly.
AMQ5848
Register proxy subscription for queue manager <insert_3> failed with reason <insert_1>.
Severity
20 : Error
Explanation
The queue manager received a proxy subscription request for stream (<insert_4>) topic (<insert_5>) from queue manager (<insert_3>). The attempt to register the subscription was unsuccessful for reason code <insert_1>. Messages published upon this topic will not be delivered to subscriptions on the relation queue manager.
Response
Use the reason code to investigate why the failure occurred and take appropriate action to correct the problem. Use the command
REFRESH QMGR TYPE(PROXYSUB)
on the relation queue manager to refresh it's proxy subscriptions.
AMQ5850
Queued Publish/Subscribe Daemon interrupted while creating queue.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon was interrupted while creating queue (<insert_3>) for user ID (<insert_4>). When the Queued Publish/Subscribe Daemon 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 Queued Publish/Subscribe Daemon should be interrupted during this operation (for example the queue manager is shut down), the Queued Publish/Subscribe Daemon cannot reliably detect that the security attributes have not been set correctly. The Queued Publish/Subscribe Daemon 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
Queued Publish/Subscribe Daemon interrupted while creating internal queue.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon was interrupted while creating internal queue (<insert_3>) for user ID (<insert_4>). When the Queued Publish/Subscribe Daemon 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 Queued Publish/Subscribe Daemon should be interrupted during this operation (for example the queue manager is shut down), the Queued Publish/Subscribe Daemon 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 Queued Publish/Subscribe Daemon 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
Unable to propagate delete publication command.
Severity
0 : Informational
Explanation
The queue manager failed to propagate delete publication command for stream (<insert_3>) to related queue manager (<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 queue managers in the sub-hierarchy supporting the stream. The queue manager reporting the error has failed to forward a delete publication command to a related queue manager (<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 queue manager, this message can be ignored. Investigate why the delete publication has failed and take the appropriate action to recover the failed command.
AMQ5853
Unable to propagate delete publication command.
Severity
0 : Informational
Explanation
The queue manager failed to propagate a delete publication command for stream (<insert_3>) to a previously related queue manager (<insert_4>). In some cases the stream or the relation cannot be determined and so is shown as '????'.
When an application issues a delete publication command to delete a global publication, the command is propagated to all queue managers in the sub-hierarchy supporting the stream. The queue manager topology was changed after deleting the publication, but before a queue manager removed by the topology change processed the propagated delete publication message. The topic for which the delete publication has failed is (<insert_5>). In some cases the topic cannot be determined and so is shown as '????'.
Response
The delete publication command will have been written to the dead-letter queue at the queue manager that was removed from the topology. In this case, further action might be necessary to propagate the delete publication command.
AMQ5854
Unable to propagate delete publication command.
Severity
0 : Informational
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, queue manager (<insert_4>) was a known relation of this queue manager supporting stream (<insert_3>). Before the delete publication command arrived at the related queue manager, the queue manager topology was changed so that queue manager (<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 queue manager activity before changing the stream topology of the queue manager. Investigate why this delete publication activity was not quiesced. The delete publication command will have been written to the dead-letter queue at queue manager (<insert_4>).
AMQ5855
Queued Pub/Sub Daemon failed.
Severity
10 : Warning
Explanation
An attempt has been made to run the queued publish/subscribe interface (Queued Publish/Subscribe Daemon) (<insert_3>) but the interface has ended for reason <insert_1>:<insert_5>.
Response
Determine why the Queued Publish/Subscribe Daemon ended. The message logs for the queue manager might contain more detailed information on why the Queued Publish/Subscribe Daemon cannot be started. Resolve the problem that is preventing the command from completing and restart the Queued Publish/Subscribe Daemon by issuing the following commands: ALTER QMGR PSMODE(COMPAT) Followed by: ALTER QMGR PSMODE(ENABLED)
AMQ5856
Unable to process publish command message. Reason code <insert_1>.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon failed to process a publish message for stream (<insert_3>). The queue manager was unable to write the publication to the dead-letter queue and was not permitted to discard the publication. The queue manager 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
Unable to process control command message. Reason code <insert_1>.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe Daemon failed to process a command message on the SYSTEM.BROKER.CONTROL.QUEUE. The queue manager was unable to write the command message to the dead-letter queue and was not permitted to discard the command message. The queue manager will temporarily stop the stream and will restart the stream and consequently retry the command message after a short interval. Other queue manager 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
Queued Publish/Subscribe stream is terminating due to an internal resource problem.
Severity
10 : Warning
Explanation
The 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 queue manager. 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 use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ5860
Unable to open source data file <insert_3>.
Severity
20 : Error
Explanation
The migration utility was not able to open the named file when attempting to read in the pub/sub state. By default, the utility looks for that file in the current default directory.
Response
Make sure that the named file exists and is readable.
AMQ5861
The format of the source data file <insert_3> is not valid.
Severity
20 : Error
Explanation
The migration utility was able to open the named file, however the contents are not valid pub/sub state information.
Response
Check that the named file has not beed edited or damaged since it was written.
AMQ5864
Unable to put a reply message. The command will be retried.
Severity
10 : Warning
Explanation
While processing a publish/subscribe command, the queue manager could not send a reply message to queue (<insert_4>) at queue manager (<insert_3>) for reason <insert_1>. The queue manager was also unable to write the message to the dead-letter queue. Since the command is being processed under syncpoint control, the queue manager 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
Queued Publish/Subscribe reply message could not be sent.
Severity
10 : Warning
Explanation
While processing a publish/subscribe command, the queue manager could not send a reply message to queue (<insert_4>) at queue manager (<insert_3>) for reason <insert_1>. The queue manager was also unable to write the message to the dead-letter queue. As the command is not being processed under syncpoint control, the queue manager 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
Queued Publish/Subscribe command message has been discarded. Reason code <insert_1>.
Severity
10 : Warning
Explanation
The queue manager failed to process a publish/subscribe command message, which has now been discarded. The queue manager 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
Queued Publish/Subscribe stream has ended abnormally.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe stream (<insert_3>) has ended abnormally for reason <insert_1>. The queue manager will attempt to restart the stream. If the stream should repeatedly fail, the queue manager 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.
AMQ5868
User is no longer authorized to subscribe to stream.
Severity
0 : Informational
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 the subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While userid (<insert_3>) remains unauthorized, the broker will continue to deregister subscriptions associated with that userid.
Response
If the authority of userid (<insert_3>) was intentionally removed, consider removing all of that userid's 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.
AMQ5870
(Unexpected Error)
Severity
0 : Informational
Explanation
N/A
Response
N/A
AMQ5871
(Resource Problem)
Severity
0 : Informational
Explanation
N/A
Response
N/A
AMQ5872
(IBM MQ Publish/Subscribe broker has a known child)
Severity
0 : Informational
Explanation
N/A
Response
N/A
AMQ5873
(Queued Publish/Subscribe Daemon active)
Severity
0 : Informational
Explanation
N/A
Response
N/A
AMQ5874
(One or more queues could not be quiesced)
Severity
0 : Informational
Explanation
N/A
Response
N/A
AMQ5875
Unable to put message to the dead-letter queue.
Severity
10 : Warning
Explanation
The queue manager 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 Publish/Subscribe hierarchy.
Severity
20 : Error
Explanation
The queue manager (<insert_3>) has named this queue manager as its parent. This queue manager has already named queue manager (<insert_3>) as its parent. The queue manager will send an exception message to queue manager (<insert_3>) indicating that a conflict has been detected. The most likely reason for this message is that the pub/sub hierarchy has been changed while inter-queue manager communication messages were in transit (for example, on a transmission queue) and that a message relating to the previous pub/sub hierarchy has arrived at a queue manager in the new topology. This message may be accompanied by an informational FFST including details of the unexpected communication.
Response
If the pub/sub hierarchy has changed and the queue manager named in the message no longer identifies this queue manager as its parent, this message can be ignored - for example, if the MQSC command "ALTER QMGR PARENT(' ')" was issued. If queue manager(<insert_3>) has been defined as this queue manager's parent, and this queue manager has been defined as queue manager (<insert_3>)'s parent, the "ALTER QMGR PARENT" MQSC command should be used to resolve the conflict.
AMQ5877
Queued Publish/Subscribe stream has ended abnormally.
Severity
10 : Warning
Explanation
A Queued Publish/Subscribe stream (<insert_3>) has ended abnormally for reason <insert_1>. The daemon recovery routines failed to reset the stream state and the stream cannot be restarted automatically.
Response
Investigate why the stream failed and why the daemon 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 save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ5878
IBM 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, save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ5879
IBM MQ Publish/Subscribe broker has been migrated.
Severity
10 : Warning
Explanation
The command was unsuccessful because the IBM MQ Publish/Subscribe 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 : Informational
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 userid's subscription is deregistered. An event publication containing details of the subscription that was removed is published on SYSTEM.BROKER.ADMIN.STREAM. While userid (<insert_3>) remains unauthorized, the broker will continue to deregister subscriptions associated with that user ID.
Response
If the authority of userid (<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 IBM 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.
A 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.
A 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.
A 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 IBM 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
Message written to the dead-letter queue.
Severity
10 : Warning
Explanation
The queue manager 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
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
Queued Publish/Subscribe state not recorded.
Severity
10 : Warning
Explanation
The Queued Publish/Subscribe 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 queue manager has been configured with the SyncPointIfPersistent option set. A failure has occurred hardening either the publisher registration or the retained publication to the queue manager's local queue. All state changes attempted as a result of this publication will be backed-out. Processing of the publication will continue and the queue manager 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 queue manager. The most likely cause is 'queue full' on a 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 queue manager can retry them in the event of a failure such as this.
AMQ5884
Queued Publish/Subscribe control queue is not a local queue.
Severity
10 : Warning
Explanation
The queue manager 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. The Queued Pub/Sub Daemon 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 Queued Publish/Subscribe Daemon will automatically create one of the correct type when started.
IBM MQ Publish/Subscribe broker is being migrated.
Severity
10 : Warning
Explanation
The command cannot be issued at this time because the IBM MQ Publish/Subscribe broker at queue manager <insert_3> is being migrated.
Response
Once the broker has ended if migration did not complete then it can be reattempted using the strmqbrk command again. Otherwise, if migration was completed successfully, the broker will be started automatically.
AMQ5887
Migration started for stream <insert_3>
Severity
0 : Informational
Explanation
Migration of stream <insert_3> has started.
Response
None.
AMQ5888
Migration complete for stream <insert_3>
Severity
0 : Informational
Explanation
All of the state of stream <insert_3> has migrated into the queue manager
Response
None.
AMQ5889
IBM MQ Publish/Subscribe broker has been successfully migrated.
Severity
0 : Informational
Explanation
Migration of the broker has completed successfully.
Response
The broker has been migrated. Resources used by it can now be freed by using the dltmqbrk command.
AMQ5892
Migration of stream <insert_3> has failed for reason <insert_1>:<insert_4>.
Severity
0 : Informational
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 strmqbrk command to retry migration.
AMQ5893
IBM 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 IBM MQ Publish/Subscribe broker (<insert_3>) but the request has failed for reason <insert_1>:<insert_5>.
Response
Determine why the strmqbrk 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 strmqbrk command.
AMQ5893 (IBM i)
IBM 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 strmqbrk 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 strmqbrk command.
AMQ5894
IBM MQ Publish/Subscribe broker migrated with inconsistent hierarchy state.
Severity
10 : Warning
Explanation
The state of stream <insert_3> is not consistent with respect to related broker <insert_4>. While an IBM 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 stream in question may have recently been created or deleted at related broker <insert_4> and this broker did not complete its processing for this change before the upgrade to a new level of MQ. 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 between 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
The state of hierarchy relations may be inconsistent now that migration is complete. Relations can be established using the 'alter qmgr parent' MQSC command. If the hierarchy relationship is not require it can be reset with the 'reset qmgr type pubsub' MQSC command.
AMQ5895
The queued pub/sub interface detected missing retained messages.
Severity
10 : Warning
Explanation
The queued pub/sub interface uses retained messages to communicate with other members of pub/sub hierarchies. The retained message was missing and has been republished.
Response
Retained messages seem to have been removed from the SYSTEM.RETAINED.PUB.QUEUE. The queued pub/sub interface has attempted to recover by republishing retained messages. If you are unaware of a reason why retained messages have been removed this may be a symptom of a more serious problem that requires further investigation.
AMQ5896
Unknown attribute for IBM 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>.
AMQ5897
Subscription (subname <insert_5>, traditional identity <insert_4>, topicstring <insert_3>) not migrated, reason code <insert_2>
Severity
10 : Warning
Explanation
The migration of a subscription has failed and will be skipped (The migration failed with reason code <insert_2>). The subscription has topic string is <insert_3>, traditional identity <insert_4> and subcription name <insert_5>.
Response
Either manually migrate this subscription or investigate and fix the problem and perform the migration again.
AMQ5898
Changing parent queue manager cannot be performed during migration.
Severity
20 : Error
Explanation
A different queue manager was supplied with the '-p' parameter to the current parent manager.
Response
Reissue the migration command without the -p option. Once the migration has been performed, use MQSC to alter the queue manager's parent queue manager.
AMQ5899
Unable to establish parent relationship to a child queue manager
Severity
20 : Error
Explanation
This queue manager is unable to establish requested parent relationship to queue manager (<insert_3>) as that queue manager is already a child of this queue manager.
Response
The existing child relationship to queue manager (<insert_3>) remains unaffected. The erroneous parent definition on this queue manager should be corrected by issuing the "ALTER QMGR PARENT(' ')" MQSC command. Review the parent definitions on this queue manager and the child queue manager (<insert_3>) and modify as appropriate using the "ALTER QMGR PARENT" MQSC command.
AMQ5928
Migrating subscription (subname <insert_5>, traditional identity <insert_4>, topicstring <insert_3>) failed when replacing an existing subscription with reason <insert_2>
Severity
20 : Error
Explanation
Because the migration command was run with the force flag (-f) it has tried to replace an existing subscription. Replacing the existing subscription failed with reason <insert_2>. The subscription has topic string is <insert_3>, traditional identity <insert_4> and subcription name <insert_5>.
Response
Use the migration log to investigate and fix the problem and perform the migration again.
AMQ5929
Migration of a subscription was skipped as a existing subscription exists with the same subname. (The subscription that was not migrated had: subname <insert_5>, traditional identity <insert_4> and topicstring <insert_3>.
Severity
10 : Warning
Explanation
The migration command was run without the force flag (-f). Therefore existing subscriptions are not overwritten. Two subscriptions cannot have the same subname so migration of the subscription was skipped.
Response
If the subscription that has been skipped is still required then either the existing subscription with the same name can be removed and the migration command then re-run, or the migration command can be re-run with the force option (-f) which will cause any existing subscriptions with the same subname to be migrated.
AMQ5930
Migration of stream <insert_3> encountered non-fatal errors, reason <insert_1>:<insert_4>.
Severity
0 : Informational
Explanation
During migration of stream <insert_3>, an error occurred but the migration of the stream continued
Response
Use earlier error messages (and/or the migration log) to investigate the reason for the failure. Once the problem has been resolved, re-issue the migmqbrk command to retry migration.
AMQ5931
Failed to create topic object for stream <insert_3> reason <insert_1>
Severity
20 : Error
Explanation
During migration a topic object is created for each stream. Creation of the topic object that corresponds to stream <insert_3> failed for reason <insert_1>.
Response
Use the migration log to investigate and fix the problem and perform the migration again.
AMQ5932
Migration of security for stream <insert_3> failed with reason <insert_1>
Severity
20 : Error
Explanation
During migration, security access for the stream is migrated to the corresponding topic object. Migrating the security for stream <insert_3> failed for reason <insert_1>.
Response
Use the migration log to investigate and fix the problem and perform the migration again.
AMQ5933
Could not open migration log: <insert_3>
Severity
20 : Error
Explanation
A log of actions performed during publish/subscribe migration is kept. (Its location can be set using the "-l" command line parameter - currently it is set to <insert_3> ). The log could not be opened for writing.
Response
Ensure that the file <insert_3> can be written to and then rerun the migration. Alternatively rerun the migration specifying a different log file location with the "-l" parameter.
AMQ5934
Could not write to migration log: <insert_3>
Severity
20 : Error
Explanation
A log of actions performed during publish/subscribe migration is kept. (Its location can be set using the "-l" command line parameter - currently is is set to <insert_3> ). The log could not be written to.
Response
Ensure that the file <insert_3> can be wriiten to and then rerun the migration. Alternatively rerun the migration specifying a different log file location with the "-l" parameter.
AMQ5940
Failed to migrate relations
Severity
20 : Error
Explanation
During migration of the hierarchy relations an error was encountered. Please see the migration log for more details.
Response
Look at the migration log for details of the error, correct the problem and re-run the migration command.
AMQ5943
Migration cannot be performed as the Queued Publish/Subscribe Daemon is currently active
Severity
10 : Warning
Explanation
The runmqbrk (and strmqbrk) commands migrate publish/subscribe data (e.g. subscriptions and retained messages) from earlier versions of IBM MQ. The migration can only be performed when the Queued Publish/Subscribe Daemon is inactive.
Response
If migration is required, the Queued Publish/Subscribe Daemon should first be disabled, which can be acheived using the following MQSC: alter qmgr psmode(compat)
AMQ5944
Migration has completed with errors. The Queued Publish/Subscribe Daemon will need to be started manually
Severity
10 : Warning
Explanation
The migration command has completed but not all data could be migrated. Details of the error(s) can be found in earlier error messages and the migration log.
Response
Examine earlier error messages and review the migration log, then manually perform migration of any remaining data that is still required (or if the problem was transitory by re-running the migration command). Once migration has been completed, the Queued Publish/Subscribe Daemon can be started by issuing the following MQSC command: alter qmgr psmode(enabled)
AMQ5945
The retained message for topic-string <insert_3> on stream <insert_4> could not be migrated for reason code <insert_2>
Severity
10 : Warning
Explanation
The migration of a retained message has failed and will be skipped (The migration failed with reason code <insert_2>). The retained mesage has topic string <insert_3>, on stream <insert_4>.
Response
Either manually republish the message for this topic or investigate and fix the problem and perform the migration again.
AMQ5946
The Queued Publish/Subscribe Daemon could not be started for reason <insert_1>
Severity
20 : Error
Explanation
After the migration, the starting of the Queued Publish/Subscribe Daemon could not be performed.
Response
Determine (from the reason) why the Queued Publish/Subscribe Daemon could not be started, correct the problem and then manually issue the following MQSC command: ALTER QMGR PSMODE(ENABLED)
AMQ5960
Distributed pub/sub command processor stopping because of errors.
Severity
20 : Error
Explanation
A severe error, as reported in the preceding messages, occurred during distributed pub/sub command processing. The pub/sub command processor was unable to continue and terminates.
Response
Correct the problem reported in the preceding messages.
AMQ5961
Distributed pub/sub publication processor stopping because of errors.
Severity
20 : Error
Explanation
A severe error, as reported in the preceding messages, occurred during distributed pub/sub publication processing. The pub/sub publication processor was unable to continue and terminates.
Response
Correct the problem reported in the preceding messages.
AMQ5962
Distributed pub/sub proxy-subscription fan out process is stopping because of errors.
Severity
20 : Error
Explanation
A severe error, as reported in the preceding messages, occurred during distributed pub/sub proxy-subscription fan out. The pub/sub proxy-subscription fan out process was unable to continue and terminates.
Response
Correct the problem reported in the preceding messages.
AMQ5963
The queued pub/sub interface is unavailable.
Severity
20 : Error
Explanation
The Distributed pub/sub process was unable to contact the queued pub/sub interface. If there is a problem with the interface, this should be highlighted in preceding messages. Hierarchical connections will not be further processed until the problem is rectified.
Response
Correct the problem reported in the preceding messages. When the interface becomes available, it may be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resync subscriptions.
AMQ5964
Pub/sub hierarchy connected.
Severity
0 : Informational
Explanation
A pub/sub hierarchy connection has been established with child or parent queue manager <insert_3>.
Response
None.
AMQ5965
Pub/sub hierarchy disconnected.
Severity
0 : Informational
Explanation
A pub/sub hierarchy connection has ended with child or parent queue manager <insert_3>.
Response
None.
AMQ5966
A previous publication is being incorrectly processed again.
Severity
20 : Error
Explanation
A publication, previously processed by this queue manager, has been received. This message will not be re-published and will be processed according to to the message's report options. Additional messages may be written if this publication is sent to the dead-letter queue. This is caused by an invalid configuration of a hierarchy and a pub/sub cluster.
Response
Correct the configuration to remove the loop. Check the message properties in the dead-letter queue to determine the route taken.
AMQ5967
Unable to deliver proxy subscription to queue manager <insert_3>. Reason code: <insert_1>.
Severity
20 : Error
Explanation
Unable to deliver proxy subscription to queue manager <insert_3>. Reason code: <insert_1>. This may result in subscriptions not receiving publications from <insert_3>.
Response
Correct the configuration to allow proxy subscriptions to be delivered to <insert_3>. When the problem has been resolved, it will be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscriptions.
AMQ5968
Inconsistent use of clustered topics and PROXYSUB FORCE attribute detected
Severity
10 : Warning
Explanation
Topic object <insert_3> is defined in cluster <insert_4>, and is below topic object <insert_5> in the topic tree. Topic object <insert_5> has set PROXYSUB to be FORCE, so no further individual proxy subscriptions are sent for any subscriptions made below <insert_5> in the topic tree. However, <insert_5> is not in the same cluster as <insert_3>, and the wildcard proxy subscription is not sent to neighboring queue managers in the cluster in which <insert_3> is defined. Therefore, publications from cluster <insert_4> might not be sent to subscriptions to <insert_3> on this queue manager.
Response
If this is the intended behavior then this warning can be ignored. If it is not, then either topic <insert_3> should also set PROXYSUB to be FORCE to generate a wildcard proxy subscription at this topic level, or topic <insert_5> should remove the FORCE setting.
AMQ5971
<insert_3>(<insert_1>) has failed to quiesce in a timely manner.
Severity
10 : Warning
Explanation
This message is issued when a task was requested to quiesce, but has failed to do so in a timely manner.
Response
One or more related FDC's may be generated capturing the reason for this. Also check the log for related messages prior and post this message appearing which may explain the reason for this.
AMQ5972
Distributed Pub/Sub fanout request put failed.
Severity
20 : Error
Explanation
Unable to place subscription fanout request to the Distributed publish/subscribe fanout request queue <insert_3>. The associated reason code is <insert_1>.
Response
Correct the problem reported in the preceding messages. When the problem has been resolved, it may be neccessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resync subscriptions.
A topic has been disabled for subscribe. This prevents distributed publish/subscribe from creating a subscription on behalf of another queue manager within the topology. The remote queue manager name is <insert_3>. The associated topic string is <insert_4>.
Response
Correct the topic definition on this queue manager to permit the creation of subscriptions. Alternatively, contact the administrator of the sending queue manager to correct the topic configuration to prevent subscription requests being sent to this queue manager. When the problem has been resolved, it will be neccessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resync subscriptions.
AMQ5974
Distributed Pub/Sub publication inhibited.
Severity
20 : Error
Explanation
A topic has been disabled for publish. This prevents distributed publish/subscribe from publishing a message received from another queue manager within the topology. This message will not be re-published and will be processed according to the message's report options. Additional messages may be written if this publication is sent to the dead-letter queue. The associated topic string is <insert_3>.
Response
Correct the topic configuration to permit publications. Alternatively, contact the administrator of the sending queue manager to correct the topic configuration to prevent publication being delivered to this queue manager.
Establishing a publish/subscribe hierarchy relationship with child or parent queue manager <insert_3>. An exchange of information is required with the other queue manager. Once the exchange is complete informational message AMQ5964 will be written. This exchange requires active channels to and from the other queue manager.
Response
If the relationship is not correctly established check for the correct configuration and state of the channels to and from the other queue manager.
AMQ5978
Unable to create/cancel proxy subscription, rc= <insert_1>
Severity
20 : Error
Explanation
The <insert_5> is unable to create or cancel a proxy subscription for <insert_3> on topic <insert_4> for reason code <insert_1>. A failure to create or cancel a proxy subscription will result in this queue manager not having a correct knowledge of subscriptions on other queue managers in the pubsub topology. This may result in this queue manager not delivering publications to other queue managers.
Response
Correct the cause of the indicated reason code. Once the problem has been resolved it may be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resync subscriptions.
AMQ5979
Proxy Subscription from <insert_3> rejected because PSCLUS(DISABLED)
Severity
10 : Warning
Explanation
Queue manager attribute PSCLUS has been set to DISABLED to indicate that Publish/Subscribe activity is not expected between queue managers in this cluster. However, a cluster subscription has been sent to this queue manager over a channel from <insert_3>. The proxy subscription request will be ignored and no subscription locally registered.
Response
If you wish to enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED. You may also need to issue REFRESH CLUSTER and REFRESH QMGR commands as detailed in the PSCLUS documentation. If you are not using publish/subscribe clusters you should delete the clustered topic object, and ensure PSCLUS is DISABLED on all queue managers.
AMQ5980
Distributed Pub/Sub proxy subscription re-synchronization occurred at startup.
Severity
0 : Informational
Explanation
The Distributed publish/subscribe process was unable to determine that the proxy subscription state was consistent across shutdown and restart so a re-synchronization with remote queue managers has been performed. This is usually seen when a queue manager was not quiesced cleanly on the previous shutdown or when the system was particularly busy.
Response
None.
AMQ5981
Disabling Publish/Subscribe when participating in a Publish/Subscribe Cluster
Severity
10 : Warning
Explanation
This queue manager is a member of a Publish/Subscribe Cluster but Publish/Subscribe has been disabled. Other queue managers within the cluster will continue to send publications and proxy subscriptions to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queues and will not be processed until Publish/Subscribe is enabled. If these queues become full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
Response
Enable Publish/Subscribe by setting PSMODE to ENABLED or COMPAT with the ALTER QMGR command then the REFRESH QMGR TYPE(PROXYSUB) command should be issued to resynchronise subscriptions.
AMQ5982
Disabling Queued Publish/Subscribe while participating in a Publish/Subscribe Hierarchy
Severity
10 : Warning
Explanation
This queue manager is a member of a Publish/Subscribe hierarchy but Queued Publish/Subscribe has been disabled. Any parent-child relations within the Publish/Subscribe hierarchy will continue to send publications and proxy subscriptions to this queue manager. They will accumulate on the Queued Publish/Subscribe system queues and will not be processed until Queued Publish/Subscribe is enabled. If the Queued Publish/Subscribe system queues become full channel failure may occur, which will affect the operation of Publish/Subscribe on parent-child relations sending messages to this queue manager. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are to be delivered using the same channels.
Response
Enable Queued Publish/Subscribe by setting PSMODE to ENABLED with the ALTER QMGR command. Once Queued Publish/Subscribe has been restarted, use the DISPLAY PUBSUB ALL command to confirm this has completed, the REFRESH QMGR TYPE(PROXYSUB) command must be issued to resynchronise subscriptions.
AMQ5983
<insert_3> failed due to reason <insert_2>:<insert_4>. Retry in <insert_1> minutes
Severity
10 : Warning
Explanation
<insert_3> encountered a problem. Earlier messages may have been issued in the queue manager or system error logs providing additional detail. The task will retry the command in <insert_1> minutes. Other queue managers within the cluster will continue to send publications to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.PUBS) and will not be processed until the problem is resolved. If the queue becomes full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5984
<insert_3> has encountered <insert_2> occurrences of reason <insert_1>:<insert_4> while attempting to process a message.
Severity
10 : Warning
Explanation
<insert_3> is currently unable to process a message due to reason <insert_1>:<insert_4>. The task has encountered this <insert_2> times. The task will continue to retry the command until the problem has been rectified. Other queue managers within the cluster will continue to send publications to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.PUBS) and will not be processed until the problem is resolved. If the queue becomes full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5987
<insert_3> failed due to reason <insert_2>:<insert_4>. Retry in <insert_1> minutes
Severity
10 : Warning
Explanation
<insert_3> encountered a problem. Earlier messages may have been issued in the queue manager or system error logs providing additional detail. The task will retry the command in <insert_1> minutes. Other queue managers within the cluster will continue to send proxy subscriptions to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.CONTROL) and will not be processed until the problem is resolved. Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed. If the Publish/subscriber Cluster system queue becomes full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5988
<insert_3> failed due to reason <insert_2>:<insert_4>. Retry in <insert_1> minutes
Severity
10 : Warning
Explanation
<insert_3> encountered a problem. Earlier messages may have been issued in the queue manager or system error logs providing additional detail. The task will retry the command in <insert_1> minutes. This task will not send proxy subscription messages to other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified. On topics for which proxy subscriptions have yet to be sent this queue manager will not receive publications from other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5989
<insert_3> has encountered <insert_2> occurrences of reason <insert_1>:<insert_4> while attempting to process a message.
Severity
10 : Warning
Explanation
<insert_3> is currently unable to process a message due to reason <insert_1>:<insert_4>. The task has encountered this <insert_2> times. The task will continue to retry the command until the problem has been rectified. Other queue managers within the cluster will continue to send proxy subscriptions to this queue manager. They will accumulate on the Publish/Subscribe Cluster system queue (SYSTEM.INTER.QMGR.CONTROL) and will not be processed until the problem is resolved. Other queue managers will not receive publications from this queue manager on topics for which proxy subscriptions have yet to be processed. If the Publish/subscriber Cluster system queue becomes full channel failure may occur, which will affect the operation of Publish/Subscribe on other queue managers in the cluster. This will also affect the delivery of other messages, unrelated to Publish/Subscribe, that are sent to this queue manager from other queue managers within the cluster.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5990
<insert_3> has encountered <insert_2> occurrences of reason <insert_1>:<insert_4> while attempting to process a message.
Severity
10 : Warning
Explanation
<insert_3> is currently unable to process a message due to reason <insert_1>:<insert_4>. The task has encountered this <insert_2> times. The task will continue to retry the command until the problem has been rectified. This task will not send proxy subscription messages to other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy until the problem is rectified. On topics for which proxy subscriptions have yet to be sent this queue manager will not receive publications from other queue managers in a Publish/Subscribe Cluster or parent-child relations within a Publish/Subscribe hierarchy.
Response
If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified wait for <insert_3> to retry the command.
AMQ5991
<insert_3> has recovered from previous error condition.
Severity
0 : Informational
Explanation
<insert_3> has recovered from previously reported error condition.
AMQ5992
<insert_4> has written a message to the dead-letter queue.
Severity
10 : Warning
Explanation
<insert_4> has written a message to the dead-letter queue (<insert_3>) for reason <insert_1>:<insert_5>.
Response
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.
AMQ5993
<insert_4> has written a message to the dead-letter queue.
Severity
10 : Warning
Explanation
<insert_4> has written a message to the dead-letter queue (<insert_3>) for reason <insert_1>:<insert_5>. Other queue managers will not receive publications from this queue manager on any topics for which this message is requesting proxy subscriptions be created.
Response
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. Once the problem has been resolved it may be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscription state with other queue managers.
AMQ5994
<insert_4> has written a message to the dead-letter queue.
Severity
10 : Warning
Explanation
<insert_4> has written a message to the dead-letter queue (<insert_3>) for reason <insert_1>:<insert_5>. This queue manager will not receive publications from other queue managers on any topics for which this is requesting proxy subscription be created.
Response
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. Once the problem has been resolved it may be necessary to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscription state with other queue managers.
AMQ5995
<insert_5> cannot write a message to the dead-letter queue.
Severity
10 : Warning
Explanation
<insert_5> 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>.
Response
Determine why the message cannot be written to the dead-letter queue. Also, determine why the message was being written to the dead-letter queue and resolve the problem that is preventing the message from being sent to its destination.
AMQ5996
Creation of proxy subscription failed on remote queue manager <insert_3> due to <insert_1>
Severity
10 : Warning
Explanation
The proxy subscription in publish/subscriber cluster <insert_4> on topic <insert_5> has failed to be created on remote queue manager <insert_3> with reason <insert_1>. The failure to create the proxy subscription will prevent publications made on queue manager <insert_3> to topic <insert_5> being delivered to subscriptions on this queue manager. If this queue manager is also participating as a member of a publish/subscribe hierarchy any subscriptions to topic <insert_5> on other members of the publish/subscribe hierarchy will not receive publications from queue manager <insert_3>.
Response
Correct the cause of the indicated reason code on the remote queue manager. Once the problem has been resolved it will be necessary on the remote queue manager to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscription state with other queue managers.
AMQ5997
Cancelling of proxy subscription failed on remote queue manager <insert_3> due to <insert_1>
Severity
10 : Warning
Explanation
The proxy subscription in publish/subscriber cluster <insert_4> on topic <insert_5> has failed to be cancelled on remote queue manager <insert_3> with reason <insert_1>. The failure to cancel the proxy subscription will result in publications made on queue manager <insert_3> to topic <insert_5> to continue being delivered to this queue manager.
Response
Correct the cause of the indicated reason code on the remote queue manager. Once the problem has been resolved it will be necessary on the remote queue manager to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscription state with other queue managers.
AMQ5998
Proxy subscription resync failed on remote queue manager <insert_3> due to <insert_1>
Severity
10 : Warning
Explanation
The request to resynchronise subscription state with other queue managers in publish/subscriber cluster <insert_4> has failed on remote queue manager <insert_3> with reason <insert_1>. There may be topic strings on which proxy subscriptions failed to be created. Publications made on queue manager <insert_3> to those topics will not be delivered to subscription on this queue manager. If this queue manager is also participating as a member of a publish/subscribe hierarchy any subscriptions to those topics on other members of the publish/subscribe hierarchy will not receive publications from queue manager <insert_3>. There may be topic strings on which proxy subscriptions have not been cancelled on queue manager <insert_3> any publications made on that queue manager will continue to be delivered to this queue manager.
Response
Correct the cause of the indicated reason code on the remote queue manager. Once the problem has been resolved it will be necessary on the remote queue manager to perform a REFRESH QMGR TYPE(PROXYSUB) to resynchronise subscription state with other queue managers.
AMQ5999
<insert_3> has encountered an invalid message on <insert_4> queue .
Severity
20 : Error
Explanation
<insert_4> is an internal queue for exclusive use of <insert_3> to maintain a Distributed Publish/Subscribe topology. The message will be processed according to the message's report options. Additional messages may be written if this message is sent to the dead-letter queue. This message may be accompanied by an informational FFST including details of the invalid message.
Response
Ensure no applications put messages directly to the <insert_4> queue. Ensure message exits do not alter system messages placed on the <insert_4> queue. If the problem persists save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.