Date Created: Mon 28-Jan-2008

Related Document Categories:

Get my WebSphere MQ course here >> http://www.themiddlewareshop.com/products/


Did you know? I now sell WMQ 75. training course for self study, it is only $149 >> http://www.themiddlewareshop.com/products

AMQ7000-AMQ7999 WebSphere MQ product messages

Reading variables in the message
Some messages display text or numbers that vary according to the circumstances giving rise to the message; these are known as message variables. The message variables are indicated in this book by the use of the '&' symbol and a number: &1, &2, and so on.

In some cases a message may have variables in the Explanation or User action. Find the values of the message variables by looking in the error log. The complete message, including the Explanation and the User action, is recorded there.


AMQ7001 The location specified for the creation of the queue manager is not valid.

Explanation: The directory under which the queue managers are to be created is not valid. It may not exist, or there may be a problem with authorization.
User 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.

Explanation: An internal error occurred while trying to create or delete a queue manager file. It is likely that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.
User Response: Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.

AMQ7002 An error occurred manipulating a file.

Explanation: An internal error occurred while trying to create or delete a queue manager file.
In the case of a failure to delete a file a common reason for this error is that a non MQ process, such as the windows explorer or a virus checker, is accessing the file. In the case where the object that cannot be deleted is a directory then a non MQ process may be accessing a file within the directory or one of its subdirectories.
It is also possible that the error was caused by a disk having insufficient space, or by problems with authorization to the underlying filesystem.
User Response: Identify the file that caused the error, using problem determination techniques. For example check if there are any FFST files, which may identify the queue manager file causing the error. This error may also be caused if users have created, renamed or deleted that file. Correct the error in the filesystem and submit the request again.

AMQ7005 The queue manager is running.

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.
User Response: If the queue manager should be stopped, stop the queue manager and submit the failed command again.

AMQ7006 Missing attribute &5 from configuration data.

Explanation: The &4 stanza in the configuration data is missing the required &5 attribute.
User Response: Check the contents of the configuration data and retry the operation.

AMQ7008 The queue manager already exists.

Explanation: You tried to create a queue manager that already exists.
User Response: If you specified the wrong queue manager name, correct the name and submit the request again.

AMQ7010 The queue manager does not exist.

Explanation: You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.
User 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.

Explanation: While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
User 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.

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.
User Response: Correct the value and resubmit the request.

AMQ7013 There is an error in the name of the specified dead-letter queue.

Explanation: You specified a name for the dead-letter queue that is not valid.
User Response: Correct the name and resubmit the request.

AMQ7014 There is an error in the name of the specified default transmission queue.

Explanation: You specified a name for the default transmission queue that is not valid.
User Response: Correct the name and submit the command again.

AMQ7015 There is an error in the maximum number of open object handles specified.

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.
User Response: Correct the value and submit the command again.

AMQ7016 There is an error in the maximum number of uncommitted messages specified.

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.
User Response: Correct the value and submit the command again.

AMQ7017 Log not available.

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.
User 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.

Explanation: An attempt has been made to perform an operation on a queue manager. Resources required to perform the operation are not available.
User Response:

AMQ7019 An error occurred while creating the directory structure for the new queue manager.

Explanation: During creation of the queue manager an error occurred while trying to create a file or directory.
User Response: Identify why the queue manager files cannot be created. It is probable that there is insufficient space on the specified disk, or that there is a problem with access control. Correct the problem and submit the command again.

AMQ7020 The operation was carried out, but one or more transactions remain in-doubt.

Explanation: The queue manager tried to resolve all internally coordinated transactions which are in-doubt. In-doubt transactions still remain after the queue manager has attempted to deliver the outcome of these transactions to the resource managers concerned. Transactions remain in-doubt when the queue manager cannot deliver the outcome of the transaction to each of the participating resource managers. For example, a resource manager may not be available at this time.
User Response: Use the DSPMQTRN command to display the remaining in-doubt transactions.

AMQ7021 An error occurred while deleting the directory structure for the queue manager.

Explanation: While deleting the queue manager, an error occurred deleting a file or directory. The queue manager may not have been completely deleted.
User 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.

Explanation: The identification number of the resource manager you supplied was not recognized.
User 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.

Explanation: The resource manager, the identification number of which you supplied, was in an invalid state.
User 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.

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.
User Response: Correct the command and submit it again. Additional information on the arguments causing the error may be found in the error logs for the queue, or queue manager, referenced in the command.

AMQ7025 Error in the descriptive text argument (-c parameter) of the crtmqm command.

Explanation: The descriptive text you supplied to the crtmqm command was in error.
User Response: Correct the descriptive text argument and submit the command again.

AMQ7026 A principal or group name was invalid.

Explanation: You specified the name of a principal or group which does not exist.
User Response: Correct the name and resubmit the request.

AMQ7027 Argument &3 supplied to command &4 is invalid.

Explanation: The argument &3 was supplied to the command &4 which could not be interpreted. This argument is either not accepted by the command, or an extra flag has been included.
User Response: Correct the command and submit it again.

AMQ7028 The queue manager is not available for use.

Explanation: You have requested an action that requires the queue manager running, however, the queue manager is not currently running.
User 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.

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.
User Response: None.

AMQ7031 The queue manager is stopping.

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.
User Response: None

AMQ7041 Object already exists.

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 &3, in directory &4, of object type &5.
User Response: Remove the conflicting object from the MQ system, then try the operation again.

AMQ7042 Media image not available for object &3 of type &4.

Explanation: The media image for object &3, type &4, is not available for media recovery. A log file containing part of the media image cannot be accessed.
User 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.

Explanation: Media recovery is not possible on a queue manager using a circular log. Damaged objects must be deleted on such a queue manager.
User Response: None.

AMQ7047 An unexpected error was encountered by a command.

Explanation: An internal error occurred during the processing of a command.
User Response: Follow problem determination procedures to identify the cause of the error.

AMQ7048 The queue manager name is either not valid or not known

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.
User Response: Correct the name and submit the command again.

AMQ7053 The transaction has been committed.

Explanation: The prepared transaction has been committed.
User Response: None.

AMQ7054 The transaction has been backed out.

Explanation: The prepared transaction has been backed out.
User Response: None.

AMQ7055 The transaction number is not recognized.

Explanation: The number of the transaction you supplied was not recognized as belonging to an in-doubt transaction.
User 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.

AMQ7056 Transaction number &1,&2.

Explanation: This message is used to report the number of an in-doubt transaction.
User Response: None.

AMQ7059 An error occurred when reading the configuration data.

Explanation: An error has occurred when reading the configuration data.
User Response: If you have changed the configuration data, check and correct the change. If you have not changed the configuration data, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ7060 An error has occurred locking the configuration data.

Explanation: An error has occurred locking the configuration data.
User 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. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ7061 An expected stanza in the configuration data is missing or contains errors.

Explanation: An expected stanza is missing from the configuration data or the stanza contains errors.
User Response: If you have changed the configuration data, check and correct the change.

AMQ7062 Unable to access the configuration data.

Explanation: Access to the configuration data is denied.
User Response: If you have changed the configuration data permissions, check and correct the change.

AMQ7063 Configuration data is missing.

Explanation: The configuration data for WebSphere MQ is missing.
User Response: If you have changed the configuration data, recover the previous configuration data and retry the operation.

AMQ7064 Log path not valid or inaccessible.

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.
User 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.

AMQ7065 Insufficient space on disk.

Explanation: The operation cannot be completed due to shortage of disk space.
User Response: Either make more disk space available, or reduce the disk requirements of the command you issued.

AMQ7066 There are no prepared transactions.

Explanation: There are no prepared transactions to be resolved.
User Response: None.

AMQ7068 Authority file contains an authority stanza that is not valid.

Explanation: A syntax error has been found in one of the files containing authorization information for the queue manager.
User 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.

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 may not be a default queue manager defined for the machine at present.
User Response: There is probably a problem with the configuration data. Update the configuration data to specify the desired default queue manager, or delete and recreate the queue manager.

AMQ7072 Stanza not valid. Refer to the error log for more information.

Explanation: A stanza that is not valid was found. Refer to the error log for more information.
User Response: Correct the error and retry the operation.

AMQ7073 Log size not valid.

Explanation: Either the number of log files or the size of the log files was outside the accepted values.
User Response: Make sure that the log parameters you enter lie within the valid range.

AMQ7074 Unknown stanza key &4 at &3 in the configuration data.

Explanation: Key &3 contained a stanza called &4. This stanza is not recognized.
User Response: Check the contents of the configuration data and retry the operation.

AMQ7075 Unknown attribute &4 at &3 in the configuration data.

Explanation: Key &3 in the configuration data contained an attribute called &4 that is not valid. This attribute is not recognized in this context.
User Response: Check the contents of the configuration data and retry the operation.

AMQ7076 Value &5 not valid for attribute &4 at &3 in the configuration data.

Explanation: Key &3 in the configuration data contained value &5 that is not valid for the attribute &4.
User Response: Check the contents of the configuration data and retry the operation.

AMQ7077 You are not authorized to perform the requested operation.

Explanation: You tried to issue a command for the queue manager. You are not authorized to perform the command.
User 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.

Explanation: You entered an object type of *ALL or *MQM and an object name that contains generic characters, this is an invalid combination.
User Response: Correct the command and submit it again.

AMQ7080 No objects processed.

Explanation: No objects were processed, either because no objects matched the criteria given, or because the objects found did not require processing.
User Response: None.

AMQ7081 Object &3, type &4 recreated.

Explanation: The object &3, type &4 was recreated from its media image.
User Response: None.

AMQ7082 Object &3, type &4 is not damaged.

Explanation: Object &3, type &4 cannot be recreated since it is not damaged.
User Response: None

AMQ7083 A resource problem was encountered by a command.

Explanation: The command failed due to a resource problem. Possible causes include the log being full or the command running out of memory.
User Response: Look at the previous messages to diagnose the problem. Rectify the problem and retry the operation.

AMQ7084 Object &3, type &4 damaged.

Explanation: The object &3, type &4 was damaged. The object must be deleted or, if the queue manager supports media recovery, recreated from its media image.
User Response: Delete the object or recreate it from its media image.

AMQ7085 Object &3, type &4 not found.

Explanation: Object &3, type &4 cannot be found.
User Response: None.

AMQ7086 Media image for object &3, type &4 recorded.

Explanation: The media image for object &3, type &4, defined in Queue Manager &5, has been recorded.
User Response: None.

AMQ7087 Object &3, type &4 is a temporary object

Explanation: Object &3, type &4 is a temporary object. Media recovery operations are not permitted on temporary objects.
User Response: None.

AMQ7088 Object &3, type &4 in use.

Explanation: Object &3, type &4 is in use. Either an application has it open or, if it is a local queue, there are uncommitted messages on it.
User 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.

Explanation: Another media recovery operation is already in progress. Only one media recovery operation is permitted at a time.
User Response: Wait for the existing media recovery operation to complete and retry the operation.

AMQ7090 The queue manager CCSID is not valid.

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.
User Response: Check the CCSID is valid for the machine on which you are working.

AMQ7091 You are performing authorization for the queue manager, but you specified an object name.

Explanation: Modification of authorizations for a queue manager can be performed only from that queue manager. You must not specify an object name.
User Response: Correct the command and submit it again.

AMQ7092 An object name is required but you did not specify one.

Explanation: The command needs the name of an object, but you did not specify one.
User Response: Correct the command and submit it again.

AMQ7093 An object type is required but you did not specify one.

Explanation: The command needs the type of the object, but you did not specify one.
User Response: Correct the command and submit it again.

AMQ7094 You specified an object type that is not valid, or more than one object type.

Explanation: Either the type of object you specified was not valid, or you specified multiple object types on a command which supports only one.
User Response: Correct the command and submit it again.

AMQ7095 An entity name is required but you did not specify one.

Explanation: The command needs one or more entity names, but you did not specify any. Entities can be principals or groups.
User Response: Correct the command and submit it again.

AMQ7096 An authorization specification is required but you did not provide one.

Explanation: The command sets the authorizations on WebSphere MQ objects. However you did not specify which authorizations are to be set.
User Response: Correct the command and submit it again.

AMQ7097 You gave an authorization specification that is not valid.

Explanation: The authorization specification you provided to the command contained one or more items that could not be interpreted.
User Response: Correct the command and submit it again.

AMQ7098 The command accepts only one entity name. You specified more than one.

Explanation: The command can accept only one principal or group name. You specified more than one.
User Response: Correct the command and submit it again.

AMQ7099 Entity &3 has the following authorizations for object &4:

Explanation: Informational message. The list of authorizations follows.
User Response: None.

AMQ7104 Resource manager &1 has prepared.

Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction.
User Response: None.

AMQ7105 Resource manager &1 has committed.

Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction.
User Response: None.

AMQ7106 Resource manager &1 has rolled back.

Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction.
User Response: None.

AMQ7107 Resource manager &1 is &3.

Explanation: This message reports the identification number and name of a resource manager.
User Response: None.

AMQ7108 Any in-doubt transactions have been resolved.

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.
User Response: None.

AMQ7109 A decision on behalf of the unavailable resource manager has been delivered.

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.
User Response: None.

AMQ7110 Media image for the syncfile recorded.

Explanation: The media image for the syncfile has been recorded.
User Response: None.

AMQ7111 Resource manager &1 has participated.

Explanation: This message reports the state of a resource manager with respect to an in-doubt transaction.
User Response: None.

AMQ7112 Transaction number &1,&2 has encountered an error.

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.
User 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

Explanation: The required flag, -rn, was omitted from the command crtmqm
User Response: Add the flag and associated database name and submit it again.

AMQ7114 The Database Password argument, -rp, is missing from the command crtmqm

Explanation: The required flag, -rp, was omitted from the command crtmqm
User Response: Add the flag and associated database password and submit it again.

AMQ7115 The Database Type argument, -rt, is missing from the command crtmqm

Explanation: The required flag, -rt, was omitted from the command crtmqm
User Response: Add the flag and associated database type and submit it again

AMQ7116 The Database Type argument, -rt, is greater than 8 characters long

Explanation: The argument supplied with the flag -rt, is greater than 8 characters long
User Response: Reduce the length of the database type argument and submit it again

AMQ7117 The MSD shared library failed to load.

Explanation: The MSD shared library was either not located or failed to load correctly.
User 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 may be found in the FFST logs. Also, ensure that ensure that the MSD shared library is installed correctly.

AMQ7120 The Trial Period license for this copy of WebSphere MQ has expired.

Explanation: This copy of WebSphere MQ was licensed to be used in trial mode for a limited period only. This period has expired.
User Response: Install a Production license for this copy of WebSphere MQ.

AMQ7121 The trial period for this copy of WebSphere MQ has now expired.

Explanation: This copy of WebSphere MQ was licensed for a limited period only. This period has now expired.
User Response: Install a Production license for this copy of WebSphere MQ.

AMQ7122 The Trial Period License Agreement was not accepted.

Explanation: When the Trial Period License Agreement is displayed, the user must accept it before this copy of WebSphere MQ can be used.
User 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.

Explanation: This copy of WebSphere MQ is licensed for a limited period only.
User Response: None.

AMQ7124 This is the final day of the trial period for this copy of WebSphere MQ.

Explanation: This copy of WebSphere MQ is licensed for a limited period only.
User Response: Install a Production license for this copy of WebSphere MQ.

AMQ7125 There are &1 days left in the trial period for this copy of WebSphere MQ.

Explanation: This copy of WebSphere MQ is licensed for a limited period only.
User Response: None.

AMQ7126 This copy of WebSphere MQ is now running in Production mode.

Explanation: A Production license has been installed for this copy of WebSphere MQ.
User Response: None.

AMQ7127
Press Enter when you have read the messages

Explanation: One or more messages have been displayed. They will disappear when the user presses the Enter key.
User Response: Press the Enter key when the messages are no longer required.

AMQ7128 No license installed for this copy of WebSphere MQ.

Explanation: No Production, Beta, or Trial Period license has been installed for this copy of WebSphere MQ.
User Response: Use the SETMQPRD command to install the production license for this copy of WebSphere MQ or use the SETMQTRY command to install a Trial Period or Beta license which will allow this copy of WebSphere MQ to be used for a limited period.

AMQ7129 The trial period for this copy of WebSphere MQ has already been started.

Explanation: This copy of WebSphere MQ is licensed for a limited period only and the trial period has been started previously.
User Response: None.

AMQ7130 This copy of WebSphere MQ is running in Production mode.

Explanation: A Production license has been installed for this copy of WebSphere MQ. A beta or trial period cannot be started.
User 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.

Explanation: The Trial Period License Agreement has been displayed to the user and the user should now accept or reject the Agreement.
User Response: Reply 'yes' or 'no' and press 'Enter'.

AMQ7143
Press Enter to continue

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.
User Response: Press the Enter key when ready for the next part of the Agreement to be displayed.

AMQ7153 A license could not be installed for this copy of WebSphere MQ.

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.
User Response: Check the ownership and permissions of the 'qmgrs/@SYSTEM' directory.

AMQ7154 The Production license for this copy of WebSphere MQ has expired.

Explanation: The production license for this copy of WebSphere MQ has an expiry date. This date has been passed.
User Response: Contact your IBM support center.

AMQ7155 License file '&3' not found or not valid. See the 'Quick Beginnings' book.

Explanation: The program requires that the file '&3' is present, available and is a valid license file. See the 'Quick Beginnings' book for this platform.
User Response: If the SETMQPRD command was issued, check that the name is specified correctly. If the SETMQTRY command was issued, check that the specified file exists.

AMQ7156 This copy of WebSphere MQ is already running in Production mode.

Explanation: A Production license has previously been installed for this copy of WebSphere MQ.
User Response: None.

AMQ7157 The Production license is not valid for this copy of WebSphere MQ.

Explanation: The license '&3' has been installed but it is not a valid production license for this copy of WebSphere MQ.
User 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.

Explanation: The license '&3' has been installed but it is not a valid trial period license for this copy of WebSphere MQ.
User Response: Check that the correct version of the file is available.

AMQ7159 A FASTPATH application has ended unexpectedly.

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.
User 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.

AMQ7162 The setmqaut command completed successfully.

Explanation:
User Response:

AMQ7196 By installing this product, you accept the terms of the International Program License Agreement and the License Information supplied with the product.

Explanation:
User Response: None.

AMQ7197 A production or trial license could not be installed for this copy of WebSphere MQ.

Explanation: This copy of WebSphere MQ is a beta version and cannot be used with a production or trial license.
User Response: Uninstall the beta version of WebSphere MQ and install the production or trial version.

AMQ7198 Insufficient capacity units.

Explanation: The purchased processor capacity (&1) is less than the number of processors (&2) in this machine.
User Response: Ensure sufficient capacity units have been purchased and use the setmqcap command to set the purchased processor capacity for this installation. Refer to the Quick Beginnings book for more information.

AMQ7199 The purchased processor capacity is set to &1.

Explanation: The purchased processor capacity for this installation has been set to &1 using the setmqcap or CHGMQMCAP command.
User Response: None.

AMQ7200 The purchased processor capacity is &1

Explanation: The purchased processor capacity is currently set to &1
User Response: Ensure sufficient capacity units have been purchased and, if necessary, use the setmqcap command (or CHGMQMCAP command on iSeries) to change the purchased processor capacity for this installation. Refer to the Quick Beginnings book for more information.

AMQ7201 The number of processors in this machine is &1

Explanation: The operating system reports that the number of processors in this machine is &1
User Response: None.

AMQ7202 The number of capacity units is sufficient for all future possible upgrades to this machine.

Explanation: The purchased processor capacity for this installation has been set to -1
User Response: None.

AMQ7203 Purchased processor capacity not set (use setmqcap).

Explanation: The purchased processor capacity for this installation has not been set.
User Response: Ensure sufficient capacity units have been purchased and use the setmqcap command to set the purchased processor capacity for this installation. Refer to the Quick Beginnings book for more information.

AMQ7206 Group name has been truncated.

Explanation: WebSphere MQ only supports group names up to 12 characters long. The operating system is attempting to return a group longer than this.
User Response: Reduce the group name to 12 characters or less.

AMQ7207 User ID longer than 12 characters.

Explanation: WebSphere MQ only supports user names up to 12 characters long. This operation is being attempted from a user name longer than this.
User Response: Reduce the user name to 12 characters or less.

AMQ7208 The queue manager failed to pass a PCF message to another queue manager.

Explanation: The queue manager attempted to put a PCF message to &3 to start the channel &4 to cluster queue manager &5. The put failed with reason &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 &3.
User Response: Resolve the problem with &3 and if necessary start the channel manually.

AMQ7209 The queue manager attempted to open SYSTEM.CHANNEL.INITQ which failed with reason &3

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
User 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.

Explanation: The Cluster Workload exit module '&3' could not be loaded for reason &4.
User Response: Correct the problem with the Cluster Workload exit module '&3'

AMQ7211 The Queue Manager is still waiting for a reply from the Cluster Workload Exit server process.

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 &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.
User 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.

Explanation: The address of the Cluster exit function '&4' could not be found in module '&3' for reason &1 &5.
User Response: Correct the problem with the Cluster exit function '&4' in the module '&3'

AMQ7214 The module for API Exit '&3' could not be loaded.

Explanation: The module '&4' for API Exit '&3' could not be loaded for reason &5.
User Response: Correct the problem with the API Exit module '&3'.

AMQ7215 The API Exit '&3' function '&4' could not be found in the module '&5'.

Explanation: The API Exit '&3' function '&4' could not be found in the module '&5'. The internal return code was &1.
User Response: Correct the problem with the API Exit '&3'.

AMQ7216 An API Exit initialization function returned an error.

Explanation: The API Exit '&3' function '&4' in the module '&5' returned CompCode &1 and ReasonCode &2.
User Response: Correct the problem with the API Exit '&3'

AMQ7217 The response set by the exit is not valid.

Explanation: The API Exit '&3' module '&4' function '&5' returned a response code '&1' that is not valid in the ExitResponse field of the API Exit parameters (MQAXP).
User Response: Investigate why the API Exit '&3' set a response code that is not valid.

AMQ7225 No matching authority records.

Explanation: No authority records match the specified parameters.
User Response:

AMQ7226 The profile name is invalid.

Explanation: The profile name contains invalid characters, contains an invalid wildcard specification, or is of invalid length.
User Response: Correct the profile name and submit it again.

AMQ7227 WebSphere MQ encountered the following network error: &3

Explanation: WebSphere MQ failed to successfully complete a network operation due to the specified error.
User Response: Ensure that your network is functioning correctly.

AMQ7305 Trigger message could not be put on an initiation queue.

Explanation: The attempt to put a trigger message on queue &4 on queue manager &5 failed with reason code &1. The message will be put on the dead-letter queue.
User Response: Ensure that the initiation queue is available, and operational.

AMQ7306 The dead-letter queue must be a local queue.

Explanation: An undelivered message has not been put on the dead-letter queue &4 on queue manager &5, because the queue is not a local queue. The message will be discarded.
User Response: Inform your system administrator.

AMQ7307 A message could not be put on the dead-letter queue.

Explanation: The attempt to put a message on the dead-letter queue &4 on queue manager &5 failed with reason code &1. The message will be discarded.
User Response: Ensure that the dead-letter queue is available and operational.

AMQ7308 Trigger condition &1 was not satisfied.

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 &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.)
User 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.

Explanation: The attempt to put a report message on queue &4 on queue manager &5 failed with reason code &1. The message will be put on the dead-letter queue.
User Response: Ensure that the reply-to queue is available and operational.

AMQ7463 The log for queue manager &3 is full.

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.
User Response: This situation may be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you may 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 recreate the queue manager.

AMQ7464 The log for queue manager &3 is no longer full.

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.
User Response: None

AMQ7465 The log for queue manager &3 is full.

Explanation: An attempt to resolve a log full situation has failed. This is due to the presence of a long-running transaction.
User 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.

Explanation: The log for queue manager &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.
User 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 &3 is &4.

Explanation: The log file &4 contains the oldest log record required to restart the queue manager. Log records older than this may be required for media recovery.
User Response: You can move log files older than &4 to an archive medium to release space in the log directory. If you move any of the log files required to recreate objects from their media images, you will have to restore them to recreate the objects.

AMQ7468 The oldest log file required to perform media recovery of queue manager &3 is &4.

Explanation: The log file &4 contains the oldest log record required to recreate any of the objects from their media images. Any log files prior to this will not be accessed by media recovery operations.
User Response: You can move log files older than &4 to an archive medium to release space in the log directory.

AMQ7469 Transactions rolled back to release log space.

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.
User 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 &3, type &4 damaged.

Explanation: Object &3, type &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.
User 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 may be recovered from a media image using the rcrmqmobj command or it may be deleted.

AMQ7601 Duplicate XA resource manager '&5' not valid for attribute &4 at &3 in the configuration data.

Explanation: Key &3 in the configuration data contained a duplicate XA resource manager '&5'. This is not valid for attribute &4. Each XA resource manager must be given a unique name.
User Response: Check the contents of the configuration data and retry the operation.

AMQ7603 WebSphere MQ has been configured with resource manager '&3' that is not valid.

Explanation: The XA switch file &4 for resource manager &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.
User Response: Remove the offending XAResourceManager stanza from the configuration data and restart the queue manager.

AMQ7604 The XA resource manager '&3' was not available when called for &4. The queue manager is continuing without this resource manager.

Explanation: The XA resource manager '&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 may be a configuration problem.
User Response: Try to establish the reason why the resource manager is unavailable. It may 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 may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters.

AMQ7605 The XA resource manager &3 has returned an unexpected return code &1, when called for &4.

Explanation: WebSphere MQ received an unexpected return code when calling XA resource manager &3 at its &4 entry point. This indicates an internal error, either within MQ or the resource manager.
User 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 &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'&5'. If you think that the error lies within the queue manager, 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.

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 may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to commit their updates.
User Response: The transaction with the mixed outcome is identified by the following XID of X'&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. To preserve data integrity you must perform recovery steps local to the failing resource managers.

AMQ7607 A transaction has been rolled back but one or more resource managers have committed.

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 may now be out of synchronization. MQ will issue further messages to indicate which resource managers failed to roll back their updates.
User Response: The transaction with the mixed outcome is identified by the following XID of X'&3'. The messages which identify the failing resource managers will also contain this same XID. If the transaction has completed it will not 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 some participants are still in prepared state. 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.

Explanation: This message is associated with the message AMQ7606 reporting a mixed transaction outcome. It identifies one of the resource managers ('&4') that failed to commit its updates. The transaction associated with this failure is identified by the following XID of X'&3'.
User Response: Use the return code &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. 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.

Explanation: This message is associated with an earlier AMQ7607 message reporting a mixed transaction outcome. It identifies one of the resource managers ('&4') that failed to rollback its updates. The transaction associated with this failure is identified by the following XID of X'&3'.
User Response: Use the return code &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. To preserve data integrity you will need to perform recovery steps local to this resource manager.

AMQ7612 Switch call exception

Explanation: Exception number &1 occurred when calling resource manager switch &3.
User Response: Check the resource manager switch has not been corrupted.

AMQ7622 WebSphere MQ could not load the XA switch load file for resource manager '&3'.

Explanation: An error has occurred loading XA switch file &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.
User 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. To do this, define the switch load file as a fully-qualified name. Note that if the queue manager is still running it must be restarted for any changes made to its configuration data can be picked up.

AMQ7623 WebSphere MQ has not been configured with XA resource manager '&3' which may be involved in in-doubt transactions. The queue manager is continuing without this resource manager.

Explanation: The queue manager has recognized that XA resource manager '&3' was removed from the registry entry of the queue manager. However, it was logged as being involved in &1 transactions that are still in-doubt. The queue manager cannot resolve these transactions.
User 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 '&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 may 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 when the queue manager is restarted.

AMQ7624 An exception occurred during an &4 call to XA resource manager '&3'.

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.
User Response: An FFST should have been produced which documents the exception. Use this and any further FFSTs to 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 &1 to this resource manager. Use this to isolate the flows concerned. First contact the supplier of the resource manager for problem resolution. If you think that the problem lies within the queue manager, contact your IBM support center. Do not discard any information describing the problem until the problem has been resolved.

AMQ7625 The XA resource manager '&3' has become available again.

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.
User Response: None.

AMQ7626 XA resource manager initialization failure. Refer to the error log for more information.

Explanation: The queue manager has failed to initialize one or more of the XA resource managers defined in the configuration data.
User Response: Correct the error and restart the queue manager.

AMQ7701 DMPMQLOG command is starting.

Explanation: You have started the DMPMQLOG command and it is processing your request.
User Response: None.

AMQ7702 DMPMQLOG command has finished successfully.

Explanation: The DMPMQLOG command has finished processing your request and no errors were detected.
User Response: None.

AMQ7703 DMPMQLOG command has used option '&3' with an invalid value '&4'.

Explanation: You started the DMPMQLOG command specifying an invalid option value. The '&4' value for option '&3' is either missing or of an incorrect format.
User Response: Refer to the command syntax, and then try the command again.

AMQ7704 DMPMQLOG command has used an invalid option '&3'.

Explanation: You started the DMPMQLOG command specifying an invalid option of '&3'.
User Response: Refer to the command syntax and retry the command.

AMQ7706 DMPMQLOG command has used an incorrect queue manager name '&3' or path '&4'.

Explanation: The DMPMQLOG command has used '&3' as the queue manager name and, if shown, '&4' as the directory path for '&3'. Either '&3' and/or '&4' is incorrect; if '&4' is not shown then it is '&3' which is incorrect.
Possible reasons for the error include:
that '&3' is not an existing queue manager name;
the entries for '&3' in the MQ configuration data are incorrect;
'&4' is not a correct path for '&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.
User Response: Check that '&3' is an existing queue manager name. Check your MQ configuration data to ensure that '&3' and its associated entries are correct. If '&4' is shown, check that it is a correct MQ system directory path for '&3'.

AMQ7707 DMPMQLOG command has failed: CompCode = 0x&1.

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.
User Response: Check that the queue manager being used by DMPMQLOG, specified using the -m command option or defaulted, exists and is not currently running. If it does not exist, retry the command specifying an existing queue manager. If it is running, stop the queue manager and then retry the command. 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 contact your IBM support center.

AMQ7708 DMPMQLOG command has used an invalid default queue manager name.

Explanation: You started the DMPMQLOG command without specifying option -m (queue manager name option); your MQ default queue manager name has been used. This default name could not be found or is not valid.
User Response: Check that the default queue manager name exists and is valid, and then retry the command.

AMQ7709 DMPMQLOG command has used an invalid combination of options.

Explanation: You started the DMPMQLOG command specifying a combination of the options -b (base LSN option), -s (start LSN option) and -n (extent number option) that is not valid. Only 1 or none of these options may be specified.
User 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.

Explanation: You started the DMPMQLOG command specifying option -n (extent number option). This is not valid when the MQ log is defined as circular.
User 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.

Explanation: Tthe DMPMQLOG command was started specifying option -m (queue manager name option) with a value that is more than &1 characters.
User 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.

Explanation: You started the DMPMQLOG command specifying option -f (log file path option) with a value which is more than &1 characters.
User Response: Specify a shorter log file path name and then try the command again.

AMQ7713 DMPMQLOG command was unable to allocate sufficient storage.

Explanation: The DMPMQLOG command has been unable to allocate some storage.
User Response: Free some storage and then retry the command.

AMQ7714 DMPMQLOG command has reached the end of the log.

Explanation: The DMPMQLOG command has processed any log data and has now reached the end of the log.
User Response: None.

AMQ7715 DMPMQLOG command cannot open file '&3'.

Explanation: The DMPMQLOG command was unable to open file '&3' for reading.
User 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.

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.
User Response: Refer to the previous message issued by the command.

AMQ7717 DMPMQLOG command has failed to initialize: CompCode = 0x&1.

Explanation: The DMPMQLOG command has failed during its initialization and the MQ recording routine has been called. The error can occur if the queue manager is still running. The completion code can be used to identify the error.
User Response: Check that the queue manager being used by DMPMQLOG, as specified 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 the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ7718 DMPMQLOG command is using a default of '&3' for the queue manager name.

Explanation: You have started the DMPMQLOG command without specifying option -m (queue manager name option). A default value of '&3' is being used. This value is obtained from the default queue manager name.
User Response: None.

AMQ7719 DMPMQLOG command is using a default of '&3' for the starting dump location.

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). A default value of '&3' is being used. This value is the Log Sequence Number (LSN) of the first record in the active part of the log, and will be used as the location from which to start dumping.
User Response: None.

AMQ7720 DMPMQLOG command is using extent '&1' but the current extent is '&2'.

Explanation: You have started the DMPMQLOG command specifying option -n (extent number option) with a value of '&1'. This value is greater than '&2', which represents the extent currently being used.
User 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 '&1'.

Explanation: During its normal processing, the DMPMQLOG command did not find any log records in this extent.
User Response: None.

AMQ7722 DMPMQLOG command cannot find the object catalogue for queue manager '&3'.

Explanation: The DMPMQLOG command is using the queue manager named '&3' but cannot find the manager's object catalogue file. This file should have been created at the time the queue manager was created.
User Response: Refer to the "System Management Guide" for a description of the location and name of the object catalogue 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).

Explanation: The DMPMQLOG command has been started with an LSN but it cannot be found in the log.
User Response: Check for an existing LSN and then try the command again.

AMQ7724 DMPMQLOG command cannot use the requested extent number.

Explanation: The DMPMQLOG command has been started with an extent number but it is beyond the end of the log.
User Response: Check for an existing extent number and then try the command again.

AMQ7725 DMPMQLOG command cannot find an old Log Sequence Number (LSN).

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.
User 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.

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.
User 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.

AMQ7806 Could not start WebSphere MQ web administration server: &1.

Explanation: An unsuccessful attempt was made to start the web administration server on port &1.
User 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 contact your service representative.

AMQ7807 WebSphere MQ web administration server running.

Explanation: WebSphere MQ web administration server running. Listening on port &4, root directory is &5.
User Response: No action is required.

AMQ7808 Internal run-time error in WebSphere MQ web administration: &4.

Explanation: WebSphere MQ web administration had the following internal run-time error: &4.
User Response: Check that: the product is installed correctly and that the required registry keys and values are correct. If the problem persists contact your service representative.

AMQ7809 MQSeries Publish/Subscribe web administration user limit reached.

Explanation: The maximum number of concurrent web administration users has been reached (&4).
User Response: Use the 'Web Administration Server' properties page in the Microsoft Management Console to increase the value of the web administration 'MaxClients' parameter.

AMQ7810 Failed to create class, reason code: &1.

Explanation: While trying to create class &3 on &4 error code &1 was encountered. The associated error message generated by the operating system is: &5
User Response: Check the system documentation to determine the course of action required to rectify the problem.

AMQ7880 Error code &1 starting &4/&3 WebSphere MQ service.

Explanation: The service was unable to start &4 or &3. The error message reported was as follows: &5
User Response: Use WebSphere MQ Services to investigate why the service could not begin. If recovery for this service is active, MQ will attempt to recover.

AMQ7881 Unable to stop &4/&3 WebSphere MQ service, return code &1.

Explanation: The WebSphere MQ service was unable to stop &4 or &3. The error message reported was as follows: &5
User Response: Use WebSphere MQ Services to investigate why the service could not be stopped.

AMQ7882 Attempting to recover &4/&3 WebSphere MQ service.

Explanation: The WebSphere MQ service has detected that &4 or &3 has failed, and is attempting to restart it.
User Response: No Action Required.

AMQ7883 &4/&3 WebSphere MQ service started from recovery.

Explanation: The WebSphere MQ service has successfully recovered &4 or &3.
User Response: No Action Required.

AMQ7884 Unable to recover &4/&3 WebSphere MQ service.

Explanation: The WebSphere MQ service has attempted to recover &4/&3, but all attempts have failed. There will be no more attempts to recover this service.
User Response: Use WebSphere MQ Services to investigate why the service failed and could not be restarted.

AMQ7885 Unable to delete queue manager &4, error &1.

Explanation: An attempt to delete queue manager &4 failed. WebSphere MQ returned error code &1: &5
User Response: Ensure that the queue manager name has been specified correctly, and try again.

AMQ7886 Unable to create queue manager &4.

Explanation: Queue manager &4 could not be created. WebSphere MQ returned error &1: &5
User Response: Check the error and application event logs to investigate the reason for the 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 contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ7890 Unable to open mapped file containing WebSphere MQ performance data.

Explanation: The WebSphere MQ extensible counter dll was unable to open a mapped file used to collect queue performance data. Your system could be running short on virtual memory.
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7891 Unable to create a mutex to access WebSphere MQ performance data.

Explanation: The WebSphere MQ extensible counter dll was unable to create a mutex required to synchronise collection of queue performance data
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7892 Unable to map to shared memory file containing WebSphere MQ performance data.

Explanation: The WebSphere MQ extensible counter dll was unable to map the shared memory file required for collection of queue performance data.
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7893 Unable to open "Performance" key for WebSphere MQ services. Status code: &1.

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.
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7894 Unable to read the "Performance\First Counter" value for WebSphere MQ services. Status code: &1.

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.
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7895 Unable to read the "Performance\First Help" value for WebSphere MQ services. Status code: &1.

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.
User Response: No action required. Performance statistics for MQ queues will not be displayed.

AMQ7901 The data-conversion exit &3 has not loaded.

Explanation: The data-conversion exit program, &3, failed to load. The internal function gave exception &4.
User Response: 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.

AMQ7903 The data-conversion exit &3 cannot be found.

Explanation: Message data conversion has been requested for a WebSphere MQ message with a user-defined format, but the necessary data-conversion exit program, &3, cannot be found. The internal function gave exception &4.
User Response: Check that the necessary data-conversion exit &3 exists.

AMQ7904 The data-conversion exit &3 cannot be found, or loaded.

Explanation: Message data conversion was requested for a WebSphere MQ message with a user-defined format, but the necessary data conversion exit program, &3, was not found, or loaded. The &4 function call gave a return code of &1.
User 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 to determine where the message originated.

AMQ7905 Unexpected exception &4 in data-conversion exit.

Explanation: The data-conversion exit program, &3, ended with an unexpected exception &4. The message has not been converted.
User Response: 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.

AMQ7907 Unexpected exception in data-conversion exit.

Explanation: The data-conversion exit routine, &3, ended with an unexpected exception. The message has not been converted.
User Response: Correct the error in the data-conversion exit routine.

AMQ7911 The default Active Directory could not be located on your domain.

Explanation: No domain controllers with Active Directories could be found on the domain that your computer is a member of.
User Response: Active Directory support for MQ client connections cannot be used without a default Active Directory available on your domain.

AMQ7912 The Active Directory support library failed to initialize.

Explanation: WebSphere MQ support libraries for Active Directory client connections could not be initialized.
User Response: Check that the Active Directory client pre-requisite software has been installed on your machine before attempting to use this feature.

AMQ7913 The WebSphere MQ Active Directory container could not be created.

Explanation: WebSphere MQ has failed to create an IBM-MQClientConnections container as a child of your domain's system container in the Active Directory.
User Response: Ensure that you have permission to create sub-containers of the system container, and modify the otherWellKnownObjects property of the system container.

AMQ7914 Migration of the client connection table for Queue Manager &3 failed with reason code &1.

Explanation: The client connection table for this Queue Manager could not be migrated at this time.
User 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 Created service connection point for connection &3.

Explanation: The service connection point was successfully created for this client connection.
User Response: None.

AMQ7916 The Active Directory channel definition table could not be opened.

Explanation: The IBM-MQClientConnections Active Directory container could not be located in the Global Catalog.
User 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.

AMQ7918 The WebSphere MQ Active Directory container could not be deleted.

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.
User Response: None.

AMQ7921 An incorrect eye-catcher field in an MQDXP structure has been detected.

Explanation: The MQDXP structure passed to the Internal Formats Conversion routine contains an incorrect eye-catcher field.
User Response: 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.

AMQ7922 A PCF message is incomplete.

Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because the message is only &1 bytes long and does not contain a PCF header. The message has either been truncated, or it contains data that is not valid.
User 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 - &1.

Explanation: Message data conversion cannot convert a message because the integer encoding value of the message, &1, was not recognized.
User 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 = &1).

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.
User 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 &1 is not supported.

Explanation: Message data conversion cannot convert a message because the Version field of the message contains an incorrect value.
User 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 &1.

Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because the parameter count field of the PCF header is incorrect.
User 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 &1 (type = &2).

Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect type field.
User 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 &1 (length = &2).

Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contained an incorrect length field.
User 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.

Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number &1, of Type value &2, within the message is incomplete. The message has either been truncated, or it contains data that is not valid.
User 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 &1 (CCSID = &2).

Explanation: A Programmable Command Format (PCF) structure passed to the Internal Formats Converter contains an incorrect CCSID.
User 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 &1 (length = &2).

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.
User 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 &1 (count = &2).

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.
User 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.

Explanation: Message data conversion cannot convert a message in Programmable Command Format (PCF) because structure number &1 of the message contains an incorrect string length value &2.
User 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.

Explanation: Message data conversion could not convert a message in Programmable Command Format (PCF) because structure &1 of the message contained a CodedCharSetId field of MQCCSI_DEFAULT while the message itself had a CodedCharSetId of MQCCSI_EMBEDDED. This is an incorrect combination.
User 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 = &1).

Explanation: Message data conversion could not convert a message because the Message Descriptor of the message contained an incorrect CodedCharSetId field.
User 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 &3 already exists.

Explanation: The output file already exists, but REPLACE has not been specified.
User Response: Specify REPLACE to over-write the existing file, or select a different output file name.

AMQ7937 Structure length &1 in MQFMT_IMS_VAR_STRING format message is not valid.

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.
User 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

Explanation: None.
User Response: None.

AMQ7953 One structure has been parsed.

Explanation: The crtmqcvx command has parsed one structure.
User Response: None.

AMQ7954 &1 structures have been parsed.

Explanation: The crtmqcvx command has parsed &1 structures.
User Response: None.

AMQ7955 Unexpected field: &1.

Explanation: The field within the structure is of a type that is not recognized.
User Response: Correct the field and retry the command.

AMQ7956 Bad array dimension.

Explanation: An array field of the structure has an incorrect dimension value.
User Response: Correct the field and retry the command.

AMQ7957 Warning at line &1.

Explanation: The structure contains another field after a variable length field. A variable length field must be the last field of the structure.
User Response: Correct the structure and retry the command.

AMQ7958 Error at line &1 in field &3.

Explanation: Field name '&3' is a field of type 'float'. Fields of type float are not supported by this command.
User 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 &1 in field &3.

Explanation: Field name '&3' is a field of type 'double'. Fields of type double are not supported by this command.
User 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 &1 in field &3.

Explanation: Field name '&3' is a 'pointer' field. Fields of type pointer are not supported by this command.
User 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 &1 in field &3.

Explanation: Field name '&3' is a 'bit' field. Bit fields are not supported by this command.
User 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.

Explanation: This command requires that an input file is specified.
User Response: Specify the name of the input file and retry the command.

AMQ7963 No output file specified.

Explanation: This command requires that an output file name is specified.
User Response: Specify the name of the output file and retry the command.

AMQ7964 Unexpected option &3.

Explanation: The option specified is not valid for this command.
User Response: Retry the command with a valid option.

AMQ7965 Incorrect number of arguments.

Explanation: The command was passed an incorrect number of arguments.
User Response: Retry the command, passing it the correct number of arguments.

AMQ7968 Cannot open file '&3'.

Explanation: You cannot open the file &3.
User Response: Check that you have the correct authorization to the file and retry the command.

AMQ7969 Syntax error.

Explanation: This line of the input file contains a language syntax error.
User Response: Correct the syntax error and retry the command.

AMQ7970 Syntax error on line &1.

Explanation: This message identifies where, in the input file, a previously reported error was detected.
User Response: Correct the error and retry the command.



--------------------------------------------------------------------------------

© IBM Corporation 1997, 2002. All Rights Reserved

Get my WebSphere MQ course here >> http://www.themiddlewareshop.com/products/


Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories