Distributed queuing messages (CSQX...)

IBM® WebSphere® MQ for z/OS® Vn

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

csect-name Channel initiator starting

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

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

csect-name Queue-sharing group is qsg-name

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.

Processing continues.

csect-name Obsolete parameter module ignored

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.

Processing continues.

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

Displays the amount of virtual storage currently used and available in the extended private region. Both values are displayed in megabytes (1048576 bytes), and are approximations.

This message is logged at channel initiator start and then either every hour if the usage does not change or when the memory usage changes (up or down) by more than 2%.

The amount of currently used extended private region storage is also given in the qcctstus field in the SMF 115, subtype 231, record.

Processing continues.

No action is required at this time. However, a frequent occurrence of this message might be an indication that the system is operating beyond the optimum region for the current configuration.

csect-name Channel initiator failed to start

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

The channel initiator started task terminates.

Investigate the problem reported in the preceding messages.

csect-name Channel initiator failed while stopping

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

The channel initiator started task terminates.

Investigate the problem reported in the preceding messages.

csect-name Unable to connect to queue manager qmgr-name, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

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

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

If you are unable to solve the problem, contact your IBM support center.

csect-name Unable to disconnect from queue manager qmgr-name, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

Processing continues.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

If you are unable to solve the problem, contact your IBM support center.

csect-name Channel initiator stopping

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

The channel initiator terminates.

Investigate the problem reported in the preceding messages.

csect-name Channel initiator stopped

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

None.

csect-name Client attachment available

Clients can be attached to and MQI channels can be used with the channel initiator.

The channel initiator startup processing continues.

csect-name Unable to open ddname data set

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

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

Investigate the problem reported in the preceding messages.

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

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.

None.

Reissue the command correctly if necessary.

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

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.

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

The channel or listener does not start.

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

csect-name started dispatchers started, failed failed

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

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

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

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

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

None.

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

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.

None.

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

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.

None.

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

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.

None.

csect-name Shared channel recovery completed

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.

Processing continues.

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

csect-name Shared channel recovery error

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

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

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

csect-name Channel initiator initialization complete

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 might still be in progress; its completion is shown by message CSQU012I.

None.

csect-name Listener started, port port address ip-address TRPTYPE=trptype INDISP=disposition

A listener has been started specifying TRPTYPE(trptype) and INDISP(disposition). This could either be because a START LISTENER command was issued, or because the listener was retrying. That listener is now active for the requested port and IP address. If ip-address is *, all IP addresses were requested.

None.

csect-name Listener stopped, port port address ip-address TRPTYPE=trptype INDISP=disposition

A STOP LISTENER command was issued specifying TRPTYPE(trptype) and INDISP(disposition), or IBM MQ has tried to stop a listener because of a failure. That listener is no longer active for the requested port and IP address. If ip-address is *, all IP addresses were requested.

None.

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

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.

Formatting terminates.

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

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

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

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.

Go to the appropriate volume of the z/OS MVS™ Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.

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

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

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.

Go to the appropriate volume of the z/OS MVS Programming: Assembler Services Reference manual for information about the return code from the STORAGE request.

csect-name Queue manager qmgr-name stopping, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The channel initiator terminates.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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

Processing continues.

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

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

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

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

The most likely cause is erroneous definition of the CSQINPX and CSQOUTX data sets. For information about the initialization command handler and these data sets, see Initialization commands. If you are unable to solve the problem, contact your IBM support center.

csect-name Initialization command handler terminated

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.

The initialization command handler ends.

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

For information about the initialization command handler, see Initialization commands.

csect-name Channel initiator stopping because of errors

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

The channel initiator terminates.

Investigate the problem reported in the preceding messages.

csect-name Channel initiator stopping because queue manager is stopping

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

The channel initiator terminates.

csect-name Connection to queue manager qmgr-name stopping or broken, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The channel initiator terminates.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to open object-type(name), MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQOPEN call for name was unsuccessful; object-type indicates whether name is a queue name, queue manager name, namelist name, channel name, topic name, or authentication information name. (The channel initiator can access channel definitions and authentication information as objects using the MQ API.)

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

The most common cause of the problem will be that the channel and queue definitions are incorrect.

csect-name Unable to get message from name, MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQGET call for queue name was unsuccessful.

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to put message to name, MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQPUT call for queue name was unsuccessful.

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to close name, MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQCLOSE call for name was unsuccessful; name can 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 IBM MQ API.)

Processing continues.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to inquire attributes for name, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, repository manager, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to set attributes for name, MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQSET call for queue name was unsuccessful.

The component where the error occurred (message channel agent, dispatcher, adapter subtask, SSL server subtask, listener, or supervisor) terminates. In the case of a message channel agent, the associated channel will be stopped.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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

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.

The channel initiator does not start.

Go to the appropriate volume of the z/OS MVS Programming: Assembler Services Reference manual for information about the return code from the CTRACE request.

If you are unable to solve the problem, contact your IBM support center.

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

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.

Channel initiator termination processing continues.

Go to the appropriate volume of the z/OS MVS Programming: Assembler Services Reference manual for information about the return code from the CTRACE request.

If you are unable to solve the problem, contact your IBM support center.

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

The channel initiator does not start.

See the MVS Authorized Assembler Services Reference manual for information about the return codes from the z/OS services. If you are unable to solve the problem, contact your IBM support center.

The channel initiator was unable to load a required module. ssss is the completion code and rrrr is the reason code (both in hexadecimal) from the z/OS LOAD service.

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

Check the console for messages indicating why the module was not loaded. See the MVS Programming: Assembler Services Reference manual for information about the codes from the LOAD request.

Ensure that the module is in the required library, and that it is referenced correctly. The channel initiator attempts to load this module from the library data sets under the STEPLIB DD statement of its started task JCL procedure xxxxCHIN.

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

The channel initiator does not start.

Check the console for messages indicating that a module was not loaded. Ensure that the module is in the required library, and that it is referenced correctly. The channel initiator attempts to load this module from the library data sets under the STEPLIB DD statement of its started task JCL procedure xxxxCHIN.

If you are unable to solve the problem, contact your IBM support center.

csect-name Unable to commit messages for name, MQCC=mqcc MQRC=mqrc (mqrc-text)

An MQCMIT call involving messages for queue name was unsuccessful.

The component where the error occurred (supervisor) terminates.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

csect-name Unable to convert message for name, MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The message is put without conversion, and processing continues.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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

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.

The channel initiator does not start.

Check the console for messages indicating why the module was not loaded.

Go to the appropriate volume of the z/OS MVS Programming: 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.

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

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.

The channel initiator does not start.

Go to the appropriate volume of the z/OS MVS Programming: 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.

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

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.

The channel initiator does not start.

Go to the appropriate volume of the z/OS MVS Programming: 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.

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

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

The channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

csect-name Error information recorded in CSQSNAP data set

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.

Processing continues.

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

csect-name Repository manager ended abnormally, reason=sssuuu-reason

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

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

User completion codes are generally the result of errors detected by the Language Environment®; see the Language Environment for z/OS Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center to report the problem.

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

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

The channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

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

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.

The component where the error occurred (message channel agent or SSL server subtask) terminates. In the case of a message channel agent, the associated channel will be stopped.

See the Language Environment for z/OS & VM Programming Guide for information about the return code from the CEEPIPI call. If you are unable to solve the problem, contact your IBM support center.

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

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

The channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

csect-name Pause service service-name failed, RC=return-code

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

The component where the error occurred (message channel agent, repository manager, cluster cache extension task,) usually terminates; in many cases, the end result will be that the channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the request. If you are unable to solve the problem, contact your IBM support center.

csect-name Unable to increase cluster cache

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

The channel initiator terminates.

Investigate the problem reported in any preceding messages.

csect-name Queued Pub/Sub task attach failed, RC=reason-code

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

The channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

csect-name Distributed Pub/Sub Offloader task attach failed, RC=return-code

The Distributed Pub/Sub Offloader task could not be attached. Return-code is the return code (in hexadecimal) from the z/OS ATTACH service.

The channel initiator terminates.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve this problem, contact your IBM support center.

csect-name Distributed Pub/Sub tasks have insufficient command authority

The PSMODE queue manager attribute has a value other than DISABLED but the channel initiator has insufficient authority to issue the DISPLAY PUBSUB command. Until such authority is granted, distributed publish/subscribe is unavailable.

The channel initiator attempts to restart the distributed Pub/Sub tasks at 1 minute intervals. This message is issued on each subsequent attempt until the required authority has been granted or publish/subscribe is disabled.

Grant the channel initiator the required authority to access the command server queues and issue the DISPLAY PUBSUB command. For the required security definitions, see Security considerations for the channel initiator on z/OS. Alternatively, if no publish subscribe operation is required, setting the PSMODE queue manager attribute to DISABLED prevents this message from being issued.

csect-name Distributed Pub/Sub Offloader started

The Distributed Pub/Sub Offloader task has started successfully.

None

csect-name Distributed Pub/Sub Offloader stopped

Processing continues, but distributed pub/sub is not available.

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

csect-name Unexpected error in distributed pub/sub Offloader

The Distributed Pub/Sub command Offloader encountered an unexpected error

Distributed publish/subscribe might no longer be available.

Investigate the problem reported in the preceding messages. If there are none or this does not resolve the problem contact IBM support.

csect-name Refresh proxy subscriptions failed

A REFRESH QMGR TYPE(PROXYSUB) was issued, but could not complete. This could be because the Channel Initiator is shutting down, or as a result of an error.

Processing continues, but remote subscriptions are not resynchronized.

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

csect-name Error removing non durable remote subscriptions

The Pub/Sub Offloader task is ending but was unable to remove one or more remote proxy subscriptions. If no previous error has occurred, this is likely to have been triggered by Queue Manager shut down.

Processing continues, but remote subscriptions might continue to exist which are no longer valid. This could cause a build-up of publications for this Queue Manager on remote transmission queues.

If the Queue Manager is to be restarted immediately, these subscriptions will be cleaned up when initial resynchronization with the cluster occurs. If this is not the case, proxy subscriptions might need to be manually removed using DELETE SUB on other Queue Managers in the cluster. Investigate the problem reported in the preceding messages to see why resynchronization failed.

Displays the amount of virtual storage that has been freed by the channel initiator transmission buffer scavenger task. This virtual storage value is displayed in megabytes (1048576 bytes), and is an approximation.

This message is logged when the amount of virtual storage used by the channel initiator is more than 75%. If storage has been freed the CSQX004I message is issued.

Processing continues.

No action is required at this time. However, a frequent occurrence of this message might indicate the system is operating beyond the optimum region for the current configuration.

csect-name CHINIT parameters ...

The channel initiator is being started with the parameter values shown in the following messages: CSQX071I, CSQX072I, CSQX073I, CSQX074I, CSQX075I, CSQX076I, CSQX078I, CSQX079I, CSQX080I, CSQX081I, CSQX082I, CSQX085I, CSQX090I, CSQX091I, CSQX092I, CSQX094I, CSQX099I.

The channel initiator startup processing continues.

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

csect-name WLM/DNS is no longer supported

The QMGR attribute DNSWLM is set to YES. This feature is no longer supported by z/OS Communications Server.

Processing continues, but registration to the WLM/DNS server will not be attempted.

csect-name Dispatcher failed to start, TCB=tcb-name

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

The channel initiator will attempt to restart the dispatcher. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately.

Investigate the problem reported in the preceding messages.

csect-name Dispatcher unable to schedule essential process process

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

The dispatcher does not start.

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

csect-name Dispatcher linkage stack error, TCB=tcb-name

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

The dispatcher ends abnormally with completion code X'5C6' and reason code X'00E7010E', and a dump is issued. The channel initiator will attempt to restart it.

The most likely cause is incorrect use of the linkage stack by a user channel exit; exits must issue any MQ API calls and return to the caller at the same linkage stack level as they were entered. If exits are not being used, or if they do not use the linkage stack, contact your IBM support center to report the problem.

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

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

The dispatcher ends abnormally with completion code X'5C6' and reason code X'00E7010F', and a dump is issued. The channel initiator will attempt to restart it.

Contact your IBM support center to report the problem.

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

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.

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

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ESTAE request. If you are unable to solve the problem, contact your IBM support center.

csect-name Unable to connect to TCP/IP using USS, service 'serv' RC=return-code reason=reason

Use of TCP/IP with the UNIX System Services (USS) sockets interface was requested, but an error occurred. return-code and reason are the return and reason codes (both in hexadecimal) from the USS service serv that gave the error.

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

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

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

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

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

User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS 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.

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

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

The process ends abnormally, and a dump is normally issued. The channel is stopped, and must be restarted manually. For auto-defined channels, the channel does not start.

User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS 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.

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

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

The process ends abnormally, and a dump is normally issued. If the process is a message channel agent, the channel is stopped, and will need to be restarted manually.

User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS 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.

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

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

The dispatcher ends abnormally, and a dump is normally issued. The channel initiator terminates.

User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.

csect-name Dispatcher failed, reason=reason

The channel initiator will attempt to restart the dispatcher. The number of current TCP/IP and LU 6.2 channels allowed will be reduced proportionately.

Investigate the problem reported in the preceding messages.

csect-name Dispatcher not restarted - too many failures

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

The dispatcher is not restarted. The number of current TCP/IP and LU 6.2 channels allowed is reduced proportionately, and other processing capacity might be reduced.

Investigate the problems causing the dispatcher failures.

csect-name Dispatcher restarted, number dispatchers active

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

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

csect-name Outgoing shared channels are restricted from starting for TCP communication

A CHISERVP() service parm flag has been set which restricts the ability for this queue manager from being able to start an outgoing shared TCP channel. For more details on this flag contact IBM support. .

Processing continues. This queue manager is unable to start outgoing shared TCP channels, and will not be selected during WebSphere MQ workload balanced start of a shared channel. This restriction persists until the flag is disabled and the channel initiator is restarted.

csect-name TCP/IP channel limit reduced to nn

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

csect-name LU 6.2 channel limit reduced to nn

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.

csect-name Shared channel recovery started for channels owned by this queue manager

The channel initiator startup procedure is starting the shared channel recovery process, for channels that are owned by itself.

Processing continues

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

csect-name Shared channel recovery started for channels owned by other queue managers in the same QSG

The channel initiator startup procedure is starting the shared channel recovery process, for channels that are owned by other queue managers.

Processing continues

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

csect-name Failed to process channel accounting, RC=retcode

The channel initiator SMF task encountered an error processing channel accounting data. retcode contains the hexadecimal return code.

Processing continues.

Contact your IBM Support Center.

csect-name Failed to process channel initiator statistics, RC=retcode

The channel initiator SMF task encountered an error processing channel initiator statistics data. retcode contains the hexadecimal return code.

Processing continues.

Contact your IBM Support Center.

csect-name SMF task ended abnormally, RC=retcode, reason=reason

For reason C59595, check MEMLIMIT for the channel initiator, or refer to the 256MB recommended limit.

For the other reasons, contact your IBM Support Center.

csect-name Channel accounting collection started

The channel initiator has started collecting channel accounting data.

Channel accounting data for channels with STATCHL (HIGH|MED|LOW) is collected and written to the System Management Facility (SMF).

csect-name Channel accounting collection stopped

The channel initiator has stopped collecting channel accounting data.

Channel accounting data that has been collected for channels with STATCHL (HIGH|MED|LOW) is written to the System Management Facility (SMF).

csect-name Channel initiator statistics collection started

The channel initiator has started collecting channel initiator statistics data.

Channel initiator statistics data is collected and written to the System Management Facility (SMF).

csect-name Channel initiator statistics collection stopped

The channel initiator has stopped collecting channel initiator statistics data.

Channel initiator statistics data that has been collected is written to the System Management Facility (SMF).

csect-name Adapter failed to start

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

The channel initiator will attempt to restart the adapter subtask.

Investigate the problem reported in the preceding messages.

csect-name started adapter subtasks started, failed failed

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.

The channel initiator startup processing continues.

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

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

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

The channel initiator will attempt to restart the adapter subtask.

Investigate the problem reported in the preceding messages.

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

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

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

If you are using user channel exits, check that your exit is setting its parameter lists correctly. User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.

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

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

The adapter subtask is not restarted.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

csect-name Adapter subtask not restarted - too many failures

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

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

Investigate the problems causing the adapter subtask failures.

csect-name Adapter subtask restarted, active subtasks active

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

Processing continues.

csect-name SSL server failed to start

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

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

Investigate the problem reported in the preceding messages.

csect-name started SSL server subtasks started, failed failed

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.

The channel initiator startup processing continues.

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

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

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

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

Investigate the problem reported in the preceding messages.

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

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

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

If you are using user channel exits, check that your exit is setting its parameter lists correctly. User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.

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

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

The SSL server subtask is not restarted.

See the MVS Programming: Assembler Services Reference manual for information about the return code from the ATTACH request. If you are unable to solve the problem, contact your IBM support center.

csect-name SSL server subtask not restarted - too many failures

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

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

Investigate the problems causing the SSL server subtask failures.

csect-name SSL server subtask restarted, active subtasks active

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

Processing continues.

csect-name SSL communications unavailable

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

Processing continues.

Investigate the problem reported in the preceding messages. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.

csect-name SSL key repository name not specified

SSL communications are requested but no SSL key repository name is specified; that is, the SSLTASKS queue manager attribute is non-zero, but the SSLKEYR queue manager attribute is blank.

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

Use the ALTER QMGR command to specify a name for the SSL key repository with the SSLKEYR attribute, and restart the channel initiator. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.

csect-name SSL CRL namelist is empty or wrong type

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

If this message is displayed during CHINIT startup, then MQ communications using SSL are not available.

If the message is displayed after a change to the existing MQ SSL configuration and issuing the REFRESH SECURITY TYPE(SSL) command, then the changed MQ SSL configuration is rejected and the current MQ SSL configuration remains in force. This is to prevent a set of valid and working MQ SSL definitions being inadvertently deactivated by an incorrect change.

Processing continues.

Correct the definitions of the namelist, and start the channel initiator again. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.

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

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

Processing continues; the excess names are ignored.

Correct the definitions of the namelist.

csect-name Unable to access SSL key repository

The SSL key repository, with a name that is specified by the SSLKEYR queue manager attribute, could not be accessed.

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

For more information, refer to System SSL RC 202.

csect-name SSL key repository refresh already in progress

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

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

csect-name AuthInfo auth-info-name has wrong type

The SSL authentication namelist specified by the SSLCRLNL queue manager attribute contains the name of an authentication information object that has an AUTHTYPE of OCSP.

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

Correct the definitions supplied in the namelist so that only authentication information objects with AUTHTYPE of CRLLDAP are named, and restart the channel initiator. If you do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.

csect-name Channel channel-name message reallocation is in progress, msg-progress messages of msg-total processed

The channel channel-name is currently in message reallocation and the progression of this processing is msg-progress message processed out of msg-total number of messages total to be processed.

The channel continues to reallocate messages. This process can take some time to complete if there are a large number of messages assigned to the channel on its transmission queue. An increase in CPU utilization might be observed during this time. Upon completion of the reallocation process the channel ends.

If reallocation is not required, for example because the destination queue manager is now available, reallocation can be interrupted using the command STOP CHANNEL MODE(FORCE).

csect-name Channel channel-name completed message reallocation, msg-processed messages processed

The channel channel-name has completed message reallocation processing, and processed msg-processed number of messages during this processing.

The channel reallocation for this channel has finished and the channel ends.

Determine if messages have been successfully reallocated, and if the channel can be started again.

csect-name Invalid response response set by exit exit-name

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

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

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

csect-name Invalid secondary response response set by exit exit-name

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

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

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

csect-name Invalid exit buffer address address set by exit exit-name

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.

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

Investigate why the user exit program set an invalid exit buffer address. The most likely cause is failing to set a value, so that it is 0.

csect-name Invalid header compression value set by exit exit-name

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.

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

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

csect-name Invalid message compression value set by exit exit-name

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.

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

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

csect-name Invalid data length length set by exit exit-name

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

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

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

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

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.

Investigate why the user exit program set invalid values.

csect-name Channel channel-name beginning message reallocation

The channel channel-name is entering message reallocation because it cannot currently deliver messages to the destination queue manager.

Messages that are not bound to a particular queue manager will be workload balanced. This may take some time if there are a large number of messages assigned to this channel. Check how many using the DISPLAY CHSTATUS(channel-name) XQMSGSA command.

If reallocation is not desired, for example because the destination queue manager is now available, reallocation can be interrupted using STOP CHANNEL MODE(FORCE).

csect-name Channel channel-name unable to stop, message reallocation in progress

A request to stop channel channel-name was made, but the channel cannot stop immediately because message reallocation is taking place.

The channel continues to reallocate messages. This process can take some time to complete if there are a large number of messages assigned to the channel on its transmission queue. An increase in CPU utilization might be observed during this time. Upon completion of the reallocation process the channel ends.

The number of messages to be reallocated can be determined using the DISPLAY CHSTATUS(channel-name) XQMSGSA command.

Turn on the MONCHL attribute of the channel and check how many users are using the DISPLAY CHSTATUS(channel-name) XQMSGSA command. The value of MONCHL should be LOW,MEDIUM or HIGH. See MONCHL for further information.

If reallocation is not desired, for example because the destination queue manager is not available, reallocation can be interrupted using the STOP CHANNEL MODE(FORCE) command.

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

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

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

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

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

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

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

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

csect-name Unrecognized message code ccc

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

Processing continues.

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

csect-name Unable to allocate conversation, channel channel-name connection conn-id TRPTYPE=trptype RC=return-code (return-text) reason=reason

The channel is not started.

The error may be due to an incorrect entry in the channel definition or some problems in the APPC setup. 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 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.

csect-name Connection or remote listener unavailable, channel channel-name connection conn-id TRPTYPE=trptype RC=return-code (return-text) reason=reason

The attempt to start the channel is retried.

Try again later.

A likely cause is that the listener at the remote end was not running or has been started using the wrong port or LU name. If this is the case, perform the necessary operations to start the appropriate listener, and try again.

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

csect-name Error in communications configuration, channel channel-name connection conn-id TRPTYPE=trptype RC=return-code (return-text) reason=reason

The channel is not started.

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

csect-name Connection attempt rejected, channel channel-name connection conn-id TRPTYPE=trptype RC=return-code (return-text) reason=reason

The channel is not started.

Check the appropriate listener has been started on the remote end.

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

csect-name Unable to resolve network address, channel channel-name connection conn-id TRPTYPE=TCP RC=return-code (return-text) reason=reason

The channel is not started.

Check the local TCP/IP configuration. Either the name server does not contain the host or LU name, or the name server was not available.

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

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

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

See 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 might have occurred because the channel at the other end has stopped for some reason, for example an error in a receive user exit.

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

The data is ignored.

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

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

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

SeeCommunications protocol return codes for information about the cause of the return code from the communications system. If using TCP/IP, see Return code 00000461 for more information about the reason code.

csect-name Connection unexpectedly terminated, channel channel-name connection conn-id (queue manager qmgr-name) TRPTYPE=trptype RC=return-code (return-text)

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.

The return code from it was: (in hexadecimal) return-code, (in text) return-text. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.

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

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

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

csect-name Unable to complete bind, channel channel-name connection conn-id TRPTYPE=LU62 RC=return-code (return-text) reason=reason

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: (in hexadecimal) return-code, (in text) return-text. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.

The channel is not started.

Check the APPC/MVS configuration.

See APPC/MVS 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.

csect-name Unable to allocate socket, channel channel-name TRPTYPE=TCP RC=return-code (return-text) reason=reason

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 from TCP/IP was: (in hexadecimal) return-code, (in text) return-text. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.

The channel is not started.

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

csect-name Communications error, channel channel-name TRPTYPE=trptype function func RC=return-code (return-text) reason=reason

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

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

An alternate version of this message exists as follows:

csect-name Communications error, function 'func' RC=return-code reason=reason

For information about the return-code and reason from the PKCS #11 callable service,see the section on ICSF and TSS Return and Reason Codes in the z/OS Cryptographic Services ICSF Application Programmer's Guide

If the error occurred for a channel, the channel is stopped. For a listener, the channel is not started or, in some cases, the listener terminates.

See 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 Distributed queuing message codes for the corresponding message number.

Check for error messages on the partner system that might indicate the cause of the problem.

One possible cause for this message appearing is connected with the use of the Integrated Cryptographic Service Facility (ICSF). See Using ICSF for more information.

csect-name Communications network not available, TRPTYPE=trptype

The channel or listener is not started.

Start the communications system, and try again.

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

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.

The listener is not started.

The failure could be due to another program using the same port number.

See Communications protocol return codes for information about the return code from TCP/IP.

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

An attempt was made to create a new TCP/IP socket because an attach request was received, but an error occurred.

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

The failure might be transitory, try again later. If the problem persists, it might be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.

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

The channel or listener is not started.

Start the communications system, and try again.

csect-name Listener unable to start channel, channel channel-name TRPTYPE=trptype INDISP=disposition connection=conn-id

An incoming attach request arrived from conn-id, 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 '????'.

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.

If a channel is involved, it is not started.

The failure could be because the channel initiator is currently too busy; try again when there are fewer channels running. If the problem persists, increase the number of dispatchers used by the channel initiator.

csect-name Listener stopped, TRPTYPE=trptype INDISP=disposition

trptype is the transport type.

Processing continues. If the listener was not deliberately stopped, the channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.

If the listener was not deliberately stopped, look at any preceding messages relating to the channel initiator or to the TCP/IP, OMVS, or APPC address spaces to determine the cause.

csect-name Invalid local address local-addr, channel channel-name TRPTYPE=trptype RC=return-code (return-text) reason=reason

The channel is not started.

Check the local TCP/IP configuration. Either the name server does not contain the host name, or the name server was not available.

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

csect-name Unable to determine local host name, channel channel-name TRPTYPE=TCP RC=return-code (return-text) reason=reason

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 from it was: (in hexadecimal) return-code, (in text) return-text. For some errors, there might also be an associated reason code reason (in hexadecimal) giving more information.

The channel or listener is not started.

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

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

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

The listener ends abnormally, and a dump is normally issued. The channel initiator will attempt to restart the listener, at the intervals specified by the LSTRTMR queue manager attribute.

User completion codes are generally the result of errors detected by the Language Environment; see the Language Environment for z/OS Debugging Guide and Runtime Messages for information about these codes. Otherwise, contact your IBM support center.

csect-name Listener started, TRPTYPE=trptype INDISP=disposition

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.

Processing continues.

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

An error occurred in the listener select processing. The listener was notified by TCP/IP, but no attach request was received.

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

The failure might be transitory, try again later. If the problem persists, it might be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.

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

An attempt was made to create a new TCP/IP socket because an attach request was received, but an error occurred.

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

The failure might be transitory, try again later. If the problem persists, it might be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.

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

An error occurred in the listener accept processing. The listener was notified by TCP/IP, but no attach request was received.

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

The failure might be transitory, try again later. If the problem persists, it might be necessary to stop some other jobs that use TCP/IP, or to restart TCP/IP.

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

The channel stops.

For a message channel, check the remote end to see why the time out occurred. Note that, if retry values are set, the remote end will restart automatically. If necessary, set the receive wait time for the queue manager to be higher.

For an MQI channel, check that the client application behavior is correct. If so, set the disconnect interval for the channel to be higher.

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

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.

The channel is not started.

If the channel's CONNAME attribute resolves to an IPv6 address, then ensure the stack being used by the combination of the TCPNAME queue manager attribute and the channel's LOCLADDR attribute supports IPv6. If the channel's CONNAME attribute resolves to an IPv4 address, then ensure the stack being used by the combination of the TCPNAME queue manager attribute and the channel's LOCLADDR attribute supports IPv4.

csect-name Communications canceled, channel channel-name TRPTYPE=trptype

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

Restart the channel if appropriate.

csect-name Channel channel-name has initiated a switch of transmission queue from old-xmitq to new-xmitq

A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is issued by the channel initiator when the process of switching the transmission queue from old-xmitq to new-xmitq is started.

The queue manager is notified to start the switching process for the channel.

The channel continues to run after closing the old transmission queue and switching to use the new transmission queue instead.

None.

csect-name Transmission queue status unavailable, channel channel-name

The transmission queue for the cluster-sender channel identified by channel-name cannot be determined because when the queue manager started it was unable to load the persisted transmission queue state from the queue SYSTEM.CHANNEL.SYNCQ.

The channel ends abnormally.

If the queue manager is unable to load the persisted transmission queue state during startup it issues message CSQM561E.

csect-name Cluster transmission queue restricted, channel channel-name, transmission queue xmitq-name

The cluster-sender channel identified by channel-name has been configured to use the transmission queue xmitq-name, however, the use of transmission queues other than SYSTEM.CLUSTER.TRANSMIT.QUEUE has subsequently been disabled by the queue manager mode of operation (OPMODE).

The channel ends abnormally.

csect-name Password protection negotiation failed for channel channel-name, connection conn-id

The channel channel-name could not be established because it failed to agree a password protection algorithm with the remote machine conn-id.

The channel does not start.

Check whether password protection settings prevent interoperability with the remote machine.

Alternatively, consider using SSL or TLS to protect passwords instead. You must use a non-null CipherSpec to protect passwords.

csect-name Auto-definition of channel channel-name suppressed by exit exit-name

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.

The channel is not started.

csect-name Phase one of REFRESH CLUSTER REPOS(YES) has completed, cluster cluster-namen objects changed

Phase one of REFRESH CLUSTER has completed.

Applications attempting to access cluster resources may see failures to resolve cluster resources until phase two of REFRESH CLUSTER is complete.

Phase two is complete once all new information has been received from other members of the cluster.

Monitor your SYSTEM.CLUSTER.COMMAND.QUEUE to determine when it has reached a consistently empty state to indicate that the refresh process has completed.

None.

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

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

None.

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

The repository manager could not process a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster, because the local queue manager provides full repository management service for the cluster.

The command is ignored.

Reissue the command with the correct values or on the correct queue manager. It might be necessary to change the queue manager so that it is not a full repository for the cluster.

csect-name Cluster queue q-name definitions inconsistent

The definition of a cluster queue has different values for the DEFPRTY, DEFPSIST, DEFPRESP, and DEFBIND attributes on the various queue managers in the cluster.

All definitions of the same cluster queue must be identical. Problems might 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.

None.

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

csect-name Repository manager started

The repository manager started successfully.

None.

csect-name Repository manager stopped

Processing continues, but clustering is not available.

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

csect-name Misdirected repository command, target target-id sender sender-id

The repository manager received a command intended for some other queue manager, with an identifier that is target-id. The command was sent by the queue manager with identifier sender-id.

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

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

csect-name Repository command format error, command code command

An internal error has occurred.

The command is ignored, and the error is reported to the sender; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

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

An internal error has occurred.

The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

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

An internal error has occurred.

The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

csect-name Cluster-senders remain for removed queue manager qmgr-name

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.

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

csect-name Only one repository for cluster cluster-name

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

None.

If you require a second full repository, alter the REPOS or REPOSNL attribute of the second queue manager that is to have a full repository for the cluster to specify the cluster name.

csect-name No cluster-receivers for cluster cluster-name

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

None.

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

csect-name No repositories for cluster cluster-name

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

None.

Define a cluster-sender channel for connecting to the queue manager that is the full repository for the cluster, or alter the REPOS or REPOSNL attribute of the queue manager that is to have a full repository for the cluster to specify the cluster name.

csect-name Repository manager error, RC=return-code

An internal error has occurred.

The repository manager attempts to continue processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

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

An internal error has occurred.

The command is ignored; the repository manager continues processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

csect-name Undeliverable repository command, channel channel-name target target-id command code command

The repository manager tried to send a command to another queue manager using channel channel-name. The other queue manager, with identifier target-id, could not be found.

The command is ignored.

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

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

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.

The command is ignored.

Check the definition of the channel on both queue managers to ensure that it is connected to a full repository for the clusters, and that it is in the same clusters on both queue managers.

csect-name Unexpected publication of a cluster queue, cluster cluster-name cluster queue q-name sender sender-id

The repository manager received a publication for cluster queue q-name from another queue manager, with an identifier 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 thus it does not have an interest in the cluster queue.

This can also occur because 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 and caused its view of the cluster to change.

The command is ignored.

If the local partial repository queue manager is supposed to be a full repository for the cluster, use the ALTER QMGR command to specify a repository or repository namelist which contains the cluster. If the local queue manager is correctly a partial repository for the cluster, ensure that the remote queue manager does not have a manually defined cluster sender directed at the local partial repository.

If the message occurs because a command is out of date, the message can be ignored.

csect-name Unexpected deletion of a cluster queue, cluster cluster-name cluster queue q-name

The repository manager received a deletion for cluster queue q-name from another queue manager, with an identifier 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 thus it does not have an interest in the cluster queue.

This can also occur because 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 and caused its view of the cluster to change.

The command is ignored.

If the local partial repository queue manager is supposed to be a full repository for the cluster, use the ALTER QMGR command to specify a repository or repository namelist which contains the cluster. If the local queue manager is correctly a partial repository for the cluster, ensure that the remote queue manager does not have a manually defined cluster sender directed at the local partial repository.

If the message occurs because a command is out of date, the message can be ignored.

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

The repository manager received a command from another queue manager, with an identifier that 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 might 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.

The command is ignored.

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

Ensure the CLUSTER and CLUSNL values are consistent, and that you have not specified a cluster-name when you meant a cluster-namelist.

csect-name Repository unavailable, cluster cluster-name channel channel-name sender sender-id

The repository manager received a command from another queue manager, with identifier sender-id, reporting that it is no longer a full repository for cluster cluster-name.

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.

csect-name Unexpected cluster query received, cluster cluster-name cluster object object-name sender sender-id

The repository manager received a query for cluster object object-name from another queue manager, with an identifier 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.

This can also occur because 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 and caused its view of the cluster to change.

The command is ignored.

If the local partial repository queue manager is supposed to be a full repository for the cluster, use the ALTER QMGR command to specify a repository or repository namelist which contains the cluster. If the local queue manager is correctly a partial repository for the cluster, ensure that the remote queue manager does not have a manually defined cluster sender directed at the local partial repository.

If the message occurs because a command is out of date, the message can be ignored.

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

The repository manager received a command from another queue manager, with identifier 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.

The command is ignored.

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

csect-name Unrecognized message on name

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.

The message is put on the dead-letter queue.

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

csect-name Unable to put repository manager message, target target-id MQCC=mqcc MQRC=mqrc (mqrc-text)

The repository manager tried to send a message to SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager with an identifier that is target-id, but the MQPUT call was unsuccessful.

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

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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.

csect-name Unable to put repository manager message, cluster cluster-name MQCC=mqcc MQRC=mqrc (mqrc-text)

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.

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

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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.

csect-name Unable to commit repository changes

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

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

If this occurs when the channel initiator is stopping, it can be ignored because the local repository information will normally be updated automatically when the channel initiator is restarted. If there is an isolated occurrence at other times, use the REFRESH CLUSTER command to bring the local repository information up to date.

If the problem persists, contact your IBM support center.

csect-name Unable to reallocate messages, channel channel-name MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The messages remain on the transmission queue.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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.

csect-name Repository error for channel channel-name

An internal error has occurred.

The repository manager attempts to continue processing. Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

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

The repository manager could not process a RESET CLUSTER 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.

The command is ignored.

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

csect-name FORCEREMOVE command processed, cluster cluster-name target target

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

None.

csect-name Phase one of REFRESH CLUSTER has completed, cluster cluster-namen objects changed

Phase one of REFRESH CLUSTER has completed.

Applications attempting to access cluster resources may see failures to resolve cluster resources until phase two of REFRESH CLUSTER is complete.

Phase two is complete once all new information has been received from other members of the cluster.

Monitor your SYSTEM.CLUSTER.COMMAND.QUEUE to determine when it has reached a consistently empty state to indicate that the refresh process has completed.

None.

csect-name SUSPEND QMGR command processed, cluster cluster-namen objects changed

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

None.

csect-name RESUME QMGR command processed, cluster cluster-namen objects changed

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

None.

csect-name Unable to backout repository changes

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

The repository manager terminates.

If the repository manager subsequently restarts successfully, or if on restarting the channel initiator the repository manager subsequently starts successfully, this can be ignored.

If not, contact your IBM support center.

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

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

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

Correct the problem reported in the preceding messages.

csect-name Repository manager restarted

The repository manager restarted successfully following an error.

None.

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

The repository manager could not process a RESET CLUSTER 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.

The command is ignored.

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

csect-name FORCEREMOVE command failed, cluster cluster-name target target not found

The repository manager could not process a RESET CLUSTER ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because no information about that queue manager was found in the local repository.

The command is ignored.

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

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

The repository manager found a cluster queue that had been used sometime 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.

The repository manager keeps information about this queue for a further 60 days from when the error first occurred. If information has not been sent to a full repository then this queue is not used to satisfy any new requests for cluster resources made to this full repository.

csect-name Repository available, cluster cluster-name channel channel-name sender sender-id

The repository manager received a command from another queue manager, with identifier sender-id, reporting that it is once again a full repository for cluster cluster-name.

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.

During an operation that requires exclusive access to the cache, another task was found to be registered. If the queue manager finds registrations still exist after waiting for the task to remove its registrations, the queue manager issues this message. The task preventing exclusive access to the repository cache has num-registrations outstanding registrations.

Processing continues.

Determine if this task is still running or terminated. If the task is not running or if the problem persists collect the items listed in the Problem determination on z/OS section and contact your IBM support center.

Information regarding cluster topic topic-name has been sent to this queue manager over a channel from qmgr-name but the queue manager attribute PSCLUS has been set to DISABLED, indicating that Publish/Subscribe activity is not expected between queue managers in this cluster.

The cluster topic definition is ignored and will not be visible from this queue manager.

If you wish to enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED. You may also need to issue REFRESH CLUSTER and REFRESH QMGR commands as detailed in the documentation for the PSCLUS attribute. If you are not using publish/subscribe clusters you should delete the clustered topic object, and ensure PSCLUS is DISABLED on all queue managers.

csect-name Cluster cache is full

No more space is available in the cluster cache area.

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

The problem may be temporary. If it persists, the queue manager must be restarted; this will cause more space to be allocated for the cluster cache area.

Consider changing the cluster cache type system parameter CLCACHE to dynamic, so that more space for the cache will be obtained automatically as required. (If you are using a cluster workload exit, ensure that it supports a dynamic cluster cache.) For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.

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

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

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

None. You can verify that the entry was successfully corrected by issuing the command DISPLAY CLUSQMGR(clusqmgr-name) on the queue manager where this message was issued.

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

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

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

csect-name Error accessing cluster cache entry

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

Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN. The component where the error occurred (message channel agent, repository manager) usually terminates; in some cases, the end result will be that the channel initiator terminates.

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

csect-name New cluster topic definition inconsistent, topic topic-name, queue manager identifier qmid, attribute attr

The definition of the cluster topic topic-name, defined on queue manager identifier qmid has different attr attribute values than one or more cluster topics that already exist in the cluster cache. The existing topic objects are reported by message CSQX466I.

All definitions of the same cluster topic 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 topic and the different instances of the topic have different TOPICSTR values, the behavior of the message transfer depends on which instance of the topic happens to be selected when it is opened.

None.

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

csect-name Cluster topic definitions inconsistent, topic topic-name, queue manager identifier qmid attribute attr

The definition of the cluster topic topic-name, defined on queue manager identifier qmid has different attr attribute value than a cluster topic being added to the cluster cache. The topic object being added is reported by message CSQX465I.

All definitions of the same cluster topic 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 topic and the different instances of the topic have different TOPICSTR values, the behavior of the message transfer depends on which instance of the topic happens to be selected when it is opened.

None.

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

Repository error for topic topic-name, MQCC=mqcc MQRC=mqrc (mqrc-text)

The cluster repository was unable to insert or delete topic topic-name due to an unexpected error in the queue manager.

The repository manager terminates. The channel initiator tries to restart the repository manager after an interval. See message CSQX448E for more information.

For more information about mqcc and mqrc completion codes (mqrc-text provides the MQRC in textual form), see API completion and reason codes.

Contact your IBM support center with the reason code provided for this failure.

csect-name Queue manager qmgr-uuid1 has replaced queue manager qmgr-uuid2 in a cluster due to reuse of channel channel-name

Queue manager qmgr-uuid1 has joined a cluster using a cluster receiver channel with the same name as one that has already been defined by queue manager qmgr-uuid2. All cluster receiver channels used within a cluster must be uniquely named.

Queue manager qmgr-uuid1uses channel channel-name. Queue manager qmgr-uuid2 cannot successfully participate in the cluster while queue manager qmgr-uuid1 is a member.

The use of a channel name currently associated with a different queue manager in the cluster can be intentional, for example it is possible the original queue manager has been deleted and recreated as a new queue manager. However, accidental duplication of a channel name across multiple queue managers would also result in this behavior. If this action was not intended review the configuration of the queue managers.

csect-name Update not received for CLUSRCVR channel channel-name hosted on queue manager qmid in cluster cluster-name, expected n days ago, m days remaining

The repository manager detected that the CLUSRCVR channel has not been republished by its owning queue manager. This republish action should have happened automatically n days ago, or in the time between then and now.

The repository manager will check for this condition approximately every hour, continuing for a period of approximately m days from now. If an update for the CLUSRCVR channel is received during this period, these messages will stop. If no update is received, these messages will continue to be written. However, after this period has elapsed, if no update has been received, the local queue manager will discard its knowledge of this channel, and these messages will stop. You should be aware that Partial Repository queue managers in this cluster will cease to be able to use the channel at about that time.

If the above items have been checked, and this problem persists over several days, causing repeats of this error message in the local queue manager's error logs, contact your IBM support center.

csect-name Channel channel-name has the wrong disposition disposition

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.

The requested action is not performed.

csect-name nn shared channels to restart, nn requests issued

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.

The channel initiator shutdown processing continues.

If the numbers in the message differ, the channel initiator was not able to issue restart requests for all the channels. In this case, use the DISPLAY CHSTATUS command to determine which channels are still owned by the queue manager for the channel initiator that is shutting down, and which therefore have not been restarted, and restart them manually as required.

csect-name Channel channel-name adopted, connection conn-id

Channel channel-name, which was orphaned because of a communications error, has been adopted by a new instance of the channel, from connection conn-id.

Processing continues.

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

An operation was requested on a channel that is active. Because the channel is shared, it might be active on another queue manager. If the channel is a receiver, a previous instance of it might have been orphaned and therefore still be active.

The request fails.

For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and try the operation again. It might 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 avoids 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 mighty be because a loss of connectivity to Db2® occurred. If the problem persists, contact your IBM support center.

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

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.

The request fails.

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

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 might be active on another queue manager. If the channel is a receiver, a previous instance of it might have been orphaned and therefore still be active.

In addition to the CSQX478E for a shared channel, another possible symptom is CSQX514E: csect-name Channel channel-name is active on qmgr-name. The new instance of the channel is starting with a different IP address from the running instance. If the sender's IP address changed or might translate into more than one address, set ADOPTCHK to QMNAME using the ALTER QMGR command. For example, /cpf ALTER QMGR ADOPTCHK(QMNAME) where "cpf" is the command prefix for the queue manager subsystem.

The request fails.

For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and try the operation again. It might 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 avoids the need for manual intervention to handle orphaned receiver channels.

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

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 received from the queue manager qmgr-name.

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

Investigate any preceding error messages to discover why the adopt failed. Either stop the channel manually, or wait for it to terminate, and try the operation again. It might be necessary to use MODE(FORCE) to stop the channel manually.

csect-name Shared channel function not available

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.

The channel command fails or the channel stops.

Check that the Db2 tables required by MQ are correctly defined, and restart the queue manager and Db2 if necessary. If these appear to be running correctly, display the information in the shared channel status (CSQ.ADMIN_B_SCST) and the shared synchronization key (CSQ.ADMIN_B_SSKT) Db2 tables, and contact your IBM support center for further assistance. For further information, and for details of a sample job (CSQ45STB) which shows the information in the Db2 tables, see Problem determination on z/OS .

csect-name Db2 not available

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

The channel command fails or the channel stops.

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

csect-name Error accessing Db2

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

The channel command fails or the channel stops.

Resolve the error reported in the preceding messages.

csect-name Shared channel status error

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.

The channel command fails or the channel stops.

Check that the Db2 tables required by MQ are correctly defined, and restart Db2 if necessary. If Db2 appears to be running correctly, display the information in the shared channel status (CSQ.ADMIN_B_SCST) and the shared synchronization key (CSQ.ADMIN_B_SSKT) Db2 tables, and contact your IBM support center for further assistance. For further information, and for details of a sample job (CSQ45STB) which shows the information in the Db2 tables, see Problem determination on z/OS .

csect-name Shared channel channel-name definitions inconsistent

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.

The request fails.

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

csect-name Maximum instance limit limit exceeded, channel channel-name connection conn-id

There are too many instances of the channel channel-name running to be able to start another. The maximum number allowed is limit and is specified in the MAXINST channel attribute.

The channel does not start.

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

csect-name Maximum client instance limit limit exceeded, channel channel-name connection conn-id

There are too many instances of the channel channel-name running from the connection conn-id to be able to start another. The maximum number allowed is limit and is specified in the MAXINSTC channel attribute.

The channel does not start.

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

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

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

The channel stops. The associated transmission queue might be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.

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

csect-name Invalid MQCD field field-name, value=nnn (Xxxx)

The MQCD structure returned by the channel auto-definition exit had an invalid value in the indicated field. The value is shown in decimal (nnn) and hexadecimal (xxx).

The channel is not defined.

Correct the channel auto-definition exit.

csect-name Channel channel-name started connection conn-id

The specified channel has been started.

If channel-name is an inbound channel (indicated by csect-name containing CSQXRESP) then it was started from connection conn-id. If channel-name is an outbound channel then conn-id will be omitted.

Processing continues.

csect-name Channel channel-name no longer active connection conn-id

Channel channel-name 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.

If channel-name was an inbound channel (indicated by csect-name containing CSQXRESP) then it was started from connection conn-id. If channel-name was an outbound channel then conn-id will be omitted.

Processing continues.

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

csect-name Action not allowed for channel chl-type(channel-name)

The action you requested cannot be performed on channel channel-name. Some actions are only valid for certain channel types. This channel is a chl-type channel type. For example, you can only ping a channel from the end sending the message.

The requested action is not performed.

csect-name Negotiation failed, channel channel-name type=last-segment-type data=xxx connection conn-id

Channel channel-name could not be established due to a negotiation failure between the local queue manager and the remote end using connection conn-id. The last control data received was of type last-segment-type and is accompanied by data indicating the error.

A value of FFFFFFFF (-1) indicates that no error data was sent by the remote end.

The channel is not started.

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

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

During communications with the remote end, the local message channel agent for channel channel-name detected a protocol error.

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

Examine the console log to determine the cause of the failure. This might 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.

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

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.

The channel does not start.

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

csect-name Message receipt confirmation not received for channel channel-name

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

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

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

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

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

The requested operation does not complete.

Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNEL command to correct the problem manually.

csect-name Channel channel-name started, connection conn-id

The specified SVRCONN channel has been started from connection conn-id.

Processing continues.

csect-name Channel channel-name no longer active, connection conn-id

SVRCONN Channel channel-name 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.

The SVRCONN channel-name was started from connection conn-id.

Processing continues.

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

csect-name Current channel limit exceeded channel channel-name connection conn-id

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.

If channel-name was an inbound channel (indicated by csect-name containing CSQXRESP) then it was started from connection conn-id. If channel-name was an outbound channel then conn-id will be omitted.

The channel does not start.

Wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase MAXCHL. A change that increases MAXCHL will not be effective until the channel initiator has been stopped and restarted. If many of the currently operating channels are server-connection channels, consider limiting the number of those using MAXINST or MAXINSTC attributes of a server-connection channel. See Server-connection channel limits for more details.

csect-name Channel channel-name is active on qmgr-name

An operation was requested on a channel that is active. If the channel is shared, it might be active on another queue manager. If the channel is a receiver, a previous instance of it might have been orphaned and therefore still be active.

The request fails.

For operations other than starting the channel, either stop the channel manually, or wait for it to terminate, and try the operation again. It might 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 avoids the need for manual intervention to handle orphaned receiver channels.

csect-name Channel channel-name changed

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

The information shown is for the new channel instance.

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

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.

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

In some cases, the channel initiator will stop as well.

If the return code is a distributed queuing message code, see the corresponding message explanation for more information. Where no such message is described, see 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.

csect-name Error in q-name - channel channel-name repeated

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.

The first set of synchronization information for the channel instance is used, and any others are ignored. Errors may occur if the channel is used.

Avoid using the channel. Remove the extra sets of information from the channel synchronization queue, and rename channels so that they have unique names.

If this does not resolve the problem, contact your IBM support center.

csect-name Channel channel-name not defined connection remote-conn-id

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

The associated remote connection name is remote-conn-id. If the request to use the channel is not from an inbound connection, or the remote connection name cannot be determined, remote-conn-id will be shown as '????'.

The requested operation fails.

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

The message can also be issued if an automatically defined cluster sender channel (CLUSSDRA) has been deleted as a result of issuing a REFRESH CLUSTER command and a putting application still has a queue object open which is using the channel.

csect-name Remote channel channel-name not defined

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

The channel does not start.

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

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

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

Examine the console log for the remote end to determine the cause of the failure. This might 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.

csect-name Remote queue manager unavailable for channel channel-name

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

The channel does not start

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

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

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

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

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

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

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.

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

Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the problem cannot be resolved, the sequence number can be reset manually at the sending end of the channel using the RESET CHANNEL command. (For some queue managers, it might be necessary to issue the RESET CHANNEL command at the receiving end as well.)

csect-name Unable to send message for channel channel-name

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

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

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

csect-name Channel channel-name stopping

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

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

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

csect-name Transmission queue q-name for channel-name has wrong usage type

Queue q-name is named as a transmission queue in the channel definition for channel-name, but it is not a transmission queue.

The channel does not start.

Ensure the queue name is specified correctly in the channel definition. If it is, alter the queue usage attribute of the queue to that of a transmission queue.

csect-name Channel channel-name is already in requested state

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.

The request is ignored.

csect-name Channel channel-name is stopped

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

The request is ignored.

Issue a START CHANNEL command to restart the channel.

csect-name Channel channel-name stopping because exit exit-name is not valid

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

The channel stops. The associated transmission queue might be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.

Ensure that the user exit name is specified correctly in the channel definition, and that the user exit program is correct and available. The channel initiator loads exits from the library data sets under the CSQXLIB DD statement of its started task JCL procedure xxxxCHIN.

csect-name Channel channel-name stopping because of request by exit exit-name

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

The channel stops. The associated transmission queue may be set to GET(DISABLED) and triggering turned off. For auto-defined channels, the channel does not start.

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

csect-name Channel channel-name for queue q-name is not available

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.

The channel does not start.

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

csect-name Unable to commit batch, channel channel-name MQCC=mqcc MQRC=mqrc (mqrc-text)

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

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

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

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

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

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

Ensure that the CCSIDs are valid and that conversion between them is supported. For information about the CCSIDs that are supported, see Codeset names and CCSIDs.

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

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

Processing continues.

Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.

csect-name Channel channel-name closing because disconnect interval expired

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

The channel ends normally.

csect-name Remote channel channel-name has the wrong type

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.

The requested operation is not performed.

csect-name Messages sent to local dead-letter queue, channel channel-name reason=mqrc (mqrc-text)

Processing continues.

Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).

For information about MQFB_* feedback codes see the MQMD description in MQMD - Message descriptor.

csect-name Queue q-name for channel channel-name is get-inhibited

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

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

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

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

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

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

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

csect-name Security exit data for channel channel-name not received, connection conn-id

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

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

Ensure that the security exit for the channel on the remote end has been defined correctly and is available. If it is, check that the exit program operates correctly.

csect-name Remote channel channel-name not available

The channel channel-name at the remote end is currently stopped or is otherwise unavailable. For example, there might be too many channels current to be able to start it.

The channel does not start.

This might be a temporary situation, and the channel will try again. 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.

csect-name No dead-letter queue for qmgr-name, channel channel-name

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

You can get this message with a cluster sender channel during message reallocation. During reallocation, the message is got from the transmission queue and put back again. If the transmission queue is full, then the put fails and tries writing the message to the dead letter queue. If the dead letter queue does not exist, message CSQX565E is produced, and the reallocation changes are rolled back. Reallocation does not happen until the queue full problem is resolved.

The channel stops, except in the case where nonpersistent messages are being sent and the NPMCLASS attribute of the channel is set to FAST, when processing continues. The associated transmission queue may be set to GET(DISABLED) and triggering turned off.

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

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

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

The listener is not started.

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

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

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

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

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

csect-name Channel channel-name exceeded TCP/IP channel limit

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

The channel does not start.

If the maximum allowed is zero, TCP/IP communications are not allowed, and no TCP/IP channels can be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase TCPCHL.

csect-name Channel channel-name exceeded LU 6.2 channel limit

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.

The channel does not start.

If the maximum allowed is zero, LU 6.2 communications are not allowed, and no LU 6.2 channels can be started. If the maximum allowed is non-zero, wait for some of the operating channels to terminate before restarting the channel, or use the ALTER QMGR command to increase LU62CHL.

csect-name Error from PKCS #11 callable service 'func', RC=return-code, reason=reason

An attempt to use PKCS #11 callable service func failed.

The component where the error occurred (message channel agent, supervisor) will continue but the feature being used will be unavailable.

If func is CSFPPRF (Pseudo-random function) the feature affected is password protection. If this feature is not being used then this error can be ignored. If this occurs at channel initiator startup, the password protection algorithm uses STCK instead.

For information about the return-code and reason from the PKCS #11 callable service, see the section on ICSF and TSS Return and Reason Codes in the z/OS Cryptographic Services ICSF Application Programmer's Guide.

For more information about Integrated Cryptographic Service Facility (ICSF), see Using ICSF.

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

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.

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

Correct the problem that caused the invalid message header.

csect-name Channel channel-name exceeded active channel limit

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.

The channel does not start.

Either wait for some of the operating channels to terminate, or stop some channels manually, before restarting the channel, or use the ALTER QMGR command to increase ACTCHL. A change that increases ACTCHL will not be effective until the channel inititator has been stopped and restarted.

csect-name Channel channel-name can now start

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.

csect-name Negotiation failed for channel

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 might not have been possible.

The channel is not started.

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

csect-name Unable to save status for channel channel-name

An internal error has occurred.

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

Information about the error is written to the data set identified by the CSQSNAP DD statement of the channel initiator started task JCL procedure, xxxxCHIN.

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

csect-name Channel channel-name ended abnormally connection conn-id

8

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

If channel-name is an inbound channel (indicated by csect-name containing CSQXRESP) then it was started from connection conn-id. If channel-name is an outbound channel then conn-id will be omitted.

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

Investigate the problem reported in the preceding messages. For more information see, Problem determination in DQM.

csect-name Remote resources in recovery for channel channel-name

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

The channel does not start.

Restart the channel at a later time. If the problem persists examine the console log for the remote end for messages explaining the cause of the problem. This includes an instance of CSQX609E with more details.

csect-name Resources in recovery, channel channel-name MQCC=mqcc MQRC=mqrc (mqrc-text)

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

The channel does not start.

Refer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form), which come from an MQCONNX request.

csect-name Channel channel-name instance is already in requested state

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.

This error will also apply if an attempt is made to stop a SVRCONN channel using the QMNAME parameter. In this case do not use the QMNAME parameter. In order to stop a specific SVRCONN instance use the CONNAME parameter

The request is ignored.

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

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

0

csect-name SSL key repository refresh started

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

Message CSQX619I will be issued when the refresh is complete.

csect-name SSL key repository refresh processed

The refresh of the cached SSL key repository is complete.

Channels will be restarted as required.

csect-name System SSL error, channel channel-name connection conn-id function 'func' RC=return-code

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 '????'. The remote connection is conn-id. func is the name of the System SSL function that gave the error, and return-code is the return code (in decimal unless func is 'gsk_fips_state_set' in which case it is in hexadecimal).

The channel is stopped.

See Secure Sockets Layer (SSL) and Transport Layer Security (TLS) return codes for z/OS for the cause of the return code from System SSL and refer to the SSL Function Return Codes in the z/OS Cryptographic Services System SSL Programming manual for more information.

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

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

The SSL server subtask terminates.

See Secure Sockets Layer (SSL) and Transport Layer Security (TLS) return codes for z/OS for the cause of the return code from System SSL and the System Secure Sockets Layer Programming Guide and Reference manual for more information.

csect-name Channel channel-name requires ICSF for SSLCIPH(ciph)

Channel channel-name is using a cipherspec ciph that requires Integrated Cryptographic Service Facility (ICSF) callable services, but ICSF is not available. Sometimes the channel name and cipherspec are unknown and so are shown as "????". If known, the cipherspec is shown in the message as a 4-character code.

Recognized values are shown in message CSQX631E.

The cipherspecs that use GCM or ephemeral elliptic curve algorithms require ICSF.

The channel will not start.

Ensure ICSF is available, or change the cipherspec that the channel is using to one that does not require ICSF. If you are using ICSF and running the queue manager with SSLFIPS(YES), ensure that ICSF is configured to run in FIPS mode.

For more information, see System SSL RC 455.

csect-name Channel channel-name requires SSL

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

The channel does not start.

If SSL is required, investigate why it is not available and take action as appropriate. One possible cause, is that there is no certificate available owned by the user who initiated the channel address space. If this is the case, you need to re-configure the user ID to have a certificate with the correct value, by issuing the command RACDCERT ID(xxxx), where xxxx is the user ID.

Check that you have the SSL queue manager properties set, for example SSLTASKS must be greater than 0.

If SSL is not required, change the channel definition so that SSL is not used.

csect-name Cipher specifications differ, channel channel-name local=local-ciph (local-protocol) remote=remote-ciph (remote-protocol) connection conn-id

The channel does not start.

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

csect-name SSL certificate has no associated user ID, remote channel channel-name, connection conn-id - channel initiator user ID used

The certificate sent from the remote end (from connection conn-id) 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 the certificate or a matching certificate name filter are not defined to the external security manager (ESM), or that the certificate contains fields that are not understood by the ESM.

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

If you are using certificate name filtering, you can create a filter that matches this certificate. See Working with Certificate Name Filters (CNFs) for details on associating a user ID with a certificate.

If the security you want on your channel does not require the use of the SSL mapped certificate user ID, you can define the channel to use Put Authority (PUTAUT) with a value of ONLYMCA instead of DEF, or ALTMCA instead of CTX and this message is not issued as no security checking for the channel is using the SSL mapped certificate user ID that could not be found. See Receiving channels using TCP/IP for more details about which user IDs are used for security checking on a receiving channel using TCP/IP.

Alternatively, change the SSLPEER channel attribute or create a CHLAUTH record to prevent this certificate being accepted from the remote channel. See Channel authentication records for more details.

csect-name SSL certificate for remote channel channel-name failed local check, connection conn-id

The certificate sent from the remote end (from 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 '????'.

The channel will not start.

Ensure that the SSL certificate connected to the key repository at the remote end is valid, and that the signing certificate(s) have been connected to the key ring on the local queue manager so that the certificate sent can be authenticated.

For full details about SSL certificates and key repositories see Security.

This error might indicate that the remote end of the channel is configured to send the wrong certificate. Check the certificate label configuration at the remote end of the channel and ensure that the local key repository contains all of the necessary CA certificates.

For more information, refer to System SSL RC 8.

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

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

The channel will not start.

Firstly, you need to check that the SSL certificate in the key ring at the local queue manager qmgr-name is valid, for example, in TRUST status and not expired.

Secondly, you also need to check that both the signing certificate (for example the certificate from the certificate authority) and the signed certificate have been connected to the key repository on the remote end, so that the certificate sent can be verified at the remote end.

The certificate used is either named on the channel in the CERTLABL attribute, or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute (for a shared channel). If no certificate label is found in any of these attributes, then the certificate is named 'ibmWebSphereMQqsg-name' (for a shared channel) or 'ibmWebSphereMQqmgr-name', or a default certificate in the key ring is used.

For full details about SSL certificates and key repositories see Security.

For more information, refer to System SSL RC 414.

csect-name Invalid cipher specification ciph for channel channel-name

The SSL cipher specification value for channel channel-name is not valid. The value is shown in the message as a four-character code.

Recognized values are shown in message CSQX631E.

This error can occur if the remote end is configured to use SSLFIPS(YES). Check the errors at the remote end to determine if this is the case.

The channel will not start.

Correct the SSL cipher specification for the channel. If the remote end is configured to only accept FIPS-certified cipher specifications, change the channel to use a FIPS-certified cipher spec. See Specifying CipherSpecs for details on which cipher specifications are FIPS-certified.

For more information, refer to System SSL RC 402, RC 412, and RC 422.

csect-name Distinguished name does not match peer name, channel channel-name name='dist-name' connection conn-id

The distinguished name, dist-name, specified in the SSL certificate at the remote end (from connection conn-id) 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 '????'.

The channel will not start.

This error might indicate that the remote end of the channel is configured to send the wrong certificate. Check the certificate label configuration at the remote end of the channel and ensure that the local key repository contains all of the necessary CA certificates.

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.

If the SSL Peer name specification needs to match a number of different distinguished names for multiple different remote SSL certificates, consider using channel authentication records to define rules to allow or block specific SSL peer names instead of the SSL Peer name specification on the channel definition. See Channel authentication records for more details.

csect-name No SSL certificate for remote channel channel-name, connection conn-id

The remote channel (from connection conn-id) 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 '????'.

The channel will not start.

Ensure that the SSL certificate is connected to the key repository of the remote end; alternatively, if appropriate, change the local channel definition so that its SSLCAUTH attribute is set to OPTIONAL.

For full details about SSL certificates and key repositories see Security.

For more information, refer to System SSL RC 403.

csect-name SSL communications error for channel channel-name, connection conn-id

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 '????'. The remote connection is conn-id.

The channel will not start.

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

For more information, refer to System SSL RC 406.

csect-name No cipher specification for remote channel channel-name, connection conn-id

No SSL cipher specification was supplied by the remote channel channel-name (from connection conn-id), but one was required. In some cases the channel name cannot be determined and so is shown as '????'.

The channel will not start.

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

csect-name Invalid peer name, channel channel-name attribute=key-name

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

The channel will not start.

Correct the SSL peer name for the channel.

csect-name Cipher specification error for remote channel, channel channel-name, connection conn-id

An error occurred with the SSL cipher specification for remote channel channel-name (from connection conn-id). In some cases the channel name cannot be determined and so is shown as '????'.

The channel will not start.

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

csect-name No SSL certificate for channel channel-name

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

The channel does not start.

Ensure that the key ring of the local queue manager qmgr-name has an SSL certificate connected to it which is associated with the queue manager. If you have configured a certificate label, check that the certificate exists.

The certificate used is either named on the channel in the CERTLABL attribute, or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute (for a shared channel). If no certificate label is found in any of these attributes, then the certificate is named 'ibmWebSphereMQqsg-name' (for a shared channel) or 'ibmWebSphereMQqmgr-name', or a default certificate in the key ring is used.

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

csect-name Peer name error for remote channel channel-name, connection conn-id

An error occurred with the SSL peer name for remote channel channel-name (from connection conn-id). In some cases the channel name cannot be determined and so is shown as '????'.

The channel will not start.

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

csect-name Unable to determine peer name for remote channel channel-name

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

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

Ensure that the SSL certificate 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.

The certificate used is either named on the channel in the CERTLABL attribute, or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute (for a shared channel). If no certificate label is found in any of these attributes, then the certificate is named 'ibmWebSphereMQqsg-name' (for a shared channel) or 'ibmWebSphereMQqmgr-name', or a default certificate in the key ring is used.

Check that the local and remote channel definitions are correct.

For full details about SSL certificates and key repositories, see Security.

csect-name Certificate cert-label missing for channel channel-name

An SSL/TLS certificate cert-label, 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 '????'.

In some cases this message will appear multiple times, once for each affected channel.

The channel does not start.

Ensure that the SSL/TLS certificate named cert-label is in the key ring and that it is valid, and that the queue manager is running with OPMODE(NEWFUNC,800).

Alternatively, change the certificate label configuration so that the channel uses a valid certificate.

The certificate used is either named on the channel in the CERTLABL attribute, or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute (for a shared channel). If no certificate label is found in any of these attributes, then the certificate is named 'ibmWebSphereMQqsg-name' (for a shared channel) or 'ibmWebSphereMQqmgr-name', or a default certificate in the key ring is used.

DISPLAY QMGR SSLKEYR

RACDCERT ID(chinit-user-id) LISTRING(key-ring-name)

For more information, refer to return codes 6 and 407 in SSL Function Return Codes.

csect-name Error accessing LDAP server for channel channel-name

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

The channel will not start.

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

For more information, refer to System SSL RC 11.

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

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.

The channel will not start.

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

For more information, refer to System SSL RC 401.

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

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

The channel will not start.

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

For more information, refer to System SSL RC 413.

csect-name Channel channel-name stopping because remote SSL socket closed, connection conn-id

The remote end of a channel using SSL communications (from connection conn-id) 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 '????'.

The channel stops.

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

For more information, refer to System SSL RC 420.

csect-name LDAP server unavailable for channel channel-name

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

The channel does not start.

Ensure that the LDAP server is running.

For more information, refer to System SSL RC 427.

csect-name Certificate label cert-label not used on channel channel-name, remote connection conn-id

The SSL or TLS channel channel-name is configured to use certificate label cert-label. However, the remote peer did not send the necessary information to allow the local channel to use the correct certificate. The remote host is conn-id.

This error occurs when the local channel definition has a certificate label and the remote peer does not support selection of certificates.

The channel will not start.

Ensure that the remote peer supports certificate label configuration. Refer to Digital certificate labels, understanding the requirements for details of certificate label requirements. Alternatively, alter the local channel definition so that it does not specify a certificate label.

csect-name Channel channel-namespecified a weak or broken SSL CipherSpec sslciph

The channel is unable to start because it is configured to use a CipherSpec that is potentially insecure.

The channel is prevented from starting.

Examine the CipherSpec specified in the SSLCIPH parameter and consider using a more secure CipherSpec.

//CSQWEAK DD DUMMY

//CSQXSSL3 DD DUMMY

You need to specify both of the preceding dummy DD statements, if you want to enable a weak SSLv3-based CipherSpec.

There are alternative mechanisms that can be used to forcibly re-enable weak CipherSpecs, and SSLv3 support,if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Unable to complete SSL key repository refresh

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

The refresh is incomplete.

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

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

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.

Processing continues.

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

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

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

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

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

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

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

The channel does not start.

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

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

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

The channel does not start.

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

csect-name SSL key repository has no certificates

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

Channels using SSL communications will not start.

Add the user certificate and any necessary certificate authority (CA) certificates to the key repository. Ensure that existing certificates are valid, have not expired, and are marked as trusted.

For more information, refer to System SSL RC 7.

csect-name SSL key repository has no CA certificates

The SSL key repository (that is, the key ring in the external security manager) does not contain any valid certificate authority (CA) certificates. A channel using SSL communications needs at least one CA or self-signed certificate to perform client authentication.

Channels using SSL communications will not start.

Add the user certificate and any necessary certificate authority (CA) certificates to the key repository. Ensure that existing certificates are valid, have not expired, and are marked as trusted.

For more information, refer to System SSL RC 109.

csect-name No self-signed certificate for channel channel-name, connection conn-id

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 '????'. The remote connection is conn-id.

The channel is not started.

For more information, refer to System SSL RC 417.

csect-name SSL private key error for channel channel-name

The SSL certificate used 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 '????'.

The certificate used is either named on the channel in the CERTLABL attribute, or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute (for a shared channel). If no certificate label is found in any of these attributes, then the certificate is named 'ibmWebSphereMQqsg-name' (for a shared channel) or 'ibmWebSphereMQqmgr-name', or a default certificate in the key ring is used.

The channel is not started.

Ensure that the private key associated with the SSL certificate used is available. Ensure that the ICSF started task is running if the private key is stored in ICSF. See Giving the channel initiator the correct access rights for information on how to actually give the CHINIT the proper accesses to get to its keys (if in ICSF).

For more information, refer to System SSL RC 428.

csect-name SSL certificate revoked by CA for channel channel-name, connection conn-id

The SSL certificate has been revoked by the certificate authority (CA). The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The remote connection is conn-id.

The channel is not started.

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

For more information, refer to System SSL RC 431.

csect-name No SSL CA certificate for channel channel-name, connection conn-id

The SSL key repository does not contain a certificate for the certificate authority (CA). The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The remote connection is conn-id.

The channel is not started.

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

For more information, refer to System SSL RC 435.

csect-name CRL cannot be processed for channel channel-name, connection conn-id

A Certificate Revocation List (CRL) is not valid and cannot be processed. The channel is channel-name; in some cases its name cannot be determined and so is shown as '????'. The remote connection is conn-id.

The channel is not started.

Contact the certificate authority and obtain a replacement CRL.

For more information, refer to System SSL RC 436.

csect-name Cipher specifications based on the SSLv3 protocol are disabled.

Cipher specifications based on the SSLv3 protocol are not enabled, and channels configured to use those cipher specifications fail when started.

Processing continues.

If you do not need to use cipher specifications based on the SSLv3 protocol, then no action is required.

//CSQWEAK DD DUMMY

//CSQXSSL3 DD DUMMY

You need to specify both of the preceding dummy DD statements, if you want to enable a weak SSLv3-based CipherSpec.

There are alternative mechanisms that can be used to forcibly re-enable weak CipherSpecs, and SSLv3 support,if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Cipher specifications based on the SSLv3 protocol are enabled.

Cipher specifications based on the SSLv3 protocol are enabled, and channels can be configured to use those cipher specifications.

Processing continues.

If you need to use cipher specifications based on the SSLv3 protocol, then no action is required.

If you do not need to use cipher specifications based on the SSLv3 protocol, you should remove the override that enables the use of SSLv3.

See message CSQX690I for information on enabling SSLv3.

csect-name Weak or broken SSL cipher specifications are disabled.

Cipher specifications that are known to be weak or broken are not enabled, This includes all SSLv3-based cipher specifications. Channels configured to use those cipher specifications fail when started.

Processing continues.

If you do not need to use broken or weak cipher specifications, no action is required.

//CSQWEAK DD DUMMY

//CSQXSSL3 DD DUMMY

You need to specify both of the preceding dummy DD statements, if you want to enable a weak SSLv3-based CipherSpec.

There are alternative mechanisms that can be used to forcibly re-enable weak CipherSpecs, and SSLv3 support,if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Weak or broken SSL cipher specifications are enabled.

Cipher specifications known to be weak or broken are enabled, and channels can be configured to use those cipher specifications.

Processing continues.

If you need to use weak or broken cipher specifications, no action is required.

If you do not need to use weak or broken cipher specifications, you should remove the override that enables the use of weak or broken cipher specifications.

See message CSQX692I for information on enabling weak or broken cipher specifications.

csect-name Cipher specifications based on the TLS v1.0 protocol are disabled.

Cipher specifications based on the TLS v1.0 protocol are not enabled, and channels configured to use those cipher specifications fail when started.

Processing continues.

//TLS10OFF DD DUMMY

There are alternative mechanisms that can be used to forcibly disable cipher specifications based on the TLS v1.0 protocol, if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Cipher specifications based on the TLS v1.0 protocol are enabled.

Cipher specifications based on the TLS v1.0 protocol are enabled, and channels can be configured to use those cipher specifications.

Processing continues.

If you need to use cipher specifications based on the TLS v1.0 protocol, then no action is required.

If you do not need to use cipher specifications based on the TLS v1.0 protocol, see message CSQX694I for information on how to disable TLS v1.0.

csect-name Weak or broken SSL cipher specifications blocked by listener.

Weak or broken SSL cipher specifications have been blocked by the listener. Consequentially you will not receive a successful SSL handshake with any cipher specifications marked as either weak or broken.

Processing continues.

If you do not want to be able to negotiate with the listener using weak or broken cipher specifications then you can disable them by adding a dummy Data Definition (DD) statement named WCIPSOFF to the channel initiator JCL. For example:

//WCIPSOFF DD DUMMY

There are alternative mechanisms that can be used to achieve the same behavior if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Listener will only negotiate System SSL default cipher specifications.

The listener will only negotiate with cipher specifications that are listed by default on the System SSL default cipher specification list.

Processing continues.

If you only want to be able to negotiate with the listener using the cipher specifications listed on the System SSL default cipher specification list, then you can enable this behavior by adding a dummy Data Definition (DD) statement named GSKDCIPS to the channel initiator JCL. For example:

//GSKDCIPS DD DUMMY

There are alternative mechanisms that can be used to achieve the same behavior if the Data Definition change is unsuitable. Contact IBM Service for further information.

csect-name Invalid cipher specification ciph for FIPS mode for channel channel-name

The SSL cipher specification value for channel channel-name is not FIPS-certified and the queue manager has been configured to run with SSLFIPS(YES). The value is shown in the message as a four-character code.

Recognized values are shown in message CSQX631E.

In some cases, when the channel is responding to an inbound request, the cipher specification cannot be determined and so is shown as '????'.

The channel will not start.

Correct the channel to use a FIPS-certified cipher specification, or if the queue manager should not be running in FIPS mode, alter the queue manager to use SSLFIPS(NO). See Specifying CipherSpecs for details on which cipher specifications are FIPS-certified.

For more information, refer to System SSL RCs 402 and 412.

csect-name mqapi-call failed, MQRC=mqrc (mqrc-text)

The indicated IBM MQ mqapi-call failed for the specified reason code mqrc, (mqrc-text).

Typically the component in which the error occurs terminates. When the component is a message channel agent, the associated channel is stopped.

Refer to API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

csect-name CHLAUTH cache load failed, all inbound channels blocked

The CHLAUTH cache has failed to load. All inbound channels has been blocked from starting until the problem has been fixed. See previous message for the cause of the problem.

All inbound channels are blocked from starting.

Look for the previous related message for the cause of the problem.

csect-name Channel channel-name from ipaddress would have been blocked due to userid, Detail: detail

The inbound channel channel-name would have been blocked from address ipaddress because the active values of the channel were mapped to a userid that should be blocked. Access is allowed as the channel authentication record is in warning mode.

The active values of the channel were detail.

The channel is started.

Examine the channel authentication records to ensure that the correct settings have been configured. If the channel authentication record was not in warning mode the channel would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH command can be used to query the channel authentication records.

csect-name Channel channel-name from ipaddress has been blocked due to userid, Detail: detail

The inbound channel channel-name was blocked from address ipaddress because the active values of the channel were mapped to a userid that should be blocked.

The active values of the channel were detail.

The channel is not started.

Examine the channel authentication records to ensure that the correct settings have been configured. The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH command can be used to query the channel authentication records.

csect-name Channel channel-name from ipaddress has been blocked due to USERSRC(NOACCESS), Detail: detail

The inbound channel channel-name was blocked from address ipaddress because the active values of the channel matched a channel authentication record configured with USERSRC(NOACCESS).

The active values of the channel were detail.

The channel is not started.

Examine the channel authentication records to ensure that the correct settings have been configured.

The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH can be used to query the channel authentication records.

If no hostname is shown in the message next to the IP address, and CHLAUTH rules using hostnames are in place, ensure that your Domain Name Servers can correctly resolve the IP address to a hostname and that your queue manager is configured with REVDNS(ENABLED).

csect-name Connection from address ipaddress has been blocked due to matching rule ip-address-pattern

The inbound connection from the address was blocked because it matches one of the blocked addresses, ip-address-pattern, in the channel authentication table.

The channel is not started.

Examine the channel authentication records to ensure that the correct settings have been configured. The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH can be used to query the channel authentication records.

csect-name Channel channel-name is configured to not use the dead-letter queue

Channel channel-name failed to deliver a message to its destination. The report option MQRO_DISCARD_MSG was not specified for the message and the channel has been configured to not use the dead-letter queue through the attribute setting USEDLQ(NO).

The channel either discards the message, or the channel ends, in accordance with the NPMSPEED attribute setting.

Investigate the cause of this error, then either correct the problem that prevented the channel delivering the message, or enable the channel to use the dead-letter queue.

csect-name Connection from address ipaddress would have been blocked due to matching rule ip-address-pattern

The inbound connection from the address ipaddress would have been blocked because it matches one of the blocked addresses, ip-address-pattern, in the channel authentication table. Access is allowed as the channel authentication table is in warning mode.

The channel is started.

Examine the channel authentication records to ensure that the correct settings have been configured. If the channel authentication record was not in warning mode the channel would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH command can be used to query the channel authentication records.

csect-name Channel channel-name from ipaddress would have been blocked due to USERSRC(NOACCESS), Detail: detail

The inbound channel channel-name would have been blocked from address ipaddress because the active values of the channel matched a channel authentication record configured with USERSRC(NOACCESS). It was not blocked due to the channel authentication record being in warning mode.

The active values of the channel were detail.

The channel is started.

Examine the channel authentication records to ensure that the correct settings have been configured. If the channel authentication record was not in warning mode the channel would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether the channel authentication records are used. The DISPLAY CHLAUTH command can be used to query the channel authentication records.

csect-name DNS lookup for address address using function 'func' took n seconds

An attempt to resolve address address using the 'func' function call took n seconds to complete. This might indicate a problem with the DNS configuration.

Processing continues.

Ensure that the DNS is correctly configured on the local system.

If the address was an IP address then the slow operation was a reverse DNS lookup. Some DNS configurations are not capable of reverse DNS lookups and some IP addresses have no valid reverse DNS entries.

If the problem persists, consider disabling reverse DNS lookups until the issue with the DNS can be resolved.

csect-name Connection authentication failed for user user-id due to CHLAUTH with CHCKCLNT(chckclnt-value), Detail: detail

The user ID user-id and its password were checked because the inbound connection matched a channel authentication record with CHCKCLNT(chckclnt-value).

The active values of the channel were detail. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH command can be used to identify the relevant CHLAUTH record.

This message accompanies a previous error to clarify the reason for the user ID and password check.

The channel is not started.

Refer to the previous error for more information.

Ensure that a password is specified by the client application and that the password is correct for the User ID.

Alternatively, to avoid the authentication check you can amend the CHLAUTH record CHCKCLNT attribute. However, allowing unauthenticated remote access is not recommended.

csect-name Client application appl-name from address ip-address did not supply a user ID and password, Detail: detail

The client application appl-name running on host ip-address did not supply a user ID and password. The channel authentication (CHLAUTH) record for the connection requires a user ID and password, but none was supplied.

The active values of the channel were detail. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH command can be used to identify the relevant CHLAUTH record.

The channel is not started.

Ensure that the application provides a valid user ID and password, or change the queue manager connection authority (CONNAUTH) configuration to OPTIONAL to allow client applications to connect which have not supplied a user ID and password.

csect-name The user ID and password for client application appl-name from address ip-address cannot be checked, Detail: detail

The user ID and password for the client application appl-name running on host ip-address cannot be checked. The channel authentication (CHLAUTH) record for the connection requires an authentication check, but the queue manager is not configured to use connection authentication for clients.

The active values of the channel were detail. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH command can be used to identify the relevant CHLAUTH record.

The channel is not started.

Change the CHLAUTH configuration so that client authentication is not required, or alter the queue manager connection authority (CONNAUTH) configuration to enable client authentication checks.

csect-name Channel initiator active

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

csect-name nn adapter subtasks started, nn requested

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.

csect-name nn dispatchers started, nn requested

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.

csect-name nn SSL server subtasks started, nn requested

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.

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

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

csect-name nn channels current, maximum nn

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.

csect-name nn channels active, maximum nn, including nn paused

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.

csect-name nn channels starting, nn stopped, nn retrying

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

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.

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

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.

csect-name TCP/IP system name is name

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.

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

This is issued in response to the DISPLAY CHINIT command for each TCP/IP listener that is active.

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

This is issued in response to the DISPLAY CHINIT command for each LU 6.2 listener that is active.

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