When using LU 6.2, make sure that your definitions are consistent throughout the network. For example, if you have increased the RU sizes in your CICS Transaction Server for OS/390 or Communications Manager definitions, but you have a controller with a small MAXDATA value in its definition, the session may fail if you attempt to send large messages across the network. A symptom of this may be that channel negotiation takes place successfully, but the link fails when message transfer occurs.
When using TCP, if your channels are unreliable and your connections break, you can set a KEEPALIVE value for your system or channels. You do this using the SO_KEEPALIVE option to set a system-wide value, and on WebSphere MQ for z/OS, you can also use the KeepAlive Interval channel attribute (KAINT) to set channel-specific keepalive values. On WebSphere MQ for z/OS you can alternatively use the RCVTIME and RCVTMIN channel initiator parameters. These options are discussed in Checking that the other end of the channel is still available, and KeepAlive Interval (KAINT).
The Adopt MCA function enables WebSphere MQ to cancel a receiver channel and to start a new one in its place.
For more information about this function, see Adopting an MCA. For details of its parameters, see WebSphere MQ for z/OS System Setup Guide.
When a group TCP/IP listener is started, it registers with DDNS. But there may be a delay until the address is available to the network. A channel that is started in this period, and which targets the newly registered generic name, fails with an 'error in communications configuration' message. The channel then goes into retry until the name becomes available to the network. The length of the delay will be dependent on the name server configuration used.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzae10343 |