Buffer manager messages (CSQP...)
CSQP001IBuffer pool n has k buffersExplanation:This message gives the number of buffers defined for the specified buffer pool.
It is sent in response to a DISPLAY USAGE command for page set information.
Severity:0
CSQP002IBUFFPOOL VALUE OUT OF RANGEExplanation:One of the following commands has been issued incorrectly:
- DEFINE BUFFPOOL(n)
- ALTER BUFFPOOL(n)
- DELETE BUFFPOOL(n)
- DEFINE PSID(x) BUFFPOOL(n)
The value of n must be in the range 0 through 15.
Severity:8
System Action:The command is ignored.
System Programmer Response:See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
CSQP003IPSID VALUE OUT OF RANGEExplanation:One of the following commands has been issued incorrectly:
- DEFINE PSID(x)
- ALTER PSID(x)
- DELETE PSID(x)
The value of x must be in the range 0 through 99.
Severity:8
System Action:The command is ignored.
System Programmer Response:See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
CSQP004Ecsect-name I/O ERROR STATUS ret-code PSID psid RBA rbaExplanation:An I/O error has occurred. ret-code is the return code from the Media Manager, psid is the identifier of the page set for which the error occurred, and rba is the RBA (in hexadecimal) of the record on which the error occurred.
Severity:8
System Action:The queue manager terminates abnormally.
System Programmer Response: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 return code from the Media Manager.
CSQP005IBUFFERS VALUE OUT OF RANGEExplanation:One of the following commands has been issued incorrectly:
- DEFINE BUFFPOOL(n) BUFFERS(x)
- ALTER BUFFPOOL(n) BUFFERS(x)
The value of x must be in the range 100 through 500 000.
Severity:8
System Action:The command is ignored.
System Programmer Response:Reissue the command correctly. The total number of buffers that it is possible to define in all the buffer pools is determined by the amount of storage available in the queue manager address space, and may be less than 500 000.
CSQP006ILOG CHECKPOINT NAME log-name DOES NOT MATCH QUEUE MANAGER NAME qmgr-nameExplanation:An attempt to restart with a log from another queue manager was detected. The name recorded in the log during checkpoint does not match the name of the queue manager using that log for restart.
Severity:8
System Action:Restart is abnormally terminated with completion code X'5C6' and reason code X'00D70102'.
System Programmer Response:Change the started task JCL procedure xxxxMSTR for the queue manager to name the appropriate bootstrap and log data sets.
CSQP007IPage set x uses buffer pool nExplanation:This message gives the buffer pool used by the specified page set.
It is sent in response to a DEFINE PSID(x) command.
Severity:0
CSQP009IPAGE RECOVERY STARTED FOR PAGE SET psid PAGE page-numberExplanation:An incomplete update operation was detected for page page-number of page set psid. The page is being restored to a consistent state from information on the log.
Message CSQP010I will be issued when the page recovery operation has completed.
Severity:0
CSQP010IPAGE RECOVERY COMPLETE FOR PAGE SET psid PAGE page-numberExplanation:An incomplete update operation was detected for page page-number of page set psid. The page has been restored to a consistent state from information on the log.
Severity:0
CSQP011ECONNECT ERROR STATUS ret-code FOR PAGE SET psidExplanation:An attempt to open a page set was unsuccessful. psid is the page set identifier and ret-code is the return code from the Data Facilities Product (DFP) CONNECT function.
This can occur during queue manager startup, where the most likely cause is that there is no DD statement for the page set included in the queue manager started task JCL, or in response to a DEFINE PSID command used to add a page set dynamically.
Severity:8
System Action:If this occurs during queue manager startup, MQ attempts to dynamically allocate the page set and retry the open, on the assumption that the DD statement for the page set is missing. Messages following message CSQI010I at the end of restart indicate whether the dynamic page set allocation was successful, or whether such page sets still remain offline.
If the page set cannot be opened, the queue manager continues running, but you will be unable to access the data in that page set. You could encounter problems during restart, or when attempting to open a queue.
System Programmer Response:If applicable, ensure that there is a DD statement for the page set included in the queue manager started task JCL.
If the page set cannot be opened, 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 return code from the Media Manager.
CSQP012IDISCONNECT ERROR STATUS ret-code FOR PAGE SET psidExplanation:An attempt to close a page set was unsuccessful. psid is the page set identifier and ret-code is the return code from the Media Manager.
Severity:8
System Action:Queue manager shutdown continues, but some information might be missing from the page set. This will be corrected from the log during restart.
System Programmer Response: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 return code from the Media Manager.
CSQP013Icsect-name NEW EXTENT CREATED FOR PAGE SET psid. NEW EXTENT WILL NOW BE FORMATTEDExplanation:Page set psid has been successfully dynamically expanded by creating a new extent.
Severity:0
System Action:The new extent is formatted; message CSQI031I will be issued when formatting completes successfully.
System Programmer Response:The page set can only be expanded 123 times. After this you will have to reallocate the page set using larger primary and secondary extents. For information about how to do this, see the WebSphere MQ for z/OS System Setup Guide.
CSQP014Icsect-name EXPANSION FAILED FOR PAGE SET psid. FUTURE REQUESTS TO EXTEND IT WILL BE REJECTEDExplanation:An attempt to expand a page set dynamically was unsuccessful.
Severity:8
System Action:Processing continues
System Programmer Response:Look for messages from VSAM or DFP that explain why the request was unsuccessful, and do the required actions.
If you have received message IEC070I, and the return code (the first value in that message) is 203, an extend was attempted, but no secondary space allocation quantity was specified. If the value of return code was 204, an extend was attempted, but the maximum number of extents was reached. The maximum number of extents for a VSAM data set cataloged in an ICF catalog is between 119 and 123, depending upon the number of extents (1-5) allocated by DADSM per allocate/extend request.
If you believe that there is sufficient free space that could be used by another secondary extent, contact your IBM support center for assistance.
Note:DFP uses up to five non-contiguous areas of disk to satisfy the total space requirements of a primary or secondary extent. This means, in the worst case of badly fragmented disk space, that you might only get around 22 times the secondary space allocated before you reach the maximum space limit.CSQP016Icsect-name PAGE SET psid HAS REACHED THE MAXIMUM NUMBER OF EXTENTS. IT CANNOT BE EXTENDED AGAINExplanation:An attempt to expand page set psid dynamically was unsuccessful because the maximum number of extents had been used.
Severity:8
System Action:The page set cannot be extended again. When the messages on the full page set are retrieved, the existing space will be reused.
System Programmer Response:Copy the page set to a new page set with larger primary and secondary extents. By defining the page set as a multivolume data set, we can take advantage of the free space on as many disk volumes as possible. See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for more information about page set organization and management.
CSQP017Icsect-name EXPANSION STARTED FOR PAGE SET psidExplanation:Page set psid is being expanded dynamically, by creating a new extent.
Severity:0
System Action:All threads that are currently adding message to page set psid are suspended until the page set expansion completes (this is indicated by message CSQP013I).
CSQP018Icsect-name CHECKPOINT STARTED FOR ALL BUFFER POOLSExplanation:A checkpoint is being taken for all defined buffer pools.
Severity:0
CSQP019Icsect-name CHECKPOINT COMPLETED FOR BUFFER POOL n, pages PAGES WRITTENExplanation:A checkpoint has been successfully taken for buffer pool n.
Severity:0
CSQP020Ecsect-name Buffer pool n is too smallExplanation:Contention is taking place for buffers in a buffer pool. Messages will have to be read from and written to the page sets, which increases the time to process an application request and increases the amount of CPU time used.
Severity:8
System Action:Processing continues.
System Programmer Response:If required, use the ALTER BUFFPOOL command to add more buffers to the buffer pool. Consider first altering other buffer pools to reduce the total number of buffers in use. Refer to the latest CSQY220I message on the z/OS console to see how much virtual storage is free, and hence how many extra buffers may be safely added to a buffer pool. (If you do change the number of buffers in the buffer pool, you should also change the DEFINE BUFFPOOL commands in the CSQINP1 initialization input data set used by the queue manager, so that the changes remain in force when the queue manager is restarted.)
Alternatively, stop the queue manager as soon as possible and increase the number of buffers on the DEFINE BUFFPOOL commands in the CSQINP1 initialization input data set used by the queue manager, and restart the queue manager.
CSQP021IPage set psid new media recovery RBA=rcvry-rba, checkpoint RBA=chkpt-rbaExplanation:During checkpoint processing, buffers have been flushed from the buffer pools to the indicated page set, establishing a new media recovery RBA. This RBA is the point from which log data would be required to perform media recovery for the page set. It should be the same as the checkpoint RBA.
Severity:0
System Action:Processing continues.
System Programmer Response:If the media recovery and checkpoint RBAs differ, contact your IBM support center.
CSQP022IBuffer pool n is not definedExplanation:A command has been issued specifying a buffer pool that is not defined.
Severity:8
System Action:The command is ignored.
System Programmer Response:See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
CSQP023IRequest completed for buffer pool n, now has k buffersExplanation:The size of the specified buffer pool has been successfully changed.
Severity:0
CSQP024IRequest initiated for buffer pool nExplanation:The request to change the buffer pool has been accepted. One of the messages CSQP023I, CSQP052I, or CSQP053I will be sent to the z/OS console when the change is complete,
Severity:0
CSQP025IPage set n is not defined or offlineExplanation:A command has been issued specifying a page set that is not available to the queue manager.
Severity:8
System Action:The command is ignored.
System Programmer Response:See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
CSQP026IPage set n is in use by a storage classExplanation:The page set specified is referenced by a storage class, and so cannot be deleted.
Severity:8
System Action:The command is ignored.
System Programmer Response:Change or delete all the storage classes that reference the page set, and then reissue the command.
CSQP027IPage set n has buffers in useExplanation:The page set specified has buffers that are still in use, and so cannot be deleted.
Severity:8
System Action:The command is ignored.
System Programmer Response:Wait until three checkpoints have been completed, and then reissue the command.
CSQP028IRequest initiated for page set nExplanation:The request to define or delete the page set has been accepted. Message CSQP042I or CSQP032I respectively will be sent to the z/OS console when the change is complete. If the change fails, messages CSQP041E or CSQP031E will be sent.
Severity:0
CSQP030EDeallocation failed for data set dsname, error status=eeeeiiii, SMS reason code=ssssssssExplanation:An error occurred when trying to dynamically deallocate the page set data set. Error status is the error reason code returned by z/OS dynamic allocation.
Severity:8
System Action:The page set is deleted and is no longer available for use.
System Programmer Response:The error status portion of this message contains a 2-byte error code (eeee, S99ERROR) followed by the 2-byte information code (iiii, S99INFO) from the SVC99 request block. If the S99ERROR code indicates an SMS allocation error ('97xx'), then ssssssss contains additional SMS reason code information obtained from S99ERSN. See the MVS Authorized Assembler Services Guide manual for a description of these codes.
CSQP031EPage set n deletion failedExplanation:An error occurred while deleting the specified page set.
Severity:8
System Action:Processing continues.
System Programmer Response:See the preceding error messages for more information about the error.
CSQP032IPage set n deletion completedExplanation:The specified page set has been successfully deleted.
Severity:0
CSQP033EError deleting page set n, error code=rrrExplanation:An error occurred while deleting the specified page set.
Severity:8
System Action:The page set is not deleted, and is still available for use.
System Programmer Response:Note the error code and contact your IBM support center.
CSQP034EPage set n is already definedExplanation:The specified page set is already in use by the queue manager, and so cannot be dynamically defined.
Severity:8
System Action:The command is ignored.
System Programmer Response:See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
CSQP035EAllocation failed for data set dsname, error status=eeeeiiii, SMS reason code=ssssssssExplanation:An error occurred when trying to dynamically allocate the page set data set. Error status is the error reason code returned by z/OS dynamic allocation.
Severity:8
System Action:The page set is not defined.
System Programmer Response:The error status portion of this message contains a 2-byte error code (eeee, S99ERROR) followed by the 2-byte information code (iiii, S99INFO) from the SVC99 request block. If the S99ERROR code indicates an SMS allocation error ('97xx'), then ssssssss contains additional SMS reason code information obtained from S99ERSN. See the MVS Authorized Assembler Services Guide manual for a description of these codes.
CSQP036IData set dsname for page set n is not formatted with RECOVER or REPLACEExplanation:The named page set data set was not formatted correctly. A data set that is to be used for adding a page set dynamically must be one that is newly formatted (using TYPE(RECOVER)), or one that has previously been used to hold messages and has been formatted using TYPE(REPLACE).
Severity:8
System Action:The page set is not defined.
System Programmer Response:Format the data set as required. If you are adding a previously unused page set to the queue manager, use the FORMAT function of the utility program CSQUTIL, specifying TYPE(RECOVER). If the page set was previously used to hold messages, use the FORMAT function specifying TYPE(REPLACE).
In the latter case, if the queue manager terminated abnormally, the formatting may fail, and message CSQU160E will be issued. It is not possible to add such a page set data set dynamically, but the page set can be brought into use again by including it in the started task JCL procedure xxxxMSTR for the queue manager, and then restarting the queue manager.
CSQP037EOPEN failed for page set n, VSAM return code=rc reason code=reasonExplanation:A VSAM error occurred when trying to open the page set data set.
Severity:8
System Action:The page set is not defined.
System Programmer Response:See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, reissue the request.
CSQP038EGET failed for page set n, VSAM return code=rc reason code=reasonExplanation:A VSAM error occurred when trying to get a record from the page set data set.
Severity:8