Having issued the command DIS CHSTATUS(QM1.TO.QM2) ALL, if the output shows the status of the channel is BINDING or REQUESTING, then it has not yet successfully connected to the partner. Do the following:
DIS CHSTATUS(QM1.TO.QM2) ALL
Initiating MCA substate 1 | Responding MCA substate 2 | Notes |
---|---|---|
NAMESERVER | The initiating MCA is waiting for a nameserver request to complete. Ensure that the correct hostname has been specified in the channel attribute, CONNAME, and that your name servers are set up correctly. | |
SCYEXIT | SCYEXIT | The MCAs are currently in conversation through a security exit. For more information, see Are there exits processing?. |
CHADEXIT | The channel autodefinition exit is currently executing. For more information, see Are there exits processing?. | |
RCVEXIT SENDEXIT MSGEXIT MREXIT |
RCVEXIT SENDEXIT MSGEXIT MREXIT |
Exits are called at channel startup for MQXR_INIT. Review the processing in this part of your exit if this takes a long time. For more information, see Are there exits processing?. |
SERIALIZE | SERIALIZE | This substate only applies to channels with a disposition of SHARED. |
NETCONNECT | This substate is shown if there is a delay in connecting due to incorrect network configuration. | |
SSLHANDSHAKE | SSLHANDSHAKE | An SSL handshake is made up of a number of sends and
receives. If network times are slow, or connection to lookup CRLs are slow,
this affects the time taken to do the handshake.
On WebSphere MQ for z/OS this substate can also be indicative of not having enough SSLTASKS. |
Notes:
|
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
rtmchast |