Channel retry error

The explanation can come from the z/OS Client Web Enablement Toolkit or from the IBM Cloud Product Insights service. ExplanationThe queue manager was unable to register with the IBM Cloud Product Insights service. Turn on the MONCHL attribute of the channel and check how many users are using the DISPLAY CHSTATUS(channel-name) XQMSGSA command. System programmer responseThe number of messages to be reallocated can be determined using the DISPLAY CHSTATUS(channel-name) XQMSGSA command. System actionMessage CSQX190E is issued giving more details, and the channel stops.

All cluster receiver channels used within a cluster must be uniquely named. System programmer responseAlter the definitions of the topic on the various queue managers so that they have identical values for all attributes. We can verify that the entry was successfully reintroduced by issuing the command DISPLAY CLUSQMGR(clusqmgr-name) on the queue manager where this message was issued. We can verify that the entry was successfully corrected by issuing the command DISPLAY CLUSQMGR(clusqmgr-name) on the queue manager where this message was issued. The repository managers on those queue managers have not ended abnormally.

ExplanationAn 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 certificate used is either named on the channel in the CERTLABL attribute, nordfx review or named on the queue manager in the CERTLABL attribute or CERTQSGL attribute . If no certificate label is found in any of these attributes, then the certificate is named ‘ibmWebSphereMQqsg-name’ or ‘ibmWebSphereMQqmgr-name’, or a default certificate in the key ring is used.

ExplanationThe user exit exit-name returned an invalid secondary response code in the ExitResponse2 field of the channel exit parameters . ExplanationThe user exit exit-name returned an invalid response code in the ExitResponse field of the channel exit parameters . System programmer responseIf reallocation is not required, for example because the destination queue manager is best indicator for intraday trading now available, reallocation can be interrupted using the command STOP CHANNEL MODE. System programmer responseIf the message indicates that some SSL server subtasks failed, investigate the problem reported in the preceding messages. System programmer responseIf the message indicates that some adapter subtasks failed, investigate the problem reported in the preceding messages.

If reallocation is not required, for example because the destination queue manager is not available, reallocation can be interrupted using the STOP CHANNEL MODE command. System programmer responseIf reallocation is not required, for example because the destination queue manager is now available, reallocation can be interrupted using STOP CHANNEL MODE. System programmer responseInvestigate why the user exit program set an invalid data length. System programmer responseInvestigate why the user exit program set an invalid secondary response code. System programmer responseInvestigate why the user exit program set an invalid response code. System programmer responseDetermine if messages have been successfully reallocated, and if the channel can be started again.

SeeSpecifying CipherSpecs for details on which cipher specifications are FIPS-certified. ExplanationThe SSL cipher specification value for channel channel-name is not FIPS-certified and the queue manager has been configured to run with SSLFIPS. ExplanationThe SSL key repository does not contain a certificate for the certificate authority . ExplanationA self-signed certificate cannot be validated as it is not in the SSL key repository. ExplanationThe cached SSL key repository is being refreshed, which involves stopping all the channels that use SSL communications.

WebSphere MQ SENDER channel fails with CSQX202E

You define a new sender channel on z/OS to connect to the Windows queue manager. Message CSQX202E is written to the channel initiator address space joblog. In phase one this will discard all locally cached information for the cluster and request new information from other members of the cluster when necessary.

ECONNABORTED means that some other process, such as a router, firewall or one of the myriad of processes that interact with a socket as it connects between one partner and the other, disconnected tickmill the socket. From an MQ perspective, your MQ Channel will automatically retry the connection and hopefully reconnect. Only this part of the reason code is intended as an interface for programmers.

ExplanationThere are too many channels current to be able to start another. The maximum number allowed is specified in the MAXCHL queue manager attribute. System programmer responseExamine the console log to determine the cause of the failure.

Distributed queuing messages CSQX ..

Check that the local and remote channel definitions are correct. System programmer responseReview the remote console log to determine the cipher specification error. ExplanationThe 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 before the channel can be started. ExplanationThe certificates sent to the remote end using the connection conn-id during SSL handshaking could not be validated. ExplanationThe certificate sent from the remote end (from connection conn-id) during SSL handshaking could not be validated.

ExplanationThe channel is closing because no messages arrived on the transmission queue within the disconnect interval. System programmer responseExamine the console log for the remote end to determine why the message cannot be received, and then restart the channel. System programmer responseEither start the remote queue manager, or retry the operation later. System programmer responseDetermine why the remote end did not accept the last batch of messages. System programmer responseChange either the local or remote channel definition so that the values specified for the message sequence number wrap value are the same. ExplanationBecause Db2 is not available, or is no longer available, the channel initiator cannot do processing for a shared channel.

Checkout the latest offers!

Applications attempting to access cluster resources may see failures to resolve cluster resources until phase two of REFRESH CLUSTER is complete. System programmer responseCheck whether password protection settings prevent interoperability with the remote machine. ExplanationThe channel channel-name could not be established because it failed to agree a password protection algorithm with the remote machine conn-id. System programmer responseRestart the channel if appropriate.

ExplanationA request to stop a particular instance of channel channel-name was made , but the channel instance was already in the specified state, or in the process of reaching that state. ExplanationAn attempt to use PKCS #11 callable service func failed. ExplanationA 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. ExplanationThere is no definition of channel channel-name at the remote end.

System programmer responseEnsure 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, ensure that ICSF is configured to run in FIPS mode. System programmer responseRefer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form), which come from an MQCONNXrequest.

Closed as program error

ExplanationThis 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. ExplanationThis 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. System programmer responseUse the ALTER QMGRcommand to specify a name for the SSL key repository with the SSLKEYR attribute, and restart the channel initiator. If we do not want to use SSL communications, set the SSLTASKS queue manager attribute to 0.

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. For an MQI channel, check that the client application behavior is correct.

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. ExplanationThe repository manager has received information about a cluster for which no full repositories are known. ExplanationThe repository manager has received information about a cluster for which it is the only full repository. Problems might arise if your applications rely on one of these attributes to determine messaging behavior. The channel continues to run after closing the old transmission queue and switching to use the new transmission queue instead.

Support

However, the channel initiator could not find a defined and available channel to start. ExplanationChannel 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. ExplanationThe 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. ExplanationThe 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. The queue is q-name in cluster_name, and its queue manager is qmgr-name.

This error occurs if the channel was stopped with mode FORCE and the communications session was canceled. System programmer responseSee Communications protocol return codes for information about the cause of the return code from TCP/IP. 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.

System programmer responseSee 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 Codesmanual for information about the reason code. ExplanationSSL communications are requested but the SSL authentication namelist specified by the SSLCRLNL queue manager attribute is empty or not of type AUTHINFO. System programmer responseInvestigate the problem reported in the preceding messages. ExplanationA SSL server subtask failed, but was successfully restarted by the channel initiator.

Generally this is used to identify the issuing module and represents a module ID. This page describes the second number reported in our MQ error message, the one called reason. As the page says, these are sometimes referred to as errnojrs or as errno2 values. Both qmgrs are recycled in the early morning around the same time, so it is natural that often one side is not ready for the other side to connect. System programmer responseIf the problem cannot be resolved, collect the items listed in the Problem Determination section and contact your IBM® support center. ExplanationThe cluster cache compression activity, indicated by message CSQX876I, has now completed.

Sss is the system completion code, and uuu is the user completion code . System actionProcessing 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. ExplanationA severe error, as reported in the preceding messages, occurred during channel initiator startup processing.

The number of current TCP/IP and LU 6.2 channels allowed will be increased proportionately. System programmer responseSee the z/OS UNIX System Services Messages and Codesmanual for information about the codes from the service request. ExplanationDuring dispatcher startup processing, one of the essential dispatcher processes could not be scheduled. This message is logged when the amount of virtual storage used by the channel initiator is more than 75%.

ExplanationAn error occurred in the listener select processing. System programmer responseIf 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. If the communications protocol is TCP/IP, it is possible that the remote host does not recognize the local host. 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.

The channel initiator is starting and the queues used by the distributed pub/sub offloader have not been defined because distributed pub/sub command processing is not required. ExplanationA token in a name/token pair required by the channel initiator could not be retrieved. ExplanationThe channel initiator startup procedure has started the requested number of dispatchers; started dispatchers started successfully and failed dispatchers did not start. 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 .