6000-6999 - Common services
See Reading a message for an explanation of how to interpret these messages.
AMQ6004An error occurred during WebSphere MQ initialization or ending.Severity:30 : Severe error
Explanation:An error was detected during initialization or ending of MQ. The MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6005 (iSeries)An error occurred during WebSphere MQ startup.Severity:30 : Severe error
Explanation: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. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6015The operating system is either too busy or has insufficient resources to complete a system request.Severity:30 : Severe error
Explanation:A system request <insert_3> was rejected by the operating system with return code <insert_1>. WebSphere 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.
AMQ6025Program not found.Severity:30 : Severe error
Explanation:WebSphere 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.
AMQ6026A resource shortage prevented the creation of a WebSphere MQ process.Severity:30 : Severe 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.
AMQ6035WebSphere MQ failed, no storage available.Severity:30 : Severe error
Explanation:An internal function of the product attempted to obtain storage, but there was none available.
Response:Stop the product and restart it. If this does not resolve the problem, save the generated output files and contact your IBM support center.
AMQ6037WebSphere MQ was unable to obtain enough storage.Severity:20 : Error
Explanation: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 your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6047Conversion not supported.Severity:30 : Severe error
Explanation:WebSphere MQ is unable to convert string data tagged in CCSID <insert_1> to data in CCSID <insert_2>.
Response:Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system.
AMQ6048DBCS errorSeverity:30 : Severe error
Explanation:WebSphere 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 WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system.
AMQ6049DBCS-only string not valid.Severity:30 : Severe error
Explanation:WebSphere 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 your job or system and change it to one supporting SBCS or mixed character sets. Refer to the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications for character sets and CCSIDs supported.
AMQ6050CCSID error.Severity:30 : Severe error
Explanation:WebSphere MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>.
Response:Check the WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system.
AMQ6051Conversion length error.Severity:30 : Severe error
Explanation:WebSphere MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>, due to an input length error.
AMQ6052Conversion length error.Severity:30 : Severe error
Explanation:WebSphere MQ is unable to convert string data in CCSID <insert_1> to data in CCSID <insert_2>.
AMQ6053CCSID errorSeverity:30 : Severe error
Explanation:WebSphere 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 WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system.
AMQ6064An internal WebSphere MQ error has occurred.Severity:30 : Severe error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6088 (iSeries)An internal WebSphere MQ error has occurred.Severity:40 : Stop Error
Explanation:An internal error occurred when API call <insert_3> was made.
Response:Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6089 (iSeries)WebSphere MQ was unable to display an error message.Severity:30 : Severe error
Explanation: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 you are unable to resolve the problem, contact your IBM support center.
AMQ6090WebSphere MQ was unable to display an error message <insert_6>.Severity:0 : Information
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>.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6091An internal WebSphere MQ error has occurred.Severity:0 : Information
Explanation:Private memory has detected an error, and is abending due to <insert_3>. The error data is <insert_1>.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6092 (Windows)Manual conversion required for CCSID: <insert_1>Severity:0 : Information
Explanation: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.
AMQ6100An internal WebSphere MQ error has occurred.Severity:0 : Information
Explanation:MQ has detected an error, and is abending due to <insert_3>. The error data is <insert_1>.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6103 (iSeries)WebSphere MQ job submission error.Severity:30 : Severe error
Explanation:WebSphere MQ is unable to submit job <insert_3>.
AMQ6107CCSID not supported.Severity:30 : Severe error
Explanation:WebSphere 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 WebSphere MQ Application Programming Reference Appendix and the appropriate National Language Support publications to see if the CCSIDs are supported by your system.
AMQ6109An internal WebSphere MQ error has occurred.Severity:30 : Severe error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6110An internal WebSphere MQ error has occurred.Severity:30 : Severe error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6112 (iSeries)WebSphere MQ CCSID <insert_1> is using a default value.Severity:10 : Warning
Explanation:When initializing WebSphere 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.
AMQ6114 (iSeries)An internal WebSphere MQ error has occurred.Severity:30 : Severe error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6115An internal WebSphere MQ error has occurred.Severity:10 : Warning
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6118An internal WebSphere MQ error has occurred (<insert_1>)Severity:40 : Stop Error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6119An internal WebSphere MQ error has occurred (<insert_3>)Severity:40 : Stop Error
Explanation:MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6120An internal WebSphere MQ error has occurred.Severity:40 : Stop Error
Explanation:An error has been detected, and the MQ error recording routine has been called.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6121An internal WebSphere MQ error has occurred.Severity:40 : Stop Error
Explanation: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 your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6122An internal WebSphere MQ error has occurred.Severity:40 : Stop 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 your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6125An internal WebSphere MQ error has occurred.Severity:40 : Stop Error
Explanation:An internal error has occurred with identifier <insert_1>. This message is issued in association with other messages.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6134 (iSeries)Trace continues in bufferSeverity:0 : Information
AMQ6135 (iSeries)Stopping early traceSeverity:0 : Information
AMQ6136 (iSeries)Stopping early trace <insert_3> system timeSeverity:0 : Information
AMQ6137 (iSeries)Resuming MQI traceSeverity:0 : Information
AMQ6138 (iSeries)Resuming MQI trace <insert_3> system timeSeverity:0 : Information
AMQ6139 (iSeries)Stopping MQI traceSeverity:0 : Information
AMQ6140 (iSeries)Stopping MQI trace <insert_3> system timeSeverity:0 : Information
AMQ6141 (iSeries)Starting MQI traceSeverity:0 : Information
AMQ6142 (iSeries)Starting MQI trace <insert_3> system timeSeverity:0 : Information
AMQ6143 (iSeries)WebSphere MQ function stackSeverity:0 : Information
AMQ6144 (iSeries)No stack availableSeverity:0 : Information
AMQ6145 (iSeries)Terminating MQI traceSeverity:0 : Information
AMQ6146 (iSeries)Entering end job processingSeverity:0 : Information
AMQ6147 (iSeries)Terminating MQI trace <insert_3> system timeSeverity:0 : Information
AMQ6148An internal WebSphere MQ error has occurred.Severity:0 : Information
Explanation:MQ has detected an error, and is abending due to <insert_3>. The error data is <insert_1>.
Response:Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
AMQ6150 (iSeries)WebSphere MQ resource <insert_3> busy.Severity:30 : Severe 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.
AMQ6150 (Windows)WebSphere MQ semaphore is busy.Severity:10 : Warning
Explanation:WebSphere 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 your system is locked then investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST.
AMQ6151 (iSeries)WebSphere MQ resource <insert_3> released.Severity:30 : Severe 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.
AMQ6152 (iSeries)WebSphere MQ failed to end commitment control while attempting to quiesce a queue manager.Severity: