Distributed queuing messages (CSQX...)
CSQX000IIBM WebSphere MQ for z/OS versionExplanation:This message is issued when the channel initiator starts, and shows the release level.
Severity:0
CSQX001Icsect-name Channel initiator startingExplanation:The channel initiator address space is starting, in response to a START CHINIT command.
Severity:0
System Action:Channel initiator startup processing begins. Message CSQX022I is sent when the startup process has completed.
CSQX002Icsect-name Queue-sharing group is qsg-nameExplanation:This is issued during channel initiator startup processing or in response to the DISPLAY CHINIT command if the queue manager that the channel initiator uses is in a queue-sharing group.
Severity:0
System Action:Processing continues.
CSQX003Icsect-name Obsolete parameter module ignoredExplanation:The START CHINIT command specified a parameter module name using the PARM keyword. The use of a channel initiator parameter module is obsolete, so the name is ignored.
Severity:0
System Action:Processing continues.
System Programmer Response:Channel initiator parameters are specified by queue manager attributes. Use the ALTER QMGR command to set the values you want.
CSQX005Ecsect-name Channel initiator failed to startExplanation:A severe error, as reported in the preceding messages, occurred during channel initiator startup processing.
Severity:8
System Action:The channel initiator started task terminates.
System Programmer Response:Investigate the problem reported in the preceding messages.
CSQX006Ecsect-name Channel initiator failed while stoppingExplanation:A severe error, as reported in the preceding messages, occurred during channel initiator termination processing.
Severity:8
System Action:The channel initiator started task terminates.
System Programmer Response:Investigate the problem reported in the preceding messages.
CSQX007Ecsect-name Unable to connect to queue manager qmgr-name, MQCC=mqcc MQRC=mqrcExplanation:An attempt by the channel initiator to connect to the queue manager was unsuccessful.
Severity:8
System Action:If the error occurred during the channel initiator startup procedure, the channel initiator does not start. In other cases, the component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, or listener) does not start and the function it provides is unavailable; in most cases, the end result is that the channel initiator terminates.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. If you are unable to solve the problem, contact your IBM support center.
CSQX008Ecsect-name Unable to disconnect from queue manager qmgr-name, MQCC=mqcc MQRC=mqrcExplanation:An attempt by the channel initiator to disconnect from the queue manager was unsuccessful.
Severity:4
System Action:Processing continues.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. If you are unable to solve the problem, contact your IBM support center.
CSQX009Icsect-name Channel initiator stoppingExplanation:A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.
Severity:8
System Action:The channel initiator terminates.
System Programmer Response:Investigate the problem reported in the preceding messages.
CSQX010Icsect-name Channel initiator stoppedExplanation:The channel initiator terminated following an error, as reported in the preceding messages.
Severity:0
System Action:None.
CSQX011Icsect-name Client attachment feature availableExplanation:The client attachment feature has been installed, so clients can be attached to and MQI channels can be used with the channel initiator.
Severity:0
System Action:The channel initiator startup processing continues.
CSQX012Ecsect-name Unable to open ddname data setExplanation:The ddname data set could not be opened, as reported in the preceding messages.
Severity:4
System Action:Processing continues, but functions that require the data set will be inhibited. For example, if the exit library data set CSQXLIB cannot be opened, user channel and channel auto-definition exits will not be available, and channels that use them will not start. If the error information data set CSQSNAP cannot be opened, the error information will be lost.
System Programmer Response:Investigate the problem reported in the preceding messages.
CSQX013Icsect-name Address conflict for listener, port port address ip-address, TRPTYPE=TCP INDISP=dispositionExplanation:A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already active for a port and IP address combination that conflicted with the requested port and IP address. If ip-address is '*', all IP addresses were requested.
The port and IP address combination specified must match a combination for which the listener is active. It cannot be a superset or a subset of that combination.
Severity:4
System Action:None.
System Programmer Response:Reissue the command correctly if necessary.
CSQX014Ecsect-name Listener exceeded channel limit, TRPTYPE=trptype INDISP=dispositionExplanation:The number of current channels using the indicated communications system trptype is the maximum allowed. The listener cannot accept an incoming request to start another channel; if the maximum is 0, the listener itself cannot start. (The name of the channel requested cannot be determined because the listener could not accept the request.) Current channels include stopped and retrying channels as well as active channels.
disposition shows which type of incoming requests the listener was handling:
- QMGR
- those directed to the target queue manager
- GROUP
- those directed to the queue-sharing group.
The maximum allowed is specified in the TCPCHL or LU62CHL queue manager attribute respectively, but may be reduced if a dispatcher fails, or if TCP/IP resources are restricted (as reported by message CSQX118I).
Severity:8
System Action:The channel or listener does not start.
System Programmer Response:If the maximum allowed is zero, communications using the indicated system trptype are not allowed, and no such channels can be started. The listener also cannot be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the remote channel, or use the ALTER QMGR command to increase TCPCHL or LU62CHL.
CSQX015Icsect-name started dispatchers started, failed failedExplanation:The channel initiator startup procedure has started the requested number of dispatchers; started dispatchers started successfully and failed dispatchers did not start.
Severity:0
System Action:The channel initiator startup processing continues. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately if some dispatchers did not start.
System Programmer Response:If the message indicates that some dispatchers failed, investigate the problem reported in the preceding messages.
CSQX016Icsect-name Listener already started, TRPTYPE=trptype INDISP=dispositionExplanation:A START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already active.
Severity:0
System Action:None.
CSQX017Icsect-name Listener already started, port port address ip-address, TRPTYPE=TCP INDISP=dispositionExplanation:A START LISTENER command was issued specifying TRPTYPE(TCP) and INDISP(disposition), but that listener was already active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.
Severity:0
System Action:None.
CSQX018Icsect-name Listener already stopped or stopping, TRPTYPE=trptype INDISP=dispositionExplanation:A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already stopped or in the process of stopping.
Severity:0
System Action:None.
CSQX019Icsect-name Listener already stopped or stopping, port port address ip-address, TRPTYPE=TCP INDISP=dispositionExplanation:A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already stopped or in the process of stopping for the requested port and IP address. If ip-address is '*', all IP addresses were requested.
Severity:0
System Action:None.
CSQX020Icsect-name Shared channel recovery completedExplanation:The channel initiator startup procedure has successfully completed the shared channel recovery process, for channels that were owned by itself and for channels that were owned by other queue managers.
Severity:0
System Action:Processing continues.
System Programmer Response:See message CSQM052I issued by the queue manager for more details.
CSQX021Ecsect-name Shared channel recovery errorExplanation:The channel initiator startup procedure did not complete the shared channel recovery process, because an error occurred.
Severity:0
System Action:The recovery process is terminated; some channels may have been recovered, while others have not.
System Programmer Response:See the error messages (such as CSQM053E) issued by the queue manager for more details. When the problem has been resolved, either start any unrecovered channels manually, or restart the channel initiator.
CSQX022Icsect-name Channel initiator initialization completeExplanation:Initialization of the channel initiator completed normally, and the channel initiator is ready for use. Note, however, that processing of the CSQINPX command data set may still be in progress; its completion is shown by message CSQU012I.
Severity:0
System Action:None.
CSQX023Icsect-name Listener started, port port address ip-address, TRPTYPE=TCP INDISP=dispositionExplanation:A START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition). That listener is now active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.
Severity:0
System Action:None.
CSQX024Icsect-name Listener stopped, port port address ip-address, TRPTYPE=TCP INDISP=dispositionExplanation:A STOP LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition). That listener is no longer active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.
Severity:0
System Action:None.
CSQX026Ecsect-name Unable to locate the trace header, RC=12Explanation:The trace formatting routine was unable to locate the trace control information in the trace data space in a dump of the channel initiator address space.
Severity:8
System Action:Formatting terminates.
System Programmer Response:The most likely cause is that the dump has not been produced correctly. Re-create the dump, and try again.
CSQX027Ecsect-name Unable to get storage, RC=return-codeExplanation:An attempt to obtain some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
Severity:8
System Action:The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, listener, repository manager, supervisor, or trace formatter) usually terminates; in many cases, the end result will be that the channel initiator terminates.
System Programmer Response:See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
CSQX028Ecsect-name Unable to free storage, RC=return-codeExplanation:An attempt to release some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
Severity:8
System Action:The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, or listener) usually ignores the error and continues processing.
System Programmer Response:See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
CSQX029Icsect-name Queue manager qmgr-name stopping, MQCC=mqcc MQRC=mqrcExplanation:In response to an MQ API call, the queue manager notified the channel initiator that it is stopping.
Severity:0
System Action:The channel initiator terminates.
System Programmer Response:Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
CSQX030Icsect-name 'type' trace started, assigned trace number tnoExplanation:During channel initiator initialization, a type trace has been started automatically and assigned the trace number tno.
System Action:Processing continues.
CSQX031Ecsect-name Initialization command handler ended abnormally, reason=00sssuuuExplanation:The initialization command handler, which processes the CSQINPX command data set, is ending abnormally. sss is the system completion code, and uuu is the user completion code (both in hexadecimal).
Severity:8
System Action:The initialization command handler ends abnormally, but the channel initiator continues.
System Programmer Response:If a system completion code is shown, see the MVS System Codes manual for information about the problem; the message will normally be preceded by other messages giving additional information.
The most likely cause is erroneous definition of the CSQINPX and CSQOUTX data sets. See the WebSphere MQ for z/OS System Setup Guide for information about the initialization command handler and these data sets. If you are unable to solve the problem, contact your IBM support center.
CSQX032Icsect-name Initialization command handler terminatedExplanation:The initialization command handler, which processes the CSQINPX command data set, was terminated before completing all the commands because the channel initiator is stopping, and so cannot process any more commands.
Severity:4
System Action:The initialization command handler ends.
System Programmer Response:Refer to the CSQOUTX data set for information about the commands that were processed. If the channel initiator is not stopping because of a STOP command, refer to the preceding messages for information about the problem causing it to stop.
See the WebSphere MQ for z/OS System Setup Guide for information about the initialization command handler.
CSQX033Ecsect-name Channel initiator stopping because of errorsExplanation:A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.
Severity:8
System Action:The channel initiator terminates.
System Programmer Response:Investigate the problem reported in the preceding messages.
CSQX034Icsect-name Channel initiator stopping because queue manager is stoppingExplanation:The queue manager notified the channel initiator that it is stopping.
Severity:0
System Action:The channel initiator terminates.
CSQX035Icsect-name Connection to queue manager qmgr-name stopping or broken, MQCC=mqcc MQRC=mqrc