AMQ8000-8999: Administration

AMQ8001
IBM® WebSphere® MQ queue manager created.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_5> created.
Response
None.
AMQ8002
IBM WebSphere MQ queue manager <insert_5> deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_5> deleted.
Response
None.
AMQ8003
IBM WebSphere MQ queue manager <insert_5> started.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_5> started.
Response
None.
AMQ8004
IBM WebSphere MQ queue manager <insert_5> ended.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_5> ended.
Response
None.
AMQ8005
IBM WebSphere MQ queue manager changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_3> changed.
Response
None.
AMQ8006
IBM WebSphere MQ queue created.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue <insert_3> created.
Response
None.
AMQ8007
IBM WebSphere MQ queue deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue <insert_3> deleted.
Response
None.
AMQ8008
IBM WebSphere MQ queue changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue <insert_3> changed.
Response
None.
AMQ8010
IBM WebSphere MQ process created.
Severity
0 : Information
Explanation
IBM WebSphere MQ process <insert_3> created.
Response
None.
AMQ8011
IBM WebSphere MQ process deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ process <insert_3> deleted.
Response
None.
AMQ8012
IBM WebSphere MQ process changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ process <insert_3> changed.
Response
None.
AMQ8014
IBM WebSphere MQ channel created.
Severity
0 : Information
Explanation
IBM WebSphere MQ channel <insert_3> created.
Response
None.
AMQ8015
IBM WebSphere MQ channel deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ channel <insert_3> deleted.
Response
None.
AMQ8016
IBM WebSphere MQ channel changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ channel <insert_3> changed.
Response
None.
AMQ8018
Start IBM WebSphere MQ channel accepted.
Severity
0 : Information
Explanation
The channel <insert_3> is being started. The start channel function has been initiated. This involves a series of operations across the network before the channel is actually started. The channel status displays "BINDING" for a short period while communication protocols are negotiated with the channel with which communication is being initiated.
Response
None.
AMQ8019
Stop IBM WebSphere MQ channel accepted.
Severity
0 : Information
Explanation
The channel <insert_3> has been requested to stop.
Response
None.
AMQ8020
Ping IBM WebSphere MQ channel complete.
Severity
0 : Information
Explanation
Ping channel <insert_3> complete.
Response
None.
AMQ8021
Request to start IBM WebSphere MQ Listener accepted.
Severity
0 : Information
Explanation
The Request to start the Listener has been accepted and is being processed.
Response
Should the request to start the listener be unsuccessful then information related to the error will be available in the queue manager error log. Once started the status of the listener may be monitored using the MQSC command 'DISPLAY LSSTATUS'. On IBM i the status of the listener may also be monitored using the 'WRKMQMLSR OPTION(*STATUS)' command.
AMQ8022
IBM WebSphere MQ queue cleared.
Severity
0 : Information
Explanation
All messages on queue <insert_3> have been deleted.
Response
None.
AMQ8023
IBM WebSphere MQ channel reset.
Severity
0 : Information
Explanation
Channel <insert_3> has been reset, the new sequence number of the channel is <insert_1>.
Response
None.
AMQ8024
IBM WebSphere MQ channel initiator started.
Severity
0 : Information
Explanation
The channel initiator for queue <insert_3> has been started.
Response
None.
AMQ8025
IBM WebSphere MQ channel resolved.
Severity
0 : Information
Explanation
In doubt messages for IBM WebSphere MQ channel <insert_3> have been resolved.
Response
None.
AMQ8026
End IBM WebSphere MQ queue manager accepted.
Severity
0 : Information
Explanation
A controlled stop request has been initiated for queue manager <insert_5>.
Response
None.
AMQ8027
IBM WebSphere MQ command server started.
Severity
0 : Information
Explanation
The command server has been started.
Response
None.
AMQ8028
IBM WebSphere MQ command server ended.
Severity
0 : Information
Explanation
The command server has been stopped.
Response
None.
AMQ8029
IBM WebSphere MQ authority granted.
Severity
0 : Information
Explanation
Authority for object <insert_5> granted.
Response
None.
AMQ8030
IBM WebSphere MQ authority revoked.
Severity
0 : Information
Explanation
Authority for object <insert_3> revoked.
Response
None.
AMQ8031 (IBM i)
Message Queue Manager connected.
Severity
0 : Information
Explanation
The message queue manager has been connected.
Response
None.
AMQ8032 (IBM i)
Message Queue Manager disconnected.
Severity
0 : Information
Explanation
The message queue manager has been disconnected.
Response
None.
AMQ8033
IBM WebSphere MQ object recreated.
Severity
0 : Information
Explanation
MQ object <insert_5> has been re-created from image.
Response
None.
AMQ8034
IBM WebSphere MQ object image recorded.
Severity
0 : Information
Explanation
Image of MQ object <insert_3> has been recorded.
Response
None.
AMQ8035
IBM WebSphere MQ Command Server Status . . : Running
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8036
IBM WebSphere MQ command server status . . : Stopping
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8037
IBM WebSphere MQ command server status . . : Starting
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8038
IBM WebSphere MQ command server status . . : Running with queue disabled
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8039
IBM WebSphere MQ command server status . . : Stopped
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8040
IBM WebSphere MQ command server ending.
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8041
The queue manager cannot be restarted or deleted because processes, that were previously connected, are still running.
Severity
40 : Stop Error
Explanation
Processes, that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted.
Response
Stop the processes and try to start the queue manager.
AMQ8041 (IBM i)
The queue manager cannot be restarted or deleted.
Severity
40 : Stop Error
Explanation
Jobs that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted or deleted.
Response
Use option 22 from WRKMQM to identify which jobs are connected to the queue manager. End the connected jobs and then retry the command.
AMQ8042
Process <insert_1> is still running.
Severity
0 : Information
AMQ8043
Non runtime application attempted to connect to runtime only queue manager.
Severity
0 : Information
Explanation
A non runtime application attempted to connect to a queue manager on a node where support for non runtime applications has not been installed. The connect attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR.
Response
If the node is intended to support only runtime applications, investigate why a non runtime application has attempted to connect to the queue manager. If the node is intended to support non runtime only applications, investigate if the base option has been installed. The base option must be installed if non runtime applications are to run on this node.
AMQ8044 (Windows)
An error occurred while removing the queue manager from the Active Directory.
Severity
0 : Information
Explanation
The attempt to remove the queue manager from the Windows Active Directory failed. This may be because the appropriate entry could not be opened or modified, or the Service Control Point has already been removed.
Response
Check that your account has the authority to delete objects from the Active Directory, and that the entry has not already been deleted.
AMQ8045
WebSphere MQ channel in use.
Severity
20 : Error
Explanation
A process is either trying to delete a running telemetry channel, or to define a new telemetry channel using a port that is already in use. If the process is trying to define a new telemetry channel, the channel is defined but not started.
Response
Stop the process that is using the port, then either delete the previously-running channel, or start the newly-defined channel.
AMQ8046
Migrating objects for <insert_3>.
Severity
0 : Information
Response
None.
AMQ8047
Channel migration statistics : <insert_1> migrated. <insert_2> failed.
Severity
0 : Information
Explanation
Information on the number of channel objects migrated from previous versions of IBM WebSphere MQ channel definitions as well as any failures that occurred.
Response
None.
AMQ8048
Default objects statistics : <insert_1> created. <insert_2> replaced. <insert_3> failed.
Severity
0 : Information
Explanation
Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects.
Response
None.
AMQ8049
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to improper authorization. The reason code is <insert_1>.
Response
Check this log for more details of what the problem may be. Make sure there are sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8050
Creating or replacing default objects for <insert_3>.
Severity
0 : Information
Response
None.
AMQ8051
For details of the failures that occurred, please check AMQERR01.LOG.
Severity
0 : Information
Response
None.
AMQ8051 (Tandem)
For details of the failures that occurred, please check MQERRLG1.
Severity
0 : Information
Response
None.
AMQ8052
Completing setup.
Severity
0 : Information
Response
None.
AMQ8053
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a broken connection. The reason code is <insert_1>.
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8054
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to unavailable storage. The reason code is <insert_1>.
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8055
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a damaged object. The reason code is <insert_1>.
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8056
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a channel definition error. The error code is <insert_1> (X<insert_2>).
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8057
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to invalid records in the channel definition file. The error code is <insert_1> (X<insert_2>).
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8058
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to not finding the channel definition file. The error code is <insert_1> (X<insert_2>).
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8059
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM WebSphere MQ queue manager <insert_5> an error occurred. The error was due to an unexpected error, error code <insert_1> (X<insert_2>).
Response
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
AMQ8060
IBM WebSphere MQ queue manager <insert_5> started as a standby.
Severity
0 : Information
Explanation
Queue manager <insert_5> started as a standby instance, ready to become the primary instance if the existing primary instance fails.
Response
None.
AMQ8061 (Windows)
Command <insert_4> is not valid.
Severity
10 : Warning
Explanation
The command <insert_4> at line <insert_1> in the IBM WebSphere MQ service command file <insert_3> for queue manager <insert_5> is not valid for use in the service command file. The line is ignored.
Response
Check the contents of the file and retry the operation.
AMQ8062 (Windows)
Unexpected return code, <insert_1>, from command <insert_3>.
Severity
10 : Warning
Explanation
An unexpected return code, <insert_1>, was returned by command <insert_3>. This command was issued by the IBM WebSphere MQ service for queue manager <insert_4>.
Response
Verify that the command and parameters are correct.
AMQ8063 (Windows)
Not authorized to issue command <insert_3>.
Severity
20 : Error
Explanation
The current user <insert_5> is not authorized to issue the command <insert_3>. This can occur if the user is a member of the Administrators group but is not currently elevated. The command is ignored.
Response
Add the user to the local 'mqm' security group and retry the operation.
AMQ8064 (Windows)
Not authorized to start trusted application.
Severity
20 : Error
Explanation
The user <insert_5> is not authorized to start the trusted application <insert_3>. The application has not started.
Response
Add the user to the local 'mqm' security group and restart the application.
AMQ8065 (Windows)
Local group <insert_3> not found.
Severity
20 : Error
Explanation
The local group <insert_3> is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
Response
Create the required local group and retry the operation.
AMQ8066 (Windows)
Local mqm group not found.
Severity
20 : Error
Explanation
The local mqm group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
Response
Create the local mqm group and retry the operation.
AMQ8067
IBM WebSphere MQ channel auto-defined.
Severity
0 : Information
Explanation
Channel <insert_5> auto-defined.
Response
None.
AMQ8068
Setup completed.
Severity
0 : Information
Response
None.
AMQ8069
ApplicationGroup for the crtmqm command does not contain the mqm userid.
Severity
40 : Stop Error
Explanation
IBM WebSphere MQ queue manager <insert_5> not created. The ApplicationGroup specified for the crtmqm command must contain the mqm userid when the RestrictedMode option (-g) is specified.
Response
None.
AMQ8070
ApplicationGroup for crtmqm command is not defined.
Severity
40 : Stop Error
Explanation
IBM WebSphere MQ queue manager <insert_5> not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist.
Response
None.
AMQ8071
RestrictedMode option not supported on this platform.
Severity
40 : Stop Error
Explanation
IBM WebSphere MQ queue manager <insert_5> not created. The RestrictedMode option was specified but is not supported on this platform.
Response
None.
AMQ8072 (Windows)
Not authorized to administer channels.
Severity
10 : Warning
Explanation
The command server for queue manager <insert_3> received an administration command for channels. The user <insert_5> is not authorized to administer IBM WebSphere MQ channels. The command server has not processed the command.
Response
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
AMQ8073 (Windows)
Authorization failed because SID: (<insert_3>) could not be resolved.
Severity
10 : Warning
Explanation
The object authority manager was unable to resolve the specified SID into entity and domain information.
Response
Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required.
AMQ8074 (Windows)
Authorization failed as the SID <insert_3> does not match the entity <insert_4>.
Severity
10 : Warning
Explanation
The object authority manager received inconsistent data - the supplied SID does not match that of the supplied entity information.
Response
Ensure that the application is supplying valid entity and SID information.
AMQ8075 (Windows)
Authorization failed because the SID for entity <insert_3> cannot be obtained.
Severity
10 : Warning
Explanation
The object authority manager was unable to obtain a SID for the specified entity.
Response
Ensure that the entity is valid, and that all necessary domain controllers are available.
AMQ8076 (Windows)
Authorization failed because no SID was supplied for entity <insert_3>.
Severity
10 : Warning
Explanation
The object authority manager was not supplied with SID information for the specified entity, and the security policy is set to 'NTSIDsRequired'.
Response
Ensure that the application is supplying a valid SID, and that the security policy is set as you require.
AMQ8077
Entity <insert_3> has insufficient authority to access object <insert_4>.
Severity
10 : Warning
Explanation
The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: <insert_5>
Response
Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group.
AMQ8078
Waiting for queue manager <insert_3> to end.
Severity
0 : Information
Response
None.
AMQ8079 (Windows)
Access was denied when attempting to retrieve group membership information for user <insert_3>.
Severity
10 : Warning
Explanation
IBM WebSphere MQ, running with the authority of user <insert_4>, was unable to retrieve group membership information for the specified user.
Response
Ensure Active Directory access permissions allow user <insert_4> to read group memberships for user <insert_3>. To retrieve group membership information for a domain user, MQ must run with the authority of a domain user and a domain controller must be available.
AMQ8079 (IBM i)
IBM WebSphere MQ trigger monitor job started.
Severity
0 : Information
Explanation
The message queue manager trigger monitor job has been started for queue manager <insert_3> to process messages on the selected initiation queue. See previously issued messages for job details.'
Response
None.
AMQ8080 (IBM i)
IBM WebSphere MQ trigger monitor job start failed.
Severity
40 : Stop Error
Explanation
Message queue manager trigger job failed to start for manager <insert_3>. Failure reason code is <insert_2>. See previously issued messages for more information.'
Response
None.
AMQ8081 (Windows)
Not authorized to administer queue managers.
Severity
10 : Warning
Explanation
The command server for queue manager <insert_3> received an administration command for a queue manager. The user <insert_5> is not authorized to administer IBM WebSphere MQ queue managers. The command server has not processed the command.
Response
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
AMQ8082 (Windows)
Not authorized to administer clusters.
Severity
10 : Warning
Explanation
The command server for queue manager <insert_3> received an administration command for clusters. The user <insert_5> is not authorized to administer IBM WebSphere MQ clusters. The command server has not processed the command.
Response
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
AMQ8083
IBM WebSphere MQ queue manager <insert_3> starting.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_3> starting.
Response
None.
AMQ8084
IBM WebSphere MQ connection not found.
Severity
0 : Information
Explanation
The connection specified does not exist.
Response
Correct the connection name and then try the command again.
AMQ8085
IBM WebSphere MQ queue manager <insert_3> is being started for replay.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_3> is being started for replay. The strmqm command has been issued with the '-r' option. see the IBM WebSphere MQ System Administration documentation for details.
Response
None.
AMQ8086
IBM WebSphere MQ queue manager <insert_3> is being activated.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_3> is being activated. The strmqm command has been issued with the '-a' option. see the IBM WebSphere MQ System Administration documentation for details.
Response
None.
AMQ8086 (IBM i)
IBM WebSphere MQ queue manager <insert_3> is being activated.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_3> is being activated. The STRMQM command has been issued with the ACTIVATE(*YES) option. see the IBM WebSphere MQ System Administration documentation for further details.
Response
None.
AMQ8087
Attempt to migrate listener <insert_3> to a QM object failed with <insert_1>.
Severity
20 : Error
Explanation
Whilst processing legacy services, listener <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8088
Attempt to migrate trigger monitor <insert_3> to a QM object failed with <insert_1>.
Severity
20 : Error
Explanation
Whilst processing legacy services, trigger monitor <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8089
Attempt to migrate channel service <insert_3> to a QM object failed with <insert_1>.
Severity
20 : Error
Explanation
Whilst processing legacy services, channel service <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8090
Attempt to migrate channel initiator <insert_3> to a QM object failed with <insert_1>.
Severity
20 : Error
Explanation
Whilst processing legacy services, channel initiator <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8091
Attempt to migrate custom service <insert_3> to a QM object failed with <insert_1>.
Severity
20 : Error
Explanation
Whilst processing legacy services, custom service <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8092
Service migration statistics : <insert_1> migrated. <insert_2> failed.
Severity
0 : Information
Explanation
Information on the number of service objects migrated from previous versions of IBM WebSphere MQ for Windows services as well as any failures that occurred.
Response
None.
AMQ8093
IBM WebSphere MQ subscription changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription <insert_3> changed.
Response
None.
AMQ8094
IBM WebSphere MQ subscription created.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription <insert_3> created.
Response
None.
AMQ8095
IBM WebSphere MQ subscription deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription <insert_3> deleted.
Response
None.
AMQ8096
IBM WebSphere MQ subscription inquired.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription <insert_3> inquired.
Response
None.
AMQ8097
Default object <insert_3>. Unable to change attribute <insert_1> to value <insert_2>.
Severity
20 : Error
Explanation
While migrating a queue manager to a newer release an attempt was made to change the value of an attribute of one of the default objects. The attribute of the above named default object could not be changed. While modifying the integer attribute <insert_1> of the default object <insert_3> for IBM WebSphere MQ queue manager <insert_4> an unexpected error occurred.
Response
The most likely cause of this error is that object <insert_3> has been redefined to be an object of a conflicting type for which the attribute <insert_1> is not applicable. For example if a default queue which was originally a local queue is changed to be an alias queue then the queue manager could fail to set the attribute MQIA_MAX_MSG_LENGTH (13) as MAXMSGL is not an attribute supported by alias queues. Review the customer configuration to see if a corresponding change needs to be made to the customer defined replacement for the named default object.
AMQ8098
IBM WebSphere MQ subscription copied.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription <insert_3> copied.
Response
None.
AMQ8099
IBM WebSphere MQ subscription status inquired.
Severity
0 : Information
Explanation
IBM WebSphere MQ subscription status <insert_3> inquired.
Response
None.
AMQ8101
IBM WebSphere MQ error (<insert_1>) has occurred.
Severity
40 : Stop Error
Explanation
An unexpected reason code with hexadecimal value <insert_1> was received from the IBM WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is <insert_4>.
Response
Correct the error and then try the command again.
AMQ8102
IBM WebSphere MQ object name specified in <insert_4> not valid.
Severity
30 : Severe error
Explanation
The object name <insert_3> specified in <insert_4> is not valid. The length of the name must not exceed 48 characters, or 20 characters if it is a channel name. The name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
Response
Change the length of the parameter value or change the parameter value to contain a valid combination of characters, then try the command again.
AMQ8103
Insufficient storage available.
Severity
40 : Stop Error
Explanation
There was insufficient storage available to perform the requested operation.
Response
Free some storage and then try the command again.
AMQ8104
IBM WebSphere MQ directory <insert_3> not found.
Severity
40 : Stop Error
Explanation
Directory <insert_3> was not found. This directory is created when IBM WebSphere MQ is installed successfully. Refer to the log for more information.
Response
Verify that installation of IBM WebSphere MQ was successful. Correct the error and then try the command again.
AMQ8105
Object error.
Severity
40 : Stop Error
Explanation
An object error occurred. Refer to the log for more information.
Response
Correct the error and then try the command again.
AMQ8106
IBM WebSphere MQ queue manager being created.
Severity
0 : Information
Explanation
The queue manager is being created.
Response
Wait for the creation process to complete and then try the command again.
AMQ8107
IBM WebSphere MQ queue manager running.
Severity
10 : Warning
Explanation
The queue manager is running.
Response
None.
AMQ8108
IBM WebSphere MQ queue manager <insert_3> ending.
Severity
10 : Warning
Explanation
The queue manager <insert_3> is ending.
Response
Wait for the queue manager to end and then try the command again.
AMQ8109
IBM WebSphere MQ queue manager being deleted.
Severity
0 : Information
Explanation
The queue manager is being deleted.
Response
Wait for the deletion process to complete.
AMQ8110
IBM WebSphere MQ queue manager already exists.
Severity
40 : Stop Error
Explanation
The queue manager <insert_5> already exists.
Response
None.
AMQ8112 (IBM i)
PRCNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The PRCNAME parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the PRCNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8113 (IBM i)
TRGENBL not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The TRGENBL parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the TRGENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8114 (IBM i)
GETENBL not allowed with queue type *RMT.
Severity
40 : Stop Error
Explanation
The GETENBL parameter may not be specified for a queue of type *RMT.
Response
Remove the GETENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8115 (IBM i)
SHARE not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The SHARE parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the SHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8116 (IBM i)
MSGDLYSEQ not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The MSGDLYSEQ parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the MSGDLYSEQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8117
IBM WebSphere MQ queue manager deletion incomplete.
Severity
40 : Stop Error
Explanation
Deletion of queue manager <insert_5> was only partially successful. An object was not found, or could not be deleted. Refer to the log for more information.
Response
Delete any remaining queue manager objects.
AMQ8118
IBM WebSphere MQ queue manager does not exist.
Severity
40 : Stop Error
Explanation
The queue manager <insert_5> does not exist.
Response
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
AMQ8119
Unsupported threading model detected.
Severity
20 : Error
Explanation
The command executed could not run because the current threading model does not contain the required level of functionality.
Response
On Linux® this may be caused by using a threading model such as LinuxThreads which does not provide process-shared mutex support. On some systems, the setting of the environment variable LD_ASSUME_KERNEL causes LinuxThreads to be used instead of native kernel threads.
AMQ8119 (IBM i)
TRGTYPE not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The TRGTYPE parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the TRGTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8120 (IBM i)
TRGDEPTH not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The TRGDEPTH parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the TRGDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8121 (IBM i)
TRGMSGPTY not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The TRGMSGPTY parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the TRGMSGPTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8122 (IBM i)
TRGDATA not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The TRGDATA parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the TRGDATA parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8123 (IBM i)
RTNITV not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The RTNITV parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the RTNITV parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8124 (IBM i)
MAXMSGLEN not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The MAXMSGLEN parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the MAXMSGLEN parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8125 (IBM i)
BKTTHLD not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The BKTTHLD parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the BKTTHLD parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8126 (IBM i)
BKTQNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The BKTQNAME parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the BKTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8127 (IBM i)
INITQNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The INITQNAME parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the INITQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8128 (IBM i)
USAGE not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The USAGE parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the USAGE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8129 (IBM i)
DFNTYPE only allowed with queue type *MDL.
Severity
40 : Stop Error
Explanation
The DFNTYPE parameter may only be specified for a queue of type *MDL.
Response
Remove the DFNTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8130 (IBM i)
TGTQNAME only allowed with queue type *ALS.
Severity
40 : Stop Error
Explanation
The TGTQNAME parameter may only be specified for a queue of type *ALS.
Response
Remove the TGTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8131 (IBM i)
RMTQNAME only allowed with queue type *RMT.
Severity
40 : Stop Error
Explanation
The RMTQNAME parameter may only be specified for a queue of type *RMT.
Response
Remove the RMTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8132 (IBM i)
RMTMQMNAME only allowed with queue type *RMT.
Severity
40 : Stop Error
Explanation
The RMTMQMNAME parameter may only be specified for a queue of type *RMT.
Response
Remove the RMTMQMNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8133 (IBM i)
TMQNAME only allowed with queue type *RMT.
Severity
40 : Stop Error
Explanation
The TMQNAME parameter may only be specified for a queue of type *RMT.
Response
Remove the TMQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8134 (IBM i)
HDNBKTCNT not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The HDNBKTCNT parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the HDNBKTCNT parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8135
Not authorized.
Severity
40 : Stop Error
Explanation
You are not authorized to perform the requested operation for the IBM WebSphere MQ object. Either you are not authorized to perform the requested operation, or you are not authorized to the specified MQ object. For a copy command, you may not be authorized to the specified source MQ object, or, for a create command, you may not be authorized to the system default MQ object of the specified type. If creating or altering a subscription it may also indicate that the subscribing user does not exist or have the required authority to the destination queue.
Response
Obtain the necessary authority from your security officer or IBM WebSphere MQ administrator. Then try the command again. If you are running amqmdain on the Windows platform, the user MUSR_MQADMIN may not be authorized.
AMQ8136 (IBM i)
Error detected by prompt control program.
Severity
30 : Severe error
Explanation
A prompt control program detected errors.
Response
See the previously listed messages in the job log. Correct the errors and then prompt for the command again.
AMQ8137
IBM WebSphere MQ queue manager already starting.
Severity
40 : Stop Error
Explanation
The strmqm command was unsuccessful because the queue manager <insert_5> is already starting.
Response
Wait for the strmqm command to complete.
AMQ8138
The IBM WebSphere MQ queue has an incorrect type.
Severity
40 : Stop Error
Explanation
The operation is not valid with queue <insert_5> because it is not a local queue.
Response
Change the QNAME parameter to specify a queue of the correct type.
AMQ8139
Already connected.
Severity
20 : Error
Explanation
A connection to the IBM WebSphere MQ queue manager already exists.
Response
None.
AMQ8140
Resource timeout error.
Severity
40 : Stop Error
Explanation
A timeout occurred in the communication between internal WebSphere MQ queue manager components. This is most likely to occur when the system is heavily loaded.
Response
Wait until the system is less heavily loaded, then try the command again.
AMQ8141
IBM WebSphere MQ queue manager starting.
Severity
40 : Stop Error
Explanation
The queue manager <insert_5> is starting.
Response
Wait for the queue manager startup process to complete and then try the command again.
AMQ8142
IBM WebSphere MQ queue manager stopped.
Severity
40 : Stop Error
Explanation
The queue manager <insert_5> is stopped.
Response
Use the strmqm command to start the queue manager, and then try the command again.
AMQ8143
IBM WebSphere MQ queue not empty.
Severity
40 : Stop Error
Explanation
The queue <insert_5> specified in <insert_2> is not empty or contains uncommitted updates.
Response
Commit or roll back any uncommitted updates. If the command is DELETE QLOCAL, use the CLEAR QLOCAL command to clear the messages from the queue. Then try the command again.
AMQ8144
Log not available.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ logging resource is not available.
Response
Use the dltmqm command to delete the queue manager and then the crtmqm command to create the queue manager. Then try the command again.
AMQ8145
Connection broken.
Severity
40 : Stop Error
Explanation
The connection to the IBM WebSphere MQ queue manager failed during command processing. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
Response
Use the strmqm command to start the message queue manager, wait until the message queue manager has started, and try the command again.
AMQ8146
IBM WebSphere MQ queue manager not available.
Severity
40 : Stop Error
Explanation
The queue manager is not available because it has been stopped or has not been created.
Response
Use the crtmqm command to create the message queue manager, or the strmqm command to start the message queue manager as necessary. Then try the command again.
AMQ8146 (IBM i)
IBM WebSphere MQ queue manager not available.
Severity
40 : Stop Error
Explanation
The queue manager is not available because it has been stopped or has not been created.
Response
Use the CRTMQM command to create the message queue manager or the STRMQM command to start the message queue manager as necessary, then retry the command. If a queue manager was not specified, ensure that a default queue manager has been created and is started using the WRKMQM command.
AMQ8147
IBM WebSphere MQ object <insert_3> not found.
Severity
40 : Stop Error
Explanation
If the command entered was Change or Display, the object <insert_3> specified does not exist. If the command entered was Copy, the source object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
Response
Correct the object name and then try the command again or, if you are creating a new queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS.
AMQ8147 (IBM i)
IBM WebSphere MQ object <insert_3> not found.
Severity
40 : Stop Error
Explanation
If the command entered was Change, Delete or Display, the MQ object <insert_3> specified does not exist. If the command entered was Copy, the source MQ object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
Response
Correct the MQ object name and then try the command again or, if you are creating a new MQ object, either specify all parameters explicitly or ensure that the system default object of the required type exists.
AMQ8148
IBM WebSphere MQ object in use.
Severity
40 : Stop Error
Explanation
The object <insert_3> is in use by an MQ application program.
Response
Wait until the object is no longer in use and then try the command again. If the command is ALTER or CHANGE, specify FORCE to force the processing of the object regardless of any application program affected by the change. If the object is the dead-letter queue and the open input count is nonzero, it may be in use by an MQ channel. If the object is another queue object with a nonzero open output count, it may be in use by a MQ channel (of type RCVR or RQSTR). In either case, use the STOP CHANNEL and START CHANNEL commands to stop and restart the channel in order to solve the problem. To alter the queue USAGE the FORCE option must be used if the queue is not empty.
AMQ8149
IBM WebSphere MQ object damaged.
Severity
40 : Stop Error
Explanation
The object <insert_3> specified in <insert_4> is damaged.
Response
The object contents are not valid. Issue the DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY PROCESS command, as required, to determine the name of the damaged object. Issue the DEFINE command, for the appropriate object type, to replace the damaged object, then try the command again.
AMQ8150
IBM WebSphere MQ object already exists.
Severity
40 : Stop Error
Explanation
The object <insert_3> specified on the <insert_5> command could not be created because it already exists.
Response
Check that the name is correct and try the command again specifying REPLACE, or delete the object. Then try the command again.
AMQ8151
IBM WebSphere MQ object has different type.
Severity
40 : Stop Error
Explanation
The type specified for object <insert_3> is different from the type of the object being altered or defined.
Response
Use the correct MQ command for the object type, and then try the command again.
AMQ8152
Source IBM WebSphere MQ object has different type.
Severity
40 : Stop Error
Explanation
The type of the source object is different from that specified.
Response
Correct the name of the command, or source object name, and then try the command again, or try the command using the REPLACE option.
AMQ8153
Insufficient disk space for the specified queue.
Severity
40 : Stop Error
Explanation
The command failed because there was insufficient disk space available for the specified queue.
Response
Release some disk space and then try the command again.
AMQ8154
API exit load error.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ queue manager was unable to load the API crossing exit.
Response
Ensure that the API crossing exit program is valid, and that its name and directory are correctly specified. Correct any error and then try the command again.
AMQ8155
Connection limit exceeded.
Severity
40 : Stop Error
Explanation
The queue manager connection limit has been exceeded.
Response
The maximum limit on the number of IBM WebSphere MQ application programs that may be connected to the queue manager has been exceeded. Try the command later.
AMQ8156
IBM WebSphere MQ queue manager quiescing.
Severity
40 : Stop Error
Explanation
The queue manager is quiescing.
Response
The queue manager was stopping with -c specified for endmqm. Wait until the queue manager has been restarted and then try the command again.
AMQ8157
Security error.
Severity
40 : Stop Error
Explanation
An error was reported by the security manager program.
Response
Inform your systems administrator, wait until the problem has been corrected, and then try the command again.
AMQ8158 (IBM i)
API exit not found.
Severity
40 : Stop Error
Explanation
The API crossing exit program was not found.
Response
Ensure that the API crossing exit program for the MQI exists, and that its name and library are correctly specified. Correct any errors and then try the command again.
AMQ8159 (IBM i)
MAXDEPTH not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The MAXDEPTH parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the MAXDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8160 (IBM i)
DFTSHARE not allowed with queue type *ALS or *RMT.
Severity
40 : Stop Error
Explanation
The DFTSHARE parameter may not be specified for a queue of type *ALS or *RMT.
Response
Remove the DFTSHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
AMQ8161 (IBM i)
AUT(*MQMPASSID) only allowed with OBJTYPE(*ADM).
Severity
40 : Stop Error
Explanation
AUT(*MQMPASSID) may only be specified with OBJTYPE(*ADM).
Response
Change the AUT parameter to specify another value and then try the command again.
AMQ8162 (IBM i)
AUT(*MQMPASSALL) only allowed with OBJTYPE(*ADM).
Severity
40 : Stop Error
Explanation
AUT(*MQMPASSALL) may only be specified with OBJTYPE(*ADM).
Response
Change the AUT parameter to specify another value and then try the command again.
AMQ8163 (IBM i)
AUT(*MQMSETID) only allowed with OBJTYPE(*ADM).
Severity
40 : Stop Error
Explanation
AUT(*MQMSETID) may only be specified with OBJTYPE(*ADM).
Response
Change the AUT parameter to specify another value and then try the command again.
AMQ8164 (IBM i)
AUT(*MQMSETALL) only allowed with OBJTYPE(*ADM).
Severity
40 : Stop Error
Explanation
AUT(*MQMSETALL) may only be specified with OBJTYPE(*ADM).
Response
Change the AUT parameter to specify another value and then try the command again.
AMQ8165 (IBM i)
AUT(*MQMALTUSR) only allowed with OBJTYPE(*ADM).
Severity
40 : Stop Error
Explanation
AUT(*MQMALTUSR) may only be specified with OBJTYPE(*ADM).
Response
Change the AUT parameter to specify another value and then try the command again.
AMQ8166 (IBM i)
IBM WebSphere MQ reference object not found.
Severity
40 : Stop Error
Explanation
The object specified by the REFOBJ and REFOBJTYPE parameters does not exist.
Response
Correct the reference object name and type, and then try the command again.
AMQ8167 (IBM i)
Referenced object name not valid.
Severity
30 : Severe error
Explanation
The referenced object name specified in REFOBJ is not valid. The length of the name must not exceed 48 characters and the name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
Response
Change the length of the parameter value or change the parameter value to contain a valid combination of characters. Then try the command again.
AMQ8168 (IBM i)
User profile name for parameter USER not found.
Severity
30 : Severe error
Explanation
The user profile name specified for parameter USER could not be found on the system, and is not the special value *PUBLIC.
Response
Correct the user profile name, or use the Create User Profile (CRTUSRPRF) command to create the user profile then try the request again.
AMQ8169 (IBM i)
Authorization list for parameter AUTL does not exist.
Severity
30 : Severe error
Explanation
The authorization list specified for parameter AUTL does not exist. It may have been destroyed.
Response
Either specify an authorization list that exists, or create the authorization list using the Create Authorization List (CRTAUTL) command. Try the request again.
AMQ8170 (IBM i)
REFOBJTYPE(*OBJTYPE) and OBJTYPE(*ALL) cannot be used together.
Severity
30 : Severe error
Explanation
REFOBJTYPE(*OBJTYPE) can be specified only with a specific object type.
Response
Change the REFOBJTYPE or OBJTYPE input value to a specific object type. Then try the Grant Authority (GRTMQMAUT) command again.
AMQ8171 (IBM i)
Authority of *AUTL is only allowed with USER(*PUBLIC).
Severity
30 : Severe error
Explanation
AUT(*AUTL) was specified on either the Grant Authority (GRTMQMAUT) command or the Revoke Authority (RVKMQMAUT) command with the USER parameter not set to *PUBLIC. Only the authority for *PUBLIC can be deferred to the authorization list.
Response
Change the AUT parameter to the authorities that are correct for the users or change the USER parameter to *PUBLIC. Then try the command again.
AMQ8172
Already disconnected.
Severity
10 : Warning
Explanation
The MQI reason code of 2018 was returned from the IBM WebSphere MQ queue manager in response to an MQDISC request issued during command processing.
Response
None.
AMQ8173
No processes to display.
Severity
0 : Information
Explanation
There are no matching processes defined on this system.
Response
Using the DEFINE PROCESS command to create a process.
AMQ8174
No queues to display.
Severity
0 : Information
Explanation
There are no matching queues defined on this system.
Response
Use the appropriate command to define a queue of the type that you require, that is, DEFINE QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or DEFINE QREMOTE.
AMQ8175 (IBM i)
IBM WebSphere MQ trace has started.
Severity
0 : Information
Explanation
The trace has started successfully.
Response
None.
AMQ8176 (IBM i)
IBM WebSphere MQ trace has been written.
Severity
0 : Information
Explanation
The trace has been written successfully.
Response
None.
AMQ8177 (IBM i)
IBM WebSphere MQ trace has stopped.
Severity
0 : Information
Explanation
The trace has stopped.
Response
None.
AMQ8178 (IBM i)
IBM WebSphere MQ trace did not start.
Severity
40 : Stop Error
Explanation
The trace did not start successfully.
Response
None.
AMQ8179 (IBM i)
IBM WebSphere MQ trace output error.
Severity
40 : Stop Error
Explanation
The trace was not output successfully.
Response
None.
AMQ8180 (IBM i)
IBM WebSphere MQ trace end request failed.
Severity
40 : Stop Error
Explanation
Your request to end the trace was not successful.
Response
None.
AMQ8181 (IBM i)
No jobs to display.
Severity
10 : Warning
Explanation
There are no matching jobs running on this system.
Response
Specify another job name from the STRMQMSRV command.
AMQ8182 (IBM i)
IBM WebSphere MQ trace already off.
Severity
10 : Warning
Explanation
An attempt was made to set trace off, but the trace is not active.
Response
None.
AMQ8183 (IBM i)
IBM WebSphere MQ trace already running.
Severity
10 : Warning
Explanation
An attempt was made to start trace, but trace is already running.
Response
Either leave trace running as it is, or, if you want to change the trace settings, turn trace off and then turn it on again with appropriate settings.
AMQ8184 (IBM i)
Requested job cannot be found
Severity
10 : Warning
Explanation
The job specified cannot be found in the table that controls IBM WebSphere MQ for IBM i trace. As a result no trace action can be performed.
Response
Specify an appropriate job name.
AMQ8185
Operating system object already exists.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ object cannot be created because an object that is not known to MQ already exists in the MQ directory with the name that should be used for the new object. Refer to the log for previous messages.
Response
Remove the non-MQ object from the MQ library, and try the command again.
AMQ8186
Image not available for IBM WebSphere MQ object <insert_5>.
Severity
40 : Stop Error
Explanation
The object <insert_5> type <insert_3> cannot be re-created because the image is not fully available in the logs that are currently online. Refer to earlier messages in the error log for information about the logs that need to be brought online for this object to be re-created.
Response
Bring the relevant logs online, and try the command again.
AMQ8187
IBM WebSphere MQ object <insert_5> is currently open.
Severity
40 : Stop Error
Explanation
The object <insert_5>, type <insert_3>, is currently in use, so the <insert_1> command cannot be issued against it. If a generic list was presented to the command, the command is still issued against the other objects in the list.
Response
Wait until the object is no longer in use, and try the command again.
AMQ8188
Insufficient authorization to IBM WebSphere MQ object <insert_5>.
Severity
40 : Stop Error
Explanation
You are not authorized to issue the <insert_1> command against the object <insert_5> type <insert_3>. If a generic list was presented to the command, the command is still issued against the other objects in the list.
Response
Obtain sufficient authorization for the object, and retry the command.
AMQ8189 (IBM i)
IBM WebSphere MQ object <insert_3> is damaged.
Severity
40 : Stop Error
Explanation
The object <insert_3> type <insert_4> is damaged and the <insert_5> command cannot be issued against it. If a generic list was presented to the command then the command is still issued against the other objects in the list.
Response
Issue the appropriate DEFINE command for the object, specifying REPLACE, and then try the command again.
AMQ8190
<insert_3> succeeded on <insert_1> objects and failed on <insert_2> objects.
Severity
40 : Stop Error
Explanation
An operation performed on a generic list of objects was not completely successful.
Response
Examine the log for details of the errors encountered, and take appropriate action.
AMQ8191
IBM WebSphere MQ command server is starting.
Severity
40 : Stop Error
Explanation
The command server is starting.
Response
Wait for the strmqcsv command to complete and then try the operation again.
AMQ8191 (IBM i)
IBM WebSphere MQ command server is starting.
Severity
40 : Stop Error
Explanation
The command server is starting.
Response
Wait for the STRMQMCSVR command to complete and then try the operation again.
AMQ8192
IBM WebSphere MQ command server already starting.
Severity
40 : Stop Error
Explanation
The request to start the command server was unsuccessful because the command server is already starting.
Response
Wait for the strmqcsv command to complete.
AMQ8192 (IBM i)
IBM WebSphere MQ command server already starting.
Severity
40 : Stop Error
Explanation
The request to start the command server was unsuccessful because the command server is already starting.
Response
Wait for the STRMQMCSVR command to complete.
AMQ8193
IBM WebSphere MQ command server is ending.
Severity
40 : Stop Error
Explanation
The command server is ending.
Response
Wait for the endmqcsv command to complete and then try the command again.
AMQ8193 (IBM i)
IBM WebSphere MQ command server is ending.
Severity
40 : Stop Error
Explanation
The command server is ending.
Response
Wait for the ENDMQMCSVR command to complete and then try the command again.
AMQ8194
IBM WebSphere MQ command server already ending.
Severity
40 : Stop Error
Explanation
The end command server request was unsuccessful because the command server is already ending.
Response
Wait for the endmqcsv command to complete.
AMQ8194 (IBM i)
IBM WebSphere MQ command server already ending.
Severity
40 : Stop Error
Explanation
The end command server request was unsuccessful because the command server is already ending.
Response
Wait for the ENDMQMCSVR command to complete.
AMQ8195
IBM WebSphere MQ command server already running.
Severity
40 : Stop Error
Explanation
The strmqcsv command was unsuccessful because the command server is already running.
Response
None.
AMQ8195 (IBM i)
IBM WebSphere MQ command server already running.
Severity
40 : Stop Error
Explanation
The STRMQMCSVR command was unsuccessful because the command server is already running.
Response
None.
AMQ8196
IBM WebSphere MQ command server already stopped.
Severity
40 : Stop Error
Explanation
The request to end the command server was unsuccessful because the command server is already stopped.
Response
None.
AMQ8197
Deleted IBM WebSphere MQ queue damaged.
Severity
20 : Error
Explanation
The deleted MQ queue <insert_3> was damaged, and any messages it contained have been lost.
Response
None.
AMQ8198 (IBM i)
Program <insert_3> called with incorrect number of parameters.
Severity
20 : Error
Explanation
The number of parameters passed in the call to program <insert_3> is not correct.
Response
Correct the calling program and then retry the operation.
AMQ8199 (IBM i)
Error in call identifier parameter passed to program QMQM.
Severity
20 : Error
Explanation
The call identifier, the first parameter passed to program QMQM, is not in the required packed decimal format, or its value is not supported. Permitted values of the call identifier are contained in the RPG copy file CMQR.
Response
Correct the calling program, and retry the call.
AMQ8200 (IBM i)
MODENAME only allowed with TRPTYPE(*LU62).
Severity
40 : Stop Error
Explanation
The MODENAME parameter may only be specified with TRPTYPE(*LU62).
Response
Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62 and then try the command again.
AMQ8201 (IBM i)
TPGMNAME only allowed with TRPTYPE(*LU62).
Severity
40 : Stop Error
Explanation
The TPGMNAME parameter may only be specified with TRPTYPE(*LU62).
Response
Remove the TPGMNAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again.
AMQ8202
TMQNAME only allowed with channel type *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The TMQNAME parameter may only be specified with channel type *SDR or *SVR.
Response
Remove the TMQNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again.
AMQ8203 (IBM i)
CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN and *CLUSRCVR
Severity
40 : Stop Error
Explanation
The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR.
Response
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR. Then try the command again.
AMQ8204
MCANAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or *CLUSRCVR
Severity
40 : Stop Error
Explanation
The MCANAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or *CLUSRCVR.
Response
Remove the MCANAME parameter from the command, or if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8205
DSCITV only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The DSCITV parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Response
Remove the DSCITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again.
AMQ8206
SHORTRTY only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The SHORTRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Response
Remove the SHORTRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again.
AMQ8207
SHORTTMR only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The SHORTTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Response
Remove the SHORTTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again.
AMQ8208
LONGRTY only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The LONGRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Response
Remove the LONGRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again.
AMQ8209
LONGTMR only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The LONGTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Response
Remove the LONGTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again.
AMQ8210
PUTAUT only allowed with channel type *RCVR, *RQSTR or *CLUSRCVR
Severity
40 : Stop Error
Explanation
The PUTAUT parameter may only be specified with channel type *RCVR, *RQSTR or *CLUSRCVR.
Response
Remove the PUTAUT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *RCVR, *RQSTR or *CLUSRCVR. Then try the command again.
AMQ8211
BATCHINT only allowed with channel type *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The BATCHINT parameter may only be specified with channel type *SDR or *SVR.
Response
Remove the BATCHINT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again.
AMQ8212 (IBM i)
TPGMNAME parameter required with TRPTYPE(*LU62).
Severity
40 : Stop Error
Explanation
A required parameter was not specified.
Response
Enter a value for parameter TPGMNAME.
AMQ8213 (IBM i)
TMQNAME parameter required with channel type *SDR or *SVR.
Severity
40 : Stop Error
Explanation
The TMQNAME parameter must be specified with channel type *SDR or *SVR.
Response
Enter a value for parameter TMQNAME.
AMQ8214
CONNAME parameter missing.
Severity
40 : Stop Error
Explanation
The CONNAME parameter must be specified with channel types SDR, RQSTR, CLNTCONN, and CLUSSDR. It is also required with channel type CLUSRCVR if the TRPTYPE is not TCP.
Response
Enter a value for parameter CONNAME.
AMQ8214 (IBM i)
CONNAME parameter missing.
Severity
40 : Stop Error
Explanation
The CONNAME parameter must be specified with channel types *SDR, *RQSTR, *CLTCN and *CLUSSDR. It is also required with channel type *CLUSRCVR if the TRPTYPE is not *TCP.
Response
Enter a value for parameter CONNAME.
AMQ8215 (IBM i)
CVTMSG only allowed with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The CVTMSG parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR.
Response
Remove the CVTMSG parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or CLUSRCVR. Then try the command again.
AMQ8216 (IBM i)
MODENAME only allowed with TRPTYPE(*LU62).
Severity
40 : Stop Error
Explanation
The MODENAME parameter may only be specified with TRPTYPE(*LU62).
Response
Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again.
AMQ8217 (IBM i)
CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or CLUSRCVR.
Severity
40 : Stop Error
Explanation
The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR.
Response
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
AMQ8218
The system cannot accept the combination of parameters entered.
Severity
30 : Severe error
AMQ8219
Command server queue is open, retry later.
Severity
30 : Severe error
Response
Wait and try again later.
AMQ8220 (IBM i)
The PNGMQMCHL command has completed.
Severity
0 : Information
Explanation
The PNGMQMCHL command sent <insert_1> bytes of data to <insert_3> and received the data back in <insert_4>.<insert_5> seconds. The number of bytes will be less than the amount requested on the command, when the length requested is greater than the allowed maximum, in one communications transmission, for the operating system and communications protocol.
Response
None.
AMQ8221 (IBM i)
Ping data length truncated, specified length <insert_1>, actual length <insert_2>.
Severity
10 : Warning
Explanation
The length of the ping data sent was reduced because of constraints in the current configuration.
Response
None.
AMQ8222 (IBM i)
The data sent and received by the PNGMQMCHL command was not identical.
Severity
40 : Stop Error
Explanation
Ping data compare failed at offset <insert_1>, data sent <insert_3>, data received <insert_4>.
Response
This is probably due to a communications failure. Other messages may have been issued.
AMQ8223 (IBM i)
No channels to display.
Severity
0 : Information
Explanation
There are no channels defined on this system.
Response
Create a channel using the CRTMQMCHL command.
AMQ8224 (IBM i)
From channel <insert_3> not found.
Severity
30 : Severe error
Explanation
The source IBM WebSphere MQ channel does not exist.
Response
Correct the MQ channel name and then try the command again.
AMQ8225 (IBM i)
From channel and to channel names are equal.
Severity
30 : Severe error
Explanation
The same name has been specified for the from channel name and the to channel name.
Response
Choose two different names, of which the from channel must exist.
AMQ8226
IBM WebSphere MQ channel already exists.
Severity
40 : Stop Error
Explanation
The channel <insert_3> cannot be created because it already exists.
Response
Check that the name is correct and try the command again specifying REPLACE, or delete the channel and then try the command again.
AMQ8227
Channel <insert_3> not found.
Severity
30 : Severe error
Explanation
The channel could not be found.
Response
Correct the Channel Name if wrong and then try the command again. For DEFINE CHANNEL check that the Channel Name in error exists.
AMQ8229 (IBM i)
No message queue managers to display.
Severity
0 : Information
Explanation
There are no message queue managers to administer.
Response
Add a queue manager using PF6 or the ADMQMNAM command.
AMQ8230 (IBM i)
No queue manager objects to display.
Severity
0 : Information
Explanation
Either the queue manager has no objects to display (this is unlikely), or the selection criteria resulted in zero objects to display.
Response
Change or remove the selection criteria.
AMQ8231 (IBM i)
No responses to display.
Severity
0 : Information
Explanation
There are no commands or command responses to display.
Response
None.
AMQ8232 (IBM i)
No messages to display.
Severity
0 : Information
Explanation
The queue is empty, or the queue does not exist.
Response
None.
AMQ8233 (IBM i)
No message data to display.
Severity
0 : Information
Explanation
The message contains no data.
Response
None.
AMQ8234 (IBM i)
No response data to display.
Severity
0 : Information
Explanation
There is no response data to display for this command. This is probably because the command has not yet completed.
Response
None.
AMQ8235 (IBM i)
No command parameters to display.
Severity
0 : Information
Explanation
Some commands have no required parameters.
Response
None.
AMQ8236 (IBM i)
Channel <insert_3> not found.
Severity
30 : Severe error
Explanation
CHGMQMCHL was issued for a non-existent channel.
Response
Correct the IBM WebSphere MQ channel name and then try the command again.
AMQ8237 (IBM i)
NPMSPEED only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Stop Error
Explanation
The NPMSPEED parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR.
Response
Remove the NPMSPEED parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
AMQ8238 (IBM i)
Queue manager connection already open.
Severity
30 : Severe error
Explanation
An MQCONN call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time.
Response
Use the MQDISC call to disconnect from the queue manager which is already connected, and then issue the MQCONN call to connect to the new queue manager. Disconnecting from the existing queue manager will close any queues which are currently open, it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is used.
AMQ8239 (IBM i)
LOCLADDR not valid for channel type *RCVR or *SVRCN.
Severity
40 : Stop Error
Explanation
The LOCLADDR parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN.
Response
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN. Then try the command again.
AMQ8240 (IBM i)
Unexpected error <insert_1> in <insert_3>.
Severity
40 : Stop Error
Explanation
The unexpected return code <insert_1> was returned during <insert_3> processing.
Response
This message is associated with an internal error. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8241 (IBM i)
Unexpected message format <insert_3> received.
Severity
40 : Stop Error
Explanation
The unexpected message format <insert_3> was received in message on the internal reply queue.
Response
This message is probably a message sent erroneously to this queue. The message in error is written to the SYSTEM.ADMIN.EXCEPTION.QUEUE, where it may be viewed using the WRKMQMMSG command.
AMQ8242
SSLCIPH definition wrong.
Severity
40 : Stop Error
Explanation
The definition of the SSLCIPH parameter was wrong.
Response
Correct the SSLCIPH definition and try the command again.
AMQ8243
SSLPEER definition wrong.
Severity
40 : Stop Error
Explanation
The definition of the SSLPEER parameter was wrong. Possible causes may be that the syntax was invalid or that it contained an invalid attribute type.
Response
Correct the SSLPEER definition and try the command again.
AMQ8266 (IBM i)
No objects to display.
Severity
0 : Information
Explanation
There are no objects with the specified name and type.
Response
None.
AMQ8276
Display Connection details.
Severity
0 : Information
Explanation
The DISPLAY CONN command completed successfully. Details follow this message.
AMQ8278 (IBM i)
Maximum handle limit reached.
Severity
40 : Stop Error
Explanation
An attempt was made to exceed the maximum handle limit specified for the message queue manager.
Response
Increase the maximum handle limit specified for the message queue manager using the CHGMQM command. Then try the command again.
AMQ8280 (IBM i)
Queue does not exist.
Severity
30 : Severe error
Explanation
The queue being displayed does not exist on this queue manager.
Response
Check the name of the queue and retry the operation. If you are attempting to display a queue of type *ALS, check the queue definition references an existing queue definition.
AMQ8282 (IBM i)
Queue manager <insert_3> is not defined on the connected queue manager.
Severity
30 : Severe error
Explanation
Either the necessary queue manager name has been entered incorrectly on the add queue manager panel, or the queue manager has not been defined on the connected queue manager.
Response
Correct the name, or define <insert_3> on the connected queue manager by creating a local queue with name <insert_3> and usage *TMQ (transmission queue), and then creating sender and receiver channels on both the connected queue manager and queue manager <insert_3>.
AMQ8284 (IBM i)
This user is not authorized to queue <insert_3>.
Severity
40 : Stop Error
Explanation
Queue <insert_3> (queue manager <insert_4>) has not been authorized for your use.
Response
Have queue <insert_3> authorized for your use. If queue manager <insert_4> is not the local queue manager, you might not be authorized to the transmission queue for this queue manager.
AMQ8287
No channels with status to display.
Severity
0 : Information
Explanation
There are no channels having status information to display. This indicates either, that the channel has not been started previously, or, that the channel has been started but has not yet completed a transmission sequence.
Response
None.
AMQ8288 (IBM i)
Not authorized to command <insert_1>
Severity
40 : Stop Error
Explanation
You are not authorized to perform the requested operation for IBM WebSphere MQ command <insert_1>.
Response
Obtain the necessary authority from your IBM WebSphere MQ administrator. Then try the command again.
AMQ8289 (IBM i)
You are not authorized to the IBM WebSphere MQ command.
Severity
40 : Stop Error
Explanation
You are not authorized to the IBM WebSphere MQ command because your user profile is not a member of the QMQMADM group.
Response
Ask your MQ administrator to give your user profile *ALLOBJ authority, or add your user profile to the QMQMADM group (either as a primary or supplemental group)
AMQ8291 (IBM i)
IBM WebSphere MQ remote trace already running.
Severity
10 : Warning
Explanation
An attempt was made to start remote trace, but it is already running.
Response
Either leave remote trace running as it is, or, if you want to change the settings, turn remote trace off and then turn it on again with appropriate settings.
AMQ8294 (IBM i)
IBM WebSphere MQ remote trace already off.
Severity
10 : Warning
Explanation
An attempt was made to end remote trace, but it is already off.
Response
Leave remote trace off.
AMQ8295 (IBM i)
IBM WebSphere MQ object not secured by authorization list.
Severity
40 : Stop Error
Explanation
The specified object is not secured by the authorization list to be revoked from it.
Response
Use the display authority (DSPMQMAUT) command to determine what authorization list is securing the object, if any. Issue the RVKMQMAUT command again with the authorization list that is securing the the object to revoke the authorization list's authority.
AMQ8296
<insert_1> MQSC commands completed successfully.
Severity
0 : Information
Explanation
The <insert_3> command has completed successfully. The <insert_1> MQ commands from <insert_5> have been processed without error and a report written to the printer spool file.
Response
None.
AMQ8297
<insert_1> MQSC commands verified successfully.
Severity
0 : Information
Explanation
The <insert_3> command completed successfully. The <insert_1> MQ commands from <insert_5> have been verified and a report written to the printer spool file.
Response
None.
AMQ8298
Error report generated for MQSC command process.
Severity
40 : Stop Error
Explanation
The <insert_5> command attempted to process a sequence of MQ commands and encountered some errors, however, the operation may have partially completed.
Response
If the <insert_5> command was executed a report has been written to a printer spool file. Examine the spooled printer file for details of the errors encountered and correct the MQSC source in <insert_3> and retry the operation.
AMQ8299
Cannot open <insert_3> for MQSC process.
Severity
40 : Stop Error
Explanation
The <insert_5> command failed to open <insert_3> for MQ command processing.
Response
Check that the intended file exists, and has been specified correctly. Correct the specification or create the object, and try the operation again.
AMQ8300 (IBM i)
Too many exit programs/user data fields defined.
Severity
30 : Severe error
Explanation
An attempt was made to create or change a channel which had more than the allowed maximum of a total of six exit programs, user data fields, or both defined.
Response
Define the channel again so that a maximum of six exit programs, user data fields, or both are defined.
AMQ8301 (IBM i)
IBM WebSphere MQ storage monitor job could not be started.
Severity
50 : System Error
Explanation
An attempt to start the storage monitor process (job QMQM in subsystem QSYSWRK) was unsuccessful.
Response
Check the job log for the reason for the failure, and try the command again.
AMQ8302
Internal failure initializing IBM WebSphere MQ services.
Severity
50 : System Error
Explanation
An error occurred while attempting to initialize IBM WebSphere MQ services.
Response
A call to xcsInitialize ended with the FAIL, STOP, or STOP_ALL return code. Refer to the log for messages diagnosing this problem.
AMQ8303
Insufficient storage available to process request.
Severity
50 : System Error
AMQ8304
Tracing cannot be started. Too many traces are already running.
Severity
40 : Stop Error
Explanation
A maximum of 15 traces may be running concurrently. This number is already running.
Response
Stop one or more of the other traces and try the command again.
AMQ8305
Tracing cannot be started. Too many traces are already running.
Severity
40 : Stop Error
Explanation
A maximum of 9 traces can be running concurrently, and this number of traces is already running.
Response
Stop one or more of the other traces and try the command again.
AMQ8306 (IBM i)
BATCHSIZE only allowed with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Stop Error
Explanation
The BATCHSIZE parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Response
Remove the BATCHSIZE parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
AMQ8307 (IBM i)
SEQNUMWRAP only allowed with channel type *SDR, *SVR, *RCVR , *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Stop Error
Explanation
The SEQNUMWRAP parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Response
Remove the SEQNUMWRAP parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
AMQ8308 (IBM i)
MSGRTYEXIT only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Stop Error
Explanation
The MSGRTYEXIT parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Response
Remove the MSGRTYEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
AMQ8309 (IBM i)
MSGRTYDATA only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Stop Error
Explanation
The MSGRTYDATA parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Response
Remove the MSGRTYDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
AMQ8310 (IBM i)
MSGRTYNBR only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Stop Error
Explanation
The MSGRTYNBR parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Response
Remove the MSGRTYNBR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
AMQ8311 (IBM i)
MSGRTYITV only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Stop Error
Explanation
The MSGRTYITV parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Response
Remove the MSGRTYITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
AMQ8312 (IBM i)
CLUSTER only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Stop Error
Explanation
The CLUSTER parameter may only be specified with queue type *ALS, *LCL and *RMT.
Response
Remove the CLUSTER parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
AMQ8313 (IBM i)
CLUSNL only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Stop Error
Explanation
The CLUSNL parameter may only be specified with queue type *ALS, *LCL and *RMT.
Response
Remove the CLUSNL parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
AMQ8314 (IBM i)
DEFBIND only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Stop Error
Explanation
The DEFBIND parameter may only be specified with queue type *ALS, *LCL and *RMT.
Response
Remove the DEFBIND parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
AMQ8315
No namelists to display.
Severity
0 : Information
Explanation
There are no matching namelists defined on this system.
Response
Use the Create Namelist (CRTMQMNL) command to create a namelist.
AMQ8316
No cluster queue managers to display.
Severity
0 : Information
Explanation
There are no matching cluster queue managers defined on this system.
Response
None.
AMQ8317 (IBM i)
CLUSTER only allowed with channel type *CLUSSDR and *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The CLUSTER parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR.
Response
Remove the CLUSTER parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8318 (IBM i)
CLUSNL only allowed with channel type *CLUSSDR and *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The CLUSNL parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR.
Response
Remove the CLUSNL parameter from the command or, if the command is CRTMQMCHL, change the CHLQTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8319
MSGEXIT only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The MSGEXIT parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR, or *CLUSRCVR.
Response
Remove the MSGEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8320 (IBM i)
MSGUSRDATA only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, or *CLUSSDR or *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The MSGUSRDATA parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Response
Remove the MSGUSRDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8321 (IBM i)
Process <insert_3> is still running.
Severity
0 : Information
AMQ8322 (IBM i)
TIMEOUT only allowed with ENDCCTJOB(*YES).
Severity
40 : Stop Error
Explanation
The TIMEOUT parameter may only be specified when connected jobs are being ended with the ENDCCTJOB option set to *YES.
Response
Remove the TIMEOUT parameter from the command or, if you want to fully quiesce the queue manager, change the ENDCCTJOB parameter to *YES. Then try the command again.
AMQ8323 (IBM i)
OPTION(*PREEMPT) must not be used with ENDCCTJOB(*YES).
Severity
40 : Stop Error
Explanation
When performing a pre-emptive shutdown of the queue manager the ENDCCTJOB(*YES) parameter is not allowed.
Response
Change the ENDCCTJOB(*YES) parameter to ENDCCTJOB(*NO) or, if you want to fully quiesce the queue manager without doing a pre-emptive shutdown, change the OPTION(*PREEMPT) parameter to another value. Then try the command again.
AMQ8324 (IBM i)
OPTION(*WAIT) not allowed with MQMNAME(*ALL).
Severity
40 : Stop Error
Explanation
The OPTION(*WAIT) parameter is not allowed when performing a shutdown of all queue managers.
Response
Remove the OPTION(*WAIT) parameter from the command or, specify individual queue manager names to shut down the queue managers one-by-one with the OPTION(*WAIT) parameter. Then try the command again.
AMQ8325 (IBM i)
MQMNAME(*ALL) is not allowed with ENDCCTJOB(*NO).
Severity
40 : Stop Error
Explanation
The MQMNAME(*ALL) parameter is only allowed when performing a full shutdown of the queue managers.
Response
Specify individual queue manager names to shut the queue managers down one-by-one or change the ENDCCTJOB parameter to *YES. Then try the command again.
AMQ8330
Running
Severity
0 : Information
AMQ8331
Ended normally
Severity
0 : Information
AMQ8332
Ended immediately
Severity
0 : Information
AMQ8333
Ended preemptively
Severity
0 : Information
AMQ8334
Ended unexpectedly
Severity
0 : Information
AMQ8335
Starting
Severity
0 : Information
AMQ8336
Quiescing
Severity
0 : Information
AMQ8337
Ending immediately
Severity
0 : Information
AMQ8338
Ending preemptively
Severity
0 : Information
AMQ8339
Being deleted
Severity
0 : Information
AMQ8340
Not available
Severity
0 : Information
AMQ8341
SUBPOOL(<insert_3>)<insert_4>PID(<insert_1>)
Severity
0 : Information
AMQ8342
No authorities to display.
Severity
0 : Information
Explanation
There are no authority records defined on this system, satisfying the input parameters.
Response
Use the appropriate input to list all the authorities defined on the system, or enter the command again with different input..
AMQ8343
Running as standby
Severity
0 : Information
AMQ8343 (IBM i)
The requested operation is not valid for user QMQMADM.
Severity
0 : Information
Explanation
You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid IBM WebSphere MQ object, with the authority *REMOVE or *NONE.
Response
Remove QMQMADM from the list of users to this command.
AMQ8344
Running elsewhere
Severity
0 : Information
AMQ8344 (IBM i)
The delete option is only valid for a generic profile name.
Severity
0 : Information
Explanation
The delete option, which will delete this authority profile by removing all the users from this authority profile, is not valid for an object name or the special value &class.
Response
To delete users from an object, work from the WRKMQMAUTD command.
AMQ8345 (IBM i)
BATCHHB not valid for channel type *RCVR, *RQSTR, *SVRCN or *CLTCN.
Severity
40 : Stop Error
Explanation
The BATCHHB parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR, or *CLUSRCVR.
Response
Remove the BATCHHB parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or *CLUSRCVR. Then try the command again.
AMQ8346 (IBM i)
Parameter mismatch between QMNAME and QMID.
Severity
40 : Stop Error
Explanation
The Queue Manager Name for Removal (QMNAME) parameter is not *QMID and there is a value for the Queue Manager Identifier for Removal (QMID) parameter.
Response
A value for QMID is not allowed unless QMNAME is *QMID. Change the value specified on the QMNAME parameter or the value of the QMID parameter and then try the request again.
AMQ8347 (IBM i)
USERID not valid for channel type *RCVR, *SVRCN or *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The USERID parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN.
Response
Remove the USERID parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again.
AMQ8348 (IBM i)
PASSWORD not valid for channel type *RCVR, *SVRCN or *CLUSRCVR.
Severity
40 : Stop Error
Explanation
The PASSWORD parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN.
Response
Remove the PASSWORD parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again.
AMQ8349 (IBM i)
Authority changes to <insert_3> failed.
Severity
40 : Stop Error
Explanation
Authority changes to an object were requested but could not be made.
Response
Check the authorities that you are granting are relevant to the object type of <insert_3>.
AMQ8350
Usage: dspmqver [-p Components] [-f Fields] [-b] [-v]
Severity
0 : Information
Explanation
This shows the correct usage.
Response
None.
AMQ8351
IBM WebSphere MQ Java environment has not been configured correctly.
Severity
20 : Error
Explanation
A command was issued that attempted to run a Java application. However either a working JRE (Java Runtime Environment) was not found or the IBM WebSphere MQ Java environment variables have not been set up. The command could not be run successfully.
Response
Ensure that you have a working JRE (Java Runtime Environment) and that the IBM WebSphere MQ Java environment variables have been set using the setjmsenv script. Retry the command.
AMQ8352
IBM WebSphere MQ queue manager <insert_5> becoming primary instance.
Severity
0 : Information
Explanation
Queue manager <insert_5> was running previously as a standby instance and is now becoming the primary instance.
Response
None.
AMQ8353
Quiesce request accepted. The queue manager will stop when all outstanding work is complete, permitting switchover to a standby queue manager.
Severity
0 : Information
Explanation
You have requested that the queue manager end when there is no more work for it. In the meantime, it will refuse new applications that attempt to start, although it allows those already running to complete their work. Once the queue manager has stopped, a switchover to a standby queue manager is permitted.
Response
None.
AMQ8354
IBM WebSphere MQ queue manager <insert_5> ended, permitting switchover to a standby queue manager.
Severity
0 : Information
Explanation
IBM WebSphere MQ queue manager <insert_5> ended. Once the queue manager has stopped, a switchover to a standby queue manager is permitted.
Response
None.
AMQ8355
IBM WebSphere MQ standby queue manager <insert_5> not permitted to become a primary instance.
Severity
20 : Error
Explanation
IBM WebSphere MQ standby queue manager <insert_5> obtained a lock on its data in the file-system but was not permitted to become a primary instance. The most likely cause is that the queue manager was stopped without permitting a switchover.
Response
None.
AMQ8367
Active instance of IBM WebSphere MQ queue manager <insert_3> not ended.
Severity
20 : Error
Explanation
You tried to end the local instance of IBM WebSphere MQ queue manager <insert_3> using the '-x' option, which ends a standby instance. The local instance is not a standby instance.
Response
Issue the endmqm command without the '-x' option.
AMQ8368
Standby instance of IBM WebSphere MQ queue manager <insert_3> not ended.
Severity
20 : Error
Explanation
You tried to end the local instance of IBM WebSphere MQ queue manager <insert_3>. It is a standby instance so you must specify the '-x' option of endmqm.
Response
Issue the endmqm command with the '-x' option.
AMQ8370
Usage: runmqdnm -q Queue -a Assembly

