7000-7999 - WebSphere MQ product
See Reading a message for an explanation of how to interpret these messages.
AMQ7001The location specified for creation of the queue manager is not valid.Severity:40 : Stop Error
Explanation:The directory under which queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization.
Response:The location is specified in the machine-wide ini file. Correct the file and submit the request again.
AMQ7001 (Windows)The location specified for the creation of the queue manager is not valid.Severity:40 : Stop Error
Explanation:The directory under which the queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization.
Response:The location is specified in the configuration data. Correct the configuration data and submit the request again.
AMQ7002An error occurred manipulating a file.Severity:40 : Stop Error
Explanation:An internal error occurred while trying to create or delete a queue manager file. It is likely that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.
Response:Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.
AMQ7002 (Windows)An error occurred manipulating a file.Severity:40 : Stop Error
Explanation:An internal error occurred while trying to create or delete a queue manager file.
In the case of a failure to delete a file a common reason for this error is that a non MQ process, such as the windows explorer or a virus checker, is accessing the file. In the case where the object that cannot be deleted is a directory then a non MQ process may be accessing a file within the directory or one of its subdirectories.
It is also possible that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.Response:Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.
AMQ7005The queue manager is running.Severity:40 : Stop Error
Explanation:You tried to perform an action that requires the queue manager stopped, however, it is currently running. You probably tried to delete or start a queue manager that is currently running.
Response:If the queue manager should be stopped, stop the queue manager and submit the failed command again.
AMQ7006Missing attribute <insert_5> on stanza starting on line <insert_1> of ini file <insert_3>.Severity:20 : Error
Explanation:The <insert_4> stanza starting on line <insert_1> of configuration file <insert_3> is missing the required <insert_5> attribute.
Response:Check the contents of the file and retry the operation.
AMQ7006 (Windows)Missing attribute <insert_5> from configuration data.Severity:20 : Error
Explanation:The <insert_4> stanza in the configuration data is missing the required <insert_5> attribute.
Response:Check the contents of the configuration data and retry the operation.
AMQ7008The queue manager already exists.Severity:40 : Stop Error
Explanation:You tried to create a queue manager that already exists.
Response:If you specified the wrong queue manager name, correct the name and submit the request again.
AMQ7010The queue manager does not exist.Severity:40 : Stop Error
Explanation:You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.
Response:If you specified the wrong name, correct it and submit the command again. If the queue manager should exist, create it, and then submit the command again.
AMQ7011The queue manager files have not been completely deleted.Severity:40 : Stop Error
Explanation:While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
Response:Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
AMQ7012The specified trigger interval is not valid.Severity:40 : Stop Error
Explanation:You specified a value for the trigger interval that is not valid. The value must be not less than zero and not greater than 999 999 999.
Response:Correct the value and resubmit the request.
AMQ7013There is an error in the name of the specified dead-letter queue.Severity:40 : Stop Error
Explanation:You specified a name for the dead-letter queue that is not valid.
Response:Correct the name and resubmit the request.
AMQ7014There is an error in the name of the specified default transmission queue.Severity:40 : Stop Error
Explanation:You specified a name for the default transmission queue that is not valid.
Response:Correct the name and submit the command again.
AMQ7015There is an error in the maximum number of open object handles specified.Severity:40 : Stop Error
Explanation:You specified a value for the maximum number of open object handles to be allowed that is not valid. The value must be not less than zero and not greater than 999 999 999.
Response:Correct the value and submit the command again.
AMQ7016There is an error in the maximum number of uncommitted messages specified.Severity:40 : Stop Error
Explanation:You specified a value for the maximum number of uncommitted messages to be allowed that is not valid. The value must be not less than 1 and not greater than 999 999 999.
Response:Correct the value and submit the command again.
AMQ7017Log not available.Severity:40 : Stop Error
Explanation:The queue manager was unable to use the log. This could be due to a log file being missing or damaged, or the log path to the queue manager being inaccessible.
Response:Ensure that the LogPath attribute in the queue manager configuration file is correct. If a log file is missing or otherwise unusable, restore a backup copy of the file, or the entire queue manager.
AMQ7018The queue manager operation cannot be completed.Severity:20 : Error
Explanation:An attempt has been made to perform an operation on a queue manager. Resources required to perform the operation are not available.
AMQ7019An error occurred while creating the directory structure for the new queue manager.Severity:40 : Stop Error
Explanation:During creation of the queue manager an error occurred while trying to create a file or directory.
Response:Identify why the queue manager files cannot be created. It is probable that there is insufficient space on the specified disk, or that there is a problem with access control. Correct the problem and submit the command again.
AMQ7020The operation was carried out, but one or more transactions remain in-doubt.Severity:10 : Warning
Explanation:The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time.
Response:Use the DSPMQTRN command to display the remaining in-doubt transactions.
AMQ7020 (iSeries)The operation was carried out, but one or more transactions remain in-doubt.Severity:10 : Warning
Explanation:The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time.
Response:Use the Work with Transactions (WRKMQMTRN) command to display the remaining in-doubt transactions.
AMQ7021An error occurred while deleting the directory structure for the queue manager.Severity:40 : Stop Error
Explanation:While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
Response:Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
AMQ7022The resource manager identification number is not recognized.Severity:20 : Error
Explanation:The identification number of the resource manager you supplied was not recognized.
Response:Ensure that you entered a valid resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers.
AMQ7023The resource manager was in an invalid state.Severity:20 : Error
Explanation:The resource manager, the identification number of which you supplied, was in an invalid state.
Response:Ensure that you entered the correct resource manager identification number. Use the DSPMQTRN command to display a list of resource managers and their identification numbers. A resource manager is in an invalid state, if it is still available to resolve the transaction, use the -a optional flag to resolve this and all other internally coordinated in-doubt transactions.
AMQ7024Arguments supplied to a command are not valid.Severity:20 : Error
Explanation:You supplied arguments to a command that it could not interpret. It is probable that you specified a flag not accepted by the command, or that you included extra flags.
Response:Correct the command and submit it again. Additional information on the arguments causing the error may be found in the error logs for the queue, or queue manager, referenced in the command.
AMQ7025Error in the descriptive text argument (-c parameter) of the crtmqm command.Severity:40 : Stop Error
Explanation:The descriptive text you supplied to the crtmqm command was in error.
Response:Correct the descriptive text argument and submit the command again.
AMQ7026A principal or group name was invalid.Severity:40 : Stop Error
Explanation:You specified the name of a principal or group which does not exist.
Response:Correct the name and resubmit the request.
AMQ7027Argument <insert_3> supplied to command <insert_4> is invalid.Severity:20 : Error
Explanation:The argument <insert_3> was supplied to the command <insert_4> which could not be interpreted. This argument is either not accepted by the command, or an extra flag has been included.
Response:Correct the command and submit it again.
AMQ7028The queue manager is not available for use.Severity:40 : Stop Error
Explanation:You have requested an action that requires the queue manager running, however, the queue manager is not currently running.
Response:Start the required queue manager and submit the command again.
AMQ7030Quiesce request accepted. The queue manager will stop when all outstanding work is complete.Severity:0 : Information
Explanation:You have requested that the queue manager end when there is no more work for it. In the meantime, it will refuse new applications that attempt to start, although it allows those already running to complete their work.
Response:None.
AMQ7031The queue manager is stopping.Severity:40 : Stop Error
Explanation:You issued a command that requires the queue manager running, however, it is currently in the process of stopping. The command cannot be run.
Response:None
AMQ7041Object already exists.Severity:40 : Stop Error
Explanation:A Define Object operation was performed, but the name selected for the object is already in use by an object that is unknown to WebSphere MQ. The object name selected by MQ was <insert_3>, in directory <insert_4>, of object type <insert_5>.
Response:Remove the conflicting object from the MQ system, then try the operation again.
AMQ7042Media image not available for object <insert_3> of type <insert_4>.Severity:20 : Error
Explanation:The media image for object <insert_3>, type <insert_4>, is not available for media recovery. A log file containing part of the media image cannot be accessed.
Response:A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, delete the object instead.
AMQ7042 (iSeries)Media image not available for object <insert_3>.Severity:20 : Error
Explanation:The media image for object <insert_3>, type <insert_4>, is not available for media recovery. A log file containing part of the media image cannot be accessed.
Response:A previous message indicates which log file could not be accessed. Restore a copy of the log file and all subsequent log files from backup. If this is not possible, delete the object instead.
AMQ7044Media recovery not allowed.Severity:20 : Error
Explanation:Media recovery is not possible on a queue manager using a circular log. Damaged objects must be deleted on such a queue manager.
Response:None.
AMQ7047An unexpected error was encountered by a command.Severity:40 : Stop Error
Explanation:An internal error occurred during the processing of a command.
Response:Follow problem determination procedures to identify the cause of the error.
AMQ7048The queue manager name is either not valid or not knownSeverity:40 : Stop Error
Explanation:Either the specified queue manager name does not conform to the rules required by WebSphere MQ or the queue manager does not exist. The rules for naming MQ objects are detailed in the WebSphere MQ Command Reference.
Response:Correct the name and submit the command again.
AMQ7053The transaction has been committed.Severity:0 : Information
Explanation:The prepared transaction has been committed.
Response:None.
AMQ7054The transaction has been backed out.Severity:0 : Information
Explanation:The prepared transaction has been backed out.
Response:None.
AMQ7055The transaction number is not recognized.Severity:20 : Error
Explanation:The number of the transaction you supplied was not recognized as belonging to an in-doubt transaction.
Response:Ensure that you entered a valid transaction number. It is possible that the transaction number you entered corresponds to a transaction which was committed or backed out before you issued the command to resolve it.
AMQ7056Transaction number <insert_1>,<insert_2>.Severity:0 : Information
Explanation:This message is used to report the number of an in-doubt transaction.
Response:None.
AMQ7059An error has occurred reading an INI file.Severity:20 : Error
Explanation:An error has occurred when reading the MQS.INI file or a queue manager QM.INI file.
Response:If you have been changing the INI file content check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ7059 (Windows)An error occurred when reading the configuration data.Severity:20 : Error
Explanation:An error has occurred when reading the configuration data.
Response:If you have changed the configuration data, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ7060An error has occurred locking an INI file.Severity: