If a buffer manager reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in Buffer manager problem determination and contact your IBM support center.
An attempt to obtain storage for a buffer manager control block (the PANC) was unsuccessful. This is probably because there is insufficient storage in your region.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Registers 2 and 0 contain the return and reason codes from the STORAGE or GETMAIN request.
Check that you are running in a region that is large enough, and if not, reset your system and restart the queue manager. If this does not resolve the problem, note the register values, and contact your IBM support center.
The name of the queue manager being restarted does not match the name recorded in a prior checkpoint log record.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. This is preceded by message CSQP006I. Register 0 contains the name found in the log record. Register 2 contains the name of the queue manager being restarted.
Change the started task JCL procedure xxxxMSTR for the queue manager to name the appropriate bootstrap and log data sets.
The print log utility, CSQ1LOGP, can be used to view checkpoint records. You might also find the MQ active log data set useful for problem determination.
An attempt to obtain storage for a buffer manager control block (a PSET) was unsuccessful.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Registers 2 and 0 contain the return and reason codes from the STORAGE or GETMAIN request.
Restart the queue manager.
Note the register values, and contact your IBM support center.
An attempt to obtain storage for a buffer manager control block (a BHDR) was unsuccessful.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Registers 2 and 0 contain the return and reason codes from the STORAGE or GETMAIN request.
Restart the queue manager.
Note the register values, and contact your IBM support center.
An internal error has occurred during dynamic page set expansion.
The current page set extend task is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. No further attempt will be made to expand the page set until the queue manager is restarted. Subsequent dynamic page set extend requests for other page sets are processed.
Collect the items listed in Buffer manager problem determination and contact your IBM support center.
An internal error has occurred.
An entry is written to SYS1.LOGREC, and a dump is produced.
Collect the items listed in Buffer manager problem determination and contact your IBM support center.
An attempt to obtain storage for the buffer pool was unsuccessful.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 2 contains the return code from the STORAGE or GETMAIN request. Register 3 contains the buffer pool number.
Provide sufficient storage for the number of buffers specified in the DEFINE BUFFPOOL command.
An internal storage error has occurred.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Registers 2 and 0 contain the return and reason codes from the STORAGE or GETMAIN request. Register 3 contains the buffer pool number.
Provide sufficient storage for the number of buffers specified in the DEFINE BUFFPOOL command.
A critical process could not be started during queue manager initialization. This could be because there is insufficient storage in your region.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the reason code for the error.
Check that you are running in a region that is large enough. If not, reset your system and restart the queue manager. If this does not resolve the problem, note the completion code and the reason code and contact your IBM support center.
A critical process could not be started during queue manager initialization. This could be because there is insufficient storage in your region.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the reason code for the error.
Check that you are running in a region that is large enough. If not, reset your system and restart the queue manager. If this does not resolve the problem, note the completion code and the reason code and contact your IBM support center.
An internal cross-component consistency check failed.
The request is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the value in error.
Note the completion code and the reason code, collect the MQ active log data set, and contact your IBM support center.
An I/O error has occurred.
An entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the Media Manager reason code from an MMCALL call. In some circumstances, the queue manager will terminate. (This depends on the nature of the error, and the page set on which the error occurred.)
Restart the queue manager if necessary.
See the MVS/DFP Diagnosis Reference manual for information about return codes from the Media Manager. If you do not have access to the required manual, contact your IBM support center, quoting the Media Manager reason code.
You might also find the MQ active log data set useful for problem determination.
An internal error has occurred while the queue manager was terminating.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced.
Restart the queue manager.
Collect the items listed in Buffer manager problem determination and contact your IBM support center.
A page was about to be written to a page set, but was found to have improper format. The executing thread is terminated. (If this is the deferred write processor, the queue manager is terminated)
The current execution unit terminates with completion code X'5C6', and a dump is produced.
Restart the queue manager. If the problem persists collect the items listed in Buffer manager problem determination and contact your IBM support center.
No buffers are available to steal. An executing thread needed a buffer in a buffer pool to bring a page in from the page set. The buffer pool is overcommitted, and despite attempts to make more buffers available, including writing pages to the page set, no buffers could be released.
The current execution unit terminates with completion code X'5C6'. The API request is terminated with reason code MQRC_UNEXPECTED_ERROR, with the aim of reducing demand for the buffer pool.
Determine the problem buffer pool from preceding CSQP019I and CSQP020E messages. Review the size of the buffer pool with the DISPLAY USAGE command. Consider increasing the size of the buffer pool using the ALTER BUFFPOOL command.
An unrecoverable error has occurred during check point.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the reason code for the error.
Restart the queue manager.
Note the completion code and the reason code, collect the MQ active log data set, and contact your IBM support center.
An internal consistency check failed.
The request is terminated, an entry is written to SYS1.LOGREC, and a dump is produced.
Note the completion code and the reason code, collect the MQ active log data set, and contact your IBM support center.
A critical process could not be started during queue manager initialization. This could be because there is insufficient storage in your region.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the reason code for the error.
Check that you are running in a region that is large enough. If not, reset your system and restart the queue manager. If this does not resolve the problem, note the completion code and the reason code and contact your IBM support center.
A critical process could not be started during queue manager initialization. This could be because there is insufficient storage in your region.
The queue manager is terminated, an entry is written to SYS1.LOGREC, and a dump is produced. Register 0 contains the reason code for the error.
Check that you are running in a region that is large enough. If not, reset your system and restart the queue manager. If this does not resolve the problem, note the completion code and the reason code and contact your IBM support center.
Collect the following diagnostic items:
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0434 |