[-m QueueManager] [-c ClassName] [-u Text] [-s Syncpoint]

[-n MaxThreads] [-t Timeout] [-b BackoutThreshold]

[-r BackoutQueue] [-p Context] [-d]

Severity
0 : Information
Explanation
This shows the correct usage.
Response
None.
AMQ8371
<insert_3> is not a valid command line option.
Severity
40 : Stop Error
Explanation
The option <insert_3> was specified on the command line to the application. This option is not a valid command line options for the application.
Response
Check the usage information for the application and then retry.
AMQ8372
The required command line option <insert_3> is missing.
Severity
40 : Stop Error
Explanation
The application expects several mandatory command line options. One of these, <insert_3>, was not specified.
Response
Check the usage information for the application and ensure that all required parameters are specified then retry.
AMQ8373
Invalid value specified for command line option <insert_3> (<insert_4>).
Severity
40 : Stop Error
Explanation
The value specified for command line option <insert_3> (<insert_4>) is invalid.
Response
Check the usage information for the application and ensure that all options specify values in the valid range then retry.
AMQ8374
IBM WebSphere MQ queue manager <insert_3> does not exist.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ queue manager <insert_3> does not exist.
Response
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
AMQ8375
IBM WebSphere MQ queue manager <insert_3> not available.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ queue manager <insert_3> is not available because it has been stopped or is otherwise not contactable.
Response
Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again.
AMQ8376
IBM WebSphere MQ queue <insert_3> not found.
Severity
40 : Stop Error
Explanation
The queue <insert_3> could not be found, it may not have been created.
Response
Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again.
AMQ8377
Unexpected error <insert_1> was received by the application.
Severity
40 : Stop Error
Explanation
The error <insert_1> was returned unexpectedly to the application.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8378
Unexpected exception received from .NET Framework

