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. If it occurs in other cases, contact your IBM support center to report the problem.
ExplanationThe SSL key repository does not contain any valid certificate authority certificates. A channel using SSL communications needs at least one CA or self-signed certificate to perform client authentication. System programmer responseChange the remote channel definition so that the value specified for the SSL cipher specification is the same as that of the local channel. System programmer responseCorrect 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.
(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. System actionThe queue manager is notified to start the switching process for the channel.
ExplanationThe channel initiator startup procedure has started the requested number of adapter subtasks; started adapter subtasks started successfully and failed adapter subtasks did not start. ExplanationThe shared channel synchronization queue queue-name is defined on a Coupling Facility structure that does not support recovery. This means that if the structure fails, shared channels might report message sequence errors, and might also lose messages. ExplanationThe channel initiator SMF task encountered an error processing channel initiator statistics data.
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.
If this occurs at channel initiator startup, the password protection algorithm uses STCK instead. System programmer responseChange the definition of the transmission queue so that it is not inhibited for MQGET calls. System programmer responseIssue a START CHANNELcommand to restart the channel. System programmer responseNote that a STOP CHANNEL hire solutions architect command puts the channel into STOPPED state. System programmer responseEnsure that the name is specified correctly and the channel definition is available. System programmer responseExamine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNELcommand to correct the problem manually.
System actionProcessing continues, but remote subscriptions might continue to exist which are no longer valid. This could cause a build-up of publications for mergers and acquisitions for dummies this Queue Manager on remote transmission queues. System actionThe component where the error occurred usually ignores the error and continues processing.
ExplanationThis is issued in response to the DISPLAY CHINIT command if the channel initiator is active. ExplanationThe 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. It was not blocked due to the channel authentication record being in warning mode. ExplanationThe inbound channel channel-name was blocked from address ipaddress because the active values of the channel matched a channel authentication record configured with USERSRC. If we do not need to use cipher specifications based on the TLS v1.0 protocol, see messageCSQX694I for information on how to disable TLS v1.0. 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.
In such situations this message will be periodically repeated until maintenance has completed, at which time message CSQX872I will be output. Refer to previous messages to determine why the dead-letter queue is not available. Explanation The send on channel channel-name could not be completed and the message could not be redirected to the dead-letter queue.
System programmer responseStart the communications system, and try again. If it is of the form 10009nnn or 20009nnn, it is a distributed queuing message code. System programmer responseCorrect the definitions of the namelist. ExplanationSSLKEYR is required when communicating with the service.
CSQX696Icsect-name Weak or broken SSL cipher specifications blocked by listener. If we 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. ExplanationA Certificate Revocation List is not valid and cannot be processed. ExplanationThe SSL certificate has been revoked by the certificate authority . ExplanationThe SSL key repository does not contain any valid certificates. System programmer responseExamine the console log for messages that might indicate why the refresh could not be started.
There are alternative mechanisms that can be used to forcibly re-enable weak CipherSpecs, and SSLv3 support,if the Data Definition change is unsuitable. For full details about SSL certificates and key repositories, see Securing. This error can occur if the remote end is configured to use SSLFIPS. Check the errors at the remote end to determine if this is the case. For full details about SSL certificates and key repositories see Securing. Likely causes are that the certificate or a matching certificate name filter are defined to the external security manager , or that the certificate contains fields that are not understood by the ESM.
System programmer responseRestart the channel if appropriate. System actionThe listener continues to run, but the connection is not created. System programmer responseThe failure might be transitory, try again later.
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. ExplanationA severe error, as reported in the preceding messages, occurred during channel initiator processing; the channel initiator is unable to continue. System programmer responseRefer to API completion and reason codes for information about mqcc and mqrc (mqrc-text provides the MQRC in textual form).
Check that we have the SSL queue manager properties set, for example SSLTASKS must be greater than 0. ExplanationThe channel channel-name at the remote end is currently stopped or is otherwise unavailable. For example, there might be too many channels https://forex-reviews.org/ current to be able to start it. ExplanationAn MQGET failed because the transmission queue had been previously inhibited for gets. System programmer responseAdd an appropriate channel definition at the remote end, and retry the operation.
System actionMessage CSQX190E is issued giving more details, and the channel stops. The channel initiator was unable to connect to the LDAP server specified in an authentication information object listed in the SSL CRL namelist. ExplanationThe channel initiator has stopped collecting channel initiator statistics data. ExplanationThe channel initiator has stopped collecting channel accounting data.
Note, however, that processing of the CSQINPX command data set might still be in progress; its completion is shown by message CSQU012I. ExplanationThe 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. System programmer responseChannel initiator parameters are specified by queue manager attributes.
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 . System actionIf the error occurred during the channel initiator startup procedure, the channel initiator does not start. In other cases, the component where the error occurred does not start and the function it provides is unavailable; in most cases, the end result is that the channel initiator terminates.
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. ExplanationThe repository manager restarted successfully following an error. The channel initiator will try to restart it after the specified interval.
ExplanationThe channel channel-name is entering message reallocation because it cannot currently deliver messages to the destination queue manager. ExplanationThe user exit exit-name returned a header compression value that was not one of those which were negotiated as acceptable when the channel started. ExplanationThe SSL authentication namelist specified by the SSLCRLNL queue manager attribute contains the name of an authentication information object that has an AUTHTYPE of OCSP. ExplanationA REFRESH SECURITY TYPE command was issued, but an SSL key repository refresh was already in progress. The channel initiator does not have permission to read the specified key repository. If a system completion code is shown, see the MVS System Codes manual for information about the problem in your exit.
ExplanationThe channel channel-name did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote end. ExplanationChannel channel-name ended abnormally because of a severe problem, as reported in the preceding messages. System programmer responseIf password protection is being used, start ICSF. ExplanationThe specified channel was waiting to start, because there were too many channels active to be able to start another. One or more of the active channels has terminated, so this channel can now start. System actionThe component where the error occurred will continue but the feature being used will be unavailable.
System programmer responseWait for some of the operating channels to terminate before restarting the channel, or use theALTER 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. ExplanationThe 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. System programmer responseCorrect the definitions of the namelist, and start the channel initiator again.
ExplanationThe 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 is set to MQXR2_USE_EXIT_BUFFER. ExplanationThe SSL key respository, with a name that is specified by the SSLKEYR queue manager attribute, could not be accessed. ExplanationThe SSL authentication namelist specified by the SSLCRLNL queue manager attribute has more names than are supported. System actionThe SSL server subtask is not restarted; processing capacity might therefore be reduced.