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.
0
One of the following commands has been issued incorrectly:
The value of n must be in the range 0 through 15.
8
The command is ignored.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
One of the following commands has been issued incorrectly:
The value of x must be in the range 0 through 99.
8
The command is ignored.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
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.
8
The queue manager terminates abnormally.
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.
One of the following commands has been issued incorrectly:
The value of x must be in the range 100 through 500 000.
8
The command is ignored.
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.
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.
8
Restart is abnormally terminated with completion code X'5C6' and reason code X'00D70102'.
Change the started task JCL procedure xxxxMSTR for the queue manager to name the appropriate bootstrap and log data sets.
This message gives the buffer pool used by the specified page set.
It is sent in response to a DEFINE PSID(x) command.
0
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.
0
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.
0
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.
8
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.
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.
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.
8
Queue manager shutdown continues, but some information might be missing from the page set. This will be corrected from the log during restart.
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.
Page set psid has been successfully dynamically expanded by creating a new extent.
0
The new extent is formatted; message CSQI031I will be issued when formatting completes successfully.
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.
An attempt to expand a page set dynamically was unsuccessful.
8
Processing continues
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.
An attempt to expand page set psid dynamically was unsuccessful because the maximum number of extents had been used.
8
The page set cannot be extended again. When the messages on the full page set are retrieved, the existing space will be reused.
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, you 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.
Page set psid is being expanded dynamically, by creating a new extent.
0
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).
A checkpoint is being taken for all defined buffer pools.
0
A checkpoint has been successfully taken for buffer pool n.
0
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.
8
Processing continues.
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.
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.
0
Processing continues.
If the media recovery and checkpoint RBAs differ, contact your IBM support center.
A command has been issued specifying a buffer pool that is not defined.
8
The command is ignored.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
The size of the specified buffer pool has been successfully changed.
0
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,
0
A command has been issued specifying a page set that is not available to the queue manager.
8
The command is ignored.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
The page set specified is referenced by a storage class, and so cannot be deleted.
8
The command is ignored.
Change or delete all the storage classes that reference the page set, and then reissue the command.
The page set specified has buffers that are still in use, and so cannot be deleted.
8
The command is ignored.
Wait until three checkpoints have been completed, and then reissue the command.
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.
0
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.
8
The page set is deleted and is no longer available for use.
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.
An error occurred while deleting the specified page set.
8
Processing continues.
See the preceding error messages for more information about the error.
The specified page set has been successfully deleted.
0
An error occurred while deleting the specified page set.
8
The page set is not deleted, and is still available for use.
Note the error code and contact your IBM support center.
The specified page set is already in use by the queue manager, and so cannot be dynamically defined.
8
The command is ignored.
See the WebSphere MQ Script (MQSC) Command Reference manual for information about the command, and reissue the command correctly.
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.
8
The page set is not defined.
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.
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).
8
The page set is not defined.
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.
A VSAM error occurred when trying to open the page set data set.
8
The page set is not defined.
See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, reissue the request.
A VSAM error occurred when trying to get a record from the page set data set.
8
The page set is not defined.
See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, reissue the request.
A VSAM error occurred when trying to close the page set data set.
8
The page set is not defined.
See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, reissue the request.
An error occurred while defining the specified page set.
8
Processing continues.
See the preceding error messages for more information about the error.
The specified page set has been successfully defined.
0
The buffer pool specified is in use by a page set, and so cannot be deleted.
8
The command is ignored.
Change or delete all the page sets that reference the buffer pool, and then reissue the command.
The buffer pool specified is not in use by any page set, and so cannot have buffers added or removed.
8
The command is ignored.
Define at least one page set that references the buffer pool, and then reissue the command, or delete the buffer pool.
The buffer pool specified is being altered or deleted by another command.
8
The command is ignored.
Wait until the other command has completed processing, and then reissue the command if appropriate.
One or more page sets are unavailable, as reported in the preceding messages; they are either offline having been used previously, not defined, or otherwise inaccessible. For example, MQ may have attempted to open a page set at restart, but failed perhaps because it was in use by another application.
This situation can cause problems, so you should take action to correct it as soon as possible.
4
Processing continues.
Use the DISPLAY USAGE command to get a list of the unavailable page sets.
If a previously-used page set is required, bring it online; this can be done without stopping the queue manager. Use the FORMAT function of the utility program CSQUTIL, specifying TYPE(REPLACE). Then issue a DEFINE PSID command to bring the page set back into use. Note that all units of recovery (except those that are indoubt) that involved the offline page set will have been backed out by the queue manager when the page set was last used. These indoubt units of recovery may be resolved once the page set is back in use by the queue manager.
If a page set is not required, issue a DELETE PSID command to remove it. Also remove any DEFINE PSID command for it from the CSQINP1 initialization input data set.
A VSAM error occurred when trying to get a record from the page set data set.
8
The page set is not defined.
See the DFSMS/MVS Macro Instructions for Data Sets for information about the return and reason codes from VSAM. If necessary, reissue the request.
The page set data set was formatted using TYPE(REPLACE), and as such may contain messages for a specific page set n. It cannot be added dynamically with a different page set identifier.
8
The page set is not defined.
Reissue the command specifying the correct data set and page set. If you intended adding a previously unused page set, reformat the data set with use the FORMAT function of the utility program CSQUTIL, specifying TYPE(RECOVER).
The size of the specified buffer pool has not been changed as requested because insufficient storage is available.
4
The DISPLAY USAGE command can be used to determine the current sizes of all buffer pools defined to the system. It may be possible to reduce the size of other buffer pools, so freeing storage, which can then be assigned to this buffer pool by reissuing the command.
The size of the specified buffer pool has been changed. The number of buffers is not that requested because, for example, insufficient storage is available.
4
The size of the specified buffer pool has not been changed. This could be because the number of buffers requested was the same as the existing size, or because there was insufficient storage available to change the size (as shown by preceding message CSQP051I).
0
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0414 |