AMQ7000-7999: WebSphere MQ product
- AMQ7001
- The 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 might not exist, or there might 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 might not exist, or there might be a problem with authorization.
- Response
- The location is specified in the configuration data. Correct the configuration data and submit the request again.
- AMQ7002
- 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. It is likely that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying file system.
- Response
- Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which might identify the queue manager file causing the error. This error might also be caused if users have created, renamed or deleted that file. Correct the error in the file system 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 might 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 file system.
- Response
- Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which might identify the queue manager file causing the error. This error might also be caused if users have created, renamed or deleted that file. Correct the error in the file system and submit the request again.
- AMQ7005
- The 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.
- AMQ7006
- Missing 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.
- AMQ7008
- The 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.
- AMQ7010
- The 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 might 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.
- AMQ7011
- The 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 might not have been completely deleted.
- Response
- Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
- AMQ7012
- The 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.
- AMQ7013
- There 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.
- AMQ7014
- There 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.
- AMQ7015
- There 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.
- AMQ7016
- There 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.
- AMQ7017
- Log 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.
- AMQ7018
- The 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.
- AMQ7019
- An error occurred while creating or checking the directory structure for the queue manager.
- Severity
- 40 : Stop Error
- Explanation
- During creation or startup of the queue manager an error occurred while creating or checking a file or directory. Further information detailing the cause of the failure is written to the queue manager error logs.
- Response
- Identify why the queue manager files cannot be created or why the check failed. It is probable that there is insufficient space on the specified disk, or that there is a problem with access permissions on a file or directory. Correct the problem and submit the command again.
- AMQ7020
- 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 might not be available at this time. Another possibility is that an earlier attempt to resolve the transaction resulted in an unexpected failure, in this case no attempt will be made to resolve the transaction until the queue manager is restarted.
- Response
- Use the DSPMQTRN command to display the remaining in-doubt transactions.
- AMQ7020 (IBM i)
- 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 might not be available at this time.
- Response
- Use the Work with Transactions (WRKMQMTRN) command to display the remaining in-doubt transactions.
- AMQ7021
- An 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 might not have been completely deleted.
- Response
- Follow problem determination procedures to identify the file or directory and to complete deletion of the queue manager.
- AMQ7022
- The 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.
- AMQ7023
- The 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.
- AMQ7024
- Arguments 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 might be found in the error logs for the queue, or queue manager, referenced in the command.
- AMQ7025
- Error 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.
- AMQ7026
- A 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.
- AMQ7027
- Argument <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.
- AMQ7028
- The 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.
- AMQ7030
- Quiesce 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.
- AMQ7031
- The 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
- AMQ7041
- Object 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.
- AMQ7042
- Media 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, you must delete the object instead.
- AMQ7042 (IBM i)
- 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, you must delete the object instead.
- AMQ7044
- Media 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.
- AMQ7047
- An 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.
- AMQ7048
- The queue manager name is either not valid or not known
- Severity
- 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.
- AMQ7048 (Windows)
- The queue manager name is either not valid or not known
- Severity
- 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.
This message can also occur when specifying an option to a command that contains a path. To ensure that the queue manager name is correctly passed to MQ by the Microsoft Windows command interpreter escape all directory separators in the path ("\\") or do not surround the path in quotation marks.
- Response
- Correct the name and submit the command again.
- AMQ7053
- The transaction has been committed.
- Severity
- 0 : Information
- Explanation
- The prepared transaction has been committed.
- Response
- None.
- AMQ7054
- The transaction has been backed out.
- Severity
- 0 : Information
- Explanation
- The prepared transaction has been backed out.
- Response
- None.
- AMQ7055
- The 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 or heuristically completed 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. It is also possible that the transaction number you entered corresponds to a transaction which is not in the appropriate state for the options you specified. For example, you cannot commit or back out a transaction which is already heuristically completed.
- AMQ7056
- Transaction number <insert_1>,<insert_2> is in-doubt.
- Severity
- 0 : Information
- Explanation
- This message is used to report the number of an in-doubt transaction.
- Response
- None.
- AMQ7059
- An 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 any generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7059 (Tandem)
- An error has occurred reading an INI file.
- Severity
- 20 : Error
- Explanation
- An error has occurred when reading the MQSINI file or a queue manager QMINI 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. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- 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. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7060
- An error has occurred locking an INI file.
- Severity
- 20 : Error
- Explanation
- An error has occurred locking the MQS.INI file or a queue manager QM.INI file.
- Response
- If you have been changing the INI file permissions 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 any generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7060 (Tandem)
- An error has occurred locking an INI file.
- Severity
- 20 : Error
- Explanation
- An error has occurred locking the MQSINI file or a queue manager QMINI file.
- Response
- If you have been changing the INI file permissions 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. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7060 (Windows)
- An error has occurred locking the configuration data.
- Severity
- 20 : Error
- Explanation
- An error has occurred locking the configuration data.
- Response
- If you have changed the configuration data permissions, 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. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7061
- An expected stanza in an INI file is missing or contains errors.
- Severity
- 20 : Error
- Explanation
- An expected stanza is missing from the MQS.INI file or a queue manager QM.INI file or the stanza contains errors.
- Response
- If you have been changing the INI file content check and correct the change.
- AMQ7061 (Tandem)
- An expected stanza in an INI file is missing or contains errors.
- Severity
- 20 : Error
- Explanation
- An expected stanza is missing from the MQSINI file or a queue manager QMINI file or the stanza contains errors.
- Response
- If you have been changing the INI file content check and correct the change.
- AMQ7061 (Windows)
- An expected stanza in the configuration data is missing or contains errors.
- Severity
- 20 : Error
- Explanation
- An expected stanza is missing from the configuration data or the stanza contains errors.
- Response
- If you have changed the configuration data, check and correct the change.
- AMQ7062
- Unable to access an INI file.
- Severity
- 20 : Error
- Explanation
- Access to the MQS.INI file or a queue manager QM.INI file is denied.
- Response
- If you have been changing the INI file permissions check and correct the change.
- AMQ7062 (Tandem)
- Unable to access an INI file.
- Severity
- 20 : Error
- Explanation
- Access to the MQSINI file or a queue manager QMINI file is denied.
- Response
- If you have been changing the INI file permissions check and correct the change.
- AMQ7062 (Windows)
- Unable to access the configuration data.
- Severity
- 20 : Error
- Explanation
- Access to the configuration data is denied.
- Response
- If you have changed the configuration data permissions, check and correct the change.
- AMQ7063
- An INI file is missing.
- Severity
- 20 : Error
- Explanation
- The MQS.INI file or a queue manager QM.INI file is missing.
- Response
- If you have been changing the INI file recover the previous file and retry the operation.
- AMQ7063 (Tandem)
- An INI file is missing.
- Severity
- 20 : Error
- Explanation
- The MQSINI file or a queue manager QMINI file is missing.
- Response
- If you have been changing the INI file recover the previous file and retry the operation.
- AMQ7063 (Windows)
- Configuration data is missing.
- Severity
- 20 : Error
- Explanation
- The configuration data for WebSphere MQ is missing.
- Response
- If you have changed the configuration data, recover the previous configuration data and retry the operation.
- AMQ7064
- Log path not valid or inaccessible.
- Severity
- 40 : Stop Error
- Explanation
- The supplied log path could not be used by the queue manager. Possible reasons for this include the path not existing, the queue manager not being able to write to the path, or the path residing on a remote device.
- Response
- Ensure that the log path exists and that the queue manager has authority to read and write to it. If the queue manager already exists, ensure that the LogPath attribute in the queue manager's configuration file matches the intended log path.
- AMQ7064 (IBM i)
- Auxiliary storage pool identifier not found.
- Explanation
- The auxiliary storage pool identifier supplied does not exist on the system and could not be used by the queue manager to create a journal receiver.
- Response
- Specify *SYSTEM, or the identifier of an existing auxiliary storage pool and try the request again. You can use WRKDSKSTS to check the assignment of disk units to auxiliary storage pools.
- AMQ7065
- Insufficient space on disk.
- Severity
- 40 : Stop Error
- Explanation
- The operation cannot be completed due to shortage of disk space.
- Response
- Either make more disk space available, or reduce the disk requirements of the command you issued.
- AMQ7066
- There are no matching prepared or heuristically completed transactions.
- Severity
- 10 : Warning
- Explanation
- There are no prepared transactions to be resolved or heuristically completed transactions which match the parameters given.
- Response
- None.
- AMQ7068
- Authority file contains an authority stanza that is not valid.
- Severity
- 40 : Stop Error
- Explanation
- A syntax error has been found in one of the files containing authorization information for the queue manager.
- Response
- Correct the contents of the incorrect authorization file by editing it.
- AMQ7069
- The queue manager was created successfully, but cannot be made the default.
- Severity
- 40 : Stop Error
- Explanation
- The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There might not be a default queue manager defined for the machine at present.
- Response
- There is probably a problem with the machine-wide ini file. Verify the existence of the file, its access permissions, and its contents. If its backup file exists, reconcile the contents of the two files and then delete the backup. Finally, either update the machine-wide ini file by hand to specify the desired default queue manager, or delete and re-create the queue manager.
- AMQ7069 (Windows)
- The queue manager was created successfully, but cannot be made the default.
- Severity
- 40 : Stop Error
- Explanation
- The queue manager was defined to be the default queue manager for the machine when it was created. However, although the queue manager has been created, an error occurred trying to make it the default. There might not be a default queue manager defined for the machine at present.
- Response
- There is probably a problem with the configuration data. Update the configuration data to specify the desired default queue manager, or delete and re-create the queue manager.
- AMQ7072
- Invalid QM.INI file stanza. Refer to the error log for more information.
- Severity
- 40 : Stop Error
- Explanation
- An invalid QM.INI file stanza was found. Refer to the error log for more information.
- Response
- Correct the error and then retry the operation.
- AMQ7072 (Tandem)
- Invalid QMINI file stanza. Refer to the error log for more information.
- Severity
- 40 : Stop Error
- Explanation
- An invalid QMINI file stanza was found. Refer to the error log for more information.
- Response
- Correct the error and then retry the operation.
- AMQ7072 (Windows)
- Stanza not valid. Refer to the error log for more information.
- Severity
- 40 : Stop Error
- Explanation
- A stanza that is not valid was found. Refer to the error log for more information.
- Response
- Correct the error and retry the operation.
- AMQ7073
- Log size not valid.
- Severity
- 40 : Stop Error
- Explanation
- Either the number of log files or the size of the log files was outside the accepted values.
- Response
- Make sure that the log parameters you enter lie within the valid range.
- AMQ7074
- Unknown stanza key <insert_4> on line <insert_1> of ini file <insert_3>.
- Severity
- 10 : Warning
- Explanation
- Line <insert_1> of the configuration file <insert_3> contained a stanza called <insert_3>. This stanza is not recognized.
- Response
- Check the contents of the file and retry the operation.
- AMQ7074 (Windows)
- Unknown stanza key <insert_4> at <insert_3> in the configuration data.
- Severity
- 10 : Warning
- Explanation
- Key <insert_3> contained a stanza called <insert_4>. This stanza is not recognized.
- Response
- Check the contents of the configuration data and retry the operation.
- AMQ7074 (IBM i)
- Unknown stanza key.
- Severity
- 10 : Warning
- Explanation
- Line <insert_1> of the configuration file <insert_3> contained a stanza key <insert_4>. This stanza is not recognized.
- Response
- Check the contents of the file and retry the operation.
- AMQ7075
- Unknown attribute in ini file.
- Severity
- 10 : Warning
- Explanation
- Line <insert_1> of the configuration file <insert_3> contained an attribute called <insert_4> that is not valid. This attribute is not recognized in this context.
- Response
- Check the contents of the file and retry the operation.
- AMQ7075 (Windows)
- Unknown attribute <insert_4> at <insert_3> in the configuration data.
- Severity
- 10 : Warning
- Explanation
- Key <insert_3> in the configuration data contained an attribute called <insert_4> that is not valid. This attribute is not recognized in this context.
- Response
- Check the contents of the configuration data and retry the operation.
- AMQ7076
- Invalid value for attribute in ini file.
- Severity
- 10 : Warning
- Explanation
- Line <insert_1> of the configuration file <insert_3> contained value <insert_5> that is not valid for the attribute <insert_4>.
- Response
- Check the contents of the file and retry the operation.
- AMQ7076 (Windows)
- Value <insert_5> not valid for attribute <insert_4> at <insert_3> in the configuration data.
- Severity
- 10 : Warning
- Explanation
- Key <insert_3> in the configuration data contained value <insert_5> that is not valid for the attribute <insert_4>.
- Response
- Check the contents of the configuration data and retry the operation.
- AMQ7077
- You are not authorized to perform the requested operation.
- Severity
- 40 : Stop Error
- Explanation
- You tried to issue a command for the queue manager. You are not authorized to perform the command.
- Response
- Contact your system administrator to perform the command for you. Alternatively, request authority to perform the command from your system administrator.
- AMQ7078
- You entered an object type that is invalid with a generic profile name.
- Severity
- 40 : Stop Error
- Explanation
- You entered an object type of *ALL or *MQM and an object name that contains generic characters, this is an invalid combination.
- Response
- Correct the command and submit it again.
- AMQ7080
- No objects processed.
- Severity
- 10 : Warning
- Explanation
- No objects were processed, either because no objects matched the criteria given, or because the objects found did not require processing.
- Response
- None.
- AMQ7081
- Object <insert_3>, type <insert_4> recreated.
- Severity
- 0 : Information
- Explanation
- The object <insert_3>, type <insert_4> was re-created from its media image.
- Response
- None.
- AMQ7082
- Object <insert_3>, type <insert_4> is not damaged.
- Severity
- 10 : Warning
- Explanation
- Object <insert_3>, type <insert_4> cannot be re-created since it is not damaged.
- Response
- None
- AMQ7083
- A resource problem was encountered by a command.
- Severity
- 20 : Error
- Explanation
- The command failed due to a resource problem. Possible causes include the log being full or the command running out of memory.
- Response
- Look at the previous messages to diagnose the problem. Rectify the problem and retry the operation.
- AMQ7084
- Object <insert_3>, type <insert_4> damaged.
- Severity
- 20 : Error
- Explanation
- The object <insert_3>, type <insert_4> was damaged. The object must be deleted or, if the queue manager supports media recovery, re-created from its media image.
- Response
- Delete the object or re-create it from its media image.
- AMQ7085
- Object <insert_3>, type <insert_4> not found.
- Severity
- 20 : Error
- Explanation
- Object <insert_3>, type <insert_4> cannot be found.
- Response
- None.
- AMQ7086
- Media image for object <insert_3>, type <insert_4> recorded.
- Severity
- 0 : Information
- Explanation
- The media image for object <insert_3>, type <insert_4>, defined in Queue Manager <insert_5>, has been recorded.
- Response
- None.
- AMQ7087
- Object <insert_3>, type <insert_4> is a temporary object
- Severity
- 20 : Error
- Explanation
- Object <insert_3>, type <insert_4> is a temporary object. Media recovery operations are not permitted on temporary objects.
- Response
- None.
- AMQ7088
- Object <insert_3>, type <insert_4> in use.
- Severity
- 20 : Error
- Explanation
- Object <insert_3>, type <insert_4> is in use. Either an application has it open or, if it is a local queue, there are uncommitted messages on it.
- Response
- Ensure that the object is not opened by any applications, and that there are no uncommitted messages on the object, if it is a local queue. Then, retry the operation.
- AMQ7089
- Media recovery already in progress.
- Severity
- 20 : Error
- Explanation
- Another media recovery operation is already in progress. Only one media recovery operation is permitted at a time.
- Response
- Wait for the existing media recovery operation to complete and retry the operation.
- AMQ7090 (Windows)
- The queue manager CCSID is not valid.
- Severity
- 40 : Stop Error
- Explanation
- The CCSID to be used by the QMGR is not valid, because:
1) It is a DBCS CCSID.
2) The CCSID encoding is not ASCII or ASCII related. EBCDIC or UCS2 encodings are not valid on this machine.
3) The CCSID encoding is unknown.
- Response
- Check the CCSID is valid for the machine on which you are working.
- AMQ7090 (IBM i)
- The queue manager CCSID is not valid.
- Severity
- 40 : Stop Error
- Explanation
- The CCSID to be used by the QMGR is not valid for the IBM i platform. The CCSID encoding must be a valid EBCDIC value.
- Response
- Check that the CCSID that you have entered is a valid EBCDIC value.
- AMQ7091
- You are performing authorization for the queue manager, but you specified an object name.
- Severity
- 40 : Stop Error
- Explanation
- Modification of authorizations for a queue manager can be performed only from that queue manager. You must not specify an object name.
- Response
- Correct the command and submit it again.
- AMQ7092
- An object name is required but you did not specify one.
- Severity
- 40 : Stop Error
- Explanation
- The command needs the name of an object, but you did not specify one.
- Response
- Correct the command and submit it again.
- AMQ7093
- An object type is required but you did not specify one.
- Severity
- 40 : Stop Error
- Explanation
- The command needs the type of the object, but you did not specify one.
- Response
- Correct the command and submit it again.
- AMQ7094
- You specified an object type that is not valid, or more than one object type.
- Severity
- 40 : Stop Error
- Explanation
- Either the type of object you specified was not valid, or you specified multiple object types on a command which supports only one.
- Response
- Correct the command and submit it again.
- AMQ7095
- An entity name is required but you did not specify one.
- Severity
- 40 : Stop Error
- Explanation
- The command needs one or more entity names, but you did not specify any. Entities can be principals or groups.
- Response
- Correct the command and submit it again.
- AMQ7096
- An authorization specification is required but you did not provide one.
- Severity
- 40 : Stop Error
- Explanation
- The command sets the authorizations on WebSphere MQ objects. However you did not specify which authorizations are to be set.
- Response
- Correct the command and submit it again.
- AMQ7097
- You gave an authorization specification that is not valid.
- Severity
- 40 : Stop Error
- Explanation
- The authorization specification you provided to the command contained one or more items that could not be interpreted.
- Response
- Correct the command and submit it again.
- AMQ7098
- The command accepts only one entity name. You specified more than one.
- Severity
- 40 : Stop Error
- Explanation
- The command can accept only one principal or group name. You specified more than one.
- Response
- Correct the command and submit it again.
- AMQ7099
- Entity <insert_3> has the following authorizations for object <insert_4>:
- Severity
- 0 : Information
- Explanation
- Informational message. The list of authorizations follows.
- Response
- None.
- AMQ7100
- New functions up to command level <insert_1> enabled.
- Severity
- 0 : Information
- Explanation
- The queue manager's command level has been increased and any new function introduced has been enabled for use.
- Response
- None.
- AMQ7104
- Resource manager <insert_1> has prepared.
- Severity
- 0 : Information
- Explanation
- This message reports the state of a resource manager with respect to an in-doubt transaction.
- Response
- None.
- AMQ7105
- Resource manager <insert_1> has committed.
- Severity
- 0 : Information
- Explanation
- This message reports the state of a resource manager with respect to an in-doubt transaction.
- Response
- None.
- AMQ7106
- Resource manager <insert_1> has rolled back.
- Severity
- 0 : Information
- Explanation
- This message reports the state of a resource manager with respect to an in-doubt transaction.
- Response
- None.
- AMQ7107
- Resource manager <insert_1> is <insert_3>.
- Severity
- 0 : Information
- Explanation
- This message reports the identification number and name of a resource manager.
- Response
- None.
- AMQ7108
- Any in-doubt transactions have been resolved.
- Severity
- 0 : Information
- Explanation
- All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved. This message reports successful completion of the RSVMQTRN command when the -a option is used.
- Response
- None.
- AMQ7108 (IBM i)
- Any in-doubt transactions have been resolved.
- Severity
- 0 : Information
- Explanation
- All, if there were any, of the internally coordinated transactions which were in-doubt, have now been resolved.
- Response
- None.
- AMQ7109
- A decision on behalf of the unavailable resource manager has been delivered.
- Severity
- 0 : Information
- Explanation
- A decision for an internally coordinated transaction which was in-doubt, has now been delivered on behalf of the unavailable resource manager. This message reports successful completion of the RSVMQTRN command when the -r option is used.
- Response
- None.
- AMQ7110
- Media image for the syncfile recorded.
- Severity
- 0 : Information
- Explanation
- The media image for the syncfile has been recorded.
- Response
- None.
- AMQ7111
- Resource manager <insert_1> has participated.
- Severity
- 0 : Information
- Explanation
- This message reports the state of a resource manager with respect to an in-doubt transaction.
- Response
- None.
- AMQ7112
- Transaction number <insert_1>,<insert_2> has encountered an error.
- Severity
- 0 : Information
- Explanation
- This message is used to report the number of an in-doubt transaction which has encountered an error with one or more resource managers.
- Response
- Refer to the queue manager error log for more information about which resource managers are in error. Ensure that the resource managers that were in error, are working correctly, restart the queue manager. If the problem persists, 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.
- AMQ7113
- The Database Name argument, -rn, is missing from the command crtmqm
- Severity
- 20 : Error
- Explanation
- The required flag, -rn, was omitted from the command crtmqm
- Response
- Add the flag and associated database name and submit it again.
- AMQ7114
- The Database Password argument, -rp, is missing from the command crtmqm
- Severity
- 20 : Error
- Explanation
- The required flag, -rp, was omitted from the command crtmqm
- Response
- Add the flag and associated database password and submit it again.
- AMQ7115
- The Database Type argument, -rt, is missing from the command crtmqm
- Severity
- 20 : Error
- Explanation
- The required flag, -rt, was omitted from the command crtmqm
- Response
- Add the flag and associated database type and submit it again
- AMQ7116
- The Database Type argument, -rt, is greater than 8 characters long
- Severity
- 20 : Error
- Explanation
- The argument supplied with the flag -rt, is greater than 8 characters long
- Response
- Reduce the length of the database type argument and submit it again
- AMQ7117
- The MSD shared library failed to load.
- Severity
- 20 : Error
- Explanation
- The MSD shared library was either not located or failed to load correctly.
- Response
- Ensure that the database type is specified correctly when creating a queue manager since this is used to form the name of the shared library to be loaded. Further information on the failure might be found in the FFST logs. Also, ensure that the MSD shared library is installed correctly.
- AMQ7118
- Transaction number <insert_1>,<insert_2> is heuristically committed.
- Severity
- 0 : Information
- Explanation
- This message is used to report the number of a heuristically committed transaction.
- Response
- None.
- AMQ7119
- Transaction number <insert_1>,<insert_2> is heuristically rolled back.
- Severity
- 0 : Information
- Explanation
- This message is used to report the number of a heuristically rolled-back transaction.
- Response
- None.
- AMQ7120
- The Trial Period license for this copy of WebSphere MQ has expired.
- Severity
- 20 : Error
- Explanation
- This copy of WebSphere MQ was licensed to be used in trial mode for a limited period only. This period has expired.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7121
- The trial period for this copy of WebSphere MQ has now expired.
- Severity
- 20 : Error
- Explanation
- This copy of WebSphere MQ was licensed for a limited period only. This period has now expired.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7122
- The Trial Period License Agreement was not accepted.
- Severity
- 10 : Warning
- Explanation
- When the Trial Period License Agreement is displayed, the user must accept it before this copy of WebSphere MQ can be used.
- Response
- Submit the command again and accept the agreement.
- AMQ7123
- There is one day left in the trial period for this copy of WebSphere MQ
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- None.
- AMQ7124
- This is the final day of the trial period for this copy of WebSphere MQ
- Severity
- 10 : Warning
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7125
- There are <insert_1> days left in the trial period for this copy of WebSphere MQ
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- None.
- AMQ7126
- This copy of WebSphere MQ is now running in Production mode.
- Severity
- 0 : Information
- Explanation
- A Production license has been installed for this copy of WebSphere MQ
- Response
- None.
- AMQ7127
-
Press Enter when you have read the messages
- Severity
- 0 : Information
- Explanation
- One or more messages have been displayed. They will disappear when the user presses the Enter key.
- Response
- Press the Enter key when the messages are no longer required.
- AMQ7128
- No license installed for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- The installation of WebSphere MQ is invalid since no Production, Beta, or Trial Period license has been installed.
- Response
- Check that the installation steps described in the Quick Beginnings documentation have been followed, and if the problem persists use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7129
- The trial period for this copy of WebSphere MQ has already been started.
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only and the trial period has been started previously.
- Response
- None.
- AMQ7130
- This copy of WebSphere MQ is running in Production mode.
- Severity
- 0 : Information
- Explanation
- A Production license has been installed for this copy of WebSphere MQ A beta or trial period cannot be started.
- Response
- None.
- AMQ7131
- International License Agreement for Evaluation of Programs
Part 1 - General Terms
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM. IBM WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED PROGRAM TO IBM.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7132
-
The Program is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM® supplier, and is copyrighted and licensed, not sold.
The term "Program" means the original program and all whole or partial copies of it. A Program consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings, or pictures), and related licensed materials.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7133
-
This Agreement includes Part 1 - General Terms and Part 2 - Country Unique Terms and is the complete agreement regarding the use of this Program, and replaces any prior oral or written communications between you and IBM. The terms of Part 2 might replace or modify those of Part 1.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7134
-
1. License
Use of the Program
IBM grants you a nonexclusive, nontransferable license to use the Program.
You may 1) use the Program only for internal evaluation, testing or demonstration purposes, on a trial or "try-and-buy" basis and 2) make and install a reasonable number of copies of the Program in support of such use, unless IBM identifies a specific number of copies in the documentation accompanying the Program. The terms of this license apply to each copy you make. You will reproduce the copyright notice and any other legends of ownership on each copy, or partial copy, of the Program.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7135
-
THE PROGRAM MAY CONTAIN A DISABLING DEVICE THAT WILL PREVENT IT FROM BEING USED UPON EXPIRATION OF THIS LICENSE. YOU WILL NOT TAMPER WITH THIS DISABLING DEVICE OR THE PROGRAM. YOU SHOULD TAKE PRECAUTIONS TO AVOID ANY LOSS OF DATA THAT MIGHT RESULT WHEN THE PROGRAM CAN NO LONGER BE USED.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7136
-
You will 1) maintain a record of all copies of the Program and 2) ensure that anyone who uses the Program does so only for your authorized use and in compliance with the terms of this Agreement.
You may not 1) use, copy, modify or distribute the Program except as provided in this Agreement; 2) reverse assemble, reverse compile, or otherwise translate the Program except as specifically permitted by law without the possibility of contractual waiver; or 3) sublicense, rent or lease the Program.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7137
-
This license begins with your first use of the Program and ends 1) as of the duration or date specified in the documentation accompanying the Program or 2) when the Program automatically disables itself. Unless IBM specifies in the documentation accompanying the Program that you may retain the Program (in which case, an additional charge might apply), you will destroy the Program and all copies made of it within ten days of when this license ends.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7138
-
2. No Warranty
SUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES.
This exclusion also applies to any of IBM's subcontractors, suppliers or program developers (collectively called "Suppliers").
Manufacturers, suppliers, or publishers of non-IBM Programs might provide their own warranties.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7139
-
3. Limitation of Liability
NEITHER IBM NOR ITS SUPPLIERS ARE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7140
-
4. General
Nothing in this Agreement affects any statutory rights of consumers that cannot be waived or limited by contract.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7141
-
IBM may terminate your license if you fail to comply with the terms of this Agreement. If IBM does so, you must immediately destroy the Program and all copies you made of it.
You may not export the Program.
Neither you nor IBM will bring a legal action under this Agreement more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation.
Neither you nor IBM is responsible for failure to fulfill any obligations due to causes beyond its control.
There is no additional charge for use of the Program for the duration of this license.
IBM does not provide program services or technical support, unless IBM specifies otherwise.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7142
- Reply 'yes' to accept the Agreement. Reply 'no' if you do not agree to the terms of the Agreement. Reply 'no' and submit the command again, if you want to read the Agreement again.
- Severity
- 0 : Information
- Explanation
- The Trial Period License Agreement has been displayed to the user and the user should now accept or reject the Agreement.
- Response
- Reply 'yes' or 'no' and press 'Enter'.
- AMQ7143
-
Press Enter to continue
- Severity
- 0 : Information
- Explanation
- Part of the Trial Period License Agreement has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed.
- Response
- Press the Enter key when ready for the next part of the Agreement to be displayed.
- AMQ7144
-
The laws of the country in which you acquire the Program govern this Agreement, except 1) in Australia, the laws of the State or Territory in which the transaction is performed govern this Agreement; 2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yugoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this Agreement; 3) in the United Kingdom, all disputes relating to this Agreement will be governed by English law and will be submitted to the exclusive jurisdiction of the English courts; 4) in Canada, the laws of the Province of Ontario govern this Agreement; and 5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this Agreement.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7145
-
Part 2 - Country Unique Terms
AUSTRALIA:
No Warranty (Section 2):
The following paragraph is added to this Section:
Although IBM specifies that there are no warranties, you might have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation.
Limitation of Liability (Section 3):
The following paragraph is added to this Section:
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7146
-
Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7147
-
NEW ZEALAND:
No Warranty (Section 2):
The following paragraph is added to this Section:
Although IBM specifies that there are no warranties, you might have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if you require the goods and services for the purposes of a business as defined in the Act.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7148
-
Limitation of Liability (Section 3):
The following paragraph is added to this Section:
Where products or services are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7149
-
GERMANY: No Warranty (Section 2):
The following paragraphs are added to this Section:
The minimum warranty period for Programs is six months.
In case a Program is delivered without specifications, we will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. You have to check the usability according to the Program information within the "money-back guaranty" period.
Limitation of Liability (Section 3):
The following paragraph is added to this Section:
The limitations and exclusions specified in the Agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7150
-
INDIA:
General (Section 4):
The following replaces the fourth paragraph of this Section:
If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party might have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7151
-
IRELAND:
No Warranty (Section 2):
The following paragraph is added to this Section:
Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded.
ITALY:
Limitation of Liability (Section 3):
This section is replaced by the following:
Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7152
-
UNITED KINGDOM:
Limitation of Liability (Section 3):
The following paragraph is added to this Section at the end of the first paragraph:
The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sales of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982.
- Severity
- 0 : Information
- Explanation
- This is part of the Trial Period License Agreement which must be accepted before a trial period can be started. A trial period allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7153
- A license could not be installed for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- A Production, Beta or Trial Period license could not be installed for this copy of WebSphere MQ This is because the 'nodelock' file in the 'qmgrs/@SYSTEM' directory could not be created or updated.
- Response
- Check the ownership and permissions of the 'qmgrs/@SYSTEM' directory.
- AMQ7154
- The Production license for this copy of WebSphere MQ has expired.
- Severity
- 20 : Error
- Explanation
- The production license for this copy of WebSphere MQ has an expiry date. This date has been passed.
- Response
- Contact your IBM support center.
- AMQ7155
- License file not found or not valid.
- Severity
- 20 : Error
- Explanation
- The program requires that the License file is present, available and is a valid license file. You can also get this error if you try and use Advanced Message Security (for example, setmqspl) but do not have the AMS component installed.
- Response
- Check that the installation steps described in the documentation have been followed, and if the problem persists use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7156
- This copy of WebSphere MQ is already running in Production mode.
- Severity
- 0 : Information
- Explanation
- A Production license has previously been installed for this copy of WebSphere MQ
- Response
- None.
- AMQ7157
- The Production license is not valid for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- The license <insert_3> has been installed but it is not a valid production license for this copy of WebSphere MQ
- Response
- Submit the SETMQPRD command again specifying the name of a valid production license.
- AMQ7158
- The Trial Period license is not valid for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- The license <insert_3> has been installed but it is not a valid trial period license for this copy of WebSphere MQ
- Response
- Check that the correct version of the file is available.
- AMQ7159
- A FASTPATH application has ended unexpectedly.
- Severity
- 10 : Warning
- Explanation
- A FASTPATH application has ended in a way which did not allow the queue manager to clean up the resources owned by that application. Any resources held by the application can only be released by stopping and restarting the queue manager.
- Response
- Investigate why the application ended unexpectedly. Avoid ending FASTPATH applications in a way which prevents WebSphere MQ from releasing resources held by the application.
- AMQ7160
- Queue Manager Object
- Severity
- 0 : Information
- AMQ7161
- Object catalog
- Severity
- 0 : Information
- AMQ7162
- The setmqaut command completed successfully.
- Severity
- 0 : Information
- AMQ7163 (IBM i)
- WebSphere MQ job <insert_2> started for <insert_3>.
- Severity
- 0 : Information
- Explanation
- The job's PID is <insert_2> the CCSID is <insert_1>. The job name is <insert_4>.
- Response
- None
- AMQ7164 (IBM i)
- WebSphere MQ is waiting for a job to start.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ has been waiting <insert_1> seconds to start job <insert_3> for Queue Manager: <insert_5>
- Response
- Check that the job queue that is associated with job description <insert_4> is not held and that the appropriate maximum active jobs value in the job queue entry is sufficient to allow the job to start. Check that the subsystem that is associated with the job queue is active and has a sufficient value specified for the maximum number of jobs that can be active at the same time.
- AMQ7165
- The Beta license for this copy of WebSphere MQ has expired.
- Severity
- 20 : Error
- Explanation
- This copy of WebSphere MQ was licensed to be used for Beta testing for a limited period only. This period has expired.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7166
- The Beta period for this copy of WebSphere MQ has now expired.
- Severity
- 20 : Error
- Explanation
- This copy of WebSphere MQ was licensed for a limited period only. This period has now expired.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7167
- The 'Early Release of Programs License Agreement' was not accepted.
- Severity
- 10 : Warning
- Explanation
- When the IBM International License Agreement for Early Release of Programs is displayed, the user must accept it before this copy of WebSphere MQ can be used.
- Response
- Submit the command again and accept the agreement.
- AMQ7168
- There is one day left in the Beta test period for this copy of WebSphere MQ
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- None.
- AMQ7169
- This is the final day of the Beta test period for this copy of WebSphere MQ
- Severity
- 10 : Warning
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- Install a Production license for this copy of WebSphere MQ
- AMQ7170 (IBM i)
- Option is not valid for this transaction.
- Severity
- 20 : Error
- Explanation
- The Resolve option is not valid for external transactions. The Commit and Backout options are not valid for internal transactions or heuristically completed transactions. The Forget option is only valid for heuristically completed transactions.
- Response
- Select a different option for this transaction.
- AMQ7171
- IBM International License Agreement for Early Release of Programs
Part 1 - General Terms
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM. IBM WILL LICENSE THE PROGRAM TO YOU ONLY IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM YOU AGREE TO THESE TERMS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED PROGRAM TO IBM.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7172
-
The Program is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or an IBM supplier, and is copyrighted and licensed, not sold.
The term "Program" means the original program and all whole or partial copies of it. A Program consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings, or pictures), and related licensed materials.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7173
-
The term "Early Release" means that the Program is not formally released or generally available. The term does not imply that the Program will be formally released or made generally available. IBM does not guarantee that a Program formally released or made generally available will be similar to, or compatible with, Early Release versions.
THIS AGREEMENT INCLUDES PART 1 - GENERAL TERMS AND PART 2 - COUNTRY-UNIQUE TERMS AND IS THE COMPLETE AGREEMENT REGARDING THE USE OF THIS PROGRAM, AND REPLACES ANY PRIOR ORAL OR WRITTEN COMMUNICATIONS BETWEEN YOU AND IBM. THE TERMS OF PART 2 MAY REPLACE OR MODIFY THOSE OF PART 1.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7174
-
1.License
Use of the Program
IBM grants you a nonexclusive, nontransferable license to use the Program.
You may
1) use the Program only for internal evaluation or testing purposes and
2) make and install a reasonable number of copies of the Program in support of such use, unless IBM identifies a specific number of copies in the documentation accompanying the Program. The terms of this license apply to each copy you make. You will reproduce the copyright notice and any other legends of ownership on each copy, or partial copy, of the Program.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7175
-
THE PROGRAM MAY CONTAIN A DISABLING DEVICE THAT WILL PREVENT IT FROM BEING USED UPON EXPIRATION OF THIS LICENSE. YOU WILL NOT TAMPER WITH THIS DISABLING DEVICE OR THE PROGRAM. YOU SHOULD TAKE PRECAUTIONS TO AVOID ANY LOSS OF DATA THAT MIGHT RESULT WHEN THE PROGRAM CAN NO LONGER BE USED.
You will
1) maintain a record of all copies of the Program and
2) ensure that anyone who uses the Program does so only for your authorized use and in compliance with the terms of this Agreement.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7176
-
You may not
1) use, copy, modify, or distribute the Program except as provided in this Agreement;
2) reverse assemble, reverse compile, or otherwise translate the Program except as specifically permitted by law without the possibility of contractual waiver; or
3) sublicense, rent, or lease the Program.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7177
-
This license begins with your first use of the Program and ends
1) as of the duration or date specified in the documentation accompanying the Program,
2) when the Program automatically disables itself, or
3) when IBM makes the Program generally available. Unless IBM specifies in the documentation accompanying the Program that you may retain the Program (in which case, an additional charge might apply), you will destroy the Program and all copies made of it within ten days of when this license ends.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7178
-
2.No Warranty
SUBJECT TO ANY STATUTORY WARRANTIES WHICH CANNOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE WARRANTY OF NON-INFRINGEMENT AND THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE PROGRAM OR TECHNICAL SUPPORT, IF ANY.. IBM MAKES NO WARRANTY REGARDING THE CAPABILITY OF THE PROGRAM TO CORRECTLY PROCESS, PROVIDE AND/OR RECEIVE DATE DATA WITHIN AND BETWEEN THE 20TH AND 21ST CENTURIES.
This exclusion also applies to any of IBM's subcontractors, suppliers or program developers (collectively called "Suppliers").
Manufacturers, suppliers, or publishers of non-IBM Programs might provide their own warranties.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7179
-
3.Limitation of Liability
NEITHER IBM NOR ITS SUPPLIERS ARE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST SAVINGS, OR ANY INCIDENTAL, SPECIAL, OR OTHER ECONOMIC CONSEQUENTIAL DAMAGES, EVEN IF IBM IS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU.
4.Rights In Data
You hereby assign to IBM all right, title, and interest (including ownership of copyright) in any data, suggestions, and written materials related to your use of the Program you provide to IBM. If IBM requires it, you will sign an appropriate document to assign such rights.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7180
-
5.General
Nothing in this Agreement affects any statutory rights of consumers that cannot be waived or limited by contract.
IBM may terminate your license if you fail to comply with the terms of this Agreement. If IBM does so, you must immediately destroy the Program and all copies you made of it.
You not export the Program.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7181
-
Neither you nor IBM will bring a legal action under this Agreement more than two years after the cause of action arose unless otherwise provided by local law without the possibility of contractual waiver or limitation.
Neither you nor IBM is responsible for failure to fulfill any obligations due to causes beyond its control.
There is no additional charge for use of the Program for the duration of this license.
Neither of us will charge the other for rights in data or any work performed as a result of this Agreement.
IBM does not provide program services or technical support, unless IBM specifies otherwise.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7182
-
The laws of the country in which you acquire the Program govern this Agreement, except
1) in Australia, the laws of the State or Territory in which the transaction is performed govern this Agreement;
2) in Albania, Armenia, Belarus, Bosnia/Herzegovina, Bulgaria, Croatia, Czech Republic, Georgia, Hungary, Kazakhstan, Kirghizia, Former Yugoslav Republic of Macedonia (FYROM), Moldova, Poland, Romania, Russia, Slovak Republic, Slovenia, Ukraine, and Federal Republic of Yugoslavia, the laws of Austria govern this Agreement;
3) in the United Kingdom, all disputes relating to this Agreement will be governed by English Law and will be submitted to the exclusive jurisdiction of the English courts;
4) in Canada, the laws of the Province of Ontario govern this Agreement; and
5) in the United States and Puerto Rico, and People's Republic of China, the laws of the State of New York govern this Agreement.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7183
-
Part 2 - Country-unique Terms
AUSTRALIA: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you might have certain rights under the Trade Practices Act 1974 or other legislation and are only limited to the extent permitted by the applicable legislation.
Limitation of Liability (Section 3): The following paragraph is added to this Section: Where IBM is in breach of a condition or warranty implied by the Trade Practices Act 1974, IBM's liability is limited to the repair or replacement of the goods, or the supply of equivalent goods. Where that condition or warranty relates to right to sell, quiet possession or clear title, or the goods are of a kind ordinarily acquired for personal, domestic or household use or consumption, then none of the limitations in this paragraph apply.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7184
-
GERMANY: No Warranty (Section 2): The following paragraphs are added to this Section: The minimum warranty period for Programs is six months. In case a Program is delivered without Specifications, IBM will only warrant that the Program information correctly describes the Program and that the Program can be used according to the Program information. You have to check the usability according to the Program information within the "money-back guaranty" period.
Limitation of Liability (Section 3): The following paragraph is added to this Section: The limitations and exclusions specified in the Agreement will not apply to damages caused by IBM with fraud or gross negligence, and for express warranty.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7185
-
INDIA: General (Section 5): The following replaces the fourth paragraph of this Section: If no suit or other legal action is brought, within two years after the cause of action arose, in respect of any claim that either party might have against the other, the rights of the concerned party in respect of such claim will be forfeited and the other party will stand released from its obligations in respect of such claim.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7186
-
IRELAND: No Warranty (Section 2): The following paragraph is added to this Section: Except as expressly provided in these terms and conditions, all statutory conditions, including all warranties implied, but without prejudice to the generality of the foregoing, all warranties implied by the Sale of Goods Act 1893 or the Sale of Goods and Supply of Services Act 1980 are hereby excluded.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7187
-
ITALY: Limitation of Liability (Section 3): This Section is replaced by the following: Unless otherwise provided by mandatory law, IBM is not liable for any damages which might arise.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7188
-
JAPAN: Rights In Data (Section 4): The following paragraph is added to this Section: You also agree to assign to IBM the rights regarding derivative works, as defined in Articles 27 and 28 of the Japanese Copyright Law. You also agree not to exercise your moral rights.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7189
-
NEW ZEALAND: No Warranty (Section 2): The following paragraph is added to this Section: Although IBM specifies that there are no warranties, you might have certain rights under the Consumer Guarantees Act 1993 or other legislation which cannot be excluded or limited. The Consumer Guarantees Act 1993 will not apply in respect of any goods or services which IBM provides, if you require the goods and services for the purposes of a business as defined in that Act.
Limitation of Liability (Section 3): The following paragraph is added to this Section: Where Programs are not acquired for the purposes of a business as defined in the Consumer Guarantees Act 1993, the limitations in this Section are subject to the limitations in that Act.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7190
-
UNITED KINGDOM: Limitation of Liability (Section 3): The following paragraph is added to this Section at the end of the first paragraph: The limitation of liability will not apply to any breach of IBM's obligations implied by Section 12 of the Sale of Goods Act 1979 or Section 2 of the Supply of Goods and Services Act 1982.
- Severity
- 0 : Information
- Explanation
- This is part of the Early Release of Programs License Agreement (VZ125-5544-01 10/97 (MK002))which must be accepted before a Beta test period can be started. A Beta test version allows a copy of WebSphere MQ to be used for a limited period only.
- Response
- None.
- AMQ7191
- There are <insert_1> days left in the beta test period for this copy of WebSphere MQ
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only.
- Response
- None.
- AMQ7192
- The Beta test period for this copy of WebSphere MQ has already been started.
- Severity
- 0 : Information
- Explanation
- This copy of WebSphere MQ is licensed for a limited period only and the Beta test period has been started previously.
- Response
- None.
- AMQ7193
- Reply 'yes' to accept the Agreement. Reply 'no' if you do not agree to the terms of the Agreement. Reply 'no' and submit the command again, if you want to read the Agreement again.
- Severity
- 0 : Information
- Explanation
- The IBM International License Agreement for Early Release of Programs has been displayed to the user and the user should now accept or reject the Agreement.
- Response
- Reply 'yes' or 'no' and press 'Enter'.
- AMQ7194
-
Press Enter to continue
- Severity
- 0 : Information
- Explanation
- Part of the IBM International License Agreement for Early Release of Programs has been displayed to the user. The user should press the Enter key to indicate that they are ready for the next part of the Agreement to be displayed.
- Response
- Press the Enter key when ready for the next part of the Agreement to be displayed.
- AMQ7195
- The Beta test license is not valid for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- The license <insert_3> has been installed but it is not a valid trial period license for this copy of WebSphere MQ
- Response
- Check that the correct version of the file is available.
- AMQ7196
- By installing this product, you accept the terms of the International Program License Agreement and the License Information supplied with the product.
- Severity
- 0 : Information
- Response
- None.
- AMQ7197
- A production or trial license could not be installed for this copy of WebSphere MQ
- Severity
- 20 : Error
- Explanation
- This copy of WebSphere MQ is a beta version and cannot be used with a production or trial license.
- Response
- Uninstall the beta version of WebSphere MQ and install the production or trial version.
- AMQ7198
- Insufficient license units.
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance (<insert_1>) is less than the number of processors (<insert_2>) in this machine.
- Response
- Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7198 (IBM i)
- Insufficient license units.
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance for this installation is zero.
- Response
- Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7199
- The purchased processor allowance is set to <insert_1>.
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance for this installation has been set to <insert_1> using the MQ setmqcap command.
- Response
- None.
- AMQ7199 (IBM i)
- The purchased processor allowance is set to <insert_1>.
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance for this installation has been set to <insert_1> using the MQ CHGMQMCAP command.
- Response
- None.
- AMQ7200
- The purchased processor allowance is <insert_1>
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance is currently set to <insert_1>
- Response
- Ensure sufficient license units have been purchased and, if necessary, use the MQ setmqcap command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7200 (IBM i)
- The purchased processor allowance is <insert_1>
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance is currently set to <insert_1>
- Response
- Ensure sufficient license units have been purchased and, if necessary, use the MQ CHGMQMCAP command to change the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7201
- The number of processors in this machine is <insert_1>
- Severity
- 0 : Information
- Explanation
- The operating system reports that the number of processors in this machine is <insert_1>
- Response
- None.
- AMQ7202
- The number of license units is sufficient for all future possible upgrades to this machine.
- Severity
- 0 : Information
- Explanation
- The purchased processor allowance for this installation has been set to -1, which allows any permitted processor configuration.
- Response
- None.
- AMQ7203
- Purchased processor allowance not set (use setmqcap).
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance for this installation has not been set.
- Response
- Ensure sufficient license units have been purchased and use the MQ setmqcap command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7203 (IBM i)
- Purchased processor allowance not set (use CHGMQMCAP).
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance for this installation has not been set.
- Response
- Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7203 (IBM i)
- Purchased processor allowance not set (use CHGMQMCAP).
- Severity
- 10 : Warning
- Explanation
- The purchased processor allowance for this installation has not been set.
- Response
- Ensure sufficient license units have been purchased and use the MQ CHGMQMCAP command to set the purchased processor allowance for this installation. Refer to the Quick Beginnings documentation for more information.
- AMQ7204
- WebSphere MQ queue manager <insert_3> cannot be started by this installation. It has previously been started by a newer release of WebSphere MQ.
- Severity
- 20 : Error
- Explanation
- The queue manager has previously been started by a newer release of WebSphere MQ at command level <insert_1>. This installation is not compatible with the newer release's data. Migration between these releases is not possible.
- Response
- If the queue manager's data is shared using networked storage, ensure that all installations used to start the queue manager are of the same release. The queue manager can be started by installing a release of WebSphere MQ which supports command level <insert_1> or higher.
- AMQ7205
- WebSphere MQ queue manager <insert_3> cannot be started because the authorization service is incompatible with the setting for ClusterQueueAccessControl.
- Severity
- 20 : Error
- Explanation
- The queue manager has an authorization service at version <insert_1> and the queue manager is configured to use ClusterQueueAccessControl=RQMName. The authorization service version is incompatible with this setting for ClusterQueueAccessControl, and so the queue manager cannot be started.
- Response
- Update the setting for ClusterQueueAccessControl to be XmitQ instead of RQMName, or upgrade the authorization service to a minimum of version MQZAS_VERSION_6.
- AMQ7206
- Group name has been truncated.
- Severity
- 40 : Stop Error
- Explanation
- WebSphere MQ only supports group names up to 12 characters long. The operating system is attempting to return a group longer than this.
- Response
- Reduce the group name to 12 characters or less.
- AMQ7207 (Windows)
- User ID longer than 12 characters.
- Severity
- 40 : Stop Error
- Explanation
- WebSphere MQ only supports user names up to 12 characters long. This operation is being attempted from a user name longer than this.
- Response
- Reduce the user name to 12 characters or less.
- AMQ7208
- The queue manager failed to pass a PCF message to another queue manager.
- Severity
- 10 : Warning
- Explanation
- The queue manager attempted to put a PCF message to <insert_3> to start the channel <insert_4> to cluster queue manager <insert_5>. The put failed with reason <insert_1>. When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to <insert_3>.
- Response
- Resolve the problem with <insert_3> and if necessary start the channel manually.
- AMQ7209
- The queue manager attempted to open SYSTEM.CHANNEL.INITQ which failed with reason <insert_3>
- Severity
- 10 : Warning
- Explanation
- When the queue manager resolves a cluster queue to a remote cluster queue manager, the message is put to the SYSTEM.CLUS.TRANSMIT.QUEUE. If the channel to the remote cluster queue manager is not running, the queue manager attempts to start the channel by sending a PCF message to the SYSTEM.CHANNEL.INITQ
- Response
- Resolve the problem with the SYSTEM.CHANNEL.INITQ and if necessary start the channels manually.
- AMQ7210
- The Cluster Workload exit module could not be loaded.
- Severity
- 10 : Warning
- Explanation
- The Cluster Workload exit module <insert_3> could not be loaded for reason <insert_4>.
- Response
- Correct the problem with the Cluster Workload exit module <insert_3>
- AMQ7211
- The Queue Manager is still waiting for a reply from the Cluster Workload Exit server process.
- Severity
- 10 : Warning
- Explanation
- The Queue Manager is configured to run the Cluster Workload Exit in SAFE mode. This means that the Cluster Workload Exit is run by a server process (amqzlw0). The Queue Manager has been waiting <insert_1> seconds for this server process to reply to a request to run the Cluster Workload Exit. It is possible that the exit is hung or is looping.
- Response
- End the Queue Manager, resolve the problem with the Cluster Workload Exit and restart the Queue Manager
- AMQ7212
- The address of the Cluster exit function could not be found.
- Severity
- 10 : Warning
- Explanation
- The address of the Cluster exit function <insert_4> could not be found in module <insert_3> for reason <insert_1> <insert_5>.
- Response
- Correct the problem with the Cluster exit function <insert_4> in the module <insert_3>
- AMQ7214
- The module for API Exit <insert_3> could not be loaded.
- Severity
- 40 : Stop Error
- Explanation
- The module <insert_4> for API Exit <insert_3> could not be loaded for reason <insert_5>.
- Response
- Correct the problem with the API Exit module <insert_3>.
- AMQ7215
- The API Exit <insert_3> function <insert_4> could not be found in the module <insert_5>.
- Severity
- 40 : Stop Error
- Explanation
- The API Exit <insert_3> function <insert_4> could not be found in the module <insert_5>. The internal return code was <insert_1>.
- Response
- Correct the problem with the API Exit <insert_3>.
- AMQ7215 (IBM i)
- Could not find a function in API Exit <insert_3>.
- Severity
- 40 : Stop Error
- Explanation
- The API Exit <insert_3> function <insert_4> could not be found in the module <insert_5>. The internal return code was <insert_1>.
- Response
- Correct the problem with the API Exit <insert_3>.
- AMQ7216
- An API Exit initialization function returned an error.
- Severity
- 10 : Warning
- Explanation
- The API Exit <insert_3> function <insert_4> in the module <insert_5> returned CompCode <insert_1> and ReasonCode <insert_2>.
- Response
- Correct the problem with the API Exit <insert_3>
- AMQ7217
- The response set by the exit is not valid.
- Severity
- 10 : Warning
- Explanation
- The API Exit <insert_3> module <insert_4> function <insert_5> returned a response code <insert_1> that is not valid in the ExitResponse field of the API Exit parameters (MQAXP).
- Response
- Investigate why the API Exit <insert_3> set a response code that is not valid.
- AMQ7219
- profile: <insert_3>
- Severity
- 0 : Information
- AMQ7220
- object type: <insert_3>
- Severity
- 0 : Information
- AMQ7221
- entity: <insert_3>
- Severity
- 0 : Information
- AMQ7222
- entity type: <insert_3>
- Severity
- 0 : Information
- AMQ7223
- authority: <insert_3>
- Severity
- 0 : Information
- AMQ7224
- profile: <insert_3>, object type: <insert_4>
- Severity
- 0 : Information
- AMQ7225
- No matching authority records.
- Severity
- 0 : Information
- Explanation
- No authority records match the specified parameters.
- AMQ7226
- The profile name is invalid.
- Severity
- 20 : Error
- Explanation
- The profile name contains invalid characters, contains an invalid wildcard specification, or is of invalid length.
- Response
- Correct the profile name and submit it again.
- AMQ7227
- WebSphere MQ encountered the following network error: <insert_3>
- Severity
- 10 : Warning
- Explanation
- MQ failed to successfully complete a network operation due to the specified error. If the error is encountered on systems that are part of a Windows 2000 domain it can indicate incorrect DNS or WINS configuration.
- Response
- Ensure that your network is functioning correctly. On the Windows platform check DNS and/or WINS settings to ensure that domain controllers, used for authentication or authorization functions, are accessible.
- AMQ7228 (IBM i)
- Display MQ Authority Records for <insert_3>
- Severity
- 0 : Information
- AMQ7229
- <insert_1> log records accessed on queue manager <insert_3> during the log replay phase.
- Severity
- 0 : Information
- Explanation
- <insert_1> log records have been accessed so far on queue manager <insert_3> during the log replay phase in order to bring the queue manager back to a previously known state.
- Response
- None.
- AMQ7230
- Log replay for queue manager <insert_3> complete.
- Severity
- 0 : Information
- Explanation
- The log replay phase of the queue manager restart process has been completed for queue manager <insert_3>.
- Response
- None.
- AMQ7231
- <insert_1> log records accessed on queue manager <insert_3> during the recovery phase.
- Severity
- 0 : Information
- Explanation
- <insert_1> log records have been accessed so far on queue manager <insert_3> during the recovery phase of the transactions manager state.
- Response
- None.
- AMQ7232
- Transaction manager state recovered for queue manager <insert_3>.
- Severity
- 0 : Information
- Explanation
- The state of transactions at the time the queue manager ended has been recovered for queue manager <insert_3>.
- Response
- None.
- AMQ7233
- <insert_1> out of <insert_2> in-flight transactions resolved for queue manager <insert_3>.
- Severity
- 0 : Information
- Explanation
- <insert_1> transactions out of <insert_2> in-flight at the time queue manager <insert_3> ended have been resolved.
- Response
- None.
- AMQ7234
- <insert_1> messages from queue <insert_4> loaded on queue manager <insert_3>.
- Severity
- 0 : Information
- Explanation
- <insert_1> messages from queue <insert_4> have
been loaded on queue manager <insert_3>.
This message might be issued during the WebSphere MQ checkpointing. See Using checkpointing to ensure complete recovery for more details.
- Response
- None.
- AMQ7235 (IBM i)
- Queue manager library <insert_3> already exists.
- Severity
- 40 : Stop Error
- Explanation
- The library <insert_3> already exists.
- Response
- Specify a library which does not already exist.
- AMQ7236
- WebSphere MQ queue manager <insert_3> activated.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ queue manager <insert_3> has been activated.
- Response
- None.
- AMQ7237
- WebSphere MQ queue manager <insert_3> is not a backup queue manager.
- Severity
- 10 : Warning
- Explanation
- WebSphere MQ queue manager <insert_3> is not a backup queue manager and so cannot be activated. A possible reason might be that the queue manager is configured for circular logging.
- Response
- Re-try the command without the '-a' option.
- AMQ7238
- WebSphere MQ queue manager <insert_3> replay completed.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ queue manager <insert_3> replay has completed.
- Response
- None.
- AMQ7249
- WebSphere MQ queue manager <insert_3> cannot be started for replay.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ queue manager <insert_3> cannot be started for replay. A possible reason might be that the queue manager is configured for circular logging.
- Response
- Re-try the command without the '-r' option.
- AMQ7250
- WebSphere MQ queue manager <insert_3> has not been activated.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ queue manager <insert_3> cannot be started because it has previously been started for replay but has not been activated.
- Response
- Activate the queue manager and try starting the queue manager again.
- AMQ7253
- The command <insert_3> requires one of the following arguments: <insert_4>.
- Severity
- 20 : Error
- Explanation
- The command <insert_3> required at least one of the following arguments, none of which you supplied: <insert_4>.
- Response
- Check the WebSphere MQ System Administration documentation for details on the usage of the command, correct the command and then retry.
- AMQ7254
- Incompatible WebSphere MQ queue manager <insert_3> has not been allowed to start.
- Severity
- 20 : Error
- Explanation
- An attempt to start a <insert_1>-bit queue manager was made, this was not allowed as previously this was a <insert_2>-bit queue manager. Migration between the previous <insert_2>-bit version to current <insert_1>-bit version is not possible and would result in an unrecoverable corrupted queue manager.
- Response
- Either delete this queue manager or uninstall the current <insert_1>-bit version and reinstall the previous <insert_2>-bit version.
- AMQ7255
- Arguments supplied to a command are incompatible.
- Severity
- 20 : Error
- Explanation
- You supplied arguments to a command that it could not interpret. It is probable that you specified one or more flags that cannot be used at the same time.
- Response
- Correct the command and submit it again. Additional information on the arguments causing the error might be found in the error logs for the queue manager referenced in the command.
- AMQ7256
- Trace directory <insert_3> has restricted permissions <insert_4>.
- Severity
- 10 : Warning
- Explanation
- The directory <insert_3> on your system has permissions <insert_4>. Some programs might attempt to write trace files to this directory, and fail because of these restricted permissions.
- Response
- If you want all WebSphere MQ programs on the system to be able to write trace, it is possible these permissions will restrict them from doing so. Please review the permissions and reset them to the product default, as appropriate.
- AMQ7257 (Windows)
- The MQ service for installation <insert_2> (<insert_3>) must be running.
- Severity
- 40 : Stop Error
- Explanation
- The command <insert_1> requires the MQ service, amqsvc.exe, and process amqpsrvn.exe, which it launches, to be running.
- Response
- Ensure that the MQ service is running before issuing the command.
Start the service in one of the following ways:
- From an administrative command prompt, issue the command: <insert_3>\bin\strmqsvc.exe
- From the Computer Management console, select and start the service named 'IBM WebSphere MQ (<insert_2>)' from the list of services shown.
- AMQ7258
- WebSphere MQ queue manager <insert_3> running as a standby.
- Severity
- 0 : Information
- Explanation
- Queue manager <insert_3> is running as a standby instance, ready to become the primary instance if the existing primary instance fails.
- Response
- None.
- AMQ7259
- WebSphere MQ queue manager <insert_3> could not obtain data lock.
- Severity
- 20 : Error
- Explanation
- Queue manager <insert_3> could not be started because it could not obtain a lock on its data in the file-system. The most likely cause is that the queue manager is running on another computer.
- Response
- None.
- AMQ7260
- WebSphere MQ queue manager <insert_3> is not permitted to become a standby.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ queue manager <insert_3> could not obtain a lock on its data in the file-system. It was not permitted to become a standby instance waiting to obtain the lock.
- Response
- None.
- AMQ7261
- The heuristically completed transaction has been forgotten.
- Severity
- 0 : Information
- Explanation
- The heuristically completed transaction has now been forgotten by the queue manager.
- Response
- None.
- AMQ7262
- <insert_1> heuristically completed transactions for queue manager <insert_3>.
- Severity
- 0 : Information
- Explanation
- There are <insert_1> heuristically completed transactions for queue manager <insert_3>. These transactions will remain heuristically completed until the queue manager is instructed to forget them by the transaction manager or the system administrator.
- Response
- None.
- AMQ7263
- Directory is not located on a local filesystem (<insert_5>).
- Severity
- 10 : Warning
- Explanation
- Directory <insert_4> appears to be located on a <insert_5> file system. Although WebSphere MQ allows you to create this directory on a non-local file system it is not recommended. Please refer to the System Administration Guide for further information on configuring WebSphere MQ to use shared networked file systems.
- Response
- None.
- AMQ7264
- IPC directory path is too long.
- Severity
- 40 : Stop Error
- Explanation
- IPC directory <insert_3> is too long for this environment. The length of the IPC directory path is <insert_1> characters, however the maximum length allowable is only <insert_2> characters.
- Response
- The length of the IPC directory path can be reduced by specifying a shorter IPC directory prefix when creating the queue manager, or, by shortening the queue manager name.
- AMQ7265
- Extended message selection available.
- Severity
- 0 : Information
- Explanation
- A connection has been made by an application capable of performing extended selection of messages on behalf of IBM WebSphere® MQ, including on the content of the message. Extended message selection is now available to subscriptions.
- Response
- None.
- AMQ7266
- Extended message selection not available.
- Severity
- 0 : Information
- Explanation
- The application that connected in order to perform extended selection of messages has now disconnected. Extended message selection is no longer available to subscriptions.
- Response
- None.
- AMQ7267
- IBM WebSphere MQ configuration information added.
- Severity
- 0 : Information
- Explanation
- IBM WebSphere MQ configuration information has been added successfully.
- Response
- None.
- AMQ7268
- IBM WebSphere MQ configuration information removed.
- Severity
- 0 : Information
- Explanation
- IBM WebSphere MQ configuration information has been removed successfully.
- Response
- None.
- AMQ7269
- A standby instance of queue manager <insert_5> has been started. The active instance is running elsewhere.
- Severity
- 0 : Information
- Explanation
- You tried to start the queue manager but it is already running elsewhere. A standby instance of the queue manager started, ready to become the active instance if the existing active instance fails.
- Response
- None.
- AMQ7270
- WebSphere MQ queue manager <insert_3> is already running elsewhere. It permits standby instances.
- Severity
- 0 : Information
- Explanation
- IBM WebSphere MQ queue manager <insert_3> could not obtain a lock on its data in the file-system when it was starting. The lock is held by the active instance of the queue manager. The active instance of the queue manager was started permitting standby instances.
- Response
- If you are trying to start multiple instances of a queue manager to make it highly available, you must start all of the instances using strmqm -x.
- AMQ7271
- IBM WebSphere MQ configuration information does not exist.
- Severity
- 20 : Error
- Explanation
- IBM WebSphere MQ configuration information does not exist.
- Response
- None.
- AMQ7272
- IBM WebSphere MQ configuration information already exists.
- Severity
- 20 : Error
- Explanation
- IBM WebSphere MQ configuration information already exists.
- Response
- None.
- AMQ7273
- Configuration attribute <insert_3> must be supplied.
- Severity
- 20 : Error
- Explanation
- IBM WebSphere MQ configuration attribute <insert_3> is required for this stanza.
- Response
- Supply a value for this attribute and reissue the command.
- AMQ7274
- IBM WebSphere MQ queue manager <insert_3> already has the maximum number of standby instances.
- Severity
- 20 : Error
- Exaplanation
- You tried to start the queue manager but it is already running elsewhere. It is not possible to start another standby instance because the queue manager has already reached the maximum number of standby instances.
- Response
- None
- AMQ7276
- IBM WebSphere MQ queue manager cannot switch over.
- Severity
- 20 : Error
- Explanation
- You cannot switch over the queue manager. This might be because the queue manager does not have a standby instance or the queue manager is ending.
- Response
- None
- AMQ7279
- IBM WebSphere MQ queue manager <insert_3> lost ownership of data lock.
- Severity
- 20 : Error
- Explanation
- The instance of queue manager <insert_3> has lost ownership of a lock on its data in the file-system due to a transient failure. It was not able to reobtain the lock and will stop automatically to prevent the risk of data corruption.
- Response
- Check that another instance of the queue manager has become active. Restart this instance of the queue manager as a standby instance. If this problem recurs, it may indicate that the file-system is not sufficiently reliable to support file locking by a multi-instance queue manager.
- AMQ7280
- WebSphere MQ queue manager <insert_3> appears unresponsive.
- Severity
- 20 : Error
- Explanation
- The queue manager is monitoring itself for responsiveness. It is not responding sufficiently quickly and will automatically stop if it continues to be unresponsive.
- Response
- None.
- AMQ7282
- Library name 'insert_3' is not expected value of 'insert_4'.
- Severity
- 20 : Error
- Explanation
The supplied queue manager library name of <insert_3> does not match the expected value of <insert_4> that was used when queue manager <insert_5> was previously created or started.
If a backup or multi-instance queue manager is being configured and the queue manager library is deliberately different between systems, this has the consequence that queue manager journals must be configured.
- Response
- Check that the library name <insert_3> is correct for this queue manager instance. If the library name is incorrect, use the RMVMQMINF command to remove the incorrect information and ADDMQMINF to re-enter the correct configuration information.
- AMQ7285
- The data contained within file <insert_3> cannot be processed by command <insert_4>.
- Severity
- 20 : Error
- Explanation
- The file <insert_3> was read by the program insert_4 but the contents of the file were found to be incorrect. Possibly this error occurs because the file <insert_4> was incorrectly specified as an argument to command <insert_4> or possibly the file is corrupt.
- Response
- Ensure the file <insert_3> is of the required format and submit the command again.
- AMQ7286
- An error occurred while restoring the cluster cache, see the error logs for details
- Severity
- 10 : Warning
- Explanation
- One or more errors were detected while restoring the cluster cache. This will not prevent the queue manager from starting but the cluster cache held by this queue manager is now incomplete which may result in inconsistencies in cluster resources visible to and owned by this queue manager. See messages in the error logs for details of the error encountered.
- Response
- Contact your IBM support center to resolve the problem.
- AMQ7287
- The command level is outside the range of acceptable values. The value must be at least <insert_3> and must not exceed <insert_4>.
- Severity
- 20 : Error
- Explanation
- The command level specified lies outside the range of acceptable values for this command's installation.
- Response
- Reissue the command specifying a command level in the range of acceptable.
- AMQ7288
- The queue manager's command level is already <insert_2>. No new function has been enabled.
- Severity
- 20 : Error
- Explanation
- The queue manager's command level is already greater than or equal to the value specified.
- Response
- None.
- AMQ7289
- The MQ service for installation <insert_3> failed to start with error <insert_1>.
- Severity
- 40 : Stop Error
- Explanation
The attempt to start the MQ service (amqsvc.exe) for installation 'insert_3' failed, the error from the operating system was <insert_1>.
The formatted message text for error <insert_1> is <insert_4> (if blank this indicates that no message text was available).
- Response
In order for the MQ service to start it must have been configured to run using the Prepare WebSphere MQ Wizard, if this has not already happened the service may be configured with an invalid userid or be in a 'Disabled' state.
Check that the service named 'IBM WebSphere MQ (insert_3)' has been properly configured and is enabled, then re-issue the command.
- AMQ7290
- The MQ service for installation <insert_3> started successfully.
- Severity
- 0 : Information
- Explanation
- The MQ service for installation <insert_3> was successfully started, or already running.
- Response
- None.
- AMQ7291
- Severity
- 40 : Stop Error
- Explanation
- The attempt to end the MQ service (amqsvc.exe) for installation <insert_3> failed, the error from the operating system was <insert_1>. The formatted message text for error <insert_1> is <insert_4> (if blank this indicates that no message text was available).
- Response
- Check that the service named 'IBM WebSphere MQ <insert_3>' has been properly configured and is enabled, then re-issue the command.
- AMQ7292
- The MQ service for installation <insert_3> ended successfully.
- Severity
- 0 : Information
- Explanation
- The MQ service for installation <insert_3> was successfully ended, or already stopped.
- Response
- None.
- AMQ7293
- Usage: strmqsvc
- Severity
- 0 : Information
- Explanation
- This shows the correct usage.
- Response
- None.
- AMQ7294
- Usage: endmqsvc
- Severity
- 0 : Information
- Explanation
- This shows the correct usage.
- Response
- None.
- AMQ7295
- IBM WebSphere MQ queue manager <insert_3> has not been allowed to start due to migration not being supported.
- Severity
- Explanation
- An attempt to start MQ queue manager <insert_3> was made. This was not allowed as previously this queue manager was started by an older version of MQ. Migration between these releases is not supported.
- Response
- If the queue manager data is shared, ensure that this queue manager is being started on the correct operating system. The queue manager can be started by installing a compatible release of IBM WebSphere MQ. See: https://www.ibm.com/software/integration/wmq/requirements
- AMQ7305
- Trigger message could not be put on an initiation queue.
- Severity
- 10 : Warning
- Explanation
- The attempt to put a trigger message on queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be put on the dead-letter queue.
- Response
- Ensure that the initiation queue is available, and operational.
- AMQ7306
- The dead-letter queue must be a local queue.
- Severity
- 10 : Warning
- Explanation
- An undelivered message has not been put on the dead-letter queue <insert_4> on queue manager <insert_5>, because the queue is not a local queue. The message will be discarded.
- Response
- Inform your system administrator.
- AMQ7307
- A message could not be put on the dead-letter queue.
- Severity
- 10 : Warning
- Explanation
- The attempt to put a message on the dead-letter queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be discarded.
- Response
- Ensure that the dead-letter queue is available and operational.
- AMQ7308
- Trigger condition <insert_1> was not satisfied.
- Severity
- 0 : Information
- Explanation
- At least one of the conditions required for generating a trigger message was not satisfied, so a trigger message was not generated. If you were expecting a trigger message, consult the WebSphere MQ Application Programming Guide for a list of the conditions required. (Note that arranging for condition <insert_1> to be satisfied might not be sufficient because the conditions are checked in an arbitrary order, and checking stops when the first unsatisfied condition is discovered.)
- Response
- If a trigger message is required, ensure that all the conditions for generating one are satisfied.
- AMQ7310
- Report message could not be put on a reply-to queue.
- Severity
- 10 : Warning
- Explanation
- The attempt to put a report message on queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>. The message will be put on the dead-letter queue.
- Response
- Ensure that the reply-to queue is available and operational.
- AMQ7315
- Failed to put message to accounting queue. Reason(<insert_1>)
- Severity
- 20 : Error
- Explanation
- The attempt to put a message containing accounting data to the
queue <insert_3> failed with reason code <insert_1>.
The message data has been discarded.
This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason.
- Response
- Ensure that the queue <insert_3> is available and operational.
- AMQ7316
- Failed to put message to statistics queue. Reason(<insert_1>)
- Severity
- 20 : Error
- Explanation
- The attempt to put a message containing statistics data to the
queue <insert_3> failed with reason code <insert_1>.
The message data has been discarded.
This error message will be written only once for attempts to put a message to the queue as part of the same operation which fail for the same reason.
- Response
- Ensure that the queue <insert_3> is available and operational.
- AMQ7320
- Failed to access the retained publication queue. Reason(<insert_1>)
- Severity
- 20 : Error
- Explanation
- An attempt to access messages on the system retained publication queue (<insert_3>) failed with reason code <insert_4> (<insert_1>).
- Response
- Ensure that the queue <insert_3> is available and operational.
- AMQ7327
- Failed to open topic object <insert_3> (referenced by <insert_4>)
- Severity
- 20 : Error
- Explanation
- Each entry in <insert_4> must have an
existing topic object, which has been created before the entry is
added to the namelist.
The topic object <insert_3> does not exist, and must be created before that stream or subpoint can be used
- Response
- Ensure that the topic object <insert_3> is available. Remove the entry and add it again to the <insert_4> namelist to notify the queue manager to check the topic object again.
- AMQ7341 (krcI_CLUSSDR_XMITQ_SWITCHED)
- The transmission queue for channel <insert_1> is <insert_3>.
- Severity
- 00 : Information
- Explanation
- The switch of transmission queue for channel <insert one> was required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue.
- Response
- No further action required.
- AMQ7342 (krcE_CLUSSDR_XMITQ_SWITCH_FAILED)
- WebSphere MQ was unable to display an error message
20007342
- Severity
- 40 : Error
- Explanation
- IBM WebSphere MQ attempted
to display the message associated with return code
X'20007342'
. The return code indicates that there is no message text associated with the message. Associated with the request are inserts <n> : <m> : <insertone> : <insert two> : <insert three>. - Response
- Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. See IBM WebSphere MQ support web page, or IBM SupportAssistant web page, to find out if a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7343 (krcE_DYNAMIC_Q_NOT_CREATED)
- The request to create a dynamic queue named <insert one> failed with reason code <n>.
- Severity
- 40 : Error
- Explanation
- A request was made to create a dynamic queue with the name <insert
one>, based upon the model queue <insert two>,
but the operation failed with reason code <n>.
Possible reasons for the failure include:
- A queue of a different type with the same name already exists.
- The model queue could not be accessed.
- Insufficient resources were available to successfully complete the request.
- Response
- Use the supplied reason code to correct the cause of the failure and reissue the request.
- AMQ7345 (krcE_OPEN_OLD_CLUSTER_XMITQ_FAILED)
- Unable to open transmission queue <insert two> for channel <insert one>.
- Severity
- 40 : Error
- Explanation
- In order to process the switch of transmission queue the original transmission queue <insert two> must be opened in order to move any pending messages to the new transmission queue. The open request failed with reason code <n>. The switch of transmission queue for channel <insert one> cannot proceed.
- Response
- In order to allow the switch to progress, use the reason code
provided to identify the cause of the failure and resolve the problem.
If the issue cannot be resolved, or the original transmission queue
has been deleted, use the runswchl command with
the -n parameter to cause the transmission queue
for the channel to be switched without attempting to move any messages
from the original transmission queue to the new transmission queue. Remember: When using this option it is the responsibility of the IBM WebSphere MQ administrator to deal with any messages pending on the original transmission queue.
- AMQ7346 (krcE_OPEN_NEW_CLUSTER_XMITQ_FAILED)
- Unable to open new transmission queue <insert two> for channel <insert one>.
- Severity
- 40 : Error
- Explanation
- In order to process the switch of transmission queue the new transmission queue <insert three> must be opened in order to receive any pending messages from the old transmission queue. The open request failed with reason code <n>. The switch of transmission queue for channel <insert one> cannot proceed.
- Response
- In order to allow the switch to progress use the reason code provided to identify the cause of the failure and resolve the problem.
- AMQ7347 (krcE_INTERNAL_MQGET_FAILED)
- MQGET from queue <insert one> failed with reason code <n>.
- Severity
- 40 : Error
- Explanation
- An internal MQGET request called as part of a queue manager operation failed with Reason Code <n>.
- Response
- This error message is issued in association with further error messages which explain the implications of this failure. Use the Queue Name <insert one> and reason code <n> provided in this message in conjunction with the messages which follow to resolve the problem.
- AMQ7348 (krcE_INTERNAL_MQPUT_FAILED)
- MQPUT to queue <insert one> failed with reason code <n>.
- Severity
- 40 : Error
- Explanation
- An internal MQPUT request called as part of a queue manager operation failed with reason code <n>.
- Response
- This error message is issued in association with further error messages which explain the implications of this failure. Use the Queue Name <insert one> and reason code <n> provided in this message in conjunction with the messages which follow to resolve the problem.
- AMQ7349 (krcE_INTERNAL_MQCMIT_FAILED)
- MQCMIT failed with reason code <n>.
- Severity
- 40 : Error
- Explanation
- An internal MQCMIT request called as part of a queue manager operation failed with reason code <n>.
- Response
- This error message is issued in association with further error messages which explain the implications of this failure. Use the reason code <n> provided in this message in conjunction with the messages which follow to resolve the problem.
- AMQ7350 (krcI_CLUSSDR_XMITQ_SWITCH_STARTED)
- The switch of transmission queue from queue <insert two> to queue <insert three> for channel <insert one> has been started.
- Severity
- 00 : Information
- Explanation
- The switch of transmission queue for channel <insert one> is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is written when the process of switching the transmission queue is started.
- Response
- None.
- AMQ7351 (krcI_CLUSSDR_XMITQ_SWITCH_MM_STARTED)
- The moving of messages for channel <insert one> from transmission queue <insert two> to transmission queue <insert three> has started.
- Severity
- 00 : Information
- Explanation
- The switch of transmission queue for channel <insert one> is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is written when the process of moving messages from the old transmission queue <insert two> to the new transmission queue is started.
- Response
- None.
- AMQ7352 (krcI_CLUSSDR_XMITQ_MM_STATUS)
- <n> messages have been moved from queue <insert two> to queue <insert three>.
- Severity
- 00 : Information
- Explanation
- The switch of transmission queue for channel <insert one> requires that messages are moved from the old transmission queue to the new transmission queue. <m> messages have been moved from queue <insert two> to queue <insert three> <n> times. The queue has been empty, but a message arrived before the switch could be completed.
- Response
- None.
- AMQ7353 (krcE_SYNCFILE_UPDATE_FAILED)
- Unable to update the channel synchronization file during the switch of transmission queue for channel <insert one>.
- Severity
- 40 : Error
- Explanation
- The queue manager was unable to update the channel synchronization file while completing the change of transmission queue from <insert two> to <insert three> for channel <insert one>. The reason code for the failure was <n>.
- Response
- Use the reason code provided, and any other failure messages to
correct the cause of the failure, before using the rcrmqobj command
to recover the contents of the channel synchronization file. Run the
command:
The command rebuilds the synchronization file for the queue manager; see rcrmqobj .rcrmqobj -m QMgrName -t syncfile
- AMQ7432 (IBM i)
- WebSphere MQ journal entry not available for replay.
- Severity
- 40 : Stop Error
- Explanation
- A journal replay operation was attempted, but the operation required journal entries from journal receivers that are not currently present on the system.
- Response
- Restore the required journal receivers from backup. Then try the operation again.
- AMQ7433 (IBM i)
- An Error occurred while performing a journal replay.
- Severity
- 40 : Stop Error
- Explanation
- WebSphere MQ encountered a problem reading one or more journal entries while performing a journal replay operation.
- Response
- If you have previously created a journal receiver for a queue manager or are performing a cold restart of a queue manager, delete the QMQMCHKPT file from the queue manager subdirectory in /QIBM/UserData/mqm/qmgrs/ and attempt to restart the queue manager. If the problem persists, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7434 (IBM i)
- The MQ commitment control exit program was called incorrectly. Code <insert_1>.
- Severity
- 40 : Stop Error
- Explanation
- The WebSphere MQ commitment control exit program was called with incorrect parameters.
- Response
- If the program was called by OS/400 as part of a commit or rollback, save the job log, and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7435 (IBM i)
- The MQ commitment control exit program failed. Code <insert_1>.
- Severity
- 40 : Stop Error
- Explanation
- The WebSphere MQ commitment control exit program failed due to an unexpected error.
- Response
- Save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7459 (IBM i)
- WebSphere MQ journal receiver <insert_3> is the oldest in the chain
- Severity
- 0 : Information
- Explanation
- The oldest journal receiver in the receiver chain is <insert_3> in library <insert_4>.
- Response
- None
- AMQ7460 (IBM i)
- WebSphere MQ startup journal information.
- Severity
- 0 : Information
- Explanation
- This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for startup recovery.
- Response
- None
- AMQ7461 (IBM i)
- WebSphere MQ object re-created - reapply authorities.
- Severity
- 0 : Information
- Explanation
- A previously damaged object has been re-created, either automatically, or by explicit use of the re-create Object (RCRMQMOBJ) command. The authorities that applied to this object have not been re-created.
- Response
- Use the Grant Authority (GRTMQMAUT) command, as appropriate, to re-create the required authorities to this MQ object.
- AMQ7462 (IBM i)
- WebSphere MQ media recovery journal information.
- Severity
- 0 : Information
- Explanation
- This message is issued periodically by WebSphere MQ to help you identify which journal receivers can be removed from the system because they are no longer required for media recovery.
- Response
- None
- AMQ7463
- The log for queue manager <insert_3> is full.
- Severity
- 20 : Error
- Explanation
- This message is issued when an attempt to write a log record is rejected because the log is full. The queue manager will attempt to resolve the problem.
- Response
- This situation might be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you might have to consider enlarging the size of the log. You can either increase the number of log files by changing the values in the queue manager configuration file. You will then have to stop and restart the queue manager. Alternatively, if you need to make the log files themselves bigger, you will have to delete and re-create the queue manager.
- AMQ7464
- The log for queue manager <insert_3> is no longer full.
- Severity
- 0 : Information
- Explanation
- This message is issued when a log was previously full, but an attempt to write a log record has now been accepted. The log full situation has been resolved.
- Response
- None
- AMQ7465
- The log for queue manager <insert_3> is full.
- Severity
- 20 : Error
- Explanation
- An attempt to resolve a log full situation has failed. This is due to the presence of a long-running transaction.
- Response
- Try to ensure that the duration of your transactions is not excessive. Commit or roll back any old transactions to release log space for further log records.
- AMQ7466
- There is a problem with the size of the logfile.
- Severity
- 10 : Warning
- Explanation
- The log for queue manager <insert_3> is too small to support the current data rate. This message is issued when the monitoring tasks maintaining the log cannot keep up with the current rate of data being written.
- Response
- The number of primary log files configured should be increased to prevent possible log full situations.
- AMQ7467
- The oldest log file required to start queue manager <insert_3> is <insert_4>.
- Severity
- 0 : Information
- Explanation
- The log file <insert_4> contains the oldest log record required to restart the queue manager. Log records older than this might be required for media recovery.
- Response
- You can move log files older than <insert_4> to an archive medium to release space in the log directory. If you move any of the log files required to re-create objects from their media images, you will have to restore them to re-create the objects. An older log file is one with a numerically smaller log number (but allowing for log number wrapping at 9999999).
- AMQ7468
- The oldest log file required to perform media recovery of queue manager <insert_3> is <insert_4>.
- Severity
- 0 : Information
- Explanation
- The log file <insert_4> contains the oldest log record required to re-create any of the objects from their media images. Any log files prior to this will not be accessed by media recovery operations.
- Response
- Use this information together with the information in the most recent AMQ7467 message. Archivable log files are all those older than BOTH <insert_4> and the log file mentioned in the AMQ7467 message.
- AMQ7469
- Transactions rolled back to release log space.
- Severity
- 0 : Information
- Explanation
- The log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that the queue manager can continue to process requests.
- Response
- Try to ensure that the duration of your transactions is not excessive. Consider increasing the size of the log to allow transactions to last longer before the log starts to become full.
- AMQ7472
- Object <insert_3>, type <insert_4> damaged.
- Severity
- 10 : Warning
- Explanation
- Object <insert_3>, type <insert_4> has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected.
- Response
- If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it can be recovered from a media image using the rcrmqobj command or it can be deleted.
- AMQ7472 (IBM i)
- Object <insert_3>, type <insert_4> damaged.
- Severity
- 10 : Warning
- Explanation
- Object <insert_3>, type <insert_4> has been marked as damaged. This indicates that the queue manager was either unable to access the object in the file system, or that some kind of inconsistency with the data in the object was detected.
- Response
- If a damaged object is detected, the action performed depends on whether the queue manager supports media recovery and when the damage was detected. If the queue manager does not support media recovery, you must delete the object as no recovery is possible. If the queue manager does support media recovery and the damage is detected during the processing performed when the queue manager is being started, the queue manager will automatically initiate media recovery of the object. If the queue manager supports media recovery and the damage is detected once the queue manager has started, it can be recovered from a media image using the RCRMQMOBJ command or it can be deleted.
- AMQ7477 (IBM i)
- WebSphere MQ session no longer active.
- Severity
- 10 : Warning
- Explanation
- The commitment control exit program was called during a commit or rollback operation. The queue manager was stopped while the program was registered. This might have resulted in the rolling back of some uncommitted message operations.
- Response
- Inform your system administrator that uncommitted message operations might have been rolled back when the queue manager was stopped.
- AMQ7484
- Failed to put message to logger event queue. Reason(<insert_2>)
- Severity
- 0 : Information
- Explanation
- The attempt to put a logger event message to the queue <insert_3> failed with reason code <insert_2>. The message data has been discarded.
- Response
- Ensure that the queue <insert_3> is available and operational. Current logger status information can be displayed with the DISPLAY QMSTATUS runmqsc command.
- AMQ7485
- Transactions rolled forward to release log space.
- Severity
- 0 : Information
- Explanation
- The log space for the queue manager is becoming full. One or more long-running prepared transactions have been rolled forward to release log space so that the queue manager can continue to process requests. Equivalent log records for the long-running prepared transactions have been created in the active log.
- Response
By the time you read this message, the long-running prepared transaction might already have been resolved automatically. If it is not resolved, this message reappears repeatedly whenever the log space for the queue manager is becoming full.
The following steps assume that there is a prepared transaction that is not being resolved automatically. You should investigate what type of transaction it is, and take steps appropriate to the type of transaction.
Use the DSPMQTRN command to check for externally managed in-doubt transactions and the DISPLAY CHS runmqsc command to check for in-doubt channels.
There are several possible responses:- If the long-running transaction is owned by external transaction manager software, then the queue manager cannot decide automatically to resolve it (commit it or roll it back). The queue manager remembers its work for this transaction until the external transaction manager software tells the queue manager the outcome (that is, either to commit the transaction or to roll it back). Therefore you must address this issue through your external transaction manager software, either by issuing commands to it, or (if no such commands exist) by restarting it.
- If the long-running transaction is owned by an in-doubt channel, then investigate its status. If it will not automatically resolve, then consider using the RESOLVE CHANNEL command.
- If the long-running transaction is owned by the local queue manager on behalf of an application using MQBEGIN, then perhaps the queue manager has lost contact with external resource manager software that participated in the transaction. Investigate and correct the connectivity from the queue manager to the external resource manager software.
- If none of the other options succeed, consider using the rsvmqtrn command to tell the queue manager to commit or roll back its work done within the in-doubt transaction. Refer to the description of the rsvmqtrn command in the product documentation.
- AMQ7486
- Transaction 1111.2222 was preventing log space from being released.
- Severity
- 0 : Information
- Explanation
- A long running transaction was detected. Message AMQ7469 or AMQ7485 has been issued indicating if the transaction was rolled back or rolled forward in the log to allow the log space to be released. The internal transaction identifier is 1111.2222 which can be correlated with 'dspmqtrn -a' output. The transaction started at <insert_1> and first wrote to the queue manager recovery log at <insert_2>. The following transaction context might be useful in identifying the application causing this behaviour: <insert_3>. This message can be correlated with the previous AMQ7469 or AMQ7485 message in the queue manager error logs.
- Response
- Identify the application responsible for the long running unit of work and ensure this application is creating and completing transactions in a timely manner. If the application is working as expected it may be appropriate to increase the size of the queue manager recovery log.
- AMQ7487
- Application <insert_1> was preventing log space from being released.
- Severity
- 0 : Information
- Explanation
- A long running transaction was detected, this message is intended to help identify the application associated with this long running transaction. Message AMQ7469 or AMQ7485 has been issued indicating if the transaction was rolled back or rolled forward in the log to allow the log space to be released. Message AMQ7486 has been issued identifying the transaction context of the transaction that was rolled back or rolled forwards. The application associated with this transaction was running with Pid 1111, Tid 2222, under application name <insert_1> and with application description <insert_2>. The following application context may also be useful in identifying the application causing this behaviour:<insert_3>. This message can be correlated with the previous AMQ7486 message in the queue manager error logs.
- Response
- Identify the application responsible for the long running unit of work and ensure this application is creating and completing transactions in a timely manner. If the application is working as expected it may be appropriate to increase the size of the queue manager recovery log.
- AMQ7540
- WebSphere MQ program <insert_3> attempted to access file or directory (<insert_4>), however it does not exist.
- Severity
- 20 : Error
- Explanation
- <insert_3> is not running as the root UserID, so cannot create the nonexistent file or directory (<insert_4>).
- Response
- If you believe there are existing MQ installations on this machine, or you wish to create a new MQ installation entry, rerun the command as UserID root.
- AMQ7541
- WebSphere MQ program <insert_3> attempted to access file or directory (<insert_4>), however access is denied.
- Severity
- 20 : Error
- Explanation
- <insert_3> is not running as the root UserID, and does not have access to file or directory (<insert_4>).
- Response
- Either correct the permissions to allow access to (<insert_4>), or rerun the command with sufficient authority.
- AMQ7542
- WebSphere MQ program <insert_3> found that file or directory (<insert_4>) permissions were not as expected.
- Severity
- 20 : Error
- Explanation
- <insert_3> is not runnig as the root UserID, so cannot correct file or directory (<insert_4>) permissions.
- Response
- Either correct the permissions to (<insert_4>), or rerun the command with sufficient authority to correct the permissions.
- AMQ7543
- WebSphere MQ program <insert_3> found that file (<insert_4>) was corrupt but has been repaired.
- Severity
- 0 : Information
- Explanation
- <insert_3> found that file (<insert_4>) was corrupt and therefore has been repaired.
- Response
- Whilst <insert_3> has repaired (<insert_4>), you may wish to check that the output from WebSphere MQ program dspmqinst reflects the state of the WebSphere MQ installations on this machine.
- AMQ7544
- WebSphere MQ program <insert_3> found that configuration data held in (<insert_4>) is corrupt.
- Severity
- 20 : Error
- Explanation
- <insert_3> needs to access MQ configuration data held in (<insert_4>), however the data has been corrupted.
- Response
- Contact your IBM support center.
- AMQ7545
- WebSphere MQ program <insert_3> was supplied an invalid installation path.
- Severity
- 20 : Error
- Explanation
- <insert_3> was supplied with installation path (<insert_4>), however this matches an entry with a different installation name.
- Response
- Correct the installation path and rerun the command.
- AMQ7546
- WebSphere MQ program <insert_3> was supplied an invalid installation name.
- Severity
- 20 : Error
- Explanation
- <insert_3> was supplied with installation name (<insert_4>), however this matches an entry with a different installation path.
- Response
- Correct the installation name and rerun the command.
- AMQ7547
- Entry created successfully.
- Severity
- 0 : Information
- Explanation
- <insert_3> has successfully created the entry.
- Response
- None.
- AMQ7548
- Entry deleted successfully.
- Severity
- 0 : Information
- Explanation
- <insert_3> has successfully deleted the entry.
- Response
- None.
- AMQ7549
- Entry does not exist.
- Severity
- 20 : Error
- Explanation
- <insert_3> could not find an entry that matched the supplied parameters.
- Response
- Use the WebSphere MQ program dspmqinst to display all the WebSphere MQ installations on this machine, then rerun the command with valid parameters.
- AMQ7550
- Entry is still active and has not been deleted.
- Severity
- 20 : Error
- Explanation
- <insert_3> has found that the entry to be deleted is still an active installation and therefore has not been deleted.
- Response
- Uninstall the installation then rerun the command.
- AMQ7551
- Entry uninstalled successfully.
- Severity
- 0 : Information
- Explanation
- <insert_3> has successfully uninstalled the entry.
- Response
- None.
- AMQ7552
- WebSphere MQ program <insert_3> did not complete successfully.
- Severity
- 20 : Error
- Explanation
- <insert_3> found problems with file (<insert_4>) and therefore could not successfully complete the command.
- Response
- Check the WebSphere MQ error logs and check if there are any FFST files for further details.
- AMQ7553
- WebSphere MQ program <insert_3> did not complete successfully.
- Severity
- 20 : Error
- Explanation
- <insert_3> had an unexpected error and therefore could not successfully complete the command.
- Response
- Check the WebSphere MQ error logs and check if there are any FFST files for further details.
- AMQ7554
- WebSphere MQ program <insert_3> was supplied an invalid installation descriptive text.
- Severity
- 20 : Error
- Explanation
- <insert_3> was supplied with installation descriptive text (<insert_4>), however this exceeds the maximum length allowed (<insert_1>).
- Response
- Correct the installation descriptive text and rerun the command.
- AMQ7555
Usage: crtmqinst ((-n InstName | -p InstPath) [-d Text] )&P -d Descriptive text. &N -n Installation name. &N -p Installation path.
- Severity
- 0
- Explanation
- This shows the correct usage.
- Response
- None.
- AMQ7556
Usage: dltmqinst (-n InstName | -p InstPath) &P -n Installation name. &N -p Installation path.
- Severity
- 0
- Explanation
- This shows the correct usage.
- Response
- None.
- AMQ7557
Usage: dspmqinst [-n InstName | -p InstPath] &P -n Installation name. &N -p Installation path.
- Severity
- 0
- Explanation
- This shows the correct usage.
- Response
- None.
- AMQ7558
- WebSphere MQ program <insert_3> has detected
an invalid installation in path (<insert_4>).
The minimum supported level of MQ for coexistence with another version
of MQ is version: <insert_5>. This message may
be the result of installing MQ onto a machine which already had an
old version of MQ installed; or a FixPack may have been removed from
the installation in path (<insert_4>).
The configuration of this machine is not supported. You should uninstall or upgrade to the minimum supported level, the installation in path (<insert_4>); or uninstall any secondary MQ installations.
- Severity
- 40 : Stop Error
- Explanation
- <insert_3> has detected an invalid installation in path (<insert_4>). The minimum supported level of MQ for coexistence with another version of MQ is version: <insert_5>. This message may be the result of installing MQ onto a machine which already had an old version of MQ installed; or a FixPack may have been removed from the installation in path (<insert_4>).
- Response
- The configuration of this machine is not supported. You should uninstall or upgrade to the minimum supported level, the installation in path (<insert_4>); or uninstall any secondary MQ installations.
- AMQ7559
- WebSphere MQ program <insert_3> has detected an invalid installation.
- Severity
- 40 : Stop Error
- Explanation
- <insert_3> has detected an invalid installation in path (<insert_4>). The minimum supported level of MQ for coexistence with another version of MQ is version: <insert_5>. This message may be the result of installing MQ onto a machine which already had an old version of MQ installed; or a FixPack may have been removed from the installation in path (<insert_4>).
- Response
- The configuration of this machine is not supported. You should uninstall or upgrade to the minimum supported level, the installation in path (<insert_4>); or uninstall any secondary MQ installations.
- AMQ7560
- WebSphere MQ program <insert_3> failed to get a lock on file (<insert_4>).
- Severity
- 20 : Error
- Explanation
- <insert_3> attempted to lock file (<insert_4>) to ensure any reading or writing of the file would not result in the file being corrupted.
- Response
- The file permissions may be incorrect or another process may be preventing <insert_3> to obtain the lock. If it is the latter case, the value supplied here for the process identifier (<insert_1>) will be a non zero value, in this case rerun the command when that process has ended.
- AMQ7561
- WebSphere MQ program <insert_3> did not complete successfully due to a lack of system resources.
- Severity
- 20 : Error
- Explanation
- <insert_3> could not obtain system resources such as: storage; handles; disk space, and therefore could not successfully complete the command.
- Response
- Check the WebSphere MQ error logs and check if there are any FFST files for further details. Rerun the command when sufficient system resources are available.
- AMQ7562
- WebSphere MQ program <insert_3> attempted to access MQ configuration data held in (<insert_4>), however access is denied.
- Severity
- 20 : Error
- Explanation
- <insert_3> needs to access MQ configuration data held in (<insert_4>) but does not have permission to access it.
- Response
- Either correct the permissions to allow access to (<insert_4>), or rerun the command with sufficient authority.
- AMQ7563
- Entry modified successfully.
- Severity
- 0 : Information
- Explanation
- <insert_3> has successfully modified the entry.
- Response
- None
- AMQ7601
- Duplicate XA resource manager is not valid.
- Severity
- 40 : Stop Error
- Explanation
- Line <insert_1> of the configuration file <insert_3> contained a duplicate XA resource manager <insert_5>. This is not valid for attribute <insert_4>. Each XA resource manager must be given a unique name.
- Response
- Check the contents of the file and retry the operation.
- AMQ7601 (Windows)
- Duplicate XA resource manager <insert_5> not valid for attribute <insert_4> at <insert_3> in the configuration data.
- Severity
- 40 : Stop Error
- Explanation
- Key <insert_3> in the configuration data contained a duplicate XA resource manager <insert_5>. This is not valid for attribute <insert_4>. Each XA resource manager must be given a unique name.
- Response
- Check the contents of the configuration data and retry the operation.
- AMQ7602 (IBM i)
- The MQ commitment control exit program was called incorrectly.
- Severity
- 40 : Stop Error
- Explanation
- The WebSphere MQ commitment control exit program was called with incorrect parameters.
- Response
- If the program was called by OS/400 as part of a commit or rollback, save the job log, and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7603
- WebSphere MQ has been configured with invalid resource manager <insert_3>.
- Severity
- 20 : Error
- Explanation
- The XA switch file <insert_4> for resource manager <insert_3> indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed so the queue manager will terminate.
- Response
- Remove the offending XAResourceManager stanza from the qm.ini configuration file and restart the queue manager.
- AMQ7603 (Windows)
- WebSphere MQ has been configured with resource manager <insert_3> that is not valid.
- Severity
- 20 : Error
- Explanation
- The XA switch file <insert_4> for resource manager <insert_3> indicates that an attempt has been made to configure another queue manager as an external resource manager. This is not allowed, so the queue manager will terminate.
- Response
- Remove the offending XAResourceManager stanza from the configuration data and restart the queue manager.
- AMQ7604
- The XA resource manager <insert_3> was not available when called for <insert_4>. The queue manager is continuing without this resource manager.
- Severity
- 10 : Warning
- Explanation
- The XA resource manager <insert_3> has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there might be a configuration problem.
- Response
- Try to establish the reason why the resource manager is unavailable. It might be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager might be reaching a resource constraint with this resource manager. For example, the resource manager might not be able to accommodate all of the queue manager processes being connected at one time, you might need to alter one of its tuning parameters.
- AMQ7604 (IBM i)
- The XA resource manager was not available when called.
- Severity
- 10 : Warning
- Explanation
- The XA resource manager <insert_3> has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for <insert_4>. The queue manager is continuing without this resource manager. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there might be a configuration problem.
- Response
- Try to establish the reason why the resource manager is unavailable. It might be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager might be reaching a resource constraint with this resource manager. For example, the resource manager might not be able to accommodate all of the queue manager processes being connected at one time, you might need to alter one of its tuning parameters.
- AMQ7605
- The XA resource manager <insert_3> has returned an unexpected return code <insert_1>, when called for <insert_4>.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ received an unexpected return code when calling XA resource manager <insert_3> at its <insert_4> entry point. This indicates an internal error, either within MQ or the resource manager.
- Response
- Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of <insert_2> to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X<insert_5>. If you think that the error lies within the queue manager, save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved.
- AMQ7605 (IBM i)
- The XA resource manager has returned an unexpected return code.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ received unexpected return code <insert_1> when calling XA resource manager <insert_3> at its <insert_4> entry point. This indicates an internal error, either within MQ or the resource manager.
- Response
- Try to determine the source of the error. A trace of the failure could be used to look at the XA flows between MQ and the resource manager. MQ has allocated an RMId of <insert_2> to this resource manager. This will be useful when isolating the flows associated with the resource manager concerned. If the error occurs on an xa_commit or xa_rollback request, the queue manager will not attempt to redeliver the commit or rollback instruction for this transaction, until after the queue manager has been restarted. The transaction indoubt is identified by the following XID of X<insert_5>. If you think that the error lies within the queue manager, save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard any information describing the problem until after the problem has been resolved.
- AMQ7606
- A transaction has been committed but one or more resource managers have backed out.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ was processing the commit operation for a transaction involving external resource managers. One or more of these resource managers failed to obey the commit request and instead rolled back their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers might now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to commit their updates.
- Response
- The transaction with the mixed outcome is identified by the following XID of X<insert_3>. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have committed their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers.
- AMQ7607
- A transaction has been rolled back but one or more resource managers have committed.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ was rolling back a transaction involving external resource managers. One or more of these resource managers failed to obey the rollback request and instead committed their updates. The outcome of the transaction is now mixed and the resources owned by these resource managers might now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to roll back their updates.
- Response
- The transaction with the mixed outcome is identified by the following XID of X<insert_3>. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it won't be displayed by the dspmqtrn command and all other transaction participants will have rolled back their updates. If the transaction is displayed by the dspmqtrn command then there are some participants still in prepared state. In order to preserve data integrity you will need to perform recovery steps local to the failing resource managers.
- AMQ7608
- XA resource manager returned a heuristic return code.
- Severity
- 20 : Error
- Explanation
- This message is associated with an earlier AMQ7606 message reporting a mixed transaction outcome. It identifies one of the resource managers (<insert_4>) that failed to commit its updates. The transaction associated with this failure is identified by the following XID of X<insert_3>.
- Response
- Use the return code <insert_1> returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the commit decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager.
- AMQ7609
- XA resource manager returned a heuristic return code.
- Severity
- 20 : Error
- Explanation
- This message is associated with an earlier AMQ7607 message reporting a mixed transaction outcome. It identifies one of the resource managers (<insert_4>) that failed to roll back its updates. The transaction associated with this failure is identified by the following XID of X<insert_3>.
- Response
- Use the return code <insert_1> returned by the resource manager to determine the effects of the failure. The return code indicates that the resource manager made a heuristic decision about the outcome of the transaction which disagrees with the rollback decision of the queue manager. In order to preserve data integrity you will need to perform recovery steps local to this resource manager.
- AMQ7612
- Switch call exception
- Severity
- 20 : Error
- Explanation
- Exception number <insert_1> occurred when calling resource manager switch <insert_3>.
- Response
- Check the resource manager switch has not been corrupted.
- AMQ7622
- WebSphere MQ could not load the XA switch load file for resource manager <insert_3>.
- Severity
- 20 : Error
- Explanation
- An error has occurred loading XA switch file <insert_4>. If the error occurred during startup then the queue manager will terminate. At all other times the queue manager will continue without this resource manager meaning that it will no longer be able to participate in global transactions. The queue manager will also retry the load of the switch file at regular intervals so that the resource manager will be able to participate again should the load problem be resolved.
- Response
- Look for a previous message outlining the reason for the load failure. Message AMQ6175 is issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the name of the switch load file is correct and that it is present in a directory from which it can be dynamically loaded by the queue manager. The easiest method of doing this is to define the switch load file as a fully-qualified name. Note that if the queue manager is still running it will need to be restarted in order that any changes made to its configuration data can be picked up.
- AMQ7623
- WebSphere MQ has not been configured with XA resource manager.
- Severity
- 10 : Warning
- Explanation
- The queue manager has noticed that XA resource manager <insert_3> was removed from the qm.ini file of the queue manager. However, it was logged as being involved in <insert_1> transactions that are still in-doubt. The queue manager cannot resolve these transactions. The queue manager is continuing without this resource manager.
- Response
- First check that the qm.ini configuration file of the queue manager concerned hasn't been mistakenly altered resulting in an 'XAResourceManager' stanza being removed, or the 'Name' of any the resource managers being changed. If the qm.ini file was changed by mistake then you will need to reinstate resource manager <insert_3> in the qm.ini file before stopping and then restarting the queue manager in order that the change will be picked up. If you have intentionally removed a resource manager from the qm.ini file, consider the integrity implications of your action since the resource manager concerned might be in an in-doubt state. If you are sure that is not the case then you can use the 'rsvmqtrn' command to deliver an outcome on behalf of the resource manager in order that the queue manager can forget about the transactions concerned. If you cannot be sure that such an action will not cause an integrity problem then you should consider re-instating the resource manager in the qm.ini file so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted.
- AMQ7623 (Windows)
- WebSphere MQ has not been configured with XA resource manager <insert_3> which might be involved in in-doubt transactions. The queue manager is continuing without this resource manager.
- Severity
- 10 : Warning
- Explanation
- The queue manager has recognized that XA resource manager <insert_3> was removed from the registry entry of the queue manager. However, it was logged as being involved in <insert_1> transactions that are still in-doubt. The queue manager cannot resolve these transactions.
- Response
- Check that the configuration data entry of the queue manager
concerned has not been altered by mistake, resulting in an 'XAResourceManager'
stanza being removed, or the 'Name' of any the resource managers being
changed.
If the configuration data entry was changed by mistake, you need to reinstate resource manager <insert_3> in the configuration data before stopping, and then restarting the queue manager to access the change.
If you have intentionally removed a resource manager from the configuration data, consider the integrity implications of your action because the resource manager concerned might be in an in-doubt state.
If you are sure that this is not the case, you can use the 'rsvmqtrn' command to instruct the resource manager to inform the queue manager that it can forget about the transactions concerned.
If using the 'rsvmqtrn' command could result in an integrity problem, you should consider reinstating the resource manager in the configuration data, so that the queue manager can contact the resource manager and automatically resolve the transactions concerned next time the queue manager is restarted.
- AMQ7624
- An exception occurred during an <insert_4> call to XA resource manager <insert_3>.
- Severity
- 20 : Error
- Explanation
- An exception has been detected during a call to an XA resource manager. The queue manager will continue after assuming a return code of XAER_RMERR from the call.
- Response
- An FFST should have been produced which documents the exception. Use this and any further FFSTs to try and determine the reason for the failure. A trace of the problem will be useful to identify the XA flows between the queue manager and the resource manager concerned. MQ has allocated an RMId of <insert_1> to this resource manager. Use this to isolate the flows concerned. First contact the supplier of the resource manager for problem resolution. If however you think that the problem lies within the queue manager then save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard any information describing the problem until after it has been resolved.
- AMQ7625
- The XA resource manager <insert_3> has become available again.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ has managed to regain contact with a resource manager that had become unavailable. Any in-doubt transactions involving this resource manager will be resolved. The resource manager will now be able to participate in new transactions.
- Response
- None.
- AMQ7626
- XA resource manager initialization failure. Refer to the error log for more information.
- Severity
- 20 : Error
- Explanation
- The queue manager has failed to initialize one or more of the XA resource managers defined in the qm.ini configuration file.
- Response
- Correct the error and restart the queue manager.
- AMQ7626 (Windows)
- XA resource manager initialization failure. Refer to the error log for more information.
- Severity
- 20 : Error
- Explanation
- The queue manager has failed to initialize one or more of the XA resource managers defined in the configuration data.
- Response
- Correct the error and restart the queue manager.
- AMQ7627
- The XA resource manager <insert_3> was not available when called for xa_open. The queue manager is continuing without this resource manager.
- Severity
- 10 : Warning
- Explanation
- The XA resource manager <insert_3> has indicated that it is not available, by returning XAER_RMERR on an xa_open request. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the resource manager should be available, then there might be a configuration problem or another possibility is that you are using a 32-bit instance of Db2, this is not supported on this platform, as WebSphere MQ processes are 64-bit and Db2 does not support 64-bit processes with its 32-bit instances.
- Response
- Try to establish the reason why the resource manager is unavailable. It might be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager might be reaching a resource constraint with this resource manager. For example, the resource manager might not be able to accommodate all of the queue manager processes being connected at one time, you might need to alter one of its tuning parameters.
- AMQ7701
- DMPMQLOG command is starting.
- Severity
- 0 : Information
- Explanation
- You have started the DMPMQLOG command and it is processing your request.
- Response
- None.
- AMQ7702
- DMPMQLOG command has finished successfully.
- Severity
- 0 : Information
- Explanation
- The DMPMQLOG command has finished processing your request and no errors were detected.
- Response
- None.
- AMQ7703
- DMPMQLOG command has used option <insert_3> with an invalid value <insert_4>.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying an invalid option value. The <insert_4> value for option <insert_3> is either missing or of an incorrect format.
- Response
- Refer to the command syntax, and then try the command again.
- AMQ7704
- DMPMQLOG command has used an invalid option <insert_3>.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying an invalid option of <insert_3>.
- Response
- Refer to the command syntax and then try the command again.
- AMQ7705
- Usage: dmpmqlog [-b | -s StartLSN | -n ExtentNumber] [-e EndLSN] [-f LogFilePath] [-m QMgrName]
- Severity
- 0 : Information
- Response
- None.
- AMQ7706
- DMPMQLOG command has used an incorrect queue manager name <insert_3> or path <insert_4>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has used <insert_3> as
the queue manager name and, if shown, <insert_4> as
the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is
incorrect; if <insert_4> is not shown then it
is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ system initialization (INI) file are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
- Response
- Check that <insert_3> is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
- AMQ7706 (Windows)
- DMPMQLOG command has used an incorrect queue manager name <insert_3> or path <insert_4>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has used <insert_3> as
the queue manager name and, if shown, <insert_4> as
the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is
incorrect; if <insert_4> is not shown then it
is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ configuration data are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
- Response
- Check that <insert_3> is an existing queue manager name. Check your MQ configuration data to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
- AMQ7706 (IBM i)
- DMPMQLOG command has used an incorrect queue manager name or path.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has used <insert_3> as
the queue manager name and, if shown, <insert_4> as
the directory path for <insert_3>. Either <insert_3> and/or <insert_4> is
incorrect; if <insert_4> is not shown then it
is <insert_3> which is incorrect.
Possible reasons for the error include:
that <insert_3> is not an existing queue manager name;
the entries for <insert_3> in the MQ system initialization (INI) file are incorrect;
<insert_4> is not a correct path for <insert_3>.
If you started the command specifying option -m (queue manager name option) with a value then this value will have been used as the queue manager name, otherwise the default queue manager name will have been used.
- Response
- Check that <insert_3> is an existing queue manager name. Check your MQ system's initialization (INI) file to ensure that <insert_3> and its associated entries are correct. If <insert_4> is shown, check that it is a correct MQ system directory path for <insert_3>.
- AMQ7707
- DMPMQLOG command has failed: CompCode = 0x<insert_1>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has detected an error and the MQ recording routine has been called. Possible reasons for this include a damaged log file, a problem during initialization for the queue manager or an internal MQ failure.
- Response
- Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it does not exist, try the command again specifying an existing queue manager. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Note the completion code (CompCode) and then use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7708
- DMPMQLOG command has used an invalid default queue manager name.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command without specifying option -m (queue manager name option) and so your MQ default queue manager name has been used. However, this default name either could not be found or is invalid.
- Response
- Check that the default queue manager name exists and is valid, and then try the command again.
- AMQ7709
- DMPMQLOG command has used an invalid combination of options.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying an invalid combination of the options -b (base LSN option), -s (start LSN option) and -n (extent number option). Only 1 or none of these options can be specified.
- Response
- Refer to the command syntax and then try the command again.
- AMQ7710
- DMPMQLOG command has used option -n which is invalid for circular logging.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying option -n (extent number option) but this is not valid when your MQ log is defined as circular.
- Response
- Use a different option and then try the command again.
- AMQ7711
- DMPMQLOG command has used option -m with a value that is too long.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying option -m (queue manager name option) with a value that is more than <insert_1> characters.
- Response
- Specify a shorter queue manager name and then try the command again.
- AMQ7712
- DMPMQLOG command has used option -f with a value which is too long.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying option -f (log file path option) with a value which is more than <insert_1> characters.
- Response
- Specify a shorter log file path name and then try the command again.
- AMQ7713
- DMPMQLOG command was unable to allocate sufficient storage.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has been unable to allocate some storage.
- Response
- Free some storage and then try the command again.
- AMQ7714
- DMPMQLOG command has reached the end of the log.
- Severity
- 0 : Information
- Explanation
- The DMPMQLOG command has processed any log data and has now reached the end of the log.
- Response
- None.
- AMQ7715
- DMPMQLOG command cannot open file <insert_3>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command was unable to open file <insert_3> for reading.
- Response
- Check that the file exists, can be opened for reading, and that you have authority to access it, and then try the command again.
- AMQ7716
- DMPMQLOG command has finished unsuccessfully.
- Severity
- 0 : Information
- Explanation
- The DMPMQLOG command has finished with your request but an error has been detected. The previous message issued by the command can be used to identify the error.
- Response
- Refer to the previous message issued by the command.
- AMQ7717
- DMPMQLOG command has failed to initialize: CompCode = 0x<insert_1>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has failed during its initialization and the MQ recording routine has been called. Possible reasons for this include that your queue manager is already running. The completion code can be used to identify the error.
- Response
- Check that the queue manager being used by DMPMQLOG, as specified by you using the -m command option or defaulted, exists and is not currently running. If it is running, stop the queue manager and then try the command again. Otherwise, use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7718
- DMPMQLOG command is using a default of <insert_3> for the queue manager name.
- Severity
- 0 : Information
- Explanation
- You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of <insert_3> is being used. This value is obtained from your default queue manager name.
- Response
- None.
- AMQ7718 (IBM i)
- DMPMQLOG command is using the default queue manager name.
- Severity
- 0 : Information
- Explanation
- You have started the DMPMQLOG command without specifying option -m (queue manager name option) and so a default value of <insert_3> is being used. This value is obtained from your MQ default queue manager name.
- Response
- None.
- AMQ7719
- DMPMQLOG command is using a default of <insert_3> for the starting dump location.
- Severity
- 0 : Information
- Explanation
- You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of <insert_3> is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and is used as the location from which to start dumping.
- Response
- None.
- AMQ7719 (IBM i)
- DMPMQLOG command is using the default starting dump location.
- Severity
- 0 : Information
- Explanation
- You have started the DMPMQLOG command without specifying option -b (base LSN option), option -s (start LSN option) or option -n (extent number option), and so a default value of <insert_3> is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and is used as the location from which to start dumping.
- Response
- None.
- AMQ7720
- DMPMQLOG command is using extent <insert_1> but the current extent is <insert_2>.
- Severity
- 20 : Error
- Explanation
- You have started the DMPMQLOG command specifying option -n (extent number option) with a value of <insert_1> but this value is greater than <insert_2>, which represents the extent currently being used.
- Response
- When using option -n, specify its value as being less than or equal to the extent number currently being used.
- AMQ7721
- DMPMQLOG command has not found any log records in extent number <insert_1>.
- Severity
- 0 : Information
- Explanation
- During its normal processing, the DMPMQLOG command did not find any log records in this extent.
- Response
- None.
- AMQ7722
- DMPMQLOG command cannot find the object catalog for queue manager <insert_3>.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command is using the queue manager named <insert_3> but cannot find the manager's object catalog file. This file should have been created at the time the queue manager was created.
- Response
- Refer to the "System Management Guide" for a description of the location and name of the object catalog file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager.
- AMQ7722 (IBM i)
- DMPMQLOG command cannot find the object catalog for the queue manager.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command is using the queue manager named <insert_3> but cannot find the manager's object catalog file. This file should have been created at the time the queue manager was created.
- Response
- Refer to the "System Management Guide" for a description of the location and name of the object catalog file. Check that the file exists and is available for use by this command. If it does not exist then you will need to re-create the queue manager.
- AMQ7723
- DMPMQLOG command cannot find the requested Log Sequence Number (LSN).
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has been started with an LSN but it cannot be found in the log.
- Response
- Check for an existing LSN and then try the command again.
- AMQ7724
- DMPMQLOG command cannot use the requested extent number.
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has been started with an extent number but it is beyond the end of the log.
- Response
- Check for an existing extent number and then try the command again.
- AMQ7725
- DMPMQLOG command cannot find an old Log Sequence Number (LSN).
- Severity
- 20 : Error
- Explanation
- The DMPMQLOG command has been started specifying an LSN which is older than the log's base LSN. However, the specified LSN could not be found.
- Response
- Check for an existing LSN and then try the command again.
- AMQ7726
- DMPMQLOG command has used option -s with an incorrect value for circular logging.
- Severity
- 20 : Error
- Explanation
- You started the DMPMQLOG command specifying option -s (start LSN option) with a value which is less than the base LSN of a log which is defined as circular. LSN values less than the base LSN can only be specified when using a linear log.
- Response
- When using option -s with a circular log, specify an option value which is equal or greater to the log's base LSN, and then try the command again.
- AMQ7751 (IBM i)
- MIGRATEMQM program is starting.
- Severity
- 0 : Information
- Explanation
- You have started the MIGRATEMQM program.
- Response
- None.
- AMQ7752 (IBM i)
- MIGRATEMQM has completed successfully.
- Severity
- 0 : Information
- Explanation
- The MIGRATEMQM program has completed migration of your queue manager and no errors were detected.
- Response
- None.
- AMQ7753 (IBM i)
- MIGRATEMQM has failed due to errors.
- Severity
- 20 : Error
- Explanation
- See the previously listed messages in the job log. Correct the errors and then restart the MIGRATEMQM program.
- Response
- None.
- AMQ7754 (IBM i)
- MIGRATEMQM has detected an error and is unable to continue.
- Severity
- 20 : Error
- Explanation
- See the previously listed messages in this job log, or in associated job logs. Correct the errors and then restart the MIGRATEMQM program.
- Response
- None.
- AMQ7755 (IBM i)
- Unable to locate a required journal receiver.
- Severity
- 20 : Error
- Explanation
- The MIGRATEMQM program attempted to locate the journal receivers to use for migration, but the operation required access to a journal or journal receiver that is not currently present on the system.
- Response
- Restore the required journal or journal receiver from backup. Then restart the MIGRATEMQM program.
- AMQ7756 (IBM i)
- Unable to locate a required journal entry.
- Severity
- 20 : Error
- Explanation
- The MIGRATEMQM program was unable to retrieve a journal entry required for migration. The operation might have failed because a required journal receiver is not currently present on the system.
- Response
- Restore the required journal receiver from backup. Then restart the MIGRATEMQM program.
- AMQ7757 (IBM i)
- Queue manager <insert_3> already exists.
- Severity
- 20 : Error
- Explanation
- The MIGRATEMQM program is unable to create a queue manager with the same name as used in the previous release because a queue manager of this name has already been created.
- Response
- Delete the queue manager. Then restart the MIGRATEMQM program.
- AMQ7758 (IBM i)
- Queue manager starting.
- Severity
- 0 : Information
- Explanation
- The queue manager "<insert_3>" is starting.
- Response
- None.
- AMQ7759 (IBM i)
- Recreating WebSphere MQ objects.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ objects are being re-created from their media images contained in the log.
- Response
- None.
- AMQ7760 (IBM i)
- Recreating WebSphere MQ channels.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ channels are being re-created from the previous channel definition file.
- Response
- None.
- AMQ7761 (IBM i)
- Unexpected return code from command <insert_3>.
- Severity
- 20 : Error
- Explanation
- An unexpected return code, <insert_1>, was returned by command <insert_3>.
- Response
- See the previously listed messages in this job log, or in associated job logs.
- AMQ7762 (IBM i)
- Unexpected error from channel migration.
- Severity
- 20 : Error
- Explanation
- The migration of channel definitions or channel synchronization data encountered an unexpected error.
- Response
- See the previously listed messages in this job log, or in associated job logs.
- AMQ7770
- Sent file <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- The file was successfully sent.
- Response
- None.
- AMQ7771
- Received file.
- Severity
- 40 : Stop Error
- Explanation
- The file was successfully received.
- Response
- None.
- AMQ7772
- Complete file list
- Severity
- 40 : Stop Error
- Explanation
- Displays a list of complete files.
- Response
- None.
- AMQ7773
- Incomplete file list
- Severity
- 40 : Stop Error
- Explanation
- Displays a list of incomplete files.
- Response
- None.
- AMQ7774
- Other message list
- Severity
- 40 : Stop Error
- Explanation
- Displays a list of other messages.
- Response
- None.
- AMQ7775
- Nothing to list.
- Severity
- 40 : Stop Error
- Explanation
- Nothing to list.
- Response
- None.
- AMQ7776
- Deleted.
- Severity
- 40 : Stop Error
- Explanation
- File deleted.
- Response
- None.
- AMQ7777
- Nothing to delete.
- Severity
- 40 : Stop Error
- Explanation
- Nothing to delete.
- Response
- None.
- AMQ7778
- Syntax error. The correct syntax is:
- Severity
- 40 : Stop Error
- Explanation
- Invalid arguments supplied.
- Response
- One or more options were incorrectly specified when issuing the send or receive command. Check the options used and reissue the command.
- AMQ7779
- Cannot connect to default queue manager.
- Severity
- 40 : Stop Error
- Explanation
- Queue manager not available.
- Response
- Check that the queue manager exists and that the listener is running.
- AMQ7780
- Cannot connect to queue manager <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- Queue manager not available.
- Response
- Check that the queue manager exists and that the listener is running.
- AMQ7781
- Application memory unavailable.
- Severity
- 40 : Stop Error
- Explanation
- There is insufficient memory to perform the requested action.
- Response
-
1) Check the message size is not excessive
2) Close other applications and try the command again
- AMQ7783
- Queue name required.
- Severity
- 40 : Stop Error
- Explanation
- A queue name was not specified when issuing a send or receive command.
- Response
- Reissue the command with the QueueName option.
- AMQ7784
- Cannot open queue <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- Cannot open queue <insert_3>
- Response
- Check that the queue exists.
- AMQ7785
- Cannot open file <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- Cannot open file <insert_3>
- Response
- Check that the file exists, that it is in the correct location and has the appropriate file permissions.
- AMQ7786
- Cannot put to queue <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- Cannot put to queue <insert_3>
- Response
-
1) Check the Queue Manager has sufficient log space for sending large messages
2) Check the queue does not have put inhibited
3) Check the queue is not full
4) Check the message size of the queue is greater than the message size
5) Check the user has sufficient authority to put messages on the queue
- AMQ7787
- No file name specified.
- Severity
- 40 : Stop Error
- Explanation
- No file name specified.
- Response
- A file name was not specified when issuing a send command. Reissue the command with the FileName option.
- AMQ7788
- Message length is too small to send data.
- Severity
- 40 : Stop Error
- Explanation
- Message length is too small to send data.
- Response
- Increase the message size and resend with a send command, using the -l MessageSize option to specify a larger message size.
- AMQ7789
- Sending file has changed.
- Severity
- 40 : Stop Error
- Explanation
- The file being sent has been changed before the complete file has been sent.
- Response
- Check the file for integrity and reissue the send command.
- AMQ7790
- Cannot get from queue <insert_3>
- Severity
- 40 : Stop Error
- Explanation
- The list, get, delete or extract request has failed.
- Response
-
1) Check the queue does have get inhibited
2) Check the user has sufficient WebSphere MQ authority to get messages from the queue
- AMQ7791
- Cannot write to file.
- Severity
- 40 : Stop Error
- Explanation
- The get or extract request has failed.
- Response
-
1) Check that the file is not write-protected. In Windows Explorer, right-click the file name and select Properties. Check the user has sufficient authority to write to the destination file system.
2) Check the destination file system exists
3) Check the destination file system is not full
- AMQ7792
- CorrelId is invalid.
- Severity
- 40 : Stop Error
- Explanation
- CorrelId is invalid.
- Response
-
1) Check that a valid correlation ID has been specified when receiving a file with the -c option.
2) It must be 48 characters in length.
3) Use the -v option of the receive command to display the correlation ID.
- AMQ7793
- MsgId is invalid.
- Severity
- 40 : Stop Error
- Explanation
- MsgId is invalid.
- Response
-
1) Check that a valid message ID has been specified when receiving an 'other' message with the -u option.
2) It must be 48 characters in length.
- AMQ7794
- No messages to receive.
- Severity
- 40 : Stop Error
- Explanation
- There are no FTA files on the specified queue.
- Response
- Check with the sender that the file was actually sent.
- AMQ7795
- Cannot delete the file because it's not unique.
- Severity
- 40 : Stop Error
- Explanation
- Cannot delete the file because it's not unique.
- Response
- None.
- AMQ7796
- Cannot replace an existing file.
- Severity
- 40 : Stop Error
- Explanation
- Cannot replace an existing file.
- Response
- Reissue the command with the -y option.
- AMQ7797
- Unable to load the WebSphere MQ library.
- Severity
- 40 : Stop Error
- Explanation
- Unable to load the WebSphere MQ library.
- Response
- None.
- AMQ7798
- Unable to locate <insert_3>.
- Severity
- 40 : Stop Error
- Explanation
- This application requires <insert_3>.
- Response
- Check that <insert_3> is available and installed correctly.
- AMQ7799
- Unable to start <insert_3>.
- Severity
- 40 : Stop Error
- Explanation
- This application cannot start <insert_3>.
- Response
- Check that <insert_3> is available and installed correctly.
- AMQ7800
- CorrelId <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7801
- Dir <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7802
- UserData <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7803
- FileName <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7804
- Length <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7805
- MsgId <insert_3>
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7806
- Could not start WebSphere MQ web administration server: <insert_1>.
- Severity
- 0 : Information
- Explanation
- An unsuccessful attempt was made to start the web administration server on port <insert_1>.
- Response
- Check the product is installed correctly; the required registry keys and values are correct and the web server port is not already in use. If the problem persists save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7807
- WebSphere MQ web administration server running.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ web administration server running. Listening on port <insert_4>, root directory is <insert_5>.
- Response
- No action is required.
- AMQ7808
- Internal run-time error in WebSphere MQ web administration: <insert_4>.
- Severity
- 0 : Information
- Explanation
- WebSphere MQ web administration had the following internal run-time error: <insert_4>.
- Response
- Check that: the product is installed correctly and that the required registry keys and values are correct. If the problem persists save any generated output files and use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.
- AMQ7809
- WebSphere MQ Publish/Subscribe web administration user limit reached.
- Severity
- 10 : Warning
- Explanation
- The maximum number of concurrent web administration users has been reached (<insert_4>).
- Response
- Use the 'Web Administration Server' properties page in the Microsoft Management Console to increase the value of the web administration 'MaxClients' parameter.
- AMQ7810 (Windows)
- Failed to create class, reason code: <insert_1>.
- Severity
- 20 : Error
- Explanation
- While trying to create class <insert_3> on <insert_4> error code <insert_1> was encountered. The associated error message generated by the operating system is: <insert_5>
- Response
- Check the system documentation to determine the course of action required to rectify the problem.
- AMQ7880 (Windows)
- Error code <insert_1> starting <insert_4>/<insert_3> WebSphere MQ service.
- Severity
- 0 : Information
- Explanation
- The service was unable to start <insert_4>/<insert_3>. The error message reported was as follows: <insert_5>
- Response
- Use WebSphere MQ Explorer to investigate why the service could not begin. If recovery for this service is active, MQ attempts to recover.
- AMQ7881 (Windows)
- Unable to stop <insert_4>/<insert_3> WebSphere MQ service, return code <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The WebSphere MQ service was unable to stop <insert_4>/<insert_3>. The error message reported was as follows: <insert_5>
- Response
- Use WebSphere MQ Explorer to investigate why the service could not be stopped.
- AMQ7882 (Windows)
- Attempting to recover <insert_4>/<insert_3> WebSphere MQ service.
- Severity
- 0 : Information
- Explanation
- The WebSphere MQ service has detected that <insert_4>/<insert_3> has failed, and is attempting to restart it.
- Response
- No Action Required.
- AMQ7883 (Windows)
- <insert_4>/<insert_3> WebSphere MQ service started from recovery.
- Severity
- 0 : Information
- Explanation
- The WebSphere MQ service has successfully recovered <insert_4>/<insert_3>.
- Response
- No Action Required.
- AMQ7884 (Windows)
- Unable to recover <insert_4>/<insert_3> WebSphere MQ service.
- Severity
- 10 : Warning
- Explanation
- The WebSphere MQ service has attempted to recover <insert_4>/<insert_3>, but all attempts have failed. There are no more attempts to recover this service.
- Response
- Use WebSphere MQ Explorer to investigate why the service failed and could not be restarted.
- AMQ7885 (Windows)
- Unable to delete queue manager <insert_4>, error <insert_1>.
- Severity
- 10 : Warning
- Explanation
- An attempt to delete queue manager <insert_4> failed. WebSphere MQ returned error code <insert_1>: <insert_5>
- Response
- Ensure that the queue manager name has been specified correctly, and try again.
- AMQ7886 (Windows)
- Unable to create queue manager <insert_4>.
- Severity
- 10 : Warning
- Explanation
- Queue manager <insert_4> could not be created. WebSphere MQ returned error <insert_1>: <insert_5>
- Response
- Check the error and application event logs to investigate the reason for the returned error and suggested responses to take to rectify the fault. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then use either the https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7890 (Windows)
- Unable to open mapped file containing WebSphere MQ performance data.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to open a mapped file used to collect queue performance data. Your system might be running short on virtual storage.
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7891 (Windows)
- Unable to create a mutex to access WebSphere MQ performance data.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to create a mutex required to synchronize collection of queue performance data
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7892 (Windows)
- Unable to map to shared memory file containing WebSphere MQ performance data.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to map the shared memory file required for collection of queue performance data.
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7893 (Windows)
- Unable to open "Performance" key for WebSphere MQ services. Status code: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7894 (Windows)
- Unable to read the "Performance\First Counter" value for WebSphere MQ services. Status code: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Counter" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7895 (Windows)
- Unable to read the "Performance\First Help" value for WebSphere MQ services. Status code: <insert_1>.
- Severity
- 20 : Error
- Explanation
- The WebSphere MQ extensible counter dll was unable to obtain performance counter values from the "Performance\First Help" key for WebSphere MQ services. Status code is the return value from the Windows registry call RegOpenKeyEx.
- Response
- No action required. Performance statistics for MQ queues will not be displayed.
- AMQ7901
- The data-conversion exit <insert_3> has not loaded.
- Severity
- 30 : Severe error
- Explanation
- The data-conversion exit program, <insert_3>, failed to load. The internal function gave exception <insert_4>.
- Response
- Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7903
- The data-conversion exit <insert_3> cannot be found.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion has been requested for a WebSphere MQ message with a user-defined format, but the necessary data-conversion exit program, <insert_3>, cannot be found. The internal function gave exception <insert_4>.
- Response
- Check that the necessary data-conversion exit <insert_3> exists.
- AMQ7904
- The data-conversion exit <insert_3> cannot be found, or loaded.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion was requested for a WebSphere MQ message with a user-defined format, but the necessary data conversion exit program, <insert_3>, was not found, or loaded. The <insert_4> function call gave a return code of <insert_1>.
- Response
- Check that the necessary data conversion exit routine exists in one of the standard directories for dynamically loaded modules. If necessary, inspect the generated output to examine the message descriptor (MQMD structure) of the MQ message for the conversion which was requested. This might help you to determine where the message originated.
- AMQ7905
- Unexpected exception <insert_4> in data-conversion exit.
- Severity
- 30 : Severe error
- Explanation
- The data-conversion exit program, <insert_3>, ended with an unexpected exception <insert_4>. The message has not been converted.
- Response
- Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7907
- Unexpected exception in data-conversion exit.
- Severity
- 30 : Severe error
- Explanation
- The data-conversion exit routine, <insert_3>, ended with an unexpected exception. The message has not been converted.
- Response
- Correct the error in the data-conversion exit routine.
- AMQ7908 (Windows)
- Display active directory CRL server details.
- Severity
- 0 : Information
- Explanation
- Display active directory CRL server details.
- Response
- None.
- AMQ7909 (Windows)
- There are no active directory CRL server details to display.
- Severity
- 0 : Information
- Explanation
- No active directory CRL server definitions could be found.
- Response
- None.
- AMQ7910 (Windows)
- Usage: setmqscp [-a [-m QmgrName | * ] | -r [-m QmgrName | * ] | -d]
- Severity
- 0 : Information
- AMQ7911 (Windows)
- The default Active Directory could not be located on your domain.
- Severity
- 20 : Error
- Explanation
- No domain controllers with Active Directories could be found on the domain that your computer is a member of.
- Response
- Active Directory support for MQ MQI client connections cannot be used without a default Active Directory available on your domain.
- AMQ7912 (Windows)
- The Active Directory support library failed to initialize.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ support libraries for Active Directory client connections could not be initialized.
- Response
- Check that the Active Directory client pre-requisite software has been installed on your machine before attempting to use this feature.
- AMQ7913 (Windows)
- The WebSphere MQ Active Directory container could not be created.
- Severity
- 20 : Error
- Explanation
- WebSphere MQ has failed to create an IBM-MQClientConnections container as a child of your domain's system container in the Active Directory.
- Response
- Ensure that you have permission to create sub-containers of the system container, and modify the otherWellKnownObjects property of the system container.
- AMQ7914 (Windows)
- Migration of the client connection table for Queue Manager <insert_3> failed with reason code <insert_1><insert_4>.
- Severity
- 10 : Warning
- Explanation
- The client connection table for this Queue Manager could not be migrated at this time.
- Response
- Ensure that the client connection table exists and is not corrupted, and that you have authority to create new objects in the Active Directory on your domain.
- AMQ7915 (Windows)
- Created service connection point for connection <insert_3>.
- Severity
- 0 : Information
- Explanation
- The service connection point was successfully created for this client connection.
- Response
- None.
- AMQ7916 (Windows)
- The Active Directory channel definition table could not be opened.
- Severity
- 20 : Error
- Explanation
- The IBM-MQClientConnections Active Directory container could not be located in the Global Catalog.
- Response
- Ensure that setmqscp has been used to create the container object and that you have permission to read the container and its child objects.
- AMQ7917 (Windows)
- Display active directory channel details.
- Severity
- 0 : Information
- Explanation
- Display active directory channel details.
- Response
- None.
- AMQ7918 (Windows)
- The WebSphere MQ Active Directory container could not be deleted.
- Severity
- 20 : Error
- Explanation
- There was a problem when attempting to delete the MQ Active Directory container. The container must be empty before it can be deleted from the directory.
- Response
- None.
- AMQ7919 (Windows)
- There are no active directory client channel details to display.
- Severity
- 0 : Information
- Explanation
- No active directory client channel definitions could be found.
- Response
- None.
- AMQ7920 (Windows)
- Usage: setmqcrl [-m QmgrName] [-a] [-d] [-r]
- Severity
- 0 : Information
- AMQ7921
- An incorrect eye-catcher field in an MQDXP structure has been detected.
- Severity
- 30 : Severe error
- Explanation
- The MQDXP structure passed to the Internal Formats Conversion routine contains an incorrect eye-catcher field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the IBM WebSphere MQ support web page at https://www.ibm.com/support/home/product/P439881V74305Y86/IBM_MQ, or the IBM support assistant at https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.
- AMQ7922
- A PCF message is incomplete.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because the message is only <insert_1> bytes long and does not contain a PCF header. The message has either been truncated, or it contains data that is not valid.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7923
- A message had an unrecognized integer encoding - <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message because the integer encoding value of the message, <insert_1>, was not recognized.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7924
- Bad length in the PCF header (length = <insert_1>).
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because the PCF header structure contains an incorrect length field. Either the message has been truncated, or it contains data that is not valid.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7925
- Message version <insert_1> is not supported.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message because the Version field of the message contains an incorrect value.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7926
- A PCF message has an incorrect parameter count value <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because the parameter count field of the PCF header is incorrect.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7927
- Bad type in PCF structure number <insert_1> (type = <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect type field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7928
- Bad length in PCF structure number <insert_1> (length = <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect length field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7929
- A PCF structure is incomplete.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number <insert_1>, of Type value <insert_2>, within the message is incomplete. The message has either been truncated, or it contains data that is not valid.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7930
- Bad CCSID in PCF structure number <insert_1> (CCSID = <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contains an incorrect CCSID.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7931
- Bad length in PCF structure number <insert_1> (length = <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because one of the structures of the message contains an incorrect length field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7932
- Bad count in PCF structure number <insert_1> (count = <insert_2>).
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because a StringList structure of the message contains an incorrect count field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message, and to see how data that is not valid became included in the message.
- AMQ7933
- Bad string length in PCF structure.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number <insert_1> of the message contains an incorrect string length value <insert_2>.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message, and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7934
- Wrong combination of MQCCSI_DEFAULT with MQCCSI_EMBEDDED or MQEPH_CCSID_EMBEDDED.
- Severity
- 30 : Severe error
- Explanation
- Message data conversion could not convert a message in Programmable Command Format (PCF) because structure <insert_1> of the message contained a CodedCharSetId field of MQCCSI_DEFAULT while the message itself had a CodedCharSetId of MQCCSI_EMBEDDED, or the Flags field of the MQEPH structure containing the PCF specified flag MQEPH_CCSID_EMBEDDED. These are incorrect combinations.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor, the headers of the message and the incorrect structure to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7935
- Bad CCSID in message header (CCSID = <insert_1>).
- Severity
- 30 : Severe error
- Explanation
- Message data conversion could not convert a message because the Message Descriptor of the message contained an incorrect CodedCharSetId field.
- Response
- Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Do not discard these files until the problem has been resolved. Use the file containing the Message Descriptor of the message to determine the source of the message and to see how data that is not valid became included in the message.
- AMQ7936
- The file <insert_3> already exists.
- Severity
- 30 : Severe error
- Explanation
- The output file already exists, but REPLACE has not been specified.
- Response
- Specify REPLACE to over-write the existing file, or select a different output file name.
- AMQ7937
- Structure length <insert_1> in MQFMT_IMS_VAR_STRING format message is not valid.
- Severity
- 30 : Severe error
- Explanation
- This error is detected when attempting data conversion. The valid range for the length is 4 (with no string data) to 32767. The message is returned unconverted with a reason code of MQRC_CONVERTED_STRING_TOO_BIG.
- Response
- Check the content of the message before data conversion and correct the message format. When converting data using two or more bytes per character, remember that the number of bytes in each character can change during data conversion. This causes the message lengths to change.
- AMQ7943
- Usage: crtmqcvx SourceFile TargetFile
- Severity
- 0 : Information
- Explanation
- None.
- Response
- None.
- AMQ7953
- One structure has been parsed.
- Severity
- 0 : Information
- Explanation
- The crtmqcvx command has parsed one structure.
- Response
- None.
- AMQ7954
- <insert_1> structures have been parsed.
- Severity
- 0 : Information
- Explanation
- The crtmqcvx command has parsed <insert_1> structures.
- Response
- None.
- AMQ7955
- Unexpected field: <insert_1>.
- Severity
- 0 : Information
- Explanation
- The field within the structure is of a type that is not recognized.
- Response
- Correct the field and retry the command.
- AMQ7956
- Bad array dimension.
- Severity
- 0 : Information
- Explanation
- An array field of the structure has an incorrect dimension value.
- Response
- Correct the field and retry the command.
- AMQ7957
- Warning at line <insert_1>.
- Severity
- 20 : Error
- Explanation
- The structure contains another field after a variable length field. A variable length field must be the last field of the structure.
- Response
- Correct the structure and retry the command.
- AMQ7958
- Error at line <insert_1> in field <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Field name <insert_3> is a field of type 'float'. Fields of type float are not supported by this command.
- Response
- Either correct the structure to eliminate fields of type float, or write your own routine to support conversion of these fields.
- AMQ7959
- Error at line <insert_1> in field <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Field name <insert_3> is a field of type 'double'. Fields of type double are not supported by this command.
- Response
- Either correct the structure to eliminate fields of type double, or write your own routine to support conversion of these fields.
- AMQ7960
- Error at line <insert_1> in field <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Field name <insert_3> is a 'pointer' field. Fields of type pointer are not supported by this command.
- Response
- Either correct the structure to eliminate fields of type pointer, or write your own routine to support conversion of these fields.
- AMQ7961
- Error at line <insert_1> in field <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- Field name <insert_3> is a 'bit' field. Bit fields are not supported by this command.
- Response
- Either correct the structure to eliminate bit fields, or write your own routine to support conversion of these fields.
- AMQ7962
- No input file specified.
- Severity
- 30 : Severe error
- Explanation
- This command requires that an input file is specified.
- Response
- Specify the name of the input file and retry the command.
- AMQ7963
- No output file specified.
- Severity
- 30 : Severe error
- Explanation
- This command requires that an output file name is specified.
- Response
- Specify the name of the output file and retry the command.
- AMQ7964
- Unexpected option <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- The option specified is not valid for this command.
- Response
- Retry the command with a valid option.
- AMQ7965
- Incorrect number of arguments.
- Severity
- 30 : Severe error
- Explanation
- The command was passed an incorrect number of arguments.
- Response
- Retry the command, passing it the correct number of arguments.
- AMQ7968
- Cannot open file <insert_3>.
- Severity
- 30 : Severe error
- Explanation
- You cannot open the file <insert_3>.
- Response
- Check that you have the correct authorization to the file and retry the command.
- AMQ7969
- Syntax error.
- Severity
- 30 : Severe error
- Explanation
- This line of the input file contains a language syntax error.
- Response
- Correct the syntax error and retry the command.
- AMQ7970
- Syntax error on line <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- This message identifies where, in the input file, a previously reported error was detected.
- Response
- Correct the error and retry the command.
- AMQ7985 (Windows)
- The WebSphere MQ Active Directory container already exists.
- Severity
- 0 : Information
- Explanation
- The IBM-MQClientConnections Active Directory container already exists and does not need to be re-created.
- Response
- None.
- AMQ7986 (Windows)
- The WebSphere MQ Active Directory container was successfully created.
- Severity
- 0 : Information
- Explanation
- The IBM-MQClientConnections Active Directory container was successfully created.
- Response
- None.
- AMQ7987 (Windows)
- Removed service connection point for connection <insert_3>.
- Severity
- 0 : Information
- Explanation
- The service connection point was successfully removed for this client connection.
- Response
- None.
- AMQ7988 (Windows)
- Failure removing service connection point for connection <insert_3>.
- Severity
- 10 : Warning
- Explanation
- The service connection point could not be removed for this client connection.
- Response
- None.
- AMQ7989 (Windows)
- The WebSphere MQ Active Directory container was removed successfully.
- Severity
- 0 : Information
- Explanation
- The IBM-MQClientConnections Active Directory container was removed successfully.
- Response
- None.
- AMQ7990 (Windows)
- The WebSphere MQ Active Directory container does not exist.
- Severity
- 0 : Information
- Explanation
- The IBM-MQClientConnections Active Directory container does not exist.
- Response
- None.
- AMQ7A01 (IBM i)
- Convert MQ Data Type
- AMQ7A02 (IBM i)
- Display MQ Version
- AMQ7A03 (IBM i)
- Create MQ Listener
- AMQ7A04 (IBM i)
- Listener name
- AMQ7A05 (IBM i)
- Listener control
- AMQ7A06 (IBM i)
- Listener backlog
- AMQ7A07 (IBM i)
- Change MQ Listener
- AMQ7A08 (IBM i)
- Copy MQ Listener
- AMQ7A09 (IBM i)
- From Listener
- AMQ7A0A (IBM i)
- To Listener
- AMQ7A0B (IBM i)
- Display MQ Listener
- AMQ7A0C (IBM i)
- Delete MQ Listener
- AMQ7A0D (IBM i)
- LSRNAME not allowed with PORT
- Severity
- 40 : Stop Error
- Explanation
- A listener object cannot be specified with a port.
- Response
- Specify either a listener object or a port number.
- AMQ7A0E (IBM i)
- LSRNAME not allowed with IPADDR
- Severity
- 40 : Stop Error
- Explanation
- A listener object cannot be specified with an IP address.
- Response
- Specify either a listener object or an IP address.
- AMQ7A0F (IBM i)
- Work with MQ Listener object
- AMQ7A10 (IBM i)
- Create MQ Service
- AMQ7A11 (IBM i)
- Change MQ Service
- AMQ7A12 (IBM i)
- Copy MQ Service
- AMQ7A13 (IBM i)
- Service name
- AMQ7A14 (IBM i)
- Start program
- AMQ7A15 (IBM i)
- Start program arguments
- AMQ7A16 (IBM i)
- End program
- AMQ7A17 (IBM i)
- End program arguments
- AMQ7A18 (IBM i)
- Standard output
- AMQ7A19 (IBM i)
- Standard error
- AMQ7A1A (IBM i)
- Service type
- AMQ7A1B (IBM i)
- Service control
- AMQ7A1C (IBM i)
- From Service
- AMQ7A1D (IBM i)
- To Service
- AMQ7A1E (IBM i)
- Display MQ Service
- AMQ7A1F (IBM i)
- Permit Standby Queue Manager
- AMQ7A20 (IBM i)
- Delete MQ Service
- AMQ7A21 (IBM i)
- Work with MQ Service object
- AMQ7A23 (IBM i)
- Start MQ Service
- AMQ7A24 (IBM i)
- End MQ Service
- AMQ7A25 (IBM i)
- Channel initiator control
- AMQ7A26 (IBM i)
- Command server control
- AMQ7A27 (IBM i)
- Display Queue Manager Status
- AMQ7A28 (IBM i)
- Display Listener Status
- AMQ7A29 (IBM i)
- Display Service Status
- AMQ7A2A (IBM i)
- LSRNAME not allowed with OPTION
- Severity
- 40 : Stop Error
- Explanation
- A listener object cannot be specified with an end option.
- Response
- Specify either a listener object or an end option.
- AMQ7A2B (IBM i)
- Service startup
- AMQ7A2C (IBM i)
- Work with Connection Handles
- AMQ7A2D (IBM i)
- Connection Identifier
- AMQ7A2E (IBM i)
- End Queue Manager Connection
- AMQ7A2F (IBM i)
- Work with MQ Connections
- AMQ7A30 (IBM i)
- Header Compression
- AMQ7A31 (IBM i)
- Message Compression
- AMQ7A32 (IBM i)
- Message compression *ANY not valid for channel type.
- Severity
- 30 : Severe error
- Explanation
- The message compression value *ANY is only valid for *RCVR, *RQSTR and *SVRCN channel types.
- Response
- Specify a valid message compression list.
- AMQ7A33 (IBM i)
- Channel Monitoring
- AMQ7A34 (IBM i)
- Channel Statistics
- AMQ7A35 (IBM i)
- Cluster Workload Rank
- AMQ7A36 (IBM i)
- Cluster Workload Priority
- AMQ7A37 (IBM i)
- Cluster Channel Weight
- AMQ7A38 (IBM i)
- Cluster workload channels
- AMQ7A39 (IBM i)
- Cluster workload queue use
- AMQ7A3A (IBM i)
- Queue Monitoring
- AMQ7A3B (IBM i)
- Queue Manager Statistics
- AMQ7A3C (IBM i)
- Cluster Sender Monitoring
- AMQ7A3D (IBM i)
- Queue Statistics
- AMQ7A3E (IBM i)
- Cluster Sender Statistics
- AMQ7A3F (IBM i)
- Statistics Interval
- AMQ7A40 (IBM i)
- Display MQ Route Information
- AMQ7A41 (IBM i)
- Correlation Identifier
- AMQ7A42 (IBM i)
- Message Persistence
- AMQ7A43 (IBM i)
- Message Priority
- AMQ7A44 (IBM i)
- Report Option
- AMQ7A45 (IBM i)
- Reply Queue
- AMQ7A46 (IBM i)
- Reply Queue Manager
- AMQ7A47 (IBM i)
- Message Expiry
- AMQ7A48 (IBM i)
- Pass Expiry
- AMQ7A49 (IBM i)
- Route Accumulation
- AMQ7A4A (IBM i)
- Reply Message
- AMQ7A4B (IBM i)
- Deliver Message
- AMQ7A4C (IBM i)
- Forward Message
- AMQ7A4D (IBM i)
- Maximum Activities
- AMQ7A4E (IBM i)
- Route Detail
- AMQ7A4F (IBM i)
- Browse Only
- AMQ7A50 (IBM i)
- Display Message
- AMQ7A51 (IBM i)
- Target Queue Manager
- AMQ7A52 (IBM i)
- Display Information
- AMQ7A53 (IBM i)
- Wait Time
- AMQ7A54 (IBM i)
- RTEINF(*YES) required for RPLYMSG(*YES).
- Severity
- 30 : Severe error
- Explanation
- RPLYMSG(*YES) cannot be specified without RTEINF(*YES).
- Response
- If RPLYMSG(*YES) is specified then RTEINF(*YES) must also be specified.
- AMQ7A55 (IBM i)
- RPLYQ required for RPLYMQM.
- Severity
- 30 : Severe error
- Explanation
- RPLYMQM cannot be specified without RPLYQ.
- Response
- If RPLYMQM is specified then RPLYQ must also be specified.
- AMQ7A56 (IBM i)
- CRRLID specified with invalid parameters.
- Severity
- 30 : Severe error
- Explanation
- The CRRLID parameter was specified with one or more of MSGPST, MSGPRTY, OPTION, RPLYQ, RPLYMQM, EXPIRY, EXPRPT, RTEINF RPLYMSG, DLVRMSG, FWDMSG, MAXACTS, DETAIL and BIND which are invalid with CRRLID.
- Response
- Specify only those parameters which are valid with CRRLID.
- AMQ7A57 (IBM i)
- DSPMSG(*NO) specified with invalid parameters.
- Severity
- 30 : Severe error
- Explanation
- DSPMSG(*NO) was specified with one or more of BROWSE, DSPINF and WAIT which are invalid with DSPMSG(*NO).
- Response
- Specify only those parameters which are valid with DSPMSG(*NO).
- AMQ7A58 (IBM i)
- RPLYQ required for DSPMSG(*NO) and RPLYMSG(*YES).
- Severity
- 30 : Severe error
- Explanation
- DSPMSG(*NO) and RPLYMSG(*YES) cannot be specified without RPLYQ.
- Response
- If DSPMSG(*NO) and RPLYMSG(*YES) are specified than RPLYQ must also be specified.
- AMQ7A59 (IBM i)
- RPLYQ required for DSPMSG(*NO) and OPTION not *NONE.
- Severity
- 30 : Severe error
- Explanation
- DSPMSG(*NO) and OPTION not *NONE cannot be specified without RPLYQ.
- Response
- If DSPMSG(*NO) and OPTION not *NONE are specified than RPLYQ must also be specified.
- AMQ7A5A (IBM i)
- Run WebSphere MQ Commands
- AMQ7A5B (IBM i)
- Non Persistent Message Class
- AMQ7A5C (IBM i)
- NPMCLASS not allowed with queue type *ALS or *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The NPMCLASS parameter cannot be specified for a queue of type *ALS or *RMT.
- Response
- Remove the NPMCLASS parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7A5D (IBM i)
- MONQ not allowed with queue type *ALS or *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The MONQ parameter cannot be specified for a queue of type *ALS or *RMT.
- Response
- Remove the MONQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7A5E (IBM i)
- STATQ not allowed with queue type *ALS or *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The STATQ parameter cannot be specified for a queue of type *ALS or *RMT.
- Response
- Remove the STATQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7A5F (IBM i)
- ACCTQ not allowed with queue type *ALS or *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The ACCTQ parameter cannot be specified for a queue of type *ALS or *RMT.
- Response
- Remove the ACCTQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7A60 (IBM i)
- All queue managers have been quiesced.
- Severity
- 0 : Information
- Explanation
- All queue managers have been successfully quiesced.
- Response
- None.
- AMQ7A61 (IBM i)
- MQMNAME not valid for TRCEARLY(*YES).
- Severity
- 40 : Stop Error
- Explanation
- The MQMNAME parameter can only be specified for TRCEARLY(*NO). TRCEARLY(*YES) applies to all queue managers.
- Response
- If TRCEARLY(*YES) is required remove MQMNAME from the command.
- AMQ7A62 (IBM i)
- MQMNAME not valid for SET(*END).
- Severity
- 40 : Stop Error
- Explanation
- The MQMNAME parameter can only be specified for SET(*ON) or SET(*OFF). SET(*END) applies to all queue managers.
- Response
- If SET(*END) is required remove MQMNAME from the command.
- AMQ7A63 (IBM i)
- Bind Option
- AMQ7A64 (IBM i)
- TGTMQMNAME only valid for channel type *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The TGTMQMNAME parameter can only be specified with channel type *CLTCN.
- Response
- Remove the TGTMQMNAME parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7A65 (IBM i)
- Invalid value specified for JOB parameter.
- Severity
- 40 : Stop Error
- Explanation
- A value for the JOB parameter has been specified however the
format of the parameter is incorrect. The value of this parameter
can be one of the followng formats:
generic-jobname
Job-name/User/Number
Job-name/User/Number/thread-identifier.
Note that the thread-identifier cannot be specified without a fully qualified jobname.
- Response
- Specify a value in one of the acceptable formats and then try the command again. If you are prompting this command, you must enter characters in the job name field first to clear an invalid value specified elsewhere in the parameter entry.
- AMQ7A66 (IBM i)
- Data Directory Prefix
- AMQ7A67 (IBM i)
- IPC Directory Prefix
- AMQ7A68 (IBM i)
- Allow Switchover
- AMQ7A69 (IBM i)
- ASP device
- AMQ7B00 (IBM i)
- MQI Accounting
- AMQ7B01 (IBM i)
- Input file
- AMQ7B02 (IBM i)
- Queue Accounting
- AMQ7B03 (IBM i)
- Member containing input
- AMQ7B04 (IBM i)
- Accounting Interval
- AMQ7B05 (IBM i)
- Accounting Override
- AMQ7B06 (IBM i)
- Trace data size
- AMQ7B07 (IBM i)
- Perform replay only
- AMQ7B08 (IBM i)
- Activate backup
- AMQ7B09 (IBM i)
- No connection handles to display
- AMQ7B0A (IBM i)
- Trace Route Recording
- AMQ7B0B (IBM i)
- Activity Recording
- AMQ7B0C (IBM i)
- No queue manager connections to display
- AMQ7B0D (IBM i)
- No listener objects to display
- AMQ7B0E (IBM i)
- No service objects to display
- AMQ7B0F (IBM i)
- CLWLRANK not allowed with queue type *MDL.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLRANK parameter cannot be specified for a queue of type *MDL.
- Response
- Remove the CLWLRANK parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7B10 (IBM i)
- CLWLPRTY not allowed with queue type *MDL.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLPRTY parameter cannot be specified for a queue of type *MDL.
- Response
- Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7B11 (IBM i)
- LSRNAME not allowed with BACKLOG
- Severity
- 40 : Stop Error
- Explanation
- A listener object cannot be specified with a listener backlog.
- Response
- Specify either a listener object or a listener backlog.
- AMQ7B12 (IBM i)
- MONCHL not valid for channel type *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The MONCHL parameter cannot be specified with channel type *CLTCN.
- Response
- Remove the MONCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B13 (IBM i)
- STATCHL not valid for channel types *CLTCN and *SVRCN
- Severity
- 40 : Stop Error
- Explanation
- The STATCHL parameter is valid only with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR or *CLUSRCVR.
- Response
- Remove the STATCHL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B14 (IBM i)
- CLWLRANK only valid for channel types *CLUSSDR and *CLUSRCVR.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLRANK parameter can only be specified with channel types *CLUSSDR or *CLUSRCVR.
- Response
- Remove the CLWLRANK parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B15 (IBM i)
- CLWLPRTY only valid for channel types *CLUSSDR and *CLUSRCVR.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLPRTY parameter can only be specified with channel types *CLUSSDR or *CLUSRCVR.
- Response
- Remove the CLWLPRTY parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B16 (IBM i)
- CLWLWGHT only valid for channel types *CLUSSDR and *CLUSRCVR.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLWGHT parameter can only be specified with channel types *CLUSSDR or *CLUSRCVR.
- Response
- Remove the CLWLWGHT parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B17 (IBM i)
- CLWLUSEQ only allowed with queue type *LCL.
- Severity
- 40 : Stop Error
- Explanation
- The CLWLUSEQ parameter can only be specified for a queue of type *LCL.
- Response
- Remove the CLWLUSEQ parameter from the command or, if the command is CRTMQMQ, specify a value of *LCL for QTYPE. Then try the command again.
- AMQ7B18 (IBM i)
- MCAUSRID not valid for channel type *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The MCAUSRID parameter cannot be specified with channel type *CLTCN.
- Response
- Remove the MCAUSRID parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B20 (IBM i)
- Message Read Ahead
- AMQ7B21 (IBM i)
- MSGREADAHD not allowed with queue type *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The MSGREADAHD parameter cannot be specified for a queue of type *RMT.
- Response
- Remove the MSGREADAHD parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7B22 (IBM i)
- Sharing Conversations
- AMQ7B23 (IBM i)
- SHARECNV is valid only when CHLTYPE is *SVRCN or *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The sharing conversations (SHARECNV) parameter cannot be specified for a channel type other than *SVRCN or *CLTCN.
- Response
- Remove the SHARECNV parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B24 (IBM i)
- Maximum Property Data Length
- AMQ7B25 (IBM i)
- Default Put Response
- AMQ7B26 (IBM i)
- Message mark-browse interval
- AMQ7B27 (IBM i)
- Property Control
- AMQ7B28 (IBM i)
- Maximum Instances
- AMQ7B29 (IBM i)
- Maximum Instances Per Client
- AMQ7B2A (IBM i)
- Client Channel Weight
- AMQ7B2B (IBM i)
- Connection Affinity
- AMQ7B2C (IBM i)
- Target Type
- AMQ7B2D (IBM i)
- PROPCTL not allowed with queue type *RMT.
- Severity
- 40 : Stop Error
- Explanation
- The PROPCTL parameter cannot be specified for a queue of type *RMT.
- Response
- Remove the PROPCTL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7B2E (IBM i)
- TARGTYPE only allowed with queue type *ALS.
- Severity
- 40 : Stop Error
- Explanation
- The TARGTYPE parameter can only be specified for a queue of type *ALS.
- Response
- Remove the TARGTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
- AMQ7B2F (IBM i)
- PROPCTL only allowed with channel type *SDR, *SRV, *CLUSSDR or *CLUSRCVR.
- Severity
- 40 : Stop Error
- Explanation
- The PROPCTL parameter can only be specified for a channel of type *SDR, *SVR, *CLUSSDR or *CLUSRCVR.
- Response
- Remove the PROPCTL parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B30 (IBM i)
- MAXINST only allowed with channel type *SVRCN.
- Severity
- 40 : Stop Error
- Explanation
- The MAXINST parameter can only be specified for a channel of type *SVRCN.
- Response
- Remove the MAXINST parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B31 (IBM i)
- MAXINSTC only allowed with channel type *SVRCN.
- Severity
- 40 : Stop Error
- Explanation
- The MAXINSTC parameter can only be specified for a channel of type *SVRCN.
- Response
- Remove the MAXINSTC parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B32 (IBM i)
- CLNTWGHT only allowed with channel type *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The CLNTWGHT parameter can only be specified for a channel of type *CLTCN.
- Response
- Remove the CLNTWGHT parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B33 (IBM i)
- AFFINITY only allowed with channel type *CLTCN.
- Severity
- 40 : Stop Error
- Explanation
- The AFFINITY parameter can only be specified for a channel of type *CLTCN.
- Response
- Remove the AFFINITY parameter from the command or, if the command is CRTMQMCHL, specify a different value for CHLTYPE. Then try the command again.
- AMQ7B34 (IBM i)
- Create MQ Topic
- AMQ7B35 (IBM i)
- Change MQ Topic
- AMQ7B36 (IBM i)
- Copy MQ Topic
- AMQ7B37 (IBM i)
- Display MQ Topic
- AMQ7B38 (IBM i)
- Topic name
- AMQ7B39 (IBM i)
- Topic string
- AMQ7B3A (IBM i)
- Durable subscriptions
- AMQ7B3B (IBM i)
- Durable model queue
- AMQ7B3C (IBM i)
- Non-durable model queue
- AMQ7B3D (IBM i)
- Publish
- AMQ7B3E (IBM i)
- Subscribe
- AMQ7B3F (IBM i)
- Wildcard behaviour
- AMQ7B40 (IBM i)
- Persistent message delivery
- AMQ7B41 (IBM i)
- Non-persistent message delivery
- AMQ7B42 (IBM i)
- From topic
- AMQ7B43 (IBM i)
- To topic
- AMQ7B44 (IBM i)
- PubSub max msg retry count
- AMQ7B45 (IBM i)
- PubSub NPM msg
- AMQ7B46 (IBM i)
- PubSub NPM msg response
- AMQ7B47 (IBM i)
- PubSub syncpoint
- AMQ7B48 (IBM i)
- Change MQ Subscription
- AMQ7B49 (IBM i)
- Copy MQ Subscription
- AMQ7B4A (IBM i)
- From subscription
- AMQ7B4B (IBM i)
- To subscription
- AMQ7B4C (IBM i)
- Destination Queue Manager
- AMQ7B4D (IBM i)
- Destination Correlation Id
- AMQ7B4E (IBM i)
- Subscription User Id
- AMQ7B4F (IBM i)
- Publish Application Id
- AMQ7B50 (IBM i)
- Subscription User Data
- AMQ7B51 (IBM i)
- Selector String
- AMQ7B52 (IBM i)
- PubSub Property
- AMQ7B53 (IBM i)
- Destination Class
- AMQ7B54 (IBM i)
- Subscription Scope
- AMQ7B55 (IBM i)
- Variable User
- AMQ7B57 (IBM i)
- Request Publications
- AMQ7B58 (IBM i)
- Publish Priority
- AMQ7B59 (IBM i)
- Wildcard Schema
- AMQ7B5A (IBM i)
- Expiry Time
- AMQ7B5B (IBM i)
- Create MQ Subscription
- AMQ7B5C (IBM i)
- Subscription name
- AMQ7B5D (IBM i)
- Topic object
- AMQ7B5E (IBM i)
- Destination
- AMQ7B5F (IBM i)
- Work with MQ Subscriptions
- AMQ7B60 (IBM i)
- No subscriptions to display
- AMQ7B61 (IBM i)
- Display MQ Subscription
- AMQ7B62 (IBM i)
- Delete MQ Subscription
- AMQ7B63 (IBM i)
- Publish Accounting Token
- AMQ7B67 (IBM i)
- Subscription identifier
- AMQ7B68 (IBM i)
- From subscription identifier
- AMQ7B69 (IBM i)
- Pubsub Engine Control
- AMQ7B6A (IBM i)
- No message properties to display.
- Severity
- 0 : Information
- Explanation
- The message contains no message properties.
- Response
- None.
- AMQ7B6B (IBM i)
- Trace directory
- AMQ7B6C (IBM i)
- Trace start control
- AMQ7B6D (IBM i)
- User
- AMQ7B6E (IBM i)
- Trace end control
- AMQ7B6F (IBM i)
- Clear MQ Topic String
- AMQ7B71 (IBM i)
- Topic Tree Life Time
- AMQ7B72 (IBM i)
- Job information
- AMQ7B73 (IBM i)
- Thread identifier
- AMQ7B74 (IBM i)
- Clear type
- AMQ7B75 (IBM i)
- Clear scope
- AMQ7B76 (IBM i)
- Invalid combination of security exit parameters.
- Severity
- 40 : Stop Error
- Explanation
- An invalid combination of security exit parameters has been provided on the command. The SCYEXIT parameter cannot be specified for a channel of type *CLTCN. The CSCYEXIT parameter can only be specified for a channel of type *CLTCN. You cannot specify both SCYEXIT and CSCYEXIT parameters together on the same command.
- Response
- Remove the invalid combination of security exit parameters from the command and then try the command again.
- AMQ7B77 (IBM i)
- Invalid combination of send exit parameters.
- Severity
- 40 : Stop Error
- Explanation
- An invalid combination of send exit parameters has been provided on the command. The SNDEXIT parameter cannot be specified for a channel of type *CLTCN. The CSNDEXIT parameter can only be specified for a channel of type *CLTCN. You cannot specify both SNDEXIT and CSNDEXIT parameters together on the same command.
- Response
- Remove the invalid combination of send exit parameters from the command and then try the command again.
- AMQ7B78 (IBM i)
- Invalid combination of receive exit parameters.
- Severity
- 40 : Stop Error
- Explanation
- An invalid combination of receive exit parameters has been provided on the command. The RCVEXIT parameter cannot be specified for a channel of type *CLTCN. The CRCVEXIT parameter can only be specified for a channel of type *CLTCN. You cannot specify both RCVEXIT and CRCVEXIT parameters together on the same command.
- Response
- Remove the invalid combination of receive exit parameters from the command and then try the command again.
- AMQ7B79 (IBM i)
- Command is not applicable to WebSphere MQ Publish/Subscribe broker.
- Severity
- 0 : Information
- Explanation
- This command performs a null operation.
- Response
- Refer to Publish/Subscribe User's Guide publication for alternative ways to perform this function.