IBM MQ queue manager <insert_5> started using V<insert_3>.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_5> started using V<insert_3>.
Response
None.
AMQ8004I
IBM MQ queue manager <insert_5> ended.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_5> ended.
Response
None.
AMQ8005I
IBM MQ queue manager changed.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_3> changed.
Response
None.
AMQ8006I
IBM MQ queue created.
Severity
0 : Informational
Explanation
IBM MQ queue <insert_3> created.
Response
None.
AMQ8007I
IBM MQ queue deleted.
Severity
0 : Informational
Explanation
IBM MQ queue <insert_3> deleted.
Response
None.
AMQ8008I
IBM MQ queue changed.
Severity
0 : Informational
Explanation
IBM MQ queue <insert_3> changed.
Response
None.
AMQ8009W
Entity <insert_3> has insufficient authority to access topic string <insert_4>.
Severity
10 : Warning
Explanation
The specified entity is not authorized to access the required topic. The following permissions were requested: <insert_5>
Response
Ensure that the correct level of authority has been set for this entity against appropriate topic objects, or ensure that the entity is a member of a privileged group.
AMQ8010I
IBM MQ process created.
Severity
0 : Informational
Explanation
IBM MQ process <insert_3> created.
Response
None.
AMQ8011I
IBM MQ process deleted.
Severity
0 : Informational
Explanation
IBM MQ process <insert_3> deleted.
Response
None.
AMQ8012I
IBM MQ process changed.
Severity
0 : Informational
Explanation
IBM MQ process <insert_3> changed.
Response
None.
AMQ8014I
IBM MQ channel created.
Severity
0 : Informational
Explanation
IBM MQ channel <insert_3> created.
Response
None.
AMQ8015I
IBM MQ channel deleted.
Severity
0 : Informational
Explanation
IBM MQ channel <insert_3> deleted.
Response
None.
AMQ8016I
IBM MQ channel changed.
Severity
0 : Informational
Explanation
IBM MQ channel <insert_3> changed.
Response
None.
AMQ8017I
Purge IBM MQ channel accepted.
Severity
0 : Informational
Explanation
The channel <insert_3> has been requested to be purged.
Response
None.
AMQ8018I
Start IBM MQ channel accepted.
Severity
0 : Informational
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 whom communication is being initiated.
Response
None.
AMQ8019I
Stop IBM MQ channel accepted.
Severity
0 : Informational
Explanation
The channel <insert_3> has been requested to stop.
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.
AMQ8022I
IBM MQ queue cleared.
Severity
0 : Informational
Explanation
All messages on queue <insert_3> have been deleted.
Response
None.
AMQ8023I
IBM MQ channel reset.
Severity
0 : Informational
Explanation
Channel <insert_3> has been reset, the new sequence number of the channel is <insert_1>.
The queue manager cannot be restarted or deleted because processes, that were previously connected, are still running.
Severity
40 : Severe
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.
AMQ8041S (IBM i)
The queue manager cannot be restarted or deleted.
Severity
40 : Severe
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.
AMQ8042I
Process <insert_1> is still running.
Severity
0 : Informational
AMQ8042I (HP NSS)
Process <insert_4> is still running.
Severity
0 : Informational
AMQ8043I
Non runtime application attempted to connect to runtime only queue manager.
Severity
0 : Informational
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.
AMQ8044I (Windows)
An error occurred while removing the queue manager from the Active Directory.
Severity
0 : Informational
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.
AMQ8045E
IBM MQ channel in use.
Severity
20 : Error
Explanation
IBM MQ channel <insert_3> in use. A process is either trying to delete a running telemetry or AMQP channel, or to define a new telemetry or AMQP channel using a port that is already in use. If the process is trying to define a new telemetry or AMQP 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.
Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects.
Response
None.
AMQ8049E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8050I
Create or replacing default objects for queue manager <insert_3>.
Severity
0 : Informational
Response
None.
AMQ8051I
For details of the failures that occurred, please check AMQERR01.LOG.
Severity
0 : Informational
Response
None.
AMQ8052I
Completing setup.
Severity
0 : Informational
Response
None.
AMQ8053E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8054E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8055E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8056E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8057E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8058E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8059E
Object <insert_4>. Unable to create or replace.
Severity
20 : Error
Explanation
While creating or replacing the default object <insert_4> for IBM 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.
AMQ8060I
IBM MQ queue manager <insert_5> started as a standby instance.
Severity
0 : Informational
Explanation
Queue manager <insert_5> started as a standby instance, ready to become the active instance if the existing active instance fails.
Response
None.
AMQ8061W (Windows)
Command <insert_4> is not valid.
Severity
10 : Warning
Explanation
The command <insert_4> at line <insert_1> in the IBM 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.
AMQ8062W (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 MQ service for queue manager <insert_4>.
Response
Verify that the command and parameters are correct.
AMQ8063E (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.
AMQ8064E (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.
AMQ8065E (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.
AMQ8066E (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.
AMQ8068I
Setup completed.
Severity
0 : Informational
Response
None.
AMQ8069S
ApplicationGroup for the crtmqm command does not contain the <insert_3> userid.
Severity
40 : Severe
Explanation
IBM MQ queue manager <insert_5> not created. The ApplicationGroup specified for the crtmqm command must contain the <insert_3> userid when the RestrictedMode option (-g) is specified.
Response
None.
AMQ8070S
ApplicationGroup for crtmqm command is not defined.
Severity
40 : Severe
Explanation
IBM MQ queue manager <insert_5> not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist.
Response
None.
AMQ8071S
RestrictedMode option not supported on this platform.
Severity
40 : Severe
Explanation
IBM MQ queue manager <insert_5> not created. The RestrictedMode option was specified but is not supported on this platform.
Response
None.
AMQ8072W (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 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.
AMQ8073W (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.
AMQ8074W (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.
AMQ8075W (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. This could be because the local machine is not in the domain to locate the entity, or because the entity does not exist.
Response
Ensure that the entity is valid, and that all necessary domain controllers are available. This might mean creating the entity on the local machine.
AMQ8076W (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.
AMQ8077W
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.
AMQ8078I
Waiting for queue manager <insert_3> to end.
Severity
0 : Informational
Response
None.
AMQ8079I (IBM i)
IBM MQ trigger monitor job started.
Severity
0 : Informational
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.
AMQ8079W (Windows)
Access was denied when attempting to retrieve group membership information for user <insert_3>.
Severity
10 : Warning
Explanation
IBM 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.
AMQ8080S (IBM i)
IBM MQ trigger monitor job start failed.
Severity
40 : Severe
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.
AMQ8081W (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 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.
AMQ8082W (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 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.
AMQ8083I
IBM MQ queue manager <insert_3> starting.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_3> starting.
Response
None.
AMQ8084E
IBM MQ connection not found.
Severity
30 : Error
Explanation
The connection specified does not exist.
Response
Correct the connection name and then try the command again.
AMQ8085I
IBM MQ queue manager <insert_3> is being started for replay.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_3> is being started for replay. The strmqm command has been issued with the '-r' option. see the IBM MQ System Administration documentation for details.
Response
None.
AMQ8086I
IBM MQ queue manager <insert_3> is being activated.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_3> is being activated. The strmqm command has been issued with the '-a' option. see the IBM MQ System Administration documentation for details.
Response
None.
AMQ8086I (IBM i)
IBM MQ queue manager <insert_3> is being activated.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_3> is being activated. The STRMQM command has been issued with the ACTIVATE(*YES) option. see the IBM MQ System Administration documentation for further details.
Response
None.
AMQ8087E
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>.
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>.
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>.
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>.
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>.
Service migration statistics : <insert_1> migrated. <insert_2> failed.
Severity
0 : Informational
Explanation
Information on the number of service objects migrated from previous versions of IBM MQ for Windows services as well as any failures that occurred.
Response
None.
AMQ8093I
IBM MQ subscription changed.
Severity
0 : Informational
Explanation
IBM MQ subscription <insert_3> changed.
Response
None.
AMQ8094I
IBM MQ subscription created.
Severity
0 : Informational
Explanation
IBM MQ subscription <insert_3> created.
Response
None.
AMQ8095I
IBM MQ subscription deleted.
Severity
0 : Informational
Explanation
IBM MQ subscription <insert_3> deleted.
Response
None.
AMQ8096I
IBM MQ subscription inquired.
Severity
0 : Informational
Explanation
IBM MQ subscription <insert_3> inquired.
Response
None.
AMQ8097E
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 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
AMQ8098I
IBM MQ subscription copied.
Severity
0 : Informational
Explanation
IBM MQ subscription <insert_3> copied.
Response
None.
AMQ8099I
IBM MQ subscription status inquired.
Severity
0 : Informational
Explanation
IBM MQ subscription status <insert_3> inquired.
Response
None.
AMQ8101S
IBM MQ error (<insert_1>) has occurred.
Severity
40 : Severe
Explanation
An unexpected reason code with hexadecimal value <insert_1> was received from the IBM 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.
AMQ8102E
IBM MQ object name specified in <insert_4> not valid.
Severity
30 : 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.
AMQ8103S
Insufficient storage available.
Severity
40 : Severe
Explanation
There was insufficient storage available to perform the requested operation.
Response
Free some storage and then try the command again.
AMQ8104E
Queue manager <insert_5> cannot be restarted or deleted because processes accessing the queue manager data path are still running.
Severity
30 : Error
Explanation
Processes are still accessing files in the queue manager data path. The queue manager cannot be deleted until the processes close the files (or end).
Response
Stop the processes and try to delete the queue manager.
AMQ8105I
Process <insert_3> (<insert_1>) is accessing the queue manager data path.
Severity
0 : Informational
AMQ8106I
IBM MQ queue manager being created.
Severity
0 : Informational
Explanation
The queue manager is being created.
Response
Wait for the creation process to complete and then try the command again.
AMQ8107W
IBM MQ queue manager running.
Severity
10 : Warning
Explanation
The queue manager is running.
Response
None.
AMQ8108W
IBM 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.
AMQ8109I
IBM MQ queue manager being deleted.
Severity
0 : Informational
Explanation
The queue manager is being deleted.
Response
Wait for the deletion process to complete.
AMQ8110E
IBM MQ queue manager already exists.
Severity
30 : Error
Explanation
The queue manager <insert_5> already exists.
Response
None.
AMQ8112S (IBM i)
PRCNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8113S (IBM i)
TRGENBL not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8114S (IBM i)
GETENBL not allowed with queue type *RMT.
Severity
40 : Severe
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.
AMQ8115S (IBM i)
SHARE not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8116S (IBM i)
MSGDLYSEQ not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8117E
IBM MQ queue manager library <insert_4> deletion incomplete.
Severity
30 : Error
Explanation
Deletion of queue manager library <insert_4> for queue manager <insert_5> was only partially successful. There are still <insert_1> object(s) left in the library. An object may have not been removed because it is not recognised as IBM MQ created object, due to an authorization failure or a because the object was in use.
Response
Use operating system facilities to remove the remaining objects in the <insert_4> library.
AMQ8118E
IBM MQ queue manager does not exist.
Severity
30 : 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.
AMQ8119E
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.
AMQ8119S (IBM i)
TRGTYPE not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8120I
Please wait while <insert_4> file system is initialized for queue manager <insert_3>.
Severity
0 : Informational
Explanation
The file system for queue manager <insert_3> is being initialized. Depending on the size of the file system and the speed of the disks this operation may take a significant time to complete.
Response
This message is for information only so no user action is required.
AMQ8120S (IBM i)
TRGDEPTH not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8121E
Updating the state of HA sub-system for Queue Manager <insert_3> failed.
Severity
20 : Error
Explanation
The update of state of the HA sub-system for Queue Manager <insert_3> could not be completed and the operation has failed.
Response
Check the system error logs for details of the failure and correct the issue before reattempting the operation.
AMQ8121S (IBM i)
TRGMSGPTY not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8122W
IBM MQ queue manager <insert_3> HA sub-system is already active.
Severity
10 : Warning
Explanation
The queue manager cannot be started, it should already be running.
Response
Check that the queue manager is active (somewhere in the HA group). If not, check the logs to determine the cause of the problem. again.
AMQ8122S (IBM i)
TRGDATA not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8123I
The HA sub-system for queue manager <insert_3> has been activated and the queue manager will now be started.
Severity
0 : Informational
Explanation
The HA sub-system for the queue manager has been activated and will cause the queue manager to start somewhere in the HA group.
Response
This message is for information only so no user action is required. If the queue manager does not shortly start somewhere within the HA group, check the logs to determine the cause of the problem.
AMQ8123S (IBM i)
RTNITV not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8124I
IBM MQ secondary queue manager created.
Severity
0 : Informational
Explanation
IBM MQ secondary queue manager <insert_3> created.
Response
None.
AMQ8124S (IBM i)
MAXMSGLEN not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8125I
Command <insert_3> run with sudo.
Severity
0 : Informational
AMQ8125S (IBM i)
BKTTHLD not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8126S (IBM i)
BKTQNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8127S (IBM i)
INITQNAME not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8128S (IBM i)
USAGE not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8129S (IBM i)
DFNTYPE only allowed with queue type *MDL.
Severity
40 : Severe
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.
AMQ8130S (IBM i)
TGTQNAME only allowed with queue type *ALS.
Severity
40 : Severe
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.
AMQ8131S (IBM i)
RMTQNAME only allowed with queue type *RMT.
Severity
40 : Severe
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.
AMQ8132S (IBM i)
RMTMQMNAME only allowed with queue type *RMT.
Severity
40 : Severe
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.
AMQ8133S (IBM i)
TMQNAME only allowed with queue type *RMT.
Severity
40 : Severe
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.
AMQ8134S (IBM i)
HDNBKTCNT not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8135E
Not authorized.
Severity
30 : Error
Explanation
You are not authorized to perform the requested operation for the IBM MQ object. Either we are not authorized to perform the requested operation, or we 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 MQ administrator. Then try the command again. If we are running amqmdain on the Windows platform, the user MUSR_MQADMIN may not be authorized.
AMQ8135S (IBM i)
Not authorized/authenticated.
Severity
40 : Severe
Explanation
You are not authorized or your credentials have failed authentication to perform the requested operation for the IBM 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 this error may also indicate that the subscribing user does not exist or have the required authority to the destination queue.
The queue manager may require authenticated username and password credentials based on the queue manager CONNAUTH settings, these credentials may not have been provided or may be incorrect. Credentials for CL commands are provided by specifying values for the USERNAME and PASSWORD parameters via the WRKMQM command.
Response
Obtain the necessary authority from your security officer or IBM MQ administrator.
Ensure that any username and password credentials provided for this job via the USERNAME and PASSWORD parameters via WRKMQM are correct.
AMQ8136E (IBM i)
Error detected by prompt control program.
Severity
30 : 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.
AMQ8137S (IBM i)
IBM MQ queue manager already starting.
Severity
40 : Severe
Explanation
The strmqm command was unsuccessful because the queue manager <insert_5> is already starting.
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.
AMQ8139E
Already connected.
Severity
20 : Error
Explanation
A connection to the IBM MQ queue manager already exists.
Response
None.
AMQ8140E
Resource timeout error.
Severity
30 : Error
Explanation
A timeout occurred in the communication between internal IBM 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.
AMQ8141S (IBM i)
IBM MQ queue manager starting.
Severity
40 : Severe
Explanation
The queue manager <insert_5> is starting.
Response
Wait for the queue manager startup process to complete and then try the command again.
AMQ8142S (IBM i)
IBM MQ queue manager stopped.
Severity
40 : Severe
Explanation
The queue manager <insert_5> is stopped.
Response
Use the strmqm command to start the queue manager, and then try the command again.
AMQ8143E
IBM MQ queue not empty.
Severity
30 : 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.
AMQ8144S (IBM i)
Log not available.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8145E
Connection broken.
Severity
30 : Error
Explanation
The connection to the IBM 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.
AMQ8146E
IBM MQ queue manager not available.
Severity
30 : 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.
AMQ8146S (IBM i)
IBM MQ queue manager not available.
Severity
40 : Severe
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.
AMQ8147E
IBM MQ object <insert_3> not found.
Severity
30 : 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 we 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.
AMQ8147S (IBM i)
IBM MQ object <insert_3> not found.
Severity
40 : Severe
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 we are creating a new MQ object, either specify all parameters explicitly or ensure that the system default object of the required type exists.
AMQ8148E
IBM MQ object in use.
Severity
30 : 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.
AMQ8149S
IBM MQ object damaged.
Severity
40 : Severe
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.
AMQ8150E
IBM MQ object already exists.
Severity
30 : 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.
AMQ8151E
IBM MQ object has different type.
Severity
30 : Error
Explanation
The type specified for object <insert_3> is different from the type of the object being altered or defined.
There are many different types of IBM MQ object, and objects from each type can all have the same name because they exist in separate object namespaces: For example, a sender channel and a client channel can both have the same name. However, an object cannot have the same name as another object in the same namespace: For example, a local queue cannot have the same name as a model queue, and a sender channel cannot have the same name as a receiver channel.
The following IBM MQ objects exist in separate object namespaces:
Authentication information
Channel
Client channel
Listener
Namelist
Process
Queue
Service
Storage class
Subscription
Topic
Response
Use the correct MQ command for the object type, and then try the command again.
AMQ8152S (IBM i)
Source IBM MQ object has different type.
Severity
40 : Severe
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.
AMQ8153S
Insufficient disk space for the specified queue.
Severity
40 : Severe
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.
AMQ8154E
API exit load error.
Severity
30 : Error
Explanation
The IBM 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.
AMQ8155E
Connection limit exceeded.
Severity
30 : Error
Explanation
The queue manager connection limit has been exceeded.
Response
The maximum limit on the number of IBM MQ application programs that may be connected to the queue manager has been exceeded. Try the command later.
AMQ8156E
IBM MQ queue manager quiescing.
Severity
30 : 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.
AMQ8157E
Security error.
Severity
30 : Error
Explanation
An error was reported by the security manager program.
Response
Inform the systems administrator, wait until the problem has been corrected, and then try the command again.
AMQ8158S (IBM i)
API exit not found.
Severity
40 : Severe
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.
AMQ8159S (IBM i)
MAXDEPTH not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8160S (IBM i)
DFTSHARE not allowed with queue type *ALS or *RMT.
Severity
40 : Severe
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.
AMQ8161S (IBM i)
AUT(*MQMPASSID) only allowed with OBJTYPE(*ADM).
Severity
40 : Severe
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.
AMQ8162S (IBM i)
AUT(*MQMPASSALL) only allowed with OBJTYPE(*ADM).
Severity
40 : Severe
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.
AMQ8163S (IBM i)
AUT(*MQMSETID) only allowed with OBJTYPE(*ADM).
Severity
40 : Severe
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.
AMQ8164S (IBM i)
AUT(*MQMSETALL) only allowed with OBJTYPE(*ADM).
Severity
40 : Severe
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.
AMQ8165S (IBM i)
AUT(*MQMALTUSR) only allowed with OBJTYPE(*ADM).
Severity
40 : Severe
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.
AMQ8166S (IBM i)
IBM MQ reference object not found.
Severity
40 : Severe
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.
AMQ8167E (IBM i)
Referenced object name not valid.
Severity
30 : 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.
AMQ8168E (IBM i)
User profile name for parameter USER not found.
Severity
30 : 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.
AMQ8169E (IBM i)
Authorization list for parameter AUTL does not exist.
Severity
30 : 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.
AMQ8170E (IBM i)
REFOBJTYPE(*OBJTYPE) and OBJTYPE(*ALL) cannot be used together.
Severity
30 : 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.
AMQ8171E (IBM i)
Authority of *AUTL is only allowed with USER(*PUBLIC).
Severity
30 : 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.
AMQ8172W (IBM i)
Already disconnected.
Severity
10 : Warning
Explanation
The MQI reason code of 2018 was returned from the IBM MQ queue manager in response to an MQDISC request issued during command processing.
Response
None.
AMQ8173I (IBM i)
No processes to display.
Severity
0 : Informational
Explanation
There are no matching processes defined on this system.
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.
AMQ8175I
IBM MQ trace for installation <insert_3> has started.
Severity
0 : Informational
Explanation
The trace for installation <insert_3> has started successfully.
Response
None.
AMQ8175I (HP NSS)
IBM MQ trace has started.
Severity
0 : Informational
Explanation
Trace has started successfully.
Response
None.
AMQ8176I
IBM MQ trace has been written.
Severity
0 : Informational
Explanation
The trace has been written successfully.
Response
None.
AMQ8177I
IBM MQ trace for installation <insert_3> has stopped.
Severity
0 : Informational
Explanation
The trace for installation <insert_3> has stopped.
Response
None.
AMQ8177I (HP NSS)
IBM MQ trace has stopped.
Severity
0 : Informational
Explanation
Trace has stopped.
Response
None.
AMQ8178E
IBM MQ trace for installation <insert_3> did not start.
Severity
30 : Error
Explanation
The trace for installation <insert_3> did not start successfully.
Response
None.
AMQ8178S (HP NSS)
IBM MQ trace did not start.
Severity
40 : Severe
Explanation
Trace did not start successfully.
Response
None.
AMQ8179E
IBM MQ trace output error.
Severity
30 : Error
Explanation
The trace was not output successfully.
Response
None.
AMQ8180E
IBM MQ trace end request failed for installation <insert_3>.
Severity
30 : Error
Explanation
Your request to end the trace for installation <insert_3> was not successful.
Response
None.
AMQ8180S (HP NSS)
IBM MQ trace end request failed.
Severity
40 : Severe
Explanation
Your request to end trace was not successful.
Response
None.
AMQ8181W (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.
AMQ8182I
IBM MQ trace for installation <insert_3> already off.
Severity
0 : Informational
Explanation
An attempt was made to set trace for installation <insert_3> off, but the trace is not active.
Response
None.
AMQ8182I (HP NSS)
IBM MQ trace already off.
Severity
0 : Informational
Explanation
An attempt was made to set trace off, but trace is not active.
Response
None.
AMQ8183I
IBM MQ trace already running for installation <insert_3>.
Severity
0 : Informational
Explanation
An attempt was made to start trace for installation <insert_3>, but trace is already running.
Response
The existing settings for the trace collection have been updated.
AMQ8183I (HP NSS)
IBM MQ trace already running.
Severity
0 : Informational
Explanation
An attempt was made to start trace, but trace is already running.
Response
The existing settings for the trace collection have been updated.
AMQ8184E
Requested job cannot be found
Severity
20 : Error
Explanation
The job specified cannot be found in the table that controls IBM MQ for IBM i trace. As a result no trace action can be performed.
Response
Specify an appropriate job name.
AMQ8185S (IBM i)
Operate system object already exists.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8186S (IBM i)
Image not available for IBM MQ object <insert_5>.
Severity
40 : Severe
Explanation
The object <insert_5> type <insert_3> cannot be recreated 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 recreated.
Response
Bring the relevant logs online, and try the command again.
AMQ8187S (IBM i)
IBM MQ object <insert_5> is currently open.
Severity
40 : Severe
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.
AMQ8188S (IBM i)
Insufficient authorization to IBM MQ object <insert_5>.
Severity
40 : Severe
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.
AMQ8189S (IBM i)
IBM MQ object <insert_3> is damaged.
Severity
40 : Severe
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.
AMQ8190E
<insert_3> succeeded on <insert_1> objects and failed on <insert_2> objects.
Severity
30 : 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.
The request to end the command server was unsuccessful because the command server is already stopped.
Response
None.
AMQ8197E (IBM i)
Deleted IBM 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.
AMQ8198E (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.
AMQ8199E (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.
AMQ8200S (IBM i)
MODENAME only allowed with TRPTYPE(*LU62).
Severity
40 : Severe
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.
AMQ8201S (IBM i)
TPGMNAME only allowed with TRPTYPE(*LU62).
Severity
40 : Severe
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.
AMQ8202E
TMQNAME only allowed with channel type *SDR or *SVR.
Severity
30 : 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.
AMQ8203S (IBM i)
CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN and *CLUSRCVR
Severity
40 : Severe
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.
AMQ8204E
MCANAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or *CLUSRCVR
Severity
30 : 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.
AMQ8205E
DSCITV only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR, *SVR or *SVRCN.
Severity
30 : 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, *SVR or *SVRCN. Then try the command again.
AMQ8206E
SHORTRTY only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Severity
30 : 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.
AMQ8207E
SHORTTMR only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Severity
30 : 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.
AMQ8208E
LONGRTY only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Severity
30 : 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.
AMQ8209E
LONGTMR only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Severity
30 : 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.
AMQ8210E
PUTAUT only allowed with channel type *RCVR, *RQSTR or *CLUSRCVR
Severity
30 : 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.
AMQ8211E
BATCHINT only allowed with channel type *SDR or *SVR.
Severity
30 : 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.
AMQ8212S (IBM i)
TPGMNAME parameter required with TRPTYPE(*LU62).
Severity
40 : Severe
Explanation
A required parameter was not specified.
Response
Enter a value for parameter TPGMNAME.
AMQ8213S (IBM i)
TMQNAME parameter required with channel type *SDR or *SVR.
Severity
40 : Severe
Explanation
The TMQNAME parameter must be specified with channel type *SDR or *SVR.
Response
Enter a value for parameter TMQNAME.
AMQ8214E
CONNAME parameter missing.
Severity
30 : 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.
AMQ8214S (IBM i)
CONNAME parameter missing.
Severity
40 : Severe
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.
AMQ8215S (IBM i)
CVTMSG only allowed with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8216S (IBM i)
MODENAME only allowed with TRPTYPE(*LU62).
Severity
40 : Severe
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.
AMQ8217S (IBM i)
CONNAME only allowed with channel type *SDR, *SVR, *RQSTR, *CLUSSDR or CLUSRCVR.
Severity
40 : Severe
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.
AMQ8218E (IBM i)
The system cannot accept the combination of parameters entered.
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.
AMQ8221W (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.
AMQ8222S (IBM i)
The data sent and received by the PNGMQMCHL command was not identical.
Severity
40 : Severe
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.
Correct the IBM MQ channel name and then try the command again.
AMQ8237S (IBM i)
NPMSPEED only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Severe
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.
AMQ8238E (IBM i)
Queue manager connection already open.
Severity
30 : 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.
AMQ8239S (IBM i)
LOCLADDR not valid for channel type *RCVR or *SVRCN.
Severity
40 : Severe
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.
AMQ8240S (IBM i)
Unexpected error <insert_1> in <insert_3>.
Severity
40 : Severe
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 MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ8241S (IBM i)
Unexpected message format <insert_3> received.
Severity
40 : Severe
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.
AMQ8242E
SSLCIPH definition wrong.
Severity
30 : Error
Explanation
The value provided in the SSLCIPH parameter was either unrecognized or has been disabled or deprecated.
Response
Check product documentation to confirm that the CipherSpec specified in the SSLCIPH parameter is valid.
Check whether the default set of CipherSpecs has been modified either using the AMQ_ALLOWED_CIPHERS environment variable or via the AllowedCipherSpecs attribute in the SSL stanza of the qm.ini or mqclient.ini (as appropriate for this environment).
Note that IBM may need to deprecate the use of CipherSpecs via product maintenance in response to a security vulnerability, for example all CipherSpecs that use the SSLv3 and TLSv1 protocol have been deprecated. Continued use of deprecated protocols is not recommended but may be enabled by setting environment variable AMQ_SSL_V3_ENABLE=TRUE or AMQ_TLS_V1_ENABLE=TRUE as required.
If the requested CipherSpec is a TLS 1.3 CipherSpec then we must enable TLS 1.3. To enable TLS 1.3 set the INI variable AllowTLSV13=TRUE in the SSL stanza of the mqclient.ini and qm.ini files.
Correct the SSLCIPH definition and try the command again.
AMQ8243E
SSLPEER definition wrong.
Severity
30 : 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.
AMQ8245W
Entity <insert_3> has insufficient authority to display object <insert_4>.
Severity
10 : Warning
Explanation
The specified entity is not authorized to display the required object. The following requested permissions are unauthorized: dsp
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.
AMQ8249E
The operation could not be completed because another HA or DR operation is in progress.
Severity
20 : Error
Explanation
The operation could not be completed because another HA or DR operation is in progress.
Response
Retry the operation once the existing HA or DR operation has completed.
AMQ8250I
The <insert_1>-bit <insert_3> component is not installed.
Severity
0 : Informational
Explanation
dspmqver cannot report the version for a component which is not installed.
Response
None.
AMQ8251E
The <insert_1>-bit <insert_3> component could not be loaded due to error <insert_2>. Its version number cannot be determined.
Severity
30 : Error
Explanation
dspmqver cannot report the version for a component due to an error.
Response
None.
AMQ8266I (IBM i)
No objects to display.
Severity
0 : Informational
Explanation
There are no objects with the specified name and type.
Response
None.
AMQ8276I
Display Connection details.
Severity
0 : Informational
Explanation
The DISPLAY CONN command completed successfully. Details follow this message.
AMQ8277E
Object <insert_3> changed.
Severity
20 : Error
Explanation
The definition of IBM MQ object <insert_3> has been changed since it was opened, invalidating the command.
Response
Retry the command.
AMQ8278S (IBM i)
Maximum handle limit reached.
Severity
40 : Severe
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.
AMQ8280E (IBM i)
Queue does not exist.
Severity
30 : 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 we are attempting to display a queue of type *ALS, check the queue definition references an existing queue definition.
AMQ8282E (IBM i)
Queue manager <insert_3> is not defined on the connected queue manager.
Severity
30 : 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>.
AMQ8284S (IBM i)
This user is not authorized to queue <insert_3>.
Severity
40 : Severe
Explanation
Queue <insert_3> (queue manager <insert_4>) has not been authorized for the use.
Response
Have queue <insert_3> authorized for the 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.
AMQ8287I (IBM i)
No channels with status to display.
Severity
0 : Informational
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.
AMQ8288S (IBM i)
Not authorized to command <insert_1>
Severity
40 : Severe
Explanation
You are not authorized to perform the requested operation for IBM MQ command <insert_1>.
Response
Obtain the necessary authority from the IBM MQ administrator. Then try the command again.
AMQ8289S (IBM i)
You are not authorized to the IBM MQ command.
Severity
40 : Severe
Explanation
You are not authorized to the IBM 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)
AMQ8291W (IBM i)
IBM 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 we want to change the settings, turn remote trace off and then turn it on again with appropriate settings.
AMQ8294W (IBM i)
IBM 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.
AMQ8295S (IBM i)
IBM MQ object not secured by authorization list.
Severity
40 : Severe
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.
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.
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.
AMQ8298E
Error report generated for MQSC command process.
Severity
30 : 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.
AMQ8299S (IBM i)
Cannot open <insert_3> for MQSC process.
Severity
40 : Severe
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.
AMQ8300E (IBM i)
Too many exit programs/user data fields defined.
Severity
30 : 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 and/or user data fields defined.
Response
Re-define the channel so that a total of six exit programs and/or user data fields are defined.
AMQ8301T (IBM i)
IBM MQ storage monitor job could not be started.
Severity
50 : Terminating
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.
AMQ8304E
Tracing cannot be started. Too many traces are already running.
Severity
30 : 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.
AMQ8306S (IBM i)
BATCHSIZE only allowed with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Severe
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.
AMQ8307S (IBM i)
SEQNUMWRAP only allowed with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Severity
40 : Severe
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.
AMQ8308S (IBM i)
MSGRTYEXIT only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Severe
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.
AMQ8309S (IBM i)
MSGRTYDATA only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Severe
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.
AMQ8310S (IBM i)
MSGRTYNBR only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Severe
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.
AMQ8311S (IBM i)
MSGRTYITV only allowed with channel type *CLUSRCVR, *RCVR or *RQSTR.
Severity
40 : Severe
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.
AMQ8312S (IBM i)
CLUSTER only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Severe
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.
AMQ8313S (IBM i)
CLUSNL only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Severe
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.
AMQ8314S (IBM i)
DEFBIND only allowed with queue type *ALS, *LCL and *RMT.
Severity
40 : Severe
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.
There are no matching namelists defined on this system.
Response
Use the Create Namelist (CRTMQMNL) command to create a namelist.
AMQ8316I (IBM i)
No cluster queue managers to display.
Severity
0 : Informational
Explanation
There are no matching cluster queue managers defined on this system.
Response
None.
AMQ8317S (IBM i)
CLUSTER only allowed with channel type *CLUSSDR and *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8318S (IBM i)
CLUSNL only allowed with channel type *CLUSSDR and *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8319S (IBM i)
MSGEXIT only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8320S (IBM i)
MSGUSRDATA only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, or *CLUSSDR or *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8321I (IBM i)
Process <insert_3> is still running.
Severity
0 : Informational
AMQ8322S (IBM i)
TIMEOUT only allowed with ENDCCTJOB(*YES).
Severity
40 : Severe
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 we want to fully quiesce the queue manager, change the ENDCCTJOB parameter to *YES. Then try the command again.
AMQ8323S (IBM i)
OPTION(*PREEMPT) must not be used with ENDCCTJOB(*YES).
Severity
40 : Severe
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 we 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.
AMQ8324S (IBM i)
OPTION(*WAIT) not allowed with MQMNAME(*ALL).
Severity
40 : Severe
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.
AMQ8325S (IBM i)
MQMNAME(*ALL) is not allowed with ENDCCTJOB(*NO).
Severity
40 : Severe
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.
AMQ8326E
Maximum number of AUTHINFO definitions reached.
Severity
30 : Error
Explanation
The maximum number of AUTHINFO definitions has been reached.
Response
None.
AMQ8330I
Running
Severity
0 : Informational
AMQ8331I
Ended normally
Severity
0 : Informational
AMQ8332I
Ended immediately
Severity
0 : Informational
AMQ8333I
Ended preemptively
Severity
0 : Informational
AMQ8334I
Ended unexpectedly
Severity
0 : Informational
AMQ8335I
Starting
Severity
0 : Informational
AMQ8336I
Quiescing
Severity
0 : Informational
AMQ8337I
Ending immediately
Severity
0 : Informational
AMQ8338I
Ending preemptively
Severity
0 : Informational
AMQ8339I
Being deleted
Severity
0 : Informational
AMQ8340I
Status not available
Severity
0 : Informational
AMQ8341I
SUBPOOL(<insert_3>)<insert_4>PID(<insert_1>)
Severity
0 : Informational
AMQ8342I (IBM i)
No authorities to display.
Severity
0 : Informational
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..
AMQ8345S (IBM i)
BATCHHB not valid for channel type *RCVR, *RQSTR, *SVRCN or *CLTCN.
Severity
40 : Severe
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.
AMQ8346S (IBM i)
Parameter mismatch between QMNAME and QMID.
Severity
40 : Severe
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.
AMQ8347S (IBM i)
USERID not valid for channel type *RCVR, *SVRCN or *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8348S (IBM i)
PASSWORD not valid for channel type *RCVR, *SVRCN or *CLUSRCVR.
Severity
40 : Severe
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.
AMQ8349S (IBM i)
Authority changes to <insert_3> failed.
Severity
40 : Severe
Explanation
Authority changes to an object were requested but could not be made.
Response
Check the authorities that we are granting are relevant to the object type of <insert_3>.
AMQ8350I
Usage: dspmqver [([-a] [-b] [-p Components] [-f Fields] [-v]) | -i]
-a All components and fields.
-b Omit header information from the report.
-f Fields, either one or a sum of the following:
1=Name, 2=Version, 4=Level, 8=Build type,
16=Platform, 32=Addressing mode, 64=Operating system,
128=Installation path, 256=Installation description,
512=Installation name, 1024=Maximum command level,
2048=Primary installation, 4096=Data path,
8192=License Type
-i Display IBM MQ installations.
-p Components, either one or a sum of the following:
1=Server or client, 2=Java, 4=JMS, 16=WCF,
32=XMS, 64=GSKit, 128=AMS, 256=AMQP, 512=MQXR,
1024=Other, 2048=WebSphere Liberty Profile,
4096=Java Runtime Environment, 8192=RDQM,
16384=Managed File Transfer
-v Display verbose output.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8350I (HP NSS)
Usage: dspmqver [-a] [-b] [-p Components] [-f Fields] [-v]
-a All components and fields.
-b Omit header information from the report.
-f Fields, either one or a sum of the following:
1=Name, 2=Version, 4=Level, 8=Build type,
16=Platform, 32=Addressing mode, 64=Operating system,
128=Installation path,
4096=Data path
-p Components, either one or a sum of the following:
1=Server or client, 4=JMS, 64=SSL
-v Display verbose output.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8350I (IBM MQ Appliance)
Usage: dspmqver [-a] [-b] [-p Components] [-f Fields] [-v]
-a All components and fields.
-b Omit header information from the report.
-f Fields, either one or a sum of the following:
1=Name, 2=Version, 4=Level, 8=Build type,
16=Platform, 32=Reserved, 64=Reserved,
128=Reserved, 256=Reserved, 512=Reserved,
1024=Maximum command level, 2048=Reserved,
4096=Reserved, 8192=License Type
-p Components, either one or a sum of the following:
1=Server or client, 2=Java, 4=JMS, 8=Reserved,
16=Reserved, 32=Reserved, 64=GSKit, 128=AMS
-v Display verbose output.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8350I (IBM i)
Usage: dspmqver [-a] [-b] [-p Components] [-f Fields] [-v]
-a All components and fields.
-b Omit header information from the report.
-f Fields, either one or a sum of the following:
1=Name, 2=Version, 4=Level, 8=Build type,
16=Platform, 32=Addressing mode, 64=Operating system,
1024=Maximum command level
-p Components, either one or a sum of the following:
1=Server or client, 2=Java, 4=JMS, 16=WCF,
32=XMS, 128=AMS, 1024=Other
-v Display verbose output.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8351E
The IBM MQ Java environment has not been configured correctly, or the IBM MQ JRE feature has not been installed.
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, possibly because the IBM MQ JRE component has not been installed, or the IBM MQ Java environment variables have not been set up. The command could not be run successfully.
Response
Ensure that we have a working JRE (Java Runtime Environment) and that the IBM MQ Java environment variables have been set using the setjmsenv script. If the IBM MQ JRE component isn't installed then consider installing it. Retry the command.
AMQ8352I
IBM MQ queue manager <insert_5> becoming the active instance.
Severity
0 : Informational
Explanation
The standby instance of queue manager instance <insert_5> is becoming the active instance.
Response
None.
AMQ8353I
Quiesce request accepted. The queue manager will stop when all outstanding work is complete, permitting switchover to a standby instance.
Severity
0 : Informational
Explanation
We 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. If there is a standby queue manager instance, it is permitted to become the active queue manager instance once this active instance has ended.
Response
None.
AMQ8354I
IBM MQ queue manager <insert_5> ended, permitting switchover to a standby instance.
Severity
0 : Informational
Explanation
IBM MQ queue manager <insert_5> ended. If there is a standby queue manager instance, it is permitted to become the active queue manager instance.
Response
None.
AMQ8355E
IBM MQ standby queue manager instance <insert_5> not permitted to become the active instance.
Severity
20 : Error
Explanation
IBM MQ standby queue manager instance <insert_5> obtained a lock on its data in the file-system but was not permitted to become the active instance. The most likely cause is that the active queue manager instance was stopped without permitting a switchover.
Response
None.
AMQ8356I
Not applicable
Severity
0 : Informational
AMQ8357I
Permitted
Severity
0 : Informational
AMQ8358I
Not permitted
Severity
0 : Informational
AMQ8359E (Windows)
The required version of the Microsoft .NET Framework could not be located.
Severity
20 : Error
Explanation
A command was issued that attempted to run a .NET application. However an acceptable version of the Microsoft .NET Framework was not found. Typically IBM MQ requires at least version 2.0 of the Microsoft .NET Framework to run .NET applications. The command could not be run successfully.
Response
Ensure that we have at least version 2.0 of the Microsoft .NET Framework installed and configured for the environment. Retry the command.
AMQ8360I
Running as standby
Severity
0 : Informational
AMQ8361I
Running elsewhere
Severity
0 : Informational
AMQ8362W
<insert_3> authority not granted to the <insert_4> group for reason <insert_1>.
Severity
10 : Warning
Explanation
As part of queue manager migration an attempt was made to grant <insert_3> authority to the <insert_4> group for the queue manager object. That attempt failed for reason <insert_1>.
Response
An administrator should determine the cause of failure and then use the setmqaut command to manually grant <insert_3> authority to the <insert_4> group for the queue manager object.
AMQ8363I
The tests on the directory completed successfully.
Severity
0 : Informational
Explanation
The program performed a series of tests on the directory supplied. The tests check for known, easily diagnosable problems which would prevent use of the directory by IBM MQ as a queue manager's data or log directory.
Response
The directory appears usable by a IBM MQ queue manager.
AMQ8364E
Environment variable <insert_3> must not be used with standby queue manager instances.
Severity
20 : Error
Explanation
The environment variable changes the behaviour of IBM MQ in such a way as to prevent standby queue manager instances from functioning correctly.
Response
To use standby queue manager instances, remove the environment variable and repeat the command. For to use the environment variable, we cannot use standby queue manager instances.
AMQ8365I
Active
Severity
0 : Informational
AMQ8366I
Standby
Severity
0 : Informational
AMQ8367E
Active instance of IBM MQ queue manager <insert_3> not ended.
Severity
20 : Error
Explanation
You tried to end the local instance of IBM MQ queue manager <insert_3> using the '-x' option, which ends a standby instance. The local instance is not a standby instance.
IBM MQ standby queue manager instance <insert_3> ended.
Severity
0 : Informational
Explanation
The standby instance of IBM MQ queue manager <insert_3> ended.
Response
None.
AMQ8370I
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]
-a .NET assembly name.
-b Backout threshold for messages retrieved from the application queue.
-c Name of the .NET class that implements the IMQObjectTrigger interface.
-d Use data conversion to retrieve messages:
YES, NO.
-m Queue manager name.
-n Maximum number of active worker threads.
-p Pass context when backing out a message:
NONE, IDENTITY, ALL.
-q Name of the application queue to monitor.
-r Queue name for requeuing messages which reach the backout threshold.
-s Use syncpoint to retrieve messages:
YES, NO, PERSISTENT.
-t Time in seconds to wait for further messages.
-u User-defined data to pass to the Execute method.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8371S
<insert_3> is not a valid command line option.
Severity
40 : Severe
Explanation
The option <insert_3> was specified on the command line to the application however this is not one of the valid set of command line options.
Response
Check the usage information for the application and then retry.
AMQ8372S
The required command line option <insert_3> is missing.
Severity
40 : Severe
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.
AMQ8373S
Invalid value specified for command line option <insert_3> (<insert_4>).
Severity
40 : Severe
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.
AMQ8374S
IBM MQ queue manager <insert_3> does not exist.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8375S
IBM MQ queue manager <insert_3> not available.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8376S
IBM MQ queue <insert_3> not found.
Severity
40 : Severe
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.
AMQ8377S
Unexpected error <insert_1> was received by the application.
Severity
40 : Severe
Explanation
The error <insert_1> was returned unexpectedly to the application.
The IBM 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>
No classes implementing IMQObjectTrigger found in <insert_3>.
Severity
40 : Severe
Explanation
The IBM 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 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.
AMQ8381S
Too many classes implementing IMQObjectTrigger (<insert_1>) found in <insert_3>.
Severity
40 : Severe
Explanation
The IBM 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 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.
AMQ8382W
A Message breaking the backout threshold (<insert_1>) was moved to <insert_4>
Severity
10 : Warning
Explanation
Whilst processing queue <insert_3> a message whose backout count 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). We 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.
AMQ8383S
A Message breaking the backout threshold (<insert_1>) could not be moved.
Severity
40 : Severe
Explanation
While processing queue <insert_3> a message whose backout count 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.
-n Connection Name as localhost(port).
-c Channel Name.
-m Queue manager name.
-i For Heuristic completion of transactions, where transaction outcome will be decided by user independent of
Transaction Manager's log
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8385E (Windows)
An Internal MQ Operation <insert_3> has failed with returnCode <insert_1>.
IBM MQ .NET XA Recovery Monitor ended. Press any key to exit.
Severity
0 : Informational
Response
None.
AMQ8388W (Windows)
Another instance of WmqDotnetXAMonitor is already running on this computer, ProcessId: <insert_1>.
Severity
10 : Warning
Response
Please wait until the current instance ends before starting a new instance of WmqDotnetXAMonitor.
AMQ8389I (Windows)
Current Transaction under Recovery:
Distributed TransactionId : <insert_3>
Local Transaction Id : <insert_4>
Provide input as "commit" to Commit Transaction Or "rollback" to Rollback Transaction :
Severity
0 : Informational
Response
None.
AMQ8390I
Usage: endmqdnm -q Queue [-m QueueManager]
-m Queue manager name.
-q Name of the application queue being monitored.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8391S
<insert_3> is not a valid command line option.
Severity
40 : Severe
Explanation
The option <insert_3> was specified on the command line to the application however this is not one of the valid set of command line options.
Response
Check the usage information for the application and then retry.
AMQ8392S
The required command line option <insert_3> is missing.
Severity
40 : Severe
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.
AMQ8393S
Invalid value specified for command line option <insert_3> (<insert_4>).
Severity
40 : Severe
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.
AMQ8394S
IBM MQ queue manager <insert_3> does not exist.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8395S
IBM MQ queue manager <insert_3> not available.
Severity
40 : Severe
Explanation
The IBM 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.
AMQ8396S
IBM MQ queue <insert_3> not found.
Severity
40 : Severe
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.
AMQ8397S
Unexpected error <insert_1> was received by the application.
Severity
40 : Severe
Explanation
The error <insert_1> was returned unexpectedly to the application.
Target shutdown time for queue manager already established.
Severity
20 : Error
Explanation
An endmqm command with the -t or -tp option has already set a target time in which the queue manager should attempt to shutdown. Once such a time has been established it cannot be modified by a further endmqm command.
Response
The shutdown type can still be manually promoted through use of endmqm with the -i or -p options, without the -t or -tp options.
The MQSC script contains <insert_1> commands having a syntax error.
Response
None.
AMQ8403I
<insert_1> valid MQSC commands could not be processed.
Severity
0 : Informational
Explanation
The MQSC script contains <insert_1> commands that failed to process.
Response
None.
AMQ8404E
Command failed.
Severity
20 : Error
Explanation
An MQSC command has been recognized, but cannot be processed.
Response
None.
AMQ8405I
Syntax error detected at or near end of command segment below:-
Severity
0 : Informational
Explanation
The MQSC script contains <insert_1> commands having a syntax error.
Response
None.
AMQ8406I
Unexpected 'end of input' in MQSC.
Severity
0 : Informational
Explanation
An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command.
Response
None.
AMQ8407I
Display Process details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY PROCESS command completed successfully, and details follow this message.
Response
None.
AMQ8408I
Display Queue Manager details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY QMGR command completed successfully, and details follow this message.
Response
None.
AMQ8409I
Display Queue details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY QUEUE command completed successfully, and details follow this message.
Response
None.
AMQ8410I
Parser Error.
Severity
0 : Informational
Explanation
The MQSC Parser has an internal error.
Response
None.
AMQ8411I
Duplicate Keyword Error.
Severity
0 : Informational
Explanation
A command in the MQSC script contains duplicate keywords.
Response
None.
AMQ8412I
Numeric Range Error.
Severity
0 : Informational
Explanation
The value assigned to an MQSC command keyword is out of the permitted range.
Response
None.
AMQ8413E
String Length Error.
Severity
20 : Error
Explanation
A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword.
Response
None.
AMQ8414I
Display Channel details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY CHL command completed successfully, and details follow this message.
Response
None.
AMQ8415I
Ping IBM MQ Queue Manager command complete.
Severity
0 : Informational
Explanation
The MQSC PING QMGR command completed successfully.
Response
None.
AMQ8416I
MQSC timed out waiting for a response from the command server to queue <insert_4>.
Severity
0 : Informational
Explanation
MQSC did not receive a response message from the remote command server in the time specified.
Response
Examine the queue manager error logs to determine the cause of the timeout and check for errors against queue <insert_4>.
AMQ8417I
Display Channel Status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message.
Response
None.
AMQ8418I
<insert_1> command responses received.
Severity
0 : Informational
Explanation
Running in queued mode, <insert_1> command responses were received from the remote command server.
Response
None.
AMQ8419E
The queue is already in the DCE cell.
Severity
30 : Error
Explanation
The SCOPE attribute of the queue already has the value CELL.
Response
None.
AMQ8420I
Channel Status not found.
Severity
0 : Informational
Explanation
No status was found for the specified channel(s).
Response
None.
AMQ8421E
A required keyword was not specified.
Severity
20 : Error
Explanation
A keyword required in this command was not specified.
Response
None.
AMQ8422I
MQSC found the following response to a previous command on the reply q :-
Severity
0 : Informational
Explanation
MQSC found additional command responses on the reply q. They will fill follow this message.
Response
None.
AMQ8423E
Cell Directory not available.
Severity
30 : Error
Explanation
The DCE cell directory is not available, so the requested operation has failed.
Response
None.
AMQ8424E
Error detected in a name keyword.
Severity
20 : Error
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.
AMQ8425E
Attribute value error.
Severity
20 : Error
Explanation
A keyword in an MQSC command contained a value that was not valid.
The text shown is the valid syntax for the MQSC command.
Response
None.
AMQ8428I
TYPE Keyword has already been specified.
Severity
0 : Informational
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.
AMQ8429E (IBM MQ Appliance)
User exits and services are not supported.
Severity
20 : Error
Explanation
User exits and services are not supported on this platform.
Response
None.
AMQ8429E (IBM i)
Error detected in a exit parameter.
Severity
20 : Error
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.
AMQ8430E
Remote queue manager name is unknown.
Severity
20 : Error
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.
You are not allowed to set both the REPOS and REPOSNL fields.
Severity
30 : Error
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.
AMQ8433E
You are not allowed to set both the CLUSTER and CLUSNL fields.
Severity
30 : Error
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.
AMQ8434E
The repository is unavailable.
Severity
30 : Error
Explanation
The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager.
The MQSC script contains no commands having a syntax error.
Response
None.
AMQ8440I
One command has a syntax error.
Severity
0 : Informational
Explanation
The MQSC script contains one command which has a syntax error.
Response
None.
AMQ8441I
Display Cluster Queue Manager details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY CLUSQMGR command completed successfully, and details follow this message.
Response
None.
AMQ8442E
USAGE can not be set to XMITQ with either the CLUSTER or CLUSNL fields set.
Severity
30 : Error
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.
AMQ8442I (IBM i)
USAGE can not be set to *TMQ with either the CLUSTER or CLUSNL fields set.
Severity
0 : Informational
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.
AMQ8443I (IBM i)
Only the CLUSTER or CLUSNL field may have a value.
Severity
0 : Informational
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.
AMQ8444I (IBM i)
The CLUSTER or CLUSNL fields must have a value.
Severity
0 : Informational
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.
AMQ8445E (IBM i)
Program cannot open queue manager object.
Severity
30 : Error
Explanation
An attempt to open a queue manager object has failed.
Response
See the previously listed messages in the job log.
AMQ8446E (IBM i)
Channel is currently active.
Severity
30 : Error
Explanation
The requested operation failed because the channel is currently active.
Response
See the previously listed messages in the job log.
AMQ8447E (IBM i)
Requested operation on channel <insert_3> not valid for this channel type.
Severity
30 : 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.
AMQ8448E (IBM i)
Channel <insert_3> is not running.
Severity
30 : Error
Explanation
A request to end 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.
An MQGET failed because the queue <insert_3> had been previously inhibited for MQGET.
Response
None.
AMQ8450I
Display queue status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY QSTATUS command completed successfully. Details follow this message.
AMQ8451I (IBM i)
STATUS(*STOPPED) not allowed with CONNAME specified.
Severity
0 : Informational
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.
AMQ8452I (IBM i)
STATUS(*STOPPED) not allowed with RQMNAME specified.
Severity
0 : Informational
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.
AMQ8453E
The path <insert_3> is invalid
Severity
20 : Error
Explanation
You typed a path which was not syntactically correct for the operating system we are running IBM MQ on.
Response
Determine the correct syntax of a path name for the operating system we are running IBM MQ on and use this information to type in a valid path.
AMQ8454E
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 MQ for this parameter.
Response
Carefully check the data entered for this parameter in conjunction with the IBM MQ Command Reference to determine the cause of error.
AMQ8455E
Password length error
Severity
20 : Error
Explanation
The password string length is rounded up by IBM 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.
AMQ8456E
Conflicting parameters in command.
Severity
20 : Error
Explanation
The command contains parameters that cannot be used together.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8457I
IBM MQ connection stopped.
Severity
0 : Informational
Explanation
The STOP CONN command successfully stopped the connection that was specified.
Response
None.
AMQ8458E
IBM MQ connection not stopped.
Severity
30 : Error
Explanation
The STOP CONN command could not stop the connection that was specified.
Response
None.
AMQ8459I
Not found.
Severity
0 : Informational
Explanation
No data was found that matched the identified you specified.
Response
None.
AMQ8460I
Syntax error in connection identifier.
Severity
0 : Informational
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.
AMQ8461I
Connection identifier not found.
Severity
0 : Informational
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.
AMQ8462E
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.
AMQ8463E
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.
AMQ8464E
IBM MQ subscription <insert_3> not found.
Severity
30 : 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 we are creating a new subscription, either specify all parameters explicitly or ensure that the system default subscription, SYSTEM.DEFAULT.SUB, exists.
AMQ8465E
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.
There was a syntax error in the hex string representing the bytes value of a keyword.
Severity
0 : Informational
Explanation
The hex string that was entered was found to contain a syntax error. This error may occur for one of the following reasons: o The string was too long o 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, e.g. DESTCORL(A) will be interpreted as DESTCORL(0A)
Response
None.
AMQ8468E
DESTCLAS(MANAGED) must not be specified with DEST, DESTQMGR or DESTCORL.
Severity
30 : Error
Explanation
When using DESTCLAS(MANAGED), a destination or destination correlation ID must not be specified. If these are required then DESTCLAS(PROVIDED) should be used.
Response
None.
AMQ8469E
IBM MQ subscription <insert_3> in use.
Severity
30 : 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.
AMQ8470E
The object <insert_3> is not a valid subscription destination.
Severity
30 : 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.
AMQ8471E
IBM MQ topic string error
Severity
30 : Error
Explanation
The topic string (TOPICSTR) supplied was not valid
Response
Correct the topic string definition and try the command again.
AMQ8472E
IBM MQ topic string not found
Severity
30 : Error
Explanation
The topic string supplied does not exist in the topic tree
Response
Correct the topic string used and try the command again
AMQ8473E
A IBM MQ topic using the supplied topic string already exists
Severity
30 : 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.
AMQ8474E
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.
AMQ8475E
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.
AMQ8476E
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.
AMQ8477E
The specified options are invalid.
Severity
30 : Error
Explanation
The combination of options supplied for the command are invalid.
Response
Check the specified options and ensure they are correct.
AMQ8478E
Standby queue manager.
Severity
30 : Error
Explanation
The queue manager is a standby queue manager instance. We must use the active instance of a queue manager to administer it.
Response
Re-issue the command using the active instance of the queue manager.
AMQ8479E
Selector will never select a message.
Severity
20 : Error
Explanation
A selection string was specified but it will never select a message as it always evaluates to false.
Response
Make any necessary corrections to the logic of the selection string and then attempt to create the subscription again.
AMQ8480E
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 MQ Messages manual, correct the underlying problem and then try the command again.
AMQ8481E
The channel was not started.
Severity
20 : Error
Explanation
The channel was not started.
Response
None.
AMQ8482E
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 wish to enable publish/subscribe clustering, modify the PSCLUS attribute to ENABLED on all queue managers participating in the cluster.
AMQ8483E
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 wish to disable publish/subscribe activity within this cluster, first DELETE all cluster topic objects, then remodify the PSCLUS attribute.
AMQ8484I
The SSL Key Store is invalid.
Severity
0 : Informational
Explanation
The SSL Key Store is invalid.
Response
None.
AMQ8485I
The cipher suite is not supported.
Severity
0 : Informational
Explanation
The cipher suite is not supported.
Response
None.
AMQ8486E
Telemetry commands are not available.
Severity
30 : Error
Explanation
The Telemetry Service 'SYSTEM.MQXR.SERVICE' is not running.
Response
Make sure that the Telemetry component is installed and that the Queue Manager is configured for Telemetry so that the Telemetry Service 'SYSTEM.MQXR.SERVICE' is running.
AMQ8487I
There was a socket error.
Severity
0 : Informational
Explanation
There was a socket error.
Response
Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.
AMQ8488I
Bind failed.
Severity
0 : Informational
Explanation
Bind failed.
Response
Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.
AMQ8489I
The host is not available.
Severity
0 : Informational
Explanation
The host is not available.
Response
Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.
AMQ8490I
The clientId is invalid.
Severity
0 : Informational
Explanation
The clientId is invalid.
Response
Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.
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
AMQ8492I
The number of responses has been limited to <insert_1>
Severity
0 : Informational
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 or AMQP Service by using a where clause, or increase the MAXDEPTH of the ReplyToQueue 'SYSTEM.MQSC.REPLY.QUEUE'
AMQ8493I
Enter password:
Severity
0 : Informational
AMQ8494E
AMQP commands are not available.
Severity
30 : Error
Explanation
The AMQP Service 'SYSTEM.AMQP.SERVICE' is not running.
Response
Make sure that the AMQP component is installed and that the Queue Manager is configured for AMQP so that the service 'SYSTEM.AMQP.SERVICE' is running.
AMQ8495E
Configuration failed, invalid attribute for an administrative topic string
Severity
20 : Error
Explanation
The topic object applies to the admin topic tree starting $SYS/MQ. Some attributes of topic objects configured within this branch of the topic tree are restricted to certain values at certain points. Restricted attributes include CLUSTER, WILDCARD, PROXYSUB and MCAST.
Response
Modify the configuration to comply with the restrictions as described in the product documentation.
AMQ8496I
Timeout waiting for a reply from the AMQP service.
Severity
0 : Informational
Explanation
Timeout waiting for a reply from the AMQP Service 'SYSTEM.AMQP.SERVICE'
Response
Reduce the number of responses expected from the AMQP Service by using a where clause
AMQ8497I
Starting local MQSC for <insert_3>.
Severity
0 : Informational
AMQ8498I
Starting MQSC for queue manager <insert_3>.
Severity
0 : Informational
Explanation
The MQSC script contains <insert_1> commands.
Response
None.
AMQ8499I
Usage: runmqsc [-e] [-v] [-c] [-n] [-u UserName] [-w WaitTime [-x]
[-f Filename] [-m LocalQMgrName]] [QMgrName]
-c Client connection to queue manager.
-e Do not echo MQSC commands into the output.
-f File to read commands from.
-m Local queue manager used to send commands to the target.
-n Do not connect to a queue manager.
-u User name for authentication.
-v Verify commands without performing the actions.
-w Run the MQSC commands on another queue manager.
-x Target queue manager is on z/OS.
Severity
0 : Informational
AMQ8499I (IBM MQ Appliance)
Usage: runmqsc [-e] [-v] [-u UserName] [-w WaitTime [-x]
[-f Filename] [-m LocalQMgrName]] [QMgrName]
-e Do not echo MQSC commands into the output.
-f URI to read commands from.
-m Local queue manager used to send commands to the target.
-u User name for authentication.
-v Verify commands without performing the actions.
-w Run the MQSC commands on another queue manager.
-x Target queue manager is on z/OS.
Severity
0 : Informational
AMQ8500I
IBM MQ Display MQ Files
Severity
0 : Informational
AMQ8501S
Common services initialization failed with return code <insert_1>.
Severity
40 : Severe
Explanation
A request by the command server to initialize common services failed with return code <insert_1>.
Response
None.
AMQ8502S
Connect shared memory failed with return code <insert_1>.
Severity
40 : Severe
Explanation
A request by the command server to connect shared memory failed with return code <insert_1>.
Response
None.
AMQ8503S
Post event semaphore failed with return code <insert_1>.
Severity
40 : Severe
Explanation
A request by the command server to post an event semaphore failed with return code <insert_1>.
Response
None.
AMQ8504S
Command server MQINQ failed with reason code <insert_1>.
Severity
40 : Severe
Explanation
An MQINQ request by the command server, for the IBM MQ queue <insert_3>, failed with reason code <insert_1>.
Response
None.
AMQ8505E
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.
AMQ8506S
Command server MQGET failed with reason code <insert_1>.
Severity
40 : Severe
Explanation
An MQGET request by the command server, for the IBM MQ queue <insert_3>, failed with reason code <insert_1>.
Response
None.
AMQ8507E
Command server MQPUT1 request for an undelivered message failed with reason code <insert_1>.
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.
AMQ8518E
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. You may find more information about logging in the System Administration Guide, Chapter 14: Recovery and restart.
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.
AMQ8519E
The topic object <insert_3> does not permit durable subscription.
Severity
30 : Error
Explanation
The topic object <insert_3> has been defined to disallow durable subscription.
Response
Ensure that the topic object to which we are creating a subscription allows durable subscription.
AMQ8520E
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.
AMQ8521I
Command completion and history unavailable.
Severity
0 : Informational
Explanation
The editline library could not be loaded, as such command completion and recall is not available in the runmqsc program.
Response
Ensure that libncurses is installed on this machine and available to the Queue Manager.
AMQ8521I (AIX)
Command completion and history unavailable.
Severity
0 : Informational
Explanation
The editline library could not be loaded, as such command completion and recall is not available in the runmqsc program.
Response
Ensure that libcurses is installed on this machine and available to the Queue Manager.
AMQ8549E
Total string length exceeds the maximum value of 999 characters.
Severity
20 : Error
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.
AMQ8550I
Display namelist details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message.
Response
None.
AMQ8551I
IBM MQ namelist changed.
Severity
0 : Informational
Explanation
IBM MQ namelist <insert_5> changed.
Response
None.
AMQ8552I
IBM MQ namelist created.
Severity
0 : Informational
Explanation
IBM MQ namelist <insert_5> created.
Response
None.
AMQ8553I
IBM MQ namelist deleted.
Severity
0 : Informational
Explanation
IBM MQ namelist <insert_5> deleted.
Response
None.
AMQ8554E
String List String Count Error.
Severity
20 : Error
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.
AMQ8555E
String List String Length Error.
Severity
20 : Error
Explanation
A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword.
Response
None.
AMQ8556I
RESUME QUEUE MANAGER accepted.
Severity
0 : Informational
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.
AMQ8557I
SUSPEND QUEUE MANAGER accepted.
Severity
0 : Informational
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.
AMQ8558I
REFRESH CLUSTER accepted.
Severity
0 : Informational
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.
AMQ8559I
RESET CLUSTER accepted.
Severity
0 : Informational
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.
AMQ8560I
IBM MQ security cache refreshed.
Severity
0 : Informational
Explanation
The Object Authority Manager security cache has been refreshed.
Response
None.
AMQ8561W (Windows)
Domain controller unavailable.
Severity
10 : Warning
Explanation
IBM 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 we 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.
AMQ8562W
The Java application failed to connect to the queue manager because the version of the native JNI library <insert_3> is inconsistent with the version of the IBM MQ queue manager <insert_4>.
Severity
10 : Warning
Explanation
The native JNI library <insert_3> is out-of-date compared to the IBM MQ queue manager <insert_4>
Response
Ensure that the Java library path points to the current version of the JNI library.
AMQ8563I
IBM MQ authentication information object created.
Severity
0 : Informational
Explanation
IBM MQ authentication information object <insert_3> created.
Response
None.
AMQ8564I
IBM MQ authentication information object deleted.
Severity
0 : Informational
Explanation
IBM MQ authentication information object <insert_3> deleted.
Response
None.
AMQ8565I
Queue status not found.
Severity
0 : Informational
Explanation
Queue status for the specified queue could not be found.
Response
None.
AMQ8566I
Display authentication information details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message.
Response
None.
AMQ8567I
IBM MQ authentication information changed.
Severity
0 : Informational
Explanation
IBM MQ authentication information <insert_3> changed.
Response
None.
AMQ8568W
The native JNI library <insert_3> was not found. For a client installation this is expected.
Severity
10 : Warning
Explanation
The native JNI library <insert_3> could not be loaded because the library was not found. For a client installation this is expected.
Response
Ensure that the java library path points to the location of the JNI library. It is not required for a client installation.
AMQ8568I (IBM i)
No authinfo objects to display.
Severity
0 : Informational
Explanation
There are no matching authinfo objects defined on this system.
Response
Using the DEFINE AUTHINFO command to create an authinfo object.
AMQ8569E
Error in filter specification
Severity
20 : Error
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 we are filtering on.
Response
None.
AMQ8570I
Attribute value error in <insert_3>.
Severity
0 : Informational
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.
AMQ8571W
<insert_3> authority not revoked from the <insert_4> group for reason <insert_1>.
Severity
10 : Warning
Explanation
As part of queue manager migration an attempt was made to revoke <insert_3> authority from the <insert_4> group for the <insert_5> object. That attempt failed for reason <insert_1>.
Response
An administrator should determine the cause of failure and then use the setmqaut command to manually revoke <insert_3> authority from the <insert_4> group for the <insert_5> object.
AMQ8572W
Securing IBM MQ objects against local groups may yield undesirable results.
Severity
10 : Warning
Explanation
A request was made to secure a IBM 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 MQ object against a corresponding domain group.
AMQ8573E (UNIX and Linux)
Unable to access installation config file <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to access the IBM MQ installation configuration file <insert_3> however the command was unable to access the file.
Response
Further messages may 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.
AMQ8574W
Refreshing settings for primary installation <insert_3> (<insert_4>).
Severity
10 : Warning
Explanation
A request was issued to set installation <insert_3> as the primary installation however this installation is already set as the primary installation. The command will continue and will refresh the settings which identify this installation as the primary installation.
Response
None.
AMQ8575E
Unable to access installation task file <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to access the IBM MQ installation task file <insert_3> however the command issued was unable to access the file.
Response
Further messages may 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.
AMQ8576I
<insert_3> (<insert_4>) set as the primary installation.
Severity
0 : Informational
Explanation
All tasks required to set installation <insert_3> 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_3> as the primary installation.
Response
None.
AMQ8576I (Windows)
<insert_3> (<insert_4>) set as the primary installation. We must restart the operating system to complete the update.
Severity
0 : Informational
Explanation
All tasks required to set installation <insert_3> 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_3> as the primary installation.
In order to ensure that the updates are visible machine-wide, a restart of the operating system is required.
Response
We must restart the operating system to complete the update.
AMQ8577E
Failed to set <insert_3> (<insert_4>) as the primary installation.
Severity
20 : Error
Explanation
The command attempted to set installation <insert_3> as the primary installation but one or more of the tasks required to set the installation as the primary installation failed to complete succesfully. 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.
AMQ8578E
Failed to refresh configuration for primary installation <insert_3> (<insert_4>).
Severity
20 : Error
Explanation
The command attempted to refresh the tasks required to set installation <insert_3> as the primary installation but one or more of the tasks failed to complete successfully. Installation <insert_3> 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.
AMQ8579E
Primary installation cannot be changed from <insert_4> to <insert_3>
Severity
20 : Error
Explanation
The command attempted to set installation <insert_3> as the primary installation but the operation could not be performed because installation <insert_4> is already set as the primary installation.
Response
If the current primary installation is Installation0, it is not possible to set <insert_3> to be the primary installation until Installation0 has been uninstalled.
Otherwise, in order to set installation <insert_3> as the primary installation we must first unset the current primary installation using the command 'setmqinst -x -n <InstName>'. We can then re-issue the command to set installation <insert_3> as the primary installation.
AMQ8580E
Failed to unset <insert_3> (<insert_4>) as the primary installation.
Severity
20 : Error
Explanation
The command attempted to unset installation <insert_3> as the primary installation but one or more of the tasks required to unset the installation as the primary installation failed to complete succesfully. 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.
AMQ8581E
<insert_3> (<insert_4>) is not currently set as the primary installation.
Severity
20 : Error
Explanation
The command attempted to unset installation <insert_3> as the primary installation but installation <insert_3> 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.
AMQ8582I
<insert_3> (<insert_4>) has been unset as the primary installation.
Severity
0 : Informational
Explanation
All tasks required to unset installation <insert_3> as the primary installation have been completed.
Response
None.
AMQ8583E
Installation details for <insert_3> (<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 recover the configuration file from a recent backup. Best practices suggest taking a backup of this file after each new installation is added, or old installation is deleted.
AMQ8584E
Insufficient permission to update installation configuration.
Severity
20 : Error
Explanation
An attempt was made to update the IBM MQ installation configuration for installation <insert_3> path <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.
AMQ8585E
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
AMQ8586I
Usage: setmqinst (-n InstName | -p InstPath)
(-i | -x | -d Text | -l LicenseName -e yes|no)
-d Descriptive text.
-i Set this installation as the primary installation.
-l Licensed entitlement.
-e Set or unset entitlement.
-n Installation name.
-p Installation path.
-x Unset this installation as the primary installation.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ8587I
Note there are a number (<insert_1>) of other installations, use the '-i' parameter to display them.
Severity
0 : Informational
Response
None.
AMQ8588W
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 we 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 we 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.
AMQ8589W
Installation <insert_3>(<insert_4>) is implicitly primary.
Severity
10 : Warning
Explanation
The command attempted to modify the primary installation <insert_3>, however this installation is implicitly primary and can only be made non-primary by uninstalling this installation.
Response
Verify that the installation <insert_3> is required, if so no other installation can be made primary.
AMQ8590E
Installation <insert_3> (<insert_4>) 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.
AMQ8592I
Queue manager <insert_3> is now associated with installation <insert_4>.
Severity
0 : Informational
Explanation
A command was issued that has associated queue manager <insert_3> with installation <insert_4>. The queue manager will be executed by this installation when it is next started.
Response
None.
AMQ8593E
Installation state for installation <insert_3> (<insert_4>) detected as invalid.
Severity
20 : Error
Explanation
An attempt was made to modify the state of installation <insert_3> (<insert_4>), 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 may have invalidated installation <insert_3>. It may be necessary to contact the IBM support center, in which case a trace of the failing command may be required.
AMQ8594W
IBM MQ commands are no longer available in /usr/bin.
In order to run MQ commands we must manage your path configuration as described in the IBM MQ product documentation. In particular review the topic on "Choosing a primary installation".
Severity
10 : Warning
Explanation
The /usr/bin (and /usr/lib) directories are not populated with symbolic links to commands for IBM MQ at installation time, as had been the case in previous releases of the product.
Symbolic links are created for the installation that has been made primary using the setmqinst -i command, only.
Response
Read the documentation on configuring the primary installation and setting the current shell environment using the setmqenv script.
AMQ8595E
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
AMQ8596W (Windows)
Unable to reconfigure installation <insert_3> (<insert_4>) as the primary installation.
Severity
10 : Warning
Explanation
A restart of the operating system is required in order to replace files from installation <insert_3> that are currently in use.
Installation <insert_3> (<insert_4>) is currently configured as the primary installation. After the operating system has been restarted, the in-use files will be replaced, but the installation will no longer be configured as the primary installation.
Response
After restarting the operating system an administrator will need to manually reconfigure installation <insert_3> as the primary installation using the following command line:
"<insert_4>\setmqinst.exe" -i -n <insert_3>
AMQ8597W
This process is linked with an unsupported shared library.
Severity
10 : Warning
Explanation
A IBM MQ 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 not supported.
The application will fail with reason code MQRC_ENVIRONMENT_ERROR until the application has been re-linked without libmqmcs and libmqmzse.
Response
Re-link the application, omitting the -lmqmcs and -lmqmzse options from the command line.
This message can be suppressed by setting the AMQ_NO_MQMCS_MSG environment variable to any value.
AMQ8598W
---------------------------------------------------------------------
Failed to load the IBM MQ native JNI library: <insert_3>.
The JVM attempted to load the platform native library <insert_3>,
which was mapped to the filename: <insert_2>.
When attempting to load the library, the JVM reported the the error
message:
<insert_1>
The JVM's bit-size is: <insert_4>
The library path which was used to locate this library was:
<insert_5>
Check that the bit size of the JVM matches the bit size of the first
native library file located within this java.library.path directory
list.
The native library <insert_3> is used by the IBM MQ classes for
Java and IBM MQ classes for JMS when creating a connection to
the queue manager using a 'bindings' mode connection. A bindings
mode connection is a connection which uses the system's memory to
communicate with the queue manager, as opposed to a 'client' mode
connection which uses a TCP/IP socket.
In order to communicate with a queue manager using a bindings mode
connection, the queue manager must be located on the same system as
the IBM MQ classes for Java/JMS. If this is not the case in
the environment, consider reconfiguring the application to utilise
client mode connections.
---------------------------------------------------------------------
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.
AMQ8599E
The <insert_3> command was unable to locate a JRE.
Severity
20 : Error
Explanation
The <insert_3> command requires a Java Runtime Environment (JRE) in order to run. The command was unable to locate either the optional IBM MQ JRE component, or any other JRE on the system path. The command could not be run successfully.
Response
Either install the IBM MQ JRE component or ensure that a suitable JRE is available on the system path, then retry the command.
AMQ8601I
IBM MQ trigger monitor started.
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor has been started.
Response
None.
AMQ8601I (IBM i)
IBM MQ trigger monitor started.
Severity
0 : Informational
Explanation
The trigger monitor has been started with initiation queue <insert_3>.
Response
None.
AMQ8602I
IBM MQ trigger monitor ended with exit code <insert_1>. If this value is anything other than zero, it indicates an error condition.
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor has ended with exit code <insert_1>.
Response
Look for earlier error messages from the trigger monitor.
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 MQ administrator. Then try the command again.
AMQ8605I
Queue manager not available to the IBM MQ trigger monitor
Severity
0 : Informational
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 the systems administrator to start it, if it is not active. Then try the command again.
AMQ8606I
Insufficient storage available for the IBM MQ trigger monitor.
Severity
0 : Informational
Explanation
There was insufficient storage available for the IBM MQ trigger monitor to run.
Response
Free some storage and then try the command again.
AMQ8607I
IBM MQ trigger monitor connection failed.
Severity
0 : Informational
Explanation
The trigger monitor's connection to the requested queue manager failed because of MQI reason code <insert_1> from MQCONN.
Response
Consult the systems administrator about the state of the queue manager.
AMQ8608I
IBM MQ trigger monitor connection broken.
Severity
0 : Informational
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 the systems administrator about the state of the queue manager.
AMQ8609I
Initiation queue missing or wrong type
Severity
0 : Informational
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.
AMQ8610I
Initiation queue in use
Severity
0 : Informational
Explanation
The IBM 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.
AMQ8611I
Initiation queue could not be opened.
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor could not open the initiation queue; reason code <insert_1> was returned from MQOPEN.
Response
Consult the systems administrator.
AMQ8612I
Waiting for a trigger message
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor is waiting for a message to arrive on the initiation queue.
Response
None.
AMQ8613I
Initiation queue changed or deleted
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened.
Response
Retry the command.
AMQ8614I
Initiation queue not enabled for input.
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor cannot read from the initiation queue because input is not enabled.
Response
Ask the systems administrator to enable the queue for input.
AMQ8615I
IBM MQ trigger monitor failed to get message.
Severity
0 : Informational
Explanation
The IBM MQ trigger monitor failed because of MQI reason code <insert_1> from MQGET.
Response
Consult the systems administrator.
AMQ8616I
End of application trigger.
Severity
0 : Informational
Explanation
The action to trigger an application has been completed.
Response
None.
AMQ8617I
Not a valid trigger message.
Severity
0 : Informational
Explanation
The IBM 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 we 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 we have started it to consume from an application queue, this should be corrected.
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.
AMQ8619I
Application type <insert_1> not supported.
Severity
0 : Informational
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.
AMQ8620I
Trigger message with warning <insert_1>
Severity
0 : Informational
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>.
The MQSC DISPLAY SERVICE command completed successfully. Details follow this message.
Response
None.
AMQ8630I
Display listener information details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY LISTENER command completed successfully. Details follow this message.
Response
None.
AMQ8631I
Display listener status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY LSSTATUS command completed successfully. Details follow this message.
AMQ8632I
Display service status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY SVSTATUS command completed successfully. Details follow this message.
AMQ8633I
Display topic details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY TOPIC command completed successfully. Details follow this message.
AMQ8649I
Reset IBM MQ Queue Manager accepted.
Severity
0 : Informational
Explanation
The MQSC RESET QMGR command completed successfully. Details follow this message.
Response
None.
AMQ8650I
Activity information unavailable.
Severity
0 : Informational
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.
AMQ8650I (IBM i)
Activity information unavailable.
Severity
0 : Informational
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.
AMQ8651I
DSPMQRTE command has finished with errors.
Severity
0 : Informational
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.
AMQ8651I (IBM i)
DSPMQMRTE command has finished with errors.
Severity
0 : Informational
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.
AMQ8652I
DSPMQRTE command has finished.
Severity
0 : Informational
Explanation
The DSPMQRTE command has finished processing your request and no execution errors were detected.
Response
None.
AMQ8652I (IBM i)
DSPMQMRTE command has finished.
Severity
0 : Informational
Explanation
The DSPMQMRTE command has finished processing your request and no execution errors were detected.
Response
None.
AMQ8653I
DSPMQRTE command started with options <insert_3>.
Severity
0 : Informational
Explanation
We 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.
AMQ8653I (IBM i)
DSPMQMRTE command started.
Severity
0 : Informational
Explanation
We 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.
AMQ8654I
Trace-route message arrived on queue manager <insert_3>.
Severity
0 : Informational
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.
AMQ8654I (IBM i)
Trace-route message arrived on queue manager <insert_3>.
Severity
0 : Informational
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.
AMQ8655I
Trace-route message expired.
Severity
0 : Informational
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.
AMQ8655I (IBM i)
Trace-route message expired.
Severity
0 : Informational
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.
AMQ8656I
DSPMQRTE command received an exception report from queue manager <insert_4> with feedback <insert_1> <insert_3>.
Severity
0 : Informational
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.
AMQ8656I (IBM i)
DSPMQMRTE command received an exception report from queue manager <insert_4> with feedback <insert_1> <insert_3>.
Severity
0 : Informational
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.
AMQ8657I
DSPMQRTE command used <insert_3> 0x<insert_4>.
Severity
0 : Informational
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.
AMQ8657I (IBM i)
DSPMQMRTE command used <insert_3> 0x<insert_4>.
Severity
0 : Informational
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.
AMQ8658I
DSPMQRTE command failed to put a message to the specified target.
Severity
0 : Informational
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.
AMQ8658I (IBM i)
DSPMQMRTE command failed to put a message on the target queue.
Severity
0 : Informational
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.
AMQ8659I
DSPMQRTE command successfully put a message on queue <insert_3>, queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8659I (IBM i)
DSPMQMRTE command successfully put a message on queue <insert_3>, queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8660I
DSPMQRTE command could not correctly order the following activities:
Severity
0 : Informational
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.
AMQ8660I (IBM i)
DSPMQMRTE command could not correctly order the following activities:
Severity
0 : Informational
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.
AMQ8661E
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 should 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.
AMQ8661E (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 should 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.
AMQ8662I
Trace-route message delivered on queue manager <insert_3>.
Severity
0 : Informational
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.
AMQ8662I (IBM i)
Trace-route message delivered on queue manager <insert_3>.
Severity
0 : Informational
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.
AMQ8663E
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 the environment.
Response
Connect to the queue manager using a server connection.
AMQ8664E
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.
AMQ8664E (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.
AMQ8665E
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.
AMQ8665E (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.
AMQ8666I
Queue <insert_3> on queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8666I (IBM i)
Queue <insert_3> on queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8667E
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.
AMQ8667E (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.
AMQ8668E
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.
AMQ8668E (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.
AMQ8669E
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.
AMQ8669E (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.
AMQ8670E
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.
AMQ8671E
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.
AMQ8672E
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.
AMQ8672E (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.
AMQ8673E
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 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 MQ System Administration documentation for further details and restrictions.
Response
Specify a valid object name and then try the command again.
AMQ8673E (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 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 MQ System Administration documentation for further details and restrictions.
Response
Specify a valid object name and then try the command again.
AMQ8674I
DSPMQRTE command is now waiting for information to display.
Severity
0 : Informational
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.
AMQ8674I (IBM i)
DSPMQMRTE command is now waiting for information to display.
Severity
0 : Informational
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.
AMQ8675E
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.
AMQ8676E
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.
AMQ8677E
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.
AMQ8677E (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.
AMQ8678E
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.
AMQ8678E (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.
AMQ8679E
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.
AMQ8679E (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.
AMQ8680E
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.
AMQ8680E (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.
AMQ8681E
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 our request. The reason for failure is <insert_1> or <insert_3>.
Response
See the IBM MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
AMQ8681E (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 our request. The reason for failure is <insert_1> or <insert_3>.
Response
See the IBM MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
AMQ8682I
Trace-route message processed by application <insert_3> on queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8682I (IBM i)
Trace-route message processed by application <insert_3> on queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8683I
Trace-route message reached the maximum activities limit of <insert_1>.
Severity
0 : Informational
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.
AMQ8683I (IBM i)
Trace-route message reached the maximum activities limit of <insert_1>.
Severity
0 : Informational
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.
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.
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.
AMQ8685E
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.
AMQ8685E (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.
AMQ8686E
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.
AMQ8686E (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.
AMQ8687I
Program ending.
Severity
0 : Informational
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.
AMQ8688E
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 our request. The reason for failure is <insert_1> or <insert_3>. The IBM MQ error recording routine has been called.
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 our request. The reason for failure is <insert_1> or <insert_3>. The IBM MQ error recording routine has been called.
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.
AMQ8690I
IBM MQ topic created.
Severity
0 : Informational
Explanation
IBM MQ topic <insert_3> created.
Response
None.
AMQ8691I
IBM MQ topic changed.
Severity
0 : Informational
Explanation
IBM MQ topic <insert_5> changed.
Response
None.
AMQ8692I
IBM MQ topic object deleted.
Severity
0 : Informational
Explanation
IBM MQ topic object <insert_3> deleted.
Response
None.
AMQ8693E
DSPMQRTE command was not supplied a local queue manager when one was required.
Severity
20 : Error
Explanation
The DSPMQRTE command was expecting a local queue manager specified by the -m option but no local queue manager was specified.
Response
Specify a local queue manager and retry the command.
AMQ8694I
DSPMQRTE command successfully put a message to topic string <insert_3>, queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8695I
Topic string <insert_3> on queue manager <insert_4>.
Severity
0 : Informational
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.
AMQ8696E
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.
AMQ8697E
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.
AMQ8698E
Too many keywords have been specified.
Severity
20 : Error
Explanation
Too many keywords for the command have been specified.
Response
None.
AMQ8701I
Usage: rcdmqimg [-z] [-l] [-m QMgrName] -t ObjType [GenericObjName]
-l Request log file information messages.
-m Queue manager name.
-t Types of object for which to record media images:
*, all, authinfo, catalog, channel, clntconn, comminfo,
listener, namelist, process, queue, qalias, qlocal,
qmgr, qmodel, qremote, service, syncfile, topic.
-z Suppress error messages.
The MQSC DISPLAY QMSTATUS command completed successfully. Details follow this message.
Response
None.
AMQ8706I
Request to stop IBM MQ Listener accepted.
Severity
0 : Informational
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.
AMQ8707I (IBM i)
Start IBM MQ DLQ Handler
Severity
0 : Informational
AMQ8708I
Dead-letter queue handler started to process INPUTQ(<insert_3>).
Severity
0 : Informational
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.
AMQ8708I (IBM i)
Dead-letter queue handler started to process INPUTQ(<insert_3>).
Severity
0 : Informational
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.
AMQ8709I
Dead-letter queue handler ending.
Severity
0 : Informational
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.
AMQ8709I (IBM i)
Dead-letter queue handler ending.
Severity
0 : Informational
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.
AMQ870AI (IBM i)
The CLCHNAME parameter is only valid for local and model queues.
Severity
0 : Informational
Explanation
The CLCHNAME parameter has been specified for an invalid queue type.
Response
Remove the CLCHNAME parameter for this command or specify a local or model queue.
AMQ870BI (IBM i)
The IMGRCOVQ parameter is only valid for local and model queues.
Severity
0 : Informational
Explanation
The IMGRCOVQ parameter has been specified for an invalid queue type.
Response
Remove the IMGRCOVQ parameter for this command or specify a local or model queue.
AMQ870CI (IBM i)
The MAXFSIZE parameter is only valid for local and model queues.
Severity
0 : Informational
Explanation
The MAXFSIZE parameter has been specified for an invalid queue type.
Response
Remove the MAXFSIZE parameter for this command or specify a local or model queue.
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.
AMQ8712E
Publish/subscribe operations are disabled for this queue manager.
Severity
30 : Error
Explanation
The queue manager configuration inhibits any publication or subscription commands.
Response
Check the queue manager options and ensure they are correct.
AMQ8721W
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, we must change the sample program called amqsdlq to cater for the needs.
AMQ8721W (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, we must change the sample program called amqsdlq to cater for the needs.
AMQ8722W
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.
AMQ8723I
Display pub/sub status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY PUBSUB command completed successfully. Details follow this message.
AMQ8724I
Refresh IBM MQ Queue Manager accepted.
Severity
0 : Informational
Explanation
The MQSC REFRESH QMGR command completed successfully. Details follow this message.
Response
None.
AMQ8729W
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.
AMQ8730W
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 the listener should not be running then use the STOP LISTENER command to stop the listener before reissuing the command.
AMQ8731W
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.
AMQ8732I
Request to stop Service accepted.
Severity
0 : Informational
Explanation
The Request to stop the Service has been accepted and is being processed.
Response
None.
AMQ8733I
Request to start Service accepted.
Severity
0 : Informational
Explanation
The Request to start the Service has been accepted and is being processed.
Response
None.
AMQ8734E
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 IBM MQ user does not have sufficient access to execute the program.
If STDOUT or STDERR are defined for the program, the IBM 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.
AMQ8735E
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 IBM MQ user has access to execute the program.
AMQ8736E
Parameter %3 conflicts with parameter %4.
Severity
20 : Error
Explanation
The values specified for the two parameters are mutually exclusive.
Response
Consult the documentation for the parameters to determine an appropriate combination of values.
AMQ8737W
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 the service should not 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 a 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.
AMQ8738W
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.
AMQ8739E
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.
AMQ8740E
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.
AMQ8741E
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.
AMQ8741E (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.
AMQ8742E
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.
AMQ8742E (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.
AMQ8743E
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.
AMQ8743E (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.
AMQ8744E
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.
AMQ8744E (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.
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.
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.
AMQ8746E
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.
AMQ8746E (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.
AMQ8747E
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>.
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.
AMQ8748E (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.
AMQ8749E
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.
AMQ8749E (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.
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 ends.
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 ends.
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.
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.
The MQSC DISPLAY TPSTATUS command completed successfully. Details follow this message.
AMQ8755I
IBM MQ topicstr cleared successfully.
Severity
0 : Informational
Explanation
All messages on topicstr have been deleted.
AMQ8756E
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.
AMQ8756E (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.
AMQ8757E
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.
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.
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.
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).
Unexpected failure while initializing process: Reason = <insert_1>.
Severity
40 : Severe
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.
Unexpected failure while initializing process: Reason = <insert_1>.
Severity
30 : 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.
Unexpected failure while connecting to queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected failure while connecting to queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unexpected error while attempting to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected error while attempting to open queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unexpected error while inquiring on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected error while inquiring on queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unexpected error while attempting to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected error while attempting to close queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unexpected failure while opening dead-letter queue for browse: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected failure while opening dead-letter queue for browse: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
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.
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.
Unexpected error while getting message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected error while getting message from dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unexpected error committing/backing out action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unexpected error committing/backing out action on dead-letter queue: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
Unable to disconnect from queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
40 : Severe
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.
Unable to disconnect from queue manager: CompCode = <insert_1> Reason = <insert_2>.
Severity
30 : 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.
The <insert_5> command failed to open <insert_3> for IBM 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.
AMQ8771I (DEC)
OpenVMS Cluster Failover Set Configuration and State.
Node <insert_3> is not in the Failover Set configuration file
Severity
20 : Error
AMQ8785E (DEC)
There are no Failover Monitors started for Queue Manager: <insert_3>
Severity
20 : Error
AMQ8786W (DEC)
Failover set update operation in progress
Severity
10 : Warning
AMQ8787I (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
Error in the format of the initialisation file FAILOVER.INI
Severity
20 : Error
AMQ8791E (DEC)
No node available on which to start the queue manager
Severity
20 : Error
AMQ8792E (DEC)
Operation not allowed; Use a Failover command
Severity
20 : Error
AMQ8793W (DEC)
The ending of the queue manager was forced
Severity
10 : Warning
AMQ8794E (DEC)
The ending of the queue manager timed out before completion
Severity
20 : Error
AMQ8795I (DEC)
End Queue Manager Time Out: <insert_1>
Severity
0 : Informational
AMQ8796E (DEC)
There is a Failover Monitor already running on node: <insert_3>
Severity
20 : Error
AMQ8799E
A certificate label cannot be specified for an SSL 3.0 channel.
Severity
20 : Error
Explanation
A inbound channel which uses an SSL 3.0 CipherSpec may not specify a certificate label. Certificate labels for inbound channels are only supported for TLS channels.
Response
For to configure a certificate label, alter the channel to use a TLS CipherSpec.
AMQ8822I
Invalid response, please re-enter (y or n):
Severity
0 : Informational
Response
None.
AMQ8825I
Usage: amqorxr <mode> [programargs]
Severity
0 : Informational
Explanation
amqorxr was run with incorrect arguments.
Response
Re-run with a valid mode argument.
AMQ8827E
Unable to set real (and effective) user id. Error: <insert_1>.
Severity
20 : Error
Explanation
amqorxr was unable to change the user it was running as. It should be setuid/setgid mqm.
Response
Check that the file permissions have not been altered since installation. If no problem is found, contact the IBM support center.
AMQ8828E
Unable to set real (and effective) group id. Error: <insert_1>.
Severity
20 : Error
Explanation
amqorxr was unable to change the group it was running as. It should be setuid/setgid mqm.
Response
Check that the file permissions have not been altered since installation. If no problem is found, contact the IBM support center.
AMQ8829E
Unable to execute <insert_3>.
Severity
20 : Error
Explanation
amqorxr was unable to execute the command indicated.
Response
Check that the install is not damaged. If no obvious problem is found, contact the IBM support center.
AMQ8848E
The cluster topic cannot currently be altered with a CLROUTE of TOPICHOST
Severity
20 : Error
Explanation
An attempt was made to alter the CLROUTE or CLUSTER attribute of a cluster topic, which is not allowed when using a CLROUTE of TOPICHOST. It is not possible to change the cluster routing mechanism or the cluster where TOPICHOST routing is occurring without first removing the topic definition from a cluster.
Response
To alter the CLROUTE or CLUSTER attributes, first quiesce publish/subscribe messaging for this topic. Remove the topic definition from the cluster by setting CLUSTER to blank and then modify the CLROUTE and CLUSTER attributes to their intended value. Once the cluster is aware of the modifications, and this queue manager has received proxy subscriptions for any remote subscriptions, resume publish/subscribe messaging. During this procedure, the topic will not be clustered and as such will not propagate publications to all subscribers in the cluster.
AMQ8849E
An existing clustered topic conflicts with the requested action.
Severity
20 : Error
Explanation
The clustered topic cannot be defined due to another clustered topic already existing at the same point, above or below it in the topic tree that would conflict with this topic's clustered attributes. CLROUTE is one property that must be consistent across all matching topics in a cluster.
Response
Identify the conflict in properties and modify the topic definitions accordingly.
AMQ8858I
IBM MQ comminfo created.
Severity
0 : Informational
Explanation
IBM MQ comminfo <insert_3> created.
Response
None.
AMQ8859I
IBM MQ comminfo changed.
Severity
0 : Informational
Explanation
IBM MQ comminfo <insert_5> changed.
Response
None.
AMQ8860I
IBM MQ comminfo object deleted.
Severity
0 : Informational
Explanation
IBM MQ comminfo object <insert_3> deleted.
Response
None.
AMQ8861I
Display comminfo details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY COMMINFO command completed successfully. Details follow this message.
AMQ8862I
IBM MQ authority record set.
Severity
0 : Informational
Explanation
IBM MQ authority record set.
Response
None.
AMQ8863I
IBM MQ authority record deleted.
Severity
0 : Informational
Explanation
IBM MQ authority record deleted.
Response
None.
AMQ8864I
Display authority record details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY AUTHREC command completed successfully. Details follow this message.
AMQ8865I
Display authority service details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY AUTHSERV command completed successfully. Details follow this message.
AMQ8866I
Display entity authority details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY ENTAUTH command completed successfully. Details follow this message.
AMQ8867E
Entity, principal or group not specified.
Severity
20 : Error
Explanation
The authorization entity, which can be either a principal or a group, is required.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command.
AMQ8868E
Profile name not valid.
Severity
20 : Error
Explanation
The profile name is not valid. In most cases, the profile name can be either the name of an MQ object or a generic profile.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command.
AMQ8869E
Authorization value error.
Severity
20 : Error
Explanation
The authorization value is incorrect for the specified type of MQ object.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command and the set of allowable authorization values for the different types of MQ objects.
AMQ8870E
Authorization value missing.
Severity
20 : Error
Explanation
The authorization value is required and has not been specified.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command.
AMQ8871E
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.
Response
None.
AMQ8872E
The CLCHNAME parameter is not allowed for non-transmission queues.
Severity
20 : Error
Explanation
The parameter is not allowed for the queue usage being created or changed.
Response
Refer to the description of the parameter in error to determine the types of queues for which this parameter is valid.
AMQ8873W
Display channel authentication record details - hostname lookup disabled.
Severity
10 : Warning
Explanation
The display channel authentication command completed successfully, although reverse DNS lookup is currently disabled on the queue manager. Details follow this message.
AMQ8877I
IBM MQ channel authentication record set.
Severity
0 : Informational
Explanation
IBM MQ channel authentication record set.
Response
None.
AMQ8878I
Display channel authentication record details.
Severity
0 : Informational
Explanation
The display channel authentication command completed successfully. Details follow this message.
AMQ8879E
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 IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8880E
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 IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8881E
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 IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8882E
Parameter <insert_3> is not allowed for this channel authentication record type.
Severity
20 : Error
Explanation
The parameter <insert_3> is not allowed for the type of channel authentication record being set or displayed (<insert_4>).
Response
Refer to the description of the parameter in error to determine the types of record for which this parameter is valid.
AMQ8883E
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.
AMQ8884E
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.
AMQ8885E
Parameter <insert_3> is not allowed with action parameter <insert_4>.
Severity
20 : Error
Explanation
The parameter <insert_3> is not allowed for action <insert_4> 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.
AMQ8886E
Parameter <insert_3> is not allowed with user source <insert_4>.
Severity
20 : Error
Explanation
The <insert_3> parameter is not allowed for a channel authentication record with a user source value of <insert_4>.
Response
Remove the parameter or alter the user source for the channel authentication record.
AMQ8887E
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 the values of match for which this parameter is valid.
Response
Remove the parameter.
AMQ8888E
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 IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8889E
Object type missing.
Severity
20 : Error
Explanation
An object type is required and has not been specified.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command.
AMQ8890E
Profile name missing.
Severity
20 : Error
Explanation
A profile name is required and has not been specified.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to check the syntax for this command.
AMQ8891E
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 MQ names, or characters which are not valid for the specified profile type.
Response
None.
AMQ8892E
Channel authentication record client bound connection value not valid.
Severity
20 : Error
Explanation
The client bound connection parameter specified on the command was not valid.
Response
Specify a valid client bound connection parameter. Refer to the IBM MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
AMQ8894E
Function restricted by queue manager's command level.
Severity
20 : Error
Explanation
The command used a function which is restricted by the queue manager's current command level. This indicates that new function is available in a greater command level which has not yet been enabled for this queue manager.
Response
Review the command and avoid use of the restricted function. To start using the restricted function, stop and restart the queue manager enabling a greater command level which supports the function.
AMQ8895E
Channel authentication record client user ID not valid.
Severity
20 : Error
Explanation
The client user ID parameter specified on the command was not valid.
Response
Specify a valid client user ID. Refer to the IBM MQ Script (MQSC) Command Reference to determine the allowable set of characters for this parameter.
AMQ8896E
SuiteB parameter is not valid.
Severity
20 : Error
Explanation
The SuiteB parameter specified on the command was not valid.
Response
Specify a valid SuiteB parameter. Refer to the IBM MQ Script (MQSC) Command Reference to determine the allowable combination of values for this parameter.
AMQ8897E
Custom parameter value error.
Severity
20 : Error
Explanation
The value of the custom parameter specified on the command is not valid.
Response
Refer to the IBM MQ Script (MQSC) Command Reference to determine the valid values for this parameter.
AMQ8898W
Display channel authentication record details - currently disabled.
Severity
10 : Warning
Explanation
The display channel authentication command completed successfully, although currently disabled on the queue manager. Details follow this message.
The attempt to perform a callback operation on queue <insert_3> on queue manager <insert_4> failed with reason code <insert_1>. To use MQCB in an MQ client application, the SHARECNV parameter of the channel must have a non-zero value.
Response
Investigate and correct the failure before submitting the command again.
AMQ8922I
IBM MQ log set.
Severity
0 : Informational
Explanation
IBM MQ log set.
Response
None.
AMQ8923E
IBM MQ log extent <insert_3> not found.
Severity
30 : Error
Explanation
The log extent cannot be found.
Response
Specify a log extent that exists.
AMQ8923S (IBM i)
IBM MQ journal receiver <insert_3> not found.
Severity
40 : Severe
Explanation
The journal receiver could not be found.
Response
Specify a journal receiver that exists.
AMQ8924E
IBM MQ log extent <insert_3> is currently in use.
Severity
20 : Error
Explanation
The log extent specified is the current log extent and is not valid for the command that was run.
Response
Specify a log extent that is not the current log extent.
AMQ8924E (IBM i)
IBM MQ journal receiver <insert_3> is currently in use.
Severity
20 : Error
Explanation
The journal receiver that was specified is the current journal receiver and is not valid for the command that was executed.
Response
Specify a journal receiver that is not the current journal receiver.
AMQ8925W
IBM MQ log not reduced.
Severity
10 : Warning
Explanation
No log extents could be deleted, so the log has not been reduced.
Response
None.
AMQ8926E
Command not applicable for current log type.
Severity
20 : Error
Explanation
A command was issued which required a different log type. For example, the SET LOG command is only supported on a queue manager configured to use archive log management. The command failed.
Response
Determine why the command was issued on a queue manager with the wrong log type.
AMQ8927E
IBM MQ log extent error.
Severity
30 : Error
Explanation
A log extent has been detected as corrupt and is not valid for use.
Response
Refer to previous error messages for more information.
AMQ8928E
Subscription creation inhibited.
Severity
20 : Error
Explanation
The subscription could not be created because the closest parent administrative topic object associated with this subscription definition is defined with the SUB attribute set to DISABLED.
Response
The SUB attribute of the administrative topic object associated with this subscription definition should be set to ENABLED.
AMQ8929E
Access to function is blocked by the queue manager.
Severity
20 : Error
Explanation
Access to this function has been inhibited on this queue manager.
Response
Refer to previous messages AMQ7354 or AMQ7355 in the queue manager error logs for more information.
AMQ8930E
Invalid administrative topic string.
Severity
20 : Error
Explanation
The topic string applies to the administrative topic tree starting $SYS/MQ. An attempt was made to use an invalid administrative topic string. When subscribing to an administrative topic string, the use of wildcard characters is restricted.
Response
Refer to the product documentation to determine a valid administrative topic string or stop using a $SYS/MQ topic string.
AMQ8932I
Display application status details.
Severity
0 : Informational
Explanation
The MQSC DISPLAY APSTATUS command completed successfully, and details follow this message.
Response
None.
AMQ8933I
Application status not found.
Severity
0 : Informational
Explanation
No status was found for the specified application name(s).
The user attempted to disable Publish Subscribe (PSMODE) or Clustered Publish Subscribe (PSCLUS) while the queue manager is a member of uniform cluster. Clustered publish subscribe functionality is required to participate in uniform clusters.
Response
If uniform clustering is not required, remove the queue manager from the uniform cluster and repeat the operation to disable publish/subscribe.
AMQ8939I
Automatic MQSC configuration script has completed, and contained <insert_1> command(s), of which <insert_2> had errors.
Severity
0 : Informational
Explanation
The automatic configuration MQSC script ran and executed <insert_1> command(s). During these commands there were <insert_2> error(s) and <insert_3> contained syntax error(s).
Response
None
AMQ8940E
An automatic MQSC command was not successful.
Severity
20 : Error
Explanation
The automatic configuration MQSC script ran the command <insert_3> and it gave a completion code of <insert_1> and a reason code of <insert_2>.
The following was the resultant MQSC output:
<insert_4><insert_5>
Response
Verify the automatic configuration script contains the expected configuration.
AMQ8941W
An automatic MQSC command had invalid syntax.
Severity
10 : Warning
Explanation
The automatic configuration MQSC script ran the command <insert_3> which failed due to a syntax error.
The following was where MQSC indicated the error started:
<insert_4><insert_5>
Response
Verify the automatic configuration script contains valid commands.
AMQ8942I
Starting to process automatic MQSC configuration script.
Severity
0 : Informational
Explanation
The queue manager is configured with an automatic configuration MQSC script and processing of that script has started.
Response
None.
AMQ8943I
Please wait while all files are verified.
Severity
0 : Informational
Explanation
The vermqpkg command is verifying a large number of files which can take a significant amount of time to process before the results are fully displayed.
Response
None.
AMQ8944E
The manifest file <insert_3> cannot be read.
Severity
20 : Error
Explanation
The vermqpkg must be able to read the manifest file <insert_3> in order to perform verification of the package but the file could not be read.
Response
Ensure that the manifest file is present and readable by the user running the vermqpkg command, then re-run the command.
AMQ8945W
Unable to verify package checksums using <insert_3><insert_4>.
Severity
10 : Warning
Explanation
The vermqpkg command was requested to perform checksum verification but it was not possible for the command to do this. This can occur if the checksum verification tool <insert_3><insert_4> is not present.
Response
Ensure that the <insert_3><insert_4> command is available and re-run the command.
AMQ8946W
File <insert_3> has been modified.
Severity
10 : Warning
Explanation
The vermqpkg command has determined that file <insert_3> has been modified. The checksum is <insert_4> whereas <insert_5> was expected.
Response
Determine if the changes to the file are expected.
AMQ8947I
File <insert_3> has been successfully verified.
Severity
0 : Informational
Explanation
The vermqpkg command has determined that file <insert_3> is present and has not been modified.
Response
None.
AMQ8948I
File <insert_3> is present in the package.
Severity
0 : Informational
Explanation
The vermqpkg command has determined that file <insert_3> is present. Checksum verification is not in use so it cannot be determined if the file has been modified.
Response
None.
AMQ8949W
File <insert_3> has been added to the package.
Severity
10 : Warning
Explanation
The vermqpkg command has determined that file <insert_3> has been added to the package.
Response
Determine if the file addition is expected.
AMQ8950W
File <insert_3> has been deleted from the package.
Severity
10 : Warning
Explanation
The vermqpkg command has determined that file <insert_3> has been removed from the package.
The vermqpkg command has processed <insert_1> files. <insert_2> files in the package were determined to have been modified. <insert_3> additional files were found in the package. <insert_4> files were found to be missing from the package.
The vermqpkg command has processed <insert_1> files but without verifying the checksums. <insert_3> additional files were found in the package. <insert_4> files were found to be missing from the package.
Response
None.
AMQ8953I
Reset successful. Current qm.ini values will now be persisted unless explicitly overridden by automatic configuration.
Severity
0 : Informational
Explanation
setmqini has removed the base qm.ini values which the queue manager reverts to on each restart. The current qm.ini values will become the new baseline from the next start of this queue manager.
Response
None.
AMQ8A00 (IBM i)
Work Queue Manager Journals
AMQ8A01 (IBM i)
Create Message Queue Manager
AMQ8A02 (IBM i)
Delete Message Queue Manager
AMQ8A03 (IBM i)
Add Queue Manager Information
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
AMQ8A22 (IBM i)
Remote Journal Sync. Timeout
AMQ8A23 (IBM i)
Work with Queue Status
AMQ8A24 (IBM i)
Change Queue Manager Journal
AMQ8A25 (IBM i)
Remove Queue Manager Journal
AMQ8A2A (IBM i)
Remove Queue Manager Info.
AMQ8A2B (IBM i)
Add Queue Manager Journal
AMQ8A2C (IBM i)
Queue Manager Journal
AMQ8A2D (IBM i)
Remote Relational Database
AMQ8A2E (IBM i)
Remote Journal Status
AMQ8A2F (IBM i)
Remote Journal Delivery
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 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 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
AMQ8B0CS (IBM i)
OPTION(*MVS) not valid without specifying a value for WAIT.
Severity
40 : Severe
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
AMQ8B35 (IBM i)
Channel Authentication
AMQ8B36 (IBM i)
Job name
AMQ8B37 (IBM i)
Number
AMQ8B38 (IBM i)
Fix directories
AMQ8B39 (IBM i)
Local Message Queue Manager
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
AMQ8B4D (IBM i)
LCLMQMNAME only allowed in indirect mode
Explanation
The LCLMQMNAME parameter is only allowed when a value for WAIT has also been specified.
Response
Remove the LCLMQMNAME parameter from the command for direct mode, or, specify a value for WAIT for indirect mode. Then try the command again.
AMQ8B4E (IBM i)
Dump MQ Configuration
AMQ8B4F (IBM i)
Reverse DNS Lookup
AMQ8B50 (IBM i)
Activity Trace Override
AMQ8B51 (IBM i)
Configuration events enabled
AMQ8B52 (IBM i)
Command events enabled
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)
Auto Chan. Def. events enabled
AMQ8B5B (IBM i)
Auto Chan. Def. exit program
AMQ8B5C (IBM i)
Redefine system objects
AMQ8B5D (IBM i)
Wait time
AMQ8B5E (IBM i)
Startup Status Detail
AMQ8B5F (IBM i)
Custom
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 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
AMQ8B6EE (IBM i)
Filter value <insert_3> not valid with keyword <insert_4>.
Severity
30 : 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>.
AMQ8B6F (IBM i)
Activity Trace
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
AMQ8B7C (IBM i)
Default Cluster Transmit Queue Type
AMQ8B7D (IBM i)
Cluster Channel Name
AMQ8B7E (IBM i)
Authorization Method
AMQ8B7F (IBM i)
Base DN Group
AMQ8B80 (IBM i)
Change MQ Processor Allowance
AMQ8B81 (IBM i)
Display MQ Processor Allowance
AMQ8B82 (IBM i)
Sufficient Licence Units
AMQ8B83 (IBM i)
OCSP Responder URL
AMQ8B84S (IBM i)
OCSPURL not allowed with AUTHTYPE *CRLLDAP.
Severity
40 : Severe
Explanation
The OCSPURL parameter may not be specified for an AUTHTYPE of *CRLDAP.
Response
Remove the OCSPURL parameter from the command or, if the command is CRTMQMAUTI, specify a different value for AUTHTYPE. Then try the command again.
AMQ8B85S (IBM i)
CONNAME not allowed with AUTHTYPE *OCSP.
Severity
40 : Severe
Explanation
The CONNAME parameter may not be specified for an AUTHTYPE of *OCSP.
Response
Remove the CONNAME parameter from the command or, if the command is CRTMQMAUTI, specify a different value for AUTHTYPE. Then try the command again.
AMQ8B86S (IBM i)
USERNAME not allowed with AUTHTYPE *OCSP.
Severity
40 : Severe
Explanation
The USERNAME parameter may not be specified for an AUTHTYPE of *OCSP.
Response
Remove the USERNAME parameter from the command or, if the command is CRTMQMAUTI, specify a different value for AUTHTYPE. Then try the command again.
AMQ8B87S (IBM i)
PASSWORD not allowed with AUTHTYPE *OCSP.
Severity
40 : Severe
Explanation
The PASSWORD parameter may not be specified for an AUTHTYPE of *OCSP.
Response
Remove the PASSWORD parameter from the command or, if the command is CRTMQMAUTI, specify a different value for AUTHTYPE. Then try the command again.
AMQ8B88S (IBM i)
CONNAME parameter required with AUTHTYPE *CRLLDAP.
Severity
40 : Severe
Explanation
The CONNAME parameter must be specified with AUTHTYPE *CRLLDAP.
Response
Enter a value for parameter CONNAME.
AMQ8B89S (IBM i)
OCSPURL parameter required with AUTHTYPE *OCSP.
Severity
40 : Severe
Explanation
The OCSPURL parameter must be specified with AUTHTYPE *OCSP.
Response
Enter a value for parameter OCSPURL.
AMQ8B8A (IBM i)
Set MQ Security Policy
AMQ8B8B (IBM i)
Authorized signers
AMQ8B8C (IBM i)
Intended recipients
AMQ8B8D (IBM i)
Tolerate unprotected
AMQ8B8E (IBM i)
Signing algorithm
AMQ8B8F (IBM i)
Encryption algorithm
AMQ8B90 (IBM i)
Policy name
AMQ8B91 (IBM i)
Remove policy
AMQ8B92 (IBM i)
Display MQ Security Policy
AMQ8B93 (IBM i)
Work with MQ Security Policies
AMQ8B94 (IBM i)
Connection Authentication
AMQ8B95 (IBM i)
Check Local
AMQ8B96 (IBM i)
Check Client
AMQ8B97 (IBM i)
Fail Delay
AMQ8B98 (IBM i)
Adopt Context
AMQ8B99 (IBM i)
Base DN User
AMQ8B9A (IBM i)
Short User
AMQ8B9B (IBM i)
Secure Communications
AMQ8B9C (IBM i)
LDAP User Object Class
AMQ8B9D (IBM i)
LDAP User Field
AMQ8B9ES (IBM i)
*REQDADMIN value only allowed for AUTHTYPE *IDPWOS.
Severity
40 : Severe
Explanation
The CHKLOCAL and CHKCLIENT parameters may only specify a value of *REQDADMIN for an AUTHTYPE of *IDPWOS.
Response
Remove the CHKLOCAL and/or CHKCLIENT parameters from the command or, if the command is CRTMQMAUTI, specify a different value for AUTHTYPE. Then try the command again.
AMQ8B9F (IBM i)
LDAP Group Object Class
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
AMQ8C06 (IBM i)
Certificate label
AMQ8C07 (IBM i)
Transmission queue
AMQ8C08 (IBM i)
Connection name
AMQ8C09 (IBM i)
Message channel agent
AMQ8C0A (IBM i)
LDAP Group Field
AMQ8C0B (IBM i)
LDAP Find Group
AMQ8C0C (IBM i)
LDAP Nested Groups
AMQ8C0D (IBM i)
Limit security PCF commands
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
AMQ8D09 (IBM i)
Export type
AMQ8D0A (IBM i)
Output member options
AMQ8D0B (IBM i)
Command Level
AMQ8D0C (IBM i)
Symmetric key reuse
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
AMQ8D1E (IBM i)
Export attributes
AMQ8D1F (IBM i)
Warnings
AMQ8D20 (IBM i)
Channel name
AMQ8D21 (IBM i)
MQSC Channel Definition
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
AMQ8D2F (IBM i)
Client connection
AMQ8D30 (IBM i)
Keep Alive Interval
AMQ8D31I (IBM i)
The requested operation is not valid for user QMQMADM.
Severity
0 : Informational
Explanation
You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid IBM MQ object, with the authority *REMOVE or *NONE.
Response
Remove QMQMADM from the list of users to this command.
AMQ8D32I (IBM i)
The delete option is only valid for a generic profile name.
Severity
0 : Informational
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.