This message is issued when the queue manager starts, and shows the release level.
The START QMGR command is accepted. System parameter values will be taken from the module parm-name. This message is issued to the z/OS console at which the START command was issued. Message CSQY022I is sent when the queue manager startup process has completed.
Queue manager startup processing begins.
The STOP QMGR command is accepted. Message CSQ9022I is issued when the queue manager shutdown process has completed. The message is issued either to the originator of the STOP QMGR command, or to the z/OS console from which the START QMGR command was received.
Queue manager shutdown is initiated.
The START QMGR command has not been accepted, because the queue manager is active. Message CSQ9023E is issued after this message.
The STOP QMGR command has not been accepted either because the queue manager shutdown is in progress for the specified option (QUIESCE or FORCE), or because the QUIESCE option was specified after a FORCE option had been accepted previously. Message CSQ9023E is issued after this message.
Queue manager shutdown continues.
The queue manager can be started only by a START QMGR command.
Queue manager startup is terminated.
Start the queue manager using the START QMGR command, and reenter the rejected command.
The queue manager initialization procedures found that a module had an invalid AMODE or RMODE attribute when it was loaded. module-name is the name of the load module with an invalid addressing or residency mode.
Queue manager startup terminates abnormally.
Notify the system programmer of the problem.
Verify that all installation and maintenance activities against WebSphere MQ have been done correctly. If you are unable to correct the problem, contact your IBM support center.
The STOP QMGR command has not been accepted because startup has not completed to the point where shutdown can occur. Message CSQ9023E is issued after this message.
Queue manager startup continues, and the STOP QMGR command is ignored.
Reissue the STOP QMGR command after startup has completed.
This message is issued to record who issued the command to stop WebSphere MQ, and what type of stop it was. verb-name might include the command prefix (CPF). This depends on how the command was entered.
The named load module is not at the correct level for the version of the queue manager that was being used.
If detected by the queue manager, startup terminates abnormally with reason code X'00E80161'. If detected by the channel initiator (module-name is CSQXJST), it does not start.
Notify the system programmer.
Verify that the correct WebSphere MQ program libraries are being used (for the queue manager or channel initiator as appropriate) and that all installation and maintenance activities against WebSphere MQ have been done correctly. If the early processing program is incorrect (module-name is CSQ3EPX), refresh it by issuing the REFRESH QMGR TYPE(EARLY) command.
If you are unable to correct the problem, contact your IBM support center.
Command prefix registration failed because the command prefix (CPF) contains invalid characters.
The queue manager does not start.
Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.
Command prefix registration failed because the queue manager name used as the owner of the command prefix (CPF) contains invalid characters.
The queue manager does not start.
Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.
Command prefix registration failed because the command prefix (CPF) was already defined to z/OS.
The queue manager does not start.
Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.
Command prefix registration failed because the command prefix (CPF) is a subset of a CPF already defined to z/OS.
The queue manager does not start.
Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.
Command prefix registration failed because the command prefix (CPF) is a superset of a CPF already defined to z/OS.
The queue manager does not start.
Reissue the z/OS command SETSSI ADD with the correct CPF parameter. Correct the CPF parameter in the record of SYS1.PARMLIB member IEFSSNxx. See the WebSphere MQ for z/OS System Setup Guide for information about the parameters.
A z/OS error occurred during command prefix (CPF) registration.
The queue manager does not start.
Check the z/OS console for other messages relating to the problem.
The queue manager initialization procedures found that the storage protect key was not 7. The most likely causes are that the program properties table (PPT) entry for CSQYASCP has not been specified correctly, or that the WebSphere MQ program libraries or other libraries in the WebSphere MQ STEPLIB are not APF authorized.
Queue manager startup terminates abnormally with reason code X'00E80162'.
Notify the system programmer.
See the WebSphere MQ for z/OS System Setup Guide for information about specifying the PPT entry for CSQYASCP and about APF authorization for the WebSphere MQ program libraries.
The queue manager initialization procedures found that they were not APF authorized. The most likely cause is that the WebSphere MQ program libraries are not APF authorized.
Queue manager startup terminates abnormally with reason code X'00E80163'.
Notify the system programmer.
See the WebSphere MQ for z/OS System Setup Guide for information about APF authorization for the WebSphere MQ program libraries.
This message is issued when the initialization of the queue manager completes normally, and it is ready for use.
The queue manager is being started with the system parameter values shown in the following messages.
Queue manager startup processing continues.
This series of messages shows the system parameter values that the queue manager is using. (Some values are followed by their internal hexadecimal representation in parentheses.) See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.
Queue manager startup processing continues.
The queue manager is being started with the log parameter values shown in the following messages.
Queue manager startup processing continues.
This series of messages shows the log parameter values that the queue manager is using. See the CSQ6LOGP macro in the WebSphere MQ for z/OS System Setup Guide for information about the log parameters.
Queue manager startup processing continues.
The queue manager is being started with the archive parameter values shown in the following messages.
Queue manager startup processing continues.
This series of messages shows the archive parameter values that the queue manager is using. See the CSQ6ARVP macro in the WebSphere MQ for z/OS System Setup Guide for information about the archive parameters.
Queue manager startup processing continues.
An ARM request (IXCARM REQUEST=request-type) for the specified element failed. rc is the return code and reason is the reason code (both in hexadecimal) from the call.
None.
See the z/OS MVS Programming Sysplex Services Reference manual for information about the return and reason codes from the IXCARM call. If you are unable to solve the problem, contact your IBM support center.
The specified element was successfully registered with ARM.
None.
An attempt to register with ARM failed.
Processing continues, but automatic restart is not available.
See the preceding CSQY200E message for more information about the failure.
An ARM request (IXCARM REQUEST=request-type) was issued but some predecessor element specified in the ARM policy did not issue an ARM READY request within its specified time interval.
Processing continues.
None required. However, if your program cannot run without the predecessor element, some installation-defined action might be necessary.
The specified element was successfully deregistered from ARM.
None.
A STOP QMGR command requested ARM restart, but the queue manager was not registered for ARM.
The queue manager stops normally, but will not be automatically restarted.
Restart the queue manager manually.
During processing for a group connect, a name token services call failed. rc is the return code (in hexadecimal) from the call.
If the failure occurs in the batch adapter (csect-name CSQBCON or CSQBDSC), the application call will fail with a reason code of MQRC_UNEXPECTED_ERROR. Otherwise (csect-name CSQYGRA1), processing continues, but the group connect facility will not be available.
See the MVS Authorized Assembler Services Reference manual for information about the return codes from the name token services call. If you are unable to solve the problem, take a stand-alone system dump and contact your IBM support center.
During initialization for the group connect facility, a new entry could not be added to the name table for this queue manager. The most likely cause is that there is already the maximum of 32 queue managers active in the group.
Processing continues, but this queue manager will not be available for group connection.
Reduce the number of active queue managers and restart this queue manager. If this does not solve the problem, contact your IBM support center.
Displays the amount of virtual storage currently used and available in the extended private region. Both values are displayed in megabytes (1048576 bytes), and are approximations.
Processing continues. Any special actions taken by MQ or that are required will be indicated by the CSQY221I and CSQY222E messages.
No action is required at this time. However, a frequent occurrence of this message may be an indication that the system is operating beyond the optimum region for the current configuation.
The queue manager is running short of virtual storage in the extended private region.
Processing continues. Storage contraction processing is performed, which attempts to remove unused storage from internal subpools so that it can be reused in other subpools. This might be necessary after a temporary need for lots of storage; for example, more than the usual number of messages held on an indexed queue, or an unusually large unit of work being performed.
No action is required at this time. However, a frequent occurrence of this message may be an indication that the system is operating beyond the optimum region for the current configuation.
The queue manager is running critically short of virtual storage in the extended private region. Action should be taken to relieve the situation, and to avoid the possible abnormal termination of the queue manager.
Processing continues. Storage contraction processing has been performed, but the remaining unallocated virtual storage is less than a predetermined safe amount. If storage use continues to increase, the queue manager may terminate abnormally in an unpredictable way.
Virtual storage is over-allocated for the current configuration. The following actions can reduce the virtual storage requirement:
If the problem persists after taking actions described above, it may be an indication of an internal error whereby storage is not freed (a 'storage leak'). If you suspect this, then collect at least two system dumps of the queue manager, separated by an interval of time, and contact your IBM support center.
The queue manager is no longer short of virtual storage in the extended private region.
Processing continues. Storage contraction processing has been performed, and the remaining unallocated virtual storage is more than a predetermined safe amount.
An unsuccessful attempt has been made to issue the message message-id. This message is issued only if the requested message could not be found in the MQ message directory.
8
Processing continues as though the requested message had been issued.
Notify the system programmer.
Use the message number (message-id) and look up the message in this book. If you are using a language other than US English, ensure that you have installed the language feature correctly and that you have the appropriate load library data set concatenations in your job. Apart from that possibility, this is an MQ system problem; see the WebSphere MQ for z/OS Problem Determination Guide.
The message generator was unable to access the routing code initialization parameter defined by the CSQ6SYSP macro. Default values defined by that macro are assumed.
4
Queue manager initialization continues.
Notify the system programmer.
It might be necessary to change the CSQ6SYSP macro. See the WebSphere MQ for z/OS System Setup Guide for information about this macro.
There was insufficient storage available for a system routine. csect-name shows the system routine function:
4
Processing continues, but the function provided by the system routine will be inhibited. For example, if the routine is CSQXLDXS, then user channel exits will not be available, and channels that use them will not start.
If the problem occurs in the queue manager, increase the size of the its address space, or reduce the number of queues, messages, and threads being used.
If the problem occurs in the channel initiator, increase the size of the its address space, or reduce the number of dispatchers, adapter subtasks, SSL server subtasks, and active channels being used.
The system dump routine was unable to issue a dump; the dump identifier was as shown in the message. rr is the return code and ss is the reason code (both in hexadecimal) from the z/OS SDUMPX service.
4
Processing continues.
See the MVS Authorized Assembler Services Reference manual for information about the return code and reason code from the SDUMPX request.
The installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
Queue manager startup processing continues.
The value specified for the parm system parameter is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
The queue manager does not start.
The MQ-IMS bridge cannot operate because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
The MQ-IMS bridge does not start.
The command that was issued is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
The command is ignored.
The value specified for the keyword is not allowed because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
The command is ignored.
The channel cannot be used because the installation and customization options chosen for WebSphere MQ do not allow all functions to be used.
The requested operation fails.
The installation and customization options chosen for WebSphere MQ do not allow all functions to be used. However, the queue manager has run previously without any functional restriction, and so may have objects and attribute settings that are not allowed with the restricted functionality.
In order to continue, these objects must be deleted (which may mean messages are lost) and the attributes must be changed. The queue manager will do this automatically.
Message CSQY341D is issued and the operator's reply is awaited.
The operator has two options:
The installation and customization options chosen for WebSphere MQ have changed, as indicated in the preceding CSQY340E message.
The queue manager waits for the operator's reply
See message CSQY340E.
This message is sent if the operator answers 'Y' to message CSQY341D.
The queue manager deletes the objects and changes the attributes that are not allowed with the restricted functionality.
This message is sent if the operator answers 'N' to message CSQY341D.
The queue manager does not start.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0421 |