<insert_3>

Severity
40 : Stop Error
Explanation
The application received an exception from the underlying .NET framework, information about the exception follows:

<insert_4>

Response
Examine the information contained within the exception to determine if it is possible to resolve locally.

If it is not possible to resolve the problem locally, save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ8379
Assembly <insert_3> could not be loaded
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ .NET Monitor attempted to load assembly <insert_3> but received an exception from the underlying .NET framework indicating that it could not be found. <insert_4>
Response
Check that the assembly does exist and is accessible to the user running the application then retry.

If the assembly should be available, save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ8380
No classes implementing IMQObjectTrigger found in <insert_3>.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ .NET monitor was unable to identify any classes in referenced assembly <insert_3> which implement the IMQObjectTrigger interface.
Response
It is a requirement of the IBM WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry.
AMQ8381
Too many classes implementing IMQObjectTrigger (<insert_1>) found in <insert_3>.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ .NET monitor found <insert_1> classes in referenced assembly <insert_3> all of which implement the IMQObjectTrigger interface.
Response
It is a requirement of the IBM WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry.
AMQ8382
A Message breaking the backout threshold (<insert_1>) was moved to <insert_4>
Severity
10 : Warning
Explanation
Whilst processing queue <insert_3> a message with a backout count that exceeded the specified backout threshold (<insert_1>) was successfully moved to <insert_4>
Response
The message moved to the backout queue has a backout count greater than the backout threshold specified (or picked up from the input queue BOTHRESH attribute). You should investigate the reason why this message was rolled back onto the input queue and resolve that issue. If backout processing is not required, modify the command line options and or queue definitions to achieve the required behaviour from the .NET monitor.
AMQ8383
A Message breaking the backout threshold (<insert_1>) could not be moved.
Severity
40 : Stop Error
Explanation
While processing queue <insert_3> a message with a backout count that exceeded the specified backout threshold (<insert_1>) was encountered however, it was not possible to move it to either a backout queue or the dead-letter queue.
Response
Because it was not possible to move the backed out message to another queue, it has been left on the input queue. As a result, the .NET monitor has ended.

It is possible that the backout queue or dead-letter queue are full or disabled for put - in this case, resolve this problem first.

If backout processing should have resulted in the message being placed on another queue, check the command line options, input queue definition and queue manager dead-letter queue attribute to ensure that they are correct, then retry.

AMQ8390
Usage: endmqdnm -q Queue [-m QueueManager]
Severity
0 : Information
Explanation
This shows the correct usage.
Response
None.
AMQ8391
<insert_3> is not a valid command line option.
Severity
40 : Stop Error
Explanation
The option <insert_3> was specified on the command line to the application. This option is not one of the valid set of command line options.
Response
Check the usage information for the application and then retry.
AMQ8392
The required command line option <insert_3> is missing.
Severity
40 : Stop Error
Explanation
The application expects mandatory command line options. One of these, <insert_3>, was not specified.
Response
Check the usage information for the application and ensure that all required parameters are specified then retry.
AMQ8393
Invalid value specified for command line option <insert_3> (<insert_4>).
Severity
40 : Stop Error
Explanation
The value specified for command line option <insert_3> (<insert_4>) is invalid.
Response
Check the usage information for the application and ensure that all options specify values in the valid range then retry.
AMQ8394
IBM WebSphere MQ queue manager <insert_3> does not exist.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ queue manager <insert_3> does not exist.
Response
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
AMQ8395
IBM WebSphere MQ queue manager <insert_3> not available.
Severity
40 : Stop Error
Explanation
The IBM WebSphere MQ queue manager <insert_3> is not available because it has been stopped or is otherwise not contactable.
Response
Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again.
AMQ8396
IBM WebSphere MQ queue <insert_3> not found.
Severity
40 : Stop Error
Explanation
The queue <insert_3> could not be found, it may not have been created.
Response
Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again.
AMQ8397
Unexpected error <insert_1> was received by the application.
Severity
40 : Stop Error
Explanation
The error <insert_1> was returned unexpectedly to the application.
Response
Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8398
Unexpected exception received from .NET Framework

<insert_3>

Severity
40 : Stop Error
Explanation
The application received an exception from the underlying .NET framework, information about the exception follows:

<insert_4>

Response
Examine the information contained within the exception to determine if it is possible to resolve locally.

If it is not possible to resolve the problem locally, save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ8401
<insert_1> MQSC commands read.
Severity
0 : Information
Explanation
The MQSC script contains <insert_1> commands.
Response
None.
AMQ8402
<insert_1> commands have a syntax error.
Severity
0 : Information
Explanation
The MQSC script contains <insert_1> commands having a syntax error.
Response
None.
AMQ8403
<insert_1> valid MQSC commands could not be processed.
Severity
0 : Information
Explanation
The MQSC script contains <insert_1> commands that failed to process.
Response
None.
AMQ8404
Command failed.
Severity
0 : Information
Explanation
An MQSC command has been recognized, but cannot be processed.
Response
None.
AMQ8405
Syntax error detected at or near end of command segment below:-
Severity
0 : Information
Explanation
The MQSC script contains <insert_1> commands having a syntax error.
Response
None.
AMQ8406
Unexpected 'end of input' in MQSC.
Severity
0 : Information
Explanation
An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command.
Response
None.
AMQ8407
Display Process details.
Severity
0 : Information
Explanation
The MQSC DISPLAY PROCESS command completed successfully, and details follow this message.
Response
None.
AMQ8408
Display Queue Manager details.
Severity
0 : Information
Explanation
The MQSC DISPLAY QMGR command completed successfully, and details follow this message.
Response
None.
AMQ8409
Display Queue details.
Severity
0 : Information
Explanation
The MQSC DISPLAY QUEUE command completed successfully, and details follow this message.
Response
None.
AMQ8410
Parser Error.
Severity
0 : Information
Explanation
The MQSC Parser has an internal error.
Response
None.
AMQ8411
Duplicate Keyword Error.
Severity
0 : Information
Explanation
A command in the MQSC script contains duplicate keywords.
Response
None.
AMQ8412
Numeric Range Error.
Severity
0 : Information
Explanation
The value assigned to an MQSC command keyword is out of the permitted range.
Response
None.
AMQ8413
String Length Error.
Severity
0 : Information
Explanation
A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword.
Response
None.
AMQ8414
Display Channel details.
Severity
0 : Information
Explanation
The MQSC DISPLAY CHL command completed successfully, and details follow this message.
Response
None.
AMQ8415
Ping IBM WebSphere MQ Queue Manager command complete.
Severity
0 : Information
Explanation
The MQSC PING QMGR command completed successfully.
Response
None.
AMQ8416
MQSC timed out waiting for a response from the command server.
Severity
0 : Information
Explanation
MQSC did not receive a response message from the remote command server in the time specified.
Response
None.
AMQ8417
Display Channel Status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message.
Response
None.
AMQ8418
<insert_1> command responses received.
Severity
0 : Information
Explanation
Running in queued mode, <insert_1> command responses were received from the remote command server.
Response
None.
AMQ8419
The Queue is already in the DCE cell.
Severity
0 : Information
Explanation
The Queue is already in the cell, that is, its SCOPE attribute is already CELL.
Response
None.
AMQ8420
Channel Status not found.
Severity
0 : Information
Explanation
No status was found for the specified channel(s).
Response
None.
AMQ8421
A required keyword was not specified.
Severity
0 : Information
Explanation
A keyword required in this command was not specified.
Response
None.
AMQ8422
MQSC found the following response to a previous command on the reply queue :-
Severity
0 : Information
Explanation
MQSC found additional command responses on the reply queue. They will follow this message.
Response
None.
AMQ8423
Cell Directory not available.
Severity
0 : Information
Explanation
The DCE cell directory is not available, so the requested operation has failed.
Response
None.
AMQ8424
Error detected in a name keyword.
Severity
0 : Information
Explanation
A keyword in an MQSC command contained a name string which was not valid. This may be because it contained characters which are not accepted in MQ names. Typical keywords which can produce this error are QLOCAL (and the other q types), CHANNEL, XMITQ, INITQ, MCANAME etc.
Response
None.
AMQ8425
Attribute value error.
Severity
0 : Information
Explanation
A keyword in an MQSC command contained a value that was not valid.
Response
None.
AMQ8426
Valid MQSC commands are:
Severity
0 : Information
Explanation
The text shows valid MQSC commands.
Response
None.
AMQ8427
Valid syntax for the MQSC command:
Severity
0 : Information
Explanation
The text shown is the valid syntax for the MQSC command.
Response
None.
AMQ8428
TYPE Keyword has already been specified.
Severity
0 : Information
Explanation
The TYPE has already been specified after the DISPLAY verb, for example DISPLAY QUEUE(*) type(QLOCAL) type(QALIAS).
Response
Delete the second TYPE keyword and run the command again.
AMQ8429 (IBM i)
Error detected in a exit parameter.
Severity
0 : Information
Explanation
A syntax error occurred an the exit parameter. This may be because it contained characters which are not accepted as exit names. Check the parameters in the MSGEXIT, RCVEXIT, SCYEXIT and SENDEXIT definitions.
Response
None.
AMQ8430
Remote queue manager name is unknown.
Severity
0 : Information
Explanation
The Remote queue manager name is not known to this queue manager. Check that a transmission queue of the same name as the remote queue manager name exists.
Response
Create a transmission queue of the same name as the remote queue manager if one does not exist.
AMQ8431
Transmission queue does not exist
Severity
0 : Information
Explanation
The transmission queue does not exist on this queue manager.
Response
None.
AMQ8432
You are not allowed to set both the REPOS and REPOSNL fields.
Severity
0 : Information
Explanation
An attempt to set both the REPOS and REPOSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank.
Response
None.
AMQ8433
You are not allowed to set both the CLUSTER and CLUSNL fields.
Severity
0 : Information
Explanation
An attempt to set both the CLUSTER and CLUSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank.
Response
None.
AMQ8434
The repository is unavailable.
Severity
0 : Information
Explanation
The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager.
Response
None.
AMQ8435
All valid MQSC commands were processed.
Severity
0 : Information
Explanation
The MQSC script contains no commands that failed to process.
Response
None.
AMQ8436
One valid MQSC command could not be processed.
Severity
0 : Information
Explanation
The MQSC script contains one command that failed to process.
Response
None.
AMQ8437
No MQSC commands read.
Severity
0 : Information
Explanation
The MQSC script contains no commands.
Response
None.
AMQ8438
One MQSC command read.
Severity
0 : Information
Explanation
The MQSC script contains one command.
Response
None.
AMQ8439
No commands have a syntax error.
Severity
0 : Information
Explanation
The MQSC script contains no commands having a syntax error.
Response
None.
AMQ8440
One command has a syntax error.
Severity
0 : Information
Explanation
The MQSC script contains one command which has a syntax error.
Response
None.
AMQ8441
Display Cluster Queue Manager details.
Severity
0 : Information
Explanation
The MQSC DISPLAY CLUSQMGR command completed successfully, and details follow this message.
Response
None.
AMQ8442
USAGE can not be set to XMITQ with either the CLUSTER or CLUSNL fields set.
Severity
0 : Information
Explanation
An attempt has been made to set USAGE to XMITQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again.
Response
None.
AMQ8442 (IBM i)
USAGE can not be set to *TMQ with either the CLUSTER or CLUSNL fields set.
Severity
0 : Information
Explanation
An attempt has been made to set USAGE to *TMQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again.
Response
None.
AMQ8443
Only the CLUSTER or CLUSNL field may have a value.
Severity
0 : Information
Explanation
An attempt has been made to set both CLUSTER and CLUSNL fields. One and only one of the fields may have a value, the other field must be blank. Change the value of one of the fields to blank and try the command again.
Response
None.
AMQ8444
The CLUSTER or CLUSNL fields must have a value.
Severity
0 : Information
Explanation
Both the CLUSTER and CLUSNL fields are blank. One and only one of the fields may be blank, the other field must be a value. Change one of the fields from blank to a value and try the command again.
Response
None.
AMQ8445
Program cannot open queue manager object.
Severity
30 : Severe error
Explanation
An attempt to open a queue manager object has failed.
Response
See the previously listed messages in the job log.
AMQ8446
Channel is currently active.
Severity
30 : Severe error
Explanation
The requested operation failed because the channel is currently active.
Response
See the previously listed messages in the job log.
AMQ8447
Requested operation on channel <insert_3> not valid for this channel type.
Severity
30 : Severe error
Explanation
The operation requested cannot be performed because channel <insert_3> is not of a suitable type. For example, only sender, server and cluster-sender channels can be resolved.
Response
Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8448
Channel <insert_3> is not running.
Severity
30 : Severe error
Explanation
A request to stop channel <insert_3> has failed because the channel is not running.
Response
Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8449
Queue <insert_3> inhibited for MQGET.
Severity
30 : Severe error
Explanation
An MQGET failed because the queue <insert_3> had been previously inhibited for MQGET.
Response
None.
AMQ8450
Display queue status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY QSTATUS command completed successfully. Details follow this message.
AMQ8451 (IBM i)
STATUS(*STOPPED) not allowed with CONNAME specified.
Severity
0 : Information
Explanation
The STATUS(*STOPPED) parameter is not allowed when specifying CONNAME on the ENDMQMCHL command.
Response
Remove the CONNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified connection name.
AMQ8452 (IBM i)
STATUS(*STOPPED) not allowed with RQMNAME specified.
Severity
0 : Information
Explanation
The STATUS(*STOPPED) parameter is not allowed when specifying RQMNAME on the ENDMQMCHL command.
Response
Remove the RQMNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified remote queue manager.
AMQ8453
The path <insert_3> is invalid
Severity
20 : Error
Explanation
You typed a path which was not syntactically correct for the operating system you are running IBM WebSphere MQ on.
Response
Determine the correct syntax of a path name for the operating system you are running IBM WebSphere MQ on and use this information to type in a valid path.
AMQ8454
Syntax error found in parameter <insert_3>.
Severity
20 : Error
Explanation
The data you entered for <insert_3> does not conform to the syntax rules laid down by IBM WebSphere MQ for this parameter.
Response
Carefully check the data entered for this parameter in conjunction with the IBM WebSphere MQ Command Reference to determine the cause of error.
AMQ8455
Password length error
Severity
20 : Error
Explanation
The password string length is rounded up by IBM WebSphere MQ to the nearest eight bytes. This rounding causes the total length of the SSLCRYP string to exceed its maximum.
Response
Decrease the size of the password, or of earlier fields in the SSLCRYP string.
AMQ8456
Conflicting parameters in command.
Severity
20 : Error
Explanation
The command contains parameters that cannot be used together.
Response
Refer to the IBM WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8457
IBM WebSphere MQ connection stopped.
Severity
0 : Information
Explanation
The STOP CONN command successfully stopped the connection that was specified.
Response
None.
AMQ8458
IBM WebSphere MQ connection not stopped.
Severity
0 : Information
Explanation
The STOP CONN command could not stop the connection that was specified.
Response
None.
AMQ8459
Not Found.
Severity
0 : Information
Explanation
You specified an identifier that was not found. Please try the command again and supply a valid identifier.
Response
None.
AMQ8460
Syntax error in connection identifier.
Severity
0 : Information
Explanation
You specified an invalid connection identifier. A valid connection identifier contains 16 hex characters, where all of the characters in the connection identifier should lie within the range 0-9, a-z or A-Z.
Response
Correct the connection identifier so that it conforms to the above specification.
AMQ8461
Connection identifier not found.
Severity
0 : Information
Explanation
You specified a connection identifier which is not associated with this queue manager.
Response
Correct the connection identifier so that it describes a connection identifier which is associated with this queue manager. Use the command DISPLAY CONN to identify potential connection identifiers to use with this command.
AMQ8462
The required parameter <insert_3> is missing.
Severity
20 : Error
Explanation
The command you entered requires the <insert_3> parameter, which has not been specified.
Response
Make sure you specify the missing required parameter.
AMQ8463
At least one of <insert_3> must be specified.
Severity
20 : Error
Explanation
At least one of the parameters <insert_3> must be specified.
Response
Make sure you specify the required parameters.
AMQ8464
IBM WebSphere MQ subscription <insert_3> not found.
Severity
30 : Severe error
Explanation
If the command entered was Change or Display, the subscription <insert_3> specified does not exist. If the command entered was Copy, the source subscription does not exist. If the command entered was Create, the system default MQ subscription does not exist.
Response
Correct the subscription name or subscription id specified and then try the command again. If you are creating a new subscription, either specify all parameters explicitly or ensure that the system default subscription, SYSTEM.DEFAULT.SUB, exists.
AMQ8465
The <insert_3> attribute cannot be modified for an existing Subscription.
Severity
20 : Error
Explanation
The Subscription could not be altered or replaced.
Response
The Subscription could not be altered or replaced. Check that the command only contains changable attributes.
AMQ8466
The remote queue <insert_3> could not be opened.
Severity
30 : Severe error
Explanation
The remote queue could not be opened..
Response
Check that the remote Queue is correctly defined on the remote Queue Manager.
AMQ8467
There was a syntax error in the hex string representing the bytes value of a keyword.
Severity
0 : Information
Explanation
The hex string that was entered was found to contain a syntax error. This error may occur for one of the following reasons:
  • The string was too long.
  • The string contained invalid hex characters.
Valid characters are 0-9, A-F and a-f. Hex strings with an odd number of characters will be prefixed with a zero, for example, DESTCORL(A) will be interpreted as DESTCORL(0A)
Response
None.
AMQ8468
DEST field must not be set when using DESTCLAS(MANAGED)
Severity
30 : Severe error
Explanation
An attempt to set both DESTCLAS(MANAGED) and DEST has been made. When using DESTCLAS(MANAGED) do not specify a destination. If a destination is required then DESTCLAS(PROVIDED) should be used.
Response
None.
AMQ8469
IBM WebSphere MQ subscription <insert_3> in use.
Severity
30 : Severe error
Explanation
The subscription <insert_3> specified is currently in use by another application.
Response
Ensure that no applications are using the specified subscription, then try the command again.
AMQ8470
The object <insert_3> is not a valid subscription destination.
Severity
30 : Severe error
Explanation
The object <insert_3> is not of a permitted type for a subscription destination.
Response
If using a QALIAS as a subscription destination object, ensure that its TARGTYPE attribute has the value of QUEUE.
AMQ8471
IBM WebSphere MQ topic string error
Severity
30 : Severe error
Explanation
The topic string (TOPICSTR) supplied was not valid
Response
Correct the topic string definition and try the command again.
AMQ8472
IBM WebSphere MQ topic string not found
Severity
30 : Severe error
Explanation
The topic string supplied does not exist in the topic tree
Response
Correct the topic string used and try the command again
AMQ8473
An IBM WebSphere MQ topic using the supplied topic string already exists
Severity
30 : Severe error
Explanation
The topic string supplied has been specified on a previously created topic object. At most, one topic object per topic string is permitted.
Response
If the topic string specified is incorrect, modify the topic string and retry the operation. Alternatively, if the previously created topic object is not required, delete that topic object first, then retry the operation.
AMQ8474
The required parameter SUB is invalid.
Severity
20 : Error
Explanation
The command you entered requires a valid SUB parameter.
Response
Make sure the required parameter is correct.
AMQ8475
Subscription already exists.
Severity
20 : Error
Explanation
The Subscription <insert_3> could not be created because it already exists.
Response
Check that the name is correct and try the command again specifying REPLACE, or delete the Subscription. Then try the command again.
AMQ8476
The required parameter <insert_3> is missing.
Severity
20 : Error
Explanation
The command you entered requires the <insert_3> parameter, which has not been specified.
Response
Make sure you specify the missing required parameter.
AMQ8477
The specified options are invalid.
Severity
40 : Stop Error
Explanation
The combination of options supplied for the command are invalid.
Response
Check the specified options and ensure they are correct.
AMQ8478
Standby queue manager.
Severity
40 : Stop Error
Explanation
The queue manager is a standby queue manager. You must use the primary instance of a queue manager to administer it.
Response
Re-issue the command on the primary instance of the queue manager.
AMQ8480
Subscription <insert_3> could not be created. The reason code from the MQSUB function call was <insert_1>.
Severity
20: Error
Explanation
During the attempt to create subscription name '<insert_3>', an error was detected. The reason for failure is <insert_1>. This reason code is returned from the MQSUB function call.
Response
Check the reason code in the IBM WebSphere MQ Messages manual, correct the underlying problem and then try the command again.
AMQ8482
Cluster topics inhibited due to PSCLUS(DISABLED).
Severity
20: Error
Explanation
The queue manager attribute PSCLUS has been set to DISABLED so clustered topics cannot be defined and existing topics can not be altered to set the CLUSTER attribute. Topic <insert_3> has not been created or altered on this system.
Response
If you need to enable publish/subscribe clustering, modify the PSCLUS attribute to ENABLED on all queue managers participating in the cluster.
AMQ8483
Unable to modify PSCLUS because cluster topic(s) exist.
Severity
20: Error
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 topic already exists, so the setting cannot be modified. The PSCLUS attribute remains unchanged.
Response
If you need to disable publish/subscribe activity within this cluster, first DELETE all cluster topic objects, then remodify the PSCLUS attribute.
AMQ8491
Timeout waiting for a reply from the Telemetry service.
Severity
0 : Information
Explanation
Timeout waiting for a reply from the Telemetry Service 'SYSTEM.MQXR.SERVICE'.
Response
Reduce the number of responses expected from the Telemetry Service by using a where clause.
AMQ8492
The number of responses has been limited to <insert_1>
Severity
0 : Information
Explanation
The number of responses has been limited to the MAXDEPTH of the ReplyToQueue 'SYSTEM.MQSC.REPLY.QUEUE'.
Response
Reduce the number of responses expected from the Telemetry Service by using a where clause, or increase the MAXDEPTH of the ReplyToQueue 'SYSTEM.MQSC.REPLY.QUEUE'.
AMQ8498
Starting MQSC for queue manager <insert_3>.
Severity
0 : Information
Explanation
The MQSC script contains <insert_1> commands.
Response
None.
AMQ8499
Usage: runmqsc [-e] [-v] [-w WaitTime [-x]] [QMgrName]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8499 (Tandem)
Usage: runmqsc [-e] [-v] [-w WaitTime] [-x] [-i In] [-o Out] QMgrName
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8500
IBM WebSphere MQ Display MQ Files
Severity
0 : Information
AMQ8501
Common services initialization failed with return code <insert_1>.
Severity
20 : Error
Explanation
A request by the command server to initialize common services failed with return code <insert_1>.
Response
None.
AMQ8502
Connect shared memory failed with return code <insert_1>.
Severity
20 : Error
Explanation
A request by the command server to connect shared memory failed with return code <insert_1>.
Response
None.
AMQ8503
Post event semaphore failed with return code <insert_1>.
Severity
20 : Error
Explanation
A request by the command server to post an event semaphore failed with return code <insert_1>.
Response
None.
AMQ8504
Command server MQINQ failed with reason code <insert_1>.
Severity
20 : Error
Explanation
An MQINQ request by the command server, for the IBM WebSphere MQ queue <insert_3>, failed with reason code <insert_1>.
Response
None.
AMQ8505
Reallocate memory failed with return code <insert_1>.
Severity
20 : Error
Explanation
A request by the command server to reallocate memory failed with return code <insert_1>.
Response
None.
AMQ8506
Command server MQGET failed with reason code <insert_1>.
Severity
20 : Error
Explanation
An MQGET request by the command server, for the IBM WebSphere MQ queue <insert_3>, failed with reason code <insert_1>.
Response
None.
AMQ8507
Command server MQPUT1 request for an undelivered message failed with reason code <insert_1>.
Severity
20 : Error
Explanation
An attempt by the command server to put a message to the dead-letter queue, using MQPUT1, failed with reason code <insert_1>. The MQDLH reason code was <insert_2>.
Response
None.
AMQ8508
Queue Manager Delete Object List failed with return code <insert_1>.
Severity
20 : Error
Explanation
A request by the command server to delete a queue manager object list failed with return code <insert_1>.
Response
None.
AMQ8509
Command server MQCLOSE reply-to queue failed with reason code <insert_1>.
Severity
20 : Error
Explanation
An MQCLOSE request by the command server for the reply-to queue failed with reason code <insert_1>.
Response
None.
AMQ8510
Command server queue is open, try again later.
Severity
30 : Severe error
AMQ8511
Usage: strmqcsv [QMgrName]
Severity
0 : Information
AMQ8512
Usage: endmqcsv [-c | -i] QMgrName
Severity
0 : Information
AMQ8513
Usage: dspmqcsv [QMgrName]
Severity
0 : Information
AMQ8514
No response received after <insert_1> seconds.
Severity
20 : Error
Explanation
The command server has not reported the status of running, to the start request, before the timeout of <insert_1> seconds was reached.
Response
None.
AMQ8515 (Tandem)
MQSeries Alter MQ Files
Severity
0 : Information
Explanation
Title for the altmqfls command.
Response
None.
AMQ8516 (Tandem)
MQSeries Clean Queue Manager
Severity
0 : Information
Explanation
Title for the cleanqm command.
Response
None.
AMQ8517 (Tandem)
The messages files are partitioned and cannot be moved.
Severity
0 : Information
Explanation
Partition Error from the altmqfls command.
Response
None.
AMQ8518
LOGGEREV is only valid when using a linear logging queue manager.
Severity
20 : Error
Explanation
The LOGGEREV attribute may only be set to ENABLED when the queue manager was created as a linear logging queue manager. For more information about logging, see Making sure that messages are not lost (logging).
Response
The system admistrator should only attempt to change the LOGGEREV queue manager attribute when the queue manager being administered was created as a linear logging queue manager.
AMQ8519
The topic object <insert_3> does not permit durable subscription.
Severity
30 : Severe error
Explanation
The topic object <insert_3> has been defined to disallow durable subscription.
Response
Ensure that the topic object to which you are creating a subscription allows durable subscription.
AMQ8520
The queue name supplied is not valid for DEFXMITQ.
Severity
20 : Error
Explanation
The specified queue is not allowed to be used as the default transmission queue because it is reserved for use exclusively by clustering.
Response
Change the value of DEFXMITQ, and try the command again.
AMQ8549
Total string length exceeds the maximum value of 999 characters.
Severity
0 : Information
Explanation
The total length of a channel exit string is 999 characters. The string list assigned to an MQSC keyword is longer than the maximum value of 999 characters permitted for that keyword.
Response
None.
AMQ8550
Display namelist details.
Severity
0 : Information
Explanation
The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message.
Response
None.
AMQ8551
IBM WebSphere MQ namelist changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ namelist <insert_5> changed.
Response
None.
AMQ8552
IBM WebSphere MQ namelist created.
Severity
0 : Information
Explanation
IBM WebSphere MQ namelist <insert_5> created.
Response
None.
AMQ8553
IBM WebSphere MQ namelist deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ namelist <insert_5> deleted.
Response
None.
AMQ8554
String List String Count Error.
Severity
0 : Information
Explanation
The number of strings within the stringlist is greater than the maximum number allowed for the keyword. Reduce the number of strings within the list and try the command again.
Response
None.
AMQ8555
String List String Length Error.
Severity
0 : Information
Explanation
A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword.
Response
None.
AMQ8556
RESUME QUEUE MANAGER accepted.
Severity
0 : Information
Explanation
The RESUME QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is now back in the cluster.
Response
None.
AMQ8557
SUSPEND QUEUE MANAGER accepted.
Severity
0 : Information
Explanation
The SUSPEND QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is leaving the cluster.
Response
None.
AMQ8558
REFRESH CLUSTER accepted.
Severity
0 : Information
Explanation
The REFRESH CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs refreshing.
Response
None.
AMQ8559
RESET CLUSTER accepted.
Severity
0 : Information
Explanation
The RESET CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs resetting.
Response
None.
AMQ8560
IBM WebSphere MQ security cache refreshed.
Severity
0 : Information
Explanation
The object authority manager security cache has been refreshed.
Response
None.
AMQ8561 (Tandem)
IBM WebSphere MQ for HP Integrity NonStop Server does not support this option.
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8561 (Windows)
Domain controller unavailable.
Severity
10 : Warning
Explanation
IBM WebSphere MQ was unable to contact the domain controller to obtain information for user <insert_3>.
Response
Ensure that a domain controller for the domain on which user <insert_3> is defined is available. Alternatively, if you are using a computer which is not currently connected to the network and have logged on using a domain user ID, you may wish to log on using a local user ID instead.
AMQ8562
The Java application failed to connect to the Queue Manager because the version of the native JNI library <insert_3> is inconsistant with the version of the IBM WebSphere MQ Queue Manager <insert_4>.
Severity
10 : Warning
Explanation
The native JNI library <insert_3> is out-of-date compared to the IBM WebSphere MQ Queue Manager <insert_4>
Response
Ensure that the Java library path points to the current version of the JNI library
AMQ8562 (Tandem)
Command line does not exist
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8563
IBM WebSphere MQ authentication information object created.
Severity
0 : Information
Explanation
IBM WebSphere MQ authentication information object <insert_3> created.
Response
None.
AMQ8564
IBM WebSphere MQ authentication information object deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ authentication information object <insert_3> deleted.
Response
None.
AMQ8565
Queue Status not found.
Severity
0 : Information
Explanation
Queue Status for the specified queue could not be found.
Response
None.
AMQ8566
Display authentication information details.
Severity
0 : Information
Explanation
The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message.
Response
None.
AMQ8567
IBM WebSphere MQ authentication information changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ authentication information <insert_3> changed.
Response
None.
AMQ8568
The native JNI library <insert_3> was not found.
Severity
10 : Warning
Explanation
The native JNI library <insert_3> could not be loaded because the library was not found.
Response
Ensure that the java library path points to the location of the JNI library.
AMQ8568 (IBM i)
No authinfo objects to display.
Severity
0 : Information
Explanation
There are no matching authinfo objects defined on this system.
Response
Using the DEFINE AUTHINFO command to create an authinfo object.
AMQ8569
Error in filter specification
Severity
0 : Information
Explanation
You specified an invalid filter. Check the WHERE statement and make sure that the operator is valid for the type of parameter, that the parameter can be filtered on, and that the value that you specified for the filter is valid for the type of attribute you are filtering on.
Response
None.
AMQ8570
Attribute value error in <insert_3>.
Severity
0 : Information
Explanation
The keyword <insert_3> contained a value that was not valid for this configuration. Please check the MQSC Command Reference to determine valid values for <insert_3>.
Response
None.
AMQ8571
<insert_1> authority not revoked from the <insert_2> group for reason 1111.
Severity
10 : Warning
Explanation
As part of queue manager migration an attempt was made to revoke <insert_1> authority from the <insert_2> group for the <insert_3> object. That attempt failed for reason 1111.
Response
An administrator must determine the cause of failure and then use the setmqaut command to manually revoke <insert_1> authority from the <insert_2> group for the <insert_3> object.
AMQ8572
Securing IBM WebSphere MQ objects against local groups may yield undesirable results.
Severity
10 : Warning
Explanation
A request was made to secure a IBM WebSphere MQ object against a local group in a Multi Instance queue manager environment. Access to these objects may be refused upon switch-over.
Response
An administrator should determine whether the request was intentional and use the setmqaut command to secure the IBM WebSphere MQ object against a corresponding domain group.
AMQ8574
Refreshing settings for primary installation <insert_1> (<insert_2>)
Severity
10 : Warning
Explanation
A request was issued to set installation <insert_1> as the primary installation however this installation is already set as the Primary Installation. The command continues and refreshes the settings which identify this installation as the primary installation.
Response
None.
AMQ8575
Unable to access installation task file <insert_1>.
Severity
20 : Error
Explanation
An attempt was made to access the IBM WebSphere MQ installation task file <insert_1> however the command issued was unable to access the file.
Response
Further messages might have been issued giving more details about the failure to access the file. Check that the file exists, and the access permissions are correct. Correct any errors and re-issue the command.
AMQ8576
<insert_1> (<insert_2>) set as the primary installation. You must restart the operating system to complete the update.
Severity
0 : Information
Explanation
All tasks required to set installation <insert_1> as the primary installation have been completed. If the installation was not already set as the primary installation then the installation configuration has also been updated to identify installation <insert_1> as the primary installation.

In order to ensure that the updates are visible machine-wide, a restart of the operating system is required.

Response
None.
AMQ8577
Failed to set <insert_1> (<insert_2>) as the primary installation.
Severity
20 : Error
Explanation
The command attempted to set installation <insert_1> as the primary installation but one or more of the tasks required to set the installation as the primary installation failed to complete successfully. Any updates made by the command have been undone.
Response
Further messages have been issued giving more details about the failure. Correct any identified errors and re-issue the command.
AMQ8578
Failed to refresh configuration for primary installation <insert_1> (<insert_2>).
Severity
20 : Error
Explanation
The command attempted to refresh the tasks required to set installation <insert_1> as the primary installation but one or more of the tasks failed to complete successfully. Installation <insert_1> is still set as the primary installation.
Response
Further messages have been issued giving more details about the failure. Correct any identified errors and re-issue the command.
AMQ8579
Primary installation cannot be changed from <insert_2> to <insert_1>.
Severity
20 : Error
Explanation
The command attempted to set installation <insert_1> as the primary installation but the operation could not be performed because installation <insert_2> is already set as the primary installation.
Response
In order to set installation <insert_1> as the primary installation you must first unset installation <insert_2> as the primary installation using the command setmqinst -x -n <insert_2>. You can then re-issue the command to set installation <insert_1> as the primary installation.
AMQ8580
Failed to unset <insert_1> (<insert_2>) as the primary installation.
Severity
20 : Error
Explanation
The command attempted to unset installation <insert_1> as the primary installation but one or more of the tasks required to unset the installation as the primary installation failed to complete successfully. The installation remains set as the primary installation.
Response
Further messages have been issued giving more details about the failure. Correct any identified errors and re-issue the command.
AMQ8581
<insert_1> (<insert_2>) is not currently set as the primary installation.
Severity
20 : Error
Explanation
The command attempted to unset installation <insert_1> as the primary installation but installation <insert_1> is not currently set as the primary installation.
Response
Verify the name of the installation supplied is correct and re-issue the command if necessary.
AMQ8582
<insert_1> (<insert_2>) has been unset as the primary installation.
Severity
0 : Information
Explanation
All tasks required to unset installation <insert_1> as the primary installation have been completed.
Response
None
AMQ8583
Installation details for <insert_3> location <insert_4> missing or corrupt.
Severity
20 : Error
Explanation
The command attempted to access the installation details for installation <insert_3> location <insert_4> but the installation details were not found or are corrupt.
Response
Use the dspmqinst command to verfiy the contents of the installation configuration file. If the entry is missing or corrupt use the crtmqinst command with the -r parameter to rebuild the configuration information for the installation.
AMQ8584
Insufficient permission to update installation configuration.
Severity
20 : Error
Explanation
An attempt was made to update the IBM WebSphere MQ installation configuration for Installation <insert_3> location <insert_4> but the request was rejected as the current user does not have sufficient authority to make the update.
Response
Issue the command from a user with sufficient authority to update the installation configuration.
AMQ8585
Invalid value specified for <insert_3> parameter.
Severity
20 : Error
Explanation
The value supplied for the <insert_3> parameter is invalid.
Response
Verify that the value supplied is
  • correctly specified
  • contains only valid characters
  • does not exceed the maxmium length for the parameter
AMQ8586
Usage: setmqinst (-n InstName | -p InstPath) (-i | -x | -d Text)
-d   Descriptive text.
-i   Set this installation as the primary installation.
-n   Installation name.
-p   Installation path.
-x   Unset this installation as the primary installation.
Severity
0 : Information
Explanation
This message shows correct usage.
Response
None.
AMQ8587
Note there are a number (1111) of other installations, use the -i parameter to display them.
Severity
0 : Information
Explanation
Response
None.
AMQ8588
No parameter was detected. The environment has been set for the installation from which the setmqenv command was issued.
Severity
10 : Warning
Explanation
The environment has been set for the installation that setmqenv originates from because setmqenv detected no parameters. If you specified parameters but these parameters have been ignored, it might be because the shell script you are using cannot pass parameters to a sourced script.
Response
If you intended to set up the environment for another installation but did not specify any parameters, issue the command again specifying the correct parameters. If you specified parameters for setmqenv but they have been ignored, use the setmqenv command from the installation you want to set up the environment for. Use the dspmqinst command to determine the path for other installations and use the dspmq command to determine the installation associated with a specific queue manager.
AMQ8589
Installation <insert_1> (<insert_2>) is implicitly primary.
Severity
10: Warning
Explanation
The command attempted to modify the primary installation <insert_1>, however this installation is implicitly primary and can only be made non-primary by uninstalling this installation.
Response
Verify that the installation <insert_1> is required, if so no other installation can be made primary.
AMQ8590
Installation <insert_1> (<insert_2>) is not installed.
Severity
20 : Error
Explanation
A command was issued specifying an installation which is not currently installed. The installation must be installed for this command to run.
Response
None.
AMQ8592
Queue manager <insert_1> is now associated with installation <insert_2>
Severity
0: Information
Explanation
A command was issued that has associated queue manager <insert_1> with installation <insert_2>. The queue manager is executed by this installation when it is next started.
Response
None
AMQ8593
Installation state for installation <insert_1> (<insert_2>) detected as invalid.
Severity
20 : Error
Explanation
An attempt was made to modify the state of installation <insert_1> (<insert_2>), however an error was detected related to the current state of this installation which prevented the change from occurring.
Response
Investigate recent changes to the system that might have invalidated installation <insert_1>. It might be necessary to contact your IBM support center, in which case a trace of the failing command might be required.
AMQ8595
The setmqenv command was not preceded by the source command.
Severity
20 : Error
Explanation
The command script containing setmqenv modifies the environment of the shell in which it is running. Because you did not precede setmqenv with the source command, it runs in a new shell and it modifies the environment in the new shell. When the setmqenv command ends, the new shell ends and control returns to the old shell. The old shell does not inherit changes to the environment from the new shell. The result is that the environment of the old shell, containing the setmqenv command does not change.
Response
Precede setmqenv with the source command. The combination of a dot followed by a space is a synonym for the source command; for example: 
. setmqenv -s
AMQ8597
This process can only use installation "<insert_4>".
Severity
10 : Error
Explanation
An MQ_long shared library "<insert_3>" was detected in this process before the first connection to a queue manager was made.
Linking applications to this shared library is deprecated. Applications that do so should be re-linked because it inhibits the use of multiple installations from within the application.
As a temporary work-around, this process is allowed to connect to queue managers associated with installation "<insert_4>". Attempting to connect to a queue manager associated with an installation other than "<insert_4>" will either fail with reason code MQRC_INSTALLATION_MISMATCH or MQRC_FASTPATH_NOT_AVAILABLE.
To obtain full multiple installation functionality, you must re-link this application, omitting -lmqmcs and -lmqmzse from the link step.
Response
Re-link your application, omitting the -lmqmcs and -lmqmzse options from the command line. When the application is re-linked without libmqmcs or libmqmzse, these restrictions are lifted and the application supports connecting to queue managers from installations other than "<insert_4>".
This message can be suppressed by setting the AMQ_NO_MQMCS_MSG environment variable to any value.
AMQ8601
IBM WebSphere MQ trigger monitor started.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor has been started.
Response
None.
AMQ8601 (IBM i)
IBM WebSphere MQ trigger monitor started.
Severity
0 : Information
Explanation
The trigger monitor has been started with initiation queue <insert_3>.
Response
None.
AMQ8602
IBM WebSphere MQ trigger monitor ended with exit code <insert_1>. If this value is anything other than zero, it indicates an error condition.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor has ended with exit code <insert_1>.
Response
Look for earlier error messages from the trigger monitor.
AMQ8603
Usage: runmqtrm [-m QMgrName] [-q InitQ]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8604
Use of IBM WebSphere MQ trigger monitor not authorized.
Severity
0 : Information
Explanation
The trigger monitor cannot be run due to lack of authority to the requested queue manager or initiation queue.
Response
Obtain the necessary authority from your security officer or IBM WebSphere MQ administrator. Then try the command again.
AMQ8605
Queue manager not available to the IBM WebSphere MQ trigger monitor
Severity
0 : Information
Explanation
The queue manager specified for the trigger monitor does not exist, or is not active.
Response
Check that you named the correct queue manager. Ask your systems administrator to start it, if it is not active. Then try the command again.
AMQ8606
Insufficient storage available for the IBM WebSphere MQ trigger monitor.
Severity
0 : Information
Explanation
There was insufficient storage available for the IBM WebSphere MQ trigger monitor to run.
Response
Free some storage and then try the command again.
AMQ8607
IBM WebSphere MQ trigger monitor connection failed.
Severity
0 : Information
Explanation
The trigger monitor's connection to the requested queue manager failed because of MQI reason code <insert_1> from MQCONN.
Response
Consult your systems administrator about the state of the queue manager.
AMQ8608
IBM WebSphere MQ trigger monitor connection broken.
Severity
0 : Information
Explanation
The connection to the queue manager failed while the trigger monitor was running. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
Response
Consult your systems administrator about the state of the queue manager.
AMQ8609
Initiation queue missing or wrong type
Severity
0 : Information
Explanation
The named initiation queue could not be found; or the queue type is not correct for an initiation queue.
Response
Check that the named queue exists, and is a local queue, or that the named queue is an alias for a local queue which exists.
AMQ8610
Initiation queue in use
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor could not open the initiation queue because the queue is open for exclusive use by another application.
Response
Wait until the queue is no longer in use, and try the command again.
AMQ8611
Initiation queue could not be opened.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor could not open the initiation queue; reason code <insert_1> was returned from MQOPEN.
Response
Consult your systems administrator.
AMQ8612
Waiting for a trigger message
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor is waiting for a message to arrive on the initiation queue.
Response
None.
AMQ8613
Initiation queue changed or deleted
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened.
Response
Retry the command.
AMQ8614
Initiation queue not enabled for input.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor cannot read from the initiation queue because input is not enabled.
Response
Ask your systems administrator to enable the queue for input.
AMQ8615
IBM WebSphere MQ trigger monitor failed to get message.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor failed because of MQI reason code <insert_1> from MQGET.
Response
Consult your systems administrator.
AMQ8616
End of application trigger.
Severity
0 : Information
Explanation
The action to trigger an application has been completed.
Response
None.
AMQ8617
Not a valid trigger message.
Severity
0 : Information
Explanation
The IBM WebSphere MQ trigger monitor received a message that is not recognized as a valid trigger message. If the queue manager has a dead letter queue, the trigger monitor attempts to put the message onto that queue. If that operation succeeds, the trigger monitor continues. Otherwise, the trigger monitor checks whether the Report options in the message descriptor allow the message to be discarded. If so, the message is discarded and the trigger monitor continues. If not, the operation is backed out and the trigger monitor ends.
Response
Investigate the reason why the trigger message was invalid. Check that you have started the trigger monitor to consume from the correct queue. The trigger monitor must be given the name of an initiation queue, not an application queue. If you have started it to consume from an application queue, this should be corrected.
AMQ8618
Error <insert_1> starting triggered application (errno <insert_2>).
Severity
0 : Information
Explanation
An error was detected when trying to start the application identified in a trigger message. The system() call returned <insert_1>. This can cause the value of errno to be set. In this case the value was <insert_2>.
Response
Check that the application the trigger monitor was trying to start is available. Refer to documentation for the system() call as to why the triggered application failed to start.
AMQ8619
Application type <insert_1> not supported.
Severity
0 : Information
Explanation
A trigger message was received which specifies application type <insert_1>; the trigger monitor does not support this type.
Response
Use an alternative trigger monitor for this initiation queue.
AMQ8620
Trigger message with warning <insert_1>
Severity
0 : Information
Explanation
The trigger monitor received a message with a warning. For example, it may have been truncated or it could not be converted to the trigger monitor's data representation. The reason code for the warning is <insert_1>.
Response
None.
AMQ8621
Usage: runmqtmc [-m QMgrName] [-q InitQ]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8622
Usage: CICS-Transaction-Name [MQTMC2 structure]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8623
IBM WebSphere MQ listener changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ listener <insert_3> changed.
Response
None.
AMQ8624
IBM WebSphere MQ service changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ service <insert_3> changed.
Response
None.
AMQ8625
IBM WebSphere MQ service created.
Severity
0 : Information
Explanation
IBM WebSphere MQ service <insert_3> created.
Response
None.
AMQ8626
IBM WebSphere MQ listener created.
Severity
0 : Information
Explanation
IBM WebSphere MQ listener <insert_3> created.
Response
None.
AMQ8627
IBM WebSphere MQ service object deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ service object <insert_3> deleted.
Response
None.
AMQ8628
IBM WebSphere MQ listener object deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ listener object <insert_3> deleted.
Response
None.
AMQ8629
Display service information details.
Severity
0 : Information
Explanation
The MQSC DISPLAY SERVICE command completed successfully. Details follow this message.
Response
None.
AMQ8630
Display listener information details.
Severity
0 : Information
Explanation
The MQSC DISPLAY LISTENER command completed successfully. Details follow this message.
Response
None.
AMQ8631
Display listener status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY LSSTATUS command completed successfully. Details follow this message.
AMQ8632
Display service status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY SVSTATUS command completed successfully. Details follow this message.
AMQ8633
Display topic details.
Severity
0 : Information
Explanation
The MQSC DISPLAY TOPIC command completed successfully. Details follow this message.
AMQ8634 (Tandem)
Message Overflow file could not be created for queue <insert_1>
Severity
0 : Information
Explanation
When attempting to create a file to hold a large message (a message larger than the message overflow threshold for the queue) the Queue Manager was unable to identify a unique filename for the file. This is probably caused by too many existing large messages for the queue, or for the queue manager as a whole if the default location for large message storage is being used.
Response
Use altmqfls to change the subvolume for large message storage for this Queue.
AMQ8635 (Tandem)
A Queue Server has ended normally.
Severity
0 : Information
Explanation
A Queue Server in CPU <insert_1> has ended normally. The process was named <insert_3>.
Response
None.
AMQ8636 (Tandem)
A Queue Server has ended with errors.
Severity
0 : Information
Explanation
A Queue Server in CPU <insert_1> has ended with errors. The process was named <insert_3>. The error return code reported by the Queue Server is <insert_2>. The Queue Server should be restarted automatically by the Queue Manager.
Response
Verify that the Queue Server has restarted correctly. Examine the Queue Manager FD subvolume for FFST files that may have been generated by the Queue Server. Use the process name to locate the relevant FFSTs. Attempt to reconstruct the chain of events or symptoms that lead to the failure and save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8637 (Tandem)
A Queue Server has detected a CPU failure.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> has detected that CPU <insert_1> failed. If there were components of the Queue Manager that were running in this CPU, they will now no longer be available, and application connections and channels may be dropped. The Queue Manager should continue to be available to new connections and channels. Any Status Server and Queue Server processes that were running in that CPU will be replaced in other available CPUs.
Response
None normally necessary. Applications could experience the reason code MQRC_CONNECTION_BROKEN (2009) from MQI operations in progress that used agent processes running in the failed CPUs, but they should be able to immediatelt re-connect successfully.
AMQ8638 (Tandem)
A Queue Server completed takeover processing.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> has completed processing that was associated with a prior takeover from a failed primary Queue Server process, or the failure of the CPU that it was running in. Normal processing resumes after this point, and the Queue Server is again in a state where it is resilient to any single point of failure.
Response
None normally necessary. This message is logged to provide positive confirmation that the takeover is complete.
AMQ8639 (Tandem)
A Queue Server processed expired messages.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> detected and processed <insert_1> messages that have expired.
Response
None normally necessary. This message is logged to provide information about the number of messages that expire for each Queue Server. If performance degradation is experienced for a particular Queue Server, verify that there are not an excessively large number of expired messages having to be processed by that Queue Server process.
AMQ8640 (Tandem)
Signal delivery timeout expired for an MQGET.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> failed to open and send a signal to the application process <insert_4> within the timeout allowed for signal delivery. The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been canceled by the Queue Server, but no notification can be delivered to the application.
Response
Manual intervention with the application may be necessary to ensure that it resumes normal processing. No further notification will be delivered to the application relating to the MQGET call that established the signal. The application can re-open the queue and re-issue the MQGET call to recover from this situation.
AMQ8641 (Tandem)
Signal delivery open error for an MQGET.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> failed to open the application process <insert_4> in order to deliver a signal IPC. The file system error number was <insert_1>. The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been canceled by the Queue Server, but no notification can be delivered to the application.
Response
Manual intervention with the application may be necessary to ensure that it resumes normal processing. No further notification will be delivered to the application relating to the MQGET call that established the signal. The application can re-open the queue and re-issue the MQGET call to recover from this situation.
AMQ8642 (Tandem)
Signal delivery error for an MQGET.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> failed to deliver a signal IPC to the application process <insert_4>. The file system error number was <insert_1>. The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been canceled by the Queue Server, but no notification can be delivered to the application.
Response
Manual intervention with the application may be necessary to ensure that it resumes normal processing. No further notification will be delivered to the application relating to the MQGET call that established the signal. The application can re-open the queue and re-issue the MQGET call to recover from this situation.
AMQ8643 (Tandem)
Signal delivery canceled for an MQGET.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> was required to terminate an MQGET with the MQGMO_SET_SIGNAL option before the specified Waitinterval expired but failed to open the application process <insert_4> in order to deliver a signal IPC. The MQGET with the MQGMO_SET_SIGNAL option issued by the application has been canceled by the Queue Server, but no notification can be delivered to the application.
Response
Manual intervention with the application may be necessary to ensure that it resumes normal processing. No further notification will be delivered to the application relating to the MQGET call that established the signal. The application can re-open the queue and re-issue the MQGET call to recover from this situation.
AMQ8644 (Tandem)
Queue Server memory threshold exceeded.
Severity
0 : Information
Explanation
The Queue Server process <insert_3> reached the threshold memory usage (<insert_1> bytes) at which unused queues are eligible for unloading to disk.
Response
Verify that the Queue Server is not overloaded with queues, or that messages are not building up unexpectedly on queues supported by the Queue Server.
AMQ8645 (Tandem)
Memory usage for Queue Server now below threshold.
Severity
0 : Information
Explanation
The memory usage of Queue Server process <insert_3> has now reduced to below the threshold (<insert_1> bytes) at which unused queues are unloaded to disk.
Response
None.
AMQ8646 (Tandem)
NonStop TM/MP reports transactions disabled
Severity
0 : Information
Explanation
The Queue Server <insert_3> has detected that the Compaq NonStop TM/MP has disabled transactions on the NSK system. The Queue Servers in the Queue Manager will no longer accept MQPUT or non-browse MQGET operations on Persistent messages, or any sync point operation. Attempts to perform operations on persistent messages will be rejected with teh reason code MQRC_SYNCPOINT_NOT_AVAILABLE.
Response
NonStop TM/MP is a critical resource for MQSeries. Immediately determine the cause using system utilities and rectify.
AMQ8647 (Tandem)
NonStop TM/MP reports transactions enabled
Severity
0 : Information
Explanation
The Queue Server <insert_3> has detected that the Compaq NonStop TM/MP transactions are enabled on the NSK system.
Response
No action is normally necessary. If transactions were previously disabled, this message indicates that the system has returned to normal operation.
AMQ8648 (Tandem)
A Queue Server has started
Severity
0 : Information
Explanation
A Queue Server in CPU <insert_1> has started. The process is named <insert_3>.
Response
None.
AMQ8649
Reset IBM WebSphere MQ Queue Manager accepted.
Severity
0 : Information
Explanation
The MQSC RESET QMGR command completed successfully. Details follow this message.
Response
None.
AMQ8650
Activity information unavailable.
Severity
0 : Information
Explanation
The DSPMQRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following:

1) One of the queue managers on the route did not support trace-route messaging.

2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details.

3) The report could not a find route back to the reply queue.

Response
Try and determine whether the activity information should have been available. Running the command with the 'outline' verbosity option (used with the -v flag) may be useful in determining where the message was when the activity information was generated.
AMQ8650 (IBM i)
Activity information unavailable.
Severity
0 : Information
Explanation
The DSPMQMRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following:

1) One of the queue managers on the route did not support trace-route messaging.

2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details.

3) The report could not a find route back to the reply queue.

Response
Try and determine whether the activity information should have been available. Running the command with DSPINF(*ALL) may be useful in determining where the message was when the activity information was generated.
AMQ8651
DSPMQRTE command has finished with errors.
Severity
0 : Information
Explanation
The DSPMQRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8651 (IBM i)
DSPMQMRTE command has finished with errors.
Severity
0 : Information
Explanation
The DSPMQMRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8652
DSPMQRTE command has finished.
Severity
0 : Information
Explanation
The DSPMQRTE command has finished processing your request and no execution errors were detected.
Response
None.
AMQ8652 (IBM i)
DSPMQMRTE command has finished.
Severity
0 : Information
Explanation
The DSPMQMRTE command has finished processing your request and no execution errors were detected.
Response
None.
AMQ8653
DSPMQRTE command started with options <insert_3>.
Severity
0 : Information
Explanation
You have started the DSPMQRTE command with command line options <insert_3> and the command is now processing your request.
Response
Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request.
AMQ8653 (IBM i)
DSPMQMRTE command started.
Severity
0 : Information
Explanation
You have started the DSPMQMRTE command and the command is now processing your request.
Response
Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request.
AMQ8654
Trace-route message arrived on queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager <insert_3>.
Response
None.
AMQ8654 (IBM i)
Trace-route message arrived on queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQMRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager <insert_3>.
Response
None.
AMQ8655
Trace-route message expired.
Severity
0 : Information
Explanation
The DSPMQRTE command has received confirmation that the trace-route message has expired.
Response
The expiry interval of trace-route messages generated by the DSPMQRTE command can be altered using the -xs option if this is required.
AMQ8655 (IBM i)
Trace-route message expired.
Severity
0 : Information
Explanation
The DSPMQMRTE command has received confirmation that the trace-route message has expired.
Response
The expiry interval of trace-route messages generated by the DSPMQMRTE command can be altered using the EXPIRY parameter if this is required.
AMQ8656
DSPMQRTE command received an exception report from queue manager <insert_4> with feedback <insert_1> <insert_3>.
Severity
0 : Information
Explanation
The DSPMQRTE command trace-route message caused an exception on queue manager <insert_4>. The Feedback field in the report was <insert_1> or <insert_3>.
Response
Use the feedback given to determine why the trace-route message caused the exception.
AMQ8656 (IBM i)
DSPMQMRTE command received an exception report from queue manager <insert_4> with feedback <insert_1> <insert_3>.
Severity
0 : Information
Explanation
The DSPMQMRTE command trace-route message caused an exception on queue manager <insert_4>. The Feedback field in the report was <insert_1> or <insert_3>.
Response
Use the feedback given to determine why the trace-route message caused the exception.
AMQ8657
DSPMQRTE command used <insert_3> 0x<insert_4>.
Severity
0 : Information
Explanation
You started the DSPMQRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had <insert_3> X<insert_4>.
Response
The <insert_3> can be used to retrieve responses to this trace-route request. Run the DSPMQRTE command again specifying this identifier with the -i flag and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager.
AMQ8657 (IBM i)
DSPMQMRTE command used <insert_3> 0x<insert_4>.
Severity
0 : Information
Explanation
You started the DSPMQMRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had <insert_3> X<insert_4>.
Response
The <insert_3> can be used to retrieve responses to this trace-route request. Run the DSPMQMRTE command again specifying this identifier for CRLLID and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager.
AMQ8658
DSPMQRTE command failed to put a message to the specified target.
Severity
0 : Information
Explanation
The request for the DSPMQRTE command to put a trace-route message was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put.
Response
Refer to previous messages issued by the command.
AMQ8658 (IBM i)
DSPMQMRTE command failed to put a message on the target queue.
Severity
0 : Information
Explanation
The request for the DSPMQMRTE command to put a trace-route message on the target queue was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put on the target queue.
Response
Refer to previous messages issued by the command.
AMQ8659
DSPMQRTE command successfully put a message on queue <insert_3>, queue manager <insert_4>.
Severity
0 : Information
Explanation
The request for the DSPMQRTE command to put a message on the target queue was successful. The target queue resolved to <insert_3> on queue manager <insert_4>.
Response
None.
AMQ8659 (IBM i)
DSPMQMRTE command successfully put a message on queue <insert_3>, queue manager <insert_4>.
Severity
0 : Information
Explanation
The request for the DSPMQMRTE command to put a message on the target queue was successful. The target queue resolved to <insert_3> on queue manager <insert_4>.
Response
None.
AMQ8660
DSPMQRTE command could not correctly order the following activities:
Severity
0 : Information
Explanation
The DSPMQRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly.
Response
Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly.
AMQ8660 (IBM i)
DSPMQMRTE command could not correctly order the following activities:
Severity
0 : Information
Explanation
The DSPMQMRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly.
Response
Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly.
AMQ8661
DSPMQRTE command will not put to queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying that the trace-route message must not be delivered to a local queue (-d yes was not specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQRTE command has chosen not to put the trace-route message to the target queue <insert_3> on queue manager <insert_4>.
Response
Determine whether it was expected that the target queue would resolve to a local queue.
AMQ8661 (IBM i)
DSPMQMRTE command will not put to queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying that the trace-route message must not be delivered to a local queue (DLVRMSG(*NO) was specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQMRTE command has chosen not to put the trace-route message to the target queue <insert_3> on queue manager <insert_4>.
Response
Determine whether it was expected that the target queue would resolve to a local queue.
AMQ8662
Trace-route message delivered on queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQRTE command has received confirmation of the successful delivery of the trace-route message on queue manager <insert_3> to a requesting application.
Response
None.
AMQ8662 (IBM i)
Trace-route message delivered on queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQMRTE command has received confirmation of the successful delivery of the trace-route message on queue manager <insert_3> to a requesting application.
Response
None.
AMQ8663
Client connection not supported in this environment.
Severity
20 : Error
Explanation
An attempt was made to connect to a queue manager using a client connection. However, client connections are not supported in your environment.
Response
Connect to the queue manager using a server connection.
AMQ8664
DSPMQRTE command could not connect to queue manager <insert_3>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying that it should connect to queue manager <insert_3>. The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8664 (IBM i)
DSPMQMRTE command could not connect to queue manager <insert_3>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying that it should connect to queue manager <insert_3>. The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8665
DSPMQRTE command was supplied an invalid CorrelId <insert_3>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying option -i with a CorrelId <insert_3> that was invalid. The CorrelId was either too long or not in the correct format.
Response
Refer to the command syntax, and then try the command again.
AMQ8665 (IBM i)
DSPMQMRTE command was supplied an invalid CorrelId <insert_3>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying CRLLID with a CorrelId <insert_3> that was invalid.
Response
Refer to the command syntax, and then try the command again.
AMQ8666
Queue <insert_3> on queue manager <insert_4>.
Severity
0 : Information
Explanation
The DSPMQRTE command trace-route message has been confirmed as having taken a route involving queue <insert_3> on queue manager <insert_4> in an attempt to reach the destination queue.
Response
Wait for subsequent messages which may indicate other queues or topics which the resultant message has been routed through.
AMQ8666 (IBM i)
Queue <insert_3> on queue manager <insert_4>.
Severity
0 : Information
Explanation
The DSPMQMRTE command trace-route message has been confirmed as having taken a route involving queue <insert_3> on queue manager <insert_4> in an attempt to reach the destination queue.
Response
Wait for subsequent messages which may indicate another queue which the message has been routed through.
AMQ8667
DSPMQRTE command could not open reply queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying reply queue <insert_3>. However the DSPMQRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error. If the -rq option was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE.
Response
Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command.
AMQ8667 (IBM i)
DSPMQMRTE command could not open reply queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying reply queue <insert_3>. However the DSPMQMRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error. If the RPLYQ parameter was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE.
Response
Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command.
AMQ8668
DSPMQRTE command could not open queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying queue <insert_3>, using the -q option. However the DSPMQRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command. Specify a queue, using the -q option, that can be opened and then retry the command.
AMQ8668 (IBM i)
DSPMQMRTE command could not open queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying queue <insert_3> for the QNAME parameter. However the DSPMQMRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command. Specify a queue, using the QNAME parameter, that can be opened and then retry the command.
AMQ8669
DSPMQRTE command failed to resolve queue manager <insert_3> on queue manager <insert_4>.
Severity
20 : Error
Explanation
The DSPMQRTE command attempted to resolve queue manager <insert_3> (supplied by the -qm option) on queue manager <insert_4> but the attempt failed. The queue specified by the -q option could not be opened.
Response
Ensure that queue manager <insert_3> can be resolved on queue manager <insert_4> or specify a different queue manager with the -qm option. Retry the command.
AMQ8669 (IBM i)
DSPMQMRTE command failed to resolve queue manager <insert_3> on queue manager <insert_4>.
Severity
20 : Error
Explanation
The DSPMQMRTE command attempted to resolve queue manager <insert_3> (supplied by the TGTMQM parameter) on queue manager <insert_4> but the attempt failed. The queue specified by the QNAME parameter could not be opened.
Response
Ensure that queue manager <insert_3> can be resolved on queue manager <insert_4> or specify a different queue manager with the TGTMQM parameter. Retry the command.
AMQ8670
Loading of server module <insert_3> failed.
Severity
20 : Error
Explanation
An attempt to dynamically load the server module <insert_3> failed. Typically this is because only the client modules are installed.
Response
Check which modules are installed and retry the command with the -c option specified if applicable.
AMQ8671
DSPMQRTE command was not supplied a reply queue when one was required.
Severity
20 : Error
Explanation
The DSPMQRTE command was expecting a reply queue specified by the -rq option but no reply queue was specified. Specifying a reply queue is mandatory if both the -n (no display) option and a response generating option (-ar or -ro [activity|coa|cod|exception|expiration]) is specified.
Response
Specify a reply queue and retry the command.
AMQ8672
DSPMQRTE command failed to get a message from queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
The DSPMQRTE command attempted to get a message from queue <insert_3>, queue manager <insert_4>, but the attempt failed. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8672 (IBM i)
DSPMQMRTE command failed to get a message from queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
The DSPMQMRTE command attempted to get a message from queue <insert_3>, queue manager <insert_4>, but the attempt failed. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8673
DSPMQRTE command was supplied option <insert_3> with an invalid object name <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying option <insert_3> with an object name <insert_4> that is invalid. In general, the names of IBM WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters:

1) Uppercase alphabetic characters (A through Z).

2) Lowercase alphabetic characters (a through z).

3) Numeric digits (0 through 9).

4) Period (.), forward slash (/), underscore (_), percent (%).

See the IBM WebSphere MQ System Administration documentation for further details and restrictions.

Response
Specify a valid object name and then try the command again.
AMQ8673 (IBM i)
DSPMQMRTE command was supplied with an invalid object name <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying an object name <insert_4> that is invalid. In general, the names of IBM WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters:

1) Uppercase alphabetic characters (A through Z).

2) Lowercase alphabetic characters (a through z).

3) Numeric digits (0 through 9).

4) Period (.), forward slash (/), underscore (_), percent (%).

See the IBM WebSphere MQ System Administration documentation for further details and restrictions.

Response
Specify a valid object name and then try the command again.
AMQ8674
DSPMQRTE command is now waiting for information to display.
Severity
0 : Information
Explanation
The DSPMQRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination.
Response
Wait for responses to be returned to the reply queue and for the information about the route to be displayed.
AMQ8674 (IBM i)
DSPMQMRTE command is now waiting for information to display.
Severity
0 : Information
Explanation
The DSPMQMRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination.
Response
Wait for responses to be returned to the reply queue and for the information about the route to be displayed.
AMQ8675
DSPMQRTE command was supplied an invalid option <insert_3>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying an option of <insert_3> that was not recognized. The command will end.
Response
Refer to the command syntax and retry the command.
AMQ8676
DSPMQRTE command was supplied an invalid combination of options.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying a combination of the options that is not valid. Only one of -ts or -q must be specified. The -i option cannot be specified with one or more of the following options: -ac, -ar, -d, -f, -l, -n, -o, -p, -qm, -ro, -rq, -rqm, -s, -t, -xs, -xp. The -n option cannot be specified with one or more of the following options: -b, -i, -v, -w. The -ar option can only be specified if the -ac option has also been specified. The -rqm option can only be specified if the -rq option has also been specified.
Response
Refer to the command documentation and then try the command again.
AMQ8677
DSPMQRTE command was supplied an option <insert_3> with conflicting values.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying values for option <insert_3> that conflict. At least two values were specified for the same option but they conflict with each other. The DSPMQRTE command will end.
Response
Refer to the command syntax and then try the command again.
AMQ8677 (IBM i)
DSPMQMRTE command was supplied a parameter with conflicting values.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying values that conflict. At least two values were specified for the same parameter but they conflict with each other. The DSPMQMRTE command will end.
Response
Refer to the command syntax and then try the command again.
AMQ8678
DSPMQRTE command was supplied option <insert_3> with an invalid value <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying an invalid option value. The <insert_4> value for option <insert_3> is either not recognized or of an incorrect format.
Response
Refer to the command syntax, and then try the command again.
AMQ8678 (IBM i)
DSPMQMRTE command was supplied an invalid value <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQMRTE command specifying an invalid parameter value. Value <insert_4> is either not recognized or of an incorrect format.
Response
Refer to the command syntax, and then try the command again.
AMQ8679
Persistent messages not allowed on reply queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
It was specified that the DSPMQRTE command should put a persistent trace-route message on the target queue (see the documentation for the -l option). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue.
Response
Ensure that the reply queue is not a temporary dynamic queue. Use the -rq option to specify the reply queue.
AMQ8679 (IBM i)
Persistent messages not allowed on reply queue <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
It was specified that the DSPMQMRTE command should put a persistent trace-route message on the target queue (see the documentation for the MSGPST parameter). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue.
Response
Ensure that the reply queue is not a temporary dynamic queue. Use the RPLYQ parameter to specify the reply queue.
AMQ8680
DSPMQRTE command failed to open queue manager <insert_3>.
Severity
20 : Error
Explanation
The DSPMQRTE command tried to open queue manager <insert_3> for inquire but the open failed. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8680 (IBM i)
DSPMQMRTE command failed to open queue manager <insert_3>.
Severity
20 : Error
Explanation
The DSPMQMRTE command tried to open queue manager <insert_3> for inquire but the open failed. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command.
AMQ8681
DSPMQRTE command has detected an error, reason <insert_1> <insert_3>.
Severity
20 : Error
Explanation
The DSPMQRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is <insert_1> or <insert_3>.
Response
See the IBM WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
AMQ8681 (IBM i)
DSPMQMRTE command has detected an error, reason <insert_1> <insert_3>.
Severity
20 : Error
Explanation
The DSPMQMRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is <insert_1> or <insert_3>.
Response
See the IBM WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
AMQ8682
Trace-route message processed by application <insert_3> on queue manager <insert_4>.
Severity
0 : Information
Explanation
The DSPMQRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager <insert_4> to application <insert_3> which processed the message.
Response
Determine if it was expected that this application would process the trace-route message.
AMQ8682 (IBM i)
Trace-route message processed by application <insert_3> on queue manager <insert_4>.
Severity
0 : Information
Explanation
The DSPMQMRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager <insert_4> to application <insert_3> which processed the message.
Response
Determine if it was expected that this application would process the trace-route message.
AMQ8683
Trace-route message reached the maximum activities limit of <insert_1>.
Severity
0 : Information
Explanation
The DSPMQRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to <insert_1>. The maximum activities limit is set using the -s option.
Response
Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit.
AMQ8683 (IBM i)
Trace-route message reached the maximum activities limit of <insert_1>.
Severity
0 : Information
Explanation
The DSPMQMRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to <insert_1>. The maximum activities limit is set using the MAXACTS parameter.
Response
Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit.
AMQ8684
Trace-route message reached trace-route incapable queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then the '-f all' option can be specified.
Response
Retry the command with different forwarding options, if appropriate.
AMQ8684 (IBM i)
Trace-route message reached trace-route incapable queue manager <insert_3>.
Severity
0 : Information
Explanation
The DSPMQMRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then FWDMSG(*ALL) can be specified.
Response
Retry the command with different forwarding options, if appropriate.
AMQ8685
Trace-route message rejected due to invalid forwarding options X<insert_1>.
Severity
20 : Error
Explanation
The DSPMQRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X<insert_1>.
Response
Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options.
AMQ8685 (IBM i)
Trace-route message rejected due to invalid forwarding options X<insert_1>.
Severity
20 : Error
Explanation
The DSPMQMRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X<insert_1>.
Response
Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options.
AMQ8686
Trace-route message rejected due to invalid delivery options X<insert_1>.
Severity
20 : Error
Explanation
The DSPMQRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X<insert_1>.
Response
Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options.
AMQ8686 (IBM i)
Trace-route message rejected due to invalid delivery options X<insert_1>.
Severity
20 : Error
Explanation
The DSPMQMRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X<insert_1>.
Response
Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options.
AMQ8687
Program ending.
Severity
0 : Information
Explanation
The program operation was interrupted by a SIGINT signal on UNIX systems or a CTRL+c/CTRL+BREAK signal on Windows systems. The program is now ending.
Response
Wait for the program to end.
AMQ8688
DSPMQRTE command has detected an unexpected error, reason <insert_1> <insert_3>.
Severity
20 : Error
Explanation
The DSPMQRTE command has detected an unexpected error during execution of your request. The reason for failure is <insert_1> or <insert_3>. The IBM WebSphere MQ error recording routine has been called.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8688 (IBM i)
DSPMQMRTE command has detected an unexpected error, reason <insert_1> <insert_3>.
Severity
20 : Error
Explanation
The DSPMQMRTE command has detected an unexpected error during execution of your request. The reason for failure is <insert_1> or <insert_3>. The IBM WebSphere MQ error recording routine has been called.
Response
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8689
Loading of client module <insert_3> failed.
Severity
20 : Error
Explanation
An attempt to dynamically load the client module <insert_3> failed. Typically this is because the client modules are not installed.
Response
Check which modules are installed and retry the command without the -c option specified, if applicable.
AMQ8690
IBM WebSphere MQ topic created.
Severity
0 : Information
Explanation
IBM WebSphere MQ topic <insert_3> created.
Response
None.
AMQ8691
IBM WebSphere MQ topic changed.
Severity
0 : Information
Explanation
IBM WebSphere MQ topic <insert_5> changed.
Response
None.
AMQ8692
IBM WebSphere MQ topic object deleted.
Severity
0 : Information
Explanation
IBM WebSphere MQ topic object <insert_3> deleted.
Response
None.
AMQ8694
DSPMQRTE command successfully put a message to topic string <insert_3>, queue manager <insert_4>.
Severity
0 : Information
Explanation
The request for the DSPMQRTE command to put a message was successful. The destination specified resolved to topic string <insert_3> on queue manager <insert_4>.
Response
None.
AMQ8695
Topic string <insert_3> on queue manager <insert_4>.
Severity
0 : Information
Explanation
The DSPMQRTE command trace-route message has been confirmed as having taken a route involving topic string <insert_3> on queue manager <insert_4>.
Response
Wait for subsequent messages which may indicate other queues or topics which the resultant messages have been routed through.
AMQ8696
DSPMQRTE command could not open topic string <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying topic string <insert_3>, using the -ts option. However the DSPMQRTE command could not successfully open that topic string on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command. Specify a topic string, using the -ts option, that can be opened and then retry the command.
AMQ8697
DSPMQRTE command could not open topic <insert_3>, queue manager <insert_4>.
Severity
20 : Error
Explanation
You started the DSPMQRTE command specifying topic <insert_3>, using the -to option. However the DSPMQRTE command could not successfully open a topic object of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Response
Refer to previous messages issued by the command. Specify a topic, using the -to option, that can be opened and then retry the command.
AMQ8698
Too many keywords have been specified.
Severity
0 : Information
Explanation
Too many keywords for the command have been specified.
Response
None
AMQ8701
Usage: rcdmqimg [-z] [-l] [-m QMgrName] -t ObjType [GenericObjName]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8702
Usage: rcrmqobj [-z] [-m QMgrName] -t ObjType [GenericObjName]
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8703
Usage: dspmqfls [-m QMgrName] [-t ObjType] GenericObjName
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8704 (Tandem)
Usage: altmqfls [--qmgr QMgrName] [--type ObjType] [--volume Volume] [-server ServerName] [--qsoptions options] [--msgofthresh Threshold] [--browse Bytes] [--meascount counter] [--qsize (primaryextent,secondaryextent, maxextents)] [--oflowsize (primaryextent,secondaryextent, maxextents)] ObjectName
Severity
0 : Information
Response
None.
AMQ8705
Display Queue Manager Status Details.
Severity
0 : Information
Explanation
The MQSC DISPLAY QMSTATUS command completed successfully. Details follow this message.
Response
None.
AMQ8706
Request to stop IBM WebSphere MQ Listener accepted.
Severity
0 : Information
Explanation
The channel listener program has been requested to stop. This command executes asynchronously so may complete after this message has been displayed.
Response
Further information on the progress of the request is available in the queue manager error log.
AMQ8707 (IBM i)
Start IBM WebSphere MQ DLQ Handler
Severity
0 : Information
AMQ8708
Dead-letter queue handler started to process INPUTQ(<insert_3>).
Severity
0 : Information
Explanation
The dead-letter queue handler (runmqdlq) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message.
Response
None.
AMQ8708 (IBM i)
Dead-letter queue handler started to process INPUTQ(<insert_3>).
Severity
0 : Information
Explanation
The dead-letter queue handler (STRMQMDLQ) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message.
Response
None.
AMQ8709
Dead-letter queue handler ending.
Severity
0 : Information
Explanation
The dead-letter queue handler (runmqdlq) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error.
Response
None.
AMQ8709 (IBM i)
Dead-letter queue handler ending.
Severity
0 : Information
Explanation
The dead-letter queue handler (STRMQMDLQ) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error.
Response
None.
AMQ8710
Usage: runmqdlq [QName[QMgrName]].
Severity
0 : Information
Explanation
Syntax for the usage of runmqdlq.
Response
None.
AMQ8711 (IBM i)
Job <insert_3> has terminated unexpectedly.
Severity
10 : Warning
Explanation
Execution of the command <insert_5> caused job <insert_3> to be started, but the job terminated unexpectedly.
Response
Consult the log for job <insert_3> to determine why it was terminated.
AMQ8712
PubSub is disabled for this queue manager.
Severity
40 : Stop Error
Explanation
The queue manager configuration inhibits any publication or subscription commands.
Response
Check the queue manager options and ensure they are correct.
AMQ8721
Dead-letter queue message not prefixed by a valid MQDLH.
Severity
10 : Warning
Explanation
The dead-letter queue handler (runmqdlq) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message.
Response
Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs.
AMQ8721 (IBM i)
Dead-letter queue message not prefixed by a valid MQDLH.
Severity
10 : Warning
Explanation
The dead-letter queue handler (STRMQMDLQ) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message.
Response
Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs.
AMQ8722
Dead-letter queue handler unable to put message: Rule <insert_1> Reason <insert_2>.
Severity
10 : Warning
Explanation
This message is produced by the dead-letter queue handler when it is requested to redirect a message to another queue but is unable to do so. If the reason that the redirect fails is the same as the reason the message was put to the dead-letter queue then it is assumed that no new error has occurred and no message is produced. The retry count for the message will be incremented and the dead-letter queue handler will continue.
Response
Investigate why the dead-letter queue handler was unable to put the message to the dead-letter queue. The line number of the rule used to determine the action for the message should be used to help identify to which queue the dead-letter queue handler attempted to PUT the message.
AMQ8723
Display pub/sub status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY PUBSUB command completed successfully. Details follow this message.
AMQ8724
Refresh IBM WebSphere MQ Queue Manager accepted.
Severity
0 : Information
Explanation
The MQSC REFRESH QMGR command completed successfully. Details follow this message.
Response
None.
AMQ8729
The listener could not be stopped at this time.
Severity
10 : Warning
Explanation
A request was made to stop a listener, however the listener could not be stopped at this time. Reasons why a listener could not be stopped are:

The listener has active channels and the communications protocol being used is LU 6.2, SPX or NETBIOS.

The listener has active channels and the communications protocol being used is TCP/IP and channel threads are restricted to run within the listener process.

Response
End the channels using the STOP CHANNEL command and reissue the request.
AMQ8730
Listener already active.
Severity
10 : Warning
Explanation
A request was made to start a listener, however the listener is already running and cannot be started.
Response
If you do not want the listener to be running, then use the STOP LISTENER command to stop the listener before reissuing the command.
AMQ8731
Listener not active.
Severity
10 : Warning
Explanation
A request was made to stop a listener, however the listener is not running.
Response
If the listener should be running then use the START LISTENER command to start the listener.
AMQ8732
Request to stop Service accepted.
Severity
0 : Information
Explanation
The Request to stop the Service has been accepted and is being processed.
Response
None.
AMQ8733
Request to start Service accepted.
Severity
0 : Information
Explanation
The Request to start the Service has been accepted and is being processed.
Response
None.
AMQ8734
Command failed - Program could not be started.
Severity
20 : Error
Explanation
The command requested was unsuccessful because the program which was defined to be run to complete the action could not be started.

Reasons why the program could not be started are

The program does not exist at the specified location.

The WebSphere MQ user does not have sufficient access to execute the program.

If STDOUT or STDERR are defined for the program, the IBM WebSphere MQ user does not have sufficient access to the locations specified.

Response
Check the Queue Manager error logs for further details on the cause of the failure and correct before reissuing the command.
AMQ8735
Command failed - Access denied.
Severity
20 : Error
Explanation
The command requested was unsuccessful because access was denied attempting to execuete the program defined to run.
Response
Examine the definition of the object and ensure that the path to program file is correct. If the defined path is correct ensure that the program exists at the location specified and that the WebSphere MQ user has access to execute the program.
AMQ8737
Service already active.
Severity
10 : Warning
Explanation
A request was made to start a service, however the service is already running and cannot be started.
Response
If you do not want the service to be running, then use the STOP SERVICE command to stop the service before reissuing the command. If the intention is to allow more than one instance of s service to run, then the service definition may be altered to be of SERVTYPE(COMMAND) which allows more than one instance of the service to be executed concurrently, however status of services of type COMMAND is not available from the SVSTAUS command.
AMQ8738
Service not active.
Severity
10 : Warning
Explanation
A request was made to stop a service, however the service is not running.
Response
If the service should be running then use the START SERVICE command to start the service.
AMQ8739
Stop cannot be executed for service with blank STOPCMD.
Severity
20 : Error
Explanation
A request was made to STOP a service, however the service has no Stop Command defined so no action could be taken.
Response
Examine the definition of the service and if necessary update the definition of the service to include the command to run when STOP is issued. For services of type 'SERVER' the command to run when STOP is executed is stored when the service is started so any alteration to the service definition will have no effect until the service is restarted following the update.
AMQ8740
Start cannot be executed for service with blank STARTCMD.
Severity
20 : Error
Explanation
A request was made to START a service, however the service has no Start Command defined so no action could be taken.
Response
Examine the definition of the service and if necessary update the definition of the service to include the command to run when START is issued.
AMQ8741
Unable to connect to queue manager.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not connect to queue manager <insert_3>. This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code (<insert_1>) and the reason (<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8741 (IBM i)
Unable to connect to queue manager.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not connect to queue manager <insert_3>. This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code (<insert_1>) and the reason (<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8742
Unable to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8742 (IBM i)
Unable to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8743
Unable to inquire on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8743 (IBM i)
Unable to inquire on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8744
Unable to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8744 (IBM i)
Unable to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8745
Unable to open dead-letter queue for browse.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not open the dead-letter queue <insert_3> for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(<insert_1>) and the reason(<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8745 (IBM i)
Unable to open dead-letter queue for browse.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue <insert_3> for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(<insert_1>) and the reason(<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8746
Unable to close dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8746 (IBM i)
Unable to close dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8747
Integer parameter outside permissible range.
Severity
20 : Error
Explanation
The integer parameter (<insert_2>) supplied to the dead-letter handler was outside of the valid range for <insert_3> on line <insert_1>.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8748
Unable to get message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8748 (IBM i)
Unable to get message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8749
Unable to commit/backout action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8749 (IBM i)
Unable to commit/backout action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Take appropriate action based upon the completion code and reason.
AMQ8750
No valid input provided to runmqdlq.
Severity
20 : Error
Explanation
Either no input was provided to runmqdlq, or the input to runmqdlq contained no valid message templates. If input was provided to runmqdlq but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8750 (IBM i)
No valid input provided to STRMQMDLQ.
Severity
20 : Error
Explanation
Either no input was provided to STRMQMDLQ, or the input to STRMQMDLQ contained no valid message templates. If input was provided to STRMQMDLQ but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8751
Unable to obtain private storage.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages.
Response
Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists save any generated output files and use either the IBM WebSphere MQ support web page, or the IBM support assistant at the IBM SupportAssistant web page, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8751 (IBM i)
Unable to obtain private storage.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages.
Response
Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists save any generated output files and use either the IBM WebSphere MQ support web page, or the IBM support assistant at the IBM SupportAssistant web page, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8752
Parameter(<insert_3>) exceeds maximum length on line <insert_1>.
Severity
20 : Error
Explanation
A parameter supplied as input to the dead-letter handler exceeded the maximum length for parameters of that type.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8753
Duplicate parameter(<insert_3>) found on line <insert_1>.
Severity
20 : Error
Explanation
Two or more parameters of the same type were supplied on a single input line to the dead-letter queue handler.
Response
Correct the input and restart the dead-letter queue handler.
AMQ8754
Display topic status details.
Severity
0 : Information
Explanation
The MQSC DISPLAY TPSTATUS command completed successfully. Details follow this message.
AMQ8755
IBM WebSphere MQ topicstr cleared successfully.
Severity
0 : Information
Explanation
All messages on topicstr have been deleted.
AMQ8756
Error detected releasing private storage.
Severity
20 : Error
Explanation
The dead-letter queue handler (runmqdlq) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends.
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.
AMQ8756 (IBM i)
Error detected releasing private storage.
Severity
20 : Error
Explanation
The dead-letter queue handler (STRMQMDLQ) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends.
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.
AMQ8757
Integer parameter(<insert_3>) outside permissible range on line <insert_1>.
Severity
20 : Error
Explanation
An integer supplied as input to the dead-letter handler was outside of the valid range of integers supported by the dead-letter queue handler.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8758
<insert_1> errors detected in input to runmqdlq.
Severity
20 : Error
Explanation
One or more errors have been detected in the input to the dead-letter queue handler(runmqdlq). Error messages will have been generated for each of these errors. The dead-letter queue handler ends.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8758 (IBM i)
<insert_1> errors detected in input to STRMQMDLQ.
Severity
20 : Error
Explanation
One or more errors have been detected in the input to the dead-letter queue handler(STRMQMDLQ). Error messages will have been generated for each of these errors. The dead-letter queue handler ends.
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8759
Invalid combination of parameters to dead-letter queue handler on line <insert_1>.
Severity
20 : Error
Explanation
An invalid combination of input parameters has been supplied to the dead-letter queue handler. Possible causes are: no ACTION specified, ACTION(FWD) but no FWDQ specified, HEADER(YES|NO) specified without ACTION(FWD).
Response
Correct the input data and restart the dead-letter queue handler.
AMQ8760
Unexpected failure while initializing process: Reason = <insert_1>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8760 (IBM i)
Unexpected failure while initializing process: Reason = <insert_1>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8761
Unexpected failure while connecting to queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8761 (IBM i)
Unexpected failure while connecting to queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8762
Unexpected error while attempting to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8762 (IBM i)
Unexpected error while attempting to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8763
Unexpected error while inquiring on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead letter queue handler (runmqdlq) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8763 (IBM i)
Unexpected error while inquiring on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead letter queue handler (STRMQMDLQ) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8764
Unexpected error while attempting to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8764 (IBM i)
Unexpected error while attempting to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8765
Unexpected failure while opening dead-letter queue for browse: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8765 (IBM i)
Unexpected failure while opening dead-letter queue for browse: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8766
Unexpected error while closing dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8766 (IBM i)
Unexpected error while closing dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8767
Unexpected error while getting message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8767 (IBM i)
Unexpected error while getting message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8768
Unexpected error committing/backing out action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8768 (IBM i)
Unexpected error committing/backing out action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8769
Unable to disconnect from queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (runmqdlq) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8769 (IBM i)
Unable to disconnect from queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : Severe error
Explanation
The dead-letter queue handler (STRMQMDLQ) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Response
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8770 (IBM)
Cannot open <insert_3> for command <insert_5>.
Severity
40 : Stop Error
Explanation
The <insert_5> command failed to open <insert_3> for IBM WebSphere MQ processing.
Response
Check that the intended file or member exists, and was specified correctly. Correct the specification or create the object and try the operation again.
AMQ8771 (DEC)
OpenVMS Cluster Failover Set Configuration and State.
Severity
0 : Information
AMQ8772 (DEC)
Queue Manager Name: <insert_3> Sequence No: <insert_1>
Severity
0 : Information
AMQ8773 (DEC)
TCP/IP Address: <insert_3> Listener Port Number : <insert_4>
Severity
0 : Information
AMQ8774 (DEC)
Queue Manager state in failover set: STARTED
Severity
0 : Information
AMQ8775 (DEC)
Queue Manager state in failover set: STOPPED
Severity
0 : Information
AMQ8776 (DEC)
Node specific configuration and state
Severity
0 : Information
AMQ8777 (DEC)
Node name: <insert_3> Priority: <insert_1> TCP/IP Interface: <insert_4>
Severity
0 : Information
AMQ8778 (DEC)
Queue Manager state : RUNNING
Severity
0 : Information
AMQ8779 (DEC)
Queue Manager state : AVAILABLE
Severity
0 : Information
AMQ8780 (DEC)
Queue Manager state : EXCLUDED
Severity
0 : Information
AMQ8781 (DEC)
Failover Monitor state: STARTED
Severity
0 : Information
AMQ8782 (DEC)
Failover Monitor state: STOPPED
Severity
0 : Information
AMQ8783 (DEC)
Failover Monitor state: WATCHING
Severity
0 : Information
AMQ8784 (DEC)
Node <insert_3> is not in the Failover Set configuration file
Severity
20 : Error
AMQ8785 (DEC)
There are no Failover Monitors started for Queue Manager: <insert_3>
Severity
20 : Error
AMQ8786 (DEC)
Failover set update operation in progress
Severity
10 : Warning
AMQ8787 (DEC)
Usage:

Start the queue manager in the failover set

failover -m <queue manager> [-n <node name>] -s

End the queue manager in the failover set

failover -m <queue manager> -e

Failover the running queue manager to another node

failover -m <queue manager> [-n <node name>] -f

Stop a failover monitor on a node

failover -m <queue manager> -n <node name> -h

Query the state of the queue manager

failover -m <queue manager> -q

Set the symbols MQS$QMGR_NODE, MQS$AVAILABLE_NODES and MQS$MONITOR_NODES

failover -m <queue manager> -l

Change the state of the failover set

failover -m <queue manager> -c -cluster stopped|started

Change the state of the queue manager on a node

failover -m <queue manager> -n <node name> -c -qmgr available|running|excluded

Change the state of the monitor on a node

failover -m <queue manager> -n <node name> -c -monitor stopped|started|watcher

Clear the update in progress flag

failover -m <queue manager> -u

Severity
0 : Information
AMQ8788 (DEC)
Usage: failover_monitor -m <queue manager> [-d]
Severity
0 : Information
AMQ8789 (DEC)
Error opening failover initialisation file FAILOVER.INI
Severity
20 : Error
AMQ8790 (DEC)
Error in the format of the initialisation file FAILOVER.INI
Severity
20 : Error
AMQ8791 (DEC)
No node available on which to start the queue manager
Severity
20 : Error
AMQ8792 (DEC)
Operation not allowed; Use a Failover command
Severity
20 : Error
AMQ8793 (DEC)
The ending of the queue manager was forced
Severity
10 : Warning
AMQ8794 (DEC)
The ending of the queue manager timed out before completion
Severity
20 : Error
AMQ8795 (DEC)
End Queue Manager Time Out: <insert_1>
Severity
0 : Information
AMQ8796 (DEC)
There is a Failover Monitor already running on node: <insert_3>
Severity
20 : Error
AMQ8797 (Tandem)
Cannot move queue files to <insert_3>.
Severity
0 : Information
Explanation
The MQSeries altmqfls utility cannot move the specified queue files to volume <insert_3>.
Response
Verify that the queue files are not already on volume <insert_3> using the dspmqfls utility. Verify that volume <insert_3> does not already contain queue files for this or any other queue manager in the same subvolume as used by this queue manager.
AMQ8798 (Tandem)
Queue files moved to <insert_3>.
Severity
0 : Information
Explanation
The MQSeries altmqfls utility has sucessfully moved the specified queue files to volume <insert_3>.
Response
None.
AMQ8801 (Tandem)
EC Boss <insert_3> for Queue Manager <insert_4> is initializing.
Severity
30 : Severe error
Explanation
The EC Boss for Queue Manager <insert_4> is beginning the startup sequence. The process name of the EC Boss is <insert_3>.
AMQ8802 (Tandem)
EC Boss <insert_3> for Queue Manager <insert_4> initialization complete.
Severity
30 : Severe error
Explanation
The EC Boss for Queue Manager <insert_4> has completed process startup actions. The process name of the EC Boss is <insert_3>.
AMQ8803 (Tandem)
EC Boss <insert_3> for Queue Manager <insert_4> controlled shutdown initiated.
Severity
30 : Severe error
Explanation
The EC Boss for Queue Manager <insert_4> has entered the controlled shutdown state. The Queue Manager will not accept new work, and once operations in progress have completed, connections will be terminated. When there are no more connections, the Queue Manager will end.
AMQ8804 (Tandem)
EC Boss <insert_3> for Queue Manager <insert_4> quiesce shutdown initiated.
Severity
30 : Severe error
Explanation
The EC Boss for Queue Manager <insert_4> has entered the quiesce shutdown state. The Queue Manager will not accept new work, but will allow existing connections to complete before ending.
AMQ8805 (Tandem)
EC Boss <insert_3> for Queue Manager <insert_4> immediate shutdown initiated.
Severity
30 : Severe error
Explanation
The EC Boss for Queue Manager <insert_4> has entered the immediate shutdown state. Any current connections are terminated and the Queue Manager will end immediately.
AMQ8806 (Tandem)
EC / EC Boss <insert_3> for Queue Manager <insert_4> cannot access file <insert_5>
Severity
40 : Stop Error
Explanation
An EC, or the EC Boss (process name <insert_3>) for Queue Manager <insert_4> has not been able to access the file named <insert_5>. This file is critical to the operation of the Queue Manager, and the Queue Manager will not start properly until the problem is corrected.
Response
End the Queue Manager and check the existence or file attributes of the file named <insert_5>. Verify that the file exists, and has the appropriate file security and type attributes, correct the problem and restart the Queue Manager.
AMQ8807 (Tandem)
EC / EC Boss <insert_3> for Queue Manager <insert_4> obtained file error <insert_1> on file <insert_5>
Severity
40 : Stop Error
Explanation
An EC, or the EC Boss (process name <insert_3>) for Queue Manager <insert_4> obtained Tandem file error <insert_1> while attempting an IO operation to file <insert_5>. The successful completion of the IO operation may be critical to the correct operation of the Queue Manager, and the Queue Manager may not operate properly until the problem is corrected.
Response
End the Queue Manager and check the file attributes of the file named <insert_5>. Verify that the file has the appropriate file security and type attributes, correct the problem and restart the Queue Manager.
AMQ8808 (Tandem)
Incorrect Queue Manager name <insert_4> supplied to process <insert_4>
Severity
40 : Stop Error
Explanation
A Queue Manager process (process name <insert_3>) was supplied with an invalid or non-existent Queue Manager name, <insert_4>. The initialization of the process failed as a result.
Response
End the Queue Manager and check the queue manager name that is being used in the configuration databases. After correcting the problem, restart the Queue Manager.
AMQ8809 (Tandem)
Queue Manager <insert_4> started.
Severity
30 : Severe error
Explanation
The EC Boss has reported that the Queue Manager named <insert_4> has entered the "started" state.
AMQ8810 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> is initializing.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has started and is performing process initialization.
AMQ8811 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> has completed initialization.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has completed process initialization.
AMQ8812 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> has started controlled shutdown.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has reported that a controlled shutdown has started. The EC will wait for all currently running agents to end before performing the final shutdown actions.
AMQ8813 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> has started quiesce shutdown.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has reported that a quiesce shutdown has started. The EC will wait for all currently running agents to end before performing the final shutdown actions.
AMQ8814 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> has started immediate shutdown.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has reported that an immediate shutdown has started. The EC will terminate immediately, without waiting for currently running agents to end.
AMQ8815 (Tandem)
EC number <insert_1>, process name <insert_3>, for Queue Manager <insert_4> has shutdown.
Severity
30 : Severe error
Explanation
An EC in the Queue Manager named <insert_4> has reported that it has completed shutdown actions. When all ECs in the Queue Manager have completed shutdown actions, the Queue Manager will end.
AMQ8816 (Tandem)
Queue Manager <insert_4> has started, though only <insert_1> of <insert_2> ECs have registered.
Severity
30 : Severe error
Explanation
The Queue Manager named <insert_4> has entered the started state, and will now accept connections. However, only <insert_1> of the expected <insert_2> ECs have registered with the EC Boss. The Queue manager's load balancing and overall performance will be adversly affected, however it will still be able to service connections.
Response
Examine the logs to determine the cause of the failure to start the missing ECs. End the Queue Manager, and rectify the problem if possible. Restart the Queue Manager and ensure that the Queue Manager starts correctly.
AMQ8817 (Tandem)
Process <insert_3> in Queue Manager <insert_4> cannot process a request due to a resource problem.
Severity
40 : Stop Error
Explanation
The process named <insert_3> has failed to process a request from another process due to a failure to allocate a resource, such as memory, or disk space. Depending upon the criticality of the resource itself, this may cause further errors, or the failure of certain Queue Manager components.
Response
Examine the logs to determine the cause of the failure. If there are resource problems that can be corrected, correct them and attempt the operation again.
AMQ8818 (Tandem)
EC Boss in Queue Manager <insert_4> rejected a registration from process <insert_3>.
Severity
40 : Stop Error
Explanation
The process named <insert_3> attempted to register with the EC Boss. The EC Boss detected a problem with the registration information and rejected the attempt.
Response
Examine the logs to determine further information about the problem. Determine the identity of the process, and verify that the process is an EC. If the process is not an EC, or cannot be identified, then a security threat may be present.
AMQ8819 (Tandem)
EC number <insert_1> registered with the EC Boss in Queue Manager <insert_4>.
Severity
40 : Stop Error
Explanation
EC number <insert_1> has registered with the EC Boss. When all the expected ECs in a Queue Manager have registered, the Queue Manager enters the started state.
AMQ8820 (Tandem)
An unknown message received by process <insert_3> in Queue Manager <insert_4> from process <insert_5> has been rejected.
Severity
40 : Stop Error
Explanation
The process <insert_3> has received and rejected a message that is either not of the correct format, or from an unknown source.
Response
Examine the log to see if further information is available. Try to identify the process to ensure that a security threat is not present.
AMQ8821 (Tandem)
The EC Boss in Queue Manager <insert_4> detected the failure of EC number <insert_1>.
Severity
40 : Stop Error
Explanation
The EC Boss has detected that EC number <insert_1> has terminated unexpectedly. If the maximum number of restarts performed on this EC has not already been exceeded, PATHWAY will attempt to restart the EC.
Response
Examine the log to see if further information is available.
AMQ8822
Invalid response, please re-enter (y or n):
Severity
0 : Information
Response
None.
AMQ8823 (Tandem)
Process <insert_3> in Queue Manager <insert_4> received and rejected a message from an unknown source, <insert_5>.
Severity
40 : Stop Error
Explanation
A process in Queue Manager <insert_4> received a message from a source that is not authorized or not registered to communicate with the Queue Manager. The process is identified by <insert_5>. The process that received the message is identified by <insert_3>.
Response
Examine the log to see if further information is available on the identity of the source of the message. Try to determine the identity of the sender and verify that no security threat is present.
AMQ8824 (Tandem)
The EC Boss in Queue Manager <insert_4> detected an inconsistency in the context data for agent process <insert_3>.
Severity
40 : Stop Error
Explanation
The EC Boss found that the information it had previously held about the agent <insert_3> is not consistent with new information.
Response
Examine the log to see if further information is available relating to process <insert_3>.
AMQ8825 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> detected the failure of the EC Boss.
Severity
40 : Stop Error
Explanation
An EC detected that the EC Boss for the Queue Manager has failed. If the maximum number of restarts for the EC Boss has not been exceeded, PATHWAY will attempt to restart the EC Boss.
Response
Examine the log to see if further information is available relating to the failure of the EC Boss. If the problem persists, end the Queue Manager, correct the problem and restart. If the problem cannot be identified as a configuration problem, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8826 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> detected the failure of an <insert_5> agent servicing <insert_3>.
Severity
40 : Stop Error
Explanation
An EC detected that an <insert_5> agent process for <insert_3> has failed. If the maximum number of restarts of agent processes has not already been exceeded, the EC will attempt to restart the agent process when it is required.
Response
Examine the log to see if further information is available relating to the failure of the agent process. If the problem persists, end the Queue Manager, correct the problem and restart. If the problem cannot be identified as a configuration problem, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8827 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to communicate with the EC Boss.
Severity
40 : Stop Error
Explanation
An EC attempted to communicate with the EC Boss, but the attempt failed. The failure to communicate is interpreted by the EC as EC Boss failure.
Response
Examine the log to see if further information is available relating to the failure to communicate with the EC Boss. If the problem persists, end the Queue Manager, correct the problem and restart. If the problem cannot be identified as a configuration problem, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8828 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to communicate with <insert_5> agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC attempted to communicate with an agent process, but the attempt failed. The failure to communicate is interpreted by the EC as agent failure. Depending upon various factors, the EC may attempt to restart the agent.
Response
Examine the log to see if further information is available relating to the failure to communicate with the agent. If the problem persists, end the Queue Manager, correct the problem and restart. If the problem cannot be identified as a configuration problem, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8829 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to start an <insert_5> agent.
Severity
40 : Stop Error
Explanation
An EC attempted to create an agent process, but the attempt failed. If the maximum number of agent restarts has not already been exceeded, the EC will attempt to restart the agent process.
Response
Examine the log to see if further information is available relating to the failure to start the agent. If the problem persists, end the Queue Manager, correct the problem and restart. If the problem cannot be identified as a configuration problem, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or thehttps://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ8830 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to service a Stop Channel request for channel <insert_5>.
Severity
40 : Stop Error
Explanation
An EC attempted to process a Stop Channel request, but the attempt failed. The failure will be relayed back to the original requestor via the EC Boss.
Response
Examine the log to see if further information is available relating to the failure to service the Stop Channel request. The originator of the Stop Channel request will be informed of the failure, togther with the reason for the failure.
AMQ8831 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to service an agent "done" request from agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC attempted to process an agent "done" request, but the attempt failed. An agent "done" request indicates that agent process <insert_3> has completed its work and is asking the EC whether to terminate, or to go idle. For some reason, the EC failed to process the request. The EC will terminate the agent process.
Response
Examine the log to see if further information is available relating to the failure to service the agent "done" request.
AMQ8832 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> created an idle <insert_5> agent process <insert_3>.
Severity
30 : Severe error
Explanation
An EC successfully created an idle agent.
AMQ8833 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to activate <insert_5> agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC failed to activate an idle agent in order to service a connection, or start channel request. The request could not be satisfied by the EC. The EC returns a failure completion and reason code to the originator of the request.
Response
Examine the log to see if further information is available relating to the failure to activate the agent.
AMQ8834 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to deactivate <insert_5> agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC failed to deactivate an active agent after the agent indicated that it had completed processing a connection or channel.
Response
Examine the log to see if further information is available relating to the failure to deactivate the agent.
AMQ8835 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> destroyed idle <insert_5> agent process <insert_3>.
Severity
30 : Severe error
Explanation
An EC successfully destroyed an idle agent process. The EC normally performs this operation as a result of managing the pool of idle agents. Agents that have been used more than a certain (configurable) number of times are destroyed and a fresh agent created in their place.
AMQ8836 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to destroy an idle <insert_5> agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC failed to destroy an idle agent process. The EC normally performs this operation as a result of managing the pool of idle agents. Agents that have been used more than a certain (configurable) number of times are destroyed and a fresh agent created in their place.
Response
Examine the log to see if further information is available relating to the failure to destroy the agent.
AMQ8837 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to create an idle <insert_5> agent.
Severity
40 : Stop Error
Explanation
An EC failed to create an idle <insert_5> agent process. The EC normally performs this operation as a result of managing the pool of idle agents. Agents that have been used more than a certain (configurable) number of times are destroyed and a fresh agent created in their place.
Response
Examine the log to see if further information is available relating to the failure to create the agent.
AMQ8838 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> initiated creation of an idle <insert_5> agent.
Severity
30 : Severe error
Explanation
An EC successfully initiated the creation of an idle <insert_5> agent process. The EC normally performs this operation as a result of managing the pool of idle agents. Agents that have been used more than a certain (configurable) number of times are destroyed and a fresh agent created in their place.
AMQ8839 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to complete a <insert_3> request for channel <insert_5>.
Severity
40 : Stop Error
Explanation
An EC failed to complete the processing of a <insert_3> request. The originator of the request is passed the completion status and reason code.
Response
Examine the log to see if further information is available relating to the failure to complete the processing of the request.
AMQ8840 (Tandem)
EC number <insert_1> in Queue Manager <insert_4> failed to complete an agent status request for agent process <insert_3>.
Severity
40 : Stop Error
Explanation
An EC failed to complete the processing of an agent status request. The EC Boss or EC has detected an inconsistency in context information about the agent.
Response
Examine the log to see if further information is available relating to the failure to complete the processing of the request.
AMQ8841 (Tandem)
EC process <insert_3> in Queue Manager <insert_4> is waiting for the EC Boss to initialize.
Severity
30 : Severe error
Explanation
An EC is waiting for the EC Boss to initialize and create its entry in the RUNTIME file for the Queue Manager.
AMQ8842 (Tandem)
Error attempting to create queue manager.
Severity
40 : Stop Error
Explanation
MQ verification request, omvStartChildProcess, failed.
Response
None.
AMQ8843 (Tandem)
Queue manager, <insert_3>, created successfully
Severity
0 : Information
Response
None.
AMQ8844 (Tandem)
Queue manager, <insert_3>, already created
Severity
0 : Information
Response
None.
AMQ8845 (Tandem)
An MQSeries NonStop Server has restarted its backup process
Severity
40 : Stop Error
Explanation
The MQSeries NonStop Server process <insert_3> detected the failure of its backup process and has restarted a new backup in CPU <insert_1>.
Response
Use the standard operating system facilities to diagnose the cause of the backup NonStop Server failure and attempt to correct it. MQSeries will continue without interruption.
AMQ8846 (Tandem)
MQSeries NonStop Server takeover initiated
Severity
40 : Stop Error
Explanation
The MQSeries NonStop Server backup process <insert_3> detected the failure of its primary process and is in the process of taking over and starting a new backup. The new NonStop Server primary process is now running in CPU <insert_1>.
Response
Use the standard operating system facilities to diagnose the cause of the primary NonStop Server failure and attempt to correct it. MQSeries will continue without interruption.
AMQ8847 (Tandem)
The EC Boss in Queue Manager <insert_4> failed to find an EC to service a request.
Severity
40 : Stop Error
Explanation
The EC Boss failed to find an active EC to service a request that was made, either by an application (in order to start a connection), or by an administration command (for example, to start or stop a channel). It is possible that all ECs in the Queue Manager have failed repeatedly, exceeding the maximum number of restarts allowed by PATHWAY.
Response
Examine the log to see if further information is available on the state of the Queue Manager. The Queue Manager will need to be ended and restarted.
AMQ8850 (Tandem)
Warning: MQSeries Licence Exception Detected MQSeries has detected that this environment exceeds the authorized licence registration. Please review your licence registration by running the installation program INSTMQM with the -l option and if necessary, obtain the required extra use-authorization from your program provider to avoid being in breach of your MQSeries licence agreement.
Severity
0 : Information
Explanation
None.
Response
None.
AMQ8851 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) encountered a(n) <insert_4> error on the rdfpurge file <insert_3>. The file system returned error code <insert_1>.
Response
Use the standard operating system facilities to verify the state of this file and reinvoke the utility if the error is deemed transient.
AMQ8852 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) has detected that the backup system <insert_4> is inaccessible. The file system returned error code <insert_1>.
Response
Contact your systems administrator and reinvoke the utility if the error is deemed transient.
AMQ8853 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) has encountered a TM/MP <insert_4> error. The system returned error code <insert_1>.
Response
Contact your systems administrator and reinvoke the utility if the error is deemed transient.
AMQ8854 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) encountered a(n) <insert_4> error on file <insert_3>. The system returned error code <insert_1>.
Response
Ensure that a file with this name exists on the same volume and subvolume (i.e. create if necessary - format is irrelevant) on both the primary system and backup systems before reinvoking the utility.
AMQ8855 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) encountered a(n) <insert_4> error for the FUP process <insert_3>. The system returned error code <insert_1>.
Response
Use the standard operating system facilities to verify the MQRDFFUPPROGNAME and MQRDFFUPPROCESSNAME environment parameters. Reinvoke the utility if the error is deemed transient.
AMQ8856 (Tandem)
MQSeries CleanRDF utility has detected an error
Severity
40 : Stop Error
Explanation
CleanRDF (queue manager <insert_5>) encountered an error when attempting to duplicate file <insert_3> to backup system <insert_4>. The system returned error code <insert_1>.
Response
Use the standard operating system facilities to verify the state of this file on both primary and backup systems. Reinvoke the utility if the error is deemed transient.
AMQ8857 (Tandem)
MQSeries CleanRDF utility STATISTICS Message
Severity
40 : Stop Error
Explanation
CleanRDF of queue manager <insert_5> has completed operation. <insert_1> files were deleted. <insert_2> files were Skipped. <insert_3> static files were duplicated to backup system <insert_4>.
AMQ8871
Entity, principal or group not known.
Severity
20 : Error
Explanation
The authorization entity, which can be either a principal or a group, could not be found.
AMQ8874 (Tandem)
Placeholder for new message
Severity
40 : Stop Error
Explanation
This is a placeholder for a new message
AMQ8875 (Tandem)
Placeholder for new message
Severity
40 : Stop Error
Explanation
This is a placeholder for a new message
AMQ8876 (Tandem)
Placeholder for new message
Severity
40 : Stop Error
Explanation
This is a placeholder for a new message
AMQ8877
WebSphere MQ channel authentication record set.
Severity
0 : Information
Explanation
WebSphere MQ channel authentication record set.
AMQ8878
Display channel authentication record details.
Severity
0 : Information
Explanation
The display channel authentication command completed successfully. Details follow this message.
AMQ8879
Channel authentication record type not valid.
Severity
20 : Error
Explanation
The type parameter specified on the command was not valid.
Response
Specify a valid type. Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8880
Channel authentication record action not valid.
Severity
20 : Error
Explanation
The action parameter specified on the command was not valid.
Response
Specify a valid action. Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8881
Channel authentication record user source not valid.
Severity
20 : Error
Explanation
The user source parameter specified on the command was not valid.
Response
Specify a valid user source. Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8882
Parameter not allowed for this channel authentication record type.
Severity
20 : Error
Explanation
The parameter is not allowed for the type of channel authentication record being set or displayed.
Response
Refer to the description of the parameter in error to determine the types of record for which this parameter is valid.
AMQ8883
Channel authentication record already exists.
Severity
20 : Error
Explanation
An attempt was made to add a channel authentication record, but it already exists.
Response
Specify action as MQACT_REPLACE.
AMQ8884
Channel authentication record not found.
Severity
20 : Error
Explanation
The specified channel authentication record does not exist.
Response
Specify a channel authentication record that exists.
AMQ8885
Parameter not allowed for this action on a channel authentication record.
Severity
20 : Error
Explanation
The parameter is not allowed for the action being applied to a channel authentication record. Refer to the description of the parameter in error to determine the actions for which this parameter is valid.
Response
Remove the parameter.
AMQ8886
Parameter not allowed for this channel authentication record user source value.
Severity
20 : Error
Explanation
The parameter is not allowed for a channel authentication record with the value that the user source field contains. Refer to the description of the parameter in error to determine the values of user source for which this parameter is valid.
Response
Remove the parameter.
AMQ8887
Parameter not allowed for this channel authentication record match value.
Severity
20 : Error
Explanation
The parameter is not allowed for an inquire channel authentication record with the value that the match field contains. Refer to the description of the parameter in error to determine the values of match for which this parameter is valid.
Response
Remove the parameter.
AMQ8888
Channel authentication record warn value not valid.
Severity
20 : Error
Explanation
The warn parameter specified on the command was not valid.
Response
Specify a valid value for warn. Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8891
Channel authentication profile name is invalid.
Severity
20 : Error
Explanation
The channel profile name used in the command was not valid. This may be because it contained characters which are not accepted in WebSphere MQ names, or characters which are not valid for the specified profile type.
Response
None.
AMQ8901 (Tandem)
A Status Server has started
Severity
0 : Information
Explanation
A Status Server in CPU <insert_1> has started. The process is named <insert_3>.
Response
None.
AMQ8902 (Tandem)
A Status Server has ended normally.
Severity
0 : Information
Explanation
A Status Server in CPU <insert_1> has ended normally. The process was named <insert_3>.
Response
None.
AMQ8903 (Tandem)
A Status Server has ended with errors.
Severity
0 : Information
Explanation
A Status Server in CPU <insert_1> has ended with errors. The process was named <insert_3>. The error return code reported by the Status Server is <insert_2>. The Status Server should be restarted automatically by the Queue Manager.
Response
Verify that the Status Server has restarted correctly. Examine the Queue Manager FD subvolume for FFST files that may have been generated by the Status Server. Use the process name to locate the relevant FFSTs. Attempt to reconstruct the chain of events or symptoms that lead to the failure and save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
AMQ8904 (Tandem)
A Status Server has detected a CPU failure.
Severity
0 : Information
Explanation
The Status Server process <insert_3> has detected that CPU <insert_1> failed. If there were components of the Status Manager that were running in this CPU, they will now no longer be available, and application connections and channels may be dropped. The Status Manager should continue to be available to new connections and channels. Any Status Server and Queue Server processes that were running in that CPU will be replaced in other available CPUs.
Response
None normally necessary. Applications could experience the reason code MQRC_CONNECTION_BROKEN (2009) from MQI operations in progress that used agent processes running in the failed CPUs, but they should be able to immediatelt re-connect successfully.
AMQ8905 (Tandem)
A Status Server completed takeover processing.
Severity
0 : Information
Explanation
The Status Server process <insert_3> has completed processing that was associated with a prior takeover from a failed primary Status Server process, or the failure of the CPU that it was running in. Normal processing resumes after this point, and the Status Server is again in a state where it is resilient to any single point of failure.
Response
None normally necessary. This message is logged to provide positive confirmation that the takeover is complete.
AMQ8906 (Tandem)
More Channel Status' hardened than Max allowed.
Severity
0 : Information
Explanation
There were more Channel Status' hardened to the STATABLE than the MAXACTIVECHANNELS in the QMINI File.
Response
None.
AMQ8919
There are no matching IBM WebSphere MQ queue manager names.
Severity
30 : Severe error
AMQ8934 (IBM i)
Message . . . . :
Severity
10 : Warning
AMQ8935 (IBM i)
Cause . . . . . :
Severity
10 : Warning
AMQ8936 (IBM i)
Recovery . . . :
Severity
10 : Warning
AMQ8937 (IBM i)
Technical Description . . . . . . . . :
Severity
10 : Warning
AMQ8A01 (IBM i)
Create Message Queue Manager
AMQ8A02 (IBM i)
Delete Message Queue Manager
AMQ8A04 (IBM i)
Work with MQ Messages
AMQ8A05 (IBM i)
Change Message Queue Manager
AMQ8A06 (IBM i)
Display Message Queue Manager
AMQ8A07 (IBM i)
End Message Queue Manager
AMQ8A08 (IBM i)
Start Message Queue Manager
AMQ8A09 (IBM i)
Change MQ Queue
AMQ8A0A (IBM i)
Clear MQ Queue
AMQ8A0B (IBM i)
Copy MQ Queue
AMQ8A0C (IBM i)
Create MQ Queue
AMQ8A0D (IBM i)
Delete MQ Queue
AMQ8A0E (IBM i)
Display MQ Queue
AMQ8A0F (IBM i)
Work with MQ Queues
AMQ8A10 (IBM i)
Change MQ Process
AMQ8A11 (IBM i)
Copy MQ Process
AMQ8A12 (IBM i)
Create MQ Process
AMQ8A13 (IBM i)
Delete MQ Process
AMQ8A14 (IBM i)
Display MQ Process
AMQ8A15 (IBM i)
Work with MQ Processes
AMQ8A16 (IBM i)
Start MQ Command Server
AMQ8A17 (IBM i)
End MQ Command Server
AMQ8A18 (IBM i)
Display MQ Command Server
AMQ8A19 (IBM i)
Set MQ
AMQ8A20 (IBM i)
Quiesce Message Queue Managers
AMQ8A21 (IBM i)
Quiesce Retry Delay
AMQ8A23 (IBM i)
Work with Queue Status
AMQ8A30 (IBM i)
Create MQ Channel
AMQ8A31 (IBM i)
Display MQ Channel
AMQ8A32 (IBM i)
Start MQ Listener
AMQ8A33 (IBM i)
Ping MQ Channel
AMQ8A34 (IBM i)
Delete MQ Channel
AMQ8A36 (IBM i)
Work with MQ Channels
AMQ8A37 (IBM i)
Change MQ Channel
AMQ8A38 (IBM i)
Copy MQ Channel
AMQ8A39 (IBM i)
Reset MQ Channel
AMQ8A40 (IBM i)
End MQ Channel
AMQ8A41 (IBM i)
Start MQ Channel
AMQ8A42 (IBM i)
Start MQ Channel Initiator
AMQ8A43 (IBM i)
Grant MQ Object Authority
AMQ8A44 (IBM i)
Revoke MQ Object Authority
AMQ8A45 (IBM i)
Display MQ Object Authority
AMQ8A46 (IBM i)
Display MQ Object Names
AMQ8A47 (IBM i)
Refresh IBM WebSphere MQ Authority
AMQ8A48 (IBM i)
Work with MQ Authority
AMQ8A49 (IBM i)
Start MQ Service
AMQ8A50 (IBM i)
End MQ Service
AMQ8A51 (IBM i)
Connect MQ
AMQ8A52 (IBM i)
Disconnect MQ
AMQ8A53 (IBM i)
Work with MQ Authority Data
AMQ8A54 (IBM i)
Resolve MQ Channel
AMQ8A55 (IBM i)
Work with MQ Channel Status
AMQ8A56 (IBM i)
SSL Client Authentication
AMQ8A57 (IBM i)
SSL CipherSpec
AMQ8A58 (IBM i)
SSL Peer name
AMQ8A59 (IBM i)
Local communication address
AMQ8A5A (IBM i)
Batch Heartbeat Interval
AMQ8A5B (IBM i)
Remove Queues
AMQ8A5C (IBM i)
Refresh Repository
AMQ8A5D (IBM i)
IP Address
AMQ8A60 (IBM i)
Cluster Name
AMQ8A61 (IBM i)
Cluster Name List
AMQ8A62 (IBM i)
Mode Name
AMQ8A63 (IBM i)
Password
AMQ8A64 (IBM i)
Transaction Program Name
AMQ8A65 (IBM i)
User Profile
AMQ8A66 (IBM i)
Network Connection Priority
AMQ8A67 (IBM i)
Batch Interval
AMQ8A68 (IBM i)
Batch Interval
AMQ8A69 (IBM i)
Cluster Workload Exit Data
AMQ8A6A (IBM i)
Cluster Workload Exit
AMQ8A6B (IBM i)
Repository Cluster
AMQ8A6C (IBM i)
Repository Cluster Namelist
AMQ8A6D (IBM i)
Cluster Workload Exit Data Length
AMQ8A6E (IBM i)
Maximum Message Length
AMQ8A6F (IBM i)
Default Queue Manager
AMQ8A70 (IBM i)
Default Binding
AMQ8A71 (IBM i)
Channel Table
AMQ8A72 (IBM i)
Change MQ Namelist
AMQ8A73 (IBM i)
List of Names
AMQ8A74 (IBM i)
Namelist
AMQ8A75 (IBM i)
Create MQ Namelist
AMQ8A76 (IBM i)
recreate MQ Object
AMQ8A77 (IBM i)
Record MQ Object Image
AMQ8A78 (IBM i)
Start IBM WebSphere MQ Commands
AMQ8A7A (IBM i)
Copy MQ Namelist
AMQ8A7B (IBM i)
From Namelist
AMQ8A7C (IBM i)
To Namelist
AMQ8A7D (IBM i)
Delete MQ Namelist
AMQ8A7E (IBM i)
Display MQ Namelist
AMQ8A7F (IBM i)
Work with MQ Namelist
AMQ8A80 (IBM i)
Group Profile
AMQ8A81 (IBM i)
User Profile
AMQ8A82 (IBM i)
Service Component
AMQ8A83 (IBM i)
Work with MQ Queue Manager
AMQ8A84 (IBM i)
Work with MQ Clusters
AMQ8A85 (IBM i)
Start MQ Trigger Monitor
AMQ8A86 (IBM i)
End MQ Listeners
AMQ8A87 (IBM i)
Work with MQ Transactions
AMQ8A88 (IBM i)
Resolve MQ Transaction
AMQ8A89 (IBM i)
Work with MQ Cluster Queues
AMQ8A8A (IBM i)
Display Journal Receiver Data
AMQ8A8B (IBM i)
Start MQ Pub/Sub Broker
AMQ8A8C (IBM i)
End MQ Pub/Sub Broker
AMQ8A8D (IBM i)
Display MQ Pub/Sub Broker
AMQ8A8E (IBM i)
Clear MQ Pub/Sub Broker
AMQ8A8F (IBM i)
Delete MQ Pub/Sub Broker
AMQ8B01 (IBM i)
Message Queue Manager name
AMQ8B02 (IBM i)
Text 'description'
AMQ8B03 (IBM i)
Trigger interval
AMQ8B04 (IBM i)
Undelivered message queue
AMQ8B05 (IBM i)
Default transmission queue
AMQ8B06 (IBM i)
Maximum handle limit
AMQ8B07 (IBM i)
Maximum uncommitted messages
AMQ8B08 (IBM i)
Queue name
AMQ8B09 (IBM i)
Output
AMQ8B0A (IBM i)
Library
AMQ8B0B (IBM i)
File to receive output
AMQ8B0C (IBM i)
OPTION(*MVS) not valid without specifying a value for WAIT.
Severity
40 : Stop Error
Explanation
The OPTION(*MVS) parameter may not be specified without specifying a value for the WAIT parameter.
Response
Remove the OPTION(*MVS) parameter from the command or, specify a value for the WAIT parameter. Then try the command again.
AMQ8B0D (IBM i)
Member to receive output
AMQ8B0E (IBM i)
Replace or add records
AMQ8B0F (IBM i)
Option
AMQ8B10 (IBM i)
Mode
AMQ8B11 (IBM i)
Put enabled
AMQ8B12 (IBM i)
Default message priority
AMQ8B13 (IBM i)
Default message persistence
AMQ8B14 (IBM i)
Process name
AMQ8B15 (IBM i)
Triggering enabled
AMQ8B16 (IBM i)
Get enabled
AMQ8B17 (IBM i)
Sharing enabled
AMQ8B18 (IBM i)
Default share option
AMQ8B19 (IBM i)
Message delivery sequence
AMQ8B1A (IBM i)
Harden backout count
AMQ8B1B (IBM i)
Trigger type
AMQ8B1C (IBM i)
Trigger depth
AMQ8B1D (IBM i)
Trigger message priority
AMQ8B1E (IBM i)
Trigger data
AMQ8B1F (IBM i)
Retention interval
AMQ8B20 (IBM i)
Maximum queue depth
AMQ8B21 (IBM i)
Maximum message length
AMQ8B22 (IBM i)
Backout threshold
AMQ8B23 (IBM i)
Backout requeue name
AMQ8B24 (IBM i)
Initiation queue
AMQ8B25 (IBM i)
Usage
AMQ8B26 (IBM i)
Definition type
AMQ8B27 (IBM i)
Target object
AMQ8B28 (IBM i)
Remote queue
AMQ8B29 (IBM i)
Remote Message Queue Manager
AMQ8B2A (IBM i)
Transmission queue
AMQ8B2B (IBM i)
From queue name
AMQ8B2C (IBM i)
To queue name
AMQ8B2D (IBM i)
Replace
AMQ8B2E (IBM i)
Queue type
AMQ8B2F (IBM i)
Application type
AMQ8B30 (IBM i)
Application identifier
AMQ8B31 (IBM i)
User data
AMQ8B32 (IBM i)
Environment data
AMQ8B33 (IBM i)
From process
AMQ8B34 (IBM i)
To process
AMQ8B36 (IBM i)
Job name
AMQ8B37 (IBM i)
Number
AMQ8B3A (IBM i)
Convert message
AMQ8B3B (IBM i)
Replace to member
AMQ8B3C (IBM i)
Heartbeat interval
AMQ8B3D (IBM i)
Non Persistent Message Speed
AMQ8B3E (IBM i)
Force
AMQ8B3F (IBM i)
No Jobs to display
AMQ8B41 (IBM i)
Queue definition scope
AMQ8B42 (IBM i)
Queue depth high threshold
AMQ8B43 (IBM i)
Queue depth low threshold
AMQ8B44 (IBM i)
Queue full events enabled
AMQ8B45 (IBM i)
Queue high events enabled
AMQ8B46 (IBM i)
Queue low events enabled
AMQ8B47 (IBM i)
Service interval
AMQ8B48 (IBM i)
Service interval events
AMQ8B49 (IBM i)
Distribution list support
AMQ8B4A (IBM i)
Parent Message Queue Manager
AMQ8B4B (IBM i)
Break Parent link
AMQ8B4C (IBM i)
Child Message Queue Manager
AMQ8B53 (IBM i)
Authorization events enabled
AMQ8B54 (IBM i)
Inhibit events enabled
AMQ8B55 (IBM i)
Local error events enabled
AMQ8B56 (IBM i)
Remote error events enabled
AMQ8B57 (IBM i)
Performance events enabled
AMQ8B58 (IBM i)
Start and stop events enabled
AMQ8B59 (IBM i)
Automatic Channel Definition
AMQ8B5A (IBM i)
Automatic Channel Definition events enabled
AMQ8B5B (IBM i)
Automatic Channel Definition exit program
AMQ8B5C (IBM i)
Redefine system objects
AMQ8B5D (IBM i)
Wait time
AMQ8B5E (IBM i)
Startup Status Detail
AMQ8B60 (IBM i)
Transaction type
AMQ8B61 (IBM i)
Log recovery events enabled
AMQ8B62 (IBM i)
IP protocol
AMQ8B63 (IBM i)
Configuration events enabled
AMQ8B64 (IBM i)
Refresh Message Queue Manager
AMQ8B65 (IBM i)
Refresh Type
AMQ8B66 (IBM i)
Include Interval
AMQ8B67 (IBM i)
IBM WebSphere MQ queue manager refreshed.
AMQ8B68 (IBM i)
Channel events enabled
AMQ8B69 (IBM i)
SSL events enabled
AMQ8B6A (IBM i)
Filter command
AMQ8B6B (IBM i)
Filter keyword
AMQ8B6C (IBM i)
Filter operator
AMQ8B6D (IBM i)
Filter value
AMQ8B6E (IBM i)
Filter value <insert_3> not valid with keyword <insert_4>.
Severity
30 : Severe error
Explanation
The filter value <insert_3> is not valid with the keyword <insert_4>.
Response
Specify a valid filter value for the keyword <insert_4>.
AMQ8B70 (IBM i)
Change MQ AuthInfo object
AMQ8B71 (IBM i)
Copy MQ AuthInfo object
AMQ8B72 (IBM i)
Create MQ AuthInfo object
AMQ8B73 (IBM i)
Delete MQ AuthInfo object
AMQ8B74 (IBM i)
Display MQ AuthInfo object
AMQ8B75 (IBM i)
From AuthInfo name
AMQ8B76 (IBM i)
AuthInfo name
AMQ8B77 (IBM i)
AuthInfo type
AMQ8B78 (IBM i)
User name
AMQ8B79 (IBM i)
User password
AMQ8B7A (IBM i)
Work with AuthInfo objects
AMQ8B7B (IBM i)
To AuthInfo name
AMQ8B80 (IBM i)
Change MQ Processor Allowance
AMQ8B81 (IBM i)
Display MQ Processor Allowance
AMQ8B82 (IBM i)
Sufficient Licence Units
AMQ8C01 (IBM i)
From channel
AMQ8C02 (IBM i)
Channel name
AMQ8C03 (IBM i)
Channel type
AMQ8C04 (IBM i)
SSL key reset count
AMQ8C05 (IBM i)
Remote queue manager
AMQ8C07 (IBM i)
Transmission queue
AMQ8C08 (IBM i)
Connection name
AMQ8C09 (IBM i)
Message channel agent
AMQ8C10 (IBM i)
Message channel agent user ID
AMQ8C12 (IBM i)
Batch size
AMQ8C13 (IBM i)
Disconnect interval
AMQ8C14 (IBM i)
Short retry count
AMQ8C15 (IBM i)
Short retry interval
AMQ8C16 (IBM i)
Long retry count
AMQ8C17 (IBM i)
Long retry interval
AMQ8C18 (IBM i)
Security exit
AMQ8C19 (IBM i)
Message exit
AMQ8C20 (IBM i)
Send exit
AMQ8C21 (IBM i)
Receive exit
AMQ8C22 (IBM i)
SSL CRL Namelist
AMQ8C23 (IBM i)
SSL Key Repository
AMQ8C24 (IBM i)
Put authority
AMQ8C25 (IBM i)
Sequence number wrap
AMQ8C27 (IBM i)
Transport type
AMQ8C28 (IBM i)
Data count
AMQ8C29 (IBM i)
Count
AMQ8C30 (IBM i)
To channel
AMQ8C31 (IBM i)
Message sequence number
AMQ8C32 (IBM i)
SSL Cryptographic Hardware
AMQ8C33 (IBM i)
Security exit user data
AMQ8C34 (IBM i)
Send exit user data
AMQ8C35 (IBM i)
Receive exit user data
AMQ8C36 (IBM i)
Message exit user data
AMQ8C37 (IBM i)
Resolve option
AMQ8C38 (IBM i)
Connection name
AMQ8C39 (IBM i)
Transmission queue name
AMQ8C40 (IBM i)
SSL Repository Password
AMQ8C41 (IBM i)
First Message
AMQ8C42 (IBM i)
Maximum number of messages
AMQ8C43 (IBM i)
Maximum message size
AMQ8C44 (IBM i)
Message retry exit
AMQ8C45 (IBM i)
Message retry exit data
AMQ8C46 (IBM i)
Number of message retries
AMQ8C47 (IBM i)
Message retry interval
AMQ8C48 (IBM i)
Coded Character Set
AMQ8C49 (IBM i)
Max message length
AMQ8C50 (IBM i)
Repository name
AMQ8C51 (IBM i)
Repository name list
AMQ8C52 (IBM i)
Cluster workload exit length
AMQ8C53 (IBM i)
Cluster workload exit
AMQ8C54 (IBM i)
Cluster workload exit data
AMQ8C55 (IBM i)
Suspend Cluster Queue Manager
AMQ8C56 (IBM i)
Reset Cluster
AMQ8C57 (IBM i)
Refresh MQ Cluster
AMQ8C58 (IBM i)
Resume Cluster Queue Manager
AMQ8C59 (IBM i)
Action
AMQ8C5A (IBM i)
Queue Manager Name for removal
AMQ8C5B (IBM i)
Work with MQ Listeners
AMQ8C5C (IBM i)
Queue Manager Id for removal
AMQ8C60 (IBM i)
Display Cluster Message Queue Manager
AMQ8C61 (IBM i)
Cluster Queue Manager name
AMQ8C62 (IBM i)
End MQ Listeners
AMQ8C63 (IBM i)
Port number
AMQ8C64 (IBM i)
Message channel agent Type
AMQ8C65 (IBM i)
Task user identifier
AMQ8D01 (IBM i)
Trace MQ
AMQ8D02 (IBM i)
Trace option setting
AMQ8D03 (IBM i)
Trace level
AMQ8D04 (IBM i)
Trace types
AMQ8D05 (IBM i)
Maximum storage to use
AMQ8D06 (IBM i)
Trace early
AMQ8D07 (IBM i)
Exclude types
AMQ8D08 (IBM i)
Trace interval
AMQ8D0A (IBM i)
Output member options
AMQ8D10 (IBM i)
Object name
AMQ8D11 (IBM i)
Object type
AMQ8D12 (IBM i)
User names
AMQ8D13 (IBM i)
Authority
AMQ8D14 (IBM i)
Authorization list
AMQ8D15 (IBM i)
Reference object name
AMQ8D16 (IBM i)
Reference object type
AMQ8D17 (IBM i)
Object name
AMQ8D18 (IBM i)
Process name
AMQ8D19 (IBM i)
Queue name
AMQ8D1A (IBM i)
Queue Manager Library
AMQ8D1B (IBM i)
ASP Number
AMQ8D1C (IBM i)
Journal receiver threshold
AMQ8D1D (IBM i)
Journal buffer size
AMQ8D20 (IBM i)
Channel name
AMQ8D22 (IBM i)
Cluster name
AMQ8D23 (IBM i)
Cluster namelist name
AMQ8D24 (IBM i)
User name
AMQ8D25 (IBM i)
Channel status
AMQ8D26 (IBM i)
End connected jobs
AMQ8D27 (IBM i)
Timeout interval (seconds)
AMQ8D28 (IBM i)
Object/Profile name
AMQ8D29 (IBM i)
Service Component name
AMQ8D2A (IBM i)
Work with MQ Topics
AMQ8D2B (IBM i)
Topic name
AMQ8D2C (IBM i)
No topics to display
AMQ8D2D (IBM i)
Delete MQ Topic
AMQ8D2E (IBM i)
Display MQ Topic
AMQ8D30 (IBM i)
Keep Alive Interval