6000-6999 - Common services

 

See Reading a message for an explanation of how to interpret these messages.

AMQ6004
An 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.

AMQ6015
The 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.

AMQ6025
Program 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.

AMQ6026
A 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.

AMQ6035
WebSphere 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.

AMQ6037
WebSphere 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.

AMQ6047
Conversion 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.

AMQ6048
DBCS error
Severity:

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.

AMQ6049
DBCS-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.

AMQ6050
CCSID 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.

AMQ6051
Conversion 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.

AMQ6052
Conversion 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>.

AMQ6053
CCSID 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:

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.

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

AMQ6090
WebSphere 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.

AMQ6091
An 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.

AMQ6100
An 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>.

AMQ6107
CCSID 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.

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

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

AMQ6115
An 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.

AMQ6118
An 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.

AMQ6119
An 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.

AMQ6120
An 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.

AMQ6121
An 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.

AMQ6122
An 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.

AMQ6125
An 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 buffer
Severity:

0 : Information

AMQ6135 (iSeries)
Stopping early trace
Severity:

0 : Information

AMQ6136 (iSeries)
Stopping early trace <insert_3> system time
Severity:

0 : Information

AMQ6137 (iSeries)
Resuming MQI trace
Severity:

0 : Information

AMQ6138 (iSeries)
Resuming MQI trace <insert_3> system time
Severity:

0 : Information

AMQ6139 (iSeries)
Stopping MQI trace
Severity:

0 : Information

AMQ6140 (iSeries)
Stopping MQI trace <insert_3> system time
Severity:

0 : Information

AMQ6141 (iSeries)
Starting MQI trace
Severity:

0 : Information

AMQ6142 (iSeries)
Starting MQI trace <insert_3> system time
Severity:

0 : Information

AMQ6143 (iSeries)
WebSphere MQ function stack
Severity:

0 : Information

AMQ6144 (iSeries)
No stack available
Severity:

0 : Information

AMQ6145 (iSeries)
Terminating MQI trace
Severity:

0 : Information

AMQ6146 (iSeries)
Entering end job processing
Severity:

0 : Information

AMQ6147 (iSeries)
Terminating MQI trace <insert_3> system time
Severity:

0 : Information

AMQ6148
An 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:

30 : Severe error

Explanation:

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

AMQ6153 (iSeries)
The attempt to quiesce queue manager <insert_3> failed
Severity:

30 : Severe 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.

AMQ6154 (iSeries)
Queue manager <insert_3> has been quiesced.
Severity:

0 : Information

Explanation:

The queue manager has been successfully quiesced.

Response:

None.

AMQ6158 (iSeries)
SBCS CCSID not found.
Severity:

30 : Severe error

Explanation:

WebSphere MQ is unable to find an SBCS CCSID which corresponds to mixed DBCS-SBCS CCSID <insert_1>.

Response:

Check the CCSID of your 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 contact your IBM support center.

AMQ6159 (iSeries)
WebSphere MQ job submission error.
Severity:

30 : Severe error

Explanation:

WebSphere MQ for iSeries 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.

AMQ6160
EXPLANATION:
Severity:

0 : Information

AMQ6161
ACTION:
Severity:

0 : Information

AMQ6162
An error has occurred reading an INI file.
Severity:

20 : Error

Explanation:

An error has occurred when reading the MQS.INI file or a queue manager QM.INI file.

Response:

If you have been changing the INI file content check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ6162 (Windows)
An error occurred when reading the configuration data.
Severity:

20 : Error

Explanation:

An error has occurred when reading the configuration data.

Response:

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

AMQ6163
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 you have been changing the INI file permissions check and correct the change. If you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ6163 (Windows)
An error has occurred locking the configuration data.
Severity:

10 : Warning

Explanation:

An error has occurred locking the configuration data.

Response:

If you have changed the the registry permissions, check and correct the change. If you have not changed the registry, 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.

AMQ6164
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 you have been changing the INI file content check and correct the change.

AMQ6164 (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 you have changed the configuration data, check and correct the change.

AMQ6165
Unable 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 you have been changing the INI file permissions check and correct the change.

AMQ6165 (Windows)
Unable to access the configuration data.
Severity:

10 : Warning

Explanation:

Access to the configuration data is denied.

Response:

If you have changed the configuration data permissions, check and correct the changes.

AMQ6166
An INI file is missing.
Severity:

20 : Error

Explanation:

The MQS.INI file or a queue manager QM.INI file is missing.

Response:

If you have been changing the INI file recover the previous file and retry the operation.

AMQ6166 (Windows)
An entry in the configuration data is missing.
Severity:

20 : Error

Explanation:

A required entry in the configuration data is missing.

Response:

If you have changed the configuration data, recover the previous configuration data and retry the operation.

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

AMQ6173
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 /var/mqm/conv/table/ccsid.tbl.

Response:

None.

AMQ6174
The library <insert_3> was not found. The queue manager will continue without this module.
Severity:

0 : Information

Explanation:

The dynamically loadable library <insert_3> was not found.

Response:

Check that the file exists and is either fully qualified or is in the appropriate directory.

AMQ6174 (iSeries)
The library was not found.
Severity:

0 : Information

Explanation:

The dynamically loadable file <insert_3> was not found. The queue manager will continue without this module.

Response:

Check that the file exists and is either fully qualified or is in the appropriate directory.

AMQ6174 (Unix)
The dynamically loadable shared library <insert_3> was not found. The system returned error number <insert_2> and error message <insert_4>. The queue manager will continue without this module.
Severity:

0 : Information

Explanation:

This message applies to UNIX systems. The shared library <insert_3> was not found.

Response:

Check that the file exists, and is either fully qualified or is in the appropriate director, also check the file access permissions.

AMQ6175 (AIX)
The system could not dynamically load the shared library <insert_3>. The system returned error number <insert_2> and error message <insert_4>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6175 (Unix)
The system could not dynamically load the shared library <insert_3>. The system returned error message <insert_4>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6175 (Windows)
The system could not dynamically load the library <insert_3>. The system return code was <insert_1>. The queue manager will continue without this module.
Severity:

30 : Severe error

Explanation:

This message applies to Windows NT and Windows 2000 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 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.

AMQ6177 (Windows)
An 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:

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

AMQ6179
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:

30 : Severe 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.

AMQ6179 (Unix)
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:

30 : Severe 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.

AMQ6180 (Windows)
Default conversion 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 default CCSIDs specified in the ccsid.tbl file and make sure that conversion is supported between these CCSIDs.

AMQ6182
Error found in line <insert_1> of ccsid.tbl
Severity:

30 : Severe error

Explanation:

Line <insert_1> contains and 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.

AMQ6183
An internal WebSphere MQ error has occurred.
Severity:

10 : Warning

Explanation:

An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process <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.

AMQ6184
An internal WebSphere MQ error has occurred on queue manager <insert_3>.
Severity:

10 : Warning

Explanation:

An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process <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.

AMQ6184 (iSeries)
An internal WebSphere MQ error has occurred.
Severity:

10 : Warning

Explanation:

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

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.

AMQ6187
User is not authorized for RestrictedMode queue manager.
Severity:

40 : Stop Error

Explanation:

All users must be in the RestrictedMode application_group.

AMQ6188 (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:

30 : Severe 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.

AMQ6188 (Unix)
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:

30 : Severe 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.

AMQ6188 (Windows)
The system could not dynamically load the library <insert_3> due to a problem with the dll. The errno was <insert_1>. The queue manager will continue without this module.
Severity:

30 : Severe error

Explanation:

This message applies to Windows NT and Windows 2000 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.

AMQ6190 (Windows)
Program <insert_3> not found.
Severity:

30 : Severe error

Explanation:

The program <insert_3> cannot be found.

Response:

Check that the program specified is available on your system. If the program name is not fully qualified, ensure that the PATH environment variable includes the directory where the program is located.

AMQ6191 (Windows)
Program <insert_3> failed to start, return code <insert_1>.
Severity:

30 : Severe 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 your system, and that sufficient system resources are available. Where applicable, verify that the user is authorized to run the program.

AMQ6192 (Windows)
IBM WebSphere MQ Utilities
Severity:

0 : Information

AMQ6193 (Windows)
The registry entry <insert_3> was not found.
Severity:

20 : Error

Explanation:

WebSphere MQ for Windows NT and Windows 2000 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.

AMQ6196
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 you have not changed the INI file, use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ6207 (AIX)
Failed to attach shared memory segment as Segment table is Full.
Severity:

20 : Error

Explanation:

When running in native mode an application may attach only 10 shared memory segments. The application which issued this message attempted to exceed this number. By setting the environment variable EXTSHM=ON this limit can be removed. Further explanation on using this variable and other options available, may be found in the documentation.

Response:

Either reduce the number of segments to which your application needs to attach or set the EXTSHM=ON variable in your environment before starting the application.

AMQ6208
<insert_3>
Severity:

10 : Warning

Explanation:

<insert_4>

Response:

<insert_5>

AMQ6209
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 WebSphere MQ.

Response:

Determine the source of the signal and prevent it from re-occurring.

AMQ6212
Failed to load Library <insert_3> as C++ environment is not initialised.
Severity:

10 : Warning

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.

AMQ6218 (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, WebSphere 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 your environment.

AMQ6230
Message <insert_3> suppressed <insert_1> times in the last <insert_4> seconds.
Severity:

20 : Error

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 you should alter the definition of the SuppressMessage attribute in the Queue Manager configuration.

AMQ6231 (Unix)
Usage: mqchkdir <insert_-a | -m QMgrName> [-f]
Severity:

20 : Error

Explanation:

An incorrect option was specified on the command line for the command.

Response:

Reissue the command specifying the correct parameters.

AMQ6232 (Unix)
Operating 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.

AMQ6233 (Unix)
Operating 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.

AMQ6234 (Unix)
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.

AMQ6235 (Unix)
Directory <insert_3> missing.
Severity:

20 : Error

Explanation:

The identified directory is missing.

Response:

Reissue the command selecting the option to create missing directories.

AMQ6236 (Unix)
Missing directory <insert_3> has been created.
Severity:

20 : Error

Explanation:

The identified directory was missing but has been created.

Response:

None

AMQ6237 (Unix)
File <insert_3> missing.
Severity:

20 : Error

Explanation:

The identified file is missing.

Response:

Reissue the command selecting the option to create missing files.

AMQ6238 (Unix)
Missing file <insert_3> has been created.
Severity:

20 : Error

Explanation:

The identified file was missing but has been created.

Response:

None

AMQ6239 (Unix)
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.

AMQ6240 (Unix)
You must be an operating system superuser to run this command.
Severity:

20 : Error

Explanation:

In irder to run this command be logged on as a user with superuser privelages.

Response:

Log in as an appropriate user and reissue the command.

AMQ6241 (Unix)
The filesystem object <insert_3> is a symbolic link.
Severity:

20 : Error

Explanation:

While checking the filesystem, an object was found which is a symbolic link.

Response:

This is not an error however you should verify that the symbolic link is expected and that the destination of the symbolic link is correct.

AMQ6242 (Unix)
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 owership.

AMQ6243 (Unix)
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 owership.

AMQ6244 (Unix)
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 owership.

AMQ6245 (Unix)
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.

AMQ6251 (Unix)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6252 (Unix)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6253 (Unix)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6254 (Unix)
The system could not dynamically load the shared library <insert_3>, library <insert_4> has been used instead.
Severity:

0 : Information

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 /var/mqm/exits; 64-bit libraries in /var/mqm/exits64.

AMQ6255 (Unix)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6256 (Unix)
The system could not dynamically load the shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6257
Message suppression enabled for message numbers (<insert_3>).
Severity:

0 : Information

Explanation:

The message contain's a list of message id's for which entries repeated within the <insert_1> suppression interval will be suppressed.

Response:

If you wish to see all occurrences of these messages you should alter the definition of the SuppressMessage attribute in the Queue Manager configuration.

AMQ6258
Message exclusion enabled for message numbers (<insert_3>).
Severity:

0 : Information

Explanation:

The message contain's a list of message id's which have been excluded. Requests to write these messages to the error log will be discarded.

Response:

If you wish to see instances of these messages you should alter the definition of the ExcludeMessage attribute in the Queue Manager configuration.

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

AMQ6260
Help Topic not found
Severity:

10 : Warning

Explanation:

The requested help topic could not be located.
For further assistance, please refer to the WebSphere MQ manuals.

Response:

Ensure that the WebSphere MQ InfoCenter is installed.

AMQ6261 (Unix)
An exception occurred trying to dynamically load shared library <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6261 (Windows)
An exception occurred trying to load DLL <insert_3>. The queue manager will continue without this module.
Severity:

30 : Severe 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.

AMQ6666 (iSeries)
Required WebSphere MQ system profile(s) can not be accessed.
Severity:

40 : Stop Error

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 WebSphere MQ system administrator.

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

AMQ6708 (iSeries)
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.

AMQ6709
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, you will have to delete and recreate the queue manager.

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

AMQ6767
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 you do not have a copy of the required log file, delete the object instead of recreating it.

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

AMQ6782
The log file numbers have wrapped.
Severity:

0 : Information

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:

You should periodically take media images of all WebSphere MQ objects. You must ensure that media images of all objects which you may need to recreate do not span more than 10 million log files.

AMQ6901 (iSeries)
WebSphere MQ for iSeries
AMQ6902 (iSeries)
WebSphere MQ for iSeries - Samples
AMQ6903 (iSeries)
Installation failed, WebSphere MQ resources are still active.
Severity:

30 : Severe error

Explanation:

An attempt to install WebSphere 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 WebSphere 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 WebSphere MQ for iSeries Quick Beginnings publication for further details.

AMQ6904 (iSeries)
Installation of WebSphere MQ for iSeries failed due to previous release installed.
Explanation:

Some releases of WebSphere MQ for iSeries require migration before a later release can be installed.

Response:


If you wish to retain your current MQ information step through the migration process - see the Quick Beginnings Manual.
If you do not wish to retain your current MQ information remove the current version of MQ before retrying the install.

AMQ6905 (iSeries)
Found <insert_3> new MQ jobs to end, and <insert_4> MQ jobs currently ending.
Severity:

0 : Information

Explanation:

Jobs with locks on library QMQM are ended so that WebSphere MQ may be deleted or updated.

Response:

None.

AMQ6906 (iSeries)
<insert_3> jobs still ending.
Severity:

40 : Stop Error

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

AMQ6907 (iSeries)
All WebSphere MQ pre-requisite PTFs on OS/400 programs are installed.
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ6908 (iSeries)
WebSphere MQ pre-requisite PTF <insert_4> for program <insert_3> is not installed.
Severity:

40 : Stop Error

Explanation:

PTF <insert_3>-<insert_4> is not installed on system in state 'Permanently applied' 'Temporarily applied' or 'Superseded'. WebSphere MQ installation will proceed, but install the PTF before starting WebSphere MQ.

Response:

Use the command GO CMDPTF to display commands to order and apply the required PTF <insert_3>-<insert_4>..

AMQ6909 (iSeries)
User space recovery failed, WebSphere MQ is running.
Severity:

30 : Severe error

Explanation:

An attempt to recover user space was unsuccessful because MQ was running.

Response:

Quiesce WebSphere MQ for iSeries and try again. See the section on "Quiescing WebSphere MQ" in the WebSphere MQ for iSeries Quick Beginnings.

AMQ6910 (iSeries)
The attempt to quiesce the queue manager failed.
Severity:

30 : Severe 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 WebSphere MQ" in the WebSphere MQ for iSeries Quick Beginnings.

AMQ6911 (iSeries)
WebSphere MQ quiesce is performing a RCDMQMIMG, please wait.
Severity:

0 : Information

Explanation:

WebSphere 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 (iSeries)
WebSphere MQ for iSeries - Java
AMQ6913 (iSeries)
WebSphere MQ for iSeries - Java samples
AMQ6988
yes
Severity:

0 : Information

AMQ6988 (iSeries)
Yes
AMQ6989
no
Severity:

0 : Information

AMQ6989 (iSeries)
No
AMQ6992 (iSeries)
Program <insert_3> parameter error.
Severity:

40 : Stop Error

Explanation:

WebSphere MQ for iSeries 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.

AMQ6993 (iSeries)
Program <insert_3> ended abnormally.
Severity:

40 : Stop Error

Explanation:

A WebSphere MQ for iSeries 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.

AMQ6994 (Windows)
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ6995 (iSeries)
xcsFFST has been called; take a look at the job log.
Severity:

0 : Information

AMQ6998 (iSeries)
An internal WebSphere MQ error has occurred.
Severity:

40 : Stop Error

Explanation:

WebSphere MQ for iSeries is diagnosing an unexpected error.

Response:

Save the job log, and contact your IBM support center.

AMQ6999 (iSeries)
An internal WebSphere MQ error has occurred.
Severity:

0 : Information

Explanation:

WebSphere 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. Contact your IBM support center. Do not discard these files until the problem has been resolved.