This message is issued when the channel initiator starts, and shows the release level.
0
The channel initiator address space is starting, in response to a START CHINIT command.
0
Channel initiator startup processing begins. Message CSQX022I is sent when the startup process has completed.
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.
0
Processing continues.
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.
0
Processing continues.
Channel initiator parameters are specified by queue manager attributes. Use the ALTER QMGR command to set the values you want.
A severe error, as reported in the preceding messages, occurred during channel initiator startup processing.
8
The channel initiator started task terminates.
Investigate the problem reported in the preceding messages.
A severe error, as reported in the preceding messages, occurred during channel initiator termination processing.
8
The channel initiator started task terminates.
Investigate the problem reported in the preceding messages.
An attempt by the channel initiator to connect to the queue manager was unsuccessful.
8
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.
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.
An attempt by the channel initiator to disconnect from the queue manager was unsuccessful.
4
Processing continues.
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.
A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.
8
The channel initiator terminates.
Investigate the problem reported in the preceding messages.
The channel initiator terminated following an error, as reported in the preceding messages.
0
None.
The client attachment feature has been installed, so clients can be attached to and MQI channels can be used with the channel initiator.
0
The channel initiator startup processing continues.
The ddname data set could not be opened, as reported in the preceding messages.
4
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.
Investigate the problem reported in the preceding messages.
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.
4
None.
Reissue the command correctly if necessary.
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:
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).
8
The channel or listener does not start.
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.
The channel initiator startup procedure has started the requested number of dispatchers; started dispatchers started successfully and failed dispatchers did not start.
0
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.
If the message indicates that some dispatchers failed, investigate the problem reported in the preceding messages.
A START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already active.
0
None.
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.
0
None.
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.
0
None.
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.
0
None.
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.
0
Processing continues.
See message CSQM052I issued by the queue manager for more details.
The channel initiator startup procedure did not complete the shared channel recovery process, because an error occurred.
0
The recovery process is terminated; some channels may have been recovered, while others have not.
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.
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.
0
None.
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.
0
None.
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.
0
None.
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.
8
Formatting terminates.
The most likely cause is that the dump has not been produced correctly. Re-create the dump, and try again.
An attempt to obtain some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
8
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.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
An attempt to release some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.
8
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.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.
In response to an MQ API call, the queue manager notified the channel initiator that it is stopping.
0
The channel initiator terminates.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
During channel initiator initialization, a type trace has been started automatically and assigned the trace number tno.
Processing continues.
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).
8
The initialization command handler ends abnormally, but the channel initiator continues.
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.
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.
4
The initialization command handler ends.
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.
A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.
8
The channel initiator terminates.
Investigate the problem reported in the preceding messages.
The queue manager notified the channel initiator that it is stopping.
0
The channel initiator terminates.
In response to an MQ API call, the channel initiator found that its connection to the queue manager was no longer available.
0
The channel initiator terminates.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
An MQOPEN call for name was unsuccessful; name may be a queue name, queue manager name, namelist name, channel name, or authentication information name. (The channel initiator can access channel definitions and authentication information as objects using the MQ API.)
8
The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. The most common cause of the problem will be that the channel and queue definitions are incorrect.
An MQGET call for queue name was unsuccessful.
8
The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
An MQPUT call for queue name was unsuccessful.
8
The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
An MQCLOSE call for name was unsuccessful; name may be a queue name, queue manager name, namelist name, channel name, or authentication information name. (The channel initiator can access channel definitions and authentication information as objects using the MQ API.)
4
Processing continues.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
An MQINQ call for name was unsuccessful; name may be a queue name, queue manager name, namelist name, channel name, or authentication information name. (The channel initiator can access channel definitions and authentication information as objects using the MQ API.)
8
The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
An MQSET call for queue name was unsuccessful.
8
The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
The CTRACE component definitions (for component comp) required by the channel initiator could not be defined. rc is the return code and reason is the reason code (both in hexadecimal) from the z/OS CTRACE service.
8
The channel initiator does not start.
See the MVS Authorized Assembler Services Reference manual for information about the return and reason codes from the CTRACE request. If you are unable to solve the problem, contact your IBM support center.
The CTRACE component definitions (for component comp) used by the channel initiator could not be deleted. rc is the return code and reason is the reason code (both in hexadecimal) from the z/OS CTRACE service.
4
Channel initiator termination processing continues.
See the MVS Authorized Assembler Services Reference manual for information about the return and reason codes from the CTRACE request. If you are unable to solve the problem, contact your IBM support center.
The PC routines required by the channel initiator could not be defined. The reason code reason shows which z/OS service failed:
rc is the return code (in hexadecimal) from the indicated OS/390 service.
8
The channel initiator does not start.
See the MVS Authorized Assembler Services Reference manual for information about the return codes from the z/OS services. If you are unable to solve the problem, contact your IBM support center.
The channel initiator was unable to load a required module. ssss is the completion code and rrrr is the reason code (both in hexadecimal) from the z/OS LOAD service.
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 many cases, the end result is that the channel initiator terminates.
Check the console for messages indicating why the module was not loaded. See the MVS Programming: Assembler Services Reference manual for information about the codes from the LOAD request.
Ensure that the module is in the required library, and that it is referenced correctly. The channel initiator attempts to load this module from the library data sets under the STEPLIB DD statement of its started task JCL procedure xxxxCHIN.
The data conversion services required by the channel initiator could not be initialized. The reason code reason shows why:
8
The channel initiator does not start.
Check the console for messages indicating that a module was not loaded. Ensure that the module is in the required library, and that it is referenced correctly. The channel initiator attempts to load this module from the library data sets under the STEPLIB DD statement of its started task JCL procedure xxxxCHIN.
If you are unable to solve the problem, contact your IBM support center.
An MQCMIT call involving messages for queue name was unsuccessful.
8
The component where the error occurred (supervisor) terminates.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
A message being put to an IMS bridge queue name required data conversion, but the conversion was not successful.
0
The message is put without conversion, and processing continues.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
A token in a name/token pair required by the channel initiator could not be retrieved. rc is the return code (in hexadecimal) from the z/OS IEANTRT service.
8
The channel initiator does not start.
See the MVS Authorized Assembler Services Reference manual for information about the return code from the IEANTRT request. If you are unable to solve the problem, contact your IBM support center.
The channel initiator could not create the necessary storage access list for the queue manager to use. rc is the return code (in hexadecimal) from the z/OS ALESERV service.
8
The channel initiator does not start.
See the MVS Authorized Assembler Services Reference manual for information about the return code from the ALESERV request. If you are unable to solve the problem, contact your IBM support center.
A request by the channel initiator to allow the queue manager to share some storage failed. rc is the return code (in hexadecimal) from the z/OS IARVSERV service.
8
The channel initiator does not start.
See the MVS Authorized Assembler Services Reference manual for information about the return code from the IARVSERV request. If you are unable to solve the problem, contact your IBM support center.
The repository manager task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.
8
The channel initiator terminates.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.
An internal error has occurred. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
8
Processing continues.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
The repository manager is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The repository manager ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center to report the problem.
The repository manager task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.
8
The channel initiator terminates.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.
A preinitialization services (CEEPIPI) call failed. func is the function code used (in decimal) and rc is the return code (in hexadecimal) from the call.
8
The component where the error occurred (message channel agent or SSL server subtask) terminates. In the case of a message channel agent, the associated channel will be stopped.
See the Language Environment for z/OS & VM Programming Guide for information about the return code from the CEEPIPI call. If you are unable to solve the problem, contact your IBM support center.
The channel initiator cluster cache task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.
8
The channel initiator terminates.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.
An error occurred processing a pause element. return-code is the return code (in hexadecimal) from the z/OS pause service service-name.
8
The component where the error occurred (message channel agent, repository manager, cluster cache extension task,) usually terminates; in many cases, the end result will be that the channel initiator terminates.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the request. If you are unable to solve the problem, contact your IBM support center.
The dynamic cluster cache cannot be increased because the channel initiator cluster cache task encountered an error.
8
The channel initiator terminates.
Investigate the problem reported in any preceding messages.
The channel initiator is being started with the parameter values shown in the following messages: CSQX071I, CSQX072I, CSQX073I, CSQX074I, CSQX075I, CSQX078I, CSQX079I, CSQX080I, CSQX081I, CSQX082I, CSQX085I, CSQX090I, CSQX091I, CSQX092I, CSQX093I, CSQX094I, CSQX099I.
0
The channel initiator startup processing continues.
Channel initiator parameters are specified by queue manager attributes. Use the ALTER QMGR command to set the values you want.
A severe error, as reported in the preceding messages, occurred during dispatcher startup processing.
8
The channel initiator will attempt to restart the dispatcher. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately.
Investigate the problem reported in the preceding messages.
During dispatcher startup processing, one of the essential dispatcher processes (named process) could not be scheduled.
8
The dispatcher does not start.
The most likely cause is insufficient storage. If increasing the available storage does not solve the problem, contact your IBM support center.
The dispatcher using TCB tcb-name found an inconsistency in the linkage stack.
8
The dispatcher ends abnormally with completion code X'5C6' and reason code X'00E7010E', and a dump is issued. The channel initiator will attempt to restart it.
The most likely cause is incorrect use of the linkage stack by a user channel exit; exits must issue any MQ API calls and return to the caller at the same linkage stack level as they were entered. If exits are not being used, or if they do not use the linkage stack, contact your IBM support center to report the problem.
The dispatcher using TCB tcb-name had an internal error.
8
The dispatcher ends abnormally with completion code X'5C6' and reason code X'00E7010F', and a dump is issued. The channel initiator will attempt to restart it.
Contact your IBM support center to report the problem.
During startup processing, the recovery environment could not be set up. return-code is the return code (in hexadecimal) from the z/OS ESTAE service.
8
The component that was starting (dispatcher, adapter subtask, SSL server subtask, supervisor, repository manager, or channel initiator itself) does not start.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ESTAE request. If you are unable to solve the problem, contact your IBM support center.
Use of TCP/IP with the OpenEdition sockets interface was requested, but an error occurred. return-code and reason are the return and reason codes (both in hexadecimal) from the OpenEdition service serv that gave the error.
The most likely causes are:
4
Processing continues, but communications using TCP/IP with the OpenEdition sockets interface will not be available.
See the z/OS OpenEdition Messages and Codes manual for information about the codes from the service request.
Use of TCP/IP was specified by the channel initiator parameters, but that interface is not available with the libraries that the channel initiator is using.
4
Processing continues, but communications using TCP/IP will not be available.
Check that the SCSQMVR1 library data set for the channel initiator has been specified in the STEPLIB DD statement of its started task JCL procedure.xxxxCHIN, See the WebSphere MQ for z/OS System Setup Guide for more information about the channel initiator parameters and the library data sets.
A process for the dispatcher using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred in a user data conversion exit. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The process ends abnormally, and a dump is normally issued. The channel is stopped, and must be restarted manually.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. If a system completion code is shown, see the MVS System Codes manual for information about the problem in your exit.
A process for the dispatcher using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred in a user channel exit. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The process ends abnormally, and a dump is normally issued. The channel is stopped, and must be restarted manually. For auto-defined channels, the channel does not start.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. If a system completion code is shown, see the MVS System Codes manual for information about the problem in your exit.
A process run by the dispatcher using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The process ends abnormally, and a dump is normally issued. If the process is a message channel agent, the channel is stopped, and will need to be restarted manually.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. If a system completion code is shown, and you are using user channel exits, check that your exit is setting its parameter lists correctly; otherwise, contact your IBM support center.
The dispatcher using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The dispatcher ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.
A dispatcher ended abnormally, as reported in the preceding messages, and could not be restarted. reason shows the type of failure:
8
The channel initiator will attempt to restart the dispatcher. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately.
Investigate the problem reported in the preceding messages.
A dispatcher failed; because it had already failed too many times, the channel initiator did not attempt to restart it.
8
The dispatcher is not restarted. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately, and other processing capacity may be reduced.
Investigate the problems causing the dispatcher failures.
A dispatcher failed, but was successfully restarted by the channel initiator. number dispatchers are now active.
0
Processing continues. The number of current TCP/IP and LU 6.2 channels allowed will be increased proportionately.
This is issued during channel initiator startup processing and in response to the DISPLAY CHINIT command if the maximum number of current TCP/IP channels allowed is less than is specified in the TCPCHL queue manager attribute. This can occur because:
0
If TCP/IP resources are restricted, consider increasing either the OpenEdition MAXFILEPROC parameter or the number of dispatchers if you need more current TCP/IP channels.
This is issued during channel initiator startup processing and in response to the DISPLAY CHINIT command if the maximum number of current LU 6.2 channels allowed is less than is specified in the LU62CHL queue manager attribute. This can occur because some dispatchers have failed and not been restarted; the number of current LU 6.2 channels allowed will be reduced proportionately.
0
A severe error, as reported in the preceding messages, occurred during adapter subtask startup processing.
8
The channel initiator will attempt to restart the adapter subtask.
Investigate the problem reported in the preceding messages.
The channel initiator startup procedure has started the requested number of adapter subtasks; started adapter subtasks started successfully and failed adapter subtasks did not start.
0
The channel initiator startup processing continues.
If the message indicates that some adapter subtasks failed, investigate the problem reported in the preceding messages.
A severe error, as reported in the preceding messages, occurred during adapter subtask startup processing.
8
The channel initiator will attempt to restart the adapter subtask.
Investigate the problem reported in the preceding messages.
The adapter subtask using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The adapter subtask ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.
If you are using user channel exits, check that your exit is setting its parameter lists correctly. User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.
An adapter subtask could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.
8
The adapter subtask is not restarted.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.
A adapter subtask failed; because it had already failed too many times, the channel initiator did not attempt to restart it.
8
The adapter subtask is not restarted; processing capacity may therefore be reduced.
Investigate the problems causing the adapter subtask failures.
A adapter subtask failed, but was successfully restarted by the channel initiator. active adapter subtasks are now active.
0
Processing continues.
A severe error, as reported in the preceding messages, occurred during SSL server subtask startup processing.
8
The channel initiator will attempt to restart the SSL server subtask.
Investigate the problem reported in the preceding messages.
The channel initiator startup procedure has started the requested number of SSL server subtasks; started SSL server subtasks started successfully and failed SSL server subtasks did not start.
0
The channel initiator startup processing continues.
If the message indicates that some SSL server subtasks failed, investigate the problem reported in the preceding messages.
A severe error, as reported in the preceding messages, occurred during SSL server subtask startup processing.
8
The channel initiator will attempt to restart the SSL server subtask.
Investigate the problem reported in the preceding messages.
The SSL server subtask using TCB tcb-name is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
8
The SSL server subtask ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.
If you are using user channel exits, check that your exit is setting its parameter lists correctly. User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.
An SSL server subtask could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.
8
The SSL server subtask is not restarted.
See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.
A SSL server subtask failed; because it had already failed too many times, the channel initiator did not attempt to restart it.
8
The SSL server subtask is not restarted; processing capacity may therefore be reduced.
Investigate the problems causing the SSL server subtask failures.
A SSL server subtask failed, but was successfully restarted by the channel initiator. active SSL server subtasks are now active.
0
Processing continues.
SSL communications are requested but an error, as reported in the preceding messages, occurred during channel initiator startup processing.
4
Processing continues.
Investigate the problem reported in the preceding messages. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.
SSL communications are requested but no SSL key respository name is specified; that is, the SSLTASKS queue manager attribute is non-zero, but the SSLKEYR queue manager attribute is blank.
4
Processing continues, but communications using SSL will not be available.
Use the ALTER QMGR command to specify a name for the SSL key repository with the SSLKEYR attribute, and restart the channel initiator. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.
SSL communications are requested but the SSL authentication namelist specified by the SSLCRLNL queue manager attribute is empty or not of type AUTHINFO.
4
Processing continues, but communications using SSL will not be available.
Correct the definitions of the namelist, and restart the channel initiator. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.
The SSL authentication namelist specified by the SSLCRLNL queue manager attribute has more names than are supported. The number supported is n.
4
Processing continues; the excess names are ignored.
Correct the definitions of the namelist.
The SSL key respository, whose name is specified by the SSLKEYR queue manager attribute, could not be accessed.
The most likely causes are:
4
Processing continues, but communications using SSL will not be available. Channels using SSL communications will not start.
Check that:
A REFRESH SECURITY TYPE(SSL) command was issued, but an SSL key repository refresh was already in progress.
The command is ignored. The refresh currently in progress continues.
0
The user exit exit-name returned an invalid response code (response, shown in hexadecimal) in the ExitResponse field of the channel exit parameters (MQCXP).
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid response code.
The user exit exit-name returned an invalid secondary response code (response, shown in hexadecimal) in the ExitResponse2 field of the channel exit parameters (MQCXP).
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid secondary response code.
The user exit exit-name returned an invalid address for the exit buffer when the secondary response code in the ExitResponse2 field of the channel exit parameters (MQCXP) is set to MQXR2_USE_EXIT_BUFFER.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid exit buffer address. The most likely cause is failing to set a value, so that it is 0.
The user exit exit-name returned a header compression value that was not one of those which were negotiated as acceptable when the channel started.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid value. If necessary, alter the channel definitions so that the desired compression value is acceptable.
The user exit exit-name returned a message compression value that was not one of those which were negotiated as acceptable when the channel started.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid value. If necessary, alter the channel definitions so that the desired compression value is acceptable.
The user exit exit-name returned a data length value that was not greater than zero.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid data length.
The user exit exit-name invoked for channel channel-name returned invalid values, as reported in the preceding messages. ExitId shows the type of exit:
and ExitReason shows the reason for invoking it:
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.
Investigate why the user exit program set invalid values.
The user exit exit-name returned data in the supplied agent buffer, but the length specified is greater than the length of the buffer.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid data length.
The user exit exit-name returned data in the supplied exit buffer, but the length specified is greater than the length of the buffer.
8
Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.
Investigate why the user exit program set an invalid data length.
An unexpected error message code has been issued by the channel initiator.
8
Processing continues.
Note the code ccc (which is shown in hexadecimal) and contact your IBM support center to report the problem.
An attempt to allocate a conversation on connection conn-id was not successful. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is not started.
The error may be due to an incorrect entry in the channel definition. Correct the error and try again.
It could also be that the listening program at the remote end is not running. If so, perform the necessary operations to start the listener for trptype, and try again.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system. If using TCP/IP, see the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An attempt to allocate a conversation was not successful because the connection conn-id was unavailable. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The attempt to start the channel is retried.
Try again later.
A likely cause is that the listener at the remote end was not running or has been started using the wrong port or LU name. If this is the case, perform the necessary operations to start the appropriate listener, and try again.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system. If using TCP/IP, see the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An attempt to allocate a conversation on connection conn-id was not successful because of a communications configuration error. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there may also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is not started.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system.
Probable causes are:
See the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An attempt to connect on connection conn-id was rejected. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is not started.
Check the appropriate listener has been started on the remote end.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system.
If the communications protocol is LU 6.2, it is possible that either the user ID or password supplied at the remote LU is incorrect. The remote host or LU may not be configured to allow connections from the local host or LU.
If the communications protocol is TCP/IP, it is possible that the remote host does not recognize the local host. See the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
The supplied connection name conn-id could not be resolved into a TCP/IP network address. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The return code from TCP/IP (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is not started.
Check the local TCP/IP configuration. Either the name server does not contain the host or LU name, or the name server was not available.
See Appendix D. Communications protocol return codes for information about the cause of the return code from TCP/IP. See the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An error occurred sending data to conn-id, which may be due to a communications failure. The associated channel is channel-name and the associated remote queue manager is qmgr-name; in some cases the names cannot be determined and so are shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system. If using TCP/IP, see the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
Note that the error may have occurred because the channel at the other end has stopped for some reason, for example an error in a receive user exit.
Data received from connection conn-id was not in the required format. The associated remote queue manager is qmgr-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
8
The data is ignored.
A likely cause is that an unknown host or LU is attempting to send data.
An error occurred receiving data from connection conn-id, which may be due to a communications failure. The associated channel is channel-name and the associated remote queue manager is qmgr-name; in some cases the names cannot be determined and so are shown as '????'. trptype shows the communications system used:
The return code from it (in hexadecimal) was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system. If using TCP/IP, see the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An error occurred receiving data from connection conn-id. The connection to the remote host or LU has unexpectedly terminated. The associated channel is channel-name and the associated remote queue manager is qmgr-name; in some cases the names cannot be determined and so are shown as '????'. trptype shows the communications system used:
However, this message can also occur in cases where there is no error; for example, if the TCP/IP command TELNET is issued that is directed at the port which the channel initiator is using.
8
If a channel is involved, it is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Review the local and remote console logs for reports of network errors.
An incoming attach request arrived on connection conn-id, but the local host or LU was unable to complete the bind. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The return code from APPC/MVS allocate services was return-code and the associated reason code was reason (both in hexadecimal).
8
The channel is not started.
Check the APPC/MVS configuration.
See APPC allocate services return codes for the cause of the return code from APPC/MVS allocate services, and the Writing Servers for APPC/MVS manual for more information.
A TCP/IP socket could not be created, possibly because of a storage problem. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The return code (in hexadecimal) from TCP/IP was return-code. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.
8
The channel is not started.
See Appendix D. Communications protocol return codes for information about the cause of the return code from TCP/IP. See the z/OS UNIX System Services Messages and Codes manual for information about the reason code.
An unexpected communications error occurred for a listener or a channel. If it was for a listener, the csect-name is CSQXCLMA, and the channel name is shown as '????'. If it was for a channel, the channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
trptype shows the communications system used:
func is the name of the TCP/IP or APPC/MVS function that gave the error. In some cases the function name is not known and so is shown as '????'.
return-code is
For some errors, there may also be an associated reason code reason (in hexadecimal) giving more information.
8
If the error occurred for a channel, the channel is stopped. For a listener, the channel is not started or, in some cases, the listener terminates.
See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system.
A distributed queuing message code nnn is generally associated with message CSQXnnnE, which will normally be issued previously. See that message explanation for more information. Where no such message is described, see Appendix F. Distributed queuing message codes for the corresponding message number.
Check for error messages on the partner system that may indicate the cause of the problem.
An attempt was made to use the communications system, but it has not been started or has stopped. trptype shows the communications system used:
8
The channel or listener is not started.
Start the communications system, and try again.
An attempt to bind the TCP/IP socket to the indicated listener port was not successful. ip-address is the IP address used, or '*' if the listener is using all IP addresses. The return code (in hexadecimal) from TCP/IP was return-code.
disposition shows which type of incoming requests the listener was handling:
8
The listener is not started.
The failure could be due to another program using the same port number.
See Appendix D. Communications protocol return codes for information about the return code from TCP/IP.
An attempt was made to create a new TCP/IP socket because an attach request was received, but an error occurred.
disposition shows which type of incoming requests the listener was handling:
8
The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.
The failure may be transitory, try again later. If the problem persists, it may be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.
An attempt was made to use the communications system by a channel or a listener, but it has not been started or has stopped. If it was for a channel, the channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. If it was for a listener, the channel name is again shown as '????'. trptype shows the communications system used:
8
The channel or listener is not started.
Start the communications system, and try again.
An incoming attach request arrived, but the listener for trptype could not start an instance of a channel to respond to it. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
disposition shows which type of incoming requests the listener was handling:
However, this message can also occur in cases where there is no error; for example, if the TCP/IP command TELNET is issued that is directed at the port which the channel initiator is using.
8
If a channel is involved, it is not started.
The failure could be because the channel initiator is currently too busy; try again when there are fewer channels running. If the problem persists, increase the number of dispatchers used by the channel initiator.
The specified listener terminated. This may be because a STOP command was issued, because there was an error in the communications system, or because of some other error.
disposition shows which type of incoming requests the listener was handling:
0
Processing continues. If the listener was not deliberately stopped, the channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.
If the listener was not deliberately stopped, look at any preceding messages relating to the channel initiator or to the TCP/IP, OMVS, or APPC address spaces to determine the cause.
The supplied local address local-addr could not be resolved to a TCP/IP network address. The associated channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The return code from TCP/IP (in hexadecimal) was return-code.
8
The channel is not started.
Check the local TCP/IP configuration. Either the name server does not contain the host name, or the name server was not available.
See Appendix D. Communications protocol return codes for information about the cause of the return code from TCP/IP.
An attempt was made to start a channel or listener using TCP/IP, but the TCP/IP gethostname call failed. If it was for a channel, the channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. If it was for a listener, the channel name is again shown as '????'. The return code (in hexadecimal) from TCP/IP was return-code.
8
The channel or listener is not started.
See Appendix D. Communications protocol return codes for information about the cause of the return code from TCP/IP.
The specified listener is ending abnormally because an error that cannot be corrected has occurred. sss is the system completion code, uuu is the user completion code, and reason is the associated reason code (all in hexadecimal).
disposition shows which type of incoming requests the listener was handling:
8
The listener ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.
User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for OS/390 Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.
The specified listener started successfully. This may be as a result of a START LISTENER command, or because the listener restarted automatically following an error.
disposition shows which type of incoming requests the listener was handling:
0
Processing continues.
An error occurred in the listener select processing. The listener was notified by TCP/IP, but no attach request was received.
disposition shows which type of incoming requests the listener was handling:
8
The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.
The failure may be transitory, try again later. If the problem persists, it may be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.
An attempt was made to create a new TCP/IP socket because an attach request was received, but an error occurred.
disposition shows which type of incoming requests the listener was handling:
4
The listener continues to run, but the connection is not created.
The failure may be transitory, try again later. If the problem persists, it may be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.
An error occurred in the listener accept processing. The listener was notified by TCP/IP, but no attach request was received.
disposition shows which type of incoming requests the listener was handling:
8
The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.
The failure may be transitory, try again later. If the problem persists, it may be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.
The connection conn-id timed out. The associated channel is channel-name and the associated remote queue manager is qmgr-name; in some cases the names cannot be determined and so are shown as '????'. trptype shows the communications system used:
Probable causes are:
8
The channel stops.
For a message channel, check the remote end to see why the time out occurred. Note that, if retry values are set, the remote end will restart automatically. If necessary, set the receive wait time for the queue manager to be higher.
For an MQI channel, check that the client application behaviour is correct. If so, set the disconnect interval for the channel to be higher.
An attempt to attach a client on connection conn-id by MQI channel channel-name was rejected because the client attachment feature is not available. In some cases, the channel name cannot be determined and so is shown as '????'.
8
The client is not attached, and the connection from the client application fails with MQRC_Q_MGR_NOT_AVAILABLE.
Install the client attachment feature if support for clients is required.
An attempt to allocate a conversation on connection conn-id for channel channel-name using TCP/IP communications was not successful because the IP stack used did not support the IP address family required for the connection.
8
The channel is not started.
If the channel's CONNAME attribute resolves to an IPv6 address, then ensure the stack being used by the combination of the TCPNAME queue manager attribute and the channel's LOCLADDR attribute supports IPv6. If the channel's CONNAME attribute resolves to an IPv4 address, then ensure the stack being used by the combination of the TCPNAME queue manager attribute and the channel's LOCLADDR attribute supports IPv4.
An unexpected communications error occurred for a listener or a channel. This error occurs if the channel was stopped with mode FORCE and the communications session was canceled.
The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. trptype shows the communications system used:
8
The channel is stopped.
Restart the channel if appropriate.
In response to a request to start a channel that was not defined, an attempt was made to define it automatically. The channel auto-definition exit exit-name prevented it being defined.
0
The channel is not started.
The repository manager successfully processed a REFRESH command with the REPOS(YES) option for the indicated cluster.
0
None.
The repository manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager.
0
None.
The repository manager could not process a REFRESH command with the REPOS(YES) option for the indicated cluster, because the local queue manager provides full repository management service for the cluster.
8
The command is ignored.
Reissue the command with the correct values or on the correct queue manager. It may be necessary to change the queue manager so that it is not a full repository for the cluster.
The definition of a cluster queue has different values for the DEFPRTY, DEFPSIST, and DEFBIND attributes on the various queue managers in the cluster.
All definitions of the same cluster queue should be identical; otherwise, problems may arise if your applications rely on one of these attributes to determine messaging behavior. For example, if an application opens a cluster queue with the option MQOO_BIND_AS_Q_DEF, and the different instances of the queue have different DEFBIND values, the behavior of the message transfer depends on which instance of the queue happens to be selected when it is opened.
4
None.
Alter the definitions of the queue on the various queue managers so that they have identical values for these attributes.
The repository manager started successfully.
0
None.
The repository manager stopped. This may be for one of three reasons:
0
Processing continues, but clustering is not available.
If an error has occurred, investigate the problem reported in the preceding messages.
The repository manager received a command intended for some other queue manager, whose identifier is target-id. The command was sent by the queue manager with identifier sender-id.
8
The command is ignored, and the error is reported to the sender.
Check the channel and cluster definitions of the sending queue manager.
An internal error has occurred.
8
The command is ignored, and the error is reported to the sender; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
An internal error has occurred.
8
The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
An internal error has occurred.
8
The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
The indicated queue manager has been deleted or forcibly removed from a cluster, but there are manually-defined cluster-sender channels that refer to it. This means that the repository manager will continue to send cluster information to the removed queue manager.
0
Delete the manually-defined cluster-sender channels that refer to qmgr-name.
The repository manager has received information about a cluster for which it is the only full repository.
0
None.
If you require a second full repository, alter the REPOS or REPOSNL attribute of the second queue manager that is to have a full repository for the cluster to specify the cluster name.
The repository manager has received information about a cluster for which no cluster-receiver channels are known.
0
None.
Define cluster-receiver channels for the cluster on the local queue manager.
The repository manager has received information about a cluster for which no full repositories are known.
0
None.
Define a cluster-sender channel for connecting to the queue manager that is the full repository for the cluster, or alter the REPOS or REPOSNL attribute of the queue manager that is to have a full repository for the cluster to specify the cluster name.
An internal error has occurred.
8
The repository manager attempts to continue processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
An internal error has occurred.
8
The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
The repository manager tried to send a command to another queue manager using channel channel-name. The other queue manager, whose identifier is target-id, could not be found.
8
The command is ignored.
Check the channel and cluster definitions of the sending and receiving queue managers.
A cluster-sender channel must be connected to a queue manager that is a full repository for all the clusters for the channel, and the corresponding cluster-receiver channel must be in the same clusters. Channel channel-name in cluster cluster-name does not satisfy this. target-id is the identifier of the target queue manager for the channel.
8
The command is ignored.
Check the definition of the channel on both queue managers to ensure that it is connected to a full repository for the clusters, and that it is in the same clusters on both queue managers.
The repository manager received a command from another queue manager, whose identifier is sender-id, relating to cluster cluster-name. The local queue manager cannot accept the command because it is not a full repository for the cluster and (in the case of a queue command) it does not have an interest in the cluster queue. The cluster-sender channel used by the other queue manager was channel-name.
This can also occur a command destined for the local repository manager is delayed in the network and is out of date when it arrives, for example because a REFRESH CLUSTER command has been issued on the local repository manager has caused its view of the cluster to change.
8
The command is ignored.
Check the definition of the channel on both queue managers to ensure that it is connected to a full repository for the cluster.
If the message occurs because a command is out of date, the message can be ignored.
The repository manager received a command from another queue manager, whose identifier is sender-id, relating to cluster cluster-name. The local queue manager cannot accept the command because it is not a full repository for the cluster, it does not have an interest in the cluster channel, and it does not have any matching cluster-sender channels. The cluster-sender channel used by the other queue manager was channel-name.
This message may appear on a queue manager that has defined a cluster-sender channel to another queue manager that does not host a full repository, if the other queue manager is later modified to host a full repository.
8
The command is ignored.
Check the definition of the channel on the sending queue manager to ensure that it is connected to a full repository for the cluster.
The repository manager received a command from another queue manager, whose identifier is sender-id, reporting that it is no longer a full repository for cluster cluster-name.
0
The cluster-sender channel channel-name is changed so that it can no longer be used to access the other queue manager in relation to the cluster.
The repository manager received a command from another queue manager, whose identifier is sender-id. The cluster-sender channel channel-name on that queue manager is in cluster cluster-name, but the corresponding cluster-receiver channel on the local queue manager is not.
8
The command is ignored.
Change the definition of the channel so that it is in the same clusters on both queue managers.
The channel initiator found a message on one of its queues that either had a format that could not be recognized or did not come from a queue manager or channel initiator.
8
The message is put on the dead-letter queue.
Examine the message on the dead-letter queue to determine the originator of the message.
The repository manager tried to send a message to SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose identifier is target-id, but the MQPUT call was unsuccessful.
4
Processing continues, but repository information may be out of date.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running.
When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to be sure that the repository information is up to date.
This error may occur if the REFRESH CLUSTER REPOS(YES) command is issued against a full repository, as the full repository will then be temporarily unable to fulfil requests from other repositories until it has rebuilt the cluster. If there is more than one full repository for the cluster, the problem will resolve itself. If there is only a single full repository for the cluster, the REFRESH CLUSTER command will need to be run against all the other queue managers in the cluster to make them contact the full repository again.
The repository manager tried to send a message to SYSTEM.CLUSTER.COMMAND.QUEUE on a queue manager that has the full repository for the specified cluster, but the MQPUT was unsuccessful.
4
Processing continues, but repository information may be out of date.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running.
When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to be sure that the repository information is up to date.
The repository manager tried to commit some updates to the repository but was unsuccessful.
4
Processing continues, but local repository information may be out of date.
If this occurs when the channel initiator is stopping, it can be ignored because the local repository information will normally be updated automatically when the channel initiator is restarted. If there is an isolated occurrence at other times, use the REFRESH CLUSTER command to bring the local repository information up to date.
If the problem persists, contact your IBM support center.
The repository manager was unable to reallocate messages for the specified channel to another destination.
8
The messages remain on the transmission queue.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc. Use this information in conjunction with any preceding error messages to determine the cause of the problem. When the problem is corrected, restart the channel.
An internal error has occurred.
8
The repository manager attempts to continue processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
The repository manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because the local queue manager does not provide a full repository management service for the cluster.
8
The command is ignored.
Reissue the command with the correct values or on the correct queue manager.
The repository manager successfully processed a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager.
0
None.
The repository manager successfully processed a REFRESH command for the indicated cluster.
0
None.
The repository manager successfully processed a SUSPEND QMGR command for the indicated cluster. (Where the command specified a namelist of clusters, the message is issued only for the first cluster in the namelist.)
0
None.
The repository manager successfully processed a RESUME QMGR command for the indicated cluster. (Where the command specified a namelist of clusters, the message is issued only for the first cluster in the namelist.)
0
None.
Following an error, the repository manager tried to backout some updates to the local repository but was unsuccessful.
8
The repository manager terminates.
If the repository manager subsequently restarts successfully, or if on restarting the channel initiator the repository manager subsequently starts successfully, this can be ignored.
If not, contact your IBM support center.
A severe error, as reported in the preceding messages, occurred during repository manager processing; the repository manager is unable to continue.
8
The repository manager terminates. The channel initiator will try to restart it after the specified interval.
Correct the problem reported in the preceding messages.
The repository manager restarted successfully following an error.
0
None.
The repository manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because there is more than one queue manager with the specified name in the cluster.
8
The command is ignored.
Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name.
The repository manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because no information about that queue manager was found in the local repository.
8
The command is ignored.
Reissue the command specifying the correct queue manager name or identifier.
The repository manager found a cluster queue that had been used in the last 30 days, and for which updated information should have been received. However, no such information has been received. The queue is q-name in cluster-name, and its queue manager is qmgr-name.
If the queue manager is a partial repository for the queue, the updated information should have been sent from a full repository. If the queue manager is a full repository, the updated information should have been sent from the queue manager on which the queue is defined.
0
The repository manager will keep information about this queue for a further 60 days. If information has not been sent to a full repository then this queue will not be used to satisfy any new requests for cluster resources made to this full repository.
If the queue is still required, check that:
The repository manager received a command from another queue manager, whose identifier is sender-id, reporting that it is once again a full repository for cluster cluster-name.
0
The cluster-sender channel channel-name is changed so that it can be used to access the other queue manager in relation to the cluster.
No more space is available in the cluster cache area.
8
The repository manager terminates. The channel initiator will try to restart it after the specified interval.
The problem may be temporary. If it persists, the queue manager must be restarted; this will cause more space to be allocated for the cluster cache area.
Consider changing the cluster cache type system parameter CLCACHE to dynamic, so that more space for the cache will be obtained automatically as required. (If you are using a cluster workload exit, ensure that it supports a dynamic cluster cache.) See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.
At channel initiator restart, the repository manager found a corrupted entry in the cluster cache. The entry has been corrected.
4
Processing continues. The cluster channel to which the entry refers, channel-name using connection conn-id, will be available for use.
None. You can verify that the entry was successfully corrected by issuing the command DISPLAY CLUSQMGR(clusqmgr-name) on the queue manager where this message was issued.
At channel initiator restart, the repository manager found a corrupted entry in the cluster cache which could not be corrected.
8
The corrupted entry is ignored. The cluster channel to which it refers, channel-name using connection conn-id, will not be usable.
The corrupted entry must be corrected and reintroduced by issuing the command
ALTER CHANNEL(channel-name) CHLTYPE(CLUSRCVR)
on the cluster queue manager clusqmgr-name. You can verify that the entry was successfully reintroduced by issuing the command DISPLAY CLUSQMGR(clusqmgr-name) on the queue manager where this message was issued.
There was an internal error when accessing a cluster cache entry.
8
Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN. The component where the error occurred (message channel agent, repository manager) usually terminates; in some cases, the end result will be that the channel initiator terminates.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
The action you requested cannot be performed on channel channel-name because it has the wrong disposition. For example, the action asked for a shared channel, but its disposition is private.
8
The requested action is not performed.
Check whether the channel name is specified correctly. If it is, check that:
The disposition of an instance of a channel is not related to that specified by QSGDISP in the channel definition:
The channel initiator is shutting down; it owns some active shared sending channels, and they have not been requested to stop. Requests to restart these channels on another queue manager have been issued as shown.
0
The channel initiator shutdown processing continues.
If the numbers in the message differ, the channel initiator was not able to issue restart requests for all the channels. In this case, use the DISPLAY CHSTATUS command to determine which channels are still owned by the queue manager for the channel initiator that is shutting down, and which therefore have not been restarted, and restart them manually as required.
While starting, the specified TCP/IP listener could not register with WLM/DNS. The return code from the IWMSRSRG service was return-code and the associated reason code was reason (both in hexadecimal).
8
The listener is not started.
See z/OS MVS Workload Management Services for more information about the return and reason codes from the IWMSRSRG service.
While stopping, the specified TCP/IP listener could not unregister from WLM/DNS. The return code from the IWMSRDRS service was return-code and the associated reason code was reason (both in hexadecimal).
8
The listener stops. It may not be possible to restart it.
See z/OS MVS Workload Management Services for more information about the return and reason codes from the IWMSRDRS service.
The specified channel, which was orphaned because of a communications error, has been adopted by a new instance of the channel.
0
Processing continues.
An operation was requested on a channel that is active. Because the channel is shared, it may be active on another queue manager. If the channel is a receiver, a previous instance of it may have been orphaned and therefore still be active.
8
The request fails.
For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and retry the operation. It may be necessary to use MODE(FORCE) to stop the channel manually if the Adopt MCA function is not being used. Using the Adopt MCA function will avoid the need for manual intervention to handle orphaned receiver channels.
If the channel is not running on the named queue manager, then there is an orphaned shared status entry, which may be because a loss of connectivity to DB2 occurred. If the problem persists, contact your IBM support center.
An operation was requested on a channel that is active. The queue queue-name named as a transmission queue in the channel definition for channel-name is in use on another member of the queue sharing group, qmgr-name.
8
The request fails.
Do the following, as appropriate:
If the channel is already running, for operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and retry the operation. It may be necessary to use MODE(FORCE) to stop the channel manually if the Adopt MCA function is not being used. Using the Adopt MCA function will avoid the need for manual intervention to handle orphaned receiver channels.
An operation was requested on a channel that is active. The connection tag used to serialize the channel within the queue-sharing group is currently in use. Because the channel is shared, it may be active on another queue manager. If the channel is a receiver, a previous instance of it may have been orphaned and therefore still be active.
8
The request fails.
For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and retry the operation. It may be necessary to use MODE(FORCE) to stop the channel manually if the Adopt MCA function is not being used. Using the Adopt MCA function will avoid the need for manual intervention to handle orphaned receiver channels.
An attempt was made to adopt channel channel-name, which was orphaned because of a communications error. It failed, either because the channel could not be stopped or because a response was not recieved from the queue manager qmgr-name.
8
The request fails, and the orphaned channel may remain active.
Investigate any preceding error messages to discover why the adopt failed. Either stop the channel manually, or wait for it to terminate, and retry the operation. It may be necessary to use MODE(FORCE) to stop the channel manually.
During the execution of a channel command, or during shared channel processing, an internal function required by the channel initiator was found to be unavailable.
8
The channel command fails or the channel stops.
Check that the DB2 tables required by MQ are correctly defined, and restart the queue manager and DB2 if necessary. If these appear to be running correctly, display the information in the shared channel status (CSQ.ADMIN_B_SCST) and the shared synchronization key (CSQ.ADMIN_B_SSKT) DB2 tables, and contact your IBM support center for further assistance. Refer to the WebSphere MQ for z/OS Problem Determination Guide for further information, and for details of a sample job (CSQ45STB) which shows the information in the DB2 tables.
Because DB2 is not available, or is no longer available, the channel initiator cannot do processing for a shared channel.
8
The channel command fails or the channel stops.
Use the preceding messages on the z/OS console to investigate why DB2 is not available, and restart it if necessary.
Because there was an error in accessing DB2, the channel initiator cannot do processing for a shared channel.
8
The channel command fails or the channel stops.
Resolve the error reported in the preceding messages.
During the execution of a channel command, or during shared channel processing, shared channel status or shared synchronization key information, held in DB2, was found to be corrupted.
8
The channel command fails or the channel stops.
Check that the DB2 tables required by MQ are correctly defined, and restart DB2 if necessary. If DB2 appears to be running correctly, display the information in the shared channel status (CSQ.ADMIN_B_SCST) and the shared synchronization key (CSQ.ADMIN_B_SSKT) DB2 tables, and contact your IBM support center for further assistance. Refer to the WebSphere MQ for z/OS Problem Determination Guide for further information, and for details of a sample job (CSQ45STB) which shows the information in the DB2 tables.
The definition of a shared channel has differing attribute values on the various queue managers in the queue-sharing group. For example, if the type of the channel differs start or stop requests cannot operate correctly.
8
The request fails.
Change the definitions of the channel so that they are the same on all the queue managers. If the channel type needs changing, you must delete and then redefine the channel.
The channel is closing because the user channel exit at the remote end requested it.
0
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.
Note that this puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.
The MQCD structure returned by the channel auto-definition exit had an invalid value in the indicated field. The value is shown in decimal and hexadecimal.
8
The channel is not defined.
Correct the channel auto-definition exit.
The specified channel has been started.
0
Processing continues.
The specified channel terminated. It is now inactive if it terminated normally when the disconnect interval expired, or stopped if it terminated because of an error or a STOP CHANNEL command.
0
Processing continues.
If the channel is stopped, resolve any error, and issue a START CHANNEL command to restart the channel.
The action you requested cannot be performed on channel channel-name. Some actions are only valid for certain channel types; for example, you can only ping a sender or server channel.
8
The requested action is not performed.
Check whether the channel name is specified correctly. If it is, check that:
Channel channel-name could not be established due to a negotiation failure between the local queue manager and the remote end.
8
The channel is not started.
Examine the console log for the remote end for messages explaining the cause of the negotiation failure.
During communications with the remote end, the local message channel agent for channel channel-name detected a protocol error. type shows the type of error that occurred:
The incorrect value is shown by xxx.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Examine the console log to determine the cause of the failure. This may occur after the channel initiator or queue manager is stopped forcibly or ends abnormally. If it occurs in other cases, contact your IBM support center to report the problem.
The sequence number wrap value for channel channel-name is local-seqno, but the value specified at the remote end is remote-seqno. The two values must be the same before the channel can be started.
8
The channel does not start.
Change either the local or remote channel definition so that the values specified for the message sequence number wrap value are the same.
The remote end did not accept the last batch of messages.
8
Channel channel-name stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Determine why the remote end did not accept the last batch of messages. Resolve the problem and restart the channel.
Channel channel-name is in-doubt with the remote end using connection conn-id. The associated remote queue manager is qmgr-name; in some cases its name cannot be determined and so is shown as '????'.
8
The requested operation does not complete.
Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNEL command to correct the problem manually.
There are too many channels current to be able to start another. The maximum number allowed is specified in the MAXCHL queue manager attribute. Current channels include stopped and retrying channels as well as active channels.
8
The channel does not start.
Wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase MAXCHL.
An operation was requested on a channel that is active. If the channel is shared, it may be active on another queue manager. If the channel is a receiver, a previous instance of it may have been orphaned and therefore still be active.
8
The request fails.
For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and retry the operation. It may be necessary to use MODE(FORCE) to stop the channel manually if the Adopt MCA function is not being used. Using the Adopt MCA function will avoid the need for manual intervention to handle orphaned receiver channels.
The channel for which information has been requested is a new instance of the channel. The previous channel instance has ended.
0
The information shown is for the new channel instance.
There was an error when accessing the channel synchronization data.
If the return code is of the form 10009nnn or 20009nnn, it is a distributed queuing message code. This is generally associated with message CSQXnnnE, which will normally be issued previously.
Otherwise the most likely cause is a shortage of storage.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
In some cases, the channel initiator will stop as well.
If the return code is a distributed queuing message code, see the corresponding message explanation for more information. Where no such message is described, see Appendix F. Distributed queuing message codes for the corresponding message number.
Restart the channel or the channel initiator. If the problem persists, contact your IBM support center.
There was more than one set of synchronization information in q-name for an instance of channel channel-name. This is probably because the channel is a receiver channel, and there are two sender channels with the same name on different queue managers within the same network address that have communicated with it.
8
The first set of synchronization information for the channel instance is used, and any others are ignored. Errors may occur if the channel is used.
Avoid using the channel. Remove the extra sets of information from the channel synchronization queue, and rename channels so that they have unique names.
If this does not resolve the problem, contact your IBM support center.
The channel initiator could not find a definition of channel channel-name.
8
The requested operation fails.
Check that the name is specified correctly and the channel definition is available.
There is no definition of channel channel-name at the remote end.
8
The channel does not start.
Add an appropriate channel definition at the remote end, and retry the operation.
During communications with the remote end, the remote message channel agent for channel channel-name detected a protocol error. type shows the type of error that occurred:
The data associated with the error (for example, the incorrect value) is shown by xxx.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Examine the console log for the remote end to determine the cause of the failure. This may occur after the channel initiator or queue manager is stopped forcibly or ends abnormally. If it occurs in other cases, contact your IBM support center.
Channel channel-name cannot start because the remote queue manager is not currently available.
8
The channel does not start
Either start the remote queue manager, or retry the operation later.
Channel channel-name is closing because the remote queue manager qmgr-name is stopping. In some cases, the remote queue manager name cannot be determined and so is shown as '????'.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Investigate why the remote queue manager is stopping, if it was not expected.
The local queue manager does not agree with the remote end on the next message sequence number for channel channel-name. The message is normally issued at both the sending and receiving end: at the sending end, msg-seqno and exp-seqno are unpredictable; at the receiving end, a message had sequence number msg-seqno but sequence number exp-seqno was expected.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the problem cannot be resolved, the sequence number can be reset manually at the sending end of the channel using the RESET CHANNEL command. (For some queue managers, it may be necessary to issue the RESET CHANNEL command at the receiving end as well.)
The remote end cannot receive the message that is being sent for channel channel-name.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Examine the console log for the remote end to determine why the message cannot be received, and then restart the channel.
The channel is closing because a STOP CHANNEL command was issued, or because the channel initiator is stopping.
0
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Note that a STOP CHANNEL command puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.
The queue q-name named as a transmission queue in the channel definition for channel-name is either in use (by this channel or another channel), or it is not a transmission queue.
8
The channel does not start.
Do the following, as appropriate:
A request to stop channel channel-name was made, but the channel was already in the specified state, or in the process of reaching that state.
0
The request is ignored.
The operation requested cannot be performed because the channel is currently stopped.
4
The request is ignored.
Issue a START CHANNEL command to restart the channel.
The user exit exit-name specified for channel channel-name is not valid.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.
Ensure that the user exit name is specified correctly in the channel definition, and that the user exit program is correct and available. The channel initiator loads exits from the library data sets under the CSQXLIB DD statement of its started task JCL procedure xxxxCHIN.
The channel is closing because the user channel exit exit-name requested it.
0
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.
Note that this puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.
A trigger message was received to start a channel channel-name to process the transmission queue q-name. However, the channel initiator could not find a defined and available channel to start.
8
The channel does not start.
Ensure that there is a channel defined to process the transmission queue, and that it is not stopped.
An MQCMIT call for the queue associated with channel channel-name was unsuccessful.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.
Either the local coded character set identifier (CCSID) or the target CCSID is not valid, or is not currently supported, or conversion between the two CCSIDs involved is not supported. (The name of the channel cannot be determined because the invalid CCSID prevents the necessary data conversion being done.)
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Ensure that the CCSIDs are valid and that conversion between them is supported. Refer to the WebSphere MQ Application Programming Reference manual for information about the CCSIDs that are supported.
During the processing of channel channel-name, one or more messages have been put the dead-letter queue at the remote queue manager.
4
Processing continues.
Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.
The channel is closing because no messages arrived on the transmission queue within the disconnect interval.
0
The channel ends normally.
The operation requested cannot be performed because channel channel-name on the remote end is not of a suitable type. For example, if the local channel is defined as a sender the remote queue manager must define its corresponding channel as either a receiver or requester.
8
The requested operation is not performed.
Check that the channel name is specified correctly. If it is, check that:
During the processing of channel channel-name, one or more messages have been put the dead-letter queue at the local queue manager. reason shows why, and is one of the following:
4
Processing continues.
Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.
For information about MQRC_* reason codes see Appendix A. API completion and reason codes. For information about MQFB_* feedback codes see the MQMD description in the WebSphere MQ Application Programming Reference manual.
An MQGET failed because the transmission queue had been previously inhibited for gets.
8
The channel stops. The associated transmission queue may have triggering turned off.
Change the definition of the transmission queue so that it is not inhibited for MQGET calls.
The operation requested for channel channel-name is not supported by the remote end using the connection conn-id. The associated remote queue manager is qmgr-name; in some cases its name cannot be determined and so is shown as '????'.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Check that the connection name parameter is specified correctly and that the levels of the queue managers in use are compatible.
The local security user channel exit for channel channel-name requested data from the remote security user channel exit, but no data was received.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Ensure that the security exit for the channel on the remote end has been defined correctly and is available. If it is, check that the exit program operates correctly.
The channel channel-name at the remote end is currently stopped or is otherwise unavailable. For example, there may be too many channels current to be able to start it.
8
The channel does not start.
This may be a temporary situation, and the channel will retry. If not, check the status of the channel at the remote end. If it is stopped, issue a START CHANNEL command to restart it. If there are too many channels current, either wait for some of the operating channels to terminate, or stop some channels manually, before restarting the channel.
A message could not be delivered normally and there is no dead-letter queue defined for queue manager qmgr-name.
8
The channel stops, except in the case where nonpersistent messages are being sent and the NPMCLASS attribute of the channel is set to FAST, when processing continues. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Correct the problem that prevented the message from being delivered normally, or define a dead-letter queue for the remote queue manager.
While starting, the specified LU 6.2 listener could not register as an APPC/MVS server. The return code from APPC/MVS allocate services was return-code and the associated reason code was reason (both in hexadecimal).
8
The listener is not started.
See Appendix D. Communications protocol return codes for the cause of the return code from APPC/MVS allocate services, and the Writing Servers for APPC/MVS manual for more information. Check that the LUNAME queue manager attribute is the same as the PARTNER_LU value for the APPC/MVS symbolic destination used by the listener.
While stopping, the specified LU 6.2 listener could not unregister as an APPC/MVS server. The return code from APPC/MVS allocate services was return-code and the associated reason code was reason (bothin hexadecimal).
8
The listener stops. It may not be possible to restart it.
See Appendix D. Communications protocol return codes for the cause of the return code from APPC/MVS allocate services and the Writing Servers for APPC/MVS manual for more information.
The number of current TCP/IP channels is the maximum allowed; another channel cannot be started. Current channels include stopped and retrying channels as well as active channels. The maximum allowed is specified in the TCPCHL queue manager attribute, but may be reduced if a dispatcher fails, or if TCP/IP resources are restricted (as reported by message CSQX118I).
8
The channel does not start.
If the maximum allowed is zero, TCP/IP communications are not allowed, and no TCP/IP channels can be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase TCPCHL.
The number of current LU 6.2 channels is the maximum allowed; another channel cannot be started. Current channels include stopped and retrying channels as well as active channels. The maximum allowed is specified in the LU62CHL queue manager attribute, but may be reduced if a dispatcher fails.
8
The channel does not start.
If the maximum allowed is zero, LU 6.2 communications are not allowed, and no LU 6.2 channels can be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase LU62CHL.
During the processing of channel channel-name, a message was found that had an invalid header. The dead-letter queue was defined as a transmission queue, so a loop would have been created if the message had been put there.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Correct the problem that caused the invalid message header.
There are too many channels active (transmitting messages) to be able to start another. The maximum number allowed is specified in the ACTCHL queue manager attribute.
8
The channel does not start.
Either wait for some of the operating channels to terminate, or stop some channels manually, before restarting the channel, or use the ALTER QMGR command to increase ACTCHL.
The specified channel was waiting to start, because there were too many channels active (transmitting messages) to be able to start another. One or more of the active channels has terminated, so this channel can now start.
0
A channel between the local queue manager and the remote end could not be established due to a negotiation failure. The failure was such that the channel name could not be determined: for example, data conversion between the coded character set identifiers (CCSIDs) used by the local and remote ends may not have been possible.
8
The channel is not started.
Examine the console log for the remote end for messages explaining the cause of the negotiation failure.
An internal error has occurred.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.
Collect the items listed in the Problem Determination section and contact your IBM support center.
Collect the following diagnostic items:
Channel channel-name ended abnormally because of a severe problem, as reported in the preceding messages.
8
The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.
Investigate the problem reported in the preceding messages.
Channel channel-name cannot start because resources at the remote queue manager are being recovered.
8
The channel does not start.
Restart the channel at a later time. If the problem persists examine the console log for the remote end for messages explaining the cause of the problem.
The message channel agent for the channel could not connect to the queue manager because resources are being recovered.
8
The channel does not start.
Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, which come from an MQCONNX request.
A request to stop a particular instance of channel channel-name was made (by specifying a connection name or a remote queue manager name), but the channel instance was already in the specified state, or in the process of reaching that state.
0
The request is ignored.
The cached SSL key repository cannot be refreshed in response to a REFRESH SECURITY TYPE(SSL) command because SSL communications are currently unavailble.
0
0
Investigate why SSL is not available and take action as appropriate. It may be necessary to restart the channel initiator to allow SSL to be used.
The cached SSL key repository is being refreshed in response to a REFRESH SECURITY TYPE(SSL) command.
0
Message CSQX619I will be issued when the refresh is complete.
The refresh of the cached SSL key repository is complete.
0
Channels will be restarted as required.
An unexpected SSL communications error occurred for a channel. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. func is the name of the System SSL function that gave the error, and return-code is the return code (in decimal).
8
The channel is stopped.
See Appendix E. Secure Sockets Layer (SSL) return codes for the cause of the return code from System SSL and the System Secure Sockets Layer Programming Guide and Reference manual for more information.
An unexpected SSL communications error occurred for an SSL server subtask. func is the name of the System SSL function that gave the error, and return-code is the return code (in decimal).
8
The SSL server subtask terminates.
See Appendix E. Secure Sockets Layer (SSL) return codes for the cause of the return code from System SSL and the System Secure Sockets Layer Programming Guide and Reference manual for more information.
Channel channel-name cannot start because it requires SSL, but SSL communications are not currently available.
8
The channel does not start.
If SSL is required, investigate why it is not available and take action as appropriate; it may be necessary to restart the channel initiator to allow SSL to be used. If SSL is not required, change the channel definition so that SSL is not used.
The SSL cipher specification value for channel channel-name is local-ciph, but the value specified at the remote end is remote-ciph. The two values must be the same before the channel can be started. They are shown in the message as two-character codes; common values are as shown in message CSQX635E.
8
The channel does not start.
Change either the local or remote channel definition so that the values specified for the SSL cipher specification are the same.
The certificate sent from the remote end during SSL handshaking was accepted, but no user ID could be found associated with it. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
Likely causes are that neither the certificate nor a matching certificate name are defined to the external security manager (ESM), or that the certificate contains fields that are not understood by the ESM.
0
The user ID of the channel initiator address space is used as the channel user ID for the channel.
If certificate name filtering is being used, you can create a filter that will match this certificate. Alternatively, change the SSLPEER channel attribute to prevent this certificate being accepted from the remote channel.
The certificate sent from the remote end during SSL handshaking could not be validated. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
8
The channel will not start.
Ensure that the SSL certificate connected to the key repository at the remote end is valid, and that the signing certificate(s) have been connected to the key ring on the local queue manager so that the certificate sent can be authenticated.
For full details about SSL certificates and key repositories see WebSphere MQ Security.
The certificates sent to the remote end using the connection conn-id during SSL handshaking could not be validated. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
8
The channel will not start.
Ensure that the SSL certificate 'ibmWebSphereMQqmgr-name' connected to in the key ring at the local queue manager qmgr-name is valid, and that the signing certificate has been connected to the key repository on the remote end so that the certificate sent can be authenticated.
For full details about SSL certificates and key repositories see WebSphere MQ Security.
The SSL cipher specification value for channel channel-name is not valid. The value is shown in the message as a two-character code; common values are:
In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Correct the SSL cipher specification for the channel.
The distinguished name, dist-name, specified in the SSL certificate at the remote end does not match the SSL peer name for channel channel-name. The distinguished name at the remote end must match the peer name specified (which can be generic) before the channel can be started. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
If you wish to allow this remote end to connect, change the SSL peer name specification for the channel so that it matches the distinguished name in the SSL certificate at the remote end, or obtain the correct certificate for the remote end, as appropriate.
The remote channel did not supply a certificate to use during SSL handshaking, but a certificate is required. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
8
The channel will not start.
Ensure that the SSL certificate is connected to the key repository of the remote end; alternatively, if appropriate, change the local channel definition so that its SSLCAUTH attribute is set to OPTIONAL.
For full details about SSL certificates and key repositories see WebSphere MQ Security.
An unexpected SSL communications error occurred for a channel, as reported in the preceding messages. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
8
The channel will not start.
Investigate the problem reported in the preceding messages. Review the local and remote console logs for reports of network errors.
No SSL cipher specification was supplied by the remote channel channel-name, but one was required. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Change the remote channel definition so that the value specified for the SSL cipher specification is the same as that of the local channel.
The SSL peer name for channel channel-name includes a distinguished name attribute key key-name which is invalid or unsupported. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Correct the SSL peer name for the channel.
An error occurred with the SSL cipher specification for remote channel channel-name. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Review the remote console log to determine the cipher specification error.
The channel channel-name. did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote end. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Ensure that the key ring of the local queue manager qmgr-name has an SSL certificate connected to it called 'ibmWebSphereMQqmgr-name'; alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL.
For full details about SSL certificates and key repositories see WebSphere MQ Security.
An error occurred with the SSL peer name for remote channel channel-name. In some cases the channel name cannot be determined and so is shown as '????'.
8
The channel will not start.
Review the remote console log to determine the peer name error.
The peer name associated with the certificate sent from the remote end during SSL handshaking could not be determined. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
If the local channel has a peer name specified it does not start.
Ensure that the SSL certificate 'ibmWebSphereMQqmgr-name' in the key ring at the local queue manager qmgr-name is valid, and that the signing certificate has been connected to the key repository on the remote end so that the certificate sent can be authenticated. Check that the local and remote channel definitions are correct.
For full details about SSL certificates and key repositories see WebSphere MQ Security.
An SSL certificate 'ibmWebSphereMQqmgr-name' or the default certificate cannot be found in the key ring or the certificate is not trusted. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel will not start.
Ensure that there is an SSL certificate 'ibmWebSphereMQqmgr-name' or a default certificate in the key ring and that it is valid.
While checking CRLs for a channel, an error occurred in setting up the LDAP environment or retrieving an LDAP directory entry. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel will not start.
Ensure that the LDAP server is specified and set up correctly, and is running.
The current time is either before the SSL certificate start time or or after the end time. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The connection is conn-id.
4
The channel will not start.
Obtain a new certificate if the certifiacte has expired, or wait until the certificate becomes valid if it is not valid yet.
In the SSL certificate sent from the remote end using the connection conn-id, the certificate signature is not correct. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel will not start.
Ensure that the SSL certificate connected to the key repository at the remote end is valid.
The remote end of a channel using SSL communications closed the socket or sent a close notification alert. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel stops.
Examine the console log for the remote end to determine the cause of the failure.
While checking CRLs for a channel, the required LDAP server was not available. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel does not start.
Ensure that the LDAP server is running.
The refresh of the cached SSL key repository could not be completed because of errors.
4
The refresh is incomplete.
Examine the console log for messages that may indicate why the refresh could not be started.
The refresh of the cached SSL key repository has completed, so the latest values and certificates are in use for all SSL channels. However, not all the outbound SSL channels which were running when the refresh was initiated could be restarted after the refresh had completed.
4
Processing continues.
Examine the console log for messages identifying the channels that did not restart.
The cached SSL key repository is being refreshed, which involves stopping all the channels that use SSL communications. One or more of the channels is taking too long to stop. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The refresh is terminated. Some channels using SSL will have been stopped.
Stop any SSL channels that have not already stopped and issue the REFRESH SECURITY TYPE(SSL) command again.
A channel using SSL communications could not be started because the cached SSL key repository is currently being refreshed. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel does not start.
Wait until the refresh has completed and start the channel again.
A channel using SSL communications could not be started because the cached SSL key repository is currently being refreshed at the remote end. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel does not start.
Wait until the refresh has completed and start the channel again.
The SSL key repository (that is, the key ring in the external security manager) does not contain any valid certificates.
4
Channels using SSL communications will not start.
Add the user certificate and any necessary certification authority (CA) certificates to the key repository. Ensure that existing certificates are valid, have not expired, and are marked as trusted.
The SSL key repository (that is, the key ring in the external security manager) does not contain any valid certification authority (CA) certifcates. A channel using SSL communications needs at least one CA or self-signed certificate in order to perform client authentication.
4
Channels using SSL communications will not start.
Add the user certificate and any necessary certification authority (CA) certificates to the key repository. Ensure that existing certificates are valid, have not expired, and are marked as trusted.
A self-signed certificate cannot be validated as it is not in the SSL key repository. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel is not started.
Add the self-signed certificate to the key repository.
The SSL certificate 'ibmWebSphereMQqmgr-name' has no associated private key, or the private key is not available because it key is stored in ICSF and ICSF services are not available. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel is not started.
Ensure that the private key associated with the SSL certificate 'ibmWebSphereMQqmgr-name' is available. Ensure that the ICSF started task is running if the private key is stored in ICSF.
The SSL certificate has been revoked by the certification authority (CA). The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel is not started.
Obtain a new certificate and add it to the key repository.
The SSL key repository does not contain a certificate for the certification authority (CA). The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'.
4
The channel is not started.
Obtain a certificate for the certification authority (CA) and add it to the key repository.
A Certificate Revocation List (CRL) is not valid and cannot be processed.
4
The channel is not started.
Contact the certification authority and obtain a replacement CRL.
This is issued in response to the DISPLAY CHINIT command if the channel initiator is active.
0
This is issued in response to the DISPLAY CHINIT command, and shows how many adapter subtasks are currently active, and how many were requested by the CHIADAPS queue manager attribute. If the numbers differ, some adapter subtasks have failed and not been restarted, which could reduce processing capacity.
0
This is issued in response to the DISPLAY CHINIT command, and shows how many dispatchers are currently active, and how many were requested by the CHIDISPS queue manager attribute. If the numbers differ, some dispatchers have failed and not been restarted. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately, and other processing capacity may be reduced.
0
This is issued in response to the DISPLAY CHINIT command, and shows how many SSL server subtasks are currently active, and how many were requested by the SSLTASKS queue manager attribute. If the numbers differ, some SSL server subtasks have failed and not been restarted, which could reduce processing capacity.
0
This is issued in response to the DISPLAY CHINIT command. It shows the maximum numbers of each type of channel that are allowed.
0
This is issued in response to the DISPLAY CHINIT command. It shows how many channels are current, and how many are allowed altogether, as requested by the MAXCHL queue manager attribute.
0
This is issued in response to the DISPLAY CHINIT command. Of the channels that are current, it shows how many are active (transmitting messages), and how many are allowed altogether to be active, by the ACTCHL queue manager attribute. It also shows how many of the active channels are paused, waiting to retry putting a message.
0
This is issued in response to the DISPLAY CHINIT command. Of the channels that are current, it show how many are:
0
This is issued in response to the DISPLAY CHINIT command for each TCP/IP listener that is trying to restart after an error. The channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.
port and ip-address show the port and IP address combination on which it listens; if ip-address is '*', it listens on all available IP addresses. disposition shows which type of incoming requests the listener handles:
0
This is issued in response to the DISPLAY CHINIT command for each LU 6.2 listener that is trying to restart after an error. The channel initiator will attempt to restart the listener at the intervals specified by the LSTRTMR queue manager attribute.
disposition shows which type of incoming requests the listener handles:
0
This is issued in response to the DISPLAY CHINIT command, and shows the TCP/IP system name that is being used, as specified in the TCPNAME queue manager attribute.
0
This is issued in response to the DISPLAY CHINIT command for each TCP/IP listener that is active.
port and ip-address show the port and IP address combination on which it listens; if ip-address is '*', it listens on all available IP addresses. disposition shows which type of incoming requests the listener handles:
0
This is issued in response to the DISPLAY CHINIT command for each LU 6.2 listener that is active.
disposition shows which type of incoming requests the listener handles:
0
This is issued in response to the DISPLAY CHINIT command for each TCP/IP listener that is not active.
disposition shows which type of incoming requests the listener handles:
0
If the listener had been started, and was not deliberately stopped, this may be because there was an error in the communications system. The channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.
This is issued in response to the DISPLAY CHINIT command for each LU 6.2 listener that is not active.
disposition shows which type of incoming requests the listener handles:
0
If the listener had been started, and was not deliberately stopped, this may be because there was an error in the communications system. The channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0420 |