An attempt to start the storage monitor process (job QMQM in subsystem QSYSWRK) was unsuccessful.
Response
Check the joblog for this job and for the QMQM job for possible reasons for failure, correct the error and try the command again. If the problem is not resolved, a problem may have been logged. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Save any generated output files and use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6007S
IBM MQ has not been initialized.
Severity
40 : Severe
Explanation
The MQ command cannot continue processing because it is not in an initialized state.
Response
Refer to previous messages issued by the command, the MQ error logs or any FFST files for further details.
AMQ6015E
The operating system is either too busy or has insufficient resources to complete a system request.
Severity
30 : Error
Explanation
A system request <insert_3> was rejected by the operating system with return code <insert_1>. IBM MQ retried the request, but it continued to fail. This failure may indicate that the operating system is either too busy or has insufficient resources to complete the request.
Response
Investigate whether the system is constrained by the workload on this system or by the workload on a server that it is using, and reduce the workload.
AMQ6024E
Insufficient resources are available to complete a system request.
Severity
30 : Error
Explanation
A system request was rejected by the operating system because insufficient resources are available to complete the request. Use any previous FFSTs, error log messages or, on Windows, system event log messages, to determine which resource is insufficient.
Response
Investigate whether the system has been configured in accordance with the documentation and increase the necessary resource to allow the system request to complete successfully.
AMQ6025E
Program not found.
Severity
30 : Error
Explanation
IBM MQ is unable to start program <insert_3> because it was not found.
Response
Check the program name is correctly specified and rerun the program.
AMQ6026E
A resource shortage prevented the creation of a IBM MQ process.
Severity
30 : Error
Explanation
An attempt to create an MQ process was rejected by the operating system due to a process limit (either the number of processes for each user or the total number of processes running system wide), or because the system does not have the resources necessary to create another process.
Response
Investigate whether a process limit is preventing the creation of the process and if so why the system is constrained in this way. Consider raising this limit or reducing the workload on the system.
AMQ6035E
IBM MQ failed, no storage available.
Severity
30 : Error
Explanation
An internal function of the product attempted to obtain storage, but there was none available.
The product is unable to obtain enough storage. The product's error recording routine may have been called.
Response
Stop the product and restart it. If this does not resolve the problem see if a problem has been recorded. If a problem has been recorded, use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6047E
Conversion not supported.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data tagged in CCSID <insert_1> to data in CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6047E (AIX)
Conversion not supported.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data tagged in CCSID <insert_1> to data in CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
If at least one of the CCSIDs is a Unicode CCSID then check that the bos.iconv.ucs.* operating system filesets have been installed on the system.
AMQ6048E
DBCS error
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data due to a DBCS error. Conversion is from CCSID <insert_1> to CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6049E
DBCS-only string not valid.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>. Message descriptor data must be in single-byte form. CCSID <insert_2> is a DBCS-only CCSID.
Response
Check the CCSID of our job or system and change it to one supporting SBCS or mixed character sets. Refer to the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications for character sets and CCSIDs supported.
AMQ6050E
CCSID error.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6051E
Conversion length error.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>, due to an input length error.
AMQ6052E
CCSID <insert_1> could not be converted to locale CCSID <insert_2>.
Severity
30 : Error
Explanation
IBM MQ could not convert CCSID <insert_1> characters to the locale CCSID <insert_2>. The <insert_2> CCSID was obtained from the locale. You will need to run this program from an environment in which the locale is altered to give a character set that can be converted to/from CCSID <insert_1>.
Response
On Windows, we can use the chcp command to change the codepage in the command prompt where we are running. On Linux, UNIX or IBM i platforms, we can use the LANG environment variable.
AMQ6053E
CCSID error
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>.
Response
One of the CCSIDs is not supported by the system. Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6064S
An internal IBM MQ error has occurred.
Severity
40 : Severe
Explanation
An error has been detected, and the MQ error recording routine has been called.
An attempt to display an error message was unsuccessful. This may be because the AMQMSG message file could not be found. The message identifier is <insert_3>.
Response
Check that the library list is set up correctly to access the AMQMSG message file. If a change is necessary, rerun the failing application and record the error message. If we are unable to resolve the problem, save any generated output files and use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center.
AMQ6090I
IBM MQ was unable to display an error message <insert_6>.
Severity
0 : Informational
Explanation
MQ has attempted to display the message associated with return code hexadecimal <insert_6>. The return code indicates that there is no message text associated with the message. Associated with the request are inserts <insert_1> : <insert_2> : <insert_3> : <insert_4> : <insert_5>.
CCSID <insert_1> exists in new format but could not be reconciled against your old format.
Response
Manually edit CCSID entry <insert_1> in conv\table\ccsid.tbl if you wish to retain your old conversion. For assistance call your Service Representative.
AMQ6103E (IBM i)
IBM MQ job submission error.
Severity
30 : Error
Explanation
IBM MQ is unable to submit job <insert_3>.
AMQ6107S
CCSID not supported.
Severity
40 : Severe
Explanation
IBM MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>, because one of the CCSIDs is not recognized.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6109S
An internal IBM MQ error has occurred.
Severity
40 : Severe
Explanation
An error has been detected, and the MQ error recording routine has been called.
When initializing IBM MQ, no valid job CCSID was found, so the CCSID used is the default 37. This warning message will be issued until a valid CCSID has been set correctly.
Response
Set the job CCSID.
AMQ6114E (IBM i)
An internal IBM MQ error has occurred.
Severity
30 : Error
Explanation
An error has been detected, and the MQ error recording routine has been called.
An error has been detected, and the MQ error recording routine has been called.
Response
MQ has detected a parameter count of <insert_1> that is not valid. Use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6122E
An internal IBM MQ error has occurred.
Severity
30 : Error
Explanation
An error has been detected, and the MQ error recording routine has been called.
Response
MQ has detected parameter <insert_1> that is not valid, having value <insert_2><insert_3>. Use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6125E
An internal IBM MQ error has occurred.
Severity
30 : Error
Explanation
An internal error has occurred with identifier <insert_1>. This message is issued in association with other messages.
An unexpected error was reported by the operating system whilst reading or writing data. The cause of this error cannot be determined by IBM MQ and an FFST has been produced. Check the logs for both MQ and the operating system for further information. If this error has occurred whilst accessing a filesystem, use operating system tools to check and if appropriate correct the integrity of the filesystem. If the I/O error has occurred for a networked filesystem, for example NFSv4, check that both client and server meet the minimum requirements required by IBM MQ and that they have the latest level of service applied.
AMQ6150E (IBM i)
IBM MQ resource <insert_3> busy.
Severity
30 : Error
Explanation
MQ was unable to access an MQ object within the normal timeout period of <insert_1> minutes.
Response
MQ will continue to wait for access. Ensure that all jobs using MQ are released. If the situation persists, quiesce the queue manager.
AMQ6150W (Windows)
IBM MQ semaphore is busy.
Severity
10 : Warning
Explanation
IBM MQ was unable to acquire a semaphore within the normal timeout period of <insert_1> minutes.
Response
MQ will continue to wait for access. If the situation does not resolve itself and you suspect that the system is locked then investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST.
AMQ6151E (IBM i)
IBM MQ resource <insert_3> released.
Severity
30 : Error
Explanation
An MQ resource, for which another process has been waiting, for a period of over <insert_1> minutes has been released.
Response
No recovery is needed.
AMQ6152E (IBM i)
IBM MQ failed to end commitment control while attempting to quiesce a queue manager.
Severity
30 : Error
Explanation
IBM MQ failed to end commitment control whilst quiescing queue manager <insert_3>.
Response
There are one or more active resources under commitment control. Use the Work with Job (WRKJOB) command with the OPTION(*CMTCTL) parameter to display the active resources under commitment control. Check the job log for previously issued messages.
AMQ6153E (IBM i)
The attempt to quiesce queue manager <insert_3> failed
Severity
30 : Error
Explanation
The attempt to quiesce queue manager <insert_3> was unsuccessful
Response
Check the job log for previously issued messages. If the quiesce was issued with the *CNTRLD option, re-issue the command with the *IMMED option. If a low TIMEOUT retry delay was used, re-issue the request with a higher value.
AMQ6154I (IBM i)
Queue manager <insert_3> has been quiesced.
Severity
0 : Informational
Explanation
The queue manager has been successfully quiesced.
Response
None.
AMQ6158E (IBM i)
SBCS CCSID not found.
Severity
30 : Error
Explanation
IBM MQ is unable to find an SBCS CCSID which corresponds to mixed DBCS-SBCS CCSID <insert_1>.
Response
Check the CCSID of our job or system and check it has a SBCS equivalent. Refer to the National Language Support Planning Guide for character sets and CCSIDs supported. If the CCSID used does have an SBCS equivalent, save the job log containing this message and use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center.
AMQ6159E (IBM i)
IBM MQ job submission error.
Severity
30 : Error
Explanation
IBM MQ for IBM i is unable to release job <insert_3>.
Response
Contact you System Administrator to remove job <insert_3>. Ensure you have *JOBCTL authority and try again.
AMQ6160I
EXPLANATION:
Severity
0 : Informational
AMQ6161I
ACTION:
Severity
0 : Informational
AMQ6162E
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 we have been changing the INI file content check and correct the change. If we have not changed the INI file, use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6162E (Windows)
An error occurred when reading the configuration data.
Severity
20 : Error
Explanation
An error has occurred when reading the configuration data.
Response
If we have changed the configuration data, check and correct the change. If we have not changed the configuration data, use the standard facilities supplied with the system to record the problem identifier, and to save the generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6163W
An error has occurred locking an INI file.
Severity
10 : Warning
Explanation
An error has occurred locking the MQS.INI file or a queue manager QM.INI file.
Response
If we have been changing the INI file permissions check and correct the change. If we have not changed the INI file, use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6163W (Windows)
An error has occurred locking the configuration data.
Severity
10 : Warning
Explanation
An error has occurred locking the configuration data.
Response
If we have changed the the registry permissions, check and correct the change. If we have not changed the registry, use the standard facilities supplied with the system to record the problem identifier, and to save the generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6164W
An expected stanza in an INI file is missing or contains errors.
Severity
10 : Warning
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 we have been changing the INI file content check and correct the change.
AMQ6164W (Windows)
An expected stanza in the configuration data is missing or contains errors.
Severity
10 : Warning
Explanation
An expected stanza is missing from the configuration data or the stanza contains errors.
Response
If we have changed the configuration data, check and correct the change.
AMQ6165W
Permission denied attempting to access an INI file.
Severity
10 : Warning
Explanation
Access to the MQS.INI file or a queue manager QM.INI file is denied.
Response
If we have been changing the INI file permissions check and correct the change.
AMQ6165W (Windows)
Unable to access the configuration data.
Severity
10 : Warning
Explanation
Access to the configuration data is denied.
Response
If we have changed the configuration data permissions, check and correct the changes.
AMQ6166E
An INI file is missing.
Severity
20 : Error
Explanation
The MQS.INI file or a queue manager QM.INI file is missing.
Response
If we have been changing the INI file recover the previous file and retry the operation.
AMQ6166E (Windows)
An entry in the configuration data is missing.
Severity
20 : Error
Explanation
A required entry in the configuration data is missing.
Response
If we have changed the configuration data, recover the previous configuration data and retry the operation.
AMQ6172E
No codeset found for current locale.
Severity
20 : Error
Explanation
No codeset could be determined for the current locale. Check that the locale in use is supported.
Response
None.
AMQ6173E
No CCSID found for codeset <insert_3>.
Severity
20 : Error
Explanation
Codeset <insert_3>. has no supported CCSID. Check that the locale in use is supported. CCSIDs can be added by updating the file <insert_4>.
Response
None.
AMQ6174I
The library <insert_3> could not be loaded.
Severity
0 : Informational
Explanation
The dynamically loadable library <insert_3> could not be loaded. Possible reasons for the error:
(a) Library is not present in the specified path.
(b) Library is present but the architecture of the library does not match the process's architecture which is <insert_5> bit.
(c) Library is present but it has a dependency on other libraries which are not present in the same directory.
Response
Check that the file exists and is either fully qualified or is in the appropriate directory. Check the architecture of the library and process match. Also check if the library has dependency on any other libraries.
AMQ6174I (IBM i)
The library could not be loaded.
Severity
0 : Informational
Explanation
The dynamically loadable file <insert_3> could not be loaded.
Response
Check that the file exists and is either fully qualified or is in the appropriate library.
AMQ6174I (UNIX and Linux)
The dynamically loadable shared library <insert_3> could not be loaded. The system returned error number <insert_2> and error message <insert_4>.
Severity
0 : Informational
Explanation
This message applies to UNIX systems. The shared library <insert_3> could not be loaded.
Response
Check that the file exists, and is either fully qualified or is in the appropriate director, also check the file access permissions.
AMQ6175E (AIX)
The system could not dynamically load the shared library <insert_3>. The system returned error number <insert_2> and error message <insert_4>.
Severity
20 : Error
Explanation
This message applies to AIX systems. The shared library <insert_3> failed to load correctly due to a problem with the library.
Response
Check the file access permissions and that the file has not been corrupted.
AMQ6175E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>. The system returned error message <insert_4>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load correctly due to a problem with the library.
Response
Check the file access permissions and that the file has not been corrupted.
AMQ6175E (Windows)
The system could not dynamically load the library <insert_3>. The system returned error message <insert_4>.
Severity
20 : Error
Explanation
This message applies to Windows systems only. The dynamically loadable file <insert_3> failed to load correctly due to an internal error. The MQ error recording routine has been called.
Response
Check that the file has not been corrupted then use the standard facilities supplied with the system to record the problem identifier, and to save the generated output files. Use either the IBM MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6177E (Windows)
An internal IBM MQ error has occurred.
Severity
30 : Error
Explanation
An error has been detected, and the MQ error recording routine has been called.
Response
Details of the error have been stored at <insert_3>. A synopsis is given in the data section below. Use the standard facilities supplied with the system to record the problem identifier, and to save the generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6179E
The system could not find symbol <insert_5> in the dynamically loaded library <insert_3>. The system returned error number <insert_2> and error message <insert_4>.
Severity
20 : Error
Explanation
The library <insert_3> does not contain symbol <insert_5> or it has not been exported.
Response
Check that symbol name <insert_5> is correct and has been exported from the library.
AMQ6179E (UNIX and Linux)
The system could not find the symbol <insert_5> in the dynamically loaded shared library <insert_3>. The system returned error message <insert_4>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> does not contain symbol <insert_5> or it has not been exported.
Response
Check that symbol name <insert_5> is correct and has been exported from the library.
AMQ6180E (Windows)
Default conversion not supported.
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data tagged in CCSID <insert_1> to data in CCSID <insert_2>.
Response
Check the default CCSIDs specified in the ccsid.tbl file and make sure that conversion is supported between these CCSIDs.
AMQ6182E
Error found in line <insert_1> of <insert_4>
Severity
30 : Error
Explanation
Line <insert_1> of <insert_4> contains an error. The content of the line is <insert_3>. Processing continues but the line in error is ignored.
Response
Correct the line and rerun the program or command giving this message.
AMQ6183W
An internal IBM MQ error has occurred.
Severity
10 : Warning
Explanation
An error has been detected, and the IBM MQ error recording routine has been called. The failing process is process <insert_1>.
An internal MQ error has occurred on queue manager <insert_3> and the MQ error recording routine has been called. The failing process is process <insert_1>.
User is not authorized for RestrictedMode queue manager.
Severity
30 : Error
Explanation
All users must be in the RestrictedMode application_group.
AMQ6188E (AIX)
The system could not dynamically load the shared library <insert_3> as the entry point to the library, symbol 'MQStart', could not be located within the library. The queue manager will continue without this library.
Severity
20 : Error
Explanation
This message applies to AIX systems. The shared library <insert_3> failed to load correctly due to a problem with the library.
Response
Check that the entry point to the library, symbol 'MQStart', exists and has been exported from the library.
AMQ6188E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3> as the entry point to the library, symbol 'MQStart', could not be located within the library. The system returned error message <insert_4>. The queue manager will continue without this library.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load correctly due to a problem with the library.
Response
Check that the entry point to the library, symbol 'MQStart', exists and has been exported from the library.
AMQ6188E (Windows)
The system could not dynamically load the library <insert_3> due to a problem with the dll. The errno was <insert_2>. The queue manager will continue without this module.
Severity
20 : Error
Explanation
This message applies to Windows systems only. The dynamically loadable file <insert_3> failed to load correctly due to a problem with the dll.
Response
Check that the dll is in the correct place with the correct file permissions etc. and has not been corrupted.
AMQ6190E (Windows)
Program <insert_3> not found.
Severity
30 : Error
Explanation
The program <insert_3> cannot be found.
Response
Check that the program specified is available on the system. If the program name is not fully qualified, ensure that the PATH environment variable includes the directory where the program is located.
AMQ6191E (Windows)
Program <insert_3> failed to start, return code <insert_1>.
Severity
30 : Error
Explanation
The program <insert_3> was invoked, but failed to start. The failure reason code is <insert_1>.
Response
Check that the program specified is available on the system, and that sufficient system resources are available. Where applicable, verify that the user is authorized to run the program.
AMQ6192I (Windows)
IBM IBM MQ Utilities
Severity
0 : Informational
AMQ6193E (Windows)
The registry entry <insert_3> was not found.
Severity
20 : Error
Explanation
IBM MQ for Windows sets the registry entry <insert_3> when the product is installed, but the entry is now missing.
Response
If the registry has been edited, restore the previous version. If the product is newly installed, check whether the installation was successful, and reinstall the product if necessary.
AMQ6196E
An error has occurred whilst processing a temporary INI file <insert_3>
Severity
20 : Error
Explanation
An error has occurred when creating a backup of an INI file. The backup file <insert_4> already exists
Response
You may have created a backup of the INI file with the name <insert_4>, or an earlier operation may have failed. Move or delete the file <insert_4> and reattempt the operation. If we have not changed the INI file, use the standard facilities supplied with the system to record the problem identifier and to save any generated output files. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.
AMQ6207E (AIX)
Failed to attach shared memory segment as Segment table is Full.
Severity
20 : Error
Explanation
IBM MQ has attempted to attach a memory segment but was unable to do so because all available segment areas are in use. 32 bit programs on AIX may attach up to a maximum of 10 shared memory segments. If the application has modified the data area layout, for example by reserving more of the address space for the program heap, this maximum number may be further reduced.
Response
Examine the needs of the application to see if the number of attached segments can be reduced. Alternatively by building the application as a 64bit program the limit of 10 shared memory segments is removed.
AMQ6208I
<insert_3>
Severity
0 : Informational
Explanation
<insert_4>
Response
<insert_5>
AMQ6209W
An unexpected asynchronous signal (<insert_1> : <insert_3>) has been received and ignored.
Severity
10 : Warning
Explanation
Process <insert_2> received an unexpected asynchronous signal and ignored it. This has not caused an error but the source of the signal should be determined as it is likely that the signal has been generated externally to IBM MQ.
Response
Determine the source of the signal and prevent it from re-occurring.
AMQ6212E
Failed to load Library <insert_3> as C++ environment is not initialised.
Severity
20 : Error
Explanation
An attempt was made to load the identified C++ shared library. However, the attempt failed because the C++ environment has not been initialized for the current process.
Response
Ensure the application is linked with the appropriate C++ runtime environment.
AMQ6218E (AIX)
EXTSHM variable detected with unrecognised value <insert_3> and has been reset to <insert_4>.
Severity
20 : Error
Explanation
Processes that access the internal queue manager control blocks must use the AIX Extended Shared Memory model, and while one such process was starting, IBM MQ detected that the EXTSHM variable was set but did not contain an appropriate value. This value has been reset and the process will continue with the new setting.
Response
No further action is required. To prevent this message being issued in future, correct the value of the EXTSHM variable in the environment.
AMQ6230W
Message <insert_3> suppressed <insert_1> times in the last <insert_4> seconds.
Severity
10 : Warning
Explanation
Message <insert_3> was issued <insert_2> times in the last <insert_4> seconds but only the first instance of the message was written to the log. The suppressed messages may have included differing message arguments.
Response
If you wish to see all occurrences of this message we should alter the definition of the SuppressMessage attribute in the queue manager configuration.
AMQ6231I (HP NSS)
Usage: amqicdir <insert_-s> [-a] [-f] [-i]
Severity
0 : Informational
Explanation
An incorrect option was specified on the command line for the command.
s Check SYSTEM directories
a Check all directories
f Fix errors
i Run install-time checking
Response
Reissue the command specifying the correct parameters.
AMQ6231I (Windows)
Usage: amqicdir <insert_-a | -i | -m QMgrName | -s> [-f]
-a Check all directories.
-f Fix errors.
-i Run install-time checking.
-m Check directories for the specified queue manager.
-s Check the system-wide directories.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6232E (UNIX and Linux)
Operate System userid <insert_3> not found.
Severity
20 : Error
Explanation
A request was made to the operating system to lookup the details of the identified userid but the request failed.
Response
Using the operating system supplied tools check for the existence of the identified userid, and if missing then recreate it.
AMQ6233E (UNIX and Linux)
Operate System authorisation group <insert_3> not found.
Severity
20 : Error
Explanation
A request was made to the operating system to lookup the details of the identified group but the request failed.
Response
Using the operating system supplied tools check for the existence of the identified group, and if missing then recreate it.
AMQ6234E (Windows)
Unknown queue manager name specified.
Severity
20 : Error
Explanation
An invalid queue manager name <insert_3> was specified in the parameters to the command.
Response
Reissue the command specifying a valid queue manager name.
AMQ6235E (UNIX and Linux)
Directory <insert_3> missing.
Severity
20 : Error
Explanation
The identified directory is missing.
Response
Reissue the command selecting the option to create missing directories.
AMQ6235E (Windows)
Directory <insert_3> missing.
Severity
20 : Error
Explanation
The identified directory is missing.
Response
Reissue the command selecting the option to create missing directories.
AMQ6236E (UNIX and Linux)
Missing directory <insert_3> has been created.
Severity
20 : Error
Explanation
The identified directory was missing but has been created.
Response
None
AMQ6236E (Windows)
Missing directory <insert_3> has been created.
Severity
20 : Error
Explanation
The identified directory was missing but has been created.
Response
None
AMQ6237E (UNIX and Linux)
File <insert_3> missing.
Severity
20 : Error
Explanation
The identified file is missing.
Response
Reissue the command selecting the option to create missing files.
AMQ6237E (Windows)
File <insert_3> missing.
Severity
20 : Error
Explanation
The identified file is missing.
Response
Reissue the command selecting the option to create missing files.
AMQ6238E (UNIX and Linux)
Missing file <insert_3> has been created.
Severity
20 : Error
Explanation
The identified file was missing but has been created.
Response
None
AMQ6239E (UNIX and Linux)
Permission denied attempting to access filesystem location <insert_3>.
Severity
20 : Error
Explanation
An attempt to query the filesystem object identified failed because the command issued did not have authority to access the object.
Response
Check the authority on the object and of the user executing the command and reissue the command.
AMQ6239E (Windows)
Permission denied attempting to access filesystem location <insert_3>.
Severity
20 : Error
Explanation
An attempt to query the filesystem object identified failed because the command issued did not have authority to access the object.
Response
Check the authority on the object and of the user executing the command and reissue the command.
AMQ6240E (UNIX and Linux)
We must be an operating system superuser to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as a user with superuser privileges.
Response
Log in as an appropriate user and reissue the command.
AMQ6240E (Windows)
We must be an operating system administrator to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as a user with administrative privileges.
Response
Log in as an appropriate user and reissue the command.
AMQ6241W (UNIX and Linux)
The filesystem object <insert_3> is a symbolic link.
Severity
10 : Warning
Explanation
While checking the filesystem, an object was found which is a symbolic link.
Response
This is not an error however we should verify that the symbolic link is expected and that the destination of the symbolic link is correct.
AMQ6242E (UNIX and Linux)
Incorrect ownership for <insert_3>. Current(<insert_1>) Expected(<insert_2>)
Severity
20 : Error
Explanation
The filesystem object <insert_3> is owned by the user with uid <insert_1> when it was expected to be owned by the user with uid <insert_2>.
Response
Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect ownership.
AMQ6243E (UNIX and Linux)
Incorrect group ownership for <insert_3>. Current(<insert_1>) Expected(<insert_2>)
Severity
20 : Error
Explanation
The filesystem object <insert_3> is owned by the group with gid <insert_1> when it was expected to be owned by the group with gid <insert_2>.
Response
Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect ownership.
AMQ6244E (UNIX and Linux)
Incorrect permissions on object <insert_3>. Current(<insert_4>) Expected(<insert_5>)
Severity
20 : Error
Explanation
The filesystem object <insert_3> has the wrong file permissions.
Response
Correct the ownership using operating system commands or reissue the command selecting the option to fix the incorrect ownership.
AMQ6245E (UNIX and Linux)
Error executing system call <insert_3> on file <insert_4> error <insert_2>.
Severity
20 : Error
Explanation
The execution of the system call <insert_3> on file <insert_4> failed and the error code <insert_2> was returned.
Response
Investigate the cause of the failure using the operating system error code <insert_1> and reissue the command.
AMQ6245E (Windows)
Error executing system call <insert_3> on <insert_4> error <insert_2>.
Severity
20 : Error
Explanation
The execution of the system call <insert_3> on <insert_4> failed and the error code <insert_2> was returned.
Response
Investigate the cause of the failure using the operating system error code <insert_1> and reissue the command.
AMQ6251E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. Note that MQ tried to find a <insert_2>-bit library named either <insert_4> or <insert_5>, but failed. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit library.
AMQ6251E (Windows)
The system could not dynamically load the DLL <insert_3>. The queue manager will continue without this module.
Severity
20 : Error
Explanation
This message applies to Windows systems. The DLL <insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. Note that MQ tried to find a <insert_2>-bit DLL named either <insert_4> or <insert_5>, but failed. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit DLL.
AMQ6252E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. Note that MQ found and loaded a <insert_2>-bit library named <insert_4> however this also failed to load with the system returning error message <insert_5>. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit library.
AMQ6252E (Windows)
The system could not dynamically load the DLL <insert_3>.
Severity
20 : Error
Explanation
This message applies to Windows systems. The DLL <insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. Note that MQ found and loaded a <insert_2>-bit DLL named <insert_4> however this also failed to load with the system returning error message <insert_5>. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit DLL.
AMQ6253E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. Note that MQ attempted to locate and load a <insert_2>-bit library named either of these: <insert_4>. The first library failed to load as it also is probably a <insert_1>-bit library, the second library is a <insert_2>-bit library, however this also failed to load with the system returning error message <insert_5>. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit library.
AMQ6253E (Windows)
The system could not dynamically load the DLL <insert_3>.
Severity
20 : Error
Explanation
This message applies to Windows systems. The DLL <insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. Note that MQ attempted to locate and load a <insert_2>-bit DLL named either of these: <insert_4>. The first DLL failed to load as it also is probably a <insert_1>-bit DLL, the second DLL is a <insert_2>-bit DLL, however this also failed to load with the system returning error message <insert_5>. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit DLL.
AMQ6254I (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>, library <insert_4> has been used instead.
Severity
0 : Informational
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. Note that MQ has sucessfully located and loaded a <insert_2>-bit library named <insert_4>.
Response
Supply the name of a <insert_2>-bit library or put the library (alternatively a symbolic link can be used) in the appropriate place: 32-bit libraries in the ExitsDefaultPath; 64-bit libraries in the ExitsDefaultPath64.
AMQ6254I (Windows)
The system could not dynamically load the DLL <insert_3>, DLL <insert_4> has been used instead.
Severity
0 : Informational
Explanation
This message applies to Windows systems. The DLL <insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. Note that MQ has sucessfully located and loaded a <insert_2>-bit DLL named <insert_4>.
Response
Supply the name of a <insert_2>-bit DLL or put the DLL in the appropriate place: 32-bit libraries in the ExitsDefaultPath; 64-bit libraries in the ExitsDefaultPath64.
AMQ6255E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit library.
AMQ6255E (Windows)
The system could not dynamically load the DLL <insert_3>.
Severity
20 : Error
Explanation
This message applies to Windows systems. The DLL<insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit DLL.
AMQ6256E (UNIX and Linux)
The system could not dynamically load the shared library <insert_3>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. The shared library <insert_3> failed to load as it is probably a <insert_1>-bit library, a <insert_2>-bit library is required. Note that MQ tried to find a <insert_2>-bit library named <insert_4>, but failed. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit library.
AMQ6256E (Windows)
The system could not dynamically load the DLL <insert_3>.
Severity
20 : Error
Explanation
This message applies to Windows systems. The DLL <insert_3> failed to load as it is probably a <insert_1>-bit DLL, a <insert_2>-bit DLL is required. Note that MQ tried to find a <insert_2>-bit DLL named <insert_4>, but failed. The following message gives details of the original failure.
Response
Supply the name of a <insert_2>-bit DLL.
AMQ6257I
Message suppression enabled for message numbers (<insert_3>).
Severity
0 : Informational
Explanation
The message contains a list of message numbers for service <insert_4> from the configuration file <insert_5>, for which entries repeated within the <insert_1> suppression interval will be suppressed.
Response
If you wish to see all occurrences of these messages we should alter the definition of the SuppressMessage attribute in the queue manager configuration.
AMQ6258I
Message exclusion enabled for message numbers (<insert_3>).
Severity
0 : Informational
Explanation
The message contains a list of message numbers which have been excluded by service <insert_4> from the configuration file <insert_5>. Requests to write these messages to the error log will be discarded.
Response
If you wish to see instances of these messages we should alter the definition of the ExcludeMessage attribute in the queue manager configuration.
AMQ6259W
Message <insert_3> cannot be <insert_4>.
Severity
10 : Warning
Explanation
Message <insert_3> cannot be excluded or suppressed but was specified in the ExcludeMessage or SuppressMessage configuration for the queue manager. The queue manager will continue however the request to suppress or exclude this message will be ignored.
Response
Update the queue manager configuration to remove the specified message identifier.
AMQ6260W
Help Topic not found
Severity
10 : Warning
Explanation
The requested help topic could not be located.
For further assistance, please refer to the IBM MQ manuals.
Response
Ensure that the IBM MQ documentation is installed.
AMQ6261E (UNIX and Linux)
An exception occurred trying to dynamically load shared library <insert_3>.
Severity
20 : Error
Explanation
This message applies to UNIX systems. Exception number <insert_1> name <insert_4>, occurred trying to dynamically load shared library <insert_3>.
Response
Check the shared library has not been corrupted. If the shared library contains any initializer functions, ensure these are not causing the problem and that they conform to the expected function prototype.
AMQ6261E (Windows)
An exception occurred trying to load DLL <insert_3>.
Severity
20 : Error
Explanation
This message applies to Windows systems only. Exception number <insert_1> error <insert_4>, occurred trying to load DLL <insert_3>.
Response
Check the DLL has not been corrupted. If the DLL contains any initializer functions, ensure these are not causing the problem and that they conform to the expected function prototype.
The MQ common services module needs to access an area of named shared memory so that various functions, including trace, can be co-ordinated between all processes on a machine or session.
For a server install, this area should have been created by the MQ services process (amqsvc.exe) and is thus shared globally, on a client-only install, or where the MQ services are not running, it should be created for this session only.
This failure implies that the named shared memory (normally mqm.SHRSEG.0) has been created by another process on the system in such a way that access to it from MQ processes is denied.
Response
Investigate which process on the machine has created the named shared memory and, if it is an MQ process or MQ application investigate why the permissions have been set to disallow others to connect.
If the process that created this area is not related to MQ, investigate why it has created this specifically named area.
AMQ6271E
Detected 64-bit JVM, but not using a suitable adapter
Severity
30 : Error
Explanation
The specified adapter <insert_1> is not compatible with 64-bit operation
Response
Either specify an appropriate adapter with the com.ibm.mq.adapter system property, or do not use the property
AMQ6272E
com.ibm.mq.adapter set to <insert_0>, which is invalid
Severity
30 : Error
Explanation
The adapter is not valid in this environment
Response
Set the com.ibm.mq.adapter to a valid value
AMQ6276W
group name <insert_3> size <insert_1> is too long to be used for <insert_4>.
Severity
10 : Warning
Explanation
<insert_4> has not been authorised for use by the groupname <insert_3>. This will not affect users who are members of group mqm.
The user provided an incorrect set of argumenmts to the amqxdbg command.
-i - Request a program FDC from the process identified by 'pid' and 'tid'.
-p - Request a program FDC from the process identified by the supplied program name. To match more than one program name the wildcard character '*' may be used at the end of the 'program_name' specification.
-x - Delete the entry identified by the -i or -p parameters
-s - Show the status of debug entries
Response
Re-issue the command using the appropriate arguments.
The user provided an incorrect set of argumenmts to the amqxdbg command.
-i - Request a program FDC from the process identified by 'pid' and 'tid'.
-p - Request a program FDC from the process identified by the supplied program name. To match more than one program name the wildcard character '*' may be used at the end of the 'program_name' specification.
-x - Delete the entry identified by the -i or -p parameters
-s - Show the status of debug entries
-t - Request a program FDC from the process identified by 'pid' by starting a remote thread in the identified process.
Response
Re-issue the command using the appropriate arguments.
AMQ6281I
Debug entry defined.
Severity
0 : Informational
Explanation
The amqxdbg command completed successfully and a debug entry was added.
Response
None
AMQ6282I
Debug entry removed.
Severity
0 : Informational
Explanation
The amqxdbg command completed successfully and a debug entry was removed.
Response
None
AMQ6283E
Debug entry not found.
Severity
20 : Error
Explanation
The debug entry identified was not found and could not removed.
Response
None
AMQ6284E
Debug entry could not be defined. The limit on the number of entries has been reached.
Severity
20 : Error
Explanation
The amqxdbg command attempted to add a debug entry but could not becuase the limit on the number of entries which can be defined was reached.
Response
Use the '-x' option to remove debug entries which are no longer required and re-issue the command.
AMQ6285E
Process <insert_1> does not exist.
Severity
20 : Error
Explanation
The amqxdbg command attempted to add a debug entry but could not because the process with process identifier <insert_1> is not running.
Response
Check the supplied process identifier and re-issue the command.
AMQ6286E
The filesystem at location <insert_3> is read-only.
Severity
20 : Error
Explanation
An attempt to write to the filesystem failed because it is read-only. Likely causes are that you specified the location incorrectly or the filesystem has been incorrectly configured.
Response
Identify where the location was specified and check it is correct. Check that the filesystem has been configured correctly.
AMQ6287I
IBM MQ V<insert_5>.
Severity
0 : Informational
Explanation
IBM MQ system information:
Host Info :- <insert_3>
Installation :- <insert_4>
Version :- <insert_5>
Response
None.
AMQ6290E
Unknown installation <insert_3> detected.
Severity
20 : Error
Explanation
When executing program <insert_4>, IBM MQ detected that, due to the configuration of the environment, resources were loaded from <insert_3>. MQ could not determine the installation name for these resources. The program cannot complete successfully while the program is executing using resources from an unknown installation.
Response
Configure the environment so that all resources required by program <insert_4> are loaded from an correctly installed installation.
AMQ6290E (UNIX and Linux)
Unknown installation path <insert_3> detected.
Severity
20 : Error
Explanation
When executing program <insert_4>, MQ detected that its resources were loaded from <insert_3>, MQ could not determine from <insert_5> the installation name and identifier for these resources. The program cannot complete successfully while the program is executing using resources from an unknown installation.
Response
Check that <insert_5> exists and has an Installation entry with 'Path=<insert_3>. If <insert_5> has been corrupted, run "crtmqinst -r" to reconstruct the file.
AMQ6291E
Error <insert_1> occurred during IBM MQ process initialization.
Severity
20 : Error
Explanation
An unexpected error was encountered while initializing the process. The process will terminate immediately. The error was <insert_1>. The MQ error recording routine may have been called.
The queue manager is associated with a different installation.
Severity
20 : Error
Explanation
A command was issued which attempted to connect to a queue manager, but the installation that the command was issued from does not match the installation that the queue manager is associated with. The attempt to connect failed.
Response
Reissue the command from the installation that the queue manager is associated with.
AMQ6293E
Cannot create symbolic link as a file with the name <insert_3> already exists. Error Number: <insert_1>.
Severity
20 : Error
Explanation
An attempt was made to create a symbolic link with the name <insert_3> but the symbolic link could not be created as a file already exists with the same name.
Response
Verify if the file named <insert_3> has been created in error. If so, remove before reissuing the command. The Error Number may give more details about the cause of the failure.
AMQ6294E
Failed to create symbolic link with the name <insert_3>. Error Number: <insert_1>
Severity
20 : Error
Explanation
An attempt was made to create a symbolic link with the name <insert_3> but the symbolic link could not be created.
Response
The Error Number for the failure may give details about why the symbolic link could not be created. Correct the problem before reissuing the command.
AMQ6295E
Unable to remove symbolic link with the name <insert_3>. Error Number: <insert_1>
Severity
20 : Error
Explanation
An attempt was made to remove a symbolic link with the name <insert_3> but the symbolic link could not be removed.
Response
The Error Number for the failure may give details about why the symbolic link could not be removed. Correct the problem before reissuing the command.
AMQ6296E
Cannot remove file <insert_3> as it is not a symbolic link.
Severity
20 : Error
Explanation
An attempt was made to remove a symbolic link with the name <insert_3> but it was not removed because the file was not a symbolic link.
Response
Check the definition of the symbolic link and, if incorrect, remove the file before reissuing the command.
AMQ6297E
Symbolic link with the name <insert_3> cannot be removed. Target <insert_4> does not match the expected target <insert_5>.
Severity
20 : Error
Explanation
An attempt was made to remove a symbolic link with the name <insert_3> but it was not removed because the target of the symbolic link <insert_4> does not match the expected target <insert_5>.
Response
Check the definition of the symbolic link and, if incorrect, remove the symbolic link manually before reissuing the command.
AMQ6299S
An error occurred while creating or checking the directory structure for the queue manager.
Severity
40 : Severe
Explanation
During creation, startup or deletion of the queue manager, an error occurred while creating or checking a file or directory. The queue manager could not access the path <insert_3>.
Response
Identify why the queue manager files cannot be created or why the check failed. Likely causes include an invalid remote path name. Correct the problem and submit the command again.
AMQ6300E
Directory <insert_3> could not be created: <insert_4>.
Severity
20 : Error
Explanation
The directory is missing and could not be created for the following reason: <insert_4>.
Response
Analyse why the directory could not be created and fix the problem. Reissue the command.
AMQ6302E
The file ( <insert_3> ) could not be read.
Severity
20 : Error
Explanation
The file ( <insert_3> ) could not be read.
Response
Check that the file exists and that the file has the appropriate read permissions.
AMQ6303E
A signal handler stopped program <insert_3> from being launched.
Severity
20 : Error
Explanation
A child process will remain as a defunct process until the exit status of the child process is read. IBM MQ was attempting to launch program <insert_3> and was going to register a SIGCHLD signal handler so that it could gather the exit status when the program ended. However, a signal handler was already registered, which stopped MQ from registering its own signal handler.
Response
Either remove the signal handler that was registered, or notify IBM MQ that the application will read the exit status of all child processes by setting the environment variable AMQ_SIGCHLD_APP_HANDLER.
AMQ6306E
We must be the <insert_3> installation owner to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as a user that owns the <insert_3> installation.
Response
Log in as an appropriate user and run the command again.
AMQ6307W
Slow random data collection.
Severity
10 : Warning
Explanation
IBM MQ requires a source of random data for security purposes. The <insert_3> function took <insert_1> seconds to complete. This delay might indicate a problem with the operating system.
Response
Determine the reason for the slow performance. If the function is a system call, consult the operating system documentation and error logs.
If the error persists, we can set the AMQ_RANDOM_ENTROPY_ALGORITHM environment variable to change the random data source. Permitted values are <insert_4>.
AMQ6308E
Failed to gather random data from the operating system.
Severity
30 : Error
Explanation
IBM MQ requires a source of random data for security purposes. The <insert_3> function unexpectedly returned error <insert_1>.
IBM MQ failed to initialize.
Response
Determine the reason for the error. If the function is a system call, consult the operating system documentation and error logs.
If the error persists, we can set the AMQ_RANDOM_ENTROPY_ALGORITHM environment variable to change the random data source. Permitted values are <insert_4>.
AMQ6312E
The <insert_3> operation on filesystem <insert_4> could not be completed as the filesystem is in use.
Severity
20 : Error
Explanation
A request was made to execute the <insert_3> operation on the <insert_4> filesystem but this request could not be completed as the filesystem is in use.
Response
Use the system commands to identify why the operation could not be completed, resolve the issue and retry the command.
AMQ6314I
Displays a summary of FFSTs in time order.
Usage: ffstsummary <options> fdcpath...
where options, obeyed in the order given, are:
-a ident Add (or replace) line ident, e.g. "Host Name".
-d ident Delete line ident, e.g. "Host Name" (a blank parameter
deletes all idents).
-c directory Specify directory to use if no fdcpaths are given.
-h Display this help.
-v Display the version of this program.
If no fdcpaths are given, defaults to reading *.FDC files from the
directory specified, or the current directory.
Note: An output line flagged with an exclamation mark indicates an
incomplete FFST, e.g. truncated due to disk full.
Severity
0 : Informational
Explanation
The usage message for the ffstsummary command.
Response
None
AMQ6315I
Please wait while FFSTs are being processed.
Severity
0 : Informational
Explanation
The ffstsumary command is reading a large amount of data which may take a significant amount of time to process before the results are displayed.
Response
None
AMQ6317E
MBCS error
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data due to a MBCS error. Conversion is from CCSID <insert_1> to CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6318E
SBCS error
Severity
30 : Error
Explanation
IBM MQ is unable to convert string data due to a SBCS error. Conversion is from CCSID <insert_1> to CCSID <insert_2>.
Response
Check the IBM MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by the system.
AMQ6321E
File <insert_3> needs updating.
Severity
20 : Error
Explanation
The identified file needs updating.
Response
Reissue the command selecting the option to fix files that need updating.
AMQ6322I (UNIX and Linux)
Usage: crtmqdir <insert_-a | -m QMgrName | -s> [-f] [-g OwningGroup] [-x standard|high]
-a Check all directories.
-f Fix errors.
-g Use this group for directory and file ownership.
-m Check directories for the specified queue manager.
-s Check the system-wide directories.
-x Level of permissions.
Severity
0 : Informational
Explanation
This shows the correct usage. We must specify either -a, -m or -s.
Response
None.
AMQ6322I (Windows)
Usage: crtmqdir <insert_-a | -m QMgrName | -s> [-f] [-x standard|high]
-a Check all directories.
-f Fix errors.
-m Check directories for the specified queue manager.
-s Check the system-wide directories.
-x Level of permissions.
Severity
0 : Informational
Explanation
This shows the correct usage. We must specify either -a, -m or -s.
Response
None.
AMQ6323E (IBM i)
We must be a member of the MQ Administration group to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as a user that is a member of the MQ Administration group.
Response
Log in as an appropriate user and reissue the command.
AMQ6323E (UNIX and Linux)
We must be the MQ Administrator or operating system superuser to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as the MQ Administrator or as a user with superuser privileges.
Response
Log in as an appropriate user and reissue the command.
AMQ6323E (Windows)
We must be a member of the MQ Administration group or an operating system administrator to run this command.
Severity
20 : Error
Explanation
In order to run this command we must be logged on as a user that is a member of the MQ Administration group or as a user with administrative privileges.
Response
Log in as an appropriate user and reissue the command.
AMQ6324E
Directory <insert_3> could not be removed: <insert_4>.
Severity
20 : Error
Explanation
The directory could not be removed for the following reason: <insert_4>.
Response
Analyse why the directory could not be removed and fix the problem. Reissue the command.
AMQ6325W
Message <insert_3> is already <insert_4>.
Severity
10 : Warning
Explanation
Message <insert_3> is already excluded or suppressed in the ExcludeMessage or SuppressMessage configuration for the queue manager.
Response
Update the queue manager configuration to remove the duplicate message identifier or correct it if a different message identifier was intended.
AMQ6326W
<insert_2> messages discarded by diagnostic message service <insert_3>.
Severity
10 : Warning
Explanation
Diagnostic message service <insert_3> of type <insert_4> is not processing messages quickly enough to keep up with demand, causing a backlog of <insert_1> messages. <insert_2> messages have been discarded in order to reduce the backlog, including messages: <insert_5>.
Response
Investigate why service <insert_3> is running so slowly or why such a backlog of messages has built up. Consider whether the service should exclude or suppress messages.
AMQ6327E
Installation path <insert_3> is not valid.
Severity
20 : Error
Explanation
When processing program <insert_4>, IBM MQ detected that, due to the configuration of the environment, resources were loaded from <insert_3>. This location is not valid. The length of the installation path is limited to 256 bytes. The installation path must not contain any spaces or the following characters: colon (:), number sign (#), percent sign (%). The program cannot complete successfully while the program is using resources from a location that is not valid.
Response
Configure the environment so that all resources required by program <insert_4> are loaded from a valid installation path.
AMQ6328W
Target <insert_4> of symbolic link with the name <insert_3> not found.
Severity
10 : Warning
Explanation
An attempt was made to create a symbolic link with the name <insert_3> to target <insert_4> but the target could not be found.
Response
The target file could not be found. Correct the problem before reissuing the command.
AMQ6500I
<insert_1> of <insert_2> tasks have been completed successfully.
Severity
0 : Informational
Explanation
The command has completed <insert_1> of <insert_2> tasks succesfully.
Response
None.
AMQ6501W
<insert_1> of <insert_2> tasks have been rolled back.
Severity
10 : Warning
Explanation
The command failed to complete so, <insert_1> of the <insert_2> task performed have been undone.
Response
If <insert_1> is not equal to <insert_2> then you may need to perform some manual cleanup of the tasks which could not be undone.
AMQ6502E
Unable to read the <insert_3> system environment variable.
Severity
20 : Error
Explanation
An attempt was made to read the system environment variable <insert_3>, however either the current contents could not be read or it contains an unexpected type of data.
Response
Verify that the existing environment variable contains expected data. This value is read from the registry on Windows where the problem might be caused by it having an unexpected data type or by a mismatch in the permissions required to access it.
AMQ6503E
Unable to modify the '%3' system environment variable.
Severity
20 : Error
Explanation
An attempt was made to modify the value of system environment variable <insert_3>, however a problem was encountered when doing so.
Response
Verify that the existing environment variable contains expected data. This value is stored in the registry on Windows where the problem might be caused by a mismatch in the permissions required to access it.
AMQ6504E
Unable to remove the <insert_3> system environment variable.
Severity
20 : Error
Explanation
An attempt was made to remove the system environment variable <insert_3>, however it could not be deleted.
Response
Verify that the existing environment variable contains expected data. This value is stored in the registry on Windows where the problem might be caused by a mismatch in the permissions required to access it.
AMQ6505E
Unable to register <insert_3> as a COM component.
Severity
20 : Error
Explanation
An attempt was made to register <insert_3> as a COM component. The call to its DllRegisterServer function returned <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6506E
Unable to unregister <insert_3> as a COM component.
Severity
20 : Error
Explanation
An attempt was made to unregister <insert_3> as a COM component. The call to its DllUnregisterServer function returned <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6507E
Unable to register .NET assembly <insert_3> as a COM component.
Severity
20 : Error
Explanation
An attempt was made to register .NET assembly <insert_3> as a COM component. The return code from the registration program, <insert_4> was <insert_1>.
This error can occur if the Microsoft Distributed Transaction Coordinator (MSDTC) is unable to start, in which case an event is written to the Windows event log indicating the nature of the problem.
If the problem occurred when setting this installation as the primary installation, the operation continues, ignoring the failure.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6508E
Unable to deregister .NET assembly <insert_3> as a COM component.
Severity
20 : Error
Explanation
An attempt was made to deregister .NET assembly <insert_3> as a COM component. The return code from the deregistration program, <insert_4> was <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6509E
Unable to update registry value.
Severity
20 : Error
Explanation
An attempt was made to update the value of <insert_4> in registry key <insert_3> to <insert_5>, however a problem was encountered when doing so. The system return code was <insert_1>.
Response
Verify that the permissions on registry key <insert_3> allow the executing user to modify values within it. Executing 'crtmqdir -f -a' under a local computer administrator user account will restore any missing permissions required by MQ.
AMQ6510E
Unable to remove value <insert_4> from registry key <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to remove the the value <insert_4> from the registry key <insert_3>, however it could not be deleted, the sytem return code was <insert_1>.
Response
Verify that the permissions on registry key <insert_3> allow the executing user to modify values within it.
AMQ6511E
Unable to copy registry key <insert_3> to <insert_4>.
Severity
20 : Error
Explanation
An attempt was made to copy the contents of registry key <insert_3> to registry key <insert_4>, however a problem was encountered when doing so. The system return code was <insert_1>.
Response
Verify that the permissions on registry key <insert_3> allow the executing user to read values within it and that the parent of key <insert_4> does not disallow the executing user to create new keys.
AMQ6512E
Unable to remove registry key <insert_4>.
Severity
20 : Error
Explanation
An attempt was made to remove registry key <insert_4> which was orignially copied there from registry key <insert_3>, however it could not be deleted. The sytem return code was <insert_1>.
Response
Verify that the permissions on registry key <insert_4> allow the executing user to modify values within it.
AMQ6514E
Unable to create an alias service named <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to create a service named <insert_3> with display name <insert_4> to act as an alias to the service for this installation. This can sometimes occur if the service database has not been updated, and can be resolved by re-starting the operating system. The system return code was <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6515E
Unable to delete the alias service named <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to delete the service named <insert_3>. This service was previously created with display name <insert_4> as an alias to the service for this installation. The system return code was <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6516E
Unable to install assembly <insert_3> into the GAC.
Severity
20 : Error
Explanation
An attempt was made to install the .NET assembly or publisher policy named <insert_3> into the .NET Global Assembly Cache. The return code from the installation program, <insert_4> was <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6517E
Unable to remove assembly <insert_3> from the GAC.
Severity
20 : Error
Explanation
An attempt was made to remove the .NET assembly or publisher policy file named <insert_3> from the .NET Global Assembly Cache. The return code from the removal program, <insert_4> was <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and re-issue the request.
AMQ6518E
Command <insert_3> <insert_4> failed with return code <insert_1>.
Severity
20 : Error
Explanation
An attempt was made to run the command <insert_3> with arguments <insert_4> but the command failed with return code <insert_1>.
Response
Resolve the issue that resulted in return code <insert_1> and run the command again.
AMQ6520E
The command failed because the remote replication address is invalid.
Severity
20 : Error
Explanation
This message is issued when the provided remote replication address is invalid.
Response
Reissue the command with a valid remote replication address.
AMQ6521E
The command failed because snapshot rollback is in progress.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because snapshot rollback is in progress.
Response
Reissue the command when the snapshot rollback has completed.
AMQ6522E
Port <insert_1> is invalid, must be in range 1025 to 9999.
Severity
20 : Error
Explanation
A port has been supplied to the command that is not within the valid range: 1025 to 9999.
Response
Reissue the command with a valid port.
AMQ6523E
The command failed because synchronization is in progress.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because synchronization is in progress.
Response
Reissue the command when the synchronization has completed.
AMQ6524E
The IP Address parameter <insert_3> is already in use by the local appliance
Severity
20 : Error
Explanation
The IP Address parameter provided on the command line is already in use by the local appliance and therefore cannot be the address of a remote appliance.
Response
Re-issue the command specifying the IP address of the remote appliance. remote appliance.
AMQ6525E
The IP Address parameter must be in dotted decimal notation.
Severity
20 : Error
Explanation
The IP Address parameter must be provided in dotted decimal notation (eg 9.20.12.14). It cannot be provided via a hostname.
Response
Re-issue the command using the numeric form of the IP Address for the remote appliance.
AMQ6526E
The command failed because the initial synchronization has not completed for queue manager <insert_3>.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the synchronization had not completed.
Response
Reissue the command when the initial synchronization has completed.
AMQ6526E (IBM MQ Appliance)
The command failed because the initial synchronization has not completed.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the synchronization had not completed.
Response
Reissue the command when the initial synchronization has completed.
Revert to snapshot started. Use the status command to monitor progress.
Severity
0 : Informational
Explanation
This message is issued from the makedrprimary command when a DR queue manager that is in Inconsistent state is about to revert to a previous snapshot.
Response
Use the status command to monitor progress.
AMQ6529I
Usage: makedrprimary -m QMgrName
-m Queue manager name
Severity
0 : Informational
Response
None.
AMQ6530I
Usage: makedrsecondary -m QMgrName
-m Queue manager name
Severity
0 : Informational
Response
None.
AMQ6531E
Insufficient space on disk on remote appliance.
Severity
20 : Error
Explanation
The operation cannot be completed due to shortage of disk space on the remote appliance.
Response
Either make more disk space available, or reduce the disk requirements of the command we issued.
AMQ6532I
Usage: dltdrprimary -m QMgrName
-m Queue manager name
Severity
0 : Informational
Response
None.
AMQ6533I
Usage: dltdrsecondary -m QMgrName
-m Queue manager name
Severity
0 : Informational
Response
None.
AMQ6534E
The command failed because it was not issued on the DR secondary appliance for the queue manager.
Severity
20 : Error
Explanation
This message is issued from <insert_3> when it failed because it was not issued on the DR secondary appliance for the queue manager.
Response
Issue the command on the DR secondary appliance for the queue manager if that is required.
AMQ6535E
The <insert_3> command cannot be issued against a DR queue manager.
Severity
20 : Error
Explanation
This message is issued from a command which cannot be issued against a DR queue manager.
Response
The queue manager can be removed from DR control with the dltdrprimary or dltdrsecondary command.
AMQ6536E
The command failed because the local and remote replication addresses are the same.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the local and remote replication addresses were the same.
Response
Ensure that the local and remote replication addresses are not the same.
AMQ6537I
Usage: crtdrprimary -m QMgrName -r Name -i IPAddress -p Port
[-f FloatingIP]
-f Floating IP address of the high availability (HA) queue manager
-i IP address of the DR replication interface on the recovery appliance
-m Queue manager name
-p Data replication listener port
-r Recovery appliance name
Severity
0 : Informational
Response
None.
AMQ6538I
Usage: crtdrsecondary -m QMgrName -s Size -l Name -i IPAddress -p Port
-i IP address of the DR replication interface on the main appliance
-l Main appliance name
-m Queue manager name
-p Data replication listener port
-s File system size in megabytes (MB)
Severity
0 : Informational
Response
None.
AMQ6539E
The command failed because the queue manager is primary on the remote appliance.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager was primary on the remote appliance.
Response
If appropriate, issue makedrsecondary on the remote appliance and reissue the command.
AMQ6540E
The command failed because the queue manager is not configured for DR.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager is not configured for DR.
Response
If appropriate, configure the queue manager for DR and reissue the command.
AMQ6541I
Queue manager <insert_3> is prepared for Disaster Recovery replication.
Now execute the following command on appliance <insert_4>:
<insert_5>
Severity
0 : Informational
Explanation
This message is issued when the crtdrprimary command succeeds. It includes the command that should be executed on the remote appliance.
Response
The user should execute the command on the remote appliance.
AMQ6542E
The command failed because the queue manager is already configured for DR.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager is already configured for DR.
Response
None.
AMQ6543E
Port <insert_1> is in use.
Severity
20 : Error
Explanation
The command failed because port number <insert_1> is currently in use.
Response
Reissue the command with a port number that is not in use.
For crtmqm -sx(s), the first crtmqm -sxs automatically selects the replication port to use. It chooses the next free port from 7000. This error indicates that the port that was chosen is one that is in use on this node. The port is added to an exclude list. The secondary queue manager(s) should be deleted and recreated on the other node(s).
AMQ6544I
The following DR commands are available. Type help <command> for more information.
crtdrprimary Prepares a local queue manager for DR replication
crtdrsecondary Creates a replicated queue manager on the DR appliance
dltdrprimary Removes a primary DR queue manager from DR control
dltdrsecondary Deletes a secondary DR queue manager
dspdrlink Displays network link used for replication when DR configured
makedrprimary Makes a queue manager primary on the local appliance
makedrsecondary Makes a queue manager secondary on the local appliance
setdrlink Sets the replication link used for subsequent DR
configurations
Severity
0 : Informational
Explanation
This message is issued when a user types help dr within the IBM MQ CLI.
Response
None.
AMQ6545I
Client channel table written to <insert_3>.
Severity
0 : Informational
Explanation
The client channel table has been written to the file <insert_3>.
Response
None.
AMQ6546E
An internal IBM MQ error has occurred.
Severity
20 : Error
Explanation
An error has been detected, and the MQ error recording routine has been called.
This shows the correct usage of amqsrua. Message shown when 'help amqsrua' is typed into the IBM MQ CLI.
AMQ6561I
Usage: <insert_3> [command]
Severity
0 : Informational
Explanation
This message is displayed when usage of the 'help' or '?' command is requested.
AMQ6562I
No help available for <insert_3>.
Severity
0 : Informational
Explanation
This message is displayed when a user types a valid command which is not available in failsafe mode.
AMQ6563I
Command <insert_3> cannot be run while in failsafe mode
Severity
0 : Informational
Explanation
This message is displayed when a user types a valid command which is not available in failsafe mode.
AMQ6564I
Unknown command or macro (<insert_3>)
Severity
0 : Informational
Explanation
This message is shown when a user types an unknown command into the mqcli.
AMQ6565W
The <insert_3> command partially succeeded.
Severity
10 : Warning
Explanation
This message is issued from an HA command when it partially succeeded.
Response
Review other messages issued to identify any subsequent actions that may be required.
AMQ6566E
Failed to query status for queue manager <insert_3>.
Severity
20 : Error
Explanation
The CLI status command failed to query status for the specified queue manager.
AMQ6567E
Failed to query status.
Severity
20 : Error
Explanation
The CLI status command failed to complete.
AMQ6568E
The Logical volume <insert_3> is missing for queue manager <insert_4>
Severity
20 : Error
Explanation
IBM MQ has detected the logical volume <insert_3> is missing for queue manager <insert_4>.
Response
We should remove the queue manager definition using the rmvmqinf command.
AMQ6569E
Logical volume <insert_3> has no associated queue manager.
Severity
20 : Error
Explanation
IBM MQ has detected the logical volume <insert_3> has no associated queue manager.
Response
We should recreate the queue manager defintion using the addmqinf command, and then if required issue the dltmqm command to delete the queue manager and logical volume.
AMQ6570I
Usage: runcheck [-a] [-v]
-v Check MQ Volume group
-a Check all
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6571I
Usage: status [QmgrName]
Severity
0 : Informational
Explanation
This message displays usage for the IBM MQ status command.
AMQ6572E
The command failed because it was not issued on the HA primary appliance for the queue manager.
Severity
20 : Error
Explanation
This message is issued from <insert_3> when it failed because it was not issued on the HA primary appliance for the queue manager.
Response
Issue the command on the HA primary appliance for the queue manager if that is required.
AMQ6573I
The command failed because there is already no preferred appliance for the queue manager.
Severity
0 : Informational
Explanation
This message is issued from clearhapreferred when it failed because there is already no preferred appliance for the queue manager.
Response
This message is for information only so no user action is required.
AMQ6574I
The command failed because this appliance is already the preferred appliance for the queue manager.
Severity
0 : Informational
Explanation
This message is issued from sethapreferred when it failed because the appliance it was issued on is already the preferred appliance for the queue manager.
Response
This message is for information only so no user action is required.
AMQ6575E
The command failed because the HA Group is not running on this appliance.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the HA Group is not running on the appliance. This may be because the HA subsystem is initializing.
Response
The user should wait for a short time, and then retry the command.
AMQ6576E
The command failed because the queue manager is not configured for HA.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager is not configured for HA.
Response
If appropriate, configure the queue manager for HA and reissue the command.
AMQ6577E
The command failed because the queue manager already exists on the other appliance in the HA Group.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager already exists on the other appliance in the HA Group.
Response
If appropriate, delete the queue manager on the other appliance in the HA Group and reissue the command.
AMQ6578I
File deleted: <insert_3>
Severity
0 : Informational
Explanation
The dltmqras command has deleted a file.
Response
None.
AMQ6579I
File found: <insert_3>
Severity
0 : Informational
Explanation
The dltmqras command has found a deletable file.
Response
None.
AMQ6580I
Do you wish to delete these files? [Y/N]
Severity
0 : Informational
Explanation
This message asks the user if they should proceed with deleting files.
AMQ6581I
Usage: dltmqras [ -y ] -a | -d | -e | -f | -h | -m QMName | -p | -t | -w
-a Purge files of all listed types except QM diagnostics.
-d File type: General diagnostics.
-e File type: Error logs.
-f File type: FDCs.
-h File type: HA.
-m File type: Queue Manager diagnostics.
-p File type: Temporary.
-t File type: Trace.
-w File type: IBM MQ Console.
-y Run without prompt.
Severity
0 : Informational
Explanation
This shows the correct usage for the dltmqras command.
Response
None.
AMQ6582I
<insert_1> diagnostic file(s) removed.
Severity
0 : Informational
Explanation
This message lets the user know how many files were removed.
AMQ6583I
<insert_1> removable diagnostic file(s) found.
Severity
0 : Informational
Explanation
This message lets the user know how many files were found.
AMQ6584E
The command failed because it was not issued on the DR primary appliance for the queue manager.
Severity
20 : Error
Explanation
This message is issued from <insert_3> when it failed because it was not issued on the DR primary appliance for the queue manager.
Response
Issue the command on the DR primary appliance for the queue manager if that is required.
AMQ6585E
The command failed because the queue manager is already configured for HA.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the queue manager is already configured for HA.
Response
No user response is required.
AMQ6586I
The <insert_3> command succeeded.
Severity
0 : Informational
Explanation
This message is issued from an HA command when it succeeded.
Response
This message is for information only so no user action is required.
AMQ6587E
The <insert_3> command failed due to an internal error. Contact IBM Support.
Severity
20 : Error
Explanation
This message is issued from <insert_3> when it failed due to an internal error.
This message is issued when IBM MQ failed to remove high availability configuration on this appliance.
Response
Refer to previous error messages for more information.
AMQ6589W
Failed to remove high availability configuration on appliance <insert_3>.
Severity
10 : Warning
Explanation
This message is issued when IBM MQ failed to remove high availability configuration on remote appliance <insert_3>. This may be because remote appliance <insert_3> is unavailable.
Response
The user should issue command <insert_4> on remote appliance <insert_3> when it becomes available.
This message is issued when IBM MQ removes high availability configuration on remote appliance <insert_3>.
Response
This message is for information only so no user action is required.
AMQ6592W
The DataPower timezone configuration has changed since MQ was started. We must reboot the system in order for the timezone to be resynchronised.
IBM MQ will continue to use the original timezone configuration.
Severity
10 : Warning
Explanation
The timezone configuration has been changed and the system should be rebooted to ensure the times displayed in the IBM MQ logs are consistent with the DataPower logs.
Response
The system should be rebooted to ensure the times displayed in the IBM MQ logs are consistent with the DataPower logs.
AMQ6593I
Waiting up to <insert_1> seconds for remote system to respond.
Severity
0 : Informational
Explanation
The crthagrp and prepareha commands both wait for the remote system to respond, as determined by the -t switch, or using the default of 10 minutes. This message marks the start of that interval.
Response
None.
AMQ6594E
The <insert_3> command was unable to connect to a <insert_4> session on the remote appliance
Severity
20 : Error
Explanation
The <insert_3> command attempts to contact a <insert_4> session that should already be running on the remote appliance, however, it was unable to do so.
Response
Possible causes for the failure to connect are:
The remote appliance was not running <insert_4> at the time that the
<insert_3> command was active.
The value supplied to the -s option was not the same on both
appliances.
A network adaptor on one of the appliances was not correctly
configured. Correct the problem and re-issue the command.
AMQ6595E
To see usage, type help amqspdbg.
Severity
20 : Error
Explanation
This message is issued when amqspdbg returns a non zero exit code from the MQ CLI.
Response
Consult the usage for amqspdbg and re-run your command.
AMQ6596I
<insert_3>://<insert_4> created.
Severity
0 : Informational
Explanation
A file named <insert_4> under the <insert_3> URI was created.
AMQ6597I
Note: With valid arguments, output will be written directly to file.
Severity
0 : Informational
Explanation
This message lets the user know that they should not expect output on screen. exist.
AMQ6598E
On the IBM MQ, this program only works in non-interactive modes.
Usage : amqrfdm -d | -s ControlString [-m QMgrName]
Severity
20 : Error
Explanation
This message is issued if a user does not specify one of the required arguments for amqrfdm. exist.
Response
amqrfdm should be run with either -d or -s ControlString specified.
AMQ6599W
Warning: Queue manager <insert_3> is using automatic configuration of ini files, and so changes to anything other than valid AutoConfig stanza keys will be lost when the queue manager restarts.
Severity
10 : Warning
Explanation
This message is a warning to the user when setmqini modifies a queue manager stanza and automatic configuration of ini files is configured.
Response
None.
AMQ6600I
The IBM MQ subsystem is starting.
Severity
0 : Informational
Explanation
The IBM MQ subsystem is starting. As part of this process all MQ queue managers which are defined to be started automatically will also start.
Response
None.
AMQ6601I
The IBM MQ subsystem is stopping.
Severity
0 : Informational
Explanation
This message is issued when the processes which together make up the IBM MQ subsystem are stopping. This may be the result of the administrator stopping the subsystem or the appliance shutting down.
As part of this process all MQ queue managers which were running will be shutdown.
Response
None.
AMQ6602I
The IBM MQ subsystem is active. Queue managers running [<insert_1>].
Severity
0 : Informational
Explanation
This message is issued at regular intervals by the IBM MQ subsystem.
Response
None.
AMQ6603I
Verifying filesystem <insert_3> on device <insert_4>.
Severity
0 : Informational
Explanation
This message is issued when IBM MQ begins the validation of the <insert_3> filesystem on device <insert_4>. If any errors are found then a subsequent message will be written with details of the failure.
This message is issued when IBM MQ encountered a problem verifying the <insert_3> filesystem.
Response
An FFST will have been created with details of the failure.
AMQ6605I
Verifying kernel settings.
Severity
0 : Informational
Explanation
This message is issued when IBM MQ begins the validation of the kernel settings. The kernel settings may be modified during this process to match the requirements of IBM MQ.
Response
None.
AMQ6606E
Failure encountered verifying the kernel configuration.
Severity
20 : Error
Explanation
This message is issued when IBM MQ encountered a problem while verifying or modifying the kernel configuration.
Response
An FFST will have been created with details of the failure.
AMQ6607I
The IBM MQ CLI has started for user <insert_3> from address <insert_4>.
Severity
0 : Informational
Explanation
The IBM MQ CLI has started for user <insert_3> from source address <insert_4>.
Response
None.
AMQ6608I
The IBM MQ CLI has ended for user <insert_3> from address <insert_4> with reason code <insert_1>.
Severity
0 : Informational
Explanation
The IBM MQ CLI has ended for user <insert_3> from source address <insert_4>.
Response
None.
AMQ6610E
The volume group <insert_3> is unavailable.
Severity
20 : Error
AMQ6610E (IBM MQ Appliance)
The volume group <insert_3> is unavailable. IBM MQ initialization is paused until this volume group is available.
Severity
20 : Error
Explanation
The volume group used for storage of IBM MQ system data is not available. IBM MQ initialization cannot proceed until it is available.
Response
Use the system command 'raid-volume-initialize-filesystem' to configure the internal disks.
AMQ6611E
The IBM MQ internal disks are unavailable. If the MQ disks have not yet been configured, or have been replaced we should use the system command 'raid-initialize raid0" to configure the internal disks.
The raid-initialize command will cause all data on the disks to be erased.
The MQ CLI will operate in failsafe mode until this issue is resolved and the CLI restarted.
Severity
20 : Error
Explanation
The raid device is unavailable.
Response
Use the system command 'raid-initialize raid0' to configure the internal disks.
AMQ6612W
The configuration of the internal disks does not match the expected configuration. If this is unexpected, use the system commands to verify the disk configuration.
Severity
10 : Warning
Explanation
IBM MQ expects the internal disk configuration to match a predefined configuration. The current disk layout does not match the expected configuration.
Response
If this is unexpected use the system commands to verify the disk configuration or the system command 'raid-volume-initialize-filesystem' can be used to reinitialize the internal disks.
AMQ6613W
Inconsistencies have been detected in the <insert_3> filesystem. If this is unexpected, use the system commands to verify and correct any inconsistencies in the filesystem.
Severity
10 : Warning
Explanation
IBM MQ has detected that a number of files in the <insert_3> filesystem are missing or have incorrect ownership or permissions.
Response
If this is unexpected, use the system commands to verify and correct any errors.
AMQ6614E
Operation is not allowed.
Severity
20 : Error
Explanation
This message is issued when you attempt to modify or delete a reserved userid.
Response
Do not attempt to alter the userid in question.
AMQ6615E
The userid <insert_3> is not known.
Severity
20 : Error
Explanation
This message is issued when you attempt to perform an operation on a userid that does not exist.
Response
Revise the command to operate on a userid that does exist or investigate why the userid does not exist.
AMQ6616E
The userid <insert_3> is currently logged in. Modification not allowed.
Severity
20 : Error
Explanation
This message is issued when you attempt to perform an operation on a userid that is currently logged in.
Response
Retry the command when the userid is no longer active.
AMQ6617E
The group is not known.
Severity
20 : Error
Explanation
This message is issued when you attempt to perform an operation that refers to a group that does not exist.
Response
Revise the command to refer to a group that does exist or investigate why the group not exist.
AMQ6618E
The userid <insert_3> already exists.
Severity
20 : Error
Explanation
This message is issued when you attempt to create a new userid and that userid already exists.
Response
Alter the userid to one that does not currently exist.
This message is issued when a user types help within the IBM MQ CLI.
Response
None.
AMQ6620I
The following MQ commands are available. Type help <command> for more information.
addmqm Adds an existing queue manager stored on a SAN volume
createbackupfs Creates file system for queue managers' backups crtmqm Creates a queue manager
deletebackupfs Deletes file system for queue managers' backups dltmqm Deletes a queue manager
dspamschl Displays MCA interception rules dspmq Displays information about queue managers
dspmqini Displays queue manager initialization parameters dspmqtrn Displays in-doubt and heuristically completed transactions
dspmqvar Displays global and queue manager environment variables dspmqweb Displays mqweb server settings and environment variables endmqm Stops a queue manager
mqbackup Creates backup of a queue manager
mqrestore Restores queue manager from a backup rcrmqobj Generates a client channel table rmvmqinf Remove queue manager configuration information (SAN QMs only) rsvmqtrn Resolves in-doubt and heuristically completed transactions runmqsc Runs MQSC commands runswchl Switches the transmission queue used by cluster channels
setamschl Sets MCA interception rules
setmqini Configures queue manager initialization parameters
setmqsize Increases the size of a queue manager file system
setmqvar Configures global and queue manager environment variables setmqweb Configures mqweb server settings and environment variables
status Displays status information strmqm Starts a queue manager
Severity
0 : Informational
Explanation
This message is issued when a user types help mq within the IBM MQ CLI.
Response
None.
AMQ6621I
The following diagnostic commands are available. Type help <command> for more information. amqsrua Collects and displays resource statistics publications from a
queue manager
dltmqras Deletes IBM MQ diagnostic information dmpmqcfg Dumps the configuration of a IBM MQ queue manager
dspmqerr Displays error logs and FDC files dspmqrte Determines the route that a message has taken through a queue
manager network dspmqtrc Formats IBM MQ trace dspmqver Displays IBM MQ version and build information endmqtrc Ends trace for some or all of the entities that are being traced mqrc Displays information about return codes runmqras Gathers IBM MQ diagnostic information together into a
single archive, for example to submit to IBM Support strmqtrc Enables trace at a specified level of detail, or reports the
level of tracing in effect
Severity
0 : Informational
Explanation
This message is issued when a user types help diag within the IBM MQ CLI.
Response
None.
AMQ6622I
The following user and group commands are available.
groupcreate Creates a messaging group in the internal user store
groupdelete Deletes a messaging group in the internal user store
grouplist Lists the messaging groups in the internal user store
usercreate Creates a messaging user in the internal user store
userdelete Deletes a messaging user in the internal user store
userlist Lists the messaging users in the internal user store
usermodify Modifies a messaging user in the internal user store
userbackup Backs up the internal user store
userrestore Restores the internal user store
Severity
0 : Informational
Explanation
This message is issued when a user types help user within the IBM MQ CLI.
Response
None.
AMQ6623I
The following certificate commands are available. Type help <command> for more information.
createcert Creates a self-signed certificate
createcertrequest Creates a certificate request
addcert Adds a CA certificate
deletecert Deletes a certificate
deletecertrequest Deletes a certificate request
detailcert Shows details of a specific certificate
detailcertrequest Shows details of a specific certificate request
receivecert Receives a certificate
recreatecertrequest Recreates a certificate request
listcert Lists certificates
listcertrequest Lists all certificate requests
keybackup Backs up a key repository
keyrestore Restores a key repository mqcertck Validates queue manager TLS configuration
Severity
0 : Informational
Explanation
This message is issued when a user types help cert within the IBM MQ CLI.
Response
None.
AMQ6624I
Usage: amqqmutil -m QMgrName [ -g | -l | -u | -c DirName -s VolumeSize [-F ] [-M] | -r DirName | -v [-M] ]
-m Queue manager name.
-g Generate the directory name for this queue manager. The queue manager must not exist.
-l Look up the directory name for this queue manager.
-u Unmangle the queue manager name (reverse of -l).
-c Create the logical volume for the queue manager.
-r Remove the logical volume for the queue manager.
-v Verify the logical volume for the queue manager.
-s The size of the logical volume to create.
-F Format the logical volume.
-M Mount the logical volume.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6625E
The set of parameters supplied for command <insert_3> are invalid.
Severity
20 : Error
Explanation
An IBM MQ command has been issued with incorrect parameters and cannot be completed. Review and correct the parameter options for the command and retry the command again.
Response
Review the command usage. any errors.
AMQ6626W
Unable to complete the requested command. Stanza <insert_3> does not exist.
Severity
10 : Warning
Explanation
IBM MQ has detected that the stanza supplied for the operation, does not exist. The command is unable to process the request.
Response
Check the spelling of the supplied Stanza and review the set of stanzas that do exist using the dspmqini command.
AMQ6627W
Unable to complete the requested command. Key <insert_3> does not exist.
Severity
10 : Warning
Explanation
IBM MQ has detected that the key supplied for the operation does not exist. The command is unable to process the requested action.
Response
Check the spelling of the supplied key and review the set of keys for stanza <insert_4> using the setmqini command.
AMQ6628E
It is not permitted to execute the command for stanza <insert_3>.
Severity
20 : Error
Explanation
IBM MQ has detected that the stanza supplied is not permitted by the operation. Review the documentation to view the stanzas that are permitted for the operation requested.
Response
Issue the command again specifying a valid stanza.
AMQ6629I
Key <insert_3> was successfully deleted from stanza <insert_4>.
Severity
0 : Informational
Explanation
IBM MQ has successfully deleted key <insert_3> from stanza <insert_4>. If this is the only remaining key for this stanza, the stanza will also have been deleted.
Response
No action required.
AMQ6630I
Key <insert_3> was successfully updated in stanza <insert_4> for queue manager <insert_5>.
Severity
0 : Informational
Explanation
IBM MQ successfully updated a key in the qm.ini file for queue manager <insert_5>.
Response
None.
AMQ6631E
Inadequate storage was provided to capture the entire content for the operation.
Severity
20 : Error
Explanation
IBM MQ has detected that a command did not allow enough storage to complete the operation
Response
Perform the operation again providing adequate storage.
AMQ6632E
The group <insert_3> already exists.
Severity
20 : Error
Explanation
This message is issued when you attempt to create a new group and that group already exists.
Response
Revise the command to refer to a group that does not already exist.
AMQ6633E
The group <insert_3> was not deleted because it is a primary group.
Severity
20 : Error
Explanation
This message is issued when you attempt to delete a group that is the primary group for some user. Usually this will be the user with the same name as the group.
Response
Consider whether you really intend to delete this group. If so, modify the corresponding user to make a different group the primary.
AMQ6635E
Failed to start the MQ Web UI server.
Severity
20 : Error
Explanation
This message is issued when the MQ WebUI server fails to start during system initialisation.
Response
None.
AMQ6636I
Usage: dspmqini -g|-m QMgrName [-s StanzaName [-k KeyName] [-n ObjectName]]
-g Show global settings.
-m Queue manager name.
-s Stanza name.
-k Key name.
-n Object name. Valid only for the next stanzas:
DiagnosticSystemMessages (global),
DiagnosticMessagesTemplate (global),
DiagnosticMessages (queue manager).
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6637I
Usage: setmqini -g|-m QMgrName (-s StanzaName -k KeyName [-d | -v Value] [-n ObjectName]) | -r
-g Set global setting.
-m Queue manager name.
-s Stanza name.
-k Key name of attribute to set.
-v Attribute value to set.
-d Delete the attribute or stanza.
-n Object name. Valid only for the next stanzas:
DiagnosticSystemMessages (global),
DiagnosticMessagesTemplate (global),
DiagnosticMessages (queue manager).
-r Permanently reset automatic configuration ini baseline.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6638E
Failed to mount filesystem <insert_4> for queue manager <insert_3>.
Severity
20 : Error
Explanation
IBM MQ attempted to mount the filesystem <insert_4> for queue manager <insert_3> but the attempt to mount the filesystem failed.
Response
Use the system commands to verify and correct any errors before reissuing the command.
Usage: setmqvar [-m QMgrName] -k KeyName [-d | -v Value]
-d Delete the environment variable.
-k Key name of environment variable to set.
-m Queue manager name.
-v Attribute value to set.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6641I
Usage: dlthagrp
Severity
0 : Informational
Explanation
This message is issued when a user types help dlthagrp within the IBM MQ CLI.
Response
None.
AMQ6642I
Usage: crthagrp -s SecretText <-a IPAddress | -r>
-a IP address of the HA group primary interface on the other appliance.
-s A string used to generate a short-lived password.
-r Recreate the existing HA group to a replacement partner appliance. This will replicate the configuration and data of all HA queue managers to the replacement partner appliance. The configuration of this appliance remains unchanged.
Severity
0 : Informational
Explanation
This message is issued when a user types help crthagrp within the IBM MQ CLI.
Response
None.
AMQ6643I
Mounted filesystem <insert_4> for queue manager <insert_3>.
Severity
0 : Informational
Explanation
The filesystem <insert_4> has been mounted for queue manager <insert_3>.
Response
None.
AMQ6644I
Initializing queue managers.
Severity
0 : Informational
Explanation
The initialization task is initializing the queue managers and their file systems.
Response
None.
AMQ6645I
The MQ Daemon has completed initialization.
Severity
0 : Informational
Explanation
The MQ task has completed initialization.
Response
None.
AMQ6646E
The user id is not valid.
Severity
20 : Error
Explanation
This message is issued when you attempt to perform an operation that refers to a userid that is not syntactically correct.
Response
Revise the command to use a valid userid.
AMQ6647I
Usage: dsphagrp
Severity
0 : Informational
Explanation
This message is issued when a user types help dsphagrp or dsphagrp with one or more arguments within the IBM MQ CLI.
Response
None.
AMQ6648I
Usage: userbackup [-f [mqbackup://]BackupName]
-f Backup file to create
Usage: userrestore [-F] -f [mqbackup://]BackupName
-f Backup file to restore
-F Force restore
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6649E
The userbackup command failed. Error identifier ( <insert_1>, <insert_2> )
Severity
20 : Error
Explanation
An error occurred backing up the user files
Response
Investigate any problems reported. Use the error identifier provided when contacting MQ support.
AMQ6650E
The userrestore command failed. Error identifier ( <insert_1>, <insert_2> )
Severity
20 : Error
Explanation
An error occurred restoring the user files
Response
Investigate any problems reported. Use the error identifier provided when contacting MQ support.
AMQ6651E
The MQ daemon task is not running or not responding.
Consult the error logs for further details on the cause of the failure. Functionality of the IBM MQ will be restricted until this issue is resolved.
Severity
20 : Error
Explanation
The MQ daemon task is not running.
Response
Consult the queue manager error logs for further details on the cause of the failure.
AMQ6652I
Environment variable <insert_3> was successfully added or updated.
Severity
0 : Informational
Explanation
IBM MQ successfully added or updated the specified environment variable.
Response
None.
AMQ6653I
Environment variable <insert_3> was successfully updated for queue manager <insert_4>
Severity
0 : Informational
Explanation
IBM MQ successfully added or updated the specified environment variable for a queue manager.
Response
None.
AMQ6654I
Environment variable <insert_3> was successfully deleted.
Severity
0 : Informational
Explanation
IBM MQ has successfully deleted the environment variable.
Response
No action required.
AMQ6655I
Environment variable <insert_3> was successfully deleted for queue manager <insert_4>
Severity
0 : Informational
Explanation
IBM MQ has successfully deleted the environment variable for the queue manager.
Response
No action required.
AMQ6656I
User data has been backed up to <insert_3>
Severity
0 : Informational
Explanation
The backup of user data completed successfully
Response
No action required.
AMQ6657I
Usage: userlist [-u UserName]
-u Messaging user name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6658I
Usage: userdelete -u UserName
-u Messaging user name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6659I
Usage: usercreate -u UserName [-d Text] [-g GroupName,...] [-p Password]
-d Messaging user description
-g Messaging group names
-p Messaging user password
-u Messaging user name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6660I
Usage: usermodify -u UserName [-d Text] [-g GroupName,...] [-p Password]
-d Messaging user description
-g Messaging group names
-p Messaging user password
-u Messaging user name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6661I
Usage: user [ add | modify | delete | list ]
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6662I
Usage: groupcreate -g GroupName
-g Messaging group name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6663I
Usage: groupdelete -g GroupName
-g Messaging group name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6664I
Usage: grouplist
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6665I
Usage: group [ add | delete | list ]
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6666I
Usage: prepareha -s SecretText -a IPAddress [-t Timeout]
-a IP address of the HA group primary interface on the other appliance.
-s A string used to generate a short-lived password.
-t Timeout interval in seconds (default 600).
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6666S (IBM i)
Required IBM MQ system profile(s) can not be accessed.
Severity
40 : Severe
Explanation
The required MQ system profile(s) QMQM and/or QMQMADM are not found or have been disabled. MQ can not continue processing the command without the profiles existing and enabled on the system. The major error code is <insert_3>, the minor error code is <insert_4>. The major error codes and their meanings are as follows: *DISABLED - The user profile has been disabled. *PWDEXP - The password for the user profile has expired . *EXIST - The user profile does not exist. If none of these error codes are shown the major error code contains the exception identifier. The minor error code identifies the user profile which cannot be accessed.
Response
Check that both QMQM and QMQMADM profiles exist and are both enabled using the DSPUSRPRF command, or contact the IBM MQ system administrator.
AMQ6667I
Usage: sethapreferred QMgrName
Severity
0 : Informational
Explanation
This message is issued when a user types help sethapreferred within the IBM MQ CLI.
Response
None.
AMQ6668I
Usage: sethagrp - Use this command to modify your HA group configuration
Suspend or resume the appliance within the HA group
sethagrp -r | -s
Include or exclude the named queue manager from the HA group
sethagrp ( -i QMName | -e QMName )
Complete an upgrade of an HA queue manager
sethagrp -u ( -a | QMName) [-f]
-e Exclude the named queue manager from the HA group.
-i Include the named queue manager in the HA group.
-r Resume the HA group on the appliance from standby mode.
-s Suspend the HA group on the appliance into standby mode.
-u Complete upgrade of the named HA queue manager.
-a Complete upgrade of all HA queue managers.
-f Force completion of upgrade even if unable to communicate with remote appliance.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ6669I
Usage: clearhapreferred QMgrName
Severity
0 : Informational
Explanation
This message is issued when a user types help clearhapreferred within the IBM MQ CLI.
Response
None.
AMQ6670E
This appliance is not part of an HA Group.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the local appliance is not part of an HA Group.
Response
If appropriate, configure the appliance to be part of an HA Group and reissue the command.
AMQ6671E
The network address of <insert_3> on the local appliance could not be determined.
Severity
20 : Error
Explanation
This message is issued when IBM MQ cannot determine a local network address for the specified network interface.
Response
Ensure that the network interface is configured and enabled before reissuing the command.
AMQ6672E
The name of the local appliance has not been configured.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the name of the local appliance has not been configured.
Response
Ensure that the name of the local appliance has been configured then reissue the command. The appliance name is a system setting that can be configured using either the command interface or the web UI.
AMQ6673E
The network addresses of the HA interfaces of the remote appliance could not be determined.
Severity
20 : Error
Explanation
This message is issued when IBM MQ cannot get the remote HA network addresses.
Response
Ensure that the HA network interfaces on the remote appliance are configured and enabled before reissuing the command.
AMQ6674E
The name of the remote appliance has not been configured.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the name of the remote appliance has not been configured.
Response
Ensure that the name of the remote appliance has been configured then reissue the command. The appliance name is a system setting that can be configured using either the command interface or the web UI.
AMQ6675E
The HA or DR appliance names are not unique.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the HA or DR appliance names are not unique.
Response
Ensure that the appliances have a different name then reissue the command. The appliance name is a system setting that can be configured using either the command interface or the web UI.
AMQ6676I
The internal disks are being configured for use by MQ. Phase <insert_1> of <insert_2>.
Severity
0 : Informational
Explanation
IBM MQ will configure the internal disks for use. This message will be reported a number of times as the disks are configured.
Response
None
AMQ6677E
The user modify command references an object that is not known.
Severity
20 : Error
Explanation
This message is issued when a user modify command refers to an object that does not exist. Typically, this will be either the userid itself or a group that is being added or removed.
Response
Revise the command to remove the reference to a non-existent object.
AMQ6678E
Unable to connect to remote appliance on interface <insert_3>
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that it is unable to connect to the remote appliance on interface <insert_3>
Response
Determine why the remote appliance was unavailable and reissue the command if appropriate.
AMQ6679W
Reading environment variables failed.
Severity
10 : Warning
Explanation
Environment variables file not correct.
Response
None
AMQ6680E
The file systems required for IBM MQ are unavailable.
A transient failure to mount the file systems might be resolved by rebooting the appliance. If this is a persistent issue then we should consult the error logs for more information and contact the IBM support center.
The MQ CLI will operate in failsafe mode until this issue is resolved and the CLI restarted.
Severity
20 : Error
Explanation
The IBM MQ file systems are unavailable.
Response
Contact IBM support for assistance in initializing the MQ file systems.
AMQ6681I
The data on this appliance will be used for the queue manager.
Severity
0 : Informational
Explanation
This appliance is chosen as the primary.
Response
No action required.
AMQ6682E
The appliance could not be made the primary for the queue manager.
Severity
20 : Error
Explanation
One of the underlying commands failed.
Response
Refer to previous error messages for more information.
AMQ6683I
Usage: makehaprimary QMgrName
Severity
0 : Informational
Explanation
This message is issued when a user types makehaprimary with zero arguments or more than one argument.
Response
None.
AMQ6684E
The Queue Manager is not in the correct state.
Severity
20 : Error
Explanation
The command is not applicable to the queue manager in its current state.
Response
Refer to previous error messages for more information.
AMQ6685E
It is not permitted to execute the command for key <insert_3>.
Severity
20 : Error
Explanation
IBM MQ has detected that the key supplied is not permitted by the operation. Review the documentation to view the keys that are permitted for the operation requested.
Response
Issue the command again specifying a valid key.
AMQ6686E
CLI input filled allocated buffer.
Severity
20 : Error
Explanation
Input buffer filled. Command will not be executed.
Response
None
AMQ6687W
Please wait while the MQ Management Task is initializing.
Severity
10 : Warning
Explanation
This command will wait until the task responsible for managing the MQ subsystem is initializing.
Response
None.
AMQ6688I
Initializing Replicated HA.
Severity
0 : Informational
Explanation
The initialization task is initializing the Replicated HA subsystem.
Response
None.
AMQ6689W
Reference to a reserved <insert_3> is not allowed.
Severity
10 : Warning
Explanation
Some user and group ids are reserved for use by MQ.
Response
Reserved user and group ids cannot be examined or modified. Choose a different id name.
AMQ6690E
An argument was too long.
Severity
20 : Error
Explanation
An argument supplied to the called function was too long.
During prepareha or crthagrp processing, the partner did not reply within the timeout period.
Severity
10 : Warning
Explanation
Either prepareha or crthagrp did not receive a response from the partner machine within the timeout interval, which is normally 10 minutes.
Response
Ensure that prepareha is run first and crthagrp is run on the partner machine shortly afterwards.
AMQ6693I
The following HA commands are available. Type help <command> for more information.
crthagrp Creates an HA group with a prepared appliance
dlthagrp Deletes an HA group
dsphagrp Displays the status of the appliances in an HA group
dsphalink Displays network link used for replication when HA configured
makehaprimary Resolves a partitioned situation in an HA group
prepareha Prepares an appliance to be part of an HA group
sethagrp Suspends or resumes an appliance in an HA group
Adds a QM to, or removes a QM from, an HA group
sethaint Sets a floating IP address for an HA queue manager
sethalink Sets the replication link used for subsequent HA
configurations
crthakeys Regenerates SSH keys used for HA communication
dsphakeys Displays status of SSH keys used for HA communication
clearhapreferred Clears the preferred appliance for an HA queue manager
sethapreferred Sets the preferred appliance for an HA queue manager
Severity
0 : Informational
Explanation
This message is issued when a user types help ha within the IBM MQ CLI.
Response
None.
AMQ6694I
Usage: mqsysinit -d <devicePath>
Path to block device for raid array.
Severity
0 : Informational
Explanation
This shows the correct usage for mqsysinit.
Response
None.
AMQ6695I
Usage: mqsysterm -d <devicePath>
Path to block device for raid array.
Severity
0 : Informational
Explanation
This shows the correct usage for the mqsysterm.
Response
None.
AMQ6696I
This command will erase all data including all queue manager data. Are you sure you wish to continue (yes/no)?
Severity
0 : Informational
Response
None.
AMQ6697E
This command cannot be executed while the MQ Daemon task is initializing. Please wait for a short time and then retry the command.
Severity
20 : Error
Explanation
The MQ Daemon task is initailizing and this command cannot be executed until the initialization is complete. The time taken to initialize is dependant upon the number of Queue Managers defined on the system, if Replicated HA is in use, and the connection to the HA partner.
Response
The user should wait for a short time, and then retry the command.
AMQ6698E
<insert_3> file not supplied.
Severity
20 : Error
Explanation
The program requires a file suffix of <insert_3>.
Response
Make sure the file suffix given is what is expected by the program.
AMQ6699I
No default FDC. Type dspmqerr -f -l to list all FDCs.
Severity
0 : Informational
Explanation
dspmqerr doesn't display a default FDC.
Response
None.
AMQ6708E
A disk full condition was encountered when formatting a new log file in location <insert_3>.
Severity
20 : Error
Explanation
The queue manager attempted to format a new log file in directory <insert_3>. The drive or file system containing this directory did not have sufficient free space to contain the new log file.
Response
Increase the amount of space available for log files and retry the request.
AMQ6708E (IBM i)
A disk full condition was encountered when formatting a new log file.
Severity
20 : Error
Explanation
The queue manager attempted to format a new log file in directory <insert_3>. The drive or file system containing this directory did not have sufficient free space to contain the new log file.
Response
Increase the amount of space available for log files and retry the request.
AMQ6709E
The log for the queue manager 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 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. We 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 we need to make the log files themselves bigger, we will have to delete and recreate the queue manager.
AMQ6710E
Queue manager unable to access directory <insert_3>.
Severity
20 : Error
Explanation
The queue manager was unable to access directory <insert_3> for the log. This could be because the directory does not exist, or because the queue manager does not have sufficient authority.
Response
Ensure that the directory exists and that the queue manager has authority to read and write to it. Ensure that the LogPath attribute in the queue manager's configuration file matches the intended log path.
AMQ6720E
A disk quota exhausted condition was encountered when formatting a new log file in location <insert_3>.
Severity
20 : Error
Explanation
The queue manager attempted to format a new log file in directory <insert_3>. The user's quota of disk blocks on the drive or file system containing this directory was exhausted and could not contain the new log file.
Response
Investigate how the disk quota was exhausted and, if necessary, increase the quota for log files and retry the request.
AMQ6721I
Log extents reduced by <insert_3>.
Severity
0 : Informational
Explanation
A request was made to reduce the number of log extents. The request completed successfully and the number of log extents has been reduced by <insert_3>.
Response
None.
AMQ6723W
IBM MQ log extent <insert_3> already archived.
Severity
10 : Warning
Explanation
Log extent <insert_3> had already been archived. No further action is required.
Response
None.
AMQ6723W (IBM i)
IBM MQ journal receiver <insert_3> already archived.
Severity
10 : Warning
Explanation
Journal receiver <insert_3> had already been archived. No further action was required.
Response
None.
AMQ6762E
IBM MQ log extent <insert_3> corrupt.
Severity
20 : Error
Explanation
Log extent <insert_3> has been detected as corrupt and is not valid for use.
Response
Determine how the log extent has become corrupt and take action to ensure that this extent is no longer required for either restart or media recovery. This might require taking media images.
AMQ6767E
Log file <insert_3> could not be opened for use.
Severity
20 : Error
Explanation
Log file <insert_3> could not be opened for use. Possible reasons include the file being missing, the queue manager being denied permission to open the file or the contents of the file being incorrect.
Response
If the log file was required to start the queue manager, ensure that the log file exists and that the queue manager is able to read from and write to it. If the log file was required to recreate an object from its media image and we do not have a copy of the required log file, delete the object instead of recreating it.
AMQ6774E
Log file <insert_3> did not contain the requested log record.
Severity
20 : Error
Explanation
Log file <insert_3> does not contain the log record whose LSN is <insert_4>. This is because the log file numbers have wrapped and the log file name <insert_3> has been reused by a newer file. Once a log file name has been reused, it is not possible to access the data in the previous versions of the file to use this name. The operation which requested this log record cannot be completed.
AMQ6776E (Windows)
Queue manager recovery log not correctly configured for advanced format disk.
Severity
20 : Error
Explanation
The queue manager recovery log is located on an advanced format disk, however the recovery log is not configured correctly to provide full write integrity with advanced format disks. Advanced format disks require 4KB alignment for reliable writing, but the current queue manager was created at an MQ version that did not yet support advanced format disks and did not enforce 4KB alignment.
Response
MQ has only supported placing the recovery log on an advanced format disk since MQ V9.0.4. MQ V9.0.4 introduced the MIGMQLOG command that can be used to migrate a pre-existing queue manager recovery log to a format suitable for advanced format disks. Any queue manager created on a version of V9.0.4 or higher will have been created with a recovery log suitable for advanced format disks. Investigate migrating the queue manager recovery log, using the MIGMQLOG command, to a format suitable for the current log location.
AMQ6782I
The log file numbers have wrapped.
Severity
0 : Informational
Explanation
Each log file formatted is assigned a number which makes up part of its file name. The numbers are allocated sequentially and consist of seven digits giving a maximum of 10 million different log file names. Once all available numbers have been allocated, the queue manager again starts allocating numbers starting from zero. Once a file number has been re-allocated, we can no longer access data in the previous log files allocated the same number. The file numbers wrapped at log sequence number <insert_3>.
Response
We should periodically take media images of all IBM MQ objects. We must ensure that media images of all objects which you may need to recreate do not span more than 10 million log files.
AMQ6901 (IBM i)
IBM MQ for IBM i
AMQ6902 (IBM i)
IBM MQ for IBM i - Samples
AMQ6903E (IBM i)
Installation or uninstallation failed, IBM MQ resources are still active.
Severity
30 : Error
Explanation
An attempt to install or uninstall IBM MQ was unsuccessful because MQ resources from a previous installation of MQ are still active. This failure may indicate that a queue manager from a previous installation of MQ is still running or has active jobs.
Response
Ensure that all queue managers from previous installations of IBM MQ have been quiesced, and that the QMQM subsystem is not active using the WRKSBS and ENDSBS commands. Refer to the installation section in the IBM MQ for IBM i Quick Beginnings publication for further details.
AMQ6904 (IBM i)
Installation of IBM MQ for IBM i failed due to previous release installed.
Explanation
Some releases of IBM MQ for IBM i require migration before a later release can be installed.
Response
If you wish to retain your current MQ information we must step through the migration process - see the Quick Beginnings Manual.
If we do not wish to retain your current MQ information remove the current version of MQ before retrying the install.
AMQ6905I (IBM i)
Found <insert_3> new MQ jobs to end, and <insert_4> MQ jobs currently ending.
Severity
0 : Informational
Explanation
Jobs with locks on library QMQM are ended so that IBM MQ may be deleted or updated.
Response
None.
AMQ6906S (IBM i)
<insert_3> jobs still ending.
Severity
40 : Severe
Explanation
Jobs report state of 'already being deleted' after timeout.
Response
If system is heavily loaded wait and reissue the command CALL QMQM/AMQIQES4 to try to delete jobs using IBM MQ resources. If this message is issued again, issue the command WRKOBJLCK for library QMQM to see which jobs have not been deleted, and end them manually.
AMQ6907I (IBM i)
All IBM MQ pre-requisite PTFs on OS/400 programs are installed.
Severity
0 : Informational
AMQ6908S (IBM i)
IBM MQ pre-requisite PTF <insert_4> for program <insert_3> is not installed.
Severity
40 : Severe
Explanation
PTF <insert_3>-<insert_4> is not installed on system in state 'Permanently applied' 'Temporarily applied' or 'Superseded'. IBM MQ installation will proceed, but we must install the PTF before starting IBM MQ.
Response
Use the command GO CMDPTF to display commands to order and apply the required PTF <insert_3>-<insert_4>..
AMQ6909E (IBM i)
User space recovery failed, IBM MQ is running.
Severity
30 : Error
Explanation
An attempt to recover user space was unsuccessful because MQ was running.
Response
Quiesce IBM MQ for IBM i and try again. See the section on "Quiescing IBM MQ" in the IBM MQ for IBM i Quick Beginnings.
AMQ690A (IBM i)
IBM MQ MQI Client for IBM i
AMQ690B (IBM i)
IBM MQ MQI Client for IBM i -Samples
AMQ690C (IBM i)
IBM MQ
AMQ690D (IBM i)
MQ
AMQ690E (IBM i)
WebSphere
AMQ690F (IBM i)
IBM WebSphere MQ
AMQ6910E (IBM i)
The attempt to quiesce the queue manager failed.
Severity
30 : Error
Explanation
The attempt to quiesce the queue manager was unsuccessful because the current job has locks on library QMQM.
Response
Sign off the current job, sign on and attempt to quiesce the queue manager again. See the section on "Quiescing IBM MQ" in the IBM MQ for IBM i Quick Beginnings.
AMQ6911I (IBM i)
IBM MQ quiesce is performing a RCDMQMIMG, please wait.
Severity
0 : Informational
Explanation
IBM MQ quiesce is performing a Record Object Image (RCDMQMIMG) for all objects. Please wait, there may be some delay until this is completed.
Response
None.
AMQ6912 (IBM i)
IBM MQ Java Messaging and Web Services
AMQ6913 (IBM i)
IBM MQ Java Messaging and Web Services
AMQ6914E (IBM i)
Apply PTF failed, IBM MQ resources are still active.
Severity
30 : Error
Explanation
An attempt to apply PTFs to a IBM MQ installation was unsuccessful because MQ resources are still active. This failure may indicate that one or more queue managers have not been fully quiesced, some MQ resources have not been released, some MQ jobs are still running or a MQ subsystem is still active.
Response
Ensure that all queue managers have been fully quiesced, using the ENDMQM command with ENDCCTJOB(*YES). Ensure that all MQ subsystems (including the QMQM subsystem) are not active using the WRKSBS and ENDSBS commands. Repeat the apply PTF action. Please note - Delete Licensed Program (DLTLICPGM) is not a circumvention for this condition, because the same checks which are listed as a possible cause, will be made before deleting a IBM MQ installation.
AMQ6915E (IBM i)
Remove PTF failed, IBM MQ resources are still active.
Severity
30 : Error
Explanation
An attempt to remove PTFs from a IBM MQ installation was unsuccessful because MQ resources are still active. This failure may indicate that one or more queue managers have not been fully quiesced, some MQ resources have not been released, some MQ jobs are still running or a MQ subsystem is still active.
Response
Ensure that all queue managers have been fully quiesced, using the ENDMQM command with ENDCCTJOB(*YES). Ensure that all MQ subsystems (including the QMQM subsystem) are not active using the WRKSBS and ENDSBS commands. Repeat the remove PTF action. Please note - Delete Licensed Program (DLTLICPGM) is not a circumvention for this condition, because the same checks which are listed as a possible cause, will be made before deleting a IBM MQ installation.
AMQ6916 (IBM i)
IBM MQ for IBM i - Security Policies
AMQ6917 (IBM i)
IBM MQ for IBM i - Web Console and REST API
AMQ691A (IBM i)
IBM MQ_cert_label
AMQ6988I
yes
Severity
0 : Informational
AMQ6988 (IBM i)
Yes
AMQ6989I
no
Severity
0 : Informational
AMQ6989 (IBM i)
No
AMQ6992S (IBM i)
Program <insert_3> parameter error.
Severity
40 : Severe
Explanation
IBM MQ for IBM i program <insert_3> has an incorrect number of parameters, or an error in the parameter value.
Response
Display the job log, using the DSPJOBLOG command, for more information on the problem.
AMQ6993S (IBM i)
Program <insert_3> ended abnormally.
Severity
40 : Severe
Explanation
A IBM MQ for IBM i program, <insert_3>, is ending abnormally.
Response
Display the job log, using the DSPJOBLOG command, for information why the job or subsystem ended abnormally. Correct the error and retry the request.
AMQ6994I (Windows)
5724-H72 (C) Copyright IBM Corp. 1994, <insert_3>.
Severity
0 : Informational
AMQ6995I (IBM i)
xcsFFST has been called; take a look at the job log.
Severity
0 : Informational
AMQ6998S (IBM i)
An internal IBM MQ error has occurred.
Severity
40 : Severe
Explanation
IBM MQ for IBM i is diagnosing an unexpected error.
IBM MQ has experienced an internal failure, from which it could not recover.
Response
Use WRKPRB to check if a problem has been created. If one has, record the problem identifier, and save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. If a problem has not been created, save the job log. Use either the MQ Support site: https://www.ibm.com/support/home/, or IBM Support Assistant (ISA): https://www.ibm.com/support/home/product/C100515X13178X21/other_software/ibm_support_assistant, to see whether a solution is already available. If we are unable to find a match, contact the IBM support center. Do not discard these files until the problem has been resolved.