Distributed queuing messages (CSQX...)

 

CSQX000I
IBM WebSphere MQ for z/OS version
Explanation:

This message is issued when the channel initiator starts, and shows the release level.

Severity:

0

CSQX001I
csect-name Channel initiator starting
Explanation:

The channel initiator address space is starting, in response to a START CHINIT command.

Severity:

0

System Action:

Channel initiator startup processing begins. Message CSQX022I is sent when the startup process has completed.

CSQX002I
csect-name Queue-sharing group is qsg-name
Explanation:

This is issued during channel initiator startup processing or in response to the DISPLAY CHINIT command if the queue manager that the channel initiator uses is in a queue-sharing group.

Severity:

0

System Action:

Processing continues.

CSQX003I
csect-name Obsolete parameter module ignored
Explanation:

The START CHINIT command specified a parameter module name using the PARM keyword. The use of a channel initiator parameter module is obsolete, so the name is ignored.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

Channel initiator parameters are specified by queue manager attributes. Use the ALTER QMGR command to set the values you want.

CSQX005E
csect-name Channel initiator failed to start
Explanation:

A severe error, as reported in the preceding messages, occurred during channel initiator startup processing.

Severity:

8

System Action:

The channel initiator started task terminates.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX006E
csect-name Channel initiator failed while stopping
Explanation:

A severe error, as reported in the preceding messages, occurred during channel initiator termination processing.

Severity:

8

System Action:

The channel initiator started task terminates.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX007E
csect-name Unable to connect to queue manager qmgr-name, MQCC=mqcc MQRC=mqrc
Explanation:

An attempt by the channel initiator to connect to the queue manager was unsuccessful.

Severity:

8

System Action:

If the error occurred during the channel initiator startup procedure, the channel initiator does not start. In other cases, the component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, or listener) does not start and the function it provides is unavailable; in most cases, the end result is that the channel initiator terminates.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. If you are unable to solve the problem, contact your IBM support center.

CSQX008E
csect-name Unable to disconnect from queue manager qmgr-name, MQCC=mqcc MQRC=mqrc
Explanation:

An attempt by the channel initiator to disconnect from the queue manager was unsuccessful.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc to determine the cause of the problem. If you are unable to solve the problem, contact your IBM support center.

CSQX009I
csect-name Channel initiator stopping
Explanation:

A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX010I
csect-name Channel initiator stopped
Explanation:

The channel initiator terminated following an error, as reported in the preceding messages.

Severity:

0

System Action:

None.

CSQX011I
csect-name Client attachment feature available
Explanation:

The client attachment feature has been installed, so clients can be attached to and MQI channels can be used with the channel initiator.

Severity:

0

System Action:

The channel initiator startup processing continues.

CSQX012E
csect-name Unable to open ddname data set
Explanation:

The ddname data set could not be opened, as reported in the preceding messages.

Severity:

4

System Action:

Processing continues, but functions that require the data set will be inhibited. For example, if the exit library data set CSQXLIB cannot be opened, user channel and channel auto-definition exits will not be available, and channels that use them will not start. If the error information data set CSQSNAP cannot be opened, the error information will be lost.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX013I
csect-name Address conflict for listener, port port address ip-address, TRPTYPE=TCP INDISP=disposition
Explanation:

A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already active for a port and IP address combination that conflicted with the requested port and IP address. If ip-address is '*', all IP addresses were requested.

The port and IP address combination specified must match a combination for which the listener is active. It cannot be a superset or a subset of that combination.

Severity:

4

System Action:

None.

System Programmer Response:

Reissue the command correctly if necessary.

CSQX014E
csect-name Listener exceeded channel limit, TRPTYPE=trptype INDISP=disposition
Explanation:

The number of current channels using the indicated communications system trptype is the maximum allowed. The listener cannot accept an incoming request to start another channel; if the maximum is 0, the listener itself cannot start. (The name of the channel requested cannot be determined because the listener could not accept the request.) Current channels include stopped and retrying channels as well as active channels.

disposition shows which type of incoming requests the listener was handling:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.

The maximum allowed is specified in the TCPCHL or LU62CHL queue manager attribute respectively, but may be reduced if a dispatcher fails, or if TCP/IP resources are restricted (as reported by message CSQX118I).

Severity:

8

System Action:

The channel or listener does not start.

System Programmer Response:

If the maximum allowed is zero, communications using the indicated system trptype are not allowed, and no such channels can be started. The listener also cannot be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the remote channel, or use the ALTER QMGR command to increase TCPCHL or LU62CHL.

CSQX015I
csect-name started dispatchers started, failed failed
Explanation:

The channel initiator startup procedure has started the requested number of dispatchers; started dispatchers started successfully and failed dispatchers did not start.

Severity:

0

System Action:

The channel initiator startup processing continues. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately if some dispatchers did not start.

System Programmer Response:

If the message indicates that some dispatchers failed, investigate the problem reported in the preceding messages.

CSQX016I
csect-name Listener already started, TRPTYPE=trptype INDISP=disposition
Explanation:

A START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already active.

Severity:

0

System Action:

None.

CSQX017I
csect-name Listener already started, port port address ip-address, TRPTYPE=TCP INDISP=disposition
Explanation:

A START LISTENER command was issued specifying TRPTYPE(TCP) and INDISP(disposition), but that listener was already active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.

Severity:

0

System Action:

None.

CSQX018I
csect-name Listener already stopped or stopping, TRPTYPE=trptype INDISP=disposition
Explanation:

A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already stopped or in the process of stopping.

Severity:

0

System Action:

None.

CSQX019I
csect-name Listener already stopped or stopping, port port address ip-address, TRPTYPE=TCP INDISP=disposition
Explanation:

A STOP LISTENER or START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), but that listener was already stopped or in the process of stopping for the requested port and IP address. If ip-address is '*', all IP addresses were requested.

Severity:

0

System Action:

None.

CSQX020I
csect-name Shared channel recovery completed
Explanation:

The channel initiator startup procedure has successfully completed the shared channel recovery process, for channels that were owned by itself and for channels that were owned by other queue managers.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

See message CSQM052I issued by the queue manager for more details.

CSQX021E
csect-name Shared channel recovery error
Explanation:

The channel initiator startup procedure did not complete the shared channel recovery process, because an error occurred.

Severity:

0

System Action:

The recovery process is terminated; some channels may have been recovered, while others have not.

System Programmer Response:

See the error messages (such as CSQM053E) issued by the queue manager for more details. When the problem has been resolved, either start any unrecovered channels manually, or restart the channel initiator.

CSQX022I
csect-name Channel initiator initialization complete
Explanation:

Initialization of the channel initiator completed normally, and the channel initiator is ready for use. Note, however, that processing of the CSQINPX command data set may still be in progress; its completion is shown by message CSQU012I.

Severity:

0

System Action:

None.

CSQX023I
csect-name Listener started, port port address ip-address, TRPTYPE=TCP INDISP=disposition
Explanation:

A START LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition). That listener is now active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.

Severity:

0

System Action:

None.

CSQX024I
csect-name Listener stopped, port port address ip-address, TRPTYPE=TCP INDISP=disposition
Explanation:

A STOP LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition). That listener is no longer active for the requested port and IP address. If ip-address is '*', all IP addresses were requested.

Severity:

0

System Action:

None.

CSQX026E
csect-name Unable to locate the trace header, RC=12
Explanation:

The trace formatting routine was unable to locate the trace control information in the trace data space in a dump of the channel initiator address space.

Severity:

8

System Action:

Formatting terminates.

System Programmer Response:

The most likely cause is that the dump has not been produced correctly. Re-create the dump, and try again.

CSQX027E
csect-name Unable to get storage, RC=return-code
Explanation:

An attempt to obtain some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.

Severity:

8

System Action:

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, listener, repository manager, supervisor, or trace formatter) usually terminates; in many cases, the end result will be that the channel initiator terminates.

System Programmer Response:

See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.

CSQX028E
csect-name Unable to free storage, RC=return-code
Explanation:

An attempt to release some storage failed. return-code is the return code (in hexadecimal) from the z/OS STORAGE service.

Severity:

8

System Action:

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, or listener) usually ignores the error and continues processing.

System Programmer Response:

See the MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.

CSQX029I
csect-name Queue manager qmgr-name stopping, MQCC=mqcc MQRC=mqrc
Explanation:

In response to an MQ API call, the queue manager notified the channel initiator that it is stopping.

Severity:

0

System Action:

The channel initiator terminates.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX030I
csect-name 'type' trace started, assigned trace number tno
Explanation:

During channel initiator initialization, a type trace has been started automatically and assigned the trace number tno.

System Action:

Processing continues.

CSQX031E
csect-name Initialization command handler ended abnormally, reason=00sssuuu
Explanation:

The initialization command handler, which processes the CSQINPX command data set, is ending abnormally. sss is the system completion code, and uuu is the user completion code (both in hexadecimal).

Severity:

8

System Action:

The initialization command handler ends abnormally, but the channel initiator continues.

System Programmer Response:

If a system completion code is shown, see the MVS System Codes manual for information about the problem; the message will normally be preceded by other messages giving additional information.

The most likely cause is erroneous definition of the CSQINPX and CSQOUTX data sets. See the WebSphere MQ for z/OS System Setup Guide for information about the initialization command handler and these data sets. If you are unable to solve the problem, contact your IBM support center.

CSQX032I
csect-name Initialization command handler terminated
Explanation:

The initialization command handler, which processes the CSQINPX command data set, was terminated before completing all the commands because the channel initiator is stopping, and so cannot process any more commands.

Severity:

4

System Action:

The initialization command handler ends.

System Programmer Response:

Refer to the CSQOUTX data set for information about the commands that were processed. If the channel initiator is not stopping because of a STOP command, refer to the preceding messages for information about the problem causing it to stop.

See the WebSphere MQ for z/OS System Setup Guide for information about the initialization command handler.

CSQX033E
csect-name Channel initiator stopping because of errors
Explanation:

A severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX034I
csect-name Channel initiator stopping because queue manager is stopping
Explanation:

The queue manager notified the channel initiator that it is stopping.

Severity:

0

System Action:

The channel initiator terminates.

CSQX035I
csect-name Connection to queue manager qmgr-name stopping or broken, MQCC=mqcc MQRC=mqrc
Explanation:

In response to an MQ API call, the channel initiator found that its connection to the queue manager was no longer available.

Severity:

0

System Action:

The channel initiator terminates.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX036E
csect-name Unable to open name, MQCC=mqcc MQRC=mqrc
Explanation:

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.)

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX037E
csect-name Unable to get message from name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQGET call for queue name was unsuccessful.

Severity:

8

System Action:

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.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX038E
csect-name Unable to put message to name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQPUT call for queue name was unsuccessful.

Severity:

8

System Action:

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.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX039E
csect-name Unable to close name, MQCC=mqcc MQRC=mqrc
Explanation:

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.)

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX040E
csect-name Unable to inquire attributes for name, MQCC=mqcc MQRC=mqrc
Explanation:

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.)

Severity:

8

System Action:

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.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX041E
csect-name Unable to set attributes for name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQSET call for queue name was unsuccessful.

Severity:

8

System Action:

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.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX042E
csect-name Unable to define comp to CTRACE, RC=rc reason=reason
Explanation:

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.

Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX043E
csect-name Unable to delete comp from CTRACE, RC=rc reason=reason
Explanation:

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.

Severity:

4

System Action:

Channel initiator termination processing continues.

System Programmer Response:

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.

CSQX044E
csect-name Unable to initialize PC routines, RC=rc reason=reason
Explanation:

The PC routines required by the channel initiator could not be defined. The reason code reason shows which z/OS service failed:

00E74007

LXRES failed

00E74008

ETCRE failed

00E74009

ETCON failed

rc is the return code (in hexadecimal) from the indicated OS/390 service.

Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX045E
csect-name Unable to load module-name, reason=ssssrrrr
Explanation:

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.

System Action:

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.

System Programmer Response:

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.

CSQX046E
csect-name Unable to initialize data conversion services, reason=reason
Explanation:

The data conversion services required by the channel initiator could not be initialized. The reason code reason shows why:

00C10002

Unable to load modules

00C10003

Insufficient storage

other

Internal error
Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX047E
csect-name Unable to commit messages for name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQCMIT call involving messages for queue name was unsuccessful.

Severity:

8

System Action:

The component where the error occurred (supervisor) terminates.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX048I
csect-name Unable to convert message for name, MQCC=mqcc MQRC=mqrc
Explanation:

A message being put to an IMS bridge queue name required data conversion, but the conversion was not successful.

Severity:

0

System Action:

The message is put without conversion, and processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX049E
csect-name Unable to retrieve token for name name, RC=rc
Explanation:

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.

Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX050E
csect-name Unable to create access list for queue manager, RC=rc
Explanation:

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.

Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX051E
csect-name Unable to share storage with the queue manager, RC=rc
Explanation:

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.

Severity:

8

System Action:

The channel initiator does not start.

System Programmer Response:

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.

CSQX052E
csect-name Timer task attach failed, RC=return-code
Explanation:

The repository manager task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

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.

CSQX053E
csect-name Error information recorded in CSQSNAP data set
Explanation:

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.

Severity:

8

System Action:

Processing continues.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX054E
csect-name Repository manager ended abnormally, reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

The repository manager ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.

System Programmer Response:

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.

CSQX055E
csect-name Repository manager attach failed, RC=return-code
Explanation:

The repository manager task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

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.

CSQX056E
csect-name Preinitialization services request failed, function code=func, RC=rc
Explanation:

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.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX057E
csect-name Cluster cache task attach failed, RC=return-code
Explanation:

The channel initiator cluster cache task could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

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.

CSQX058E
csect-name Pause service service-name failed, RC=return-code
Explanation:

An error occurred processing a pause element. return-code is the return code (in hexadecimal) from the z/OS pause service service-name.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX059E
csect-name Unable to increase cluster cache
Explanation:

The dynamic cluster cache cannot be increased because the channel initiator cluster cache task encountered an error.

Severity:

8

System Action:

The channel initiator terminates.

System Programmer Response:

Investigate the problem reported in any preceding messages.

CSQX070I
csect-name CHINIT parameters ...
Explanation:

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.

Severity:

0

System Action:

The channel initiator startup processing continues.

System Programmer Response:

Channel initiator parameters are specified by queue manager attributes. Use the ALTER QMGR command to set the values you want.

CSQX100E
csect-name Dispatcher failed to start, TCB=tcb-name
Explanation:

A severe error, as reported in the preceding messages, occurred during dispatcher startup processing.

Severity:

8

System Action:

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.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX101E
csect-name Dispatcher unable to schedule essential process process
Explanation:

During dispatcher startup processing, one of the essential dispatcher processes (named process) could not be scheduled.

Severity:

8

System Action:

The dispatcher does not start.

System Programmer Response:

The most likely cause is insufficient storage. If increasing the available storage does not solve the problem, contact your IBM support center.

CSQX102E
csect-name Dispatcher linkage stack error, TCB=tcb-name
Explanation:

The dispatcher using TCB tcb-name found an inconsistency in the linkage stack.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX103E
csect-name Dispatcher unexpected error, TCB=tcb-name RC=return-code
Explanation:

The dispatcher using TCB tcb-name had an internal error.

Severity:

8

System Action:

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.

System Programmer Response:

Contact your IBM support center to report the problem.

CSQX104E
csect-name Unable to establish ESTAE, RC=return-code
Explanation:

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.

Severity:

8

System Action:

The component that was starting (dispatcher, adapter subtask, SSL server subtask, supervisor, repository manager, or channel initiator itself) does not start.

System Programmer Response:

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.

CSQX106E
csect-name Unable to connect to TCP/IP using OpenEdition, service 'serv' RC=return-code reason=reason
Explanation:

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:

  • The user ID that the channel initiator uses is not set up correctly for use with OpenEdition. For example, it may not have a valid OMVS segment defined or its security profile may be incomplete.

  • The TCPNAME queue manager attribute does not specify a valid TCP/IP stack name. These stack names are defined in the SUBFILESYSTYPE NAME parameter in member BPXPRMxx for SYS1.PARMLIB.

  • The MAXFILEPROC or MAXPROCUSER parameter in member BPXPRMxx for SYS1.PARMLIB is too small.

Severity:

4

System Action:

Processing continues, but communications using TCP/IP with the OpenEdition sockets interface will not be available.

System Programmer Response:

See the z/OS OpenEdition Messages and Codes manual for information about the codes from the service request.

CSQX107I
csect-name TCP/IP communications unavailable
Explanation:

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.

Severity:

4

System Action:

Processing continues, but communications using TCP/IP will not be available.

System Programmer Response:

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.

CSQX110E
csect-name User data conversion exit error, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

The process ends abnormally, and a dump is normally issued. The channel is stopped, and must be restarted manually.

System Programmer Response:

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.

CSQX111E
csect-name User channel exit error, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX112E
csect-name Dispatcher process error, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX113E
csect-name Dispatcher ended abnormally, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

The dispatcher ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.

System Programmer Response:

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.

CSQX114E
csect-name Dispatcher failed, reason=reason
Explanation:

A dispatcher ended abnormally, as reported in the preceding messages, and could not be restarted. reason shows the type of failure:

0000000A

Startup error

0000000B

Linkage stack error

0000000D

Uncorrectable error

other

Completion code in the form 00sssuuu, where sss is the system completion code and uuu is the user completion code (both in hexadecimal).
Severity:

8

System Action:

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.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX115E
csect-name Dispatcher not restarted - too many failures
Explanation:

A dispatcher failed; because it had already failed too many times, the channel initiator did not attempt to restart it.

Severity:

8

System Action:

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.

System Programmer Response:

Investigate the problems causing the dispatcher failures.

CSQX116I
csect-name Dispatcher restarted, number dispatchers active
Explanation:

A dispatcher failed, but was successfully restarted by the channel initiator. number dispatchers are now active.

Severity:

0

System Action:

Processing continues. The number of current TCP/IP and LU 6.2 channels allowed will be increased proportionately.

CSQX118I
csect-name TCP/IP channel limit reduced to nn
Explanation:

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:

  • TCP/IP resources are restricted. The OpenEdition MAXFILEPROC parameter (specified in the BPXPRMxx member of SYS1.PARMLIB) controls how many sockets each task is allowed: in other words, how many channels each dispatcher is allowed

  • Some dispatchers have failed and not been restarted; the number of current TCP/IP channels allowed will be reduced proportionately

Severity:

0

System Programmer Response:

If TCP/IP resources are restricted, consider increasing either the OpenEdition MAXFILEPROC parameter or the number of dispatchers if we need more current TCP/IP channels.

CSQX119I
csect-name LU 6.2 channel limit reduced to nn
Explanation:

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.

Severity:

0

CSQX140E
csect-name Adapter failed to start
Explanation:

A severe error, as reported in the preceding messages, occurred during adapter subtask startup processing.

Severity:

8

System Action:

The channel initiator will attempt to restart the adapter subtask.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX141I
csect-name started adapter subtasks started, failed failed
Explanation:

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.

Severity:

0

System Action:

The channel initiator startup processing continues.

System Programmer Response:

If the message indicates that some adapter subtasks failed, investigate the problem reported in the preceding messages.

CSQX142E
csect-name Adapter subtask failed to start, TCB=tcb-name
Explanation:

A severe error, as reported in the preceding messages, occurred during adapter subtask startup processing.

Severity:

8

System Action:

The channel initiator will attempt to restart the adapter subtask.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX143E
csect-name Adapter subtask ended abnormally, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

The adapter subtask ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.

System Programmer Response:

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.

CSQX144E
csect-name Adapter subtask attach failed, RC=return-code
Explanation:

An adapter subtask could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

Severity:

8

System Action:

The adapter subtask is not restarted.

System Programmer Response:

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.

CSQX145E
csect-name Adapter subtask not restarted - too many failures
Explanation:

A adapter subtask failed; because it had already failed too many times, the channel initiator did not attempt to restart it.

Severity:

8

System Action:

The adapter subtask is not restarted; processing capacity may therefore be reduced.

System Programmer Response:

Investigate the problems causing the adapter subtask failures.

CSQX146I
csect-name Adapter subtask restarted, active subtasks active
Explanation:

A adapter subtask failed, but was successfully restarted by the channel initiator. active adapter subtasks are now active.

Severity:

0

System Action:

Processing continues.

CSQX150E
csect-name SSL server failed to start
Explanation:

A severe error, as reported in the preceding messages, occurred during SSL server subtask startup processing.

Severity:

8

System Action:

The channel initiator will attempt to restart the SSL server subtask.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX151I
csect-name started SSL server subtasks started, failed failed
Explanation:

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.

Severity:

0

System Action:

The channel initiator startup processing continues.

System Programmer Response:

If the message indicates that some SSL server subtasks failed, investigate the problem reported in the preceding messages.

CSQX152E
csect-name SSL server subtask failed to start, TCB=tcb-name
Explanation:

A severe error, as reported in the preceding messages, occurred during SSL server subtask startup processing.

Severity:

8

System Action:

The channel initiator will attempt to restart the SSL server subtask.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX153E
csect-name SSL server subtask ended abnormally, TCB=tcb-name reason=sssuuu-reason
Explanation:

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).

Severity:

8

System Action:

The SSL server subtask ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart it.

System Programmer Response:

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.

CSQX154E
csect-name SSL server subtask attach failed, RC=return-code
Explanation:

An SSL server subtask could not be attached. return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

Severity:

8

System Action:

The SSL server subtask is not restarted.

System Programmer Response:

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.

CSQX155E
csect-name SSL server subtask not restarted - too many failures
Explanation:

A SSL server subtask failed; because it had already failed too many times, the channel initiator did not attempt to restart it.

Severity:

8

System Action:

The SSL server subtask is not restarted; processing capacity may therefore be reduced.

System Programmer Response:

Investigate the problems causing the SSL server subtask failures.

CSQX156I
csect-name SSL server subtask restarted, active subtasks active
Explanation:

A SSL server subtask failed, but was successfully restarted by the channel initiator. active SSL server subtasks are now active.

Severity:

0

System Action:

Processing continues.

CSQX160E
csect-name SSL communications unavailable
Explanation:

SSL communications are requested but an error, as reported in the preceding messages, occurred during channel initiator startup processing.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

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.

CSQX161E
csect-name SSL key repository name not specified
Explanation:

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.

Severity:

4

System Action:

Processing continues, but communications using SSL will not be available.

System Programmer Response:

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.

CSQX162E
csect-name SSL CRL namelist is empty or wrong type
Explanation:

SSL communications are requested but the SSL authentication namelist specified by the SSLCRLNL queue manager attribute is empty or not of type AUTHINFO.

Severity:

4

System Action:

Processing continues, but communications using SSL will not be available.

System Programmer Response:

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.

CSQX163I
csect-name SSL CRL namelist has too many names - first n used
Explanation:

The SSL authentication namelist specified by the SSLCRLNL queue manager attribute has more names than are supported. The number supported is n.

Severity:

4

System Action:

Processing continues; the excess names are ignored.

System Programmer Response:

Correct the definitions of the namelist.

CSQX164E
csect-name Unable to access SSL key repository
Explanation:

The SSL key respository, whose name is specified by the SSLKEYR queue manager attribute, could not be accessed.

The most likely causes are:

  • The specified key repository does not exist.

  • The channel initiator does not have permission to read the specified key repository.

  • The channel initiator was unable to connect to the LDAP server specified in an authentication information object listed in the SSL CRL namelist.

  • When using shared key rings, the name is not prefixed with 'userid/'.

Severity:

4

System Action:

Processing continues, but communications using SSL will not be available. Channels using SSL communications will not start.

System Programmer Response:

Check that:

  • the SSL key repository name is specified correctly; if using a shared key ring, it is prefixed with 'userid/'

  • the key ring specified as the SSL key repository exists, and the channel initiator has permission to read it

  • the LDAP name is specified correctly and that it is available.

CSQX165I
csect-name SSL key repository refresh already in progress
Explanation:

A REFRESH SECURITY TYPE(SSL) command was issued, but an SSL key repository refresh was already in progress.

System Action:

The command is ignored. The refresh currently in progress continues.

Severity:

0

CSQX181E
csect-name Invalid response response set by exit exit-name
Explanation:

The user exit exit-name returned an invalid response code (response, shown in hexadecimal) in the ExitResponse field of the channel exit parameters (MQCXP).

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid response code.

CSQX182E
csect-name Invalid secondary response response setby exit exit-name
Explanation:

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).

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid secondary response code.

CSQX184E
csect-name Invalid exit buffer address address set by exit exit-name
Explanation:

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.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

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.

CSQX187E
csect-name Invalid header compression value set by exit exit-name
Explanation:

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.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid value. If necessary, alter the channel definitions so that the desired compression value is acceptable.

CSQX188E
csect-name Invalid message compression value set by exit exit-name
Explanation:

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.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid value. If necessary, alter the channel definitions so that the desired compression value is acceptable.

CSQX189E
csect-name Invalid data length length set by exit exit-name
Explanation:

The user exit exit-name returned a data length value that was not greater than zero.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid data length.

CSQX190E
csect-name Channel channel-name stopping because of error in exit exit-name, Id=ExitId reason=ExitReason
Explanation:

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:

11

MQXT_CHANNEL_SEC_EXIT, security exit

12

MQXT_CHANNEL_MSG_EXIT, message exit

13

MQXT_CHANNEL_SEND_EXIT, send exit

14

MQXT_CHANNEL_RCV_EXIT, receive exit

16

MQXT_CHANNEL_AUTO_DEF_EXIT, auto-definition exit

and ExitReason shows the reason for invoking it:

11

MQXR_INIT, initialization

12

MQXR_TERM, termination

13

MQXR_MSG, process a message

14

MQXR_XMIT, process a transmission

15

MQXR_SEC_MSG, security message received

16

MQXR_INIT_SEC, initiate security exchange

18

MQXR_AUTO_CLUSSDR, auto-definition of cluster-sender channel

28

MQXR_AUTO_CLUSRCVR, auto-definition of cluster-receiver channel
Severity:

8

System Action:

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.

System Programmer Response:

Investigate why the user exit program set invalid values.

CSQX196E
csect-name Data length data-length set by exit exit-name is larger than agent buffer length ab-length
Explanation:

The user exit exit-name returned data in the supplied agent buffer, but the length specified is greater than the length of the buffer.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid data length.

CSQX197E
csect-name Data length data-length set by exit exit-name is larger than exit buffer length eb-length
Explanation:

The user exit exit-name returned data in the supplied exit buffer, but the length specified is greater than the length of the buffer.

Severity:

8

System Action:

Message CSQX190E is issued giving more details, and the channel stops. For auto-defined channels, the channel does not start.

System Programmer Response:

Investigate why the user exit program set an invalid data length.

CSQX199E
csect-name Unrecognized message code ccc
Explanation:

An unexpected error message code has been issued by the channel initiator.

Severity:

8

System Action:

Processing continues.

System Programmer Response:

Note the code ccc (which is shown in hexadecimal) and contact your IBM support center to report the problem.

CSQX201E
csect-name Unable to allocate conversation, channel channel-name, connection conn-id TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX202E
csect-name Connection or remote listener unavailable, channel channel-name, connection conn-id TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The attempt to start the channel is retried.

System Programmer Response:

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.

CSQX203E
csect-name Error in communications configuration, channel channel-name, connection conn-id TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

See Appendix D. Communications protocol return codes for information about the cause of the return code from the communications system.

Probable causes are:

  • If the communications protocol is LU 6.2:

    • One of the transmission parameters (MODENAME or TPNAME or PARTNER_LU) in the side information is incorrect, or that there is no side information for the symbolic destination name specified as the connection name. Correct the error and try again.

    • An LU 6.2 session has not been established, perhaps because the LU has not been enabled. Issue the z/OS command VARY ACTIVE if this is the case.

  • If the communications protocol is TCP/IP:

    • The connection name specified is incorrect, or that it cannot be resolved to a network address, or the name may not be in the name server. Correct the error and try again.

    • If the return code is zero, there is a name server problem. The OMVS command OPING usually fails in the same way. Resolve this failure and restart the channel. Check the

      /etc/resolv.conf file and check that the correct name server address is specified in the NSINTERADDR statement.

See the z/OS UNIX System Services Messages and Codes manual for information about the reason code.

CSQX204E
csect-name Connection attempt rejected, channel channel-name, connection conn-id TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX205E
csect-name Unable to resolve network address, channel channel-name, connection conn-id TRPTYPE=TCP RC=return-code reason=reason
Explanation:

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX206E
csect-name Error sending data, channel channel-name, connection conn-id (queue manager qmgr-name) TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The channel is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX207E
csect-name Invalid data received, connection conn-id (queue manager qmgr-name) TRPTYPE=trptype
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS
Severity:

8

System Action:

The data is ignored.

System Programmer Response:

A likely cause is that an unknown host or LU is attempting to send data.

CSQX208E
csect-name Error receiving data, channel channel-name, connection conn-id (queue manager qmgr-name) TRPTYPE=trptype RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

The channel is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX209E
csect-name Connection unexpectedly terminated, channel channel-name, connection conn-id (queue manager qmgr-name) TRPTYPE=trptype
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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.

Severity:

8

System Action:

If a channel is involved, it is stopped. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Review the local and remote console logs for reports of network errors.

CSQX210E
csect-name Unable to complete bind, channel channel-name, connection conn-id TRPTYPE=LU62 RC=return-code reason=reason
Explanation:

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).

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX212E
csect-name Unable to allocate socket, channel channel-name, TRPTYPE=TCP RC=return-code reason=reason
Explanation:

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX213E
csect-name Communications error, channel channel-name, TRPTYPE=trptype function 'func' RC=return-code reason=reason
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

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

  • normally, the return code (in hexadecimal) from the communications system function

  • for an LU 6.2 listener, it may be the reason code (in hexadecimal) from APPC/MVS allocate services

  • if it is of the form 10009nnn or 20009nnn, it is a distributed queuing message code.

For some errors, there may also be an associated reason code reason (in hexadecimal) giving more information.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX215E
csect-name Communications network not available, TRPTYPE=trptype
Explanation:

An attempt was made to use the communications system, but it has not been started or has stopped. trptype shows the communications system used:

TCP

TCP/IP

LU62

APPC/MVS
Severity:

8

System Action:

The channel or listener is not started.

System Programmer Response:

Start the communications system, and try again.

CSQX218E
csect-name Listener not started - unable to bind, port port address ip-address, TRPTYPE=TCP INDISP=disposition, RC=return-code
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

8

System Action:

The listener is not started.

System Programmer Response:

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.

CSQX219E
csect-name Listener stopped - error creating new connection, TRPTYPE=TCP INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

8

System Action:

The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.

System Programmer Response:

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.

CSQX220E
csect-name Communications network not available, channel channel-name, TRPTYPE=trptype
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS
Severity:

8

System Action:

The channel or listener is not started.

System Programmer Response:

Start the communications system, and try again.

CSQX228E
csect-name Listener unable to start channel, channel channel-name, TRPTYPE=trptype INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.

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.

Severity:

8

System Action:

If a channel is involved, it is not started.

System Programmer Response:

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.

CSQX234I
csect-name Listener stopped, TRPTYPE=trptype INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

System Action:

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.

System Programmer Response:

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.

CSQX235E
csect-name Invalid local address local-addr, channel channel-name, TRPTYPE=trptype RC=return-code
Explanation:

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX239E
csect-name Unable to determine local host name, channel channel-name, TRPTYPE=TCP RC=return-code
Explanation:

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.

Severity:

8

System Action:

The channel or listener is not started.

System Programmer Response:

See Appendix D. Communications protocol return codes for information about the cause of the return code from TCP/IP.

CSQX250E
csect-name Listener ended abnormally, TRPTYPE=trptype INDISP=disposition, reason=sssuuu-reason
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX251I
csect-name Listener started, TRPTYPE=trptype INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

System Action:

Processing continues.

CSQX256E
csect-name Listener stopped - error selecting new connection, TRPTYPE=TCP INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

8

System Action:

The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.

System Programmer Response:

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.

CSQX257I
csect-name Listener unable to create new connection, TRPTYPE=TCP INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

4

System Action:

The listener continues to run, but the connection is not created.

System Programmer Response:

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.

CSQX258E
csect-name Listener stopped - error accepting new connection, TRPTYPE=TCP INDISP=disposition
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

8

System Action:

The listener stops. The channel initiator will attempt to restart it, at the intervals specified by the LSTRTMR queue manager attribute.

System Programmer Response:

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.

CSQX259E
csect-name Connection timed out, channel channel-name, connection conn-id (queue manager qmgr-name) TRPTYPE=trptype
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS

Probable causes are:

  • A communications failure.

  • For a message channel, if the Receive Timeout function is being used (as set by the RCVTIME, RCVTTYPE, and RCVTMIN queue manager attributes) and no response was received from the partner within this time.

  • For an MQI channel, if the Client Idle function is being used (as set by the DISCINT server-connection channel attribute) and the client application did not issue an MQI call within this time.

Severity:

8

System Action:

The channel stops.

System Programmer Response:

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.

CSQX260E
csect-name Client attachment feature unavailable, channel channel-name, connection conn-id
Explanation:

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 '????'.

Severity:

8

System Action:

The client is not attached, and the connection from the client application fails with MQRC_Q_MGR_NOT_AVAILABLE.

System Programmer Response:

Install the client attachment feature if support for clients is required.

CSQX261E
csect-name No suitable IP stack available, channel channel-name, connection conn-id
Explanation:

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX262E
csect-name Communications canceled, channel channel-name, TRPTYPE=trptype
Explanation:

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:

TCP

TCP/IP

LU62

APPC/MVS
Severity:

8

System Action:

The channel is stopped.

System Programmer Response:

Restart the channel if appropriate.

CSQX403I
csect-name Auto-definition of channel channel-name suppressed by exit exit-name
Explanation:

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.

Severity:

0

System Action:

The channel is not started.

CSQX404I
csect-name REFRESH CLUSTER REPOS(YES) command processed, cluster cluster-name, n objects changed
Explanation:

The repository manager successfully processed a REFRESH command with the REPOS(YES) option for the indicated cluster.

Severity:

0

System Action:

None.

CSQX405I
csect-name FORCEREMOVE QUEUES(YES) command processed, cluster cluster-name, target target
Explanation:

The repository manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager.

Severity:

0

System Action:

None.

CSQX406E
csect-name REFRESH CLUSTER REPOS(YES) command failed, cluster cluster-name, - qmgr-name is a full repository
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

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.

CSQX407I
csect-name Cluster queue q-name definitions inconsistent
Explanation:

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.

Severity:

4

System Action:

None.

System Programmer Response:

Alter the definitions of the queue on the various queue managers so that they have identical values for these attributes.

CSQX410I
csect-name Repository manager started
Explanation:

The repository manager started successfully.

Severity:

0

System Action:

None.

CSQX411I
csect-name Repository manager stopped
Explanation:

The repository manager stopped. This may be for one of three reasons:

  • The channel initiator is stopping.

  • The channel initiator is starting and the queues used by the repository manager have not been defined because clustering is not required.

  • An error has occurred.

Severity:

0

System Action:

Processing continues, but clustering is not available.

System Programmer Response:

If an error has occurred, investigate the problem reported in the preceding messages.

CSQX412E
csect-name Misdirected repository command, target target-id sender sender-id
Explanation:

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.

Severity:

8

System Action:

The command is ignored, and the error is reported to the sender.

System Programmer Response:

Check the channel and cluster definitions of the sending queue manager.

CSQX413E
csect-name Repository command format error, command code command
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX415E
csect-name Repository command state error, command code command cluster object object-name, sender sender-id
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX416E
csect-name Repository command processing error, RC=return-code, command code command cluster object object-name, sender sender-id
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX417I
csect-name Cluster-senders remain for removed queue manager qmgr-name
Explanation:

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.

Severity:

0

System Programmer Response:

Delete the manually-defined cluster-sender channels that refer to qmgr-name.

CSQX418I
csect-name Only one repository for cluster cluster-name
Explanation:

The repository manager has received information about a cluster for which it is the only full repository.

Severity:

0

System Action:

None.

System Programmer Response:

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.

CSQX419I
csect-name No cluster-receivers for cluster cluster-name
Explanation:

The repository manager has received information about a cluster for which no cluster-receiver channels are known.

Severity:

0

System Action:

None.

System Programmer Response:

Define cluster-receiver channels for the cluster on the local queue manager.

CSQX420I
csect-name No repositories for cluster cluster-name
Explanation:

The repository manager has received information about a cluster for which no full repositories are known.

Severity:

0

System Action:

None.

System Programmer Response:

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.

CSQX422E
csect-name Repository manager error, RC=return-code
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX425E
csect-name Repository command merge error, command code command cluster object object-name, sender sender-id
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX426E
csect-name Undeliverable repository command, channel channel-name, target target-id command code command
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Check the channel and cluster definitions of the sending and receiving queue managers.

CSQX427E
csect-name Cluster-sender not connected to repository, cluster cluster-name, channel channel-name, target target-id
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

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.

CSQX428E
csect-name Unexpected queue or query repository command, cluster cluster-name, channel channel-name, sender sender-id
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

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.

CSQX430E
csect-name Unexpected queue manager repository command, cluster cluster-name, channel channel-name, sender sender-id
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Check the definition of the channel on the sending queue manager to ensure that it is connected to a full repository for the cluster.

CSQX431I
csect-name Repository unavailable, cluster cluster-name, channel channel-name, sender sender-id
Explanation:

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.

Severity:

0

System Action:

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.

CSQX433E
csect-name Cluster-receiver and cluster-sender differ, cluster cluster-name, channel channel-name, sender sender-id
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Change the definition of the channel so that it is in the same clusters on both queue managers.

CSQX434E
csect-name Unrecognized message on name
Explanation:

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.

Severity:

8

System Action:

The message is put on the dead-letter queue.

System Programmer Response:

Examine the message on the dead-letter queue to determine the originator of the message.

CSQX435E
csect-name Unable to put repository manager message, target target-id MQCC=mqcc MQRC=mqrc
Explanation:

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.

Severity:

4

System Action:

Processing continues, but repository information may be out of date.

System Programmer Response:

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.

CSQX436E
csect-name Unable to put repository manager message, cluster cluster-name, MQCC=mqcc MQRC=mqrc
Explanation:

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.

Severity:

4

System Action:

Processing continues, but repository information may be out of date.

System Programmer Response:

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.

CSQX437E
csect-name Unable to commit repository changes
Explanation:

The repository manager tried to commit some updates to the repository but was unsuccessful.

Severity:

4

System Action:

Processing continues, but local repository information may be out of date.

System Programmer Response:

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.

CSQX438E
csect-name Unable to reallocate messages, channel channel-name, MQCC=mqcc MQRC=mqrc
Explanation:

The repository manager was unable to reallocate messages for the specified channel to another destination.

Severity:

8

System Action:

The messages remain on the transmission queue.

System Programmer Response:

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.

CSQX439E
csect-name Repository error for channel channel-name
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX440E
csect-name FORCEREMOVE command failed, cluster cluster-name, target target - repository is not on qmgr-name
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the correct values or on the correct queue manager.

CSQX441I
csect-name FORCEREMOVE command processed, cluster cluster-name, target target
Explanation:

The repository manager successfully processed a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager.

Severity:

0

System Action:

None.

CSQX442I
csect-name REFRESH CLUSTER command processed, cluster cluster-name, n objects changed
Explanation:

The repository manager successfully processed a REFRESH command for the indicated cluster.

Severity:

0

System Action:

None.

CSQX443I
csect-name SUSPEND QMGR command processed, cluster cluster-name, n objects changed
Explanation:

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.)

Severity:

0

System Action:

None.

CSQX444I
csect-name RESUME QMGR command processed, cluster cluster-name, n objects changed
Explanation:

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.)

Severity:

0

System Action:

None.

CSQX447E
csect-name Unable to backout repository changes
Explanation:

Following an error, the repository manager tried to backout some updates to the local repository but was unsuccessful.

Severity:

8

System Action:

The repository manager terminates.

System Programmer Response:

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.

CSQX448E
csect-name Repository manager stopping because of errors. Restart in n seconds
Explanation:

A severe error, as reported in the preceding messages, occurred during repository manager processing; the repository manager is unable to continue.

Severity:

8

System Action:

The repository manager terminates. The channel initiator will try to restart it after the specified interval.

System Programmer Response:

Correct the problem reported in the preceding messages.

CSQX449I
csect-name Repository manager restarted
Explanation:

The repository manager restarted successfully following an error.

Severity:

0

System Action:

None.

CSQX453E
csect-name FORCEREMOVE command failed, cluster cluster-name, target target is not unique
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name.

CSQX455E
csect-name FORCEREMOVE command failed, cluster cluster-name, target target not found
Explanation:

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.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command specifying the correct queue manager name or identifier.

CSQX456I
csect-name Full repository update not received, cluster cluster-name, queue q-name (queue manager qmgr-name)
Explanation:

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.

Severity:

0

System Action:

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.

System Programmer Response:

If the queue is still required, check that:

  • The cluster channels to and from the queue manager that is the full repository for the cluster, and between there and the queue manager where the queue is located, are able to run.

  • The repository managers on those queue managers have not ended abnormally.

CSQX457I
csect-name Repository available, cluster cluster-name, channel channel-name, sender sender-id
Explanation:

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.

Severity:

0

System Action:

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.

CSQX460E
csect-name Cluster cache is full
Explanation:

No more space is available in the cluster cache area.

Severity:

8

System Action:

The repository manager terminates. The channel initiator will try to restart it after the specified interval.

System Programmer Response:

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.

CSQX461I
csect-name Cluster cache entry corrected, cluster queue manager clusqmgr-name, channel channel-name, connection conn-id
Explanation:

At channel initiator restart, the repository manager found a corrupted entry in the cluster cache. The entry has been corrected.

Severity:

4

System Action:

Processing continues. The cluster channel to which the entry refers, channel-name using connection conn-id, will be available for use.

System Programmer Response:

None. We 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.

CSQX462E
csect-name Cluster cache entry is unusable, cluster queue manager clusqmgr-name, channel channel-name, connection conn-id
Explanation:

At channel initiator restart, the repository manager found a corrupted entry in the cluster cache which could not be corrected.

Severity:

8

System Action:

The corrupted entry is ignored. The cluster channel to which it refers, channel-name using connection conn-id, will not be usable.

System Programmer Response:

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. We 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.

CSQX463E
csect-name Error accessing cluster cache entry
Explanation:

There was an internal error when accessing a cluster cache entry.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX470E
csect-name Channel channel-name has the wrong disposition
Explanation:

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.

Severity:

8

System Action:

The requested action is not performed.

System Programmer Response:

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:

  • A sending channel is shared if its transmission queue is shared, and private if it is not.

  • A receiving channel is shared if it was started in response to an inbound transmission directed to the queue-sharing group, and private if it was started in response to an inbound transmission directed to the queue manager.

CSQX471I
csect-name nn shared channels to restart, nn requests issued
Explanation:

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.

Severity:

0

System Action:

The channel initiator shutdown processing continues.

System Programmer Response:

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.

CSQX473E
csect-name Listener unable to register to WLM/DNS, TRPTYPE=TCP INDISP=disposition host name=hhh server name=sss, RC=return-code reason=reason
Explanation:

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).

Severity:

8

System Action:

The listener is not started.

System Programmer Response:

See z/OS MVS Workload Management Services for more information about the return and reason codes from the IWMSRSRG service.

CSQX474E
csect-name Listener unable to unregister from WLM/DNS, TRPTYPE=TCP INDISP=disposition host name=hhh server name=sss, RC=return-code reason=reason
Explanation:

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).

Severity:

8

System Action:

The listener stops. It may not be possible to restart it.

System Programmer Response:

See z/OS MVS Workload Management Services for more information about the return and reason codes from the IWMSRDRS service.

CSQX475I
csect-name Channel channel-name adopted
Explanation:

The specified channel, which was orphaned because of a communications error, has been adopted by a new instance of the channel.

Severity:

0

System Action:

Processing continues.

CSQX476E
csect-name Channel channel-name is active on qmgr-name, shared status entry found
Explanation:

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.

Severity:

8

System Action:

The request fails.

System Programmer Response:

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.

CSQX477E
csect-name Channel channel-name is active, transmission queue queue-name in use on qmgr-name
Explanation:

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.

Severity:

8

System Action:

The request fails.

System Programmer Response:

Do the following, as appropriate:

  • Check if the channel is already running

  • Check if another channel is using the queue by using the DISPLAY QSTATUS command

  • Ensure the queue name is specified correctly in the channel definition

  • Alter the queue usage attribute of the queue to that of a transmission queue.

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.

CSQX478E
csect-name Channel channel-name is active on qmgr-name, connection tag in use
Explanation:

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.

Severity:

8

System Action:

The request fails.

System Programmer Response:

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.

CSQX479E
csect-name Channel channel-name is active on qmgr-name, shared channel adoption failed
Explanation:

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.

Severity:

8

System Action:

The request fails, and the orphaned channel may remain active.

System Programmer Response:

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.

CSQX482E
csect-name Shared channel function not available
Explanation:

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.

Severity:

8

System Action:

The channel command fails or the channel stops.

System Programmer Response:

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.

CSQX483E
csect-name DB2 not available
Explanation:

Because DB2 is not available, or is no longer available, the channel initiator cannot do processing for a shared channel.

Severity:

8

System Action:

The channel command fails or the channel stops.

System Programmer Response:

Use the preceding messages on the z/OS console to investigate why DB2 is not available, and restart it if necessary.

CSQX484E
csect-name Error accessing DB2
Explanation:

Because there was an error in accessing DB2, the channel initiator cannot do processing for a shared channel.

Severity:

8

System Action:

The channel command fails or the channel stops.

System Programmer Response:

Resolve the error reported in the preceding messages.

CSQX485E
csect-name Shared channel status error
Explanation:

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.

Severity:

8

System Action:

The channel command fails or the channel stops.

System Programmer Response:

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.

CSQX486E
csect-name Shared channel channel-name definitions inconsistent
Explanation:

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.

Severity:

8

System Action:

The request fails.

System Programmer Response:

Change the definitions of the channel so that they are the same on all the queue managers. If the channel type needs changing, delete and then redefine the channel.

CSQX496I
csect-name Channel channel-name stopping because of request by remote exit
Explanation:

The channel is closing because the user channel exit at the remote end requested it.

Severity:

0

System Action:

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.

System Programmer Response:

Note that this puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.

CSQX498E
csect-name Invalid MQCD field field-name, value=nnn (xxx)
Explanation:

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.

Severity:

8

System Action:

The channel is not defined.

System Programmer Response:

Correct the channel auto-definition exit.

CSQX500I
csect-name Channel channel-name started
Explanation:

The specified channel has been started.

Severity:

0

System Action:

Processing continues.

CSQX501I
csect-name Channel channel-name is no longer active
Explanation:

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.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

If the channel is stopped, resolve any error, and issue a START CHANNEL command to restart the channel.

CSQX502E
csect-name Action not allowed for channel channel-name
Explanation:

The action you requested cannot be performed on channel channel-name. Some actions are only valid for certain channel types; for example, we can only ping a sender or server channel.

Severity:

8

System Action:

The requested action is not performed.

System Programmer Response:

Check whether the channel name is specified correctly. If it is, check that:

CSQX503E
csect-name Negotiation failed for channel channel-name
Explanation:

Channel channel-name could not be established due to a negotiation failure between the local queue manager and the remote end.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

Examine the console log for the remote end for messages explaining the cause of the negotiation failure.

CSQX504E
csect-name Local protocol error, channel channel-name, type=type data=xxx
Explanation:

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:

0000000A

Incorrect segment type

00000012

Incorrect message length

00000013

Incorrect segment number

The incorrect value is shown by xxx.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX505E
csect-name Sequence wrap values differ, channel channel-name, local=local-seqno remote=remote-seqno
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Change either the local or remote channel definition so that the values specified for the message sequence number wrap value are the same.

CSQX506E
csect-name Message receipt confirmation not received for channel channel-name
Explanation:

The remote end did not accept the last batch of messages.

Severity:

8

System Action:

Channel channel-name stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Determine why the remote end did not accept the last batch of messages. Resolve the problem and restart the channel.

CSQX507E
csect-name Channel channel-name is in-doubt, connection conn-id (queue manager qmgr-name)
Explanation:

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 '????'.

Severity:

8

System Action:

The requested operation does not complete.

System Programmer Response:

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.

CSQX513E
csect-name Channel channel-name exceeded current channel limit
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase MAXCHL.

CSQX514E
csect-name Channel channel-name is active on qmgr-name
Explanation:

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.

Severity:

8

System Action:

The request fails.

System Programmer Response:

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.

CSQX515I
csect-name Channel channel-name changed
Explanation:

The channel for which information has been requested is a new instance of the channel. The previous channel instance has ended.

Severity:

0

System Action:

The information shown is for the new channel instance.

CSQX516E
csect-name Error accessing synchronization data, RC=return-code
Explanation:

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.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX517E
csect-name Error in q-name - channel channel-name repeated
Explanation:

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.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX519E
csect-name Channel channel-name not defined
Explanation:

The channel initiator could not find a definition of channel channel-name.

Severity:

8

System Action:

The requested operation fails.

System Programmer Response:

Check that the name is specified correctly and the channel definition is available.

CSQX520E
csect-name Remote channel channel-name not defined
Explanation:

There is no definition of channel channel-name at the remote end.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Add an appropriate channel definition at the remote end, and retry the operation.

CSQX523E
csect-name Remote protocol error, channel channel-name, type=type data=xxx
Explanation:

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:

0000000A

Incorrect segment type

0000000B

Incorrect length

0000000C

Invalid data

0000000D

Invalid segment

0000000E

Invalid ID

0000000F

Invalid MSH

00000010

General error

00000011

Batch failure

00000012

Incorrect message length

00000013

Incorrect segment number

The data associated with the error (for example, the incorrect value) is shown by xxx.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX524E
csect-name Remote queue manager unavailable for channel channel-name
Explanation:

Channel channel-name cannot start because the remote queue manager is not currently available.

Severity:

8

System Action:

The channel does not start

System Programmer Response:

Either start the remote queue manager, or retry the operation later.

CSQX525E
csect-name Channel channel-name closing because remote queue manager qmgr-name is stopping
Explanation:

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 '????'.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Investigate why the remote queue manager is stopping, if it was not expected.

CSQX526E
csect-name Message sequence error for channel channel-name, sent=msg-seqno expected=exp-seqno
Explanation:

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.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.)

CSQX527E
csect-nameUnable to send message for channel channel-name
Explanation:

The remote end cannot receive the message that is being sent for channel channel-name.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Examine the console log for the remote end to determine why the message cannot be received, and then restart the channel.

CSQX528I
csect-name Channel channel-name stopping
Explanation:

The channel is closing because a STOP CHANNEL command was issued, or because the channel initiator is stopping.

Severity:

0

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Note that a STOP CHANNEL command puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.

CSQX531E
csect-name Queue q-name for channel channel-name is in use or wrong type
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Do the following, as appropriate:

  • Check if the channel is already running

  • Check if another channel is using the queue; use the DISPLAY QSTATUS command

  • Ensure the queue name is specified correctly in the channel definition

  • Alter the queue usage attribute of the queue to that of a transmission queue.

CSQX533I
csect-name Channel channel-name is already in requested state
Explanation:

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.

Severity:

0

System Action:

The request is ignored.

CSQX534E
csect-name Channel channel-name is stopped
Explanation:

The operation requested cannot be performed because the channel is currently stopped.

Severity:

4

System Action:

The request is ignored.

System Programmer Response:

Issue a START CHANNEL command to restart the channel.

CSQX535E
csect-name Channel channel-name stopping because exit exit-name is not valid
Explanation:

The user exit exit-name specified for channel channel-name is not valid.

Severity:

8

System Action:

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.

System Programmer Response:

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.

CSQX536I
csect-name Channel channel-name stopping because of request by exit exit-name
Explanation:

The channel is closing because the user channel exit exit-name requested it.

Severity:

0

System Action:

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.

System Programmer Response:

Note that this puts the channel into STOPPED state. A START CHANNEL command must be issued to restart it.

CSQX539E
csect-name Channel channel-name for queue q-name is not available
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Ensure that there is a channel defined to process the transmission queue, and that it is not stopped.

CSQX540E
csect-name Unable to commit batch, channel channel-name, MQCC=mqcc MQRC=mqrc
Explanation:

An MQCMIT call for the queue associated with channel channel-name was unsuccessful.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc.

CSQX541E
csect-name Invalid CCSIDs for data conversion, ccsid1 and ccsid2
Explanation:

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.)

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX544E
csect-name Messages for channel channel-name sent to remote dead-letter queue
Explanation:

During the processing of channel channel-name, one or more messages have been put the dead-letter queue at the remote queue manager.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

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.

CSQX545I
csect-name Channel channel-name closing because disconnect interval expired
Explanation:

The channel is closing because no messages arrived on the transmission queue within the disconnect interval.

Severity:

0

System Action:

The channel ends normally.

CSQX547E
csect-name Remote channel channel-name has the wrong type
Explanation:

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.

Severity:

8

System Action:

The requested operation is not performed.

System Programmer Response:

Check that the channel name is specified correctly. If it is, check that:

  • The channel definition on the remote end has an appropriate channel type

  • The connection name of the local channel identifies the remote end correctly

  • For cluster channels, the connection names do not specify a generic address

  • For TCP/IP connections, the port number specified by the local channel matches that used by the listener at the remote queue manager.

CSQX548E
csect-name Messages sent to local dead-letter queue, channel channel-name, reason=reason
Explanation:

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:

  • an MQRC_* reason code from an MQPUT or MQPUT1 call

  • an MQFB_* feedback code.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

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.

CSQX549E
csect-name Queue q-name for channel channel-name is get-inhibited
Explanation:

An MQGET failed because the transmission queue had been previously inhibited for gets.

Severity:

8

System Action:

The channel stops. The associated transmission queue may have triggering turned off.

System Programmer Response:

Change the definition of the transmission queue so that it is not inhibited for MQGET calls.

CSQX551E
csect-name Action not supported, channel channel-name, connection conn-id (queue manager qmgr-name)
Explanation:

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 '????'.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Check that the connection name parameter is specified correctly and that the levels of the queue managers in use are compatible.

CSQX552E
csect-name Security exit data for channel channel-name not received
Explanation:

The local security user channel exit for channel channel-name requested data from the remote security user channel exit, but no data was received.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

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.

CSQX558E
csect-name Remote channel channel-name not available
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX565E
csect-name No dead-letter queue for qmgr-name, channel channel-name
Explanation:

A message could not be delivered normally and there is no dead-letter queue defined for queue manager qmgr-name.

Severity:

8

System Action:

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.

System Programmer Response:

Correct the problem that prevented the message from being delivered normally, or define a dead-letter queue for the remote queue manager.

CSQX567E
csect-name Listener unable to register to APPC/MVS, TRPTYPE=LU62 INDISP=disposition RC=return-code reason=reason
Explanation:

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).

Severity:

8

System Action:

The listener is not started.

System Programmer Response:

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.

CSQX568E
csect-name Listener unable to unregister from APPC/MVS, TRPTYPE=LU62 INDISP=disposition RC=return-code reason=reason
Explanation:

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).

Severity:

8

System Action:

The listener stops. It may not be possible to restart it.

System Programmer Response:

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.

CSQX569E
csect-name Channel channel-name exceeded TCP/IP channel limit
Explanation:

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).

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX570E
csect-name Channel channel-name exceeded LU 6.2 channel limit
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX572E
csect-name Channel channel-name stopping because message header is not valid
Explanation:

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.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Correct the problem that caused the invalid message header.

CSQX573E
csect-name Channel channel-name exceeded active channel limit
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX574I
csect-name Channel channel-name can now start
Explanation:

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.

Note:
This message is not itself issued, although the corresponding event is generated.
Severity:

0

CSQX575E
csect-name Negotiation failed for channel
Explanation:

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.

Severity:

8

System Action:

The channel is not started.

System Programmer Response:

Examine the console log for the remote end for messages explaining the cause of the negotiation failure.

CSQX578E
csect-name Unable to save status for channel channel-name
Explanation:

An internal error has occurred.

Severity:

8

System Action:

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.

System Programmer Response:

Collect the items listed in the Problem Determination section and contact your IBM support center.

Problem Determination:

Collect the following diagnostic items:

CSQX599E
csect-name Channel channel-name ended abnormally
Explanation:

Channel channel-name ended abnormally because of a severe problem, as reported in the preceding messages.

Severity:

8

System Action:

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

System Programmer Response:

Investigate the problem reported in the preceding messages.

CSQX608E
csect-name Remote resources in recovery for channel channel-name
Explanation:

Channel channel-name cannot start because resources at the remote queue manager are being recovered.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX609E
csect-name Resources in recovery, channel channel-name, MQCC=mqcc MQRC=mqrc
Explanation:

The message channel agent for the channel could not connect to the queue manager because resources are being recovered.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqcc and mqrc, which come from an MQCONNX request.

CSQX613I
csect-name Channel channel-name instance is already in requested state
Explanation:

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.

Severity:

0

System Action:

The request is ignored.

CSQX617I
csect-name SSL key repository refresh not processed, SSL communications unavailable
Explanation:

The cached SSL key repository cannot be refreshed in response to a REFRESH SECURITY TYPE(SSL) command because SSL communications are currently unavailble.

Severity:

0

System Action:

0

System Programmer Response:

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.

CSQX618I
csect-name SSL key repository refresh started
Explanation:

The cached SSL key repository is being refreshed in response to a REFRESH SECURITY TYPE(SSL) command.

Severity:

0

System Action:

Message CSQX619I will be issued when the refresh is complete.

CSQX619I
csect-name SSL key repository refresh processed
Explanation:

The refresh of the cached SSL key repository is complete.

Severity:

0

System Action:

Channels will be restarted as required.

CSQX620E
csect-name System SSL error, channel channel-name, function 'func' RC=return-code
Explanation:

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).

Severity:

8

System Action:

The channel is stopped.

System Programmer Response:

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.

CSQX625E
csect-name System SSL error, function 'func' RC=return-code
Explanation:

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).

Severity:

8

System Action:

The SSL server subtask terminates.

System Programmer Response:

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.

CSQX630E
csect-name Channel channel-name requires SSL
Explanation:

Channel channel-name cannot start because it requires SSL, but SSL communications are not currently available.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

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.

CSQX631E
csect-name Cipher specifications differ, channel channel-name, local=local-ciph remote=remote-ciph
Explanation:

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.

Severity:

8

System Action:

The channel does not start.

System Programmer Response:

Change either the local or remote channel definition so that the values specified for the SSL cipher specification are the same.

CSQX632I
csect-name SSL certificate has no associated user ID, remote channel channel-name - channel initiator user ID used
Explanation:

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.

Severity:

0

System Action:

The user ID of the channel initiator address space is used as the channel user ID for the channel.

System Programmer Response:

If certificate name filtering is being used, we 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.

CSQX633E
csect-name SSL certificate for remote channel channel-name failed local check
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

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.

CSQX634E
csect-name SSL certificate failed remote check, channel channel-name, connection conn-id
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

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.

CSQX635E
csect-name Invalid cipher specification ciph for channel channel-name
Explanation:

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:

01

NULL_MD5

02

NULL_SHA

03

RC4_MD5_EXPORT

04

RC4_MD5_US

05

RC4_SHA_US

06

RC2_MD5_EXPORT

09

DES_SHA_EXPORT

0A

TRIPLE_DES_SHA_US

2F

TLS_RSA_WITH_AES_128_CBC_SHA

35

TLS_RSA_WITH_AES_256_CBC_SHA

In some cases the channel name cannot be determined and so is shown as '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Correct the SSL cipher specification for the channel.

CSQX636E
csect-name Distinguished name does not match peer name, channel channel-name, name='dist-name'
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

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.

CSQX637E
csect-name No SSL certificate for remote channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

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.

CSQX638E
csect-name SSL communications error for channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Investigate the problem reported in the preceding messages. Review the local and remote console logs for reports of network errors.

CSQX639E
csect-name No cipher specification for remote channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Change the remote channel definition so that the value specified for the SSL cipher specification is the same as that of the local channel.

CSQX640E
csect-name Invalid peer name, channel channel-name, attribute=key-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Correct the SSL peer name for the channel.

CSQX641E
csect-name Cipher specification error for remote channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Review the remote console log to determine the cipher specification error.

CSQX642E
csect-name No SSL certificate for channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

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.

CSQX643E
csect-name Peer name error for remote channel channel-name
Explanation:

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 '????'.

Severity:

8

System Action:

The channel will not start.

System Programmer Response:

Review the remote console log to determine the peer name error.

CSQX644E
csect-name Unable to determine peer name for remote channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

If the local channel has a peer name specified it does not start.

System Programmer Response:

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.

CSQX645E
csect-name SSL certificate missing for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel will not start.

System Programmer Response:

Ensure that there is an SSL certificate 'ibmWebSphereMQqmgr-name' or a default certificate in the key ring and that it is valid.

CSQX646E
csect-name Error accessing LDAP server for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel will not start.

System Programmer Response:

Ensure that the LDAP server is specified and set up correctly, and is running.

CSQX658E
csect-name SSL certificate has expired, channel channel-name, connection conn-id
Explanation:

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.

Severity:

4

System Action:

The channel will not start.

System Programmer Response:

Obtain a new certificate if the certifiacte has expired, or wait until the certificate becomes valid if it is not valid yet.

CSQX663E
csect-name SSL certificate signature is incorrect, channel channel-name, connection conn-id
Explanation:

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 '????'.

Severity:

4

System Action:

The channel will not start.

System Programmer Response:

Ensure that the SSL certificate connected to the key repository at the remote end is valid.

CSQX665E
csect-name Channel channel-name stopping because remote SSL socket closed
Explanation:

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 '????'.

Severity:

4

System Action:

The channel stops.

System Programmer Response:

Examine the console log for the remote end to determine the cause of the failure.

CSQX666E
csect-name LDAP server unavailable for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel does not start.

System Programmer Response:

Ensure that the LDAP server is running.

CSQX675E
csect-name Unable to complete SSL key repository refresh
Explanation:

The refresh of the cached SSL key repository could not be completed because of errors.

Severity:

4

System Action:

The refresh is incomplete.

System Programmer Response:

Examine the console log for messages that may indicate why the refresh could not be started.

CSQX676E
csect-name SSL key repository refresh completed, but some channels not restarted
Explanation:

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.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Examine the console log for messages identifying the channels that did not restart.

CSQX677E
csect-name SSL key repository refresh terminated, waiting for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The refresh is terminated. Some channels using SSL will have been stopped.

System Programmer Response:

Stop any SSL channels that have not already stopped and issue the REFRESH SECURITY TYPE(SSL) command again.

CSQX678E
csect-name Channel channel-name not started, refreshing SSL key repository
Explanation:

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 '????'.

Severity:

4

System Action:

The channel does not start.

System Programmer Response:

Wait until the refresh has completed and start the channel again.

CSQX679E
csect-name Channel channel-name not started, refreshing remote SSL key repository
Explanation:

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 '????'.

Severity:

4

System Action:

The channel does not start.

System Programmer Response:

Wait until the refresh has completed and start the channel again.

CSQX683E
csect-name SSL key repository has no certificates
Explanation:

The SSL key repository (that is, the key ring in the external security manager) does not contain any valid certificates.

Severity:

4

System Action:

Channels using SSL communications will not start.

System Programmer Response:

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.

CSQX684E
csect-name SSL key repository has no CA certificates
Explanation:

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.

Severity:

4

System Action:

Channels using SSL communications will not start.

System Programmer Response:

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.

CSQX685E
csect-name No self-signed certificate for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel is not started.

System Programmer Response:

Add the self-signed certificate to the key repository.

CSQX686E
csect-name SSL private key error for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel is not started.

System Programmer Response:

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.

CSQX687E
csect-name SSL certificate revoked by CA for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel is not started.

System Programmer Response:

Obtain a new certificate and add it to the key repository.

CSQX688E
csect-name No SSL CA certificate for channel channel-name
Explanation:

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 '????'.

Severity:

4

System Action:

The channel is not started.

System Programmer Response:

Obtain a certificate for the certification authority (CA) and add it to the key repository.

CSQX689E
csect-name CRL cannot be processed for channelchannel-name
Explanation:

A Certificate Revocation List (CRL) is not valid and cannot be processed.

Severity:

4

System Action:

The channel is not started.

System Programmer Response:

Contact the certification authority and obtain a replacement CRL.

CSQX830I
csect-name Channel initiator active
Explanation:

This is issued in response to the DISPLAY CHINIT command if the channel initiator is active.

Severity:

0

CSQX831I
csect-name nn adapter subtasks started, nn requested
Explanation:

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.

Severity:

0

CSQX832I
csect-name nn dispatchers started, nn requested
Explanation:

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.

Severity:

0

CSQX833I
csect-name nn SSL server subtasks started, nn requested
Explanation:

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.

Severity:

0

CSQX836I
csect-name nn Maximum channels - TCP/IP nn, LU 6.2 nn
Explanation:

This is issued in response to the DISPLAY CHINIT command. It shows the maximum numbers of each type of channel that are allowed.

Severity:

0

CSQX840I
csect-name nn channels current, maximum nn
Explanation:

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.

Severity:

0

CSQX841I
csect-name nn channels active, maximum nn, including nn paused
Explanation:

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.

Severity:

0

CSQX842I
csect-name nn channels starting, nn stopped, nn retrying
Explanation:

This is issued in response to the DISPLAY CHINIT command. Of the channels that are current, it show how many are:

  • waiting to become active, because the limit for active channels has been reached

  • stopped, requiring manual intervention

  • attempting to reconnect following a temporary error.

Severity:

0

CSQX843I
csect-name TCP/IP listener INDISP=disposition retrying, for port port address ip-address
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

CSQX844I
csect-name LU 6.2 listener INDISP=disposition retrying, for LU name name
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

CSQX845I
csect-name TCP/IP system name is name
Explanation:

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.

Severity:

0

CSQX846I
csect-name TCP/IP listener INDISP=disposition started, for port port address ip-address
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

CSQX847I
csect-name LU 6.2 listener INDISP=disposition started, for LU name name
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

CSQX848I
csect-name TCP/IP listener INDISP=disposition not started
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

System Programmer Response:

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.

CSQX849I
csect-name LU 6.2 listener INDISP=disposition not started
Explanation:

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:

QMGR

those directed to the target queue manager

GROUP

those directed to the queue-sharing group.
Severity:

0

System Programmer Response:

